Subject:Win2K, KMixers, and Time-Out's... Oh My!

Posted by: nlamartina

Date:3/23/2002 1:44:56 AM

Okay, here's a puzzle for you... Just spent the last couple days building a DAW from scratch. Everything put together and operating flawlessly. I was just starting to pat myself on the back when I opened Acid, started playing back a project and got the dreaded message, "Unable to mix audio. Operation timed out". If I were new or inexperienced, this wouldn't surprise me. However, since I am neither, this is frustrating. I've gone all through the forums and found out very little, other than the fact that the KMixer in Win2K is buggy with WDM drivers. I am not currently recording 24 bit though, so I don't see this as a problem yet.

Here are the specs relevant to operation:

- Win2K (SP2) and Win98SE dual-boot (clean install)
- DirectX 8.1
- Sound Blaster Live! Platinum (WDM driver)
- 20 gig Maxtor system hard disk (FAT32; 7200 RPM, UDMA-100)
- 30 gig Maxtor capture disk (NTFS; 7200 RPM, UDMA-66)
- 60 gig Maxtor storage disk (NTFS; 5400 RPM, UDMA-66)
- Acid Pro, Vegas Video, and Sound Forge installed
- Windows Media 7, Quicktime 5, and DivX 5 installed
- Netgear FA311 ethernet card
- 3D Prophet II GTS 32 MB
- 192 MB SDRAM
- FIC SD11 motherboard
- Generic TI-based 1394 bus adapter

Concerning environment:
- Win2K is completely updated (sans Internet Explorer)
- NO OTHER SOFTWARE is installed beside the SoFo apps and WinZip
- All SoFo apps are completely updated
- Hard disks were all zeroed out before being formatted
- BIOS updated to latest revision
- All VIA chipset drivers are current
- UDMA enabled on all drives
- Sound Blaster drivers are latest available
- Video card drivers are current
- All source files are local; no network activity
- System resources are clean and available; nothing unusual running in background
- All software was installed in correct order
- CPU usage is as low as 1% when problem occurs

It appears the error occurs upon the first press of the play button, and then somewhat at random afterwards. Project complexity appears to be a non-issue. Before someone suggests that I upgrade the system or start bouncing tracks, save your breath. I was running this stuff on an AMD K6-450 with 128 MB of RAM in Win98SE with the same sound board, and it ran flawlessly. However, I was using MME drivers. Is this the problem? Do I need to revert to MME? If so, where can I find the drivers for Win2K? Do they even exist? Will the eventual fix for the KMixer correct the problem I'm having? Something else? Any help will be GREATLY appreciated. I'd really like to get this system off it's behind.

Regards,
Nick LaMartina

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: Iacobus

Date:3/23/2002 7:49:16 PM

It certainly sounds like everything in the system is up to snuff. If anything, did you make sure you contacted SF support?

Sorry I can't be of more help as I don't use W2K and don't know of the issues associated with the OS. (I'm using XP which, save for a little quirkiness in my Audiophile 2496's control panel/mixer, works great with ACID Pro and Sound Forge. Still wish they'd update the drivers though.)

Iacobus

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: MacMoney

Date:3/24/2002 7:46:46 AM

Same here.
Im running Win2k with no problems with MOTU hardware.I want to go to XP pro but no need to fix what's not broken. Please feel free to send me an e-mail I could put you in touch with the guy who built all of my systems.

Good luck
George Ware

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: kleb

Date:7/14/2002 5:11:54 PM

Same here...
I've got the same problem as nlamartina, migrating from Win98 Second Edition to Win2k Pro. This is the error:

"An error occurred while starting playback.
Unable to mix audio. The operation timed out."

What's up with that?

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: Vocalpoint

Date:7/15/2002 7:01:50 AM

Nick,

Been running Acid, Vegas and Forge for over 18 months on Windows 2K with M-Audio Delta 66 and Omni Studio - I have never ever seen this message. I believe there is a hardware or driver conflict on your box somewhere...

And I don't mean to be rude, but why the Soundblaster? You have a hell of a fine rig there, you sound like a guy who really enjoys recording and working with these apps and you have laid out a fairly sizeable load of cash on your setup only to grace it with a 125.00 soundcard? Again - I don't want this to sound like an invite to argue - I just want to know more about why you are using this card and not something a little more "pro" (bad word - i know but it's all I could think of at this early hour. :)

Sorry I can't be of more help on the error but I have just never seen this message in the longtime that I have been using SF apps. And I have used Win2K from the beginning so I do not believe the KMixer can be totally to blame...

As a side note - I have never heard of your motherboard and VIA chipsets have been known to cause all sorts of annoying problems in the past year or 2 (I know there are fixes availble but you never specified if one had been applied)...you may want to look at something there...

Cuzin B

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: ramallo

Date:7/15/2002 1:24:06 PM

Hello,

Isn't a sound card problem (I tried with a lot with same results), is a Sonic Foundry audio engine problem (I tried with win2k and XP), I use diferent editor and only have this problem with Vegas Video and Acid.

Bye

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: Vocalpoint

Date:7/15/2002 2:17:04 PM

ramallo,

So are you saying you took your single machine, popped in a bunch of different sound cards and the error continued to appear or did the error appear over your use of a bunch of different boxes with completely different configs/OS/hardware?

Update when you can,

Cuzin B

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: ramallo

Date:7/15/2002 5:36:02 PM

Hello CuzinB,

I'm not the only one with this problem, if you search the SF forums (Vegas for example), you can see the answer at your question, the same problem with diferents machines. Ok, is simple, read.

For your records, my machine is a Dell Inspirion 8200, and only have problems with Vegas and Acid, have you a solution?, have you any idea?

My experience with differents sound cards is for isolate the problem (I work for resolve my problems), the audio hardware ins't the problem.

I tried all possible hardware combination, but I don't like change one of the very best and powerfull laptops avaliable in the market today, that work well with Nuendo and Cooledit.

I tolk with Dell, conclusion:

The Sonic Foundry audio engine fails, almost with Dell Inspirion machines, and nlamartina machine, and others (Please read hte forums before write any smart reply)

I repeat my question: have you any idea about this problem?, any solution?.

Bye

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: Vocalpoint

Date:7/15/2002 6:34:13 PM

ramallo,

Thanks for the update. I will see what else I can find out. Sonic Foundry must know in their program code what conditions must be met before this message will appear. Maybe someone from SF can chime in here?

Cuzin B

Subject:MY SOLUTION (forgot to mention this months ago)

Reply by: nlamartina

Date:7/15/2002 6:46:49 PM

Whoah, I didn't expect to see this topic resurrected. To get everyone caught up, I fixed this problem a few days after posting the original message. I posted the follow-up in the Vegas forum but I guess I neglected to do so in here too.

Here's the deal: I started uninstalling Windows updates. Don't ask me why. Call it a hunch. I went one after another, until I found the naughty one... SP-2. I don't know why or how, but for whatever reason, SP-2 was causing the Acid/Vegas audio engine to fail again and again, regardless of what else I did. Since I've gotten rid of the service pack, everything has worked absolutely flawlessly. No crashes, no errors, no lost performance. To date, I've had Vegas crash on me three times. Acid has yet to do so.

So MD, if you have SP-2 installed on your Win2K boot, nuke it and see if the error goes away. That's my best guess for you.

Cuzin, as to your question about the Sblaster… First off, no offense taken. Truthfully, I've long wanted to get a pro card, like an Aardvark 24/96 or Q10. Before, it was simply a matter of not being economically feasible, but now, it's just that I haven't the need for it at all. I was recently put in charge of building and administering a brand new workstation at my college (dual Athlons, two Q10’s, a gig of RAM, etc), funded by a very large grant. We’re trying to get a recording studio started up, and since the faculty knew I’m very involved in both the music department and music technology, they thought I’d be the best person to get this project off its feet. I'll be practically sleeping with the thing in my bed for the next two years, so I won't need to buy anything for myself personally for a while. Any major recording projects will be covered with that machine. So personally, the only thing a pro card could offer me at this point would be 24-bit audio in my room and powered mic in's, which in all honesty would be really, really nice, but it's really not that crucial at this point. When I graduate in two years, you better believe I'll be dropping some cash on an Aardvark, but until then, I should be satisfied administrating this new beast. Cuz hey, someone’s gotta test its abilities. =) Additionally, I've been using a really sweet open-source WDM driver for the SBLive on my own system, known as the kX Project. It COMPLETELY blows away the standard driver, with quieter operation, buss and FX routing onboard, lower latency, and greater input control. There are even plans for making it multitrack capable. However that proceeds, it's enough of a middle ground for me right now. Thanks for your concern though. =)

Hope this helps everyone,
Nick LaMartina

Subject:RE: MY SOLUTION (forgot to mention this months ago)

Reply by: Vocalpoint

Date:7/15/2002 9:13:52 PM

Nick,

I am glad that everything worked out for you. Can't figure out why SP2 would be a problem. (SP2 is pretty much the first thing I put on my DAW after a reformat). Strange.

Cuzin B

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: kleb

Date:7/15/2002 10:37:33 PM

I have just installed the latest ACID PRO Version 3.0g (Build 365) and continue to get the error: "An error occurred while starting playback. Unable to mix audio. The operation timed out." I haven't removed SP2 yet... though it'll be my next attempt at a fix. I wish there were a better solution than removing SP2! SP2 is usually recommended, the network guys at my IT shop swear by it.

I'm using the M Audio DiO 2448 Digital I/O card. Maybe I need a newer driver for Win2k?

Sonic customer service said check the Options, Preferences, Audio, 'Audio device type' Change settings from Microsoft Sound Mapper to Windows Classic Wave Driver and set 'Default audio playback device' to DiO 2448. I tried this and still no improvement.

What about Playback buffering (seconds)? 0.35 is my default setting.

Surely someone at Sonic Foundry can shed some light on this!?

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: Vocalpoint

Date:7/16/2002 9:14:59 AM

kleblanc,

This has got to be something to do with drivers or something besides SP2. I have used the Delta (M-Audio) 66 for a long time with Acid, Forge and Vegas on Windows 2000 with SP2 and I have never ever seen this message. So it is possible to have everything running correctly.

And always make sure you select the Windows Classic Wave Driver whenever you are setting up a SF product.

This one is strange but as I have said - a SF rep should jump in here. SF must be able to look up this error in their source code and be able to piece together the conditions that cause this error to appear.

Cuzin B

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: kleb

Date:7/16/2002 1:09:51 PM

I checked with the M Audio web site, downloaded and installed the latest Win2k Pro drivers. I already had the correct DiO 2448 driver loaded. Still getting the error... I'm not sure about removing Service Pack 2 (SP2) because I did'nt create a reversible install.

Can someone at Sonic Foundry give any advice??

K LeBlanc

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: Iacobus

Date:7/16/2002 3:39:26 PM

Nick: I don't have W2K. :) I have Windows XP. The quirkiness I noted in my last post was actually not the Audiophile mixer's fault. It was mine. (Figures.)

For everyone else: Tracking down and finding out what's exactly causing the problem could be a myriad of causes. If someone like Cuzin B isn't having a problem and he has a similar setup, that should tell you something. It has to be your system, either your hardware and/or combination of software on that particular system. It's quite possible that something in your system just might be not working right like it should and ACID just might be picking up on it.

However, here are some things I can recommend (try a combination of them if one possible solution doesn't help and in no particular order):

-Uninstall and reinstall ACID. Get the latest build here. Install the latest build only. (It's actually a full version of ACID to begin with.) Do not update your existing install of ACID.

-Reinstall DirectX.

-Scandisk and defrag your system regularly.

-Format your system and reinstall W2K. (This is a last ditch effort, as this will require you set aside some time to reinstall everything.)

-Keep your installed applications to a minimum. Install only what you use. In the same vein, make sure nothing else is running in the background except ACID and any other audio app like Sound Forge if possible. Typically, utilties such as antivirus programs and software firewalls make themselves intrusive even when you think you've shut them down via the Systray. Use the good old three finger salute (CTRL+ALT+DELETE) to find and hunt down any resident programs that may be running.

-Keep your installed hardware to a minimum. The ideal setup would be video card, soundcard/audio interface (and any associated device such as mixers, MIDI keyboards, etc.) and modem or network card (for Internet access). Nothing else. No scanners, no printers, no cameras, no other doodads not associated with audio production.

-For the best possible experience, always install ACID on a "clean" system. By that I mean don't install ACID on a computer that has the OS and any software already pre-installed. You just might be asking for trouble. Typically, such systems come from vendors such as Dell and Gateway and stores such as Best Buy. Save yourself some trouble and pay extra to either have the computer built to your specs or D.I.Y.

-Get the latest drivers for your hardware—video card, soundcard, motherboard, everything.

-I've heard that motherboards with a VIA chipset aren't too friendly unless you get an update. Check with your motherboard manufacturer for possible BIOS updates as well. Chances are if your motherboard is less than 6 months old, there's an update available of some sort.

-Check to see if your installed hardware is sharing any IRQ's with another device in your system. Ideally, each device should have its own IRQ. Shared IRQ's are sometimes not a problem for other users though. Windows XP handles IRQ sharing more efficiently than previous versions of Windows (or so I've heard).

-Lastly, contact SF's tech support via email. Be patient for a response. Since this is practically the only free version of support directly from SF, I'm sure they get bombarded. If you need help right away, pay for the Annual Support Plan or call their 900 number. Users who have the pro-level products like ACID Pro or Vegas get 60 days of free support following product registration but it's a toll call.

HTH,
Iacobus

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: ramallo

Date:7/17/2002 9:36:18 AM

Hello,

Isn't a problem of the sound cards (I tried a lot), ins't a problem of any Service Pack (I have XP and have the problem), isn't a problem of configuration of windows (Acid and Vegas will be work with a standart system), isn't problem of fragmrntation (I have the better defragmenter and use it every day), is a problem of Sonic Foundry Audio Engine and certain configurations.

I have problems with Vegas and Acid, but don't have any problems (With the same hardware) with any Video or Audio editors from other brands (Like Cooledit, Nuendo, Windows Movie Maker, etc.).

I believe that SF, need give us an explanation, and resolve this bug (As fastest possible).

Regards

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: Iacobus

Date:7/17/2002 3:43:52 PM

Did you ever format your Dell laptop and just try it with Vegas and/or ACID (once XP is reinstalled, of course)? Even better, has the system ever been formatted since you received it?

Iacobus

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: kleb

Date:7/17/2002 6:36:03 PM

Guys,
I've got a very clean Win2k Pro system. I could likely use some additional maintenance under the hood. I'm a developer and network technician and understand that with a little effort this problem can, I am positive, be resolved! However, each time I try to re-create this particular error on Win98 SE (which is fairly loaded with applications) I get error-free results. I never had to really tweak Acid or Vegas much at all...

Here's what I've tried and the results. I upgraded DirectX 8.0 (4.08.00.0400) to DirectX 8.1 (4.08.01.0901), which is the latest on MS site. Results, only minor improvement on playback. The error still occurs after about an average of 10-30 seconds.

Next, I tried adjusting the Audio Preferences. Playback Buffering and the check box next to 'Do not pre-roll buffers before starting playback'. The manual states that the Playback Buffering value be kept as low as possible and increased when playback gapping starts. As I increased the value in increments of .05 I noticed an improvement each time in playback time before crashing with the error until I maxed the setting at 1.00. Then, by checking the box preventing pre-roll buffers before playback, I was able to get almost 2 to 3 minutes into the song before the playback error and ensuing stoppage. According to the manual, 'some devices do not behave properly if this check box is cleared. If your audio stutters when you start playback, try selecting this option.'

So, by now... I'm pretty frustrated. I will call tech support on this, not sure about the cost. I'll listen to anyone's advice, oh and continue to use Win98 SE.

K Leblanc

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: pwppch

Date:7/18/2002 12:04:11 AM

This error is caused by the 'mixing' engine timing out.

Increasing buffer can make it worse, as the time out is typically caused by something "preventing" reads of the audio data or mixes of the audio data. That is, some other process is stealing time from the mix engine.

It is very system dependent. Memory load, harddive speed, number of tracks, other I/O devices, etc,etc.

I have had people solve this problem by merely moving their audio card to another slot in the machine. Sometimes only a clean install of Windows and ACID will solve the problem.

Believe me, if there something that we knew would fix it for everybody, we would have done so already. We are working on a solution to meet this goal.

Peter

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: Vocalpoint

Date:7/18/2002 7:31:39 AM

All,

SonicPCH - thanks for stopping by and giving us an update. Again - I have what I consider to be a pretty stock system:

Intel PIII 1GHZ CPU
ASUS TUSL-C Motherboard
512 MB Kingston RAM
Matrox G450
Delta 66 with Omni Studio
Windows 2000 with SP2 and all the latest updates
Latest version of Acid, Vegas and Forge

And everything works great - have never seen this message and never had a project stop, snap, crackle or pop. Never made any special arrangements to unseat cards or mess with IRQS - I do however disable ACPI in my audio install (I have a dual boot with XP) to ensure that the Delta audio card gets it's own IRQ and does not conflict with anything else in the system. That's the only "on purpose" tweak I have done.

I do hope that SF can pinpoint the exact issue so you guys can get back to making some noise.

Cheers,

Cuzin B

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: kleb

Date:7/18/2002 10:45:01 AM

Thanks all,

I've made some progress on system tweaking. Here's my setup, maybe this will shed some light on the problem.

AMD 751 Processor
ASUS K7M Slot A Motherboard, VIA KX133 Chipset
256 MB RAM
Western Digital WD153BA (for OS/APPS)
IBM DNES-309170W SCSI (for media record & playback)
Adaptec AHA-2940U2W - Ultra2 SCSI (PCI Interface)
MS Windows 2000 Profesional, SP2 Build 2195 (dual boot w/ Windows 98 SE)
M-Audio DiO 2448 (plan to integrate MOTU's or M-Audio TDIF Interface soon)
Latest Acid, Vegas and Forge XP Studio

I downloaded and installed the latest VIA Service Pack 4.40V. Noticed marked improvements. I'm investigating an article found at Tom's Hardware guide www.tomshardware.com/mainboard/00q2/000508/index.html. The article is concerned with the problems that Windows2000 has with the CPU-to-AGP bridge of the VIA Apollo KX133. Something about 'you have got to make Windows2000 believe that the system is equipped with a MVP3 CPU-to-AGP-bridge, so that it installs and initializes VIA's AGP-driver 'viaagp.sys'.' I'm curious if this has something to do with the PCI bus?

Does anyone have experience in upgrading the VIA chipset?

Cuzin B, you mentioned IRQ conflicts and sharing. What's the best way set the audio cards IRQ so that it does not conflict with anything else in the system? I notice mine is set to IRQ 9 along with a host of others including my Ultra2 SCSI device and PCI Adapter, etc.

Thanks,

K Leblanc

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: Vocalpoint

Date:7/18/2002 2:00:55 PM

kleblanc,

Hmmm...interesting setup there - one thing I know that without the VIA fix, you had a recipe for disaster there. Did you notice any bad popping and clicking prior to the fix?

IRQ Sharing Tips - this is critical especially for the Delta/M-Audio cards. This topic is a touchy one since it works for some but not for others. I do not claim to know every little detail about it but I have benefitted greatly from this info. Like I mentioned - It is the ONLY left field specialist tweak that I perform on my DAW to ensure no hardware issues. This info applies to Windows 2000 only. Can't confirm if XP behaves the same way since I don't use XP for audio (yet) So here we go with a bit of history first:

During an initial WIN2K install on todays recent machines (Say in the last 2.5 years or so), if your system BIOS is set to "Plug and Play OS", Windows 2000 will attempt to detect if your box has the right combo of parts to install the ACPI (Advanced Configuration and Power Interface). This gives you power management like shutting down your PC automatically and a few other things...if you machine meets the requirements, Win2K will use a particular setup routine to brand your machine type as ACPI (Check it out in Device Manager under Computer) If it says ACPI, then you need to make some changes to get it to read "Standard Computer". The gross end result of this ACPI install is that Win2K piles a whole mess of IRQ action on IRQ 9 -and if your audio card is in amongt this list - you are destined for a world of hurt when recording.

Pro audio cards - the Delta/M-Audios in particular need to have their own IRQ with no conflict so they are not interrupted by any other devices on board when doing audio work. The down side of this is that if your machine is already noted as an ACPI in Device Manager, a reinstall is the only way to fix this. (some folks have other methods they claim will work - don't buy it.) A reinstall is it.

The tweaks are simple but not very obvious:

1. Set your BIOS to read "non-plug and play" before you install anything. This is critical.
2. Very very early in the Win2K setup (right after the "inspecting your computer" part flashes by...when you see the blue install screen for the first time, hit F6. Then hit F5. In a few seconds, Win 2K setup will allow you to choose your computer config. Choose Standard Computer and continue with your setup as normal.

Windows will take care of the rest - when setup is done and your are up and running, confirm in Device Manager that your Computer Type is in fact "Standard Computer" and check your IRQ's to see where your audio card ended up. Mine always takes IRQ 5 for itself.

My standard disclaimer - This may or may not have anything to do with this timout error condition. That being said - for me - this tweak provided a much better audio experience on the whole since my audio card can do it's thing uninterrupted.

Let me know how it goes.

Cheers,

Cuzin B

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: kleb

Date:7/18/2002 10:39:04 PM

CuzinB,

No snaps, crackles, or pops of any kind experienced here. The audio playback on my Win2k Pro system has been fine up until now.

I suspect the IRQ sharing could possibly be the cause. I just noticed the exact same error using Vegas Video 3.0c. "An error occurred while starting playback. Unable to mix audio. The operation timed out."

Thanks for the tip. I'll give it a try and let you know. Upon searching I found other threads here on this same topic. Also, Steinberg's knowledgebase has the same suggestion.

http://service.steinberg.net/knowledge.nsf/show/acpi_kills_audio_performance

Thanks,

K Leblanc

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: kleb

Date:7/21/2002 4:00:40 PM

Cuzin B

Great news! The IRQ tweak has cured my timeout error in ACID and Vegas. Thanks for the assist...

Here is another possible trouble spot though...

My ATI Technologies Inc. RAGE 128 GL AGP Display adapter insists on taking the same IRQ 11 as my M Audio DiO 2448 Sound card. This will likely cause problems in Vegas. Audio skips randomly with intensive video edits during playback.

The Vegas thread may be a better place to discuss this.

Thanks,

K Leblanc

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: ramallo

Date:7/21/2002 6:44:46 PM

Hello,

Of course, I was installed Windows 2000.

You think:

If the system comes with windows XP, and I was installed Windows 2000, is a logical need reformat the drive for install the Windows 2K over the XP.

If I tried with Windows 2000 and Xp (I wrote this), isn't a clever idea think that I was need reformat.

For your records, the system fails with Windows 2000 (ACPI), Windows 2000 (Standart PC), Windows XP Pro (ACPI), Windows XP Pro (Standar Pc), I need almost 4 reformats.

Of course the installation was made in a completly virgin Windows

Bye

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: ramallo

Date:7/21/2002 6:52:41 PM

Hello,

>I have had people solve this problem by merely moving their audio card to another >slot in the machine. Sometimes only a clean install of Windows and ACID will solve >the problem.

This is a very clever idea, how I can move the the sound card in a laptop?. I tried with Cardbus card and and USB card and the Vegas/Acid fails with the two. I tried too with a lot of diferents clean installs, and the problem continues.

>We are working on a solution to meet this goal.

I hope this solution.

Best Regards

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: pwppch

Date:7/23/2002 12:16:48 AM

>>This is a very clever idea, how I can move the the sound card in a laptop?. I tried with Cardbus card and and USB card and the Vegas/Acid fails with the two. I tried too with a lot of diferents clean installs, and the problem continues.
<<
Guess you should get rid of your laptop....

USB audio is problematic at best period. USB audio will never assure a timely delivery of the audio stream it can drop samples or do basically what ever it wants in order to meet its timing goals. BAD choice for pro/pro sumer audio.

I have never experianced this problem with a CardBus card (DigiGram). Again, every machine is different. Laptops have all kinds of issues because of the hardwired nature of them.

One thing to try is to complete disable and uninstall all power management hardware and software.


Peter

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: ramallo

Date:7/23/2002 8:00:52 AM

Hello,

>One thing to try is to complete disable and uninstall all power management >hardware and software.

I tried this solution without positive results.

>USB audio is problematic at best period.

I tried with USB, but don't use USB. But for your records, USB bandwith is enougth for 2 in and 2 out at same time of 24 bits 48 kHz. See this table on this link

http://www.usbpre.com/datarates.htm

>Guess you should get rid of your laptop....

You know any better laptop?

>I have never experianced this problem with a CardBus card (DigiGram).

I have nerver experianced this problem with the same hardware (RME hamerfall DSP) and Nuendo o Cooledit, or Windows Movie Maker, or...

I other hand, RME Hamerfall DSP and Digigram plays in diferents leages, you know any better soundcard than the RME for a laptop?.

The problem is clear (Almost for me), fails your audio engine with certain hardware configurations.

Please, work in a solution for this bug.

Regards

Subject:RE: Win2K, KMixers, and Time-Out's... Oh My!

Reply by: Iacobus

Date:7/23/2002 1:10:13 PM

Actually, I've never had a problem with my M-Audio USB Duo. I was bracing myself since I've heard horror stories too. I can go up to 24-bit/96 kHz as well. However, I haven't tried it in a laptop, so...

Iacobus