Oh, wow, tape now prompts for file name but auto generates! (Did reset to 0000)

1 Like

i know this has been brought up a few times already, but is there a fix for this yet? even something temporary? it’s getting very annoying to have to bring up my monitor level every time i open a script

1 Like

Didn’t this get patched in 200328?

2 Likes

Can you describe what your doing in detail so i can try to replicate?

I tried to plug in my Apple keyboard today and it was causing my Fates to crash and restart over and over and only after I unplug the keyboard would the Norns properly boot up. I had used this Keyboard prior to the 200328 (back in January) without issue (but with an RPi3B).

I’m using an RPi4 and just before it reset itself Matron spit out the following

product: Apple_Keyboard
vendor: Apple__Inc
serial: (null)

Is anyone else having this issue?

Just tested with my older apple extended keyboard on my pi4 and no issue.

Does this happen on any/all of the 4 USB ports?

Can you test with any other USB devices (HID or otherwise)?

Could be an issue with the Pi4 itself (if a pi3 was working fine otherwise)?

Nop, not even a temporary yet but I have all the info to fix this and trying to do it correctly. Check dm :slight_smile:

1 Like

Yup the keyboard causes the crash on all 4 ports. The only other USB device I have handy is an Arduinoboy (Teensy 2) and it works fine in every port. I even tried a couple of different scripts. Is there a better way to troubleshoot peripherals?

Not really sure what to suggest.

Perhaps remove the pi and test it individually?

It might be worth checking dmesg or other logs on the pi to see if something is getting logged. The HID device getting added/removed should dump info to dmesg

1 Like

if i understand correctly, this is the expected behavior now for the RESET function. it clears all configuration data and puts the system in a known default state. SLEEP saves state.

changing scripts should not affect the mix levels (unless the script in question sets them for you, which is possible,) i have not seen that behavior but will try and reproduce later today.

@encephalitislethargi i cannot reproduce this.

steps:

  • load script A.
  • change mix levels
  • load a different script B. mix levels stay the same.
  • perform SLEEP
  • power up. script B is running and mix levels are again the same.
  • perform RESET. when the system comes up again, mix levels are at default and no script is selected. (this is intended behavior; RESET is a sort of “panic button” that you should use in lieu of a hard reset if a) you want to discard state changes you’ve made, or b) are having issues with the current script.)

if you are seeing different behavior, i will need more context and steps to repro.

i checked this on norns and norns-shield. i don’t have a Fates. but all these behaviors are defined in the lua layer of the norns system, so i wouldn’t expect any difference. i tested with a clean system on update 200328, and also with a development system using the current master branch.

4 Likes

Thanks so much for testing!

I went through your steps above on my Fates and could not reproduce any obvious error. Mix levels stayed the same between scripts and a reboot.

Also for good measure I did a roundtrip from norns -> Orac -> norns and mix levels looked the same.

I’ve noticed in the past that the mix levels did not update right away if a script changed the value on launch, but not sure if that’s still the case with the most recent params overhaul.

my mistake, i was conflating the 200328 update post with the 200323 post. totally missed that. i’m on the old update. i’m sure the new one will be fine. sorry for the confusion

2 Likes

I can’t seem to connect my phone to Fates in hotspot mode. nnnnnnnn password is rejected. Any ideas? Thanks!

I had similar issue when trying to connect from my Windows PC and just gave up on it but that was a good 6 months ago.

@static @jmsiener I’m on Windows and had trouble for awhile, too. I was able to use SSH to update, and with the most recent versions of the software it’s been connecting fine. What version are you on?

generally i always have problems with hotspot mode. I can’t seem to make it work if my regular wifi network is available.

So… disable home wifi. Set pi4 Fates wifi to off, try clicking on hotspot. Nada. Same on pi3. However, the Shield works. I wonder if I’m missing some magic network manager kung fu deep in the guts. :-\

doing some research and will try to see what I can find after I get some coffee

1 Like

just updated from 200323 to 200328 without issue. thanks for the clear, easy instructions, and for continuing to provide such great support for this project! i really appreciate it :grin:

2 Likes

wifi hotspot update

I’ve found I had an incorrect network config that was causing me problems with establishing a wifi hotspot.

I’ll roll this into the next update, but if you want to use hotspot and would like the fix please send me a message.

1 Like

Man the last time I’d tried probably was back at the start of November. I used used fates to record my band’s live sets we did on our cruise ship gig and when we got back to the room I was just trying to pull the files on my laptop so I could send the guys home with it. Ended up using a phone as a hot spot, connected to that, and then just sent everything that way.

Btw, fates did a great job recording the mix straight off the board. Seems like @okyeron has got it under control now as per usual anyhow.

1 Like

Has anyone attempted to use ethernet/RTP-MIDI to send MIDI to and from Fates? I haven’t messed with RTP-MIDI before and Fates/Norns may not support this at all, but I have an empty ethernet port on both my iConnectivity MIDI box and Fates so it’s got me wondering.