Edit Previews
- KVRAF
- 4891 posts since 3 Jan, 2003 from Vancouver
Is there some kind of way to predict if Waveform will make a preview for an edit? It rarely does any more. I was pretty excited when I got WF11 because the previous version I was using (WF9) had pretty much stopped making previews and WF11 was quite good at making them consistently.
Until now. Now it only makes a preview maybe 30% of the time.
Does it hit some kind of limit? Are there too many in the previews folder? Does it get confused when I go back and forth between WF9 and WF11? They seem to share the previews folder.
I have 320 OGG files in my preview folder. Only 3 have been generated so far this month. At this point I have dozens of edits without a preview.
Until now. Now it only makes a preview maybe 30% of the time.
Does it hit some kind of limit? Are there too many in the previews folder? Does it get confused when I go back and forth between WF9 and WF11? They seem to share the previews folder.
I have 320 OGG files in my preview folder. Only 3 have been generated so far this month. At this point I have dozens of edits without a preview.
Surely there must be consensus by now...
-
- KVRist
- 228 posts since 2 Feb, 2015
Yes I agree the edit previews are somewhat hit and miss. I'm not sure what triggers them sometimes, is it save or closing the edit or both? It would be nice to be able to manually force a preview sometimes.
- KVRist
- 236 posts since 9 Feb, 2017
I figured: save, close a project and keep tracktion alive will trigger rendering. It takes a while to render. Preview will update on next startup.
You can follow the rendering process if you use rewire. The play head moves inside the second daw, while rendering the preview.
You can follow the rendering process if you use rewire. The play head moves inside the second daw, while rendering the preview.
-
- KVRist
- 228 posts since 2 Feb, 2015
Thanks, no wonder I found it inconsistent, I must be shutting Waveform down too quickly.astey wrote: Tue Jul 07, 2020 7:15 pm I figured: save, close a project and keep tracktion alive will trigger rendering. It takes a while to render. Preview will update on next startup.
- KVRAF
- Topic Starter
- 4891 posts since 3 Jan, 2003 from Vancouver
You can see the preview being generated up at the top right, in the background tasks (the circle 100). I'm still having few previews created even if i leave Waveform running.
Surely there must be consensus by now...
- KVRist
- 189 posts since 27 Mar, 2014 from Brisbane, Australia
I'm running the Linux version and I've not a seen a preview get generated for some time now with various version numbers.
Making Bitpop music....
Tracktion Waveform 11 under Ubuntu 20.04.
ROC CUbe Ryzen 3400G - 32GB RAM, 2xSSD, Integrated Radeon RC Vega 11 GPU
Yamaha USB Mixing Station, Mackie Reference Monitors & Axiom A.I.R 32 controller.
Tracktion Waveform 11 under Ubuntu 20.04.
ROC CUbe Ryzen 3400G - 32GB RAM, 2xSSD, Integrated Radeon RC Vega 11 GPU
Yamaha USB Mixing Station, Mackie Reference Monitors & Axiom A.I.R 32 controller.
- KVRAF
- Topic Starter
- 4891 posts since 3 Jan, 2003 from Vancouver
UPDATE: After a few tests I think some issues might be the result of sandboxed plugins. I made a fresh edit with just one non-sandboxed plugin. Waveform generated a preview. I duplicated the edit and added a sandboxed plugin. No preview. I duplicated the duplicate and replaced the sandboxed plugin with another non-sandboxed plugin. Waveform generated a preview.
I think I've had more problems with the sandbox than without it. It's nice to have for the few plugins that definitely cause trouble, but there are plugins that only cause trouble when sandboxed.
So... feature request: have an easy way to un-check ALL plugins for the sandboxing. Then I can check the few plugins that need it. Not many do.
I think I've had more problems with the sandbox than without it. It's nice to have for the few plugins that definitely cause trouble, but there are plugins that only cause trouble when sandboxed.
So... feature request: have an easy way to un-check ALL plugins for the sandboxing. Then I can check the few plugins that need it. Not many do.
Surely there must be consensus by now...
-
- KVRian
- 657 posts since 12 Mar, 2013 from Vladivostok
viewtopic.php?p=7674627#p7674627So... feature request: have an easy way to un-check ALL plugins for the sandboxing. Then I can check the few plugins that need it. Not many do.
You can ctrl+a to select multiple rows then enable/disable them all together.
- KVRian
- 1300 posts since 3 May, 2005 from Victoria, BC
Thanks for the report, looking into why previews aren't generating for edits with sandboxed plugins.
- KVRAF
- Topic Starter
- 4891 posts since 3 Jan, 2003 from Vancouver
Do all the various Waveform editions share the edit previews, but don't share nicely? I fired up WF9 to do some testing - seeing if a particular issue with a plugin is WF11-specific or in multiple versions and all my previews in WF11 seem to have vanished.
Yup. I made new previews in WF11 and then loaded WF9. Now those new previews are gone from WF11.
BTW, there are things that work in WF9 that don't work in WF11. One is initial settings loading. Some VSTs load up from a saved edit with the correct settings in WF9 but load up with the init or mangled settings in WF11. Image-Line plugins in particular seem to have this issue, as do some old VSTs that are jBridged.
Is settings loading different in WF11 over WF9 (I don't have WF10 to test)? Loading an edit in WF11 is much more likely to result in a VST that doesn't successfully load the settings.
Another thing I've noticed is that really old edits with folder tracks go crazy (tracks missing and/or no browser contents) in WF11 but load fine in WF9. That's not a huge issue as long I can run WF9 and re-save the edit.
Yup. I made new previews in WF11 and then loaded WF9. Now those new previews are gone from WF11.
BTW, there are things that work in WF9 that don't work in WF11. One is initial settings loading. Some VSTs load up from a saved edit with the correct settings in WF9 but load up with the init or mangled settings in WF11. Image-Line plugins in particular seem to have this issue, as do some old VSTs that are jBridged.
Is settings loading different in WF11 over WF9 (I don't have WF10 to test)? Loading an edit in WF11 is much more likely to result in a VST that doesn't successfully load the settings.
Another thing I've noticed is that really old edits with folder tracks go crazy (tracks missing and/or no browser contents) in WF11 but load fine in WF9. That's not a huge issue as long I can run WF9 and re-save the edit.
Surely there must be consensus by now...
- KVRAF
- Topic Starter
- 4891 posts since 3 Jan, 2003 from Vancouver
In case anyone else has both WF9 and WF11 installed, I highly recommend changing WF11 to use its own Temporary folder. I did some tests and used UltraCompare to check and WF9 definitely erases all of WF11's preview files. How rude. I made a copy of the Temporary folder and renamed it to TemporaryWF11 and then I updated WF11 to use that folder instead.
Surely there must be consensus by now...
-
Peter Widdicombe Peter Widdicombe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=336849
- KVRian
- 1206 posts since 29 Aug, 2014
Huh. I lucked out. 7, 8, 10, 11 only !
Waveform 13; Win10 desktop/8 Gig; Win11 Laptop; MPK261; VFX+disfunctional ESQ-1
- KVRAF
- Topic Starter
- 4891 posts since 3 Jan, 2003 from Vancouver
10 and 11 don't interfere with each other? I didn't get v10. Maybe they started the "don't delete what isn't yours" policy with v10.
Surely there must be consensus by now...
