So, Whats Next For T6.x.x

Discussion about: tracktion.com
RELATED
PRODUCTS

Post

Hi,

Edition window more flexible with drag clips edition in virgin tab.

Post

Ben di Arrows wrote:
jabe wrote: Plug-ins per clip and not just per track?
Just like you always could?
Darn, there's always something I miss...
[W10-64, T5/6/7/W8/9/10/11/12/13, 32(to W8)&64 all, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.

Post

VST3 presets would be nice!

Post

rich_h wrote:VST3 presets would be nice!
+100

plus support for subfolders for aupresets (and vstpresets)

Post

How about a fix for Slate Digitals Trigger 2. Sent in support tickets to both Tracktion and Slate Digital, months ago. Both say its the other companies issue. I know its a Tracktion 4 and later issue because Trigger 2 works on T3. Trigger 2 also works in PT10, PT11, Reaper and in Studio One 3.0 (both 32 and 64 bit versions of all listed). So come one guys !!!! Get it fixed !!!!

Post

BushmasterM4 wrote:How about a fix for Slate Digitals Trigger 2. Sent in support tickets to both Tracktion and Slate Digital, months ago. Both say its the other companies issue. I know its a Tracktion 4 and later issue because Trigger 2 works on T3. Trigger 2 also works in PT10, PT11, Reaper and in Studio One 3.0 (both 32 and 64 bit versions of all listed). So come one guys !!!! Get it fixed !!!!
Yeah, that's the trouble. Some follow the proper VST protocols and some don't. And some make allowances for slack programming standards and some don't. I know where my money would be if I was betting where the slack practice was. And it don't begin with T.
[W10-64, T5/6/7/W8/9/10/11/12/13, 32(to W8)&64 all, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.

Post

jabe wrote:
BushmasterM4 wrote:How about a fix for Slate Digitals Trigger 2. Sent in support tickets to both Tracktion and Slate Digital, months ago. Both say its the other companies issue. I know its a Tracktion 4 and later issue because Trigger 2 works on T3. Trigger 2 also works in PT10, PT11, Reaper and in Studio One 3.0 (both 32 and 64 bit versions of all listed). So come one guys !!!! Get it fixed !!!!
Yeah, that's the trouble. Some follow the proper VST protocols and some don't. And some make allowances for slack programming standards and some don't. I know where my money would be if I was betting where the slack practice was. And it don't begin with T.

Strange how Trigger 2 works in Tracktion 3 and not Tracktion 4,5, or 6. And it works in all the other DAW's I use. So to me its a Tracktion issue. And I'm not the only Tracktioneer here, that has the issue with Trigger 2 and the new versions of Tracktion. I love Tracktion and its my DAW of choice. And I always buy every new version. So keep a loyal customer happy, get it fixed... :)

Post

jabe wrote:
Ben di Arrows wrote:
jabe wrote: Plug-ins per clip and not just per track?
Just like you always could?
Darn, there's always something I miss...
just tails extending over clipborders are missing (delay, reverb).
that would make the feature complete.

Post

klangbastler wrote:
jabe wrote:
Ben di Arrows wrote:
jabe wrote: Plug-ins per clip and not just per track?
Just like you always could?
Darn, there's always something I miss...
just tails extending over clipborders are missing (delay, reverb).
that would make the feature complete.
Not sure that extending beyond clip borders would be possible except if you put a send on the clip and have the effect on a return track somewhere else in the track list.

Post

it depends on the audioengine i guess.
it probably would need an internal "upgrade".
and it must be possible, as daws like samplitde can do it.

there are also some scenarios, where plugin delaycompensation is not working correctly, when sends/aux busses are involved. back when i reported it (t5!), the answer was "limitations of the audioengine".
a new audioengine is in development, i was told.
so that's my hope for t7 now, including the "extend clipeffects over clipborder/-fade".

Post Reply

Return to “Tracktion”