#173

Thanks a lot, I was indeed confused about theses, that makes sense now :slight_smile:

What i’m saying is the second option : I always hear the dry signal before looping, even while having monitor level to -inf.

I just tried it one more time :
– Power on norns
– Lower monitor level to - inf
– Launch Otis, i hear the dry signal + the loops, since it starts with record engaged for both loops, I stop rec and clear both buffers.
– Dry input signal is still here (pre-loop) although monitor level is still set to - inf (sc input level at 0.0 and sc engine level at 1.0).

Im using Otis on a Fates if that could help someway (?) but never got through this kind of trouble before…

#174

I’ll get some norns time after breakfast. :slight_smile: Hopefully we’ll get you sorted out. Some of this definitely needs to be simplified.

1 Like
#175

Thanks a lot, i’m already enjoying your script a lot when using it with a Dogslit and a Fourses, and it forced me to build a tiny stereo mixer to mute my inputs. Only trouble is it’s passive and I loose too much volume with it. If we find a solution it will be a perfect match :slight_smile:

1 Like
#176

there’s def something going on. working it out now. it doesn’t happen in bounds, which makes me think it’s something with the engine.

#177

Thank you for looking into it, let me know if I can help with testing or anything else :slight_smile:

1 Like
#178

definitely seems to be some confusion about meanings of “dry,” “wet,” “monitor” etc.

“monitor” level in norns system is a dry ADC->DAC path, with stereo/mono switch, totally independent of the engine.

likewise of course there is built-in ADC->softcut path.

Decimator engine additionally adds ADC->decimation->DAC and ADC->decimation->softcut.

so there are a lot of paths to keep track of. (and we have not added the softcut->engine path which has been requested.)

that’s accurate.

if “dry/wet” here means, “decimated -> DAC / decimated -> softcut”, then it would require modifying crone behavior. supercollider->softcut level is effectively a post-fader send after supercollider level.

here:

instead of applying the smoothed “engine” level in the initial copy to the EXT bus, it would need to copy to the EXT bus, send EXT bus to softcut, then apply the “engine” level (aka “dry engine” i guess.)

#179

thank you for the detailed information!

if i am understanding correctly, i need to use the ADC->decimation->softcut path and zero out the adc -> engine -> dac path to bring the monitor controls back to “expected behavior”.

expected behavior being, with monitoring set to -inf there is no input signal present at the outputs, input is still recorded by softcut assuming rec is engaged. is this correct?

1 Like
#180

Sounds correct. For reference OOOOOO script does this in the expected way :slight_smile:

#181

the difference being, oooooo doesn’t use an engine. so there’s no need to handle an engine -> dac path in oooooo.

#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?