New Driver version problems

[WillyNanita]

Hello.

I just downloaded the new driver "Delta_V32_5.10.00.5069v2" for my Delta 2496 (PCI) only to find out that the control panel still says version 5.10.0.5065 and that the problem listed as fixed was not fixed at all: * Fixed Delta Control Panel not retaining buffer size after system restart under Vista or XP. Every time I restart the PC the buffer size is reset to 256 samples.

I'm using XP pro SP3.

Willy.
-------------------------------------------------------------
Windows XP Pro SP3 • PIV 3.4GHz HT • Ram: 2GB
M-Audio Delta 2496 • M-Audio Axiom 61 Controller

[thomasabarnes]

I have a Delta 1010LT. I'm running Vista 32Bit, and control panel still says version 5.10.0.5065 (after installing the Delta_V32_5.10.00.5069v2 for Vista 32Bit), but control panel does retain the buffer size after restart. It was a problem with the version Delta_V32_5.10.00.5065 driver, but now it's fixed in Vista for me.

Your problem may be a XP specific issue. I do wish the control panel showed the correct driver version as 5.10.00.5069v2 and not 5.10.0.5065. I just wanted to share my experience here. I hope you don't mind, Willy?

[WillyNanita]

Of course not... It must be XP specific because it is the same driver for XP and Vista. I hope they don't take too long to fix it, I don't want to uninstall and install and uninstall just to see if the driver is working fine.

Willy.

[Kleine2]

Same problem here!

[mjmelland]

Same issue with my D44 driver update... stil indicates and is using the old driver files after install. Using XP SP3...

[shAmii]

So, is everyone experiencing both issues - the buffer size resetting itself and the driver version being displayed?

We'll set up a test Monday in our Verifications Dept. to see if we can duplicate the issue and log it, if necessary.

[Kleine2]

Yes! Same issue here, the driver is reseting the buffer size

[rfi]

Same issues here, and also an additional issue: Emphasis option in "hardware" tab does not work, resets to "not indicated" when I exit out of the panel.

[shAmii]

OK, we were able to reproduce the issues where the 5.10.00.5069v2 displays the older version, 5065, on the About Tab and resets the buffers to 256. It has been escalated to our engineers.

[WillyNanita]

Thank you.

[Hippo]

Might be an idea to take these non finished drivers down until a solution is found, here on vista 32 I can tell no difference between these and the old drivers, buffer size is lost on reboot and no change in Device panel (Even the release number displayed is unchanged and the driver shows the same number in systems properties)

In short has anything changed at all?

Hippo

[WillyNanita]

Hi! I just confirmed with tech support that this is a known issue and they're working to update it as quickly as possible.


Willy.

[Peakdesign]

Just installed the latest 5069v2 driver on XP Pro SP2 (started as Media Center Edition) with a Delta 1010LT card to test. AMD X2 4800+, 4GB RAM. I had been using a driver version from two years ago, it's what gave me the best results, I forget the version number now.

I was pushing the latency playing the Thonex test file, ASIO with a 64 sample buffer, and playing notes on a USB connected keyboard into a VSTi. Bam, blue screen. This machine has been running 24x7 for two years with never never a Blue Screen, so i wasn't at all prepared to take notes. Sorry, but it was in DeltSomething.sys as I recall, and I didn't write down the fault number.

End of the line on this driver as far as I'm concerned. I'm not willing to do any further testing on this version. I'll post if I find anything in the rubble tomorrow.

Since this driver is the only one that even installs with SP3, it would be wise to continue to discourage people from "upgrading" to SP3 on their DAW if they have a Delta card, until all the issues are fully worked out.

[rfi]

Since this driver is the only one that even installs with SP3, it would be wise to continue to discourage people from "upgrading" to SP3 on their DAW if they have a Delta card, until all the issues are fully worked out.

Well, I was using the old driver (the one with the old interface) on SP3, but I had it installed prior to installing SP3. Worked great. If the installer for the old driver is bombing out in SP3 I assume you can run it in "compatibility mode" and it should fool the installer.

I too will be downgrading to the old driver. It's a shame because the old driver has issues with ASIO locking up for me (even in SP2) whereas the new one fixed that issue. The new one broke the emphasis option in SPDIF settings though and that feature is a must for my situation so I'll be using the old one and putting up with the ASIO issue.

[noisebeam]

I installed Delta_V32_5.10.00.5069v2.exe last night on a WinXP Pro SP3 system.

I too noted that the control panel shows ...5065.

However the main problem I had is that I could not longer change the sample rate when using Cubase VST 5.0. I could always do this with previous version Delta_WDM_5.10.00.5057v3.exe. Instead with this new version the sample rate was locked in Cubase and in the Delta Control panel at 44.1kHz

Al

[WillyNanita]

When is this going to be fixed?

Willy.

[cvor]

I'm having issues too, but not with the buffer size. I'm having issues with the sample rate. It doesn't stay where I put it.
Also, I use Ableton live and it reported slightly higher latency using the new drivers using the same sample rate and buffer size as the last driver.

[Kleine2]

Hope they will fix soon!

[shAmii]

We've reposted the 5069v3 (http://www.m-audio.com/index.php?do=support.drivers&f=930) driver with the correct updates:

It now displays the correct version.

It does not have the issue where it resets the buffer size.

The variable signal options are back!

It should have the correct emphasis setting for s/pdif now too.

[cvor]

Still having issue with XP SP3 driver. Sample Rate changes from where I leave it set and I get .20 ms additional overall latency reported in Ableton. I'm back to the SP2 driver.

[noisebeam]

I just installed the new version (5069v3) for Delta66 and I see some of the changes (can change input sensitivity, shows 5069 on about panel)

However in Cubase VST 5.2 I still can no longer change the sample rate in either Cubase audio control panel or m-audio panel - it starts locked at 44.1kHz no matter the previous nor song settings.

I rolled back again to 5057v3 and both Cubase and the M-Audio panjel allow me to change sample rate, with a drop down menu in Cubase and the any of the radio button options in m-audio panel.

Quad core duo extreme & winXP SP3, 4GB mem

Al

[Peakdesign]

When I say I wish I had been better prepared for the Blue Screen with 69v2, it sounds patently absurd, but it's true. After uninstalling 69v2 following the crash, things are not yet back to normal with 57v3. Some projects that were fine are now oddly routed in the mixer panel and will not play, I'm not sure yet why, and Cubase locks up when I try to change the outputs and inputs to fix it. It's as if 69v2 had left config data somewhere that 57v3 cannot handle.

I'm stuck now, because neither is OK, 69v3 obviously still has that blue screen just waiting to happen and e.g. mess up my disks, so I'm afraid of trying 69 again. Hope y'all find & fix it soon! All I can say is that it happened when I was "pushing" things at a buffer size of 64.

So where can I look for settings data to clear out or modify and try to get back to the way 57v3 ran before? There was a MFC Delta Uninstaller App from 2001. Might that help?

[Peakdesign]

I installed 069v3, and the hits just keep on coming. Now the old projects still won't play, the options at least can be changed without locking up, but the routing is all messed up with double input and outputs, like ASIO Delta and another ASIO name referring to the same ports. Very strange. Tried that old Uninstaller with (as might be expected) no visible effect.

Will have to try wiping all trace of 69v3 and reinstall 057V3, hope it works.

Kids, don't do this at home. If you have a working XP SP2 setup, don't mess with it, leave it be.

[My main PC is an AMD 64 x2 4800 with XP Pro Sp2 and 4 Gb RAM].

[lespaulman35]

I'm still thinking about trying it with my Delta 1010lt and AP192. Has anyone not had a problem with this version?

[ChrisByrd]

Just tried the updated 5069v3 and have not found any issues yet (I was getting problems with the previous 5069v3). I'm using Cubase 4 and Sonar 7 on XP SP3, and both allow me to change the sample rate (which is updated in the M-Audio Panel). Buffer size is now saved between PC restarts and I can change input sensitivity. I tried a few old projects and these seemed OK as well.

I've only been using it for about an hour though, so will report back if I hit any problems

Chris

[Hippo]

Just a note to say v3 is working OK here on this vista machine.

Hippo.

[cvor]

I'm still thinking about trying it with my Delta 1010lt and AP192. Has anyone not had a problem with this version?

Yup. I have the 1010LT --as stated, the sample rate will not stay where I put it and Ableton Live reports almost .20 MS increase in latency. I am on Windows XP SP 3. I am now using the SP2 driver.

[Bob Olhsson]

The problem of switching from internal to SPDIF in Pro Tools M-Powered has returned with this latest update. The first XPsp3 version no longer had the problem.

M-Audio Audiophile 192 (driver v.32_5.10.00.5065)

[BlackBurst]

Does anybody know if 5.10.00.5057v3 works with Vista 32bit?

I assume it does, but I'd like to be sure before I mess around too much.

[tsylvester]

I've been having sample rate issues between Acid, Vegas, and using rewire devices like bfd2 and sampletank with the new driver in xp. Everything is set 44.1khz, and then all of a sudden a program won't open and say something about unsupported sample rates and sure enough I'll open the v5065 (showing anyway) driver and it'll be on 48khz? Also, like the above posts, my buffer size will automatically revert to 256 samples. Now I'm getting issues in Protools M-Powered 7.1 saying "dae error -6006 was encountered.." And in the digidesign faq/troubleshooting guide is describes firewire/driver specific issues. I've been using 2 sync'd 1010lt's for about a year so it's not a firewire issue, so I'm guessing it's a driver issue...?

Please let us know when this is resolved!

[PhoenixGTR]

Just tried the updated 5069v3 and have not found any issues yet (I was getting problems with the previous 5069v3). I'm using Cubase 4 and Sonar 7 on XP SP3, and both allow me to change the sample rate (which is updated in the M-Audio Panel). Buffer size is now saved between PC restarts and I can change input sensitivity. I tried a few old projects and these seemed OK as well.

I've only been using it for about an hour though, so will report back if I hit any problems

Chris

Unfortunately it doesn't retain the sample rate between restarts on my system, and considering some of the other issues on this thread, I think I'll wait.
Mindful of Peakdesign's woes, and also having run into other issues while experimenting with driver versions, I restored from a disk image to get back to the way things were.
Please, M-Audio folks, keep working on these drivers...

[IronChicken]

Trying to delete duplicate post - but it won't let me, so you get this.

[IronChicken]

Hi - I too have 2 1010LT's synced using PT M-P 7.4 - Have you gotten anywhere with your 6006 error with the latest drivers? I even upgraded to XP SP3 thinking that would help since they were listed under SP3 on the driver page, but no luck. Uninstalled/Reinstalled, tried deleting all pref files, etc. - still no luck. What a load of garbage - they don't even work with their own company's product?? I don't get it. And of course here I am the fool because everything's been working perfectly fine with SP2 and the old (VERY OLD) drivers. But then hey, I guess curiosity killed the cat eh?

Pfffft. Ridiculous. My projects better not have gotten wrecked! Next time I'll know to spend an hour or so digging around reading up on stuff before I actually trust a software company to know what their doing I guess. Wow. Just wow. Sorry about the rant - as you can tell I'm a bit pissed about this situation. It's going to cost me money and I reeeeally don't like that. (And of course my ranting is not directed at you but the people who are responsible for this failure) :( By disabling one of the cards in Windows device manager, Pro Tools loads up just fine, so it's definately a dual card thing. UGH. I've now tried about every conceivable config combination possible and still no go.

HW:
(2) Delta 1010LT's
Core2 Duo 3Ghz
Intel DP35DP Mobo
4gb 1066 RAM

I understand that 2 (or more) 1010's aren't "officially" supported, but when many people have no problems with 2 working with PT MP, at least with the old drivers, myself included, and with no "official" explanation as to WHY they aren't supported (my theory is that it's simply to get you to buy something more expensive) I just don't understand this entire problem. These are in no way NEW products, and have been around way long enough that they should be having no issues at all, but it seems that someone felt the need to just completely disable the capability altogether with these drivers, which is really a shame, since now I'm probably just going to end up selling these off and not buy another M-Audio product (and seriously thinking of ditching PT altogether as well now with these ridiculous snively problems.) If I had the capability without support for it before, I should have the capability without support for it now, plain and simple, IMO. People have a want/need for more inputs, this is their product that doesn't "support" it, the cards have the capability to work with multiple ones alongside each other, and seem to work fine in COMPETING products, but not their own. Yikes.

[votdDale]

I'm having a few issues with the S/PDIF output using 5069v3 drivers for my Delta 66. Using the earlier drivers I can set the input of the s/pdif to be the monitor mixer and get digital output; when I try this on the new drivers I get no sound even though I can see the monitor bars rising and falling; the s/pdif does work however for non-audio dts when watching DVDs.

I'm running the digital output via coax into my Creative Labs Inspire 5.1 Digital 5500; as I said it works fine with the 5057v3 and 5052v3 drivers, I'll keep the older ones for now as I don't have any problems with them, just the lack of the latest snazzy interface.

[robero]

Hey there! First, here's my setup: Q9300, GA-EX38-DS4, 5 harddrives, WIN XP Sp3 tuned to DAW work. Everything non-audio, including MB's audiocircuit and CPU power and other energy controllers are disabled, .
I built my system in May, but I can't recall which version of drivers I installed then with my 1010LT, but no problems whatsoever.

A week a ago I tried to install the new 5069v3 drivers; BSOD during install, most likely with the last sys-file in the installer. Then no hope of things working. After several tries of installing the 5069v2 and finally v3 drivers again, I upped the CPU core-voltage a bit which helped the the computer not to crash (I mean system restart, no time even for BSOD) everytime I opened a project with only a few plugins and ASIO buffer size set to 64.

When I had the system stable again, I got these screeching and zippery sounding noises, reported by others here as well, no matter of the soft, just playing guitar direct was enough. After I set the buffer size to 256 they disappeared.

I did a complete registry cleansing, removed the DeltaIITray.exe, and installed the 5057v3 drivers, I'm not sure if they should be Sp3 compatible, but they installed just fine, and everything was OK again. No BSODs, ASIO buffers set to 64 and everything is working like they should do. So definetly there is an issue with the new drivers. Hope you guys at M-Audio will solve it...

[Stone21]

Just wanted to say that since I've installed the new drivers, Adobe Audition will freeze after previewing and applying an effect on a wave.

I will try the old drivers that came with my delta 1010lt and test it again.

[mellodge]

The only bug I've found, is the faders on the output wont save when ever I change something in cubase such as assigning new inputs.

[cvor]

Here's my post from July
Still having issue with XP SP3 driver. Sample Rate changes from where I leave it set and I get .20 ms additional overall latency reported in Ableton. I'm back to the SP2 driver.
Any update on this?

[JA]

Here's my post from July

Any update on this?

I just tested the 5057 and then the 5069v3 driver and did not experience these problems. I can manually set the sample rate from Windows, restart and the sample rate is retained. If I change the sample rate in Ableton and exit the program, the sample rate from Ableton is retained, as well as upon another restart.

I compared the latency reported in Ableton with both drivers at 44.1 & 96k sample rates with buffer sizes of 256 and 512 samples, and there was only a difference of .2ms with the new driver.

Are you sure you're using the latest v3 version of the driver? There were 2 releases of the 5069 within days of each other. I would suggest uninstalling the Delta drivers, then download and install the 5069v3 driver (http://www.m-audio.com/index.php?do=support.drivers&f=930).

[cvor]

Ja

I just tried again and get the same results. I leave it at 48000 and reboot and it's back at 44100.
Ableton goes from 3.96 ms to 4.15ms latency. I downloaded the link you gave. I'm going back to the SP2 version. Let me know if I should try something else.

[cvor]

So any ideas on why this would be happening?

[JA]

I'm not sure why it's happening; we can't reproduce this behavior. Perhaps there is a problem with your Delta card's EEPROM and there is an issue with the new firmware. Maybe another program or service is interfering and changing the sample rate. Try disabling Windows sounds. You can also try disabling all Startup Items and non-Microsoft services from Start>Run>msconfig