#182

Yes, but additionally I’m saying that as pointed out above, its not presently possible to get the engine output Into softcut without also sending it to the DAC. That would require changes to the crone sources I linked. The changes are pretty simple and I don’t see any major downside to having engine->softcut before engine->DAC.

2 Likes
#183

this is the part i wasn’t getting, thank you for clarifying!

1 Like
#185

Just a few characters to say how wonderful you all are and how thankful I am for your kindness and the knowledge you share with us.

8 Likes
#187

otis v1.4

1.4 brings “tape” saturation! many thanks to @ganders for the contribution :partying_face:

new params:

  • saturation
  • crossover
  • tone
  • noise (tape hiss)

update via the maiden project manager! (you’ll need to sleep after updating as there are engine changes that need to compile)

i’ve also thought about the monitoring situation, and while it’s not a perfect solution… here’s

otis_classic

classic, 75%
classic, 75%2100×1500 70.7 KB

a pre-engine version of otis, updated. use this if you need monitoring to work, and don’t mind losing all the bit crushing/sample reduction/tape saturation stuff.

22 Likes
#188

YUSSSSSSSS! going to try right MEOW!

1 Like
#189

Stoked on this @Justmat!

Question for you and please forgive me if this has been covered above:

I noticed some weird phasing issues when monitoring through OTIS (pre update). Almost as if the stereo width collapses or something strange. Is this expected behavior or is that what “otis classic” is for?

Thanks Mat!!

1 Like
#190

yeah, monitoring is weird in otis due to the way audio is routed between the engine/softcut/DAC.
there’s a detailed post up-thread about it. omitting the engine avoids the routing issue and restores expected monitor behavior. :grinning:

2 Likes
#191

@Justmat
hey ya!

fyi…
running into a wee issue when updating Otis in maiden.

i get this error in the Update All maiden report:
update failed: worktree contains unstaged changes

so…i deleted it and just did a fresh install via maiden to get it onto norns.

this happened on three out of three norns and one shield.

#192

Did you make any manual changes to Otis? If that’s the case, you could update by doing -

git stash to save your changes
git pull to get the latest changes
git stash pop to pop your changes back

1 Like
#193

Hmm, did you try just updating Otis? Instead of using update all? That error suggests that you made changes to a script on your device, but doesn’t say which script changed.

1 Like
#194

does script itself modify any files that are under version control?

#195

no, but since they used “update all”, perhaps another script does?

2 Likes
#196

oh, i missed that the error wasn’t necessarily otis-related. yep.

so this is OT but i’d say the error message is by design. any workaround in maiden would open up the possibility of lost user data. scripts should make alterations to dust/data and never to dust/code.

2 Likes
#197

LOVING the new OTIS! yussss!

Would more than 4 Lfo’s be possible? I want all the modulation! :metal:

2 Likes
#198

Too many will really gum things up, but you’re welcome to experiment! Just change the number on line #9 in otis/lib/hnds.lua

Screen Shot 2020-10-26 at 3.51.49 PM

1 Like
#199

i didn’t try just updating that one script since i usually just do a Update All so i won’t miss something.

and @ganders

heh!
nope…if i touch code EVERYTHING will break.
:stuck_out_tongue:
i leave those sorts of things to the professionals.

2 Likes
#200

Thanks so much! I can certainly see how it can set Otis into a panic state if not careful. I’m thinking 6 is my magic number. 4 LFO’s for flips and skips and 2 for other things.

#201

i’m pretty sure that i had 6 working at one point. :grinning:

2 Likes
#202

Oh I love it!!! Running islands on norns one for some FM-y earthsea goodness into Otis on norns two. Don’t know where the time just went but I’m drifting off to a hissy driven ever so slowly decaying pair of loops dancing around my head.

2 Likes
#203

For the last couple of days I’ve been getting a weird sort of distortion from Otis when speeding up or slowing down the playback speed. It sounds like the downsample parameter in Ableton’s Redux effect, or a very light bitcrushing effect. I checked my parameters, and sample rate is 48k, bit depth is 31, saturation is at 5.

I recently updated Norns to 201029 (Fates on 3b+), so I’m thinking that might be the culprit? Tried a couple other scripts since updating (Cranes, OOOOOO) and the downsampled effect is not present.

Anyone run into this issue, or might there be some setting I’m overlooking that’s causing this?