Forums - Computer music & technology
Subject: Here we go again
Viewing all 19 messages - View by pages of 10: 1 2
Original Message 1/19 08-Feb-03 @ 11:46 PM - Here we go again
PCAV:
System Overload.
The audio engine was not able to process all required data in time.
(-10011)
Any ideas anyone? I have my latency set on 256- I tried moving it around but didn't do much. I only get the error message when I am playing in the arrange window, it popps up every second or so and interupts play. Is anyone familiar with the problem or the similar soundcard?
Thank you guys, I promise this will be the last topic =)
Message 2/19 09-Feb-03 @ 12:09 AM Edit: 09-Feb-03 | 12:26 AM - RE: Here we go again
Message 3/19 09-Feb-03 @ 01:05 AM - RE: Here we go again
On the cpu: "Audio" is like really high, red sometimes, but disk i/o never moves...my cpu is p4 2.0gigs, 512 rd ram.
I tried higher latency, but no luck.
Also, it seems to work alright with really small files etc, but with my song (7mins) that I made on it, everytime I play it, it gives me the error message, while I can play small files with the same amount of synths/tracks etc, just not the same amount of matrix data. (If you know what I mean)
I have 15 instruments, 10 are s/w synths (5 are ES2, 1 FM7, 1 ES1, and 7 ESX24 the sampler). I don't think it is the ammount of instruments I am using becuase I can open a different file with the same ammount and work just fine, it only overloads with alot of shit on the arrange screen.
Message 4/19 09-Feb-03 @ 01:22 AM - RE: Here we go again
Regards.
Steve.
Message 5/19 09-Feb-03 @ 02:02 AM - RE: Here we go again
Message 6/19 09-Feb-03 @ 09:58 AM - RE: Here we go again
You may have a corrupt song. This happens from time to time.
Creat an brand new autoload, andd copy all your songs stuff into it.
Also sometimes if you create a song on a certain version of logic then upgrade to another which is a major update (eg 5.0 to 5.2 which is a brand new audio engine) this can cause strange things....
Cheers
Stvy
Message 7/19 09-Feb-03 @ 12:02 PM - RE: Here we go again
Is Logic's Scroll In Play activated? Have you tried altering your display settings? Changing the amount of colours (Bit-depth), or Hardware Acceleration etc may be what you're after here.
Regards.
Steve.
Message 8/19 09-Feb-03 @ 02:59 PM - RE: Here we go again
No- scroll in play is not on.
Tried display, but no luck. =(
Message 9/19 09-Feb-03 @ 05:52 PM - RE: Here we go again
Also look at your video settings. What kind of video card are you running. Are you pushing it too hard? Reduce the resolution and bits. See if this makes a difference on the audio meter.
If these don't seem to help, then is this computer dedicated to audio ? If not and you can't afford to do that get a copy of partition magic and make the system dual boot. Use one for games, Inet, Word proc. and dedicate your self to a few choice apps for audio. Tweak out audio partition you should see better performance.
Once your happy get a copy of Ghost or whatever and back up the whole partition.
Flor
Message 10/19 09-Feb-03 @ 06:28 PM - RE: Here we go again
i'm saying this cause i caught my machine doing this on one track where i'm feeding a reverb from a delay plugin, and as soon as i'm not sending anything into the delay it builds up and overloads. then, when i mute the track which feeds both, the cpu meter drops right down and makes no problems whatsoever.
might not be your problem, but i thought i post this somewhere...
Message 11/19 10-Feb-03 @ 12:20 AM - RE: Here we go again
No unfortunatley, this cpu is my general cpu, even though I really try to keep it basically for music and music downloading. I do have a copy of partition magic lying around somewhere, and that seems like a good idea.
I reinstalled the program, and it hasn't been giving me any shit lately. I'm going to try all that stuff though when I put a track together tomarrow when I have some time.
I know it's a little off topic, but it's still on logic at least:
When logic is initializing my midi ports when I start up, I get this error that says:
(While trying to open MIDI port ""in function"midiOutGetDevCaps", the error "A device ID has been used that is out of range for your system." occured. Make sure that the midi interface is connected and switched on.)
Could this contribute to anything? My midi interface is on and midi works just fine in logic even after that error.
Thanks guys,
Andrew
Message 12/19 13-Feb-03 @ 02:03 AM - RE: Here we go again
Message 13/19 13-Feb-03 @ 09:08 AM - RE: Here we go again
Message 14/19 13-Feb-03 @ 09:01 PM - RE: Here we go again
My midi interface wants to install itself every time I load up my cpu...but it works in logic...but still gives me that shit every time I start logic too.
Where did you download the beta drivers? I tried downloading some other drivers, but the only ones that worked were on the german site
Message 15/19 20-Feb-03 @ 08:28 AM - RE: Here we go again
Message 16/19 20-Feb-03 @ 11:31 AM - RE: Here we go again
I used Logic with midimans EASI driver myself which is emagic's own protocol like asio.
___________________________________
I had an idea for a script once. It's basically Jaws except when the guys in the boat are going after Jaws, they look around and there's an even bigger Jaws. The guys have to team up with Jaws to get Bigger Jaws.... I call it... Big Jaws!!!
Message 17/19 20-Feb-03 @ 02:17 PM - RE: Here we go again
Message 18/19 20-Feb-03 @ 05:26 PM - RE: Here we go again
Message 19/19 20-Feb-03 @ 08:25 PM - RE: Here we go again
Graphics cards take up a LOT of CPU when drawing images...turn down hardware acceleration in windows (won´t make any diffrence in games)
And also, it could be denormalization happening, there are plugs that uses very low noise to avoid this, specially created for the denorm issue. Try DigitalFishPhones denorm plugin.
Viewing all 19 messages - View by pages of 10: 1 2
There are 19 total messages for this topic
Reply to Thread
You need to register/login to use the forum.
Click here to Signup or Login !
[you'll be brought right back to this point after signing up]
Back to Forum