Well, this has been fun! There are quite a few reports so I need to review who has said what. Here is a list of reporters and the state I believe them to be. Please confirm / answer any questions below.
The Aeolus (and probably other enginesâ parameter control) issue is reported in ticket 1306. I have identified the commit that broke it and we will get a hotfix patch out soon.
There could be another problem⌠I tried to record some music in real time but it didnât work, both in midi and audio reording. I mean that i donât have any capture as a result.
Please update stable to fix Aeolus (and some other engines). I have rolled back some changes so there may be less functionality than yesterday but the important thing is that the engines are working again.
Hi @riban and zynthianers, I just like to add that I successfully updated from the first stable Oram release to the latest stable version 2409.4 with my V5.1 kit. There were two rounds of updates to get to the latest stable version. Everything is working well so far, including the small NVME SSD I added before the update. Thanks to all the zynthian developers.
Can confirm this fixed the parameters in Fluidsynth.
EDIT: the filter/envelope page parameters are still set to 64 and changing them doesnât affect the sound, tested with some of the soundfonts included in the OS image. Other pages work normally. Iâll file a bug report later today unless I hear otherwise here. I pretty much never use soundfonts so I might be missing something obvious.
Unfortunately, doing the update also replicated another issue I noticed yesterday but wasnât going to mention until I had replicated it:
Since at least the pre-rollback 2409.4 update yesterday (possibly the 2409.3 update as well, but I reflashed my SD card for that one so I donât know), the list of enabled processors is reset to the defaults after an update. I donât believe this happened with previous updates, although Iâve only had the Zynthian for about a month and only ran the updater a couple times early on, so itâs possible I hadnât enabled or disabled anything yet at that point (but I think I had).
Example: after I flashed 2409.3, Osirus and OsTIrus were disabled in the MIDI Instrument/Synth list by default so I enabled them (along with a few others) and disabled a few that I donât use. After updating to 2409.4 yesterday, all of these changes had been reverted. I enabled Osirus, OsTIrus again. After updating again today, Osirus and OsTIrus were disabled.
I can do a full bug report but wanted to run it by the thread first since Iâm not entirely sure when it started happening.
Please do add a bug report to the issue tracker. I think we need to draw a line under this point release and gather issues to be resolved in the round.
I canât see any âStart Audio Recordingâ and âStop Audio Recordingâ option. Pushing the record button it seems it starts recording as i see the red circle but in the end nothing is recorded.
In the Midi Recorder window i habe the âStart midi recordingâ option and it seems to work, but again it wonât record anything.
MIDI recordings are only made if there is some MIDI received during the recording. So if you start MIDI recording then stop it again before sending MIDI to the zynthian, there will be no resulting SMF.
Audio recording should be recorded whilst the red circle displays. How are you checking for audio recordings?
Do you have a memory stick plugged in?
Audio recordings go there, if itâs available, and I might mention they ainât easy to find by any of our preferred routes if they have.
This seems to be something specific to your workflow. Audio and MIDI recording has been working fine in stable, staging and testing without anyone reporting any issues. Will you please describe each step you take to make a recording and check whether it has suceeded?
