There was been a few times since the update that I didn’t have any sound when I power on!
Always use headphones. I hope it isn’t on the road out. Could this be FW thing? Maybe part of the non powering on bug? (which doesn’t seem to be gone) The lights come on, I hear the audio “pop” into action but nothing when I play the keys, tried adjusting volume, changing patches etc. Need to reboot. Once it needed two reboots before the sound came back.
Anyone else have this?
yes me too from time to time
yes I have also experienced this occasionally
Phew not just me then, must be a FW issue then. As long as the HW isn’t dying on me!
Slightly different but perhaps related issue: After updating to 0.27 I had extremely loud volume through my headphones. Unit didn’t respond at all to turning the volume knob. Restarting the synth resolved the problem.
Hi, we’ve found this. Once in a while on boot up, the fpga doesn’t start, and a power cycle is required to restore operation. It is completely random and on our units quite rare but certainly more frequent in 0,27 than before. Don’t worry there is nothing wrong with your hardware, I am looking into it and will hopefully resolve it soon.
Thanks! George
Many thanks Georges.
Something that has happened twice now (last time yesterday) is I edit a patch, hold to save, then rename it but then it corrupts. You can’t choose it from the patch button now so you need to delete it altogether!
Is this a new FW bug?
I delete it from Windows but I reboot the synth and it comes back but it now sounds almost like an INIT patch, not like my edit or the original patch. I will need to factory reset to get rid of it now. The patch is named like it was originally even though I deleted it! (after reboot)
I tried to delete it then replace it with the original patch but it sounds like an INIT patch. Weird,.
The patch disk should only be unlocked for writing when you wish to rename/move/copy or perform disk operations with the computer.
Although you can use the synth in this mode, FAT systems do not like having two masters and corruption can easily happen.
To avoid this scenario, please do not save patches with the patch disk unlocked and connected to a computer via usb.
If a new patch is saved, you should always either power cycle or at least remove and replug usb before trying to rename it from the PC.
In a nutshell, for playing, creating and saving patches, do not have the patch disk unlocked and connected to a pc. When the patch disk is unlocked and connected to the pc via usb, only perform librarian duties(move/rename etc) do not save new patches.
It’s a very peculiar scenario having a FAT system on a drive with two masters (synth and pc) and it’s not well specified by any standard how this should behave, so my advice for now is to try and avoid the scenario.
I delete the patch but it isn’t going away. If I delete then refresh F5 it just comes back. Delete then reboot the synth it comes back. If I try to replace (drag and drop) the patch it says it’s corrupt.
It is 0KB all other patches are 36KB.
If I delete the entire folder all patches get deleted except this one 0KB patch. Zombie patch over here!
What should I do?
Don’t worry it’s easily fixed, can you send me an email to support@udo-audio.com, describing the scenario. In the meantime, without the PC connected or the patch disk unlocked, overwrite the location by saving a new patch into it.
I believe this is what happened both times, didn’t know you weren’t allowed to do that so I will refrain and hopefully no more corrupts. I will stay frosty 
This worked perfectly thanks.
OK so I successfully edited the patch this time (a CO5MA preset), saved it, then rebooted in unlocked mode to rename it. Kind of unintuitive, I like to rename patches that I edit so I know they’re edits.
Hopefully we will get an editor that navigates round this problem 
Beautiful sounding synth so I can bear the foibles.
Just for clarification, is the only way that the patch disk becomes unlocked is when it gets connected to a computer? Just making sure we don’t need to do something at times to make sure it is locked.
Unlocking it requires you to hold down Patch while turning the S6 on. Just don’t try to program the synth and save new patches when the device is in that state.
Anyone any ideas on the progress of 0.28? Would be great to get some of those bugs ironed out.
Don’t mean to just complain though - I love the sweet new lighting system for the tempo sync!
I like the visual display of divisions too - would like it for the delay times also.
I just received mine a few days ago an it says I have firmware v.028…
The newest deliveries have 0,28 firmware installed. Please don’t revert to 0,27. We have a new firmware version queued up for when we all get back to work next week with some hotfixes to 0,27. Kind regards, George
Please consider me an alternate for the beta list - I’ve done a lot of beta testing and isolating corner cases.