search

martin-lueders / ML_modules

free modules for VCV Rack
BSD 3-Clause "New" or "Revised" License
90 stars 18 forks source link

shift register reset #69

Open joopvdl opened 3 years ago

joopvdl commented 3 years ago

Would it be possible to have a reset function for the shift register? So that all the registers will be emptied? I like to build patches that start with just one note, and slowly build up by using the ML shift register. But when I re-start a patch, there will still be values in the shift register (hope I make myself clear) Only solution for now that I know of is to restart Rack.

martin-lueders commented 3 months ago

Sorry for the very late response. I assume you have actually figured it out by now, but you can simply use the 'Initialize' in the right click menu to reset all outputs. I will implement a menu option to always reset on load for the next update.

martin-lueders commented 3 months ago

Actually, while trying to implement it, i realized that I must have misunderstood you. When I load a patch, containing the shift register, the values are always zero. It never stores the values when saving a patch. I will try to implement that values can be stored, when unselecting the option 'Reset on start'.

joopvdl commented 3 months ago

Hey Martin, Funny to hear from you after all this time! Actually I was looking for a way to empty the register so that every time I start a patch I won't have the residu of the previous play. A cv input for that would be my suggestion. I am still using your modules a lot!

On Sat, 27 Apr 2024, 16:45 Martin Lueders, @.***> wrote:

Actually, while trying to implement it, i realized that I must have misunderstood you. When I load a patch, containing the shift register, the values are always zero. It never stores the values when saving a patch. I will try to implement that values can be stored, when unselecting the option 'Reset on start'.

— Reply to this email directly, view it on GitHub https://github.com/martin-lueders/ML_modules/issues/69#issuecomment-2080819890, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH6IMGNL277VB3DI6TVO22LY7O2ZLAVCNFSM475EAFM2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBYGA4DCOJYHEYA . You are receiving this because you authored the thread.Message ID: @.***>

martin-lueders commented 3 months ago

Hi. Thanks for the feedback. Problem with a new CV input if the size of the module. I will see whether I can squeeze it a bit. If it is getting too crowded, I might consider a simple expander module, with a reset input. Another alternative would be to use a negative voltage pulse on the trigger input to reset. With the new stackable inputs this even would be easy to patch.

joopvdl commented 3 months ago

You could also make an expanded that resets all modules like evolution (my favourite) and sequential switches in one go to their initial state

On Sat, 27 Apr 2024, 17:08 Martin Lueders, @.***> wrote:

Hi. Thanks for the feedback. Problem with a new CV input if the size of the module. I will see whether I can squeeze it a bit. If it is getting too crowded, I might consider a simple expander module, with a reset input. Another alternative would be to use a negative voltage pulse on the trigger input to reset.

— Reply to this email directly, view it on GitHub https://github.com/martin-lueders/ML_modules/issues/69#issuecomment-2080866268, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH6IMGP6MNAYDP34Q3REOYDY7O5PLAVCNFSM475EAFM2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBYGA4DMNRSGY4A . You are receiving this because you authored the thread.Message ID: @.***>