- Add some Clips to the Launcher
- Open Sample/Clip Automation Editor for any Clip, click on eye icon, and select any automation parameter such as Volume or Pan
- Create a time selection in the Sample/Clip Automation Editor and leave it as is
- While time selection is active, Cut and Delete operation do not work in the Launcher, the entire Launcher is locked, all Launcher Clips affected
- After clearing the time selection in the Sample/Clip Automation Editor, Cut and Delete works again
Waveform 13.5 Ongoing Bugs
-
jurij.es.a.szakkor jurij.es.a.szakkor https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=53332
- KVRist
- 50 posts since 31 Dec, 2004
The Cut and Delete action does not work in Clip Launcher, if time selection is active in Automation Editor, I can reproduce it 100%:
-
- KVRist
- 125 posts since 26 Apr, 2021
Thanks for reporting these bugs, Tracktion TEAM is working hard to have all of those issues fixed in the next release, they already fixed the "only white canvas in some plugins" in version 13.5.22, but there's more work to do, due to changing and updating the code as the JUCE platform have an evolution upgrading and updating the platform.
Thanks for your patience and support!
Thanks for your patience and support!
-
jurij.es.a.szakkor jurij.es.a.szakkor https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=53332
- KVRist
- 50 posts since 31 Dec, 2004
The Multiplicative Automation Curve does not work properly for Bipolar (-/+) parameters - Ticket #74017:
The same automation results in correct automation curve and audio playback in Bitwig Studio 5.3:
WF Pro 13.5.21 - Windows 10 Pro
- Add a Clip to Arranger Track or Clip Launcher
- Open Sample/Clip Automation Editor, click on the eye icon, and select any bipolar automation parameter, such as Pan
- For easier visualization, Create an Absolute Curve with Square Wave (Hard Left-to-Right Panning)
- Switch to Multiplicative Curve and create a 0 to 100% Fade In/Transition in the editor
- The calculated target curve is wrong, it seems like it doesn't handle the negative range at all/properly
The same automation results in correct automation curve and audio playback in Bitwig Studio 5.3:
WF Pro 13.5.21 - Windows 10 Pro
You do not have the required permissions to view the files attached to this post.
-
jurij.es.a.szakkor jurij.es.a.szakkor https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=53332
- KVRist
- 50 posts since 31 Dec, 2004
Visualization of Bipolar (-/+) Automation Curves are displayed incorrectly in the Automation Curve editor - Ticket #74091:
The same automation results in correct visualization in Bitwig Studio 5.3:
WF Pro 13.5.21 - Windows 10 Pro
- Add a Clip to Arranger Track or Clip Launcher
- Open Sample/Clip Automation Editor, click on the eye icon, and select any bipolar automation parameter, such as Pan
- Create an Absolute Curve with a gradient from +0.75% to -0.75% in the editor
- Switch to Additive Curve and create a +/-10% Square Wave for easy visualization
- Although the calculated target curve is correct, the visualization is incorrect because it suggests that the envelope is Unipolar (the modulation range is from the bottom/0% to the top/100% of the window)
The same automation results in correct visualization in Bitwig Studio 5.3:
WF Pro 13.5.21 - Windows 10 Pro
You do not have the required permissions to view the files attached to this post.
-
jurij.es.a.szakkor jurij.es.a.szakkor https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=53332
- KVRist
- 50 posts since 31 Dec, 2004
The Track Automation Curve visualization only follows the Absolute Curve, ignoring Additive and Multiplicative Curves - Ticket #74155
WF Pro 13.5.21 - Windows 10 Pro
- Add a Clip to Arranger Track
- Open Clip Automation Editor, click on the eye icon, and select the Volume automation parameter as an example
- Create Absolute, Additive and Multiplicative Curves with Square Wave pattern for easy visualization and readout
- The Arranger Track Automation Curve visualization only follows the Clip Absolute Curve, ignoring the Additive and Multiplicative Curves (highlighted in red)
- Note that the numerical display on the track is correct, this number follows and displays the correctly calculated value of the Absolute, Relative and Multiplicative Curves (marked in green)
WF Pro 13.5.21 - Windows 10 Pro
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- Topic Starter
- 4890 posts since 3 Jan, 2003 from Vancouver
VST3 automatic CC->automation parameter assignment (Ticket #44040 from 2022!)
It requires a few specific conditions, and has a relatively high chance of being a plugin problem*. But I thought I would put it here anyways.
Some VST3 plugins from some vendors will respond to any MIDI CC data because of a mysterious link to their first reported automation parameter. This first came to my attention when it almost blew out my speakers. The first parameter of Voxengo's EBusLim limiter is the input threshold control. Setting it to -30 makes the output volume very loud. In a lot of other plugins with this problem it's a bypass control or on/off. With boz digital's El Clapo, the clapping stops.
Why is it likely to happen? Every time Waveform loops, it sends MIDI CC to make sure instrument plugins stop sustaining. Why is it unlikely to happen? Most plugins don't allow MIDI data to pass through them, so effect plugins are mostly safe.
Waveform's internal plugins pass MIDI through. Definitely 4OSC does.
Easy test: add 4OSC and the VST3 version of a Vexengo SPAN to a track. The first parameter is "meterin" (Metering) and by default it's DBFS. Change it to something else. Add a MIDI clip to the track and add some notes. Set the in/out around the clip and turn on loop mode. At the end of the first loop, the Metering in SPAN will change back to DBFS. There is no way I can find to de-couple this connection.
* Maybe it's a case of Waveform actually following a spec that nobody else does, like the one that showed up on Linux when plugins didn't explicitly state that they would be doing UI stuff and the default was no. Voxengo asserts that it's not their plugins. Meanwhile, this problem mysteriously went away in Auburn Sounds plugins after some updates.
It requires a few specific conditions, and has a relatively high chance of being a plugin problem*. But I thought I would put it here anyways.
Some VST3 plugins from some vendors will respond to any MIDI CC data because of a mysterious link to their first reported automation parameter. This first came to my attention when it almost blew out my speakers. The first parameter of Voxengo's EBusLim limiter is the input threshold control. Setting it to -30 makes the output volume very loud. In a lot of other plugins with this problem it's a bypass control or on/off. With boz digital's El Clapo, the clapping stops.
Why is it likely to happen? Every time Waveform loops, it sends MIDI CC to make sure instrument plugins stop sustaining. Why is it unlikely to happen? Most plugins don't allow MIDI data to pass through them, so effect plugins are mostly safe.
Waveform's internal plugins pass MIDI through. Definitely 4OSC does.
Easy test: add 4OSC and the VST3 version of a Vexengo SPAN to a track. The first parameter is "meterin" (Metering) and by default it's DBFS. Change it to something else. Add a MIDI clip to the track and add some notes. Set the in/out around the clip and turn on loop mode. At the end of the first loop, the Metering in SPAN will change back to DBFS. There is no way I can find to de-couple this connection.
* Maybe it's a case of Waveform actually following a spec that nobody else does, like the one that showed up on Linux when plugins didn't explicitly state that they would be doing UI stuff and the default was no. Voxengo asserts that it's not their plugins. Meanwhile, this problem mysteriously went away in Auburn Sounds plugins after some updates.
Surely there must be consensus by now...
-
jurij.es.a.szakkor jurij.es.a.szakkor https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=53332
- KVRist
- 50 posts since 31 Dec, 2004
The padlock state of the Automation/MIDI editor window is lost during docking/undocking - Ticket #74218:
WF Pro 13.5.21 - Windows 10 Pro
- Add Audio/MIDI Clips to Arrange Track
- Click on a Clip to open the editor window
- Select some Clips on the Arrange Track, then lock the padlock in the editor
- Click on the undock icon
- The padlock loses its state during the dock/undock operation (in both direction)
- The padlock loses its state in both the Audio/Automation and MIDI editors
- For Audio Clips, incorrect text appears in the info bar: "Dock or undock the MIDI editor"
WF Pro 13.5.21 - Windows 10 Pro
You do not have the required permissions to view the files attached to this post.
-
jurij.es.a.szakkor jurij.es.a.szakkor https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=53332
- KVRist
- 50 posts since 31 Dec, 2004
When Docking/Undocking the Automation/Audio Editor, the editor loses context and switches to MIDI - Ticket #74219:
Note that the same procedure works well for MIDI Clip:
WF Pro 13.5.21 - Windows 10 Pro
- Add an Audio Clip to the Arranger Timeline
- Click on the Audio Clip to open it in the Editor
- Press ESC to remove the selection in the Arranger Timeline
- Dock/Undock the Editor Window
- The Audio context is lost, the editor switches to MIDI
- The problem is bidirectional, occur in both direction (Docking/Undocking)
Note that the same procedure works well for MIDI Clip:
WF Pro 13.5.21 - Windows 10 Pro
You do not have the required permissions to view the files attached to this post.