I want to know if there are any conflicts
a few people have these, tho’ not me - I’m audigy platinum pro. No real probs reported. Hang around and you should get some decent feedback.
Maaszy
Been away for a few days. Just caught this thread. I have an 1820M. No problems, sounds GREAT! I use n-Track V3.3 though. Not brave enough to jump into v4.0 yet…
The EMU stuff is looking to be great bang for the buck cards.
TG
| Quote (gtr4him @ Sep. 28 2004,15:47) |
| Been away for a few days. Just caught this thread. I have an 1820M. No problems, sounds GREAT! I use n-Track V3.3 though. Not brave enough to jump into v4.0 yet.......... The EMU stuff is looking to be great bang for the buck cards. TG |
I have the 1820M, but it does not work with nTrack, I have tried everything, including getting my money back
, no luck, now when I tried to open nTrack [click on teh icon] it comes up as an installation file and then, it "says" is the wrong file...........I know I know, this is not the place but I have to get it out
That doesn’t even remotely sound like a sound card problem, Vilo. Sounds like n-Tracks isn’t installed properly…Of course the first time you double click ntrack_sw.exe it will be an installation file since that is the ntracks installation file. Sound like you are running that thinking it’s the app.
| Quote (phoo @ Sep. 28 2004,19:23) |
| That doesn't even remotely sound like a sound card problem, Vilo. Sounds like n-Tracks isn't installed properly.....Of course the first time you double click ntrack_sw.exe it will be an installation file since that is the ntracks installation file. Sound like you are running that thinking it's the app. |
The problem is that I can reeinstall the program and it works for a while and then all of a sudden, when I click on the same nTrack icon, it comes up with the installation file
, But besides that I have 1001 problems with it..........
Dunno, I have an 1820M and it works fine with n-track too. I think Phoo is on to something. There is no way that the main exe can turn into or trigger an installer. I think there might be some icon confusion going on.
There is some different in the shortcuts created for V3 and V4. You can see them by opening up the properties to the short cut and clicking on the Shortcut tab.
The shortcut to V4 does not have a target location, and the target is a grayed out "n-Tracks Studio 4"
The shortcut to V3 had “n-Track Studio” as the target location and the fill path to the exe as the Target.
“Start in” points to were n-Tracks is installed.
V4 had no compatibility tab and Security shows different groups and users.
I have double-clicked on the V4 icon in the past and had V4 not run, but that was a really early beta build. I think it just popped up the looking for for app thing…what any shortcut pops up when what it tries to start is missing.
My guess is that ntrack.exe (the app) isn’t visible to the shortcut and it quickly finding the install exe. That could happen if the install exe is in the system path and is named something similar enough that the automatic search thinks it’s a match.
That sure would be a kicker if that’s what’s happening.
| Quote (phoo @ Sep. 29 2004,14:07) |
| There is some different in the shortcuts created for V3 and V4. You can see them by opening up the properties to the short cut and clicking on the Shortcut tab. The shortcut to V4 does not have a target location, and the target is a grayed out "n-Tracks Studio 4" The shortcut to V3 had "n-Track Studio" as the target location and the fill path to the exe as the Target. "Start in" points to were n-Tracks is installed. V4 had no compatibility tab and Security shows different groups and users. I have double-clicked on the V4 icon in the past and had V4 not run, but that was a really early beta build. I think it just popped up the looking for for app thing...what any shortcut pops up when what it tries to start is missing. My guess is that ntrack.exe (the app) isn't visible to the shortcut and it quickly finding the install exe. That could happen if the install exe is in the system path and is named something similar enough that the automatic search thinks it's a match. That sure would be a kicker if that's what's happening. |
The funny thing is it works for a while, and then all of a sudden starts doing the same thing again, until I reeinstall the program
hey I’m curious about the emu cards. are they of good quality ? (I’ve currently got a Layla 24/96)
I’ve been wanting something that could do effects for the headphone mix that didn’t require LIVE input processing so my CPU didn’t get eaten up. I see that the EMU cards can supposedly record dry while processing effects for the mix at the same time? that’d be awesome. Plus the less expensive one is only $200 so I could get two for my layla and have 24 inputs 
With the current drivers, multiple cards are not supported. i.e. only one 1212M or 1820(M) or 0404. EMU says they will have multi-card support. We’ll see. I have the 1820M. It sounds great. I’m a happy tracker…
TG
EDIT** Yes, you can record dry and monitor with the EMU DSP effects. It’s a snap to setup. **END EDIT
hi
I am using the e-mu 1212m sound card and emulatorX.I can,t seem the get the emulatorX vst instrument to produce any sound.I am getting no midi signal reading in emulatorX.I find this is so with the 3.3 plus 4.0 version of n-track.I use it with cubasis vst 4.0 all works fine.But cubasis vst 4.0 is a real pian in the butt to get up and running so far.It sure would be nice to get this bug worked out as the interface of n-track is so much easyer to use and i can get back to the music.I was wondering if they will ever fix the problem or should i keep read the cubasis manual inside out a few more time, and just give up hope on using n-track with emulatorX vst instruments.I fine that N-track become very unstable also and dosen,t seem to want to respond to general commands and chashes sometimes.Hopwe they work the bugs out.I will keep writting both n-track and e-mu in the hopes of them fixing it.
I just got my 1820 system from E-bay. It’s definitely a bit more complicated to set up than my old AudioPCI:-)
This has been discussed in a previous article about E-mu 1820 drivers, but I’m wondering if Flavio has done any bug fix yet, i.e, is n-Track now functioning with the new drivers (1.6) for the E-mu? Judging by the previous post in this string, there seems to remain some problems.
My n-Track v. 3.3 hangs when it is scanning the VST’s. Is this problem solved now in v.4? It has reportedly to do with the powerFX VST-plugin. With the old E-Mu drivers, it does not hang.
Or is it only because I’m using the 16-bit version? I suspect ASIO is only provided in 24 bit, since N responds with an “upgrade to 24bit version”-nagscreen whenever I’m using ASIO instead of WDM.
You folks who are running 1820/1820M or any other E-Mu card without problems, what version of n-Track are you using?
TIA!
You can’t force 16 bit mode with the ASIO driver. Unfortunately, that’s the only multi-channel driver for the EMU. Pop for the 24 bit license and you are golden.
The EMUPowerFX.dll that gets put in your plugin directory is whats causing the “Scanning for plugins…” to crash. I still use the 1.60 driver but I moved the dll out of n’s directory.
I sent Flavio a bug report. We’ll see what happens. The PowerFX work great with Cubase VST which came with the card.
TG
PS I’m still on V3.3.