Lemar Sain Posted August 2, 2019 Share Posted August 2, 2019 1 hour ago, msmcleod said: This could be an indication of a failing memory module. When it's random like this, it's really hard to track down. I did a ram diagnostic with no errors found. Though I can't reproduce it on the fly it does seem to happen after editing clips. Paste, move, slip edits etc. Press play and freeze. Link to comment Share on other sites More sharing options...
HIBI Posted August 2, 2019 Share Posted August 2, 2019 On 8/1/2019 at 7:19 AM, Jesse Jost said: Edit Filter not persisting correctly with SITs What is "SIT"? Link to comment Share on other sites More sharing options...
Jonathan Sasor Posted August 2, 2019 Share Posted August 2, 2019 Just now, HIBI said: What is "SIT"? Simple Instrument Track Link to comment Share on other sites More sharing options...
HIBI Posted August 2, 2019 Share Posted August 2, 2019 @Jon Sasor Ah, thank you! Link to comment Share on other sites More sharing options...
Lemar Sain Posted August 2, 2019 Share Posted August 2, 2019 Didn't the quantize resolution use to go to 64 triplet? I hope I'm not imagining this. Link to comment Share on other sites More sharing options...
Jonathan Sasor Posted August 2, 2019 Share Posted August 2, 2019 30 minutes ago, Lemar Sain said: Didn't the quantize resolution use to go to 64 triplet? I hope I'm not imagining this. Input Quantize function has options to go higher than 32nds, but both the Process | Quantize and the Quantize MIDI FX plugin top out at 1/32. This hasn't changed with this update. 1 1 Link to comment Share on other sites More sharing options...
Lemar Sain Posted August 2, 2019 Share Posted August 2, 2019 2 minutes ago, Jon Sasor said: Input Quantize function has options to go higher than 32nds, but both the Process | Quantize and the Quantize MIDI FX plugin top out at 1/32. This hasn't changed with this update. Thanks. Thought was going crazy there for a sec ...lol! Link to comment Share on other sites More sharing options...
Blogospherianman Posted August 4, 2019 Share Posted August 4, 2019 (edited) I’m having an issue when dragging an FX Chain with Waves plugins from one track’s bin to another. It drags fine but all of the FX on the A side of all the Waves plugins are nulled. It worked fine when I tried to replicate it with a brand new chain until I saved it as a TEST Chain preset, then inserted the newly saved preset in a track’s FX bin and then dragged it to a new track. At that point they null. Workaround is copy A side to B side before dragging or just reinsert the preset on the new track. Drag copy also works fine. Any thoughts? Edited August 5, 2019 by Blogospherianman Link to comment Share on other sites More sharing options...
Recommended Posts