cubase settings not same as Ntrack
I am starting to get a bit frustrated with the setup process of Ntrack. I feel that the program itself is very good but I can not seem to get it to function as smooth as Cubase.
Equipment: Ntrack 4.2.1 build 2099, Reason, Cubase LE, Presonus Firepod, OS XP home version (stripped down), 3.2 mghz CPU, 2gig memory, 7200 rpm 80 gig HD.
Problem: I can not run the spectralizer with out a ton of pops and clicks. I have addjusted the latency on the firepods ASIO driver control panel without any success. I also noticed that the CPU usage at the bottom left of the screen is up to anywhere from 34% to 64% depending on the amount of FX I am using with 3 recorded tracks of audio. The bottom right of the screen tells me that there is only 3% CPU load with the FX running. I am totally stumped with this because when I run Cubase LE with a hell of alot more plug-ins I have no problems at all. Also, on occasion, while running reason with Ntrack, reason will lock up as well as Ntrack crashing. I would like to eventually switch over to Ntrack exclusively beacuase of the cost factor but I need some help to fix the above problems. (I am almost certain that it is a latency issue but need some advice).
I would really appreciate any help that anyone can give me. As I said I am totally befuddled!
i think to get the performance increase you want you nay have to upgrade to V5 - you can download the latest version and it will run in DEMO mode for quite some time, apart from the DEMO MODE TONES every few minutes it will run unhindered - it wont interfere with your present installation of V4, then you can see if performs better with your plugins -
Dr J
Thanks for the info.
I may try that, but what in the world could be causing this issue to arise in the first place?
I looked at the v5 release notes and did not notice anything that would lead
me to believe that this version would solve any issues. Again, I pray that there is some little adjustment which I have over looked that will correct my problems. If anyone has had any similar problems please let me know.
the implementation of .NET into N -
Dr J
Quote: (DR Jackrabbit @ Sep. 19 2007, 12:21 AM)
the implementation of .NET into N -
Dr J
I do remember this being a major discussion here!
When it was new, the .NET framework was a real booger, and caused problems for lots of us.
The buzz now is that v5 has got it sussed and in working order.
I haven't ordered v5, but that's the general word.
Quote:
The buzz now is that v5 has got it sussed and in working order.
Ummm... nope. Not here at least. I grabbed the latest 2308 and tried out n AGAIN. Nope. Click, pop, fart and crashes galore. Just trying to drag a standard 16/44.1 wav file onto the time line with the "File chooser" hickey crashed the program... on THREE different PC's. All of them up to date, XP OS... etc... blah... blah.
It's broke.
D
And after all those nice reports of success I’d been reading here! Well, there you have it.
Just amazes me when people have trouble with Ntrack. I’m using version 5 with absolutely no problems. I have a friend still running version 4, but I can’t get him to upgrade because it works well. I guess it’s the same always, if it works we don’t say much, but if it doesn’t we make a lot of noise.
So, in the interest of “balance.” I have Ntrack, I use it, I have used it for a long time, I like it and any problems I have had were quickly cured.
Hi bax3 and Gents:
I don’t use any other multi-track editor other than n-Track.
However, I do use other track editors…
I do find that everytime I upgrade from build-to-build I have to run the tracks in the timeline a few times to align the data packets so they stream evenly, from the Hard drives…
Otherwise, the audio will stutter and go-on… But after a few passes from end-to-end start-to-finish the audio reproduction will settle down and become stable…
Then all is fine…
I do notice that the tracks I have on the timeline at present uses in the neighbourhood of some 81% on the average… and stays in the “RED” from beginning-to-end, of the song…
But that’s with 17 tracks and 6 VST Plug ins on Tracks Groups and Master strips…
Several of the plugs are hi-usage resource plugs…
Bill…
Quote: (bax3 @ Sep. 23 2007, 12:55 AM)
Just amazes me when people have trouble with Ntrack. I'm using version 5 with absolutely no problems. I have a friend still running version 4, but I can't get him to upgrade because it works well. I guess it's the same always, if it works we don't say much, but if it doesn't we make a lot of noise.
So, in the interest of "balance." I have Ntrack, I use it, I have used it for a long time, I like it and any problems I have had were quickly cured.
Nothing "amazing" about it... how is Flavio going to know something is broken if we don't post it here and/or give bug reports?
I really like n-Track! So in the interest of "balance"
I want to see it perform as well or better than other hosts! Nothing wrong with that is there?D
Ok here it is again.
I went ahead and paid for the V5 upgrade in hopes that it would solve some of the issues. Guess what? The main issue I am now having is that every time I try to use reason through the rewire interface within N, Reason stops responding. What the heck is going on? The program is supposed to be compatable with Reason but I cannot get the two to play well together. Does anyone have any suggetions?
Process: I open N as the host program. Every thing is fine. N is stable. I then open up reason either through N or out side of N and the same issue occurs. It locks up. Sometimes Reason will load a little but always seems to stop responding!
I have re-installed N to no avail. I have all the newest drivers that I am aware of and still this. I can open up Cubase LE w/ reason and have absolutly no issues. I keep thinking that there is some little setting that I have forgotten about that eventually will come to me but at this time I am at a loss.
Thanks in advance for any help you can give.
Hi BogoZ:
There’s gonna be a post that’ll shed some light on this and get you up-and-running…
In the meantime I would think if there is a conflict or something causing this with n-Track or n-Track creates a “Close Exception”, n-Track would create a .dmp file and attempt to send the file off to n-Track Support…
Are you on line with your setup?
And…
Do you have the box checked to have n-Track “Call Home”, when n-Track is launched?
There’s a check box in the n-Track settings will will allow n-Track to call home…
I’m sure you are aware of this…
There are some guys that don’t allow n-Track to report or Call Home…
But that’s a nice feature to have working…
In my opinion…
of course…
Bill…
Thanks Bill.I will be waiting for the posting.
To answer your question about being on line, no. My studio laptop is not connected. I have tried to keep my studio cpu away from as much exposure to anything that could cause any unwanted problems. I will look into the dump file and try to get a copy sent in if the posting does not help.
Again thanks for the info.
Just a thought: check to see if Cubase or Reason is running in the background when you start your computer.
What I mean: some programs like to load into memory at start up and reserve their opperating “space”.
This could cause a conflict if Cubase was “reserving” Reason for itself.
Does Reason have a setting that ties it to cubase?
I have no knowledge that either program does this, but the error you are getting happens sometimes when two programs try to access the same program.
I have had trouble with programs “grabbing” the sound mixer so that it is not available to other programs, and the same thing might be happening to Reason.
You probably won’t like this, but you might try uninstalling Reason and Cubase and Ntrack and load back just Ntrack and Reason and see if that works. If it does add Cubase and see if everything still works - of doesn’t.
Thanks Bax3,
That is a very good point! Let me check into this one.
Thanks!
Hi Gents:
It appears that more-and-more software and program designers want their customers/buyers to have their computers on line for Calling Home to tally the number of uses that products are used and to confirm their legitimacy and for any number of other reasons…
Even some of the Heavy duty plug manufacturers want their products calling home to see what host programs are serving their use…
Is that the right thought process?
Another thing…
Some of these plug manufacturers allow installation of their plugs on a memory stick or portable drive so that their owners can move these plugs from studio-to-studio…
This allows producers/mixers/and trackers to take their tools with them…
Forget about computers-and-DAWs…
and all…
I know…
This is somewhat OFF TOPIC to your thread but we’re still in the same Church…
just a different PUE…
Bill…
Alright,
I was just trying to do a few short tracks and started a new project inside of N and reason. Everything was looking pretty good until all of a sudden this error popped up Rewire DLL error, thus locking up N:
RewireDLL\portable\rewireDLL.cpp(980):verify failure
What is up with this?
I tried to locate a folder inside of the program files that holds the dump but was unable to find it.
Hi Again BogoZ:
The n-Track .dmp file is created if n-Track closes as the result of faliure or error…
That is an automatic creation by n-Track.
But someone can confirm if the computer has to be online and connected… If it’s not the result of n-Treack then possibly the .dmp file is not created…
The path to the .dmp file can be searched…
look for .dmp file
Start/search for files and folders… I thought I knew the Path to where they are stored…
I don’t remember…
Someone knows the path…
Anyway, they are numbered…
Bill…
Again, thank you very much for your insight into the workings of N Bill. It’s not looking good at this time for me to try to find a solution. I truly want to find a fix but I’m starting think there is something more to the fix than I am capable of finding.
At a loss for words…