#238

@Justmat
hello again!

another couple of performance requests…
(please forgive me if these are not possible and or have been already requested)

  • is it possible to have the volume level for each sound persistent on their screens? and if so…can they change with external control as well as with E1?

  • is it possible to add a parameter to turn off the screensaver/sleep screen mode?

thank you!

1 Like
#239

I’ll consider making the volume persistent before I release the next update. I don’t think I can do anything about the screensaver from the script, but I could be wrong. I’ll investigate.

1 Like
#240

The most crippling instance occurred when loading a saved session (a preset, from the menu where one can assign midi CC’s, etc). Like yourself, I am arcless, so that variable is out for my setup. Otherwise, vanilla 128 grid (2019) and vanilla norns (also 2019).

Norns only returned to a normal state after I pulled the plug via the kill switch on the bottom.

FWIW, this has only happened 2-3 times, out of probably 30 sessions.

Part of the difficulty here is that, when this flavor of lockup occurs, maiden/matron don’t produce a readout. Is there any kind of log file that one can pull after the fact? Sorry for my ignorance, I’m trying to be helpful, but alas am a level three minstrel.

1 Like
#242

This is likely a general Norns thing. All the midi mapping is handled by the parameter menu.

1 Like
#243

ok…
moving it to NORNS help.

thanks!

1 Like
#244

so the MIDI controller issue was resolved here:
(i tested it with a horde of controllers)
https://llllllll.co/t/norns-mangl-midi-issue/29730

the killer was…
…
…
…
.pmap
(cue suspense music: duhn, duhn, DUHN!)

thank you @zebra , @dan_derks and always @Justmat for his patience!
:slight_smile:

1 Like
#245

update v2.2

Just a quick update to make use of the new param menu features. Make sure you are running the latest version of norns. (200323 at the moment)

edit:
@SPIKE, i just changed the screen drawing to make the volume/cutoff indication persistent on the screen. :smiley: I almost forgot :smiley:

9 Likes
#246

THANK YOU THANK YOU!!!
so much noiz to create during the Plague!

3 Likes
#247

Most welcome! :sweat_smile: :sweat_smile: :sweat_smile:

1 Like
#248

dove into it for last night’s broadcast!
phenomenal!

took a second to navigate around.
this is really a giant overhaul of the parameters!

all the data on display when assigning controls.
and thank you again for the dB display…it really helps when there is a horde of noiz going on!

#249

I have a problem.
I mapped the volume of the tracks on a Korg nanoKontrol, with the slider at zero the display shows -60 but the sound comes out. What can I do?
The app is updated to the latest version.

1 Like
#250

Sounds like you may still have delay send set to a non-zero value. The default voice setting puts delay send at .02 on all voices, so even with track vol set to -60, you’ll still hear anything being sent to the delay.

Thinking on it now, perhaps I should change the default to zero out the delay sends…

1 Like
#251

Solved, thank you!
So for the moment using the delay it is not possible to reset the volume?

#252

Only way that I can think of currently, is by deactivating the voice (use key2 on norns). This seems silly to me, and adding a delay volume parameter would be super easy. I will try to look at it this morning and post an update.

1 Like
#253

Thanks a lot, it would be great! :green_heart:
I encountered another problem, playing a sample with a non-zero speed, the sound distorts even at low volumes. For example, the same sample used with MLR doesn’t distort.

1 Like
#254

I’ve ran into this before as well, but never figured out what was going on. :sweat_smile: I’ll keep poking around

2 Likes
#255

Thanks! I’m sure you will understand it!

1 Like
#256

Just pushed an update with a delay output volume parameter. This does make some engine changes, so you will need to sleep your norns after updating.

2 Likes
#257

hey ya!
just an FYI…

after updating and sleep…

MANGL loaded up just fine…
loaded up the PSET i was working on.
went to Parameters page…CRASH.

maiden is displaying: Not connected to matron

norns screen is frozen on PSET save/load page

GRID and ARC are moving about and visually i can see it switching tracks when i push a button on the GRID but it won’t mute a track.

had to hit the murder button on the bottom of norns.
:frowning:
(i thought there was an added Vulcan Death Grip to force shut down norns)

anyhow…after a fresh start from sleep it’s running!
:slight_smile:

1 Like
#258

it’s K3 + K2 + K1 , in that order, and hold for 10 seconds. this is a soft reboot of the matron, crone and sclang components.

{so sorry, i had this backwards before}

3 Likes