Tracktion User Survey / Waveform 13.5 feature requests

[nowgad]

hi! pinning tracks, just like in excel. I'll go on the other side of my old idea

[Watchful]

Feature request: WHAT HAVE I DONE?

Please note that I am not asking for extended undo features. I just want a historical list of key-presses that have resulted in something happening due to keyboard shortcuts.

A fair number of help requests here have to do with users having pressed keys that resulted in unwanted actions and they didn't even know that it happened. For example, pressing the letter Y and turning on automation read. Suddenly, ghosts are messing with their song. For myself, I sometimes look down at the keyboard to type and only afterwards notice that I wasn't in a typed entry context and just... did a bunch of things.

Also, yes, this. This happens to me at least once a week.

[fedexnman]

I have a BUG no one else seems to have . When I close Waveform13 on Windows11 , if I try to re open it Waveform13 hangs and won't re open .
SOLVED or FIXED . After new 13.1.2 release . And uninstalling the old 13.0.44 .

[bungle]

I will need Automation Clips before I buy back in to a newer version of Waveform Pro.

[metamorphosis]

More bugs encountered:

* Severe (completely unacceptable) bug: when exporting many individual tracks using "Render Each Track to a Separate File", minute timing differences may be introduced at the start of each track. When exporting this means that two tracks, where each is L/R of a stereo pair, may develop cancellation or echoing as a result of the delay between the two signals, when re-paired in another application, or within another edit. This occurs even with no plugins in the mix. Please Fix.

* Working with jbridge, the jbridge'd plugins will scan in fine when running a manual scan from the settings menu,
however if waveform detects the new plugins on boot and tries to scan them then, it crashes.
Not sure whether this bug is specific to jbridge'd plugins (you can test with their demo), or vst 2.4 plugins in general.

* Exporting has the same bug as rendering tracks: if the Only Render Selected Tracks option is ticked, and those selected tracks don't output to Default but instead output to another track, no rendering takes place.

* Exporting outputs a brief burst of audio to the audio buffer after finishing the export.

* Exporting "forgets" if the "Only render selected tracks" option is ticked the next time you go to it, but remembers all other options.

* Currently the "panic" button lights up if the Run Audio Engine When Stopped option is unticked. Distracting and confusing. Clicking the panic button re-ticks the option, which is not helpful.


More pet peeves:

* Exporting and Rendering currently share a common remembered filepath string. This is problematic as they exist for different purposes. Exporting defaults to the Export folder, Rendering to the Renders folder. There's a reason for that. But if you change one, it changes the other.

* It would be appreciated if Exporting was back on the menu as it's own item, rather than a sub-item of File, simply because it gets used so often.

* Would be appreciated if Shift-E was restored to being the default keyboard shortcut to turn "Run Audio Engine When Stopped" on/off - currently it appears to have no keyboard shortcut by default.

* The automatic insertion of an audio/midi input to the track you click on feels distracting to me and I'm not sure how it could be useful. Recording is probably 1/10th of my work, if that - the rest is editing and mixing.

* I forgot to mention a long-standing gripe:
Please make clip waveforms localised to the project, not the edit, and store them in the project folder. I do quite a bit of comparing between mixes, and saving to a new edit before I make changes, and the fact is that the program is Quite Capable of transferring the clip waveforms to the new edit, because it doesn't re-render them as soon as you save a new edit. But having to re-render clip waveforms when you open up that new edit later on, can be tedious and time-consuming - not to mention unnecessary.
If for some technical reason you can't make the clip waveforms project-based rather than edit-based, at least copy them when you save a new edit rather than rendering from scratch the next time you open it.


I will add some appreciative notes for what I'm liking about this version, compared to some of the earlier versions which supported 32-bit plugins. Stability, speed of interface in terms of zooming in/out and scrolling, support for more than 4 plugins on the master channel, default support for master channel as it's own channel in the editor window, reduced memory usage, full colour editor, better support for larger numbers of clips.

But looking at this collection of bugs and small feature issues, I think all features should be tested more thoroughly and the work actually completed, before adding new features.

[dysjoint]

* Exporting has the same bug as rendering tracks: if the Only Render Selected Tracks option is ticked, and those selected tracks don't output to Default but instead output to another track, no rendering takes place.

I agree, older versions would bypass your set output routing and render the track in place. Currently rendering tracks or stems is a very tedious process of: change output to default. Render track. Change output back to where it should be.
Multiply that by 30 or more tracks and it gets old pretty fast. I wish that Waveform recognised that the track I've selected (and anything routed into that track, so the sum of all audio passing through the end of this selected track) is the audio I wish to be rendered.


A bug I have that no-one else has mentioned, and I haven't explored too much yet is: insert an audio clip. Shorten the clip from both ends to find an interesting section. (This can be seen in the properties panel as two markers showing the start and end points of the shortened clip within the full file) Then I hit the loop button and it now seems to forget this chosen window and loop from the start of the full file.
Workaround is render first, then loop, which isn't ideal.

[nowgad]

A bug I have that no-one else has mentioned, and I haven't explored too much yet is: insert an audio clip. Shorten the clip from both ends to find an interesting section. (This can be seen in the properties panel as two markers showing the start and end points of the shortened clip within the full file) Then I hit the loop button and it now seems to forget this chosen window and loop from the start of the full file.
Workaround is render first, then loop, which isn't ideal.

Yes it is. I described this error and provided a link to the video or inserted screenshots. Guys, when describing a bug, always write the environment: Win10, WF12.5

[Maarid]

guys, I just checked in version 13, everything works perfectly, I cut it down to where, and from there the cycle begins, with and without autotamp. Maybe I misunderstood what is not working for you? (I won't even put the 12th one, it directly annoys me grrrr)

[skipscada]

Request (maybe doable with a macro?) "Normalise each clip in track": Select several clips (or "all clips in track"), normalise each clip individually to a set level. Let's say you split a vocal track into individual phrases, one phrase per clip. The aim is to have all of them peak at the same level. This is useful as preparation for further adjustments. It's a bit of a hassle to normalise the clips one by one if you have 20 of them.

[metamorphosis]

I'll add the one feature I would genuinely use if it were present: A-weighted plugin before/after volume-matching.
ie. the ability to click on a plugin, and in it's info page (bottom of tracktion window) click something next to the "wet" volume slider to make it detect the average subjective volume difference after plugin processing while playing, and adjust the wet level to match the incoming signal.
This would make gain-staging trivial compared to how you have to do it now. And would make detecting when you're only making something Louder instead of Better, easier.
It would probably require the wet level to be able to go above 0db though, to match for plugins when they lower the subjective volume difference.
But it's one feature that (to the best of my knowledge) no other DAWs have - only some plugins, like FG-X.

[Kido]

Please make it possible to record midi from vst. It would be possible to record the result of arpeggiator's work into a midi clip.

[nowgad]

Please make it possible to record midi from vst. It would be possible to record the result of arpeggiator's work into a midi clip.

learn this tool https://trackbout.com/ripchord put it right after the arpeggiator

There are several ways to record midi clips using built-in tools:
1. Combine all the instruments after the arpeggiator into a rack, make a midi bypass of all plug-ins in the rack (red wire), and record with built-in tools. Now direct the signal to any Track (Route MIDI from track-> Track ...), click the record icon on that track, and click record. The entire midi signal will be recorded in a midi clip.
2. Put AUX Send after the midi instrument (Track 1), AUX Return on another track (Track 2). Turn on Route MIDI from track-> Track 2 on Track 3, turn on the recording icon on Track 3, turn on recording. Now you have the entire midi signal recorded as a clip on Track 3. It's faster to do it than to describe it.

[nowgad]

delete

[nowgad]

delete

[ndrw9138]

Thanks for the opportunity to give feedback, I missed it last year.

FRs:
- Each track having a built in channel strip with high/low cuts, eq, compression, gating applied at the beginning/end of current fx chain... available via actions panel.
- Option for automation write mode to record to separate automation lanes, instead of everything into the clip where it can't be seen.
- On/off note chance option in arpeggiator, for more random/generative MIDI.
- Pinning tracks, submixes, and folders to top/bottom of arranger, or left/right in mixer.
- 2 octave qwerty keyboard, (Z,S,X,D,C... for first octave, Q,2,W,3.... for second octave).
- More splitting options for audio like transient splitting, left/right splitting, mid-side splitting, available via sends to returns. After sending, the full signal is passed.
- Vertical master meter on left or right side (toggling visibility, similar to actions/browser panels).
- A convolution reverb plugin.
- Pitch detection for samples in the file browser.
- Probability for note on/off using midi clips (not just step clips).
- Option for mouse middle mouse button to grab and drag arranger canvas (horizontal and vertical scrolling).