1. Save a D3 reaper project using a custom wavetable
2. Close project
3. Delete wavetable file from file system
4. Load Reaper which typically reloads last open project
5. D3 throws error, crashes Reaper on play
Prefer it to mark oscillator as missing wavetable so user can supply alternative wt and at least have a chance of saving the patch.
Reaper crash on attempt to laod when wavetable movedModerators: Christophe, Mark
3 posts
• Page 1 of 1
Re: Reaper crash on attempt to laod when wavetable movedThis is what should happen, i.e. DUNE 3 giving an error message what wavetable is missing, then using the default wavetable as a temporary replacement.
FWIW I could not reproduce the crash issue in Reaper here (PC/Windows), or any other host for that matter. So could you give us your system specs please? And the exact Reaper version might be useful, too Admin - Synapse Audio Software
Twitter - www.twitter.com/SynapseAudio Facebook - www.facebook.com/SynapseAudioOfficial
Re: Reaper crash on attempt to laod when wavetable movedOk I figured it out, the complication is this is a project I saved on a previous computer, and then everything got moved to a new computer and the drive letters changed.
When Dune3 was in that project, the wavetable directory (and all vsts) were on drive D:. On my new computer, all vsts and configuration are on drive C:. Dune tried to load the wavetable from a missing D directory, and then it tried to fallback to its own soundbanks on the drive relative to the missing wavetable (and it would complain about missing soundbank! or something like that) and then it would crash on attempted playback. I know its d3 specifically crashing because I confirmed it in windows event logs. Note, Dune is installed correctly and has all soundbanks, but they are on C. When I load an empty project with Dune 3, it loads soundbanks and plays back any patch fine. I was able to load and play the project by simply copying my icarus wavetable dir into the new D drive, and then resaving the patch pointing to the correct wavetable location on drive C. So basically, somehow, the old soundbank location was being used when trying to fallback from the missing wavetable. I suppose it was Reaper giving it that location? Soooo, long story short, this is a very uncommon case. Not sure how cost effective it is for you to fix, but at least there's a simple workaround. Thanks Richard, oh and thanks for an amazing update on Obsession as well.
3 posts
• Page 1 of 1
Who is onlineUsers browsing this forum: HYPNAGOGIA and 463 guests |
© 2017 Synapse Audio Software. All Rights Reserved. |