1.1.0 USB Audio - Is it working for you?

@Odilon

So the USB audio is working ok on your M2/Sequoia, that’s interesting.

With the SD card crash what do you exactly see, any messages in the patcher screen? Patcher Disconnects? Need to turn the power off to the Gills to get it back?

Does this only happen if you plug in a SD Card, so if the SD card is already inserted when you turn the power on is that ok?

The Ksoloti/Gills doesns’t connect at all to the editor if there is an SD card inserted in it. If I remove the card, power cycle and restart the editor it connects, but can only be used in Live mode.

I haven’t tried formatting a card in the ksoloti while running the audio firmware.

It played system audio/spotify quite happily, as well as sound from Max. I haven’t tried it as an audio input just yet. I need the board stable for a performance o Thursday so Ive gone back to previous firmware, but after Thursday I’ll do a bit more in-depth testing.

All good clean fun!

Thanks for the info on the audio.

For the SDCard problem I guess there is a startup patch on it and the new firmware is not liking it.

@Ksoloti ??

Seems like there is a pattern that everyone has SD issues during the first time using 1.1.0. Let me check if FatFS was updated to a new format or something. If yes, I guess a reformat is the only way.

I seem to remember having problems if the startup patch had a different CRC to the firmware but I can’t remember the details!

Same here, though this has always been solved by the CRC check during patch init. “If the CRC does not match, just stop before anything happens.”

However … I have added a LED blink pattern to show that a startup patch has been found but could not be loaded … maybe this part is making trouble.

sysmon_blink_pattern(0xA0A0A0A0);

I would just remove it then. It seemed a bit hit and miss anyway. Mostly did not see it blink though it should have.

I have a vague memory that might have been setting the issue off, something to do with the sysmon thread?

Yes, after going back to this part I realized there may have been at least one second of sleep necessary, but never mind, it’s gone now!

@pmj After some digging I have found the main issue and am now looking at another smaller issue :slight_smile: Should have some news soon…

3 Likes

Thanks, appreciate your digging :+1:

Ok we have a fix, it all ended up being a lot more complicated than I originally thought!

@Ksoloti will need to look at it and go through the pain of a new release.

If anyone is geeky enough and interested in the details of the issue the fix is here: Usbaudio fix by AndrewCapon · Pull Request #11 · ksoloti/ksoloti · GitHub

2 Likes