Buffer Shuffler Auto Dice polluting Undo history
Buffer Shuffler Auto Dice polluting Undo history
The subject title pretty much sums it up. If I use the Auto - Dice feature on Buffer Shuffler 2 my undo history gets cluttered with these random changes. Bit of a pain as it means a change I may have done only a few seconds earlier pretty much cannot be undone due to all the dicing thats happened since, rendering Undo useless with this feature enabled. Does anyone know if this can be turned off/filtered out? IMO the undo history should only include changes I've made myself.
Live 11 Suite (64 bit)
Windows 10 (64 bit)
Plugins galore
Push
Windows 10 (64 bit)
Plugins galore
Push
Re: Buffer Shuffler Auto Dice polluting Undo history
Ah, I recently noticed this too, very inconvenient.
Sorry, no solution, just a +1 from me
Sorry, no solution, just a +1 from me
Re: Buffer Shuffler Auto Dice polluting Undo history
They had the same problem with m4l's LFO & envelope follover back at version 9.0.
it was fixed in the next beta... but probably they overlooked buffershuffler...
it was fixed in the next beta... but probably they overlooked buffershuffler...
Re: Buffer Shuffler Auto Dice polluting Undo history
Thanks for the feedback, pleased it's not just me. Think I'll get it logged with Ableton as a fault.
Live 11 Suite (64 bit)
Windows 10 (64 bit)
Plugins galore
Push
Windows 10 (64 bit)
Plugins galore
Push
Re: Buffer Shuffler Auto Dice polluting Undo history
Same here, really a pity, since I just discovered the new one and adore it.
The previous version (Ableton 8, Max 5) was fixable as described here https://www.ableton.com/en/articles/buf ... ndo-steps/, but it didn't manage to figure it out with this version. Can't see the object that generates the changes.
Any advice from someone who's more in-depth familiar with Max would be appreciated.
The previous version (Ableton 8, Max 5) was fixable as described here https://www.ableton.com/en/articles/buf ... ndo-steps/, but it didn't manage to figure it out with this version. Can't see the object that generates the changes.
Any advice from someone who's more in-depth familiar with Max would be appreciated.
Re: Buffer Shuffler Auto Dice polluting Undo history
Is there really still no fix or workaround for this, 2 years later?
Re: Buffer Shuffler Auto Dice polluting Undo history
No, unless the whole way that M4L works changes... You can't have something that's MIDI Mappable without it writing to the undo history....
If you can live without it being mapped then open the patch to edit, locate the Auto Dice button and change the settings from Automated and Stored to Stored only...
You can then click on it with the mouse...
Cheers
D
If you can live without it being mapped then open the patch to edit, locate the Auto Dice button and change the settings from Automated and Stored to Stored only...
You can then click on it with the mouse...
Cheers
D
Re: Buffer Shuffler Auto Dice polluting Undo history
In case anyone is still struggling with or stumbling upon this...
Based on the link in Oscard's post, this is what worked for me for BufferShuffler 2.0 :
The live.grid objects are in the 8 similar bpatcher objects on the right when you exit Presentation Mode.
For each one, open the bpatcher, unlock it and select the live.grid object. You can then set the Parameter Visibility to Hidden via the Inspector.
All pattern selection operations and automation will be available, and written to the Undo history, but any changes to the steps themselves will not, including AutoDice.
If you want total freedom from the undo history, you can also change Parameter visibility for the live.tab object (the pattern 1>10 selection button object) but that will remove automation possibility for pattern selection...
I've only tested it with the BS, but the same idea should work with most M4L devices. For non-object parameters you can always go to View > Parameters in Max and change to Hidden the visibility of the worst offenders.
Based on the link in Oscard's post, this is what worked for me for BufferShuffler 2.0 :
The live.grid objects are in the 8 similar bpatcher objects on the right when you exit Presentation Mode.
For each one, open the bpatcher, unlock it and select the live.grid object. You can then set the Parameter Visibility to Hidden via the Inspector.
All pattern selection operations and automation will be available, and written to the Undo history, but any changes to the steps themselves will not, including AutoDice.
If you want total freedom from the undo history, you can also change Parameter visibility for the live.tab object (the pattern 1>10 selection button object) but that will remove automation possibility for pattern selection...
I've only tested it with the BS, but the same idea should work with most M4L devices. For non-object parameters you can always go to View > Parameters in Max and change to Hidden the visibility of the worst offenders.