#12

20 characters of thanks for docs and the engine.

#13

First observations:

mlr stable
tape rec/play not working?
fx engine adds 20% on cpu

Many thanks for the update :slight_smile:

#14

Got the update installed without a hitch, and MLR has been awesome in my two sessions so far!

This is the case for me as well. Just tried recording two MLR takes to tape, and neither of them took. The levels interface is fine, and recording seems to work, but then I get nothing when I play back.

#15

thanks for reporting the broken tape (yikes)

will get a fix right away

2 Likes
#16

confirmed. record is actually working. it’s TAPE playback that isn’t. i just recorded some earthsea and then played it back within mlr. issue: https://github.com/monome/norns/issues/618

is anyone else seeing differently?

#17

Ya I made some recordings last night that load up in MLR but don’t play back in TAPE.

Edit: to clarify, i agree with you @tehn

#18

Does this update include the rollback described in the help thread?


#19

after many hours of testing and triage we decided that the kernel faults were probably not caused by supernova and only correlated with its introduction. we think the changes in the update should help. since you were one of the norns users experiencing regular kernel faults it would be great to get your feedback on it. (as far as i can tell, this is a minority of users which didn’t happen to include anyone in the core development group.)

this update also pulls in the supercollider 3.10 beta2. this exposed a bug in the TAPE playback as described above. we have a fix for this (https://github.com/monome/norns/pull/620) and are also adding a few more things (including a fix for upstream supercollider: https://github.com/supercollider/supercollider/pull/4137) for the next “hotfix” update which will come very soon.

3 Likes
#20

With the upgrade to the new version, when I turn off the effects, I don’t get any volume out of my headphones - I “reset” the audio but that didn’t seem to have any impact. Am I missing something at a controls level?

#21

Is it possible to entirely re-image the device? I’d like to start from a blank slate if possible. Or is that not recommended? If so, do you have documentation on the process? (I’m a dev/sysadmin, FYI.)

#22

yes, you can open it up, put it in usb-disk mode, and do what you will.

[ https://github.com/monome/norns-image/blob/master/readme-usbdisk.md ]

(NB: the newest boards look a little different from the photo, the power-mode switch is much bigger and easier to use.)

i’m not sure what your “blank slate” looks like. if it’s a linux box with nothing on it, then at the least you will want the kernel build and overlays to make the built-in soundcard work - these are in every update tarball. if you want supercollider, you can either build it yourself or use debian and install the .debs that are also in the tarball. if you want the norns lua / menu stuff, yep, those are in the tarball too, so i’d just run the update script on a vanilla rpi debian. (i’m like 85% sure that would give you a working system.)

we don’t regularly build and post “factory images” simply because this would take up a lot of time and bandwidth, it’s rarely useful and is a relative PITA to apply.

in short, i wouldn’t particularly recommend re-flashing the whole filesystem unless something has been inflicted on it to make it unbootable, or you want to do something with the norns that is totally different from what we’re doing.

i can’t reproduce this. maybe post more details?

it is possible to put the output at an inaudibly low level (say -60db) and then put reverb output or compressor makeup gain at a correspondingly very high level, such that the output is inaudible with the fx disabled? :woman_shrugging:

1 Like
#23

Ok, I’ll report back this evening after I apply the update.

#24

The details are … I was using the wrong headphone plug. I am Officially a Dumbass.

2 Likes
#25

e-mail info@monome.org and i’ll help walk you through this and provide an image file

#26

Thanks, Brian. I appreciate it. I’m going to run the update the usual way and see what happens. Will report back. Failing that, I’ll drop you a line.

#27

Just performed update via shell. Ran Flin at fastest tempo, all steps on for about 20 minutes. No crash. Good long run with Loom, too, without issues. Cautiously optimistic!

2 Likes
#28

I tried to make Norns crash. I really did. And I failed.

Nice work everyone. Full speed ahead.

10 Likes
#29

Just a heads up. I updated via USB to 181023 and everything worked like a charm. First use I had a lock up with Loom and rebooted. Used for many hours and no further issues. Yesterday, I ran loom and had multiple lock-ups (four times) after anywhere from 5-20 mins of run time. I am just using Grid in slot one and I have a USB memory stick in slot 3 - no wifi. Anyone else with similar issues? I used the hotspot to reload the update and will test tonight again incase the USB failed.

#30

Loom didn’t get any changes in that release but there is an update in dust now which will be part of the next release and may help. I’d be interested to hear.

1 Like
#31

try turning off the AUX reverb. it’s very heavy on the CPU.

new update getting prepared now

3 Likes