New release, what do we want for the next?

[zOap]

OK, so now the number is 2.1.0.6

Some new and exciting features are in, like the Tranzport impl. I love it.

But what do we want for the next release?

I propose that we let the uber Voting machine himself, Rock, do another vote.

To kick the ball off, I'll propose OMF Import/export,
Mute/disable single notes and clips, key shortcuts for
Mute/Solo active track, and (mood killer) Aux Returns available as track inputs. And track selection follows edit movements...

[ceenda]

Line tool in CC data not limited to piano roll snap setting (is there any justification for it to be this way anyway?).
Ghost clips.
MIDI 1 Export.
Full screen MIDI editing.
Keyboard short-cut for "Triplets"

*ding ding* "next please!"

[djsubject]

relitive snap button, mute notes & clips (via short cut key)

Subz

[GaryG]

timestretch
ghost clips
clip based automation

same old, same old...

.g

[jplanet]

- More flexible freeze (allow mute/pan/volume)
- Tempo changes can be moved and grouped with clips
- Aftertouch support (if it can be done with a plugin, this is probably the easiest to quickly throw in)

[rpc9943]

sorry but what are ghost clips again?

RonC

[AD80]

Isnt this what the "most wanted features" thread was about?

[djsubject]

sorry but what are ghost clips again?

RonC

if you have say 10 copys of a clip spread out along the time line, if thay are ghosted then what ever you edit in one of them will happen to all 10 of them

Subz

[pethu]

I feel the boys have once more managed to pull off a good update without actually messing too much with the program core or Tracktion file formats. But they're getting closer to the inevitable...

So, things that have been mentioned in that respect already is an overhaul of the project structure, folder tracks or similar "edit management" features, changes to PDC -- and still hoping for my no. 1 request, aftertouch / *complete* MIDI support!

Unfortunately, I also predict a significantly higher risk of some of those updates producing more new bugs, and requiring insane amounts of testing...

[clueless]

ACID-style/quality of time/pitch manipulation, before ACID 6 starts to look too tempting...

[hefalump]

Maybe Tracktion<->controler communication?
What do we need control sourface mapping for if tracktion doesnt send any info to a controller ...

[chagzuki]

Clip based automation. The current system is really poor in certain ways: If you adjust tempo the automation doesn't stay locked to song position.

[Daniel78]

aftertouch/channel-pressure support

And umm... everything everyone else said...

I'd really like a more flexible freeze system too... but thats not essential to me.

[jplanet]

Clip based automation. The current system is really poor in certain ways: If you adjust tempo the automation doesn't stay locked to song position.

It seems like there would be fewer limitations if tempo was based on a tempo-track instead of floating above the timeline. If you could create a midi clip, set the tempo of it (can only do this with clips on the tempo track), then you could stretch or move it, and everything else on the timeline could follow.

There is something in T2 already that might allow for this. When you drop a MIDI file onto the timeline, the timeline changes to the tempo of that file. If only it could continue to follow it once you manipulate it...

[AD80]

Ok well I guess we're voting again so here's my votes

1) Track size management system. Aka folder-tracks or atleast lockable track sizes

2) Count-in in loop mode for the love of gosh

3) Ghost clips

With those three things I could take over the world.

Heres the other thread I was talking about with a few other votes....

http://www.kvraudio.com/forum/viewtopic.php?t=110052