shutIt reset

[joopvdl]

A reset input for shutit would be very useful to me! So when using it in a song, yo can be sure it starts with the default setting.

[phdsg]

thx for the feedback. i agree that's a useful feature. and not hard to integrate. but i'd have to change the panel layout(s) a bit. may i ask which version you are using? i'm currently a bit undecided whether i should keep the 4,8,12 ch versions or just do one.

[joopvdl]

I'm on 0.5.7, I think that's the latest version, right? I like the 8ch because it's quite efficient in space usage. I like to use it to control levels in an 8ch mixer, so that's very convenient. But there's not much room for a reset input, as it is now, I guess. I haven't seen the 4 and 12 ch versions, I think.

[phdsg]

there're 3 versions of the shutters. 8ch was first. but didn't like the layout anymore and ditched it (for now). currrent master has only the 2HP 4ch and 6HP 12 ch version. now, with that request, i think i'll give the 8ch another shot. won't be 4HP tho.

here's a quick mockup with placeholders.

does "mute all" / "flip all" / "unmute all" cover your needs?

[joopvdl]

Yes, I think that would be excellent. So you can start with all channels muted or unmuted. Great idea, it's sort of a reset function where you can choose the initial state.

[phdsg]

ok, done...ish!

while hacking this together, i came up with another idea, but i'm not sure if it suits your needs... a menu option that saves whether the module is relaunched in "init" state or in the "last saved" state. how's that?

[joopvdl]

you mean when re-opening the patch?

On 14 Feb 2018 3:01 p.m., "phdsg vn chfhn" notifications@github.com wrote:

ok, done...ish! [image: shutit] https://user-images.githubusercontent.com/33329578/36207985-e5d18b5c-1197-11e8-94b7-4c33c2dc8c98.png

while hacking this together, i came up with another idea, but i'm not sure if it suits your needs... a menu option to saves whether the module is relaunched in "init" state or in the "last saved" state. how's that?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/phdsg/PvC/issues/7#issuecomment-365615693, or mute the thread https://github.com/notifications/unsubscribe-auth/AfyGGR4xFBVoLe5OsyrXQPpk_UHDbEtUks5tUudOgaJpZM4SFItx .

[phdsg]

yes, that's the idea. menu choice will be stored in the .vcv file.

[joopvdl]

it's a great idea. so you can start with open and closed settings. that said, when you stop and re-start a song (which I do a lot), you cannot use this function. Because it will only return to the initial state after re-opening the patch.

On 14 Feb 2018 3:20 p.m., "phdsg vn chfhn" notifications@github.com wrote:

yes, that's the idea. menu choice will be stored in the .vcv file.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/phdsg/PvC/issues/7#issuecomment-365620974, or mute the thread https://github.com/notifications/unsubscribe-auth/AfyGGSYAZX1tXS8Jg_8RUpfFQU_mbvYCks5tUuuugaJpZM4SFItx .

[phdsg]

correct! it was just a "convenience" thing for re-opening a patch. ok so, i'll leave it at that for now and save the menu thing for later.

can't thank you enough for your input. it really helps to have feedback from other users. i had already ditched the 8ch version, but now i'll probably only keep this one and ditch the rest.

[joopvdl]

I'm the one to say thank you! If you like some more feedback, please let me know, I'd be more than happy to help. Joop

On 14 Feb 2018 4:00 p.m., "phdsg vn chfhn" notifications@github.com wrote:

correct! it was just a "convenience" thing for re-opening a patch. ok so, i'll leave it at that for now and save the menu thing for later.

can't thank you enough for your input. it really helps to have feedback from other users. i had already ditched the 8ch version, but now i'll probably only keep this one and ditch the rest.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/phdsg/PvC/issues/7#issuecomment-365633234, or mute the thread https://github.com/notifications/unsubscribe-auth/AfyGGa5USsjPvwzbsWt1jrd8AHsteuFmks5tUvTxgaJpZM4SFItx .

[phdsg]

just shoot! all feedback helps. so far i've received close to none and therefore most of the modules are kind of centered around my way of doing things in rack, while others might use them in a way i never thought of.

and exchange of ideas always leads to new ideas :) i.e. you mentioned "starting/stopping a lot". i immediately remembered how i used to always hit the space bar in vcv for the first sessions. just out of daw habit. gave me the idea that maybe i can make the button module have a "bind-to-key" function...

[joopvdl]

Yes, that would be wonderful! Keep hitting space, too :) I actually brought that up on the facebook group, a few weeks ago. I believe Andrew said it's not possible, though. I would really like some expansion of the bernoulli gate idea. Bernoulli switches. Basically the same switch we discussed before, but with a bernoulli-style randomness to it. So the difference between the current bernoulli gate would be that it can actually input and output a cv or audio, instead of just a pulse. It would need a reset function, too, I guess.

[phdsg]

funny coincidence that you bring up bernoulli gates. big fan too, so i made a module (unreleased still) that's basically a tree of 7 bernoulli gates. saving some space that way.

i know that's not what you were asking for, but your idea is nice too and i'll give it shot.

just to understand correctly, because there's two ways: signal flow: input -> chance-gate -> output
chance-gate has a probability filter that depending on the outcome decides if the trigger
1) changes the state or not
or
2) directly sets state MUTE or UNMUTE

[joopvdl]

That's it. And an input trigger to trigger the probability filter. And of course it has to have lots of blinking lights :) Now I'm trying to make sense of your bernoulli tree..

[phdsg]

its just one bernoulli gate, outputs fed into 2 more, their outputs fed into 4 more. each individual gate has its own input that overides whats coming from above. so at default settings, for the first set of outs you get 50/50 distribution second stage 25/25/25/25 and so on...

[joopvdl]

nice!

2018-02-14 17:55 GMT+01:00 phdsg vn chfhn notifications@github.com:

its just one bernoulli gate, outputs fed into 2 more, their outputs fed into 4 more. each individual gate has its own input that overides whats coming from above.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/phdsg/PvC/issues/7#issuecomment-365672171, or mute the thread https://github.com/notifications/unsubscribe-auth/AfyGGWHNG9ubdifQd__KSEK4pzGugVXVks5tUw_8gaJpZM4SFItx .

[phdsg]

back to the switch. i prototyped it like this: 4HP, 2 sections 1 - A or B into OUT
2 - IN into A or B
each section has: trigger to flip the current state, trigger to toss a coin with associated probability knob over cv triggers to directly set A or B. with a layout roughly like this:

[joopvdl]

so it's a probability switch, but also usable as a regular switch, right?

[joopvdl]

Maybe it's better to have two different versions, one AB into out, one in into AB. Because I'm afraid you'll just need half of the device most of the time.

[phdsg]

yes to the first question! and you're probably right about that second thing too. back to the drawing board...

[joopvdl]

is the red circle that says prob a cv input or a knob?

On 14 Feb 2018 7:17 p.m., "phdsg vn chfhn" notifications@github.com wrote:

yes to the first question! and you're probably right about that second thing too. back to the drawing board...

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/phdsg/PvC/issues/7#issuecomment-365697239, or mute the thread https://github.com/notifications/unsubscribe-auth/AfyGGYxFARW7q3kwYtFt5kNUm3AHb8JKks5tUyNSgaJpZM4SFItx .

[phdsg]

yep, placeholders for probability knob+cv. upper one would be the knob, then cv, then label.

[joopvdl]

I'm starting to look forward to this one!

[phdsg]

okidoke, InToAorB sort of done (except lights):

[joopvdl]

NICE!

2018-02-14 21:22 GMT+01:00 phdsg vn chfhn notifications@github.com:

okidoke, InToAorB sort of done (except lights): [image: intoaorb] https://user-images.githubusercontent.com/33329578/36225977-baa8fa7a-11cc-11e8-82bd-42b2531c8402.png

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/phdsg/PvC/issues/7#issuecomment-365733490, or mute the thread https://github.com/notifications/unsubscribe-auth/AfyGGQIu5CdE2eysVTw7yFRJWX8xp7vPks5tU0CZgaJpZM4SFItx .

[phdsg]

ok, committed to master branch. do you use the binary releases or are you building from source?

[joopvdl]

have been trying, but no luck so far. so it's just binaries for now for me.

On 14 Feb 2018 10:22 p.m., "phdsg vn chfhn" notifications@github.com wrote:

ok, committed to master branch. do you use the binary releases or are you building from source?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/phdsg/PvC/issues/7#issuecomment-365749256, or mute the thread https://github.com/notifications/unsubscribe-auth/AfyGGcxmIi5VAPX9YtWuTQsAVNZi-aBNks5tU06dgaJpZM4SFItx .

[phdsg]

ok, gonna make a beta build then. what platform?

oh and the question from above still remains: would you like the coin-toss result to a) flip the state OR not
or b) switch to A OR B
currently i'm using b, but if a is useful too i can make an option for that.

[joopvdl]

I'm on windows. I do not really understand the question. Isn't the state always either A or B? In that case, I can't see how option would happen. Anyway I am a bit confused by the four outputs. I thought it would be input to either A or B. So one input, two outputs. And its brother, with two inputs, one output.

2018-02-14 22:54 GMT+01:00 phdsg vn chfhn notifications@github.com:

ok, gonna make a beta build then. what platform?

oh and the question from above still remains: would you like the coin-toss result to a) flip the state OR not or b) switch to A OR B currently i'm using b, but if a is useful too i can make an option for that.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/phdsg/PvC/issues/7#issuecomment-365757465, or mute the thread https://github.com/notifications/unsubscribe-auth/AfyGGWC0s3vQ2UYCmxG1JWILe3G-fMluks5tU1YOgaJpZM4SFItx .

[phdsg]

the difference in short: a) tosses coin to decide whether to switch outputs. (heads: switch / tails: don't switch) b) tosses coin to decide which output is on (heads: B(HI) / tails: A(LO) )

the four outputs explained: i added gate outs that are high when its output is on.

PvC-0.5.8-win.zip

gonna work on AorBtoOut tomorrow.

[joopvdl]

Looking good! Btw nice blank panel :) good night, looking forward to what tomorrow will bring.

Joop

2018-02-14 23:44 GMT+01:00 phdsg vn chfhn notifications@github.com:

the difference in short: a) tosses coin to decide whether to switch outputs. (heads: switch / tails: don't switch) b) tosses coin to decide which output is on (heads: B(HI) / tails: A(LO) )

the four outputs explained: i added gate outs that are high when its output is on.

PvC-0.5.8-win.zip https://github.com/phdsg/PvC/files/1725883/PvC-0.5.8-win.zip

gonna work on AorBtoOut tomorrow.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/phdsg/PvC/issues/7#issuecomment-365769977, or mute the thread https://github.com/notifications/unsubscribe-auth/AfyGGTxV9yW1A5wG_U6IP0-8G-0uqwIFks5tU2HFgaJpZM4SFItx .

[phdsg]

damn, i just noticed a bug: cv input for the prob is somehow not working as intended. gonna fix that tomorrow too.

[phdsg]

closing this issue. went a little bit off topic, but in a good way, i must say. feel free to open new ones whenever something comes up.