FR: it would be great to have a possibility to lock clips on the timeline. so you don't have to worry to screw things up after editing.
there could be options to be set, what clip-lock includes like: moving, borders, fades, ...
but timeline-lock seems the most important to me.
it could be a little locksymbol on the cliphandlebar.
best,
mathias
T5 bugs + FRs
-
- KVRist
- 473 posts since 1 Feb, 2006
-
- KVRian
- 755 posts since 4 Jun, 2004
+1
Also lock track, edit, whatever. I especially would like to see this for edit clips. When they're unlocked they automatically adapt to the length of the original edit.
And the locksymbol is already there (although used to pin the interfaces).
Also lock track, edit, whatever. I especially would like to see this for edit clips. When they're unlocked they automatically adapt to the length of the original edit.
And the locksymbol is already there (although used to pin the interfaces).
-
- KVRist
- 473 posts since 1 Feb, 2006
as for editclips:
i was imagining an option to disconnect an editclip from the source-edit, so it is no longer updated, when changing the source-edit.
i can see a few situations, where this could be useful. the moment you connect it again, it will be updated again. when you never connect it again, it is like a render export of the source-edit.
i was imagining an option to disconnect an editclip from the source-edit, so it is no longer updated, when changing the source-edit.
i can see a few situations, where this could be useful. the moment you connect it again, it will be updated again. when you never connect it again, it is like a render export of the source-edit.
-
- KVRAF
- 4056 posts since 8 Jan, 2005 from Hamilton, New Zealand
Nitpicks and congratulations:
The bad:
- 4-pixel gap on right of vertical slider - common mistake in many applications, but didn't occur in prev versions. Basically you can't slam the mouse to the right and expect to grab the vertical slider, that'll only happen if you precisely move the mouse about 4 pixels inwards. Under windows.
- double-clicking vertical slider too easy to do, not useful function - too easy to accidentally 'scrunch' the entire edit view by doing this, and it's not a useful function. More commonly you multi-click the empty slider space to move the slider along. This kind of f**ks with that.
- folder tracks - if you've got a boner to make everything look just like OSX, I suppose this is the way to go - but in pragmatic terms, 4mm whitespace is not a great way to differentiate non-folder tracks from folder tracks, and in terms of subfolders it gets incomprehensible real quick. tree-view was the way to go.
- colour schemes - cannot come fast enough. Default scheme not bad, but glaring on the wrong monitor.
- display often slow to update when scrolling compared to t4/t3
- vertical scrolling while mouseover plugin panel too slow - should be same speed as when mouseover vertical slider. Having it that slow serves no purpose.
- vst icons in filter tree - possibly useful to those with multiple plugin formats but not sure how - adds visual noise/clutter for normal users.
the good:
volume/pan - great design, gets around the old issues I noted long ago.
new 'flat + rounded' look & general presentation - quite like it
new pin & close icons - much more self-explanitory
new project menu - good, more organised
panic button and cpu usage windows - great tools
filter 'stacking' layout - very good solution to the old problem
generally the interface is clearer and the resizing algorithm seems to make better results than in t4
The bad:
- 4-pixel gap on right of vertical slider - common mistake in many applications, but didn't occur in prev versions. Basically you can't slam the mouse to the right and expect to grab the vertical slider, that'll only happen if you precisely move the mouse about 4 pixels inwards. Under windows.
- double-clicking vertical slider too easy to do, not useful function - too easy to accidentally 'scrunch' the entire edit view by doing this, and it's not a useful function. More commonly you multi-click the empty slider space to move the slider along. This kind of f**ks with that.
- folder tracks - if you've got a boner to make everything look just like OSX, I suppose this is the way to go - but in pragmatic terms, 4mm whitespace is not a great way to differentiate non-folder tracks from folder tracks, and in terms of subfolders it gets incomprehensible real quick. tree-view was the way to go.
- colour schemes - cannot come fast enough. Default scheme not bad, but glaring on the wrong monitor.
- display often slow to update when scrolling compared to t4/t3
- vertical scrolling while mouseover plugin panel too slow - should be same speed as when mouseover vertical slider. Having it that slow serves no purpose.
- vst icons in filter tree - possibly useful to those with multiple plugin formats but not sure how - adds visual noise/clutter for normal users.
the good:
volume/pan - great design, gets around the old issues I noted long ago.
new 'flat + rounded' look & general presentation - quite like it
new pin & close icons - much more self-explanitory
new project menu - good, more organised
panic button and cpu usage windows - great tools
filter 'stacking' layout - very good solution to the old problem
generally the interface is clearer and the resizing algorithm seems to make better results than in t4
I make music: progressive-acoustic | electronica/game-soundtrack work | progressive alt-metal
Win 10/11 Simplifier | Also, Specialized C++ containers
Win 10/11 Simplifier | Also, Specialized C++ containers
-
- KVRAF
- 37544 posts since 14 Sep, 2002 from In teh net
New bug - Load Halionsonic 2 VST3 - T5 go poof!
-
- KVRist
- 77 posts since 9 Oct, 2002 from UK
Likewise with HALion 5.aMUSEd wrote:New bug - Load Halionsonic 2 VST3 - T5 go poof!
-
- KVRAF
- 37544 posts since 14 Sep, 2002 from In teh net
Looks like there are lots of kinks to workout in the VST3 support
-
- KVRian
- 755 posts since 4 Jun, 2004
How about: 'lock tempo and time signature to clip'. So you can move them along the timeline.klangbastler wrote:lock clips on the timeline
-
- KVRist
- 35 posts since 23 Nov, 2011 from Ottawa, Ontario, Canada
It's all nice to say plugins crash, but a log would help trying to figure out the big question; why does it go poof? Please get in touch with support for things like this - it would help a tad more; support@tracktionsoftware.com.aMUSEd wrote:New bug - Load Halionsonic 2 VST3 - T5 go poof!
Also, if you're a C++ programmer, feel free to help out and contribute to JUCE; the library which contains the hosting code.
-
- KVRAF
- 37544 posts since 14 Sep, 2002 from In teh net
If there was a log of this specific instance I would send it but the only log seems to be cumulative so is huge and I have no idea where this crash can be found in it. Would be better if there was a dated/timestamped log for each crash
-
- KVRian
- 755 posts since 4 Jun, 2004
Well, it's a chronological log with timecode. The last event is also the last in the log. You could just copy the relevant lines in a text file and send this.
-
- KVRer
- 17 posts since 16 Mar, 2013
I've got a bug with automation. I've opened a project in t5, created originally in t4. One track (midi, Kontact 4 drums) with volume automation is not behaving correctly. The volume dips down and then back up several bars earlier than the automation points are telling it to. If I disable automation playback, the track plays through fine at fixed volume.
Mid-2010 MacBook Pro, i7, 8gb ram, Mavericks
-Andrew
Mid-2010 MacBook Pro, i7, 8gb ram, Mavericks
-Andrew
-
- KVRer
- 13 posts since 17 Sep, 2003 from London
On the topic of bugs, are Visual Studio crash dumps of any use to the Devs? I can generate them easily - they zip up to about 40 Mb if there's somewhere to upload them.
-
- KVRAF
- 2417 posts since 17 Jun, 2003
Why don't you just mail the devs the log they asked you to mail them, instead of editing it, or telling them how they should do their logs? I'm not really buying it's so huge you can't email it.
"my gosh it's a friggin hardware"