Reels

[circuitghost]

Hey all, new user here with Norns and Grid, diving into Reels as my first script to learn. Apparently, I did register for an account here four years ago, so technically, I’m not new but in all ways that count, I’d say I am.

Anyway, loving what Norns and Grid offer so far, and here’s my first very modest venture into it, using the Reels app with recordings from Awake into Tape and then into Reels, as well as grains and drums from my own sample library:

[return_from_zero]

@its_your_bedtime

Thanks! For now its 60 sec for each track (but you can record on (extreme)low speeds which will give you much more time and also adds nice lo-fi character)

Can anyone confirm that 60sec is still the maximum at default quality? Also, what exactly is meant by “much more time”? Five minutes would be plenty for my purposes.

[papernoise]

I’m not close to my norns right now, but I think you can slow the loop down to 1/4 which would give you 4 minutes I guess. But the audio quality is probably going to be more grainy, haven’t really tried though.

[Rollingpeople]

same here,
can i rec from track 1, 2 and 3 in track 4?

[huron]

I can’t get this to load on my Norns Shield. error: load fail

[Justmat]

Are you running the latest firmware? Can you connect to maiden and paste the error output here?

[huron]

Yeah, it’s the latest firmware.

# script load: /home/we/dust/code/reels-master/reels.lua

# cleanup

# script clear

ERROR (i2c/hp) failed to write

### MISSING INCLUDE: reels/lib/libreels

### SCRIPT ERROR: load fail

/home/we/dust/code/reels-master/reels.lua:15: MISSING INCLUDE: reels/lib/libreels

stack traceback:

/home/we/norns/lua/core/norns.lua:136: in function </home/we/norns/lua/core/norns.lua:136>

[C]: in function 'error'

/home/we/norns/lua/core/startup.lua:47: in function 'include'

/home/we/dust/code/reels-master/reels.lua:15: in main chunk

[C]: in function 'dofile'

/home/we/norns/lua/core/script.lua:172: in function </home/we/norns/lua/core/script.lua:172>

[C]: in function 'xpcall'

/home/we/norns/lua/core/norns.lua:137: in field 'try'

/home/we/norns/lua/core/script.lua:172: in function 'core/script.load'

/home/we/norns/lua/core/menu/preview.lua:21: in function 'core/menu/preview.key'

/home/we/norns/lua/core/menu.lua:139: in function </home/we/norns/lua/core/menu.lua:116>

# script clear

ERROR (i2c/hp) failed to write

[Justmat]

Just rename your script folder from reels-master to reels and it should sort it out

[huron]

Thanks, and sorry I’m new to this stuff. Just finished my Norns Shield build last night!

[Justmat]

no worries! we were all new to this stuff once! congrats on the successful build, and welcome to norns

[nareshran]

Hey there!
I have problems with saving presets since I installed the new version of the Norns system.
First I had to reinstall Reels 'cause the older one didn’t work anymore, then everything was fine beside the presets savings.
Any clue?
Thank you for any tip!

[Ravel]

@its_your_bedtime it may be me… but I can only seem to play loaded samples on track 1 (not 2,3,4). It’s the first time i’ve used this script so it’s very possible I’m missing something. Excited to dive in though, this is exactly the kind of thing that got me into norns.

EDIT: actually I can load samples on tracks 1 and 3. Perhaps this is expected behaviour.

[mcpepe]

First of all, thanks @its_your_bedtime for this great script.

I don’t own an OP-1 but I would love to!!
Meanwhile, I thought I could use my little Casio and Reels to make something similar…(not really)

The poor man's OP1 | Casio VL-Tone VL-1 | DIY Monome Norns Reels | Digitech...

[Cementimental]

Since the latest Norns update (on a diy norns shield) I get 'error: init" when trying to run Reels

Tried deleting and re-installing but no joy

Here’s what I see in Maiden:

# script load: /home/we/dust/code/reels/reels.lua
# cleanup
# script clear
ERROR (i2c/hp) failed to write
including /home/we/dust/code/reels/lib/libreels.lua
# script run
>> reading PMAP /home/we/dust/data/reels/reels.pmap
m.read: /home/we/dust/data/reels/reels.pmap not read.
Engine.register_commands; count: 0
___ engine commands ___
___ polls ___
amp_in_l
amp_in_r
amp_out_l
amp_out_r
cpu_avg
cpu_peak
pitch_in_l
pitch_in_r
# script init
### SCRIPT ERROR: init
/home/we/dust/code/reels/lib/libreels.lua:374: attempt to index a nil value (global 'mix')
stack traceback:
	/home/we/norns/lua/core/norns.lua:138: in metamethod '__index'
	/home/we/dust/code/reels/lib/libreels.lua:374: in field 'init'
	/home/we/dust/code/reels/reels.lua:19: in global 'init'
	/home/we/norns/lua/core/script.lua:105: in function 'core/script.init'
	[C]: in function 'xpcall'
	/home/we/norns/lua/core/norns.lua:139: in field 'try'
	/home/we/norns/lua/core/engine.lua:91: in function </home/we/norns/lua/core/engine.lua:89>

[speakerdamage]

from Norns: update 201113

deprecated
for scripting, mix is deprecated. please use:

params:set('output_level', value)
params:delta('output_level', delta)
params:get('output_level'

lines 374 and 804 of /code/reels/lib/libreels.lua should be changed from
mix:set_raw("monitor", rec_vol)
to
params:set("monitor", rec_vol)

maybe more after that, not in front of norns

[Nornsrulez]

Ughh. This is why I never update anymore. Shit always gets broke

[dan_derks]

@speakerdamage

params:set(“monitor”, rec_vol)

quick correction, these param addresses all end with _level, so monitor_level, etc

looks like a fix already got in, threw up a PR with correct syntax, should be only a little bit before reels is up and running again

[its_your_bedtime]

Thanks @dan_derks and @speakerdamage, all should be fine now!

[speakerdamage]

things like this are usually resolved quickly, and should be expected every now and then with so much continued active development taking place. plus, even if you don’t have a background in coding it’s a good exercise to try to troubleshoot things like this using maiden output and going from there. (I accidentally “liked” this post and can’t undo it for some reason)

[sleeepwalk]

I’m performing next month and was planning on using reels as a live looper and I’ve noticed sometimes when I record a loop it makes the end point - whatever number and it kind of glitches.

Is there anyway to keep the start and end points consistent and not have it change after recording to a track?