Anyone using Delta 66 with Win2k?

  • Thread starter Thread starter KaBudokan
  • Start date Start date
K

KaBudokan

New member
I just did a clean install of Win2k and put in my new Delta 66 with the Omni I/O box. Unfortunately, things aren't going well so far. I had an unusually difficult installation on Win2k (don't ask), and now the OS is in fine, but the card is not happy at all.

It makes a lot of popping and clicking noises when I open and close app's, windows, etc. I thought that was all (which is bad enough), but then I noticed when I installed Acid and Vegas that I don't have access to any individual inputs - just the "Delta 66" - no "H/W 1,2" or SPDIF in/out, etc. In addition to that, I can't access any 24 bit recording.

I originally thought it might be a hardware issue, but now I am thinking it is a problem with the beta drivers from Midiman.

Anyone have the Delta 66 running smoothly on Win2k?

My hardware set up is:

AMD K6-3+ @ 550mhz
Epox MVP3GM (9/19/00 BIOS)
256 MB pc133
Western Dig 27gb caviar
IBM 30 gb deskstar
Initio SCSI controller
Asus V3400tv TNT video card
Intel 2100 dsl modem

I thought that maybe my motherboard (VIA MVP3) chipset was causing problems, but like I said, I am thinking it is drivers.

Thanks for any help. (I'm going to call tech support tomorrow, but figured I'd give you detectives a crack at it. :) )
 
I have a Delta44 and Win2k.
People say that it works fine for them, but I'll be damned if I can get the thing to work right. I have 3 seperate PC's I have used it on. An Intel BX with a P700, a VIA set with a P733, and a Compaq Deskpro EN733. All with Win2k and It won't work right on any of them. It will record, but as you said, it gives me NO multiple inputs, and I need them to really do anything.
Oh, BTW...I'm a Network analyst and work for a Fortune 25 corporation in NT network support. So knowing about PC config is NOT the answer here!!!
Those drivers MUST suck.
I'd LOVE to hear what tech support tells YOU.
 
I'm using the Delta 1010 with W2K. I had some problems initially, but they were not related to the beta drivers. I have access to multiple I/O in both Cubase and Nuendo. I'm not sure what the problem would be, calling tech support is a good plan though.
 
The problems were with some of the plugin's crashing when launching either Cubase or Nuendo (the solution was just a reinstall, I don't know the exact cause - some plugin's still do crash on occasion). I did have one occurence of audio glitching, but after upgrading to 256MB I haven't had any problems. The problems you are describing are quite different. Maybe it is specific to Vegas and Acid and nothing to do with the beta W2K drivers? Sonic Foundry may know of a solution, maybe check their site and email them.
 
Well, if I can get through to tech support, I'll ask them. :mad:

I got an email from someone at the RAP ng, where I posted the same thing. He had the EXACT same problems using the Delta 1010 - including the clicking and all of that stuff. Same with no specific inputs or 24 bit recording, which he said is because of the limited drivers also.

I'm going to try to get through to Midiman, but it looks like I am going back to Win98. :(
 
BTW - If that is how a driver issue, you would think that Midiman would at least MENTION it on their site. Maybe not, since Emeric has it going with other programs. If I can't get through to tech support, I'm just going to reformat and install 98.
 
Maybe I'll give my copy of Cubase another shot. I got it and tried it a while ago, but I just hate it. Come to think of it, though, it does the same crap with Cool Edit Pro and N-Track, so I don't think it's the tracking software.
-H2H
 
Just got off the phone with tech support.

The problem, apparantly is with the Windows 2000 wdm setup. They are waiting for code from MS to work around. Acid and Vegas both use those drivers. CuBase and some other programs apparantly use the ASIO drivers, and will work ok.

He was going to help me through reinstalling the drivers for Win2k, to get rid of the popping and clicking. Because of the WDM issue though, I would only be able to record stereo in and out, AND also only record at 16 bit.

I could have stayed with my SB Live if that was an option.

So... I am just going to go ahead and go back to Windows 98.

Anyone try Windows 98 Lite? I am going to be using the computer mainly for recording, but it is my only computer, so I do need it for other things.
 
KaBudokan: I use 98lite, it's a great program. I bought it specifically for recording, and have been using it for over a year with no problems. I've only been using W2K for about a month. I may yet go back to 98lite, so I left the option open. Windows 98lite on one partition, W2K on another, and a full blown 98 on a third. Allows you to keep everything seperate, almost like having 3 computers. Check it out:

http://www.masterbooter.com
http://www.98lite.net
 
I'm just starting to try to use a similar setup. Win2k, Delta 66, Omni I/O, Cakewalk. I can only get Left Delta, Right Delta, or Stereo Delta for inputs. Also having a bit of trouble with the outputs. It sounds like I may want to try to use Win98 until the driver issue gets ironed out. I also want to use Gigasampler but I can't even install that in Win2k. Oh well, glad I found this post. It's been helpful. I don't have to keep spinning my wheels. Thanks.
 
same problem

I'm using the delta 66 on win 2K, and have had the exact same problem - pops, clicks, and missing inputs. Fortunately, I've been able to get my software (n-track) to work with the ASIO driver. Still - its pretty shitty - wierd skipping occurs whenever I engage or dissengage audio (play/record or stop). Its also hogging alot more cpu, and tends to skip whenever I move windows around, or change setting on the mixer. I'm using a p3-500 with plenty of RAM - these problems did not occur in win 98. But win 98's memory management and overall performance is so bad, it's also practicly unusable for DAR.


I've also been having realy bad latency problems with win 2K- making sound on sound recording impossible. I read somewhere that switching priority to background apps (under system control panel) fixes the latency problem. I haven't tested to see if this makes a difference yet. I'm not that confident that it will, because I've read elsewhere that this is a fundemental problem with the way win 2K handles audio, and hasn't been fixed yet.
 
You must log in or register to reply here.
Back
Top