Cubase SX3 Audio Drop-outs, especially when min. or maximizing
Home > Home Recording Forum > Computers & Software > Cubase SX3 Audio Drop-outs, especially when min. or maximizing
Posted on Jan 06, 2006 08:16 am
carbonic44
Member Since: Nov 23, 2005
Well, the topic basicly says it all. The problem started when I noticed that while playing an audio track, despite the following being properly set-up and tested with any and all possibilities: bit-depth, khz rate, buffer size, sync set-up, audio driver background release setting, vst connections set-up, switched firewire cables and I/O boxes, virtual (paging) memory increased in Win. Xp, numerous PCI latency tools run, etc. etc. .... When I minimize the project window while audio is playing, the audio still plays fine but if I minimize and/or maximize the program window (which encases the project window), ALL audio turns off. Now, I have continuous audio drop-outs regardless of wether I min. or maximize the screen. Cubase never did this before and on the same 2 computers (see my profile), I have done home recording and on-site recording including band recording of 8 simultaneous 24/96 32-bit float-point tracks and mixed down apx 35 @ same rates with absolutely 0 hang-ups. Yes, I've toggled the release ASIO driver in back-ground setting as stated earlier, no goods. Cubase support had no clue how to fix and nowhere in their forums was this issues mentioned. Its definately a Cubase problem. I have run the Double Dawg PCI latency tool to take care of severe PCI bus bottle-necking that was plagueing my system therby effecting ALL my software. All problems were fixed after running it except Cubase SX3 ! I have purchased and used Cubase VST32, SX1, SX2, and now am having problems pop up with SX3 about 2 to 4 times a year. Also, I had the same problems when I tried a Delta 66 (on of the most solid on the market).
Please don't let the complexity of this discourage you from posting. I really, really need help and am open to ANY suggestions at this point.
[ Back to Top ]
Jan 06, 2006 08:23 am Well, on the simple side, I went to a doctor once and said "doc, it hurts when I do this" and the doc said "well, stop doing that".
In an effort to be less sarcastic, I have to ask, your profile has two computers listed, neither of which meet the "recommended specs" for running the application. They both meet the "required specs", but "required specs" are virtually worthless...a 2800+ (your fastest) is right around 2gHz, Steinberg recommends a CPU about 50% faster than that...which one is running into this issue?
The possibility also stands you have gotten infected with some sort of spyware running some background processes or something sucking up CPU power, or installed software that does the same...
Jan 06, 2006 09:16 am I hear ya, Its just the simple fact that both boxes ran Cubase SX3 flawlessly with massive audio loads and not even a hiccup( a year & 1/2 on the 1700+ and 8 mos. on the 2800+ 64-bit, not Sempron.. Full 512 L2 cache on that both running 32-bit Win. XP Pro) Both computers are having the same issues. I also have the #1 MOTU recommended Firewire cards for both 896's. ( 1 older 896 per computer) I'm nearly 100% positive it has nothing to do with hardware. I'm sure Steinberg designers wrote some complex queries when developing Cubase SX3 that load CPU's down. According to the CPU meter in on the Transport Control in SX3, while @ 24/96 32-bit float, it uses apx. 20 to 30% of CPU potential on 1700+. The thing is, I've been using the 1700+, with Acid 5.0 as the Main app.(since Cubase SX3 is down) with Reason 2.5, Drumcore, and Melodyne Studio 3x all Rewired to ACID with each program LOADED full of demo files at max bit/sample rates and once again, not one single slight stutter. Although, I am aware that CPU rate and Memory amt. & rate are most important when running programs, and are often the manufacturer's greatest concerns, most of their stats are probably derived from INTC benchtesting. Intel tends to take the muscle car approach to desktopping whereas AMD is like a supercharged V6. Which wins light to light? I have also installed 1.5 gigs of RAM in both computers. Any other thoughts?
Jan 06, 2006 09:22 am Have you checked for spyware, malware, perhaps any other background processes that may have been added recently?
DrumCore, eh? Pretty cool app.
Jan 06, 2006 09:30 am I just slightly edited that post, so reread if you like. Drumcore is alright, the main thing is the recorded sounds are extremely clean, Almost too clean at times. Usable I'd say but not really as adjustable as I'd prefer. the Melodyne software .. Mys first time with that.. Holy %#%$. That is some FREAKY software. Check their site if you don't know about it. They charge $500 or $600 which garners you 1 license for a stationary computer and 1 for a Laptop. Then $150 for each additional license. Back to Cubase ...no spyware, malware, background services, newly added registries, etc. I've detected no extra CPU spurts either. If you buy Melodyne @ celemony.com. I recommend you go to kinko's with the pdf manual, and pay $18 to have it printed one-side and collated. Well worth having the info directly in front of you.
Jan 06, 2006 09:32 am hmmmm, then I would be suspecting some RAM leakage or hardware issues...possibly driver issues, have you updated drivers? Did the problems start after updating? have you rolled back then?
Jan 06, 2006 09:35 am Yeah, both boxes were blitzed and rebuilt with current updates. The previous installs were the same darn updates though.
Jan 06, 2006 09:36 am starting to look like hardware to me...
Jan 06, 2006 09:38 am I have rolled back too but that hasn't changed things.
Jan 06, 2006 09:46 am In the future I will tame my software purchases and stop "beta-testing" for recent releases. I read an article in EM last month or so re. a cat that does major Video game sound design and now movies. He religiously uses Cubase whil running 5 pc's and a Mac. So are some guys doing TV show sound design I read. They all use the video on Cubase for syncing and most are having NO probs. I just find it awkward to have dual hardware problems on 2 totally seperate systems. Maybe older MOTU 896's have expiration dates . lol
Jan 06, 2006 09:48 am Yeah, I kinda came to that conclusion a while ago. I don't just go an install every damn softsynth thats free, or beta test for any company that wants me to just to get free stuff (especially device drivers)...I am much more picky about how and when I add apps to my boxes...I highly suggest everyone does the same...
Jan 06, 2006 09:58 am Not to say that I actually do betatest, Just that using new releases is practically the same. ya know !
Jan 07, 2006 04:40 pm Fixed it on my slower computer by deleting all clipboard files (did that before too), turned of DEP in Advanced Tab, Performance, Data Execution Protection, added CUbase SX3 to ignore list, started SX3 back up , still didn't work. Then I restarted cubase, applied changes after unchecking the "release ASIO driver in background" (which by the way, I had done 5 times previously and had no positive response)
And mysteriously ALL the problems went away. The first audio file I imported when this problem occured was a vocal track recorded about a month ago. Just a plain .wav file. Then I imported and Acid loop file or two when shortly afterwords the stuttering began continuously
occuring. I've never had problems in the past with files from the Acid sound banks in other programs but I have a hunch that embedded data with some of the wave files caused this problem.
Now the min / maximizing of the program window doesn't stop audio or stutter sound nor does any min/maxing of any program and Rewire syncs to Cubase flawlessly. Not totally sure what I did but hell, It worked!! I hope this helps some of you and thanks all for posting.
Noize2uCzar of MidiAdministrator
Since: Apr 04, 2002
Jan 07, 2006 05:20 pm Glad its working again for you. Hopefully it will help someone down the road.
jmailjimmie neutronMember
Since: Feb 14, 2005
Jan 08, 2006 08:48 am If you check-back, carbonic44, look at your Device Setup and the "Share ASIO driver" check-box (or similar listing...). If it's one way, you lose audio when minimizing, and not the other... Seems to me it happens when you "check" the sharing...
