ok, thanks. i’ll try and reproduce as i work on tape refactor (likely by scripting record start/stop a lot of times)

re: filename index, it’s not super smart, you can manually change the counter by editing /home/we/dust/data/system.state

4 Likes

@Justmat
hey ya!
just more reporting from the front line of noiz…

MANGL was the foundation for an entire modern dance performance that had a showcase performance and then two full performances over the past two weeks.

it was solid and sounded GREAT over a full PA system in the theater.
this is a newer facility here in Houston so it’s really nice!

loading saved presets worked flawlessly.
only thing i had to be careful of was sometimes mangl would make a POP sound when loading the next set of sounds.
i had each of my presets saved with all four sounds muted so i could bring them in as needed for each scene.

my safety work around was to just mute that channel on the mixer for a second to load.

anyhow…
after all of that work…rehearsals, tech rehearsal and three public performances of the show…

i finally had a break and wanted to load all these new scripts that you and everyone else is designing…plugged in the WiFi thingie…turned on norns…and BAM…the whole thing locked up since it defaulted to mangl on startup.
:crazy_face:

rebooted with the kill button underneath norns and pulled the WiFi doodad.
loaded another script and then added WiFi thingie back and now it’s happy again.

anyhow…just more FYI.

now i’m off to connect a Cocoquantus to Otis.
:laughing:

oh yeah…
here was the setup for the show…
https://www.instagram.com/p/BzBsK8egJjk/

3 Likes

You might have a conflict with mangl and a new script you loaded. You should check the output in Maiden to see what the error message is.

If you routinely run without the wifi nub then there is a strong likelihood that you could have run into this bug: https://github.com/monome/norns/issues/399

The short of it is that norns does not have the hardware to keep track of time while powered off which means that the date/time which norns has its clock set to falls behind when it is off. When norns connects to the network it automatically re-syncs to the correct date/time. Unfortunately scsynth freaks out when the clock jumps and hammers the CPU which makes things appear to lockup.

The best way to avoid this scsynth bug is to ensure the wifi nub is plugged in when norns in powered on.

3 Likes

thanks for all of the info!

the WiFi nub was plugged in before i booted up…that’s why i was wondering if it was the script since i ran into this before with mangl.

anyhow…thanks again…this gives me a better understanding of the issue!
:smile:

Mangle chewing on four different samples from Ryuchi Sakamoto’s track andata. MixPre serving as interface, send/returning the mix to FabFilter plug-ins on the iPad and recording the lot.
This is a very elegant (though not inexpensive) route to extremely inspiring music making.
Oh, and beer. And the World Cup! :soccer:

Thank you all for making such very grand instruments!

8 Likes

requests :slight_smile:
pan
lfo> pan+vol

possible?
many many thanks!

1 Like

Just pushed a small bug fix. re-download and replace, or git pull if that’s your thing :slight_smile:

edit: just found another bug/unintended behavior. Won’t be able to fix it until tomorrow :sweat_smile:

2 Likes

i was just looking for any updates!

i’ll wait till tomorrow!
:stuck_out_tongue:

there is also a bug where the speed gets to 0 when switching from scrub mode. I can’t remember if this happens when the action is momentary or not…thanks

1 Like

This is the one I am fixing today :slight_smile: I’ve fixed where alt behavior == momentary, just need to decide how to go about it when alt behavior is set to toggle. :slight_smile:

Bugs, hopefully, squashed! Re-download and replace/ git pull to update.

3 Likes

Any idea why I’m getting this error (related to the polling object)?:

### SCRIPT ERROR: init
/home/we/dust/code/mangl/mangl.lua:152: attempt to index a nil value (local 'phase_poll')
stack traceback:
	/home/we/norns/lua/core/norns.lua:190: in metamethod '__newindex'
	/home/we/dust/code/mangl/mangl.lua:152: in function 'init'
	/home/we/norns/lua/core/script.lua:74: in function 'core/script.init'
	[C]: in function 'xpcall'
	/home/we/norns/lua/core/norns.lua:191: in field 'try'
	/home/we/norns/lua/core/engine.lua:89: in function </home/we/norns/lua/core/engine.lua:88>
>> reading PMAP /home/we/dust/data/mangl/mangl.pmap

Not quite sure. Can you post the output from the other REPL tab? The SC tab


  


warning: didn't find engine: Engine_Glut
cpu_peak
cpu_avg
amp_in_l
amp_in_r
amp_out_l
amp_out_r
pitch_in_l
pitch_in_r

I guess that’s a clue! I’m brand new to norns. I’m guessing I’m missing the GLUT engine… not sure where to get it…

1 Like

It’s here in the Library! I added Glut to the list of requirements in the top post, can’t believe I missed that :sweat_smile:

Thanks for the help. That worked.

1 Like

Enjoying mangl: https://www.instagram.com/p/B09jV-rhdAu/?igshid=sfdju1lqscd5

2 Likes

How’s that FATES board working for you? You running a Pi3 or 4? Also, what was the build time on that custom ARC???

God, I want an ARC so I can play with Mangl so bad. Hahah

1 Like

You can midi map every parameter that the arc controls! No need to wait for an arc :sweat_smile:

3 Likes