#118

Weird. “Unstaged changes” is a reference to modified files in your sines folder that git thinks should be committed. Maybe there is a .git folder that maiden doesn’t clear out properly?

ssh into norns, cd to /sines folder, and then run git status - you should see the files that maiden is complaing about. maybe you edited sines.lua? git reset --hard in \sines will wipe out your local changes.

but - maybe you want these changes?

1 Like
#119

will do.

yeah…when it comes to code…i do not touch anything. :stuck_out_tongue:
i would break the code and i don’t have the patience one needs to code to begin with. :slight_smile:

i have run into this before a few times with other scripts.

1 Like
#120

OK. But remember, you did checkout a develop branch - I think you mentioned this upthread. this might be the cause of those errors…

1 Like
#121

If find yourself pining for slighty different timbres, I made two variants of the app and posted them on Github. You can install the variants by pasting the below into Maiden. You will need to remap all controls for each variant. Squares has a pulsewidth and filter control, Saws has a filter control. Otherwise identical to Sines.

;install https://github.com/aidanreilly/saws

;install https://github.com/aidanreilly/squares

8 Likes
#122

Oh, nice! Talking of variants…
Two ideas: one variant with frequency controls instead of notes, one with grabbing the input and translating it to a freq (pretty much what @zebra’s crowns does but with the added bonus of the sines interface. Probably it could be just one script that does this, maybe moving some things like bit/samplerate to the parameters could help to add these to the script ui.
I gotta get back to my somehow working/somehow failed attempt to add libreels into the original script as well. Got a strange flickering between scripts after a while and could only load on certain reels.

#123

hmmm. yes I really like that idea of being able to grab a frequency from the input! I’ll check it out.

2 Likes
#124

huge fan of this script… is there any chance we could get an update with the original envelope controls alongside the current sample rate and bit depth ones?

2 Likes
#125

I kind of liked these too.

(I don’t necessarily prefer to get control over every parameter. It can also be very nice if you have to live with choices the instrument (or its inventor) made for you.)

2 Likes
#126

Yeah I agree the current envelope gui is a bit goofy. it would be easy to put back something like the original. I’ll add that to the list.

2 Likes
#127

thanks so much! I do like the envelope control we have now, but the other modes would definitely be nice. seriously nice work :slight_smile:

1 Like
#128

Ok yes. The original envelope implementation is much more fun and playable. I think I’ll put it back, but it will be at the expense of individual attack / decay control.

edit: actually i think we can have our cake and eat it. just added env presets and individual control to the master branch. refresh the app to pick up the changes.

3 Likes
#129

Played around with this yesterday and love it @Oootini ! (Realized a midi controller would be super handy and ordered one today :sweat_smile:)

2 Likes
#130

Same with me. Decided to get a Faderfox ec4 to tame all these parameters from this and also other scripts like CC.

2 Likes
#131

Was looking at a faderfox but went really cheap with nanokontrol2 just to have something :sweat_smile:

1 Like
#132

Yeah. Quite expensive but hopefully fun for a long time. Nanokontrol 2 also seems to be a good choice!

2 Likes
#133

Faderfox is certainly not cheap but built quality is top notch and the ec4 with its webeditor is really easy to set up, also works with both shields and factory norns without a powered hub.
Had the pc4 before and am really happy with the ec4. Still did not feel the need to fix my broken 16n (usb on the teensy broke off…) since I got the ec4.

1 Like
#134

yeah…FaderFox is an investment. :stuck_out_tongue:
but it’s amazingly well built and the simplicity of the programming is great!
with so many map-able features in the scripts i actually upped my rig with a second PC12.
:crazy_face:

#135

Can you explain how the envelope preset vs individual controls work? I can only seem to find parameters for the attack and decay times, but not different envelope types. Maiden library manager says that I am on branch “dc6c100” and says that I am up to date.

#136

Weird. I did update yesterday and got the envelope types.

#137

You don’t see the preset envelopes on the main app page? That would suggest that somehow you are not on the latest version.

How they work is that behind the scenes, each preset fires an attack, decay and bias value to the engine. Further, each value can be individually tweaked from the parameters page.