2.1 feature requests

[headquest]

Racks and sends really do make things tricky though.

Tracktion's mixer paradigm makes it more tricky too, I suspect. But I love Tracktion's mixer paradigm

[headquest]

I'm not bvothered about the 64bit summing, but I've always wondered why Tracktion renders tracks at lower bitdepths. To me it makes sense to leave them as 32bit.

I'm not sure about the 64-bit summing, but I guess you should know .

As for rendering at lower bit depths, I can understand why it defaults to the soundcard settings, I agree that it would be nice to override this and keep things at 32-bit. I think that is actually quite normal in other software (I use Adobe Audition, which treats everything internally at 32-bit if you set it to). Is this something you have asked Jules about?

[valley]

The 32bit issue has been mentioned numerous times. I might raise it again, though.

If I can possibly walk over into the "we already have render and add" territory whilst in a freeze thread, without being mauled as a fanboy:

one thought I had, was if folder tracks were implemented, and they were implmented in such a way, that you can opt to collapse to one track (ie there may be five tracks in the folder but only one is visible), this could give you two advantages:

- group mixes could be collapsed down to just the group mixer track
- you could use render and add much like some people do at current, *but* the original and rendered track could be foldered into one track. You could freeze (or more accurately render) whichever filters you want, leaving the remainder available for editing. It wouldn't be as elegant as a true feeze, but it offers most of the same advantages without getting to bogged down in racks, auxes and whatevere else.

[diverdee]

For me freeze seems to work as it is. Maybe another freeze option would be great, personally I think that the folder track idea would be extremely useful in loads of difernet ways if implemented right - just my tuppence worth.

[semiquaver]

I have come around to the folder tracks idea and your suggestion Valley is right on the money. Blank tracks are a waste of real estate!

Among other advantages to that scheme are that you could folder together muted source tracks and a final comp! Likewise a drumkit could be collapsed and the resulting track would still look like drums.

One detail that would fall to Jules to settle would be which editing ops apply to all the tracks in the folder and which (if any) only to the frontmost track.

[diverdee]

tracktions all on 1 screen paradigm is cool - but as has been mentioned numerous timers it can get cluttered with large projects. Folder tracks would definately be a useful addition that could, if not solve, at least help to minimise some problems & help to provide more viable workarounds 4 others. I reckon.

[braj]

one thought I had, was if folder tracks were implemented, and they were implmented in such a way, that you can opt to collapse to one track (ie there may be five tracks in the folder but only one is visible), this could give you two advantages:

- group mixes could be collapsed down to just the group mixer track
- you could use render and add much like some people do at current, *but* the original and rendered track could be foldered into one track. You could freeze (or more accurately render) whichever filters you want, leaving the remainder available for editing. It wouldn't be as elegant as a true feeze, but it offers most of the same advantages without getting to bogged down in racks, auxes and whatevere else.

That sounds brilliant. I'd be happy with that. Maybe a 'render to <folder track> option so you can choose which available folder track to render to. I like this approach, you could have multiple takes (midi or rendered) of the same part saved in a folder track like an archive for that part.