#61

just pushed an update!

  • changed to the new clock system (which is super awesome!).
  • updated the parameter menu to take advantage of the new menu features.
15 Likes
#62

hey ya!
quick question…
does Foulplay not react to MIDI Start and Stop messages?

#63

Not at the moment, but it’s easy to do! I’ll add it in today :slight_smile:

edit: @SPIKE, update foulplay and you should be good to go!

6 Likes
#64

AWESOME!
THANK YOU so much!!!

#65

just reporting back from the trench… :stuck_out_tongue:
ran into a couple of weird things.
(apologies…i didn’t have maiden running for any other data)

sending clock from an e-rm Multiclock box.

on one norns it would start and stop with MIDI as it should.

on another norns it would start and then never stop.
i erased it and reinstalled it again and it seemed to work ok at first.

then one or both would sometimes keep running and not stop.
i couldn’t get them to stop with a key command either.
(this was inconsistent by the way)
i would just clear the script and re-run it.

i noticed something else as well.
i was looking at the clock parameters page and i noticed it would jump to the correct time but…there was one time a norns would be at the wrong tempo.
i was sending a BPM of 100 and it would think it was at 34bpm or 82bpm.
after stopping and restarting the clock it would correct and jump to 100bpm.

there were also instances where it would start playing slowly at first and then jump to the correct tempo.
(this occurred on both norns)

#66

Well, that is certainly strange! I only have an OP-1 to test with, so I could have missed something. I’ll poke at it some more today and hopefully get it sorted. Sorry for the troubles!

1 Like
#67

Hi, sorry if this is incorrect as I am very new to the platform but it seems to me the parameter screen is messed up. I don’t see a line for every track and the parameter to select the sample of track 4 in inside the track 3’s parameters.

Let me know if I need to give an specific information, not sure what the etiquette is here :smiley:

#68

Whoops! I will have a chance to look into it later this evening. :sweat_smile:

#69

Awesome. Is there any way also that sample the selector opens in the last folder it was used ? Navigating down everytime you want to try out a sample feels like overkill :smiley:

Thanks for listening !

1 Like
#70

have you updated your Norns recently? there was an update that changed the param menu, and foulplay uses some of these new features. if you update to the latest norns firmware your problem should resolve.

#71

Yeah, I just checked, it says it’s up to date.

#72

If you’re talking about the file selector interaction in general (e.g., menu > params > track x > x: sample), then that’s all handled by the norns system, not Foulplay.

1 Like
#73

that is very odd. everything looks ok to me on my norns. have you updated foulplay?

are you on a factory norns?

does your param menu look like this?

#74

I’m using a shield, not sure how that would affect the result though. Here’s a much less classy version than yours, so you see what I’m seeing.

1 Like
#75

Wowee! That is super strange :exploding_head:

Can you delete and re-install the script?

#76

My memory is hazy here, but I believe this happened to me while developing my own ack-based script when I had a saved paramset that was from an old version of my script. So: maybe try deleting all the pset files in data/foulplay/? And make sure your ack is up to date as well :thinking:

1 Like
#77

@SPIKE, i figured out the midi start/stop thing! i’ll have a fix tomorrow :grin:

1 Like
#78

thank you!!!
sorry for opening a can of worms!

1 Like
#79

FWIW, I removed & reinstalled FoulPlay, made sure Ash was up to date and removed pattern data. It still shows up wierd. Is there any other app that uses the same parameter sub-system ?

#80

try updating Ack, not Ash

Cyrene also uses Ack (it’s the app I was developing where I said I saw something similar during development)

have you opened maiden to see error messages when this happens? seeing error logs would be helpful