goddamn computer issues

i spent the last week of my spare time trying to figure out why i was getting such bad crackling audio on my DAW
it would always crackle when plugin GUIs were showing
i was repositioning PCI cards, changing drivers, changing video cards, looking into changing PCI latencies...a real mess
til finally i found that it was 1 single plugin that was dicking me over the whole time...
plugin => dumpster, freeware versions already replaced it anyway.

WHY are some commercial plugins so poorly coded?
WHY do these plugins try to fit everything under the sun into 1 vst when modularity is better anyway???

i think i'm going to stop buying plugs altogether unless they only do 1 function and do it completely and with low CPU impact

Tell me about it...

I 'updated' to Lion last night because all my software and hardware drivers are now compatible, only to find my interface won't work.

Probably doesn't help that I haven't got a **** clue what I'm doing with Mac!

sometimes i'm amazed that anyone gets any work done at all.
my work getting finished with Warm Blooded Lizard was entirely due to not changing a DAMN THING hardware/pluginwise on my DAW for a year plus. i changed some workflow stuff but for the most part everything was static.

Coz wrote:Tell me about it...

I 'updated' to Lion last night because all my software and hardware drivers are now compatible, only to find my interface won't work.

Probably doesn't help that I haven't got a **** clue what I'm doing with Mac!

you can boot Mac OSX Lion in 32 bit mode, as long as you have the latest drivers installed. To boot the Mac in 32 bit mode hold down the 3 and the 2 buttons while starting up.

try it, see if it works! it worked with another cat who had similar problems w/ his tascam uss-122...

Nym wrote:sometimes i'm amazed that anyone gets any work done at all.
my work getting finished with Warm Blooded Lizard was entirely due to not changing a DAMN THING hardware/pluginwise on my DAW for a year plus. i changed some workflow stuff but for the most part everything was static.

Yeah, once I crack this problem I'm leaving well alone. On the software side everything works perfectly and Lion is uber sleek... I just can't get the interface to link to the comp.

Rockin'DoublZ wrote:

Coz wrote:Tell me about it...

I 'updated' to Lion last night because all my software and hardware drivers are now compatible, only to find my interface won't work.

Probably doesn't help that I haven't got a **** clue what I'm doing with Mac!

you can boot Mac OSX Lion in 32 bit mode, as long as you have the latest drivers installed. To boot the Mac in 32 bit mode hold down the 3 and the 2 buttons while starting up.

try it, see if it works! it worked with another cat who had similar problems w/ his tascam uss-122...

Nice one, I'll try that tomorrow.

ive had similar issues with vista (i know ) and ozone 4 in pro tools...

it was killing me for some time but i figured out it was ozone causing this problem that whenever i switched between sessions my cpu would overload if ozone was active in any one of the mixing channels... it's bullshit but for the time being whenever i close out a file i have to deactivate ozone 4...

ive restored my cpu countless times and reinstalled protools and it all boiled down to ozone... i dont know too much about reprogramming plugins but i totally understand your frustration... im pissed cuz i spent 200 on software that interrupts my workflow...

j rhodes wrote:ive had similar issues with vista (i know ) and ozone 4 in pro tools...

it was killing me for some time but i figured out it was ozone causing this problem that whenever i switched between sessions my cpu would overload if ozone was active in any one of the mixing channels... it's **** but for the time being whenever i close out a file i have to deactivate ozone 4...

ive restored my cpu countless times and reinstalled protools and it all boiled down to ozone... i dont know too much about reprogramming plugins but i totally understand your frustration... im pissed cuz i spent 200 on software that interrupts my workflow...

Ozone4 is a HUGE CPU hog. Its little sister Alloy is a much better resource for multiple instances in a session with more than a few tracks and tons of signal processing.