Petition: Should all hosts have "render to track" feature?

Audio Plugin Hosts and other audio software applications discussion

Should all hosts have such "render to track" feature?

Yes
58
79%
No
15
21%
 
Total votes: 73

RELATED
PRODUCTS

Post

Here is some explanation:

Each track (audio/midi/whatever :) ) has a little button beside it called "RTT".

When you press this RTT button, the following will automatically take place:
- the whole contents of this track will be rendered. Only regions with sound will be rendered into clips. Regions with silence will be omitted.
- a new audio track will be created
- all the rendered contents inserted into this new track at exactly the same location as the source
- the source track will be automatically desabled taking it out of RAM/CPU (all the plugs will be disabled)
- the source track's width will be minimized to like 2 mm or the source track will be moved to a folder track

Guys, wouldn't this be beautiful?

Tracktion 2 is very very close to completing this whole process.

Also, notice how I called this thread a "petition" because this is a formal REQUEST to all host developers!!! hehehe
Last edited by superddman on Sun May 07, 2006 2:04 am, edited 1 time in total.

Post

superddman wrote:... - all the rendered contents inserted into this new track at exactly the same location as the source ...
What host are you using? What do you mean by "same location"?
Eventually something intelligent will appear written here. Watch this space.

Post

superddman wrote:Here is some explanation:

Each track (audio/midi/whatever :) ) has a little button beside it called "RTT".

When you press this RTT button, the following will automatically take place:
- the whole contents of this track will be rendered
- a new audio track will be created
- all the rendered contents inserted into this new track at exactly the same location as the source
- the source track will be automatically desabled taking it out of RAM/CPU (all the plugs will be disabled)
- the source track's width will be minimized to like 2 mm or the source track will be moved to a folder track

Guys, wouldn't this be beautiful?

Tracktion 2 is very very close to completing this whole process.

Also, notice how I called this thread a "petition" because this is a formal REQUEST to all host developers!!! hehehe
Yeah it would be nice. It would be even nicer if freaking Digidesign would get their act together and let you render a mix. I get so damn sick of real time bouncing! :x
Vocalvoodoo Productions and VO
St. Louis, MO
www.Vocalvoodoo.com
www.facebook.com/vocalvoodooproductions

Post

I think its much simpler to work within your limitations, don't you? Encourages creativity and innovation, don't you think? [Of course you don't.]
NOVAkILL : Legion GO, AMD Z1x, 16GB RAM, Win11 | Audient EVO 8 | Lumi Keys | Studio Pro 8
Korg Odyssey, bx-oberhausen, Proxima, PolyMax, GR8, JP6K, Union, Atomika,
Invader 2, Flow Motion, Olga, TRK 01, Thorn, Spire, VG Iron

Post

Ja.x wrote:
superddman wrote:... - all the rendered contents inserted into this new track at exactly the same location as the source ...
What host are you using? What do you mean by "same location"?
If the source track has two separate sound clips: one sound clip from 1:04 until 1:43 and the second sound clip from 2:45 until 3:01, then the rendered content will also contain two separate sound clips. One will be placed from 1:04 until 1:43 (if the release is the same) and the second one from 2:45 until 3:01 (if release is the same). If the release is longer, then the new content clips will also be longer.

Basically, silance will be omitted. No clips will be rendered in the region where there is silenece. Only regions with sound will be rendered.

Post

superddman wrote:
Each track (audio/midi/whatever :) ) has a little button beside it called "RTT".

When you press this RTT button, the following will automatically take place:
- the whole contents of this track will be rendered
- a new audio track will be created
- all the rendered contents inserted into this new track at exactly the same location as the source
- the source track will be automatically desabled taking it out of RAM/CPU (all the plugs will be disabled)
- the source track's width will be minimized to like 2 mm or the source track will be moved to a folder track

WOW - you just invented track-freezing :hail:




too bad that da real shit nowadays is clip-based freezing.


edt: reading your further explanation I realize yopu jut invented clip-based freezing - Tracktion hoiwever is far from it. Look at Sonar and Samplitude. They do exactly what you are asking.
Last edited by jens on Sun May 07, 2006 1:16 am, edited 1 time in total.

Post

BONES wrote:I think its much simpler to work within your limitations, don't you?
This has to be one of the biggest contradictions hehehe

No, limitations don't make things simpler for me. They do the reverse. They discourage me. Work arounds piss me off. :)

Post

jens wrote:
superddman wrote:
Each track (audio/midi/whatever :) ) has a little button beside it called "RTT".

When you press this RTT button, the following will automatically take place:
- the whole contents of this track will be rendered
- a new audio track will be created
- all the rendered contents inserted into this new track at exactly the same location as the source
- the source track will be automatically desabled taking it out of RAM/CPU (all the plugs will be disabled)
- the source track's width will be minimized to like 2 mm or the source track will be moved to a folder track

WOW - you just invented track-freezing :hail:




too bad that da real shit nowadays is clip-based freezing.
Actually you don't get the real differnce, FREEDOM.

With track freeze once your freeze a track it is completely disabled from use. You can't move the frozen contents, you cannot apply fx onto frozen parts, you cannot change automation envelopes, you cannot delete frozen parts. You are stuck (only sonar and samplitude have somewhat usable freeze but it is more based on my outline)

In other words, I hate freeze.

With something that I have explained you still have a complete freedom of the rendered tracks.

Post

Wow, I see almost an even score in the poll. All those against it, please provide some words to back it up. I don't know how on earth you would not benefit from something like this. Strange.

Post

superddman wrote:Wow, I see almost an even score in the poll. All those against it, please provide some words to back it up. I don't know how on earth you would not benefit from something like this. Strange.
That's because kvr is full of useless, flippant trolls who live to shoot
down people's ideas.

Then there's helpful people, too, like you that hopefully don't get discouraged
by the mindless twits of the internet.

In Samplitude you can do whatever you want to the audio once it's frozen in place -
add new fx, envelopes, whatever - the freeze is new rendered audio and yet the freeze
can be undone with one command should editing need to be done. It's perfect and
all programs will indeed need to get this feature someday.

Post

runagate wrote:
superddman wrote:Wow, I see almost an even score in the poll. All those against it, please provide some words to back it up. I don't know how on earth you would not benefit from something like this. Strange.
That's because kvr is full of useless, flippant trolls who live to shoot
down people's ideas.

Then there's helpful people, too, like you that hopefully don't get discouraged
by the mindless twits of the internet.

In Samplitude you can do whatever you want to the audio once it's frozen in place -
add new fx, envelopes, whatever - the freeze is new rendered audio and yet the freeze
can be undone with one command should editing need to be done. It's perfect and
all programs will indeed need to get this feature someday.
Yes, you are completely right about Samplitude. I have tried it in the past and all the hosts should take an example from it in terms of freeze. (sonar is also a bit better)
However, you should still notice some differences between my outline and Samplitude's freeze. Main difference is that with my outline, you can continously render tracks out of the same source. Whereas, with Samplitude's freeze, you would have to unfreeze it first which is not a big deal but still :) With my outline the disadvantage is that there is more tracks taking up space.

99% of hosts that have freeze, have it implemented literally, meaning, everything is frozen without any freedom to change things.
I don't know how poepole can live with that :)

Post

That's a terrific idea, Superddman. I can't see any reason for not implementing your idea. It makes perfectly sweeet sense to me!!! :D :D
RogerPerrin

I'm up to my old hat tricks again.

Post

I agree.

I wish they would implement this in Live. Freeze has uses obviously, but when you want to render several midi clips in Live, the best you can do is bounce them down by recording them (which is primitive) or freeze them which limits what you can do to them. I am hoping that Live 6 implements RTT. It is a Godsend in Tracktion.
Mixcraft 8 Recording Studio : Reason 10

Post

There is a feature similar to this in EnergyXT although not as easy to sort as what you suggest. Truely one of my most used things.

I do think that all sequencers should have this function though.

Post

I don't really need freeze :shrug:

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”