Greetings:
I will make this as short as possible. Please let me know if you need more detail. I’ll be glad to fill it in.
First, the problems. I cannot make NTrack work consistently w/ MIDI. I click on play, and the MIDI track starts 500ms early. Next time I try it, it starts 250 ms late. 3rd timie, right on the money. Now, it seems I’ve introduced a CPU issue along with it. With only 6 or 7 tracks (2 of which are midi) my cpu util is jumping to the 70 and 80% range. Now, I freely confess that I have a bunch of real time effects and I’m not editing destructively, so keep that in mind. It still doesn’t seem right though that 20 VST plugins would bring the thing to it’s knees.
I have a Dell 2.4Ghz Intel proccessor (P4) computer w/512mb ram and an 80GB hard drive running Windows XP, SP2, coupled with an EMU 0404 sound card. All of my software is up to date. I am running the lastest drivers for the EMU, the latest version of NTRACK (just checked to make sure there’s nothing more current). I have defraged and uninstalled 'til I can’t any more. I have 40 GB free on the disk, 300 MB of RAM free and available.
I have experimented in the following way: 1. Read through the forum. I’ve uninistalled and reinstalled the sound card. I’ve been to the musicxp.net site and followed it. I’ve updated my bios and made all the tweaks I can. I’ve messed with the latency settings in the EMU control panel (no big deal, but just to point out that I have). I’ve messed with priorities, Windows settings, removing services, shutting down Antivirus settings and disconnected it from the Network. It’s been really great to see the improvements on my computer – it’s certainly sped everything up, excepting NTrack. 
MIDI still starts randomly slow or fast and the tracks are now jittering like a caffeine junkie going thru DT’s. OH! Also, if I click on anything while it’s playing - the song stops or stutters.
I’m sure that I’ve just over looked something here and would appreicate any thoughts or comments. My next step will be to format the box and start all over, but MAN I don’t want to do that. 
BTW, it is a valid, licensed version of NTrack.
First, make sure you have “Preferences -> MIDI Settings -> Timer to use” set to “Wave”. No doubt you tried that, but make sure you’ve gone back to it.
I don’t know anything about the EMU so I can’t help you with that.
Concerning the CPU time, the first thing to do is get rid of the FFT display on the timeline, if you have that going. It can be a big CPU hog, depending on its configuration. (It’s highly configurable, in case you didn’t already know that.)
If that doesn’t cure the CPU woes, try clicking the green “FX” box at the upper left hand corner of the timeline display. It will go gray, and all effects except EQ will stop. (Maybe even EQ, but I think it keeps working.) If the CPU time goes down to a reasonable level (e.g., 20% or less), then you’re using an effect that’s a CPU hog. Find out which one. (Easiest way is use the Mixer view and click the little green squares to make them red and see which one is the offender.)
None of this (other than the wave timer thing) addresses the synchronization problem, but let’s tame the CPU issues first and meanwhile someone might know more about that. Let us know what you find out.
BTW, 20 VST plugins can be very significant. If you’re using the same plugin on lots of tracks with the same settings, you’d be better off using an aux channel (depending on the kind of plugin – e.g., reverb and echo are good on an aux). It also depends on the plugin: some are very efficient; others are so bad you can only run one or two of at a time. There are workarounds for this kind of problem (e.g., “Freeze”).
Hey Jeff,
I have similar cpu issues to Bill. What exactly is this “FFT display on the timeline” thingy?
Thanks
Mike
What driver version for the EMU? I think some early units shipped with V1.60 and then EMU posted V1.71 on their support site to address a few issues with the 0404. Most notably was 192khz sampling support. If you have 1.71 and don’t need or want 192khz, you might try rolling back to 1.60 to see if things improve or not. Also, what are you using to “play” your MIDI tracks? VSTi’s or something? I know the MS Wavetable synth is notorious for causing the bugga-boos you are talking about…
TG
PS Oh yeah, don’t use MIDI Mapper for anything. That thing is a surefire synch issue waiting to happen!
I had similar benefits from rolling back my Audiophile 24/96 delta drivers; the cpu usage improved dramaticly
Mike
| Quote (Mike Floutier @ April 12 2005,12:07) |
| Hey Jeff, I have similar cpu issues to Bill. What exactly is this "FFT display on the timeline" thingy? Thanks Mike |
When you have the EQ window open and see the pretty little dancing red line. That is a frequency spectrum display. While useful at times, it is a resource hog.
TG
"What driver version for the EMU? I think some early units shipped with V1.60 and then EMU posted V1.71 on their support site to address a few issues with the 0404. Most notably was 192khz sampling support. If you have 1.71 and don’t need or want 192khz, you might try rolling back to 1.60 to see if things improve or not. Also, what are you using to “play” your MIDI tracks?"
Hey–thanks everyone for the responses. I AM running the EMU 1.71 driver. I may try rolling that back. I’m actually quite busted by the FFT thing though. I had no clue that it could be a culprit. To take that one step further–is the FFT a setting which is “in use” even if I’m not viewing it, or just by closing it out, do I release the cpu cycles, or do I need to change some global parameter that I haven’t found yet.
Regarding midi stuff, I’m one of the old timer midi guys. I still play it all in live thru the keyboard and use my Alesis rack to actually produce the sounds. I haven’t figured out the soundfont stuff yet. I’m using the EMU driver for that as well.
Hi Bill,I would guess that your first problem could be solved by running a regcleaner. I had simular issues and my reg'mechanic found a few ntrack related kinks, fixed them and those cpu surges stoped. I'm not sure about the odd starting points for your midi file but that might be related.
Tom
Do you have “Compensate for latency” checked in preferences? This whole thngs sounds weird. I’ve got an EMU 1820M and it works just peachy with N, MIDI, and my external MIDI controllers. Heck, I have been having a swell time using VSTs in realtime with my little drum controller at 7ms… I know this combo should work for you. There just has to be a check box screwing you somewhere.
That panel has two functions: a parametric EQ and a frequency display. They’re very handy to have together – watching the frequency display while adjusting EQ. When you make the panel go away, the display stops running, but the EQ keeps working. The EQ is not the resource hog, just the frequency display.
BTW, if you want to be able to adjust the EQ while playing (duh!) and you’re short on CPU cycles, you can also configure the display to do very little (and maybe turn it off). Don’t have N up right now so I can’t be more specific, but right click and try a shorter window size. There’s something else too but I don’t recall (like Reagan said).
Good point, Bubba – that matters. Though I wouldn’t expect it to vary.
Hey,
Sorry about the Some weirdo thing caused me to miss part of your post or you only had entered part of it??
Anyway, yep check out what Bubba and Jeff are saying. I too have an EMU 1820m and it works great with n-Track. It’s a safe bet some little setting is messing you up. BTW, do you have another DAW package to try to confirm it is for sure n-Track? Did the 0404 come with Cubase or something?
TG
| Quote (gtr4him @ April 12 2005,19:49) |
| Hey, Sorry about the Some weirdo thing caused me to miss part of your post or you only had entered part of it??Anyway, yep check out what Bubba and Jeff are saying. I too have an EMU 1820m and it works great with n-Track. It's a safe bet some little setting is messing you up. BTW, do you have another DAW package to try to confirm it is for sure n-Track? Did the 0404 come with Cubase or something? the 0404 came w/ Cubasis VST and works really really well. I've done one tune w/12 tracks and a mess of effects w/o trouble. But I really like what NTrack offers, and since I spent the dough on it, would really like to see it work. Besides, I like this forum! thanks all much for the input. |
Yup. I fat fingered the keyboard and submitted it that way. I laughed at your response. NBD.
the 0404 came w/ Cubasis VST and works really really well. I've done one tune w/12 tracks and a mess of effects w/o trouble. But I really like what NTrack offers, and since I spent the dough on it, would really like to see it work. Besides, I like this forum! thanks all much for the input.
In regard to the "compensate for latency" that Bubba brought up, I don't see it. I see "Compensate for VST Latency", but that doesn't seem right (yes, it's checked though) and under MIDI settings, "Compensation ms" which is not a radio button or check box; rather a field prefilled in at 750.
I can agree with your assessment of Cubase VST versus n-Track. Cubase is convoluted and UGLY IMO. It works well for me though on the occasions I use it. n-Track just looks and feels familiar somehow. Even the first time I used it.
I think that MIDI COmpensation setting is for compensating KNOWN lag values in complex in inefficient MIDI setups. I’ve never had to mess with it. I’m stuck back at work again so when I get home I’ll try to poke around and see if I find something in n’s preferences for you to try.
<!–QuoteBegin>
| Quote |
| Besides, I like this forum! |
Yep. These guys on here are a vast resource of knowledge. Often, I can find a solution to a problem just by searching the forum. Good folks here.
TG
TG–
Find anything out?
Not yet Bill. Problems at the “salt mine” have kept me away from any DAW’ing. Work SUX!
TG
“Life is what happens to you while you’re busy making other plans”
--John Lennon
Thanks for trying. Don’t rush on account of me!