Digital Audio Workstation & MIDI > Vision & Studio Vision by Opcode

CPU Overload

(1/5) > >>

Syntho:
When I'm using SVP it's usually in midi-only mode. If I stop and start a song very quickly, I always get the CPU overload thing coming up. If I'm slower with it, no problem. I'm doing this on a 9600/350 machine, so maybe this is normal, but I'm guessing I'm being a little too fast for SVP. Anyone else get this?

GaryN:
When you say "stop and start", do you mean pause and resume from that spot, or stop and restart from the beginning?
If the latter, do you have a bunch of stuff like patch changes etc. at the beginning?

You seem to be saying there's a whole bunch of data that needs to be processed and/or sent on restart.
Simply starting over is not a proc-heavy thing in itself unless there are other things happening as well.

I need more info: How many tracks? Does it gradually get slower as tracks are added? Are you sending or receiving any kind of sync? (especially MIDI beat Clock?)
* Try muting all but one and see - then add in more. Watch both the track count and if maybe one or more of the MIDI mod/synths is spitting something back it shouldn't be.
** Set a loop and/or reset the beginning so the song starts on bar 2 or 3 and see what happens.

The 9600 @350MHz should not be choking. If you don't actually hear any ill effects and it's just the overload indicator, it MAY be that SVP just "expects" more proc power (something other than a 604e) than plain vanilla Vision would have. This guess is based on absolutely nothing at all because …WhoTF really knows?

Syntho:
I made a mistake in the setup info. I was actually running on the Acadia engine. When I would hit the stop and start button very fast (keyboard shortcuts rather) the system would come to a halt and the little box that shows CPU, Disk and Ram would have red flags by both the Disk and CPU. I switched it to midi-only and all is well now. I've also got the optimized Acadia file (I think it's called) for the 9600/350 in there. I haven't yet tested it with DAE since I only use that for Pro Tools so I wonder if it'll do it with that.

Off topic: I use Pro Tools for audio recording/editing, but man... SVP just seems awesome as an all-in-one DAW. I absolutely couldn't do what I do in PT in SVP, but I'm tempted to try the audio capabilities in SVP and see how I fare.

GaryN:

--- Quote from: Syntho on June 15, 2020, 08:48:02 PM ---……the little box that shows CPU, Disk and Ram would have red flags by both the Disk and CPU.

Off topic: I use Pro Tools for audio recording/editing, but man... SVP just seems awesome as an all-in-one DAW. I absolutely couldn't do what I do in PT in SVP, but I'm tempted to try the audio capabilities in SVP and see how I fare.

--- End quote ---
Flickering the Disk and CPU lights , especially when you don't have any digital audio tracks recorded, is not normal. There's probably something in the audio settings that's incorrect and you haven't found it because you've never really used SVP for audio. It's probably no big deal. It just might be the "wrong" Acadia or……? No big deal though.

That said, I really don't think there's anything OS9 PT can do that SVP can't. Seriously. I'd love to hear what exactly you "absolutely couldn't do what I do in PT in SVP". I'm really curious…

Syntho:
The editing seems much quicker in PT from what I tried in SVP, and there is no Sound Replacer  -afro-

Navigation

[0] Message Index

[#] Next page