yes it is an incremental change - v1.7 really
good things:
midi controller mapping (yay)
quantize amount slider
input meters
thorough key command bindings
velocity in midi editor good
hi-rez mix option (why not?)
hiding side panels
almost good things:
The MIDI editor is improved but....
the MIDI nudge doesn't quite work: timecode fields are not updated and movements are quite course - snapping whether snapping is enabled or no. Suggestion - have midi nudge snap only when snnapping is enabled OR use alt-arrows for fine nugeing and control for course.
Also there needs to be a way of lassoing controller data (am I missing something?)
The best thing about T2 is that it preserves the great design and workflow of T1 !! Yes I want a full-featured MIDI editor and decent pitch shifting, but I want them only if they are implemented with the Jules' usual vision and clarity.
initial assessments
-
- KVRAF
- 1615 posts since 28 Mar, 2005
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
Yet, it's this very fact (that it's basically the same) that leads you to believe that it's only an incremental update. 
-
- KVRAF
- 3617 posts since 26 Sep, 2003 from Bradford - The Armpit of Britain
good point about lasooing/moving controller data - i've just been playing at nudging notes around and then trying to move controller data to match - isn't having it is it, or are we missing something obvious?
-
- KVRAF
- Topic Starter
- 1615 posts since 28 Mar, 2005
I didn't say that an incremental update is a bad thing!
I am happy with the update (excepting the color schemes which is the first unnecessary choice presented in the program) and will buy it.
I am looking forward to a proper MIDI editor in 2.1 though!
I am happy with the update (excepting the color schemes which is the first unnecessary choice presented in the program) and will buy it.
I am looking forward to a proper MIDI editor in 2.1 though!
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
Colour schemes aren't an unecessary choice. I find it very necessary to make that choice and pick a new scheme. 
I see what you mean about the controller data. I only use a keyboard that transmits nots, not other data. Strange one. Can't comment, as I don't really know much about this feature.
Even though I now see that you don't mean it as an insult, I STILL disagree that it's an incremental change, though. A lot of the 'subtle' changes are things that require huge overhauls, which warrants more than just an incremental increase in version.
I see what you mean about the controller data. I only use a keyboard that transmits nots, not other data. Strange one. Can't comment, as I don't really know much about this feature.
Even though I now see that you don't mean it as an insult, I STILL disagree that it's an incremental change, though. A lot of the 'subtle' changes are things that require huge overhauls, which warrants more than just an incremental increase in version.
-
- KVRAF
- 3617 posts since 26 Sep, 2003 from Bradford - The Armpit of Britain
The controller data thing isn't a biggie for most people probably - as the way teh automation works for vsti's is much better now. But if u use an outboard synth, or rewire reason say & create a nice part with perfectly timed filter sweeps (using tracktions midi to sequence it rather than reasons - in order to be able to use a control surface or keyboard) & then realise that just 1 or 2 notes need moving slightly u have a problem trying to move your controller data to match, it can be done by creative (& tedious use) of splitting clips & playing with the offset - but that is a ballache of a kludgey workaround. If u have reason etc. just examine it to see how it should be done - just select the area & move - simple as. In tracktion the selection tool & pencil tool perform virually the same task on midi cc data - ideally the selection tool would be better utilised selecting a range, so that on ecould then move/nudge it nito line with moved midi notes (imo).