New beta 13.3.11 available
-
- KVRer
- 20 posts since 20 May, 2004 from Zzz
Waveform ChangeList
13.3.11
- Shortcuts: Made the "Expand/collapse folder track" shortcut also work with audio tracks to show/hide automation tracks
- Direct2D: Improved the performance of the Direct2D renderer on Windows in certain situations
13.3.10
- Rendering: Fixed a rare crash that could occur if "Render Automatically" is enabled and options are changed quickly
13.3.9
- Rendering: Fixed a rare crash that could occur if "Render Automatically" is enabled and options are changed quickly
13.3.8
- UI: Optimised drawing of EQ displays to prevent slowdowns when the editor is open
13.3.7
- Video: Remove legacy video modes (jadeo & juce)
- MIDI: Show sharps or flats correctly on the MIDI keyboard when fold mode enabled
- Quick Actions: Fixed the colours of the quick action buttons not reflecting the colour scheme
- Edit clips: Fixed EditClips not correctly generating their source Edit's when "Use proxy file" is disabled for the clip
13.3.11
- Shortcuts: Made the "Expand/collapse folder track" shortcut also work with audio tracks to show/hide automation tracks
- Direct2D: Improved the performance of the Direct2D renderer on Windows in certain situations
13.3.10
- Rendering: Fixed a rare crash that could occur if "Render Automatically" is enabled and options are changed quickly
13.3.9
- Rendering: Fixed a rare crash that could occur if "Render Automatically" is enabled and options are changed quickly
13.3.8
- UI: Optimised drawing of EQ displays to prevent slowdowns when the editor is open
13.3.7
- Video: Remove legacy video modes (jadeo & juce)
- MIDI: Show sharps or flats correctly on the MIDI keyboard when fold mode enabled
- Quick Actions: Fixed the colours of the quick action buttons not reflecting the colour scheme
- Edit clips: Fixed EditClips not correctly generating their source Edit's when "Use proxy file" is disabled for the clip
- KVRist
- 125 posts since 26 Apr, 2021
Great success! I'm testing WF 13.3.11 on Ubuntu 22.04 lts with ALSA only and it's working without major issues, the only issue is that the "Edit with external editor" feature is not present since the early versions also the "Launch this wave in its default application" is also broken and is unusable, third party VST-3 plugins opens sub menu hidden in the background so I need to move the plugin aside to see the option. I hope one day Waveform could work on Linux the same as in Windows/Mac.Seastream wrote: Tue Jan 28, 2025 7:54 pm Waveform ChangeList
13.3.11
- Shortcuts: Made the "Expand/collapse folder track" shortcut also work with audio tracks to show/hide automation tracks
- Direct2D: Improved the performance of the Direct2D renderer on Windows in certain situations
13.3.10
- Rendering: Fixed a rare crash that could occur if "Render Automatically" is enabled and options are changed quickly
13.3.9
- Rendering: Fixed a rare crash that could occur if "Render Automatically" is enabled and options are changed quickly
13.3.8
- UI: Optimised drawing of EQ displays to prevent slowdowns when the editor is open
13.3.7
- Video: Remove legacy video modes (jadeo & juce)
- MIDI: Show sharps or flats correctly on the MIDI keyboard when fold mode enabled
- Quick Actions: Fixed the colours of the quick action buttons not reflecting the colour scheme
- Edit clips: Fixed EditClips not correctly generating their source Edit's when "Use proxy file" is disabled for the clip
-
Peter Widdicombe Peter Widdicombe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=336849
- KVRian
- 1205 posts since 29 Aug, 2014
Version 13.2.0 worked under Windows 8.1, but 13.3.6 and 13.3.11 both install, but fail even before the start banner, with a
"The procedure entry point GetSystemMetricsForDpi could not be located in the dynamic link library c:\program files\tracktion\waveform 13\waveform13.exe". Is there a new Juce .dll assumed that needs to be manually installed?
"The procedure entry point GetSystemMetricsForDpi could not be located in the dynamic link library c:\program files\tracktion\waveform 13\waveform13.exe". Is there a new Juce .dll assumed that needs to be manually installed?
Waveform 13; Win10 desktop/8 Gig; Win11 Laptop; MPK261; VFX+disfunctional ESQ-1
-
- KVRist
- 372 posts since 18 Nov, 2023
Maybe the cause is partly a Linux configuration mismatch and not only a Waveform issue?cupcakemusic wrote: Wed Jan 29, 2025 3:05 am (...) the only issue is that the "Edit with external editor" feature is not present since the early versions also the "Launch this wave in its default application" is also broken and is unusable
(...).
As asked for it a week ago in another thread (viewtopic.php?p=9030374#p9030374), could you clarify to us how your plain Linux behaves, what happens if you try to open a WAV file by double-clicking on the WAV file entry as listed in your Desktop Environment's file browser, or alike procedure to request opening a WAV file with the regarding MIME type assigned app, without Waveform being involved? It should be assured that the xdg-specs are set fine (https://specifications.freedesktop.org/ ... ec/latest/).
Classical guitar --> Line Audio CM4 @ SSL12 --> KDE-Plasma @ Debian-Linux --> Waveform PRO 13.5
- KVRAF
- 4888 posts since 3 Jan, 2003 from Vancouver
It'd sure be nice if the Track Presets I made would show up somewhere, preferably when I select the Tracks category. I'd be willing to accept the Presets category.
Surely there must be consensus by now...
- KVRist
- 125 posts since 26 Apr, 2021
This is the error that WF13 reproduces running by terminal:talby wrote: Wed Jan 29, 2025 10:43 amMaybe the cause is partly a Linux configuration mismatch and not only a Waveform issue?cupcakemusic wrote: Wed Jan 29, 2025 3:05 am (...) the only issue is that the "Edit with external editor" feature is not present since the early versions also the "Launch this wave in its default application" is also broken and is unusable
(...).
As asked for it a week ago in another thread (viewtopic.php?p=9030374#p9030374), could you clarify to us how your plain Linux behaves, what happens if you try to open a WAV file by double-clicking on the WAV file entry as listed in your Desktop Environment's file browser, or alike procedure to request opening a WAV file with the regarding MIME type assigned app, without Waveform being involved? It should be assured that the xdg-specs are set fine (https://specifications.freedesktop.org/ ... ec/latest/).
/bin/sh: 1: /mnt/Data/Waveform Projects/My Rock/Rendered/My Rock Edit 1 Render 2.wav: Exec format error
-
- KVRist
- 372 posts since 18 Nov, 2023
Tested today for WF-PRO 13.3.11 in KDE(X11)@Debian12 to work fine:
Edit Audio File - Basic editing operations...
This applies the chosen action correctly.
Edit Audio File - Launch this wave file in its default application...
This opens the default application as configured in KDE/Linux for the XDG MIME type handling of WAV file without problems, there changes are applied and saved to the WAV file and closing that app returns to WF, in WF the changes are found to have been applied to the audio clip (to the file having initially been imported as a copy to the project and carrying the audio of the clip, and subsequently having been edited externally).
Although not being a friend of finding other characters than ASCII letters or numbers or underscore in a file name, I tested for you that both procedures also work fine when exchanging all underscores in my file name to spaces. I did not test to introduce spaces into the directory path, though. However, your error message does not state that the file wouldn't have been found, so it anyway does not look like a problem of path and file name resolution.
Please, what is the output of the following command? Note that your /path/filename has to be placed in quotes ( ' ' ) because of the spaces present in your particular /path/filename.
Edit Audio File - Basic editing operations...
This applies the chosen action correctly.
Edit Audio File - Launch this wave file in its default application...
This opens the default application as configured in KDE/Linux for the XDG MIME type handling of WAV file without problems, there changes are applied and saved to the WAV file and closing that app returns to WF, in WF the changes are found to have been applied to the audio clip (to the file having initially been imported as a copy to the project and carrying the audio of the clip, and subsequently having been edited externally).
Although not being a friend of finding other characters than ASCII letters or numbers or underscore in a file name, I tested for you that both procedures also work fine when exchanging all underscores in my file name to spaces. I did not test to introduce spaces into the directory path, though. However, your error message does not state that the file wouldn't have been found, so it anyway does not look like a problem of path and file name resolution.
Please, what is the output of the following command? Note that your /path/filename has to be placed in quotes ( ' ' ) because of the spaces present in your particular /path/filename.
Code: Select all
xdg-mime query default $(mimetype -M -b '/path/filename')Classical guitar --> Line Audio CM4 @ SSL12 --> KDE-Plasma @ Debian-Linux --> Waveform PRO 13.5
- KVRist
- 125 posts since 26 Apr, 2021
Thanks for the advice, The problem was a permission issue because my projects are in a secondary SSD and the "Create and Edit Files" permission was only available to root owner, I fix the issue with "cd ./disk1" and "sudo chown -v $USER /mnt/disk1" also backed up the disk, reformatted as a local disk then it has my user permissions.talby wrote: Wed Jan 29, 2025 10:07 pm Tested today for WF-PRO 13.3.11 in KDE(X11)@Debian12 to work fine:
Edit Audio File - Basic editing operations...
This applies the chosen action correctly.
Edit Audio File - Launch this wave file in its default application...
This opens the default application as configured in KDE/Linux for the XDG MIME type handling of WAV file without problems, there changes are applied and saved to the WAV file and closing that app returns to WF, in WF the changes are found to have been applied to the audio clip (to the file having initially been imported as a copy to the project and carrying the audio of the clip, and subsequently having been edited externally).
Although not being a friend of finding other characters than ASCII letters or numbers or underscore in a file name, I tested for you that both procedures also work fine when exchanging all underscores in my file name to spaces. I did not test to introduce spaces into the directory path, though. However, your error message does not state that the file wouldn't have been found, so it anyway does not look like a problem of path and file name resolution.
Please, what is the output of the following command? Note that your /path/filename has to be placed in quotes ( ' ' ) because of the spaces present in your particular /path/filename.Code: Select all
xdg-mime query default $(mimetype -M -b '/path/filename')
However the "edit with external wave editor" is not available the same as is in Windows/Mac, It have the keyboard shortcut but doesn't have the option to choose the external wave editor as in Windows/Mac, it looks like the they coded linux version different in that option.
- KVRist
- 82 posts since 28 Nov, 2023
that's odd... seems to be that the beta versions break backwards compatibility with Windows 8.Peter Widdicombe wrote: Wed Jan 29, 2025 4:09 am Version 13.2.0 worked under Windows 8.1, but 13.3.6 and 13.3.11 both install, but fail even before the start banner, with a
"The procedure entry point GetSystemMetricsForDpi could not be located in the dynamic link library c:\program files\tracktion\waveform 13\waveform13.exe". Is there a new Juce .dll assumed that needs to be manually installed?
Ryzen 5 3600 | 32GB | GPU RX 590 | Lewitt Connect 6 + LCT440 Vida | Ubuntu 24.04 LTS / Windows 11 | Waveform 13 PRO | Bitwig 5
-
Peter Widdicombe Peter Widdicombe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=336849
- KVRian
- 1205 posts since 29 Aug, 2014
I'm suspecting that new code with enhanced scaling of plugins and the GUI in general is enquiring into the OS to handle various hi-res monitors; but forgetting some environments may not have those OS hooks in place.
I have created a problem request for this.
I have created a problem request for this.
Waveform 13; Win10 desktop/8 Gig; Win11 Laptop; MPK261; VFX+disfunctional ESQ-1
-
- KVRist
- 372 posts since 18 Nov, 2023
Good to hear that you got it sorted out!cupcakemusic wrote: Thu Jan 30, 2025 12:40 am However the "edit with external wave editor" is not available the same as is in Windows/Mac, It have the keyboard shortcut but doesn't have the option to choose the external wave editor as in Windows/Mac, it looks like the they coded linux version different in that option.
Yes, you are right. The Linux version cannot configure the wished to be used external editor application in WF like it is possible in Windows, but can only call the app which in the Linux system is configured to be the default app for opening WAV files. Nevertheless, if you configure this 'mime type : app assignment' for WAV files in your Linux system for your editor of choice, then it works fine.
Classical guitar --> Line Audio CM4 @ SSL12 --> KDE-Plasma @ Debian-Linux --> Waveform PRO 13.5
- KVRAF
- 19788 posts since 16 Sep, 2001 from Las Vegas,USA
13.3.11 was released through the Product Manager today. The same issue exists that I reported several versions back. The Product Manager says the latest version is installed when it is in fact not. It has to be manually installed which makes a Product Manager kind of pointless.
Also the update broke the Piano Roll Keyboard. Previous versions:
Version 13.3.11 on two different systems (Win 11 and Win 10)
Also the update broke the Piano Roll Keyboard. Previous versions:
Version 13.3.11 on two different systems (Win 11 and Win 10)
You do not have the required permissions to view the files attached to this post.
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe
- KVRAF
- 4888 posts since 3 Jan, 2003 from Vancouver
You mean some of the lines not showing up between the keys? It seems to work a bit better when I use software rendering instead of Direct2D, but it should work better than that.
Surely there must be consensus by now...
- KVRAF
- 4888 posts since 3 Jan, 2003 from Vancouver
Looks like any new Track Presets that I make will show up in the Track Presets. Old ones do not.It'd sure be nice if the Track Presets I made would show up somewhere...
Surely there must be consensus by now...
-
- KVRAF
- 1594 posts since 9 Jan, 2018
I'm also experiencing this.Teksonik wrote: Tue Feb 04, 2025 9:05 pm 13.3.11 was released through the Product Manager today. The same issue exists that I reported several versions back. The Product Manager says the latest version is installed when it is in fact not. It has to be manually installed which makes a Product Manager kind of pointless.
Also the update broke the Piano Roll Keyboard. Previous versions:
WF Pro 020425-2.png
Version 13.3.11 on two different systems (Win 11 and Win 10)
WF Pro 020425-3.png
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.
More fun at Twitter @watchfulactual
More fun at Twitter @watchfulactual
