Tracktion User Survey / Waveform 13.5 feature requests

[Peter Widdicombe]

Option (or default?) to stop playback when the last loop or last clip has been seen. Don't bother making it "smart" and look for actual content in clips or whether clips are muted; but when you reach the end (and you're not recording), then stop playback - rather than taking us up to bar 1000 or 2000 if you happen to leave the room.

Could also have an "end of viable play" option with options STOP, STOP and RETURN, or REPEAT which I might like if reviewing piece and making notes.

[Watchful]

I like this idea a lot. It can be a stop in the marker menu. I can see a lot of uses for this when incorporating projects into other media, too.

[Teksonik]

A very minor issue but it would ne nice to be able to delete all the factory project templates. I don't need "House of Worship, EDM, etc".

I've tried deleting the folder but every time Waveform is loaded it just writes them back again.

It would leave room for more of my own templates. Again not a big deal at all but something I would change if I had a magic wand.

[talby]

Option (or default?) to stop playback when the last loop or last clip has been seen. Don't bother making it "smart" and look for actual content in clips or whether clips are muted; but when you reach the end (and you're not recording), then stop playback - rather than taking us up to bar 1000 or 2000 if you happen to leave the room.

Could also have an "end of viable play" option with options STOP, STOP and RETURN, or REPEAT which I might like if reviewing piece and making notes.

I strongly support this feature request. Currently no end of playback exists and this frequently annoys when listening to an edit/project. This is really needed and shouldn't be a big thing to implement. Like the variable to position start marker, which recently was kindly implemented, there should also be a variable to position end marker, and this end marker should by default be placed at the end of the last of the content containing clips, at least for playback. It could be ignored for recording.

[Watchful]

Well, while we're at it, a 0 bar would be overdue.

1. Partial measure intros are common to pretty much all genres, with bar 1 occurring on the new beat.

2. Rendered audio files sometimes get clipped if they begin at bar 1, beat 1.

[ndrw9138]

An elaboration of my channel strip idea. Not a minor feature, just wanted to share. Inspired by nowgad's plugin groups idea.

ChannelStrip_Clean.png

ChannelStrip_Annotations.png

[nowgad]

An elaboration of my channel strip idea. Not a minor feature, just wanted to share. Inspired by nowgad's plugin groups idea.

Yes, that's interesting too. But following Waveform logic, it should be on the right side, just like my idea with equalizers. It should be possible to expose the controls of all plugins in the chain for a track. Great idea. It will be more convenient than what we have now. In Ableton it is in horizontal form, in Waveform it is in vertical form.

[ndrw9138]

Yes, that's interesting too. But following Waveform logic, it should be on the right side, just like my idea with equalizers. It should be possible to expose the controls of all plugins in the chain for a track. Great idea. It will be more convenient than what we have now. In Ableton it is in horizontal form, in Waveform it is in vertical form.

The console/channel strip would be a fixed number of plugins pre-embedded into each track, not an alternative for editing every plugin in the fx chain. Similar to a real mixing console. It would be meant as a quick and convenient way to process whats before or after user added plugins. It could be accessed with a button as such:

WF_Console.png

Adding console emulation pre-amps may be something interesting as well, and could be sold as expansions for non pro users.

For vertical processing, the action pane could be used, however showing 3rd party plugins with a large number of parameters would be tricky. Certain parameters would need be specified to keep the list smaller. Allowing a 3rd party's plugin parameters to be favorited so they may be exposed to the actions pane could allow this. Similar to the built-in compressor plugin. Then pinning that action so the said plugins parameters are available as an action when clicking a track into focus, not just clicking on the plugin.

[ForrestH]

FR: numbering and/or bookmarks for the pattern generator's arpeggio patterns.

[Shadowdarknes9]

An idea would be to line the Midi editor notes up with the BPM.
FL Studio keeps it lined up on the vertical lines.
But it seems every time i switch the BPM in Waveform 13 it goes off those lines.
I do not wish to have to snap them all back and possibly reshift my note timings.
God this triggers my ocd so damn much.

[ndrw9138]

Updated my console/channel strip response, three posts up.

[metamorphosis]

Don't know if there's currently a way to do this, but for intricate editing of long audio, some kind of functionality which allows the user to select *all clips after this clip* but not all clips in track, would save craploads of time.
Being able to do this for multiple tracks would be even better (ie. select a clip in each track, then press the hotkey combo to select all clips after those clips in those tracks).

[Peter Widdicombe]

For Shadowdarknes9; do you want notes in the MIDI editor to line up with the notes, or are you using seconds as the timebase within a musical bar? You can work with either; but it probably doesn't work if you keep changing it.

Also, if you highlight the clip in question, there is an option to remap on tempo change which you probably want. Just changing BPM using bars as time reference should NOT move notes around relative to it's note timing. Unless you have note samples that have a little dead space at the start of notes??

Now, if you are changing tempo and have a mix of MIDI and audio, that can be problematic and there are choices in audio clips for stretching audio. But a MIDI note at, say, exactly 3rd beat in a bar will remain there, even if BPM changes.

[dysjoint]

.....Good points....

Also Settings/General/Editing/Tempo change remapping has your default options if you don't want to make all your changes at clip level.

[vitocorleone123]

I missed the survey.

One thing needed is something like ASIO Guard or Dropout Protection. It's the one thing preventing me from returning to using Waveform (though I did just upgrade to support the company as I always have since v3).

I can set my ASIO buffer to 32 @ 48khz for a very very low latency on my hardware synths (< 2.5ms) in Studio One, but if I try to same in Waveform it's a crackle-fest until I raise it to 128, at which point the latency, while not bad, is annoyingly higher when playing the instruments.

Waveform just can't compete with Studio One in my use case. It's a complete blocker.

A plugin akin to Studio One's Pipeline would also be welcomed but isn't required.