T6 feature requests and bugs

[TSC]

Hey guys - starting a new sticky for T6 ideas etc - go at it

[aMUSEd]

1) Proper preset management for all formats, currently you only properly support fxp/b which is the format VST2 uses. You kindof support aupresets for AU plugins, but since aupresets are always separate files (no banks) they are usually organised by subfolders, and those you don't support so we end up with a useless long list. And you don't support VST3 preset format at all (vstpresets). Logically the best way to support loading and managing presets is via the browser, as there it makes sense for presets to be organised in folders and subfolders, get rid of the current bank loader.

2) Better ways to organise plugins in the drag menu, none of the current methods are optimal. Ideally we should be able to customise the menu using tags to sort plugins.

3) Add more options for creating space in the gui by making it possible to remove the strip above the tabs and space that is unused when you remove the ios.

4) Make it possible to have the browser on the right (which makes more sense since you drag plugins to the right side, not the left).

5) Auto add automation lanes for tweaked params.

[Stonecutter]

Possible "Game Changers" (for me at least)...

1. Adaptive Snapping. Another snapping option that doesn't snap to the grid, but to everything else that someone might want to snap to. Basically it would snap to clips, the in/out marker, and the cursor.

2. Keyboard Shortcut expansion. Possible keyboard shortcuts for every parameter available in the properties menu. For example, "hide automation curves," "apply edge fades," "move selected clip earlier to meet end of previous clip," etc. All those options that don't currently have keyboard shortcut possibilities. Then like to see some general expansion, for example: "Scroll through active automation parameters for selected track." "Jump to Previous/Next marker."

3. Markers. See them as flags with their names seen (fully displayed when there is room) when the marker track is closed. I like to label sections (verse, chorus, etc.) but I don't like to have the marker track open. Setting keyboard numbers as key commands to jump to markers 1-9 would be cool also (edit: guess you can do this, thanks phledo)

Smaller Stuff ...

4. Pushing the "stop playing" key command twice would return the cursor to where it started.

5. Track Grouping

6. Aborting and "delete source file" sends files to trash/recycle bin.

Thanks!

[phledo]

Possible "Game Changers" (for me at least)...
Setting keyboard numbers as key commands to jump to markers 1-9 would be cool also.

You can do that already?
Place the play cursor where you want to set the marker. Hit a number key. Now look to the left of the cpu meter. A number pop up appears with a red background. Hit the enter key to set the marker.
Now repeat with the other keys (0 - 999)
If a marker is set already the background of the number pop up changes to green.
You can now jump between the markers by hitting a number followed by the enter or return key.

Cheers

[gigazaga]

Some great ideas here. This might actually be the first T7 feature request thread.

[gigazaga]

1. Adaptive Snapping. Another snapping option that doesn't snap to the grid, but to everything else that someone might want to snap to. Basically it would snap to clips, the in/out marker, and the cursor.

This partially exists. You can snap clips to other clips using a keyboard modifier. Turn snap off, then drag a clip while holding Alt. The Alt modifier makes the clips snap to other clips even when Snap is turned off.

I have been using this when editing voice over in Tracktion. It doesn't snap to the cursor or to the markers, but it does help when you want to get clips lined up end to end.

I would still like to have a way to toggle "Snap clips to neighbors" that is independent from snap-to- grid.

[gigazaga]

5. Track Grouping

Could you explain how you would use this. Do you mean so you can edit clips that are on multiple tracks as a group?

Right now, folder tracks allow you to do that.

[whyterabbyt]

1. Arbitrary per-track grid divisions, changeable on the fly

2. Per-clip effects and automation.

3. Automation 'metacontrols' (ie 1-to-many) 'generators' (eg LFO) and 'modifiers' (eg scale).

4. Full mapping of all context-dependent button operations to the right-click menu

5. Soundminer tag support

[gigazaga]

2) Better ways to organise plugins in the drag menu, none of the current methods are optimal. Ideally we should be able to customise the menu using tags to sort plugins.

FWIW you can tag them in the browser Search tab with a right-click. It is a little tedious because you must set them do them one by one.

The browser view would be much more useful, if the list of tags only included tags for the selected search filter. I mean if you set search to "Plugins: only, it would only show the tags for plugins.

[aMUSEd]

2) Better ways to organise plugins in the drag menu, none of the current methods are optimal. Ideally we should be able to customise the menu using tags to sort plugins.

FWIW you can tag them in the browser Search tab with a right-click. It is a little tedious because you must set them do them one by one.

The browser view would be much more useful, if the list of tags only included tags for the selected search filter. I mean if you set search to "Plugins: only, it would only show the tags for plugins.

Yes I'm well aware of that and use it a lot, I have all my plugins tagged that way already, but if the drag drop insert plugin method is going to stay it would help if some of that tagging could be used to organise the tree menu too, organising plugins by type, location or manufacturer isn't entirely effective.

[gigazaga]

Yes I'm well aware of that and use it a lot, I have all my plugins tagged that way already, but if the drag drop insert plugin method is going to stay it would help if some of that tagging could be used to organise the tree menu too, organising plugins by type, location or manufacturer isn't entirely effective.

Right, I agree.

[gigazaga]

2. Per-clip effects and automation.

Per-clip effects are already there. Just drag the plugin to the clip. You can then automate the plugin the normal way.

[whyterabbyt]

2. Per-clip effects and automation.

Per-clip effects are already there. Just drag the plugin to the clip. You can then automate the plugin the normal way.

Doh! Of course there are. Badly phrased, really should be 'per-clip automation'
Unless Im wrong; current automation for per-clip effects isnt part of the clip, though is it?

[aMUSEd]

Yes I'm well aware of that and use it a lot, I have all my plugins tagged that way already, but if the drag drop insert plugin method is going to stay it would help if some of that tagging could be used to organise the tree menu too, organising plugins by type, location or manufacturer isn't entirely effective.

Right, I agree.

I would do it this way. Generally when I tag a plugin I have 3 levels of definition, so for example it might be 'Effect, Reverb, Spring'. if I have a lot by a particular company I also put that. Obviously you can't have them all applied to a linear tree at once but what you can do is tell it to group plugins based on first, second or third tag, or combinations of. So for example "effect" would probably be too broad so I would go for the 2nd level there.

[aMUSEd]

This is one bug that has been present for too long already

http://www.kvraudio.com/forum/viewtopic ... e#p5991495