#109

Not yet, no – I intentionally wanted it to be easy to have different tempos for different effects (e.g., delay and tremolo slightly offset from each other). It shouldn’t be too hard to sync it to MIDI technically, but I’ll want to dig into how to make it easy from a UI perspective to switch between MIDI-syncing and “free” BPM

2 Likes
#110

Maybe in BPM the furthest left option is “MIDI” – the 404 has something similar with sample BPMs; they can all be synced to a global “pattern” BPM by turning the pot full CCW.

3 Likes
#111

Great script! I’m wondering if an LFO could be used that switches between which pedal is active/bypassed for probably crazy results ?

1 Like
#112

Very impressive , are they able to be clocked to an external Midi master clock?

#113

This sounds really cool. One thing I’d be interested in is a notch filter with variable q (the ability to get pretty tight) and the ability to do a lot of dB reduction. My use case is playing bass through my guitar cab. the cab/speaker resonates at 100hz, so I have to play a lot quieter, but if I run through my DAW and reamp back through with a notch filter from proq-3 on the offending frequency, I get get some really loud, thick sounds out of the bass.

Also, on the latest version, I’m noticing a bug in the params menu for the mod matrix. When I start adding, removing, moving effects, the mod matrixes that are there don’t line up with what effects I actually have.

For example, I had an EQ, Delay, and Vibrato, and in the params menu, there was just two matrices, both labeled vibrato. I can dive deeper into a more deterministic reproduction scenario if it’s not reproducible.

EDIT: Also, modulation on the size of the reverb is awesome. I was able to dial in a pretty close setting as to one of my favorite settings on my meris mercury7. Long decay, about 40% on the size with a very very small amount of mod (slow sine LFO with depth at 25 and 2 or 3 on the mod matrix), 10% shimmer, and tone and mix set to taste (I had them somewhere aroudnd 50%. You get the slow, subtle pitch warble in the tails.

#114

Right now it only lets you LFO “continuous” values (which are most values), but it shouldn’t be too hard to map the continuous LFO to a discrete setting like active/bypassed. I’ll look into that for the next release :+1:

Not yet! That’s a wonderful idea, though. That’s certainly how I use most all of my LFOs in eurorack :smile: I’ll see if I can work it in to an upcoming release; it may take a bit of UI/UX tinkering

The EQ pedal should work already! For the mid frequency band: the Q goes from 0.1 to 4, the gain goes from -20dB to +20dB, and the frequency goes from 100Hz to 8kHz. So setting things at 100Hz, -20dB, Q of 4 should get you what you need :smile:

Would love some reproduction steps! I’m using the script pretty frequently and haven’t seen anything like this yet :thinking:

3 Likes
#115

Did you use a boost on the guitar for this?

#116

This was before I got a boost pedal, so this is just using Pedalboard’s master “input gain” parameter :+1: If you have a boost pedal, I’d recommend it – it will probably provide a cleaner analog gain vs norns’ digital gain

#117

Version 2.1.0 is here! Available in Maiden, or as a ZIP file

Changes:

  • Allow the Mod Matrix to modify “discrete” parameters in addition to the “continuous”
    parameters. You can now have Mod Matrix control over things like: Delay’s “Quality” option, the Granular effect’s “Freeze” option, the Resonator’s “Model” option, Tremolo’s “Beat Division” option, every pedal’s “Bypass” setting, and more (cc @Glitcher)
    • This means that at this point, every parameter is modulate-able (except Delay’s BPM and Beat Division – it produces rather noticeable artifacts that I’d like to fix first). I haven’t tried all of them extensively, please let me know if any of them are acting up on you!
  • Fix a bug in the Mod Matrix’s UI that would happen after you swapped pedal positions (cc @jlmitch5)
11 Likes
#118

Ah sorry forgot to reply…the eq is working great! Also I hadn’t ran into the issue again but sounds good

1 Like
#119

Bugfix release! v2.1.1 (c7c11b3) available in Maiden or ZIP File

There were two bad bugs caused by the Mod-matrix-ification:

  • Pitch Shifter pedal was entirely broken (you couldn’t even add it to the board)
  • If you swapped the pedal in a given slot a bunch, eventually the whole app would slow to a crawl

These are both now fixed! :tada:

Stay tuned within the next week or so for… arc support! :eyes:

9 Likes
#120

Arc support is here with v2.2.0 (e1b51da) available in Maiden or as a ZIP File

  • Choose “Follow” or “Fixed” in the params menu, under “Arc”. Defaults to “Follow”
  • “Follow” mode
    • On The Board, each arc encoder controls wet/dry
    • On Pedal Pages, arc encoders 1, 2, and 3 change dial values and arc encoder 4 changes wet/dry
    • On the Mod Matrix page, arc encoders change what they control depending on which row you are on
      • In the LFOs and Envelope Follower “meta” sections, each encoder controls a different “meta” control
      • In the detailed Mod Matrix grid, the four encoders control the four columns of the focused row
  • “Fixed” mode
    • Use the params page to choose which params are controlled by which arc encoder
10 Likes
#121

Arc support works wonderfully well, thank you for that! This has been one of my favorite scripts to use!

1 Like
#122

Thanks @21echoes for the amazing work.

I have a strange issue with E1 not changing pages correctly. If I turn it it does nothing, then if I press K1 to exit and return to the script, the page has then changed. It’s the only way I can change pages for now.

Everything else works perfectly. I’ve got the newest version of norns and Pedalboard installed.

#123

Hmm, I’m having trouble reproducing. Can you try uninstalling pedalboard and installing again? If that doesn’t help, mind firing up maiden and seeing if anything interesting like an error message gets printed out to the logs when you turn E1 but the page doesn’t change?

#124

Thanks for getting back to me. I had already re-installed, but tried again, still the same thing. Checked in maiden and got this error:

lua:
/home/we/dust/code/pedalboard/lib/ui/util/arcify.lua:332: attempt to index a nil value (global ‘tabutil’)
stack traceback:
/home/we/dust/code/pedalboard/lib/ui/util/arcify.lua:332: in method ‘map_encoder_via_params’
/home/we/dust/code/pedalboard/lib/ui/modmatrix.lua:249: in method ‘_arcify_maybe_follow’
/home/we/dust/code/pedalboard/lib/ui/modmatrix.lua:45: in method ‘enter’
/home/we/dust/code/pedalboard/pedalboard.lua:127: in function ‘enc’
/home/we/norns/lua/core/encoders.lua:60: in function ‘core/encoders.process’

#125

Oh wow! So the import is definitely missing from the file, but there must be something on my end that loads tabutil properly somehow anyway. I’ve just now pushed a fix. Thanks so much for this bug report!

:tada: Version 2.2.1 (38459b1) is now live. Available in Maiden (sometimes it takes a few minutes to show up) or as a ZIP file

Two small bug fixes:

  • Fixes a bad import which could have any number of strange side-effects, especially changing pages while in Arc “follow” mode
  • When in Arc “follow” mode, if you had less than 4 pedals active, then went away from the main Board page, then returned to the board, all of the arcs “beyond” the number of pedals you had on the board would still be mapped to their old parameters, rather than being freshly unmapped like they should be
2 Likes
#126

Wow, quick work!

Re-installed, but now the script won’t actually load. Maiden has this result:

script load: /home/we/dust/code/pedalboard/pedalboard.lua

cleanup

script clear

including /home/we/dust/code/pedalboard/lib/ui/board.lua

SCRIPT ERROR: load fail

/home/we/dust/code/pedalboard/lib/ui/board.lua:161: ‘then’ expected near ‘do’
stack traceback:
/home/we/norns/lua/core/norns.lua:138: in function </home/we/norns/lua/core/norns.lua:138>
[C]: in function ‘dofile’
/home/we/norns/lua/core/startup.lua:43: in function ‘include’
/home/we/dust/code/pedalboard/pedalboard.lua:48: in main chunk
[C]: in function ‘dofile’
/home/we/norns/lua/core/script.lua:186: in function </home/we/norns/lua/core/script.lua:186>
[C]: in function ‘xpcall’
/home/we/norns/lua/core/norns.lua:139: in field ‘try’
/home/we/norns/lua/core/script.lua:186: in function ‘core/script.load’
/home/we/norns/lua/core/menu/preview.lua:23: in function ‘core/menu/preview.key’
/home/we/norns/lua/core/menu.lua:140: in function </home/we/norns/lua/core/menu.lua:117>

script clear

clock: ignoring resumption of canceled clock (no coroutine)
clock: ignoring resumption of canceled clock (no coroutine)

#127

Well well then, another little typo. It’s wild to me that these are crashing the script for you but things are working on my end. Perhaps we’re running different versions of Lua? Are you on a factory norns or a shield or fates or something? Either way, thanks so much for the bug reports! These are definitely bugs, even if they’re not impacting me by some grace of god :sparkles:

Anyway, fix is up now! v2.2.2 (0323837) available in Maiden shortly, or as a ZIP File

#128

Haha, great, so working perfectly now!

I’m running a Shield, from a shield kit all updated to 210114.

1 Like