#11

for sure! i will add it to the list for a forthcoming update

4 Likes
#12

@Justmat
hey ya!!!
dove into this one quite a bit tonight!
your scripts are so cool as always!

wondering…
could you add ye old S&H LFO to toggle on and off the record button?
or…maybe a random probability % like Cheat Codes has for the record?
:stuck_out_tongue:

2 Likes
#13

LFO’s are coming “soon”, i’ll make sure the record toggle is modulatable :slight_smile:

edit: lfo’s are a thing. still have a couple things to add before announcing an update, but it’s close!

https://www.instagram.com/p/CJlvQzxBYTW/

2 Likes
#14

Word! I literally just added Lua LFOs with Arc speed controls for the Sines lib. It was mostly copy pasted. Moving all that logic into a lib was on my list. The LED ring speed redraw function in Cccccccc I found very easy to work with.

#15

update v1.01

4 lfo’s

  • sine, square, or s+h
  • lfo targets:
    • amplitude/volume
    • panning
    • filter cutoff
    • record toggle

i’ve also wrapped record toggle into a param, @encephalitislethargi, should be midi map-able now!

update via the maiden project manager :slight_smile:

15 Likes
#16

hey ya!

went right for the s&h on all LFOs and i noticed a lot of clicking when set to pan.
i set them all to sines and the clicking went away.
settings were around 90-100 for depth and 0.5 - 1.5 for freq.

am i doing something wrong or is this an inherit behavior when s&h pans are set?

1 Like
#17

hmmm, i will look into it this morning. clicking while panning is definitely not the intended behavior :slight_smile:

edit: so i was able to repro the clicks, not sure exactly what the root cause is, but setting the pan slew param to a non zero value (per voice) fixes it.

i’ll push a change to the default pan slew amount as a fix.

edit the second: pan slew update pushed. update via the maiden project manager.

3 Likes
#18

alright, i’m up to date on norns and i have Larc 1.01 and i don’t see Rec Toggle anywhere except as a lfo destination. any idea what i’m doing wrong here?

i appreciate you doing that, by the way. i wish all sampler scripts had this function. so cool. you rule

2 Likes
#19

you’re not doing anything wrong! it’s a couple of different things on my end. i had the parameter hidden, thinking it would still show up in the mapping menu. having fixed that i am noticing that it doesn’t seem like trigger type params are mappable.

i’ll have a bit of time later to work out a fix.

2 Likes
#20

I really love this. Thanks for making it! Works great with no fuss.

1 Like
#21

they should be? this was affected by recent updates though… will check

… ok @Justmat, no i misremembered, map isn’t supported for 'trigger', but is supported by 'binary' type in 'trigger' mode (which is the default.)

so it’s a simple change:

function init()
  -- not mappable:
  params:add({id="t", type="trigger", action=function()print("bang!") end})

  -- mappable:
  params:add({id="tb", type="binary", action=function()print("bang!") end})
end

i’m not really sure if we are supposed to be deprecating trigger for binary or what. (i’m guessing yes)

4 Likes
#22

thanks so much, @zebra!

i was considering using a number type param and doing weird things with it lol your way is much better :sweat_smile:

edit: i don’t have a midi controller to test with, but that seems to have worked!
i pushed the change so, @encephalitislethargi, can you update your larc and let me know?

1 Like
#23

YES! it works perfectly. thanks, both of you. this is so awesome

1 Like
#24

@Justmat such a great script! Thank you for making everything midi map-able for the Arcless among us! Finally sat down with it this evening, mapped my 16n and recorded some strange string loops. Played one back while Larc was still running, only expecting to listen back to what I had just recorded, and surprise! Larc takes tape input!

2 Likes
#25

Hey there!
I’ve recently had issues with Larc: can’t recognize my Arc and do not record anything. Maybe a Sofctcut issue after the last update?
I have the same problem with Mlr…
Thank you🙂

#26

hello!

hmmm, sounds like something another user experienced after the update.

could you check the levels under PARAMS>SOFTCUT and make sure input is turned up?

2 Likes
#27

the last update made the state of mix levels persist independently of script parameters. as an unintended side effect, softcut levels are zeroed by default until they are re-set and the system is sleep'd.

it may be a good idea for softcut-based scripts to explicitly set the softcut levels. (or maybe not, i dunno. if the script is intended as a mixin you may not want to override those settings.)

(sorry, updated with actually relevant lines)

2 Likes
#28

Oh yeah, I didn’t saw this preview post, sorry!
Now everything works well as usual.
Thank you🙂

#29

i do that here :sweat_smile:

#30

hm you’re right. there is a deeper regression and the audio API seems a little broken now. in any case, setting those things through the params does make them persistent, and we will sort the other thing asap.

[update] @Justmat ok, the “quick fix” if you don’t want to require user action and do want to unilaterally set softcut routing levels, is: move calls to audio.___ to the end of init (after params:bang())

1 Like