![]() ![]() Maybe the buffer gets corrupted and does not reset properly when it changes size. So it definitely has to do something with the local audio engine and how it handles buffer sizes. Because I set the buffer back to 4096 to see if drops appeared once again, but no!! The output was perfect again. So I finally found something that affects my renders directly! or at least I thought so. So I did another render setting the playback buffer to the other extreme (32). Surprise: there were many more drop-outs than in the previous render, but also only at the beginning. So I increased the buffer to maximum (4096) and rendered again. It probably was left there during my dozens of previous tests. So I checked Prefernces - audio I/O and saw the playback buffer was at 2048 samples. other dopouts were at more random locations. The last 80% of the render was drop-out free.Īlso a curious fact, the first dropout was at 0,5s exactly (24000 samples) which is half of the sampling rate (48.000 Hz). Like a stuttering engine starting and stabilizing after a while. What caught my attention is that the dropouts seemed to occur in the first moments of the render. So the first render I did (all local) had indeed some audio dropouts. So I generated some 90min test tone wavs to act as audio tracks, then it's easier to visually inspect them after render for any problem. May I mention my projects mainly consists of taking an existing movie (1 large ProRes) and replacing / adding new audio tracks. So I started simple: local project database, local media and local render output. Hi, I've been able to do some more tests and think i'm narrowing it down. Screenshot2: 7 min of multichanel audio, red lines are drops I'm now stuck with 3 unusable workstations, I cannot find a way to export without random audio drops. I moved / created projects in the local database, drops still happen. Tried to delete project cache from resolve, drops still happen Two consecutive exports of the same timeline will generate these drops at different points in time. drops are generally shorter than one frame (about 100 to 800 samples long) Random drops (complete silence) appear in any channel at different points in time. ![]() Happens with stereo or multichannel audio. This happens when exporting to quicktime mov, mxf, wav, etc. happens when exporting from two different machines (same specs), drops appear in different places been working on these machines over 1 year without issues. I believe this started to happen when upgrading to v17 and setting up a shared project server. I hope it will work for you.Hi, I'm having serious problems with random audio drops appearing on all exports I do. In MacOS, it's located at Users/(your username)/Library/Application Support/Propellerhead Software/Reason Suite/Caches/ (3) Search and delete a file called "_PluginDatabase.dat" which seems to hold a lot of information of all the VST plugins which Reason scanned. Once they're all enabled, Reason will launch without without a hitch - no re-scanning or getting stuck on WaveShells.īUT FIRST DO THE FOLLOWING BEFORE CARRYING OUT THE ABOVE STEPS: You will see the Waves you've enabled individually are actually "enabled" and the rest as "crashed".Įnable one or two more Waves plugins, close Reason, and repeat the aforementioned steps until all plugins are enabled. Reason will scan and might get stuck again. The same thing happens every time!Įnable only one or two of the "Crashed" Waves plugins at a time. I repeated the process of clicking "SKIP" to let Reason launch open MANAGE PLUGINS window clicking "ENABLE ALL" and closing and opening Reason again. But every time I launched Reason, it scanned the plugins and gotten stuck on WavesShellsV12. I uninstalled and re-installed WavesV12 several times rebooted the computer several times after each go cleared up cache and preferences and everything else I could think of. Again Reason started rescanning plugins and gotten stuck on WavesShellV12. TwistedWave by TwistedWave is an Audio Plugin Host and a Mobile Audio App for macOS and iOS. Then I clicked "Enable All" and relaunched Reason. However most of the WaveShellsV12 plugins were "crashed". Once Reason was launched, I opened its MANAGE PLUGINS window and scrolled down the list to see which VST's were "enabled" or "crashed". The scanning went alright until it got stuck on WaveShellsV12.Īfter some time, I clicked the SKIP button in order to get Reason launched. It immediately started scanning all my VST's. Yesterday I decided to update my WavesV12 via Waves Central app. My system is iMac Pro w/ MacOS 10.15.7 Catalina. ![]()
0 Comments
Leave a Reply. |