T3 - AES New Feature Preview

[larsfarm]

Lots of very impressive progress reported! Very nice indeed.

Folder Tracks and Collection Clips - New Folder Tracks allow hiding and showing of groups of tracks in edit with support for nested folders, Edit all folder contents at once using new Collection Clips, New VCA filters to adjust volume of all tracks in the folder

When you say "Edit all folder contents". Could you elaborate a bit on that. What operations can you perform on a collection clip or ask a collection clip to perform? For instance does that include splitting and splicing all contained clips? Does it include changing levels on all contained clips? applying plug-ins to a collection clip? Can you drag a collection clip back and forth in time? copy/paste? ...

best regards
Lars

[ero]

OK, im in for T3. It's upgrade time.

[GaryG]

That all looks amazing, giving the people what they want indeed.

Really keen to hear about these new upgrade paths, hopefully the path for non-US users will be clearly laid out this time.

.g

[djsubject]

looks intresting

keep us posted Beno


Subz

[pquenin]

Impressive features list. I'm using Tracktion 1.6 and have never gone to T2 because there where knowned bugs that where not fixed (first note, rendering, etc...), and idem for T2.1.
T3 seems a dream on the paper, but my only wish is that it will be stable and reliable.

Bravo to the Mackie designer and developpers.

[spacefox]

Very nice. It seems Mackie are finally delivering feature-wise. Most (if not all) the frequentely requested features made it to that list but, or so it seems, without drastially changing T's way of working.

The rack filters enhacements seem real nice - I was looking foreward for features to make working with them more convinient. The rack filters are one of T's great strength, even if they don't get mentioned this often (or are considered a clumsy workaround). Hopefully these will include a quick way of wrapping a multi-out effect into several instances of a rack filter.


Beno: can you confirm if the notorious first-note bug is fixed, or if there were attempts at fixing it, at least? What about the click-through interface bug?

[Ixox]

Does it not work if it is assigned affinity to one particular core in the task manager either?

A friend told me about that about 2 houres ago...
I'll give it a try tonight...
Thanks.


Still no official news about multi core support in T3 ?

I would really have loved a bug fixed T2..
or a T2 with newer Juce version as said some times ago.

[ObsoleteAcc99]

[DELETED]

[ObsoleteAcc99]

[DELETED]

[ObsoleteAcc99]

[DELETED]

[Lunch Money]

Which, the last? All plug-ins do that. At least in Tracktion. It's part of the VST2 spec. It's a poorly coded host or plug-in that doesn't release CPU when not processing audio. I can't think of any off the top of my head, though I'm sure they exist.

As for the rest-- I agree that your requests were relatively minor, and completely fair. I just don't think they'll all be implemented, because some of them are minor or not frequently-asked-for.

Merging audio... that would be AWESOME! Definitely not trying to take the piss out of your suggestions. Au contraire, they seem well thought-out and balanced. I just meant that there were several of them, and it's not likely you'll see all of that particular list on the next release. But again, I don't actually know. I only say that because something like "loop preview at project tempo," while perfectly sensible and intuitive as default behaviour even, isn't something that's even been discussed yet because of how new looping and timestretching is in general. It strikes me as one of those things where now that it's been announced, and someone says, "What about preview at tempo?" Mackie would say, "Snap! That's a great idea! We gotta get on that," which doesn't take away from its worth as a suggestion, but DOES at least offer the possibility that it won't be there at initial release.

Just an example.

Greg

[ObsoleteAcc99]

[DELETED]

[IIRs]

I am sking it be added for non acidized files...

How would Tracktion know how much to timestretch, if they are normal wavs with no tempo data?

[haydxn]

Yeah, the only way it would be able to do that would be to guess the number of beats in it and just go by sample length. that would be wrong in many cases, and could therefore be a pointless feature if there's no guarantee it would get it right.

unless it performed an analysis on the sample when you clicked on it, but then what if you clicked on a massive sample by accident (e.g. a full session recording), and it took ages to process?

TBH i'm not sure it's gonna happen, and i'm not sure anyone will actually be missing out.

[ObsoleteAcc99]

[DELETED]