T3 - AES New Feature Preview

[valley]

95% of the time your loops are trimmed to bar divisions?

It wouldn't work at all on my loop library 'cos in most cases I keep the first kick of the next repeat.

[shindigger]

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

wow....90% of my plugins continue to process LOL...must know what u r using....

Tracktion's broswer the way i undderstand it IS going to have preview at project tempo, thats what support for acid loops is all about. I am sking it be added for non acidized files...

regardless, no multi processor, no point. That is number one feature, and to be honest, if T3 is released without full multicore support, it will be the ONLY host app on mac to not have it!!

I just have a bad feeling cause I thought it would be at the top of the announcement list, and something that would put alot of minds at ease...

Here ya go...


Misc. - Universal Binary for Mac Intel Support, Windows Vista RC1 Support, VST 2.4 Support including complete *.vstxml support, New Hover Edit of Clips, Improved Meter Response with improved scaling and range, Improved Input Routing view and operation combining previous old and new views, New mute individual clips, New editable Clip Length field for all clips, Divider between Controllers and Notes in Midi Editor can now be resized, Bottom Panel can now be resized, Zoom controls from GUI, New First Run Wizard, Misc. GUI improvements, Lots of new key commands, Many More…

[GaryG]

It wouldn't work at all on my loop library 'cos in most cases I keep the first kick of the next repeat.

just out of curiosity, why's that then?

.g

[Lunch Money]

ttoz, I'm not using anything special. Just your usual selection of freeware, included plugs, and a few commercial offerings like RoomVerb M2, Green Machine Amp II, and Wusikstation.

If you keep your audio input active, and do not have a threshold set for activation, you might be processing the sound of air. Dunno!

[flamin-gitaur]

someone said once you cant hear .005 of a db difference but unfortanately I can and it's how I perfect my vocal mixes with very precise automation that I can drag by .000 whatever of a db (eg in cubase).

I hope this is the answer....\/\/

Automation Curve Enhancements - New Smart Automation Node Entry correctly creates stepped automation curves for discrete value changes, New adjustable Bezier Curves between nodes, New editing of multiple nodes at once, New enhanced editing of line segments, New Automation Follows Clips Mode

Sure does sound promising. I have had frustrations with the value resolution on the automation curves myself. Sometims when you what to get something to sit just right in the mix, you can't adjust the values as precise as it should be. Dragging the curve jumps the values far more than you would like sometimes, so being able to drag the curve at a finer resolution, or being able to type in a specific value would be a nice feature.

[jplanet]

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

wow....90% of my plugins continue to process LOL...must know what u r using....

Tracktion's broswer the way i undderstand it IS going to have preview at project tempo, thats what support for acid loops is all about. I am sking it be added for non acidized files...

regardless, no multi processor, no point. That is number one feature, and to be honest, if T3 is released without full multicore support, it will be the ONLY host app on mac to not have it!!

I just have a bad feeling cause I thought it would be at the top of the announcement list, and something that would put alot of minds at ease...

Here ya go...


Misc. - Universal Binary for Mac Intel Support, Windows Vista RC1 Support, VST 2.4 Support including complete *.vstxml support, New Hover Edit of Clips, Improved Meter Response with improved scaling and range, Improved Input Routing view and operation combining previous old and new views, New mute individual clips, New editable Clip Length field for all clips, Divider between Controllers and Notes in Midi Editor can now be resized, Bottom Panel can now be resized, Zoom controls from GUI, New First Run Wizard, Misc. GUI improvements, Lots of new key commands, Many More…

Does ny of this directly imply that it will have dual core supprt? It doesn't say it, but is that implied by the Vista support or anything else?

[MasonAtom]

Everything sounds great, particularly:

This is easy now with the new Global Track. Tempo is now node based and you can do everything with tempo that you can with automation nodes/curves. Time Sig and Tempo Changes are events on the track independent of tempo.

Can't wait to be able to use that because most of the songs I write have different time changes and tempo ramps. Also excited that the tempo ramps are not going to be limited to linear.

But for me, the BIGGEST FEATURE would be true multiprocessor support! Please, please tell me that this version of Tracktion is going to able to run on a Dualie... I almost weep every time I load up Logic and see how efficient is in comparison to Tracktion on my dual G5. The new feature list makes Logic completely obsolete for me, but I would love for Tracktion to be more efficient on my system.

I'm starting to get nervous since this has been asked several times already and no definitive answer has been provided.

Mason

[MasonAtom]

Beno - will there be a way to export the timeline data from the Global track as a midi file? It really bothers me that you can't do it in T2. The workaround of making a dummy midi file never seems to work for me either.

Mason

[MasonAtom]

OH MAN! Just looked at the high res. screenshot - the new global and marker tracks look super sweet! This is exactly the type of simple, yet effective methodology that I have come to expect from Tracktion.

Folder tracks look AWESOME - this is going to make organizing my songs soooo much easier. Holy crap, I can't wait to get my hands on this version!

[wayover]

What about support for dual core cpu's? Without that, you can't even run half as many plugins in Tracktion as you can in alternatives like Cubase, Logic, Live. Without that, none of the new features matter, IMHO.

[rainydays]

I added a screenshot to the original post. You can see the editable collection clips on the folder track.
Ben

If that's the final GUI then I'll be a bit dissapointed

You did click the pic a second time to view the higher res image right?

Ben

Yes I did. It looks pretty unpolished to me. The browser really looks forced into the GUI.
The main problem I think is the lack of margins and padding on the UI elements. Space is a good tool for dividing regions and making the UI look less cluttered.
Also, I have a hard time understanding why the track labels aren't vertically centered and why they use different font sizes. Especially why the label "guitar 2b" has a larger font size than "guitar 2". I guess has to do with some "smart" resizing?

I'm actually very exited about the markers track though. That looks awesome!

[ObsoleteAcc99]

[DELETED]

[valley]

It wouldn't work at all on my loop library 'cos in most cases I keep the first kick of the next repeat.

just out of curiosity, why's that then?

Old skool hardware, and old skool working methods. If the sample is set to play to end, you can hear immediatedly if you have your loop tempo dead on cos there is no sound of double-kick (or if absolutely on, flanging) the next time the sample is triggered.

When working with old hardware, and loops that seldom are exactly the BPM they claim to be, that's pretty much the easiest way to be sure you've got it right.

[valley]

I should add, if T's loop librarian is all it seems, I'll probably go back and edit them all down to natural length though.

(edit : and sell my sampler)

[dextrus]

If the app has been multithreaded properly (UI in one thread, Core engine/Plugins in another), then that's half the battle won.. The other part on the mac side would have been to support the intel processors. You have to be careful in threading because they can be expensive, in terms of memory resources to store their state when transistion from thread to thread and the cpu in terms of the swithcing process (unloading/loading thread states) and synchronisation of resources that are shared between threads. If you have too many threads, then you spend more time switching between them then actually doing work you created them for in the first place. It's usually best for a given application to only use as many threads as there are cores/cpus in your system.