Forums

Full Version: If I can do this, I'll buy right now
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Been using beta version forever; It does me heart good to see developers actively going for it. Plus you guys have a certain style I find refreshing.
I would like to know if I can disable the visualizer gunk. I do e-music and the pretty pictures are a nice music consumer touch but to reach this apps' potential as a music production tool (don't tell me you haven't thought of it), we need to be able to free up resources (ram and cpu) that visualizer might use, whether in active use or not.
This ability will make mc a true dual use app. No more sittin on the fence, dudes.

Keepin the ole credit card warmed up....one word; yeah or neah.

Best,
Hi,

In short, neah, it is Not Possible to completely disable the visualizer in AudioCodex 1.1, so I guess we miss out on the action.

While there's currently no way to remove all traces of the visualizer, you don't have to use it, just don't open it. 1.1 remembers the main window configuration, and so if you close the visual split, it won't pop open on successive launches. You will also need to go to the 'Visual' tab of the Inspector and turn on Global mode, and make sure the enabled checkbox is un-ticked, that way AC won't attempt to load / enable a visualizer with each new track played.

This might also marry well with the Advanced Preferences 'Show Visuals & Videos in a floating window'. This effectively closes & disables the visual split in the main window.

There is one scenario where this setup will break-down; after a Quicktime video has been played, if you then play a Core Audio track, the visualizer will re-enable itself in the space previously occupied by the movie, and you will have to manually turn it off again by closing the floating window (or shutting the visual split).

I will give some thought to how total disablement of the visualizer might be achieved, but one final thing to note is that if the visualizer is turned off in the Inspector, in theory it should use no CPU cycles, and if it is also offscreen it should also use no RAM (according to Apple's Quartz Composer Developer docs).

Cheers,

Mark Hill
MachineCodex Software
Reference URL's