|
Subject:New bug introduced in ACID Pro 4c & 4d
Posted by: billybk
Date:6/5/2003 8:04:35 AM
A convenient feature in previous versions (ACID Pro 4, 4a & 4b) was the ability to change and match the audio cards (Delta 66/ASIO in my case) buffer size to that of ACID, from the Advanced Audio Configuration tab. All you had to do was click the "Configure" button and my Delta software control panel would pop up and I could easily change the DMA buffer size. Once I closed the Delta control panel I would click "Refresh" and the new audio card setting would now be accurately updated & reflected in the Advanced Audio Configuration tab. Unfortunately, as of ACID 4c and ACID 4d this not not work reliably anymore and often results in a BSOD. Which I never got in ACID 4a or 4b. Which of course, now makes it a PITA to change buffer settings. Bummer! :( Billy Buck |
|
Subject:RE: New bug introduced in ACID Pro 4c & 4d
Reply by: L25
Date:6/5/2003 8:27:06 AM
You know I had a BSOD yesterday myself, and that is extemely rare, the kind where my computer just rebooted on its own, (not a lock-up), I am not sure, but I think it did follow an odd message about my sound card being not available, being used by another app. I went into the ACID audio prefs and my ASIO did not even show up (I have a delta1010). |
|
Subject:RE: New bug introduced in ACID Pro 4c & 4d
Reply by: Iacobus
Date:6/5/2003 12:28:22 PM
I'm using an Audiophile 2496 w/ latest pro betas from M-Audio. (The 029x12's.) Using ACID 4.0d. I can change and refresh buffer settings without a problem. If any of you updated your drivers, be sure to use the "Delta Uninstaller" executable that comes with the driver set before you install and update drivers. If you're using Windows XP, go to Start>Control Panel>System. Click on the Advanced tab, under "Startup and Recovery," click the Settings button. Under "System Failure," uncheck Automatically restart. This will prevent Windows from rebooting on you if there's a problem. HTH, Iacobus |
|
Subject:RE: New bug introduced in ACID Pro 4c & 4d
Reply by: billybk
Date:6/5/2003 1:52:16 PM
Are you using the Delta in ASIO mode? Are you sure the actual buffer size in the Delta control panel is changed? I will try to change it from ACID, in the "Advanced Audio Configuration" box, and ACID will intially update to reflect the changed Delta ASIO buffer size. But, if I open the Delta control panel externally from ACID, the buffer size is still the same as before I made the change. If you try to force the change from ACID or try to then play the project, you are likely to get a BSOD. Nothing has changed on my system in months. I am using the same Delta drivers (5.10.00.0114x2) for the last nine months. Works fine in ACID 4a,b (ASIO mode), Vegas 4c(ASIO mode), SF6e and SONAR 2.2 (WDM mode). The only time I have ever had a BSOD in the last year using XP Pro, has been since I upgraded to ACID 4 c/d this past week. Something has definitely changed since ACID 4b to start causing BSOD's. I can still use the same drivers in Vegas 4c, SF 6e and SONAR 2.2 with no problems. Go figure! Billy Buck |
|
Subject:RE: New bug introduced in ACID Pro 4c & 4d
Reply by: Iacobus
Date:6/5/2003 2:46:13 PM
I'm using the Delta with ASIO in ACID, yes. Positive about the change. I've tried it several times. The Panel, when I initiate it separately after changing the buffer in ACID, definitely reflects the change I made in ACID. Pick up the 029x12's anyway; they include the ACID 4.0 ASIO fix and just might help you out. (Be absolutely sure, as I've said. to use the Delta Uninstaller that comes with the drivers before installing new ones. I always restart my system after uninstalling old drivers and then point to the new ones when Windows starts up and detects the Delta.) HTH, Iacobus |
|
Subject:RE: New bug introduced in ACID Pro 4c & 4d
Reply by: billybk
Date:6/5/2003 3:18:49 PM
I tried the 029x12 drivers when they were first released last December. Although, intitial results were good, eventually I would get BSOD's in both SONAR and ACID Pro 4 when previewing loops from the Loop Explorer. Also, the playback and record meters in SF6 would exhibit erratic behavior as well. That was enough for me to go back to the tried and true ACID40 drivers, and then, all was well again. Why is it, if I go back to ACID Pro 4b, everything is fine. It just does not make any sense. Billy Buck |
|
Subject:RE: New bug introduced in ACID Pro 4c & 4d
Reply by: buckaroo
Date:6/5/2003 3:45:46 PM
I had same BSOD today out of the blue with Gina 24 - always been fine, but have just upgraded to 4.0d.............uh oh......... |
|
Subject:RE: New bug introduced in ACID Pro 4c & 4d
Reply by: pwppch
Date:6/5/2003 7:37:57 PM
How could you have the same BSOD that a user with a MAudio card with you using a Gina? Not possible. What were you doing when the BSOD occured? ACID cannot cause BSOD errors, only drivers can do that. Regardless, we have been unable to reproduce what Billy has seen. If you have details one what you were doing when you hit the BSOD, please, let us know. Peter |
|
Subject:RE: New bug introduced in ACID Pro 4c & 4d
Reply by: dkistner
Date:6/6/2003 5:34:30 AM
Peter, I've just come into this thread, and I can say that I, too, have been having bizarre behavior since installing Acid 4.0d last week. I just installed it and checked a few of my preferences settings but haven't done anything else in Acid because other things have required my attention. So I didn't even suspect installing Acid had anything to do with it. But I wonder now. I am running Windows XP Professional, with both an Echo Mia and a Soundblaster Live! Value card installed (Pentium IV). I have two hardware profiles, one just for recording and mixing work with the Mia, and the other a more general-use (where the SB Live is just fine). No BSOD, but my system has been mysteriously rebooting while I'm working in any app that sends midi (and maybe audio, too...I'll have to be more observant). When I check my Control Panel, often I'll show "No Audio Device" in Sound and Audio Devices Properties--in one or the other hardware profile, if I am not mistaken. I'll reinstall the drivers (it's almost always the Echo Mia, 6.08 driver), I'll see my audio device installed, but it will disappear again later. XP just issued a new update. I thought maybe it was something with the update that was causing this. Maybe it's some interaction between the update and Acid and the Echo drivers. It wasn't happening before I installed 4.0d, I know, but maybe that's just coincidence. I'll really be interested in hearing what comes of this. If you need any kind of specs from those of us having the problem, please tell us exactly what you need. Diane P.S. I'm confusing myself now. Was it 4.0c or 4.0d? Where were we...at 4.0b, then c came out with the first announcement? Then that's what I installed. My About says 4.0c (Build 390). I'll install 4.0d and see if I get any difference. |
|
Subject:RE: New bug introduced in ACID Pro 4c & 4d
Reply by: buckaroo
Date:6/6/2003 6:39:15 AM
yeah obviously i didnt get the same error with a Maudio card on my Gina!! |
|
Subject:What's a BSOD?
Reply by: gunhed
Date:6/6/2003 9:38:00 AM
I can't say I'm familar with the acronym BSOD - what does it stand for, and what does one look like when it happens? |
|
Subject:RE: What's a BSOD?
Reply by: ATP
Date:6/6/2003 9:57:20 AM
it stands for Blue Screen Of Death, a well known fenomenon amongst Win9x users, i'm sure you (like all of us) had your share of those. :) |
|
Subject:RE: What's a BSOD?
Reply by: Iacobus
Date:6/6/2003 12:52:06 PM
billybk: Because there might be something in the drivers that's causing the problem that ACID "sees" in version 4.0b or c. Remember the Delta ASIO bug in the initial release of ACID Pro 4.0? It only happened with ACID Pro 4.0. And that was M-Audio's fault (which they acknowledged and fixed), not SoFo's. Regardless, go and try the 029x12's again, just to see if the new problem was fixed. What would be really helpful: What does the BSOD say? Write it down. Diane: See my first response in this thread to possibly prevent XP rebooting on you in the middle of something. It indeed went from b to c and now d. 4.0d only fixed a problem with rendering mono files within a 5.1 surround project. Otherwise, I believe it was the same as 4.0c. Everyone: As Peter said, a BSOD is caused by a driver, not an app. It could be anything; it could be a video driver causing the sudden error, for instance. I personally can't help anyone until they give more details as to what the BSOD says and what's in their system hardware-wise. Otherwise, the only thing I can suggest is to try other drivers. Try also turning video acceleration off completely. HTH, Iacobus |
|
Subject:RE: What's a BSOD?
Reply by: gunhed
Date:6/6/2003 2:51:47 PM
Ah, yes, I'm quite familiar with a blue screen error! I just didn't catch the acronym! Thank you for enlightening me! |
|
Subject:RE: What's a BSOD?
Reply by: dkistner
Date:6/7/2003 6:35:50 AM
Got it, Iacobus! Thanks! I missed that the first read-through. I'm starting to wonder if the "No Audio Device" thing I get under the Volume tab in my Control Panel Sound Properties window is not due to the fact that the Echo console takes over volume adjustment from Windows and the new 6.80 driver is just written to put the wrong identifier in there. It didn't used to do that, but I haven't really tweaked in that window since installing the new driver. More testing today, with the automatic restart thing unchecked. And I'll be installing 4.0d. We've lost broadband, so downloading that thing with dial-up took ALL DAY yesterday! :) Diane |
|
Subject:RE: Back to ACID4.0b and all is well again
Reply by: billybk
Date:6/7/2003 7:36:31 AM
Thankfully, I always archive previous updates/patches for all my software on CDROM for instances like this. Yes, ACID 4b works like before and as I described it should it my intitial post. Yes, the "Advanced Audio Configuration" dialog box works flawlessly, again with my ACID40_FIX drivers. The only thing I changed was the ACID Pro version. BTW, both ACID 4 & Vegas 4 use the exact same "Advanced Audio Configuration" utility, which makes it very convenient to change latency settings in the middle of a project, easily and seamlessly. For me, if that does not work right or reliably, (and I change latencies a lot, depending on the task at hand) then the rest of it does not matter. I can do without the BSOD's. I don't really use rewire much anyway, and if and when I do want to venture into rewire land, I can always use SONAR 2.2 for that with it's excellent softsynth & midi capabilities and keep using my ACID Pro for it's superb loop arranging tools. So I'm not really losing anything, am I? Billy Buck |