2.1 feature requests

[haydxn]

/me echos chico. it's not a workaround. it's how it works.

[soulata]

Well, actually, it is *exactly* the same thing. This has been covered about forty million times, and i'm amazed people still aren't capable of realising that the feature is already there. "Render and Add" the track, you get a duplicate of the track as an audio wav, mute the original track and it no longer plays. If you decide to make changes in the future unmute the original, make any changes you want and then render again. This is not a workaround, it's how it's done.

yes and no.

pros:

+ it works
+ it's there already

cons:

- clutter

Folder tracks would help.

It'd be great if we could one click "render the selected tracks individually and put the muted parts with disabled instruments to folder x"

That's d be great. As it is now it is more of a workaround.

IMO

k

[braj]

"• A per-track freeze feature allowing frozen tracks to be mixed and automated ala Logic. This is really handy. " - use render

That's not the same thing. You can't go back 2 weeks later and edit the notes on a rendered track.

Well, actually, it is *exactly* the same thing. This has been covered about forty million times, and i'm amazed people still aren't capable of realising that the feature is already there. "Render and Add" the track, you get a duplicate of the track as an audio wav, mute the original track and it no longer plays. If you decide to make changes in the future unmute the original, make any changes you want and then render again. This is not a workaround, it's how it's done.

There's no point in making feature requests for features that already exist. Try reading the manual.

In Logic, if I want to conserve resources on my modest laptop, I can freeze all my (especially soft synth) tracks. I don't have to deal with a bunch of disabled tracks, and my screen isn't cluttered at all. one sweep of the mouse and everything is unfrozen. This is especially handy if I want to tweak the tempo at a later date and of course on final mixing. Using your way, I'd have to unmute all the muted tracks, and mute all the rendered tracks nearly every time I wanted to change anything. It isn't the same thing at all.

And I hate the bullshit way some people say 'read the manual. Ignorant f**ks That's not how it's done right.

[braj]

If the point of Tracktion is to simplify and streamline your workflow, then it is a workaround. It isn't very efficient. You guys are happy with that? Bah!

I need some sleep!

[chico.co.uk]

Things i'd like to see in Tracktion 2.1

1) The ability to edit the colour schemes
2) A way to record both audio AND midi
3) Support for VSTs
4) Some way to use an external midi controller
5) Individual volume and pan filters for each track
6) A decent manual that tells me those features already exist

Anybody else?

[braj]

Things i'd like to see in Tracktion 2.1

1) The ability to edit the colour schemes
2) A way to record both audio AND midi
3) Support for VSTs
4) Some way to use an external midi controller
5) Individual volume and pan filters for each track
6) A decent manual that tells me those features already exist

Anybody else?

Just because you don't know what features actually do doesn't mean you have to try and be a cheeky bastard

[Mr. Tingle]

I for one would use the individual freeze track instead of track render, especially as track render does not render at 32bit!

My main concern with freeze is that it keeps on unfreezing! How many times I've reopened an edit to find everything thored made me give up. This is especially true when you regularly swap between different sound cards.

The best bit about freeze is the increase in work flow and reduction in clutter, both big pluses that Tracktion usually scores well with.

This would make working with big projects a god send (I work with big projects )

[braj]

Regarding rendering and muting source tracks: how many tracks would you do this with, because without a conventional mixer in T you would have to make the track sizes large enough to see the meters, and that would mean a huge amount of scrolling to see all the tracks, which defeats T's 'one screen' interface concept. It would seem anything you could do that would aide making that one view provide the most info in one view would be worthwhile, right? If you want to mix drums on their own tracks and ever feel a need to freeze them (er, render and mute, so sorry!) you'd be clicking little 'm' for days.

Someone mentioned in another thread that folder tracks would go against the 'one screen' concept that therefore that's probably why they don't exist, which I could understand.

[nuisance sonore]

About the clutter thing, you guys know about the "shrink" and "grow" track buttons? I didn't untill last week, just overlooked it I guess, and shrinking muted track really help cleaning up the interface when you have lot's of tracks.

[braj]

About the clutter thing, you guys know about the "shrink" and "grow" track buttons? I didn't untill last week, just overlooked it I guess, and shrinking muted track really help cleaning up the interface when you have lot's of tracks.

Try altering the volume and pan, reading the filters and meters with 30+ tracks shrunk on the screen. Not fun:( Anything to aide keeping everything simple and legible the better. Actually, anything over 20 and you gotta squint.

[soulata]

Actually, anything over 20 and you gotta squint.

exactly.

k

(not starting a war here. I Tracktion)

[braj]

Yeah, I'm not dissing T, I'm just making feature requests here. 2.1 and up!

[haydxn]

okay, so this IS a workaround but if you put all the 'shrunk' source tracks to the bottom of the list, then you can forget about them til you need them. grab the line separating the shrunk and normal tracks with the right mouse button and you'll stretch all the tracks above them to whatever height you want

[IIRs]

Try altering the volume and pan, reading the filters and meters with 30+ tracks shrunk on the screen. Not fun:(

i regularly get more than 30 tracks to deal with: leave them zoomed vertically to a sensible size so you can adjust the vol / pan filters, and use the mouse-wheel over the filters section to scroll vertically up and down. If you need an overview, cntrl-scroll to zoom vertically, or hit F8. I find it very fast and easy personally..

As far as muted tracks go, when I'm fairly certain I won't need to re-render a track, I delete the muted original(s) and save the edit with an incremented version number. This keeps my edits manageable, while still allowing me to change my mind if I really need to..

[braj]

Another instance where Logic's freeze is better: Render a track, mute the source in T. Go do automation on the rendered track, later realize you want to change the source note data, then you have to go redo all that stuff. Maybe you can copy the automation from one track to another in T, I'm not sure, but it still takes a bunch of extra steps and is a major hassle if you have multiple rendered tracks to work with. In Logic, you just unfreeze the track, alter the midi, and click freeze on the tracks again and you're done. Really simple.

I personally don't see why anyone objects to this feature request. You like doing things the hard way or something?

If you need an overview, cntrl-scroll to zoom vertically, or hit F8.

The problem here is if you have 20 redundant tracks, you have to see them every time you hit F8, which makes that view less useful.

I like T's current freeze/render features *sometimes*, but it is far less flexible for some things (which I find very useful in Logic).

To throw the fanboys a bone , Logic (at least LE7) doesn't allow you to render to a new track, you have to solo a track and bounce down to an audio file, and reimport it. I always yearn for T's render when I need it in these situations. ie. I want to chop up and mess with the audio file. If I just want to save CPU cycles though, Logic's freeze works great.