FX Freeze type script?

PipelineAudio wrote on 9/19/2004, 9:43 PM
I and the other Vegas users are dying for a solution like FX Freeze

FX Freeze is not available for DX and has a host of other problems as well.

I think maybe we can do it a little better

Heres how I envision it happening

1. You select the track(s)

2. you open the script and choose freeze

3. For each event the script opens " apply non realtime fx" as if you right clicked the event

4. The script copies all insert fx and insert fx settings from the track it belongs to, including fx automation for insert fx on that track

5. The script then applies all those fx, choosing correctly if it is a mono or stereo event per event and then as normal opens a copy as a take on top of the original

6. The script then deletes all the channel's insert fx but somehow remembers the channels insert fx automation ( if any)

7. You go on your happy way with the fx you liked, but now the CPU is much less loaded down

to unfreeze

1. select the track(s)

2. Open the script and choose UnFreeze

3. The script now goes and brings to the top each correct take of each event pre freeze script

4. The script restores all channel insert fx and insert fx settings for the selected track(s)

5. The script then restores all insert fx automation for that channel

PLEASE tell me this is possible ?

Comments

rcampbel wrote on 9/20/2004, 7:22 AM
I wish that it were possible. I was trying to copy effects from one event to another this week and could not get it to work. In looking at the code, it does not appear to be possible with the current API implementation. The other problem is that the Apply non realtime fx command is not available to the API.

The Effects object does not allow access to all of the plug-in settings, so the only what that you could get this to work would be if you could actually copy the Effect object and add it to another Effects collection. Unfortunately this does not work either.

We have added this to our scripting API requirements list that we will be sending to Sony.

EDIT: Added the link to the requirements list. Feel free to add to the list.

Randall
PipelineAudio wrote on 9/20/2004, 10:02 AM
Well, second best, for now I guess is something that renders the track out, with the console zeroed out and nothing BUT the track and its insert fx, like none of the send fx or whatever, and maybe saves the fx chain as an fx package automatically, maybe asking you for a name?
SHTUNOT wrote on 9/20/2004, 10:34 PM
Pipe start bothering gary+jetdv about this. I told them my ideas on this type of freeze functionality a while ago. He said he still had the notes of my ideas so I hope its in the works. I even spoke to gary kleiner about this at the nyc vasst stop.

Keeping my fingers crossed.

Ed.
rcampbel wrote on 9/21/2004, 12:04 PM
I have taken a look at this and talked to jetdv. There are several issues:

1. It is easy enough to solo a track and render it to a new file.
2. However, there is no way in the current API to disable the AudioBus or Master effects. Also, there is no way to remove and then restore the effects.
3. The Bus volume and pan settings are not exposed to the API.

So, another approach that I came up with is to create a new audio bus, route the bus to the output hardware to bypass the master bus, route the track to the new audio bus, then render the track. The issue with this approach is:

1. I can create a new audio bus, but can not set where it is to be routed.

So, here is a process that I think could be scripted:

1. The user would have to create a new AudioBus with no effects that is routed directly to the output hardware and give it a specific name (e.g. "Freeze")
2. The user would select an audio track and run the Freeze script.
3. The script would reroute the selected track to the Freeze audio bus.
4. The selected track would be soloed (ensuring that no other tracks are soloed)
5. The timeline would be rendered to a new .wav file in the temp files folder (or some other location if desired)
6. The selected track would be switched back its original audio bus and muted.
7. A new track would be inserted and the rendered .wav file added to the track. The new track's output bus would be set to the same as the selected track.

To unfreeze, the user would simply mute or delete the new track and unmute the selected track. Could also have a script do this and also delete the temp .wav file.

Is this what you are looking for?

Randall
PipelineAudio wrote on 9/21/2004, 1:21 PM
might be doable, but muting the tracks does not free up the resources. I am asking for this tool because I run out of CPU juice to run FX. I need a way to renbder them out so I can remove them from the project, but still be able to pull them right back in instantly if I need to make a change.

Maybe a bunch of us on the audio side should email SF/Sony and see if they cant make these features available to the scripting commands
rcampbel wrote on 9/21/2004, 1:55 PM
Are you trying to just save CPU cycles or are you also trying to save memory? I just tried a test on my system with a single audio track and three fully turned on Ozone plugins running on the track. With the track unmuted, the CPU was around 70%, when I muted the track, the CPU went down to less than 10%. Of course, memory usage does not change.

I think that it would be a good idea if customers would email Sony about scripting enhancements.

Randall
jetdv wrote on 9/21/2004, 2:26 PM
I think that it would be a good idea if customers would email Sony about scripting enhancements.

Or go vote and/or add more suggestions in our poll and we'll forward the information.
PipelineAudio wrote on 9/21/2004, 3:06 PM
weird Some fx just simply dont seem to bypass right. In the case of the UAD-1 youve only got so many plugs able to be run on the card, muted or not. Im trying to save CPU, memory, and resources in general. The more youve got going in vegas, edits, automation, fades, events, takes, all that starts to sketch out the audio performance. But plugins seem to be the worst offenders.
rcampbel wrote on 9/21/2004, 3:28 PM
Interesting. Well, I guess if the freeze script is not going to help, there is no point in writing it. Sorry.

Randall
PipelineAudio wrote on 9/21/2004, 5:03 PM
I just have to think of better alternative steps, for the concerns we have. Im sure there's some way
rcampbel wrote on 9/21/2004, 5:10 PM
Let me know if you have any other ideas and I will see if it can be scripted.

Take care,

Randall
PipelineAudio wrote on 9/21/2004, 6:32 PM
Randall, is there no way for a script to copy to memory or save someplace the channel's insert fx settings?
Trying to rethink this here
jetdv wrote on 9/21/2004, 8:47 PM
That answer is no because you can't read the individual settings on the effects settings screen.
rcampbel wrote on 9/21/2004, 8:48 PM
Nope, not with the current API. I have talked to Sony about this and they acknowledged that this can't be done.

The API allows me to add an effect and set a preset name, but I can't read the current effect settings or even read the current preset name. I can get the list of all presets for a plug-in, but not the current one. I can't disable/enable an effect. I can't copy a track or Bus track either. The ability to rebuild and automation envelope is also questionable.

So, the user could save a preset for each effect on a track, then I could delete them and add them back, but the user would have to tell the script which presets to reapply. By the time you get though with all of this clicking, you could have done it manually.

I am afraid that there are just too many holes in the API for this to happen.

There are some programs to automate mouse movements, but in general this is not reliable. I don't see any keystrokes that will bring up effects so that we could disable them with a keystroke.

Randall

Randall

PipelineAudio wrote on 9/22/2004, 12:04 AM
OK looks like you guys have seriously done your homework! Ill be bugging SF about it, and also filling out your poll thingy

Thanks for taking all this time to help out!