Thanks. I did not know that.pough wrote: Sat Feb 27, 2021 10:04 pmSandboxed plugins are in a separate process and are pretty much not a child of Waveform so they don't obey the rules you're expecting.JamminFool wrote: Sat Feb 27, 2021 7:41 am I'm using version 11.5.2 on Windows 10 and notice that Waveform is not bringing dialogs to the top anymore. If I have a plug-in window open and exit Waveform, the "Save or Discard changes" dialog is hidden beneath the plug-in window. This looks like the program is hung until you realize that it is waiting for input.
My recommendation for sandboxing:
Leave sandboxing on. Turn off sandboxing for all individual plugins except in cases where you know there is a problem.
11.5 is up
-
- KVRAF
- 2206 posts since 16 Apr, 2004 from between my ears
- KVRAF
- 4891 posts since 3 Jan, 2003 from Vancouver
Anyone else having troubles with the interface becoming inaccessible? It seems to be a combination of the edit playing and a particular plugin GUI showing. I can only stop the edit playing by using a MIDI controller.
Never mind. Looks like it was due to my trying out OpenGL Renderer a little while back. Switching back to Software Renderer fixed it. It only seems to be a problem for some plugins and not others.
So if anyone else has issues with the interface becoming inaccessible, try Software Renderer (Settings -> Advanced). Also, be careful when this happens. All of those clicks and key commands will go ahead and process AFTER the edit stops playing.
Never mind. Looks like it was due to my trying out OpenGL Renderer a little while back. Switching back to Software Renderer fixed it. It only seems to be a problem for some plugins and not others.
So if anyone else has issues with the interface becoming inaccessible, try Software Renderer (Settings -> Advanced). Also, be careful when this happens. All of those clicks and key commands will go ahead and process AFTER the edit stops playing.
Surely there must be consensus by now...
- KVRAF
- 4891 posts since 3 Jan, 2003 from Vancouver
Render Marked Region seems to be a little vague on where the end is. I have an audio clip. I chose In and Out positions. I chose Render Clip -> Render the marked region of the selected clip and the resulting rendered clip is longer than the marked region.
Windows 10. Waveform 11.5.2.
As you can see from the attached image, the rendered clip (cyan) is longer than the marked region.
Windows 10. Waveform 11.5.2.
As you can see from the attached image, the rendered clip (cyan) is longer than the marked region.
You do not have the required permissions to view the files attached to this post.
Surely there must be consensus by now...
-
- KVRist
- 358 posts since 3 Dec, 2004
I can't reproduce this one. Are you using the range selector at all? What's your exact render process after marking the clip?pough wrote: Tue Mar 02, 2021 6:12 pm Render Marked Region seems to be a little vague on where the end is. I have an audio clip. I chose In and Out positions. I chose Render Clip -> Render the marked region of the selected clip and the resulting rendered clip is longer than the marked region.
Windows 10. Waveform 11.5.2.
As you can see from the attached image, the rendered clip (cyan) is longer than the marked region.
-
- KVRist
- 358 posts since 3 Dec, 2004
My bad, just noticed you said 'render clip'. I did 'render track' and the normal render option but with "selected track only". I'll check again when I get a chance.Kang wrote: Wed Mar 03, 2021 4:43 pmI can't reproduce this one. Are you using the range selector at all? What's your exact render process after marking the clip?pough wrote: Tue Mar 02, 2021 6:12 pm Render Marked Region seems to be a little vague on where the end is. I have an audio clip. I chose In and Out positions. I chose Render Clip -> Render the marked region of the selected clip and the resulting rendered clip is longer than the marked region.
Windows 10. Waveform 11.5.2.
As you can see from the attached image, the rendered clip (cyan) is longer than the marked region.
-
- KVRist
- 358 posts since 3 Dec, 2004
All the render clip options are working perfectly for me with the markers. It does give priority to the range selection over the I/O markers as the "marked region" (as it seems like it does with most things).
- KVRAF
- 4891 posts since 3 Jan, 2003 from Vancouver
Thank you for testing that. I've done some more testing. The track has two Voxengo plugins: HarmoniEQ and Crunchessor (VST3 versions). If I removed them, the render works perfectly. But it renders too long if I have even just one of the plugins. It also renders too long if I have both plugins disabled!
Switched from Voxengo to ToneBoosters (VST2) and it's still too long, but not as much.
Switched to the VST2 versions of the same Voxengo plugins and it works perfectly. No extra.
Weird. Some kind of plugin delay compensation thing, maybe?
Switched from Voxengo to ToneBoosters (VST2) and it's still too long, but not as much.
Switched to the VST2 versions of the same Voxengo plugins and it works perfectly. No extra.
Weird. Some kind of plugin delay compensation thing, maybe?
Surely there must be consensus by now...
-
- KVRist
- 358 posts since 3 Dec, 2004
Ah, Ok. Weird. I have Crunchessor and I have still have the Toneboosters demos and yeah you're right. The weirdest part is that the Crunchessor one cuts off sound where the clip should end, but with Toneboosters reverb it doesn't, you can hear the reverb tail in the extended part of the clip. I tried with IK T-racks and Plugin Alliance VST3 plugins (for testing I'm putting 5 instances on the track) and it was fine.pough wrote: Thu Mar 04, 2021 1:43 am Thank you for testing that. I've done some more testing. The track has two Voxengo plugins: HarmoniEQ and Crunchessor (VST3 versions). If I removed them, the render works perfectly. But it renders too long if I have even just one of the plugins. It also renders too long if I have both plugins disabled!
Switched from Voxengo to ToneBoosters (VST2) and it's still too long, but not as much.
Switched to the VST2 versions of the same Voxengo plugins and it works perfectly. No extra.
Weird. Some kind of plugin delay compensation thing, maybe?
Fortunately, the sounds seemed to line up perfectly so I don't think it's a PDC thing, the starts all match to the IN marker as well. I've actually done a bunch of PDC testing since I switched from Tracktion to Waveform (pretty recently), and it's been solid.
Render Track also seems to work fine with any plugins and will give you the same exact render. That's what I always use anyway, I don't think I've ever done 'render clip'. Interesting find.
-
- KVRer
- 9 posts since 26 Nov, 2020
Sorry for the late reply (I don't get notified), but no; not on Mac. Windows. This issue with existing plugins not found is most persistent for plugins on the master in the bottom right. Occasionally this happens with plugins on regular tracks to (as well as plugins working, but having been reset to a default by themselves).FigBug wrote: Fri Feb 26, 2021 5:07 pm Are you on an M1 mac? Since Waveform is now M1 native it will no longer see your VST plugins that are Intel only. Get Info on the Waveform icon, enable Rosetta mode and then you'll be able to see your Intel VST plugins again.
Worst case scenario is the attached screenshot... all these 'not found' plugins are actually there... this whole song has basically been trashed :\
You do not have the required permissions to view the files attached to this post.
-
- KVRer
- 9 posts since 26 Nov, 2020
it seems the above screenshot is a slightly different scenario though: the "Tempo Delay" I've been using successfully in previous Waveform version now seems to crash the plugin sandbox environment.
- KVRian
- 1300 posts since 3 May, 2005 from Victoria, BC
That is super weird. Can you zip up that project folder and send it to me at roland@tracktion.com?stuffkikker wrote: Fri Mar 05, 2021 11:33 amSorry for the late reply (I don't get notified), but no; not on Mac. Windows. This issue with existing plugins not found is most persistent for plugins on the master in the bottom right. Occasionally this happens with plugins on regular tracks to (as well as plugins working, but having been reset to a default by themselves).FigBug wrote: Fri Feb 26, 2021 5:07 pm Are you on an M1 mac? Since Waveform is now M1 native it will no longer see your VST plugins that are Intel only. Get Info on the Waveform icon, enable Rosetta mode and then you'll be able to see your Intel VST plugins again.
Worst case scenario is the attached screenshot... all these 'not found' plugins are actually there... this whole song has basically been trashed :\
-
spoontechnique spoontechnique https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=418750
- KVRist
- 492 posts since 7 May, 2018
Has anyone noticed oddness using Modifiers inside of Racks? The envelope follower seems to be outputting audio when I plug it in. And then other modifiers don't seem to want to follow the notes when on note mode. I could have sworn I had these working a bit ago, but I'm not sure.
Linux version?
-
- KVRer
- 9 posts since 26 Nov, 2020
Actually I think I've found what causes it. Since the upgrade, some third party plugins either fail to load or load improperly. When that happens, every plugin loaded after that seem to get that little exclamation mark and won't work.FigBug wrote: Fri Mar 05, 2021 2:30 pm That is super weird. Can you zip up that project folder and send it to me at roland@tracktion.com?
Especially plugins put on the master output seem to be disruptive. If I remove those (even if they themselves don't show up with that warning icon), save the file and load it up again everything works. This is not too invasive; those plugins I put on the master output are just a touch of equalizing and compression, nothing that can't be reproduced quick enough.
Not entirely sure how zipping the project folder would help without including all third party plugins as well though?

