segfault is back in my machine!
EDIT: I did not mean to sound complaining!
And this is before the day’s soup has been allocated….
Very brave. . .
Can you confirm the full behaviour, including software versions, steps to reporduce and log entries? I am not seeing the segfault any more and definitely fixed at least one cause.
I did some testing now, but must leave it for a while and do other stuff.
The result seems to be that one snapshot causes the segfault. The segfault also shows up at the first shutdown AFTER “remove all”, but after that, shutdown works fine.
I removed a clippy chain in the snapshot, and again - after one more segfault, shutdown is ok.
I then reloaded the snapshot and removed everything BUT the clippychain, and this snap consistently caused the segfault. And after removing the Clippy chain - same pattern as before. One segfault shutdown, and then nice working shutdowns.
013-faulty.zss (77.5 KB)
The long story
I’m not exactly sure how to pull log entries, but the ui-log said this:
Feb 03 09:32:44 zynthian startx[1065]: ERROR:zynthian_chain_manager.remove_processor: Chain None doesn't exist!
Feb 03 09:32:44 zynthian startx[1026]: ./zynthian.sh: line 316: 1065 Segmentation fault ./zynthian_main.py
Feb 03 09:32:44 zynthian startx[1026]: *******************
Feb 03 09:32:44 zynthian startx[1026]: EXIT STATUS => 139
Feb 03 09:32:44 zynthian startx[1026]: *******************
Software:
zyncoder: vangelis (2e0799e)
zynthian-ui: vangelis (5b32a34)
zynthian-sys: vangelis (019e70c)
zynthian-data: vangelis (781d76c)
zynthian-webconf: vangelis (0e2c255)
I tried to load another snapshot, but same error. But this time just hanging on the error screen - no reboot.
I then tried to clear all chains before shutdown, and now shutdown is ok - no segfault
I then tried to reload the “initial” snapshot, and now shutdown gives Segfault (and autoreboot)
I then cleared all again, and this time i got Segfault with autoreboot. From there i did another shutdown, this time successful, and i observed the ui-log that still gave me:
Feb 03 09:45:46 zynthian startx[2637]: ERROR:zynthian_chain_manager.remove_processor: Chain None doesn’t exist!
But not the next line about the python script
Another successful shutdown, again with no chains+no sequences
Added a chain with Pianoteq - another successful shutdown
Then loaded one of the “problematic” snaps - again successful shutdown
Then loaded the other “problematic” snap - segfaulterror - autoreboot
Removing all - segfault and autoreboot
Straight to new shutdown - successful
One more time - success
Loaded attached snap (the initially problematic one) - segfault
another shutdown - segfault
and again
removed clippy chain - segfault
and again - sucess
again - sucess
This is implemented in the latest version. You must clean the sequences or start from scratch (clean all) to get the new sequences “disabled by default”. The sequences are enabled when entering pated. No matter you changed something or not. I did like this because you would like to have an empty pattern enabled.
Please, play a little bit with this and tell me if we are getting closer…
Enjoy!
4 Likes
Oh wow 
I hope to find some time this evening
You guys are amazing 
3 Likes
This is very similar to my segfault error prior to the fixes mentioned above.
I am new of this Vangelis: where can I find MIDI recorder?
What hardware and configuration do you have?
Definitely much better for me. I just noticed that the Tempo in the upper right windows now is wrong. In this project should be 90 instead of 120. In the Tempo window everything is ok, and when playing timing is correct. I tested another project and the problem is the same. So it seems that in the pattern window Time is always 120.
5 Likes
custom RPi5 Zynthian with V5 keypad at right
This is due to changes in a recent commit. I have commented in github and @jofemodo can consider how to resolve this. (The change could be reverted or an explicit update of tempo could be done.)
ALT then bold PLAY whill show the MIDI recorder/player.
1 Like
using display buttons it does not work
It worked for me!
- Press and release ALT.
- Buttons turn purple.
- Press PLAY for 1s then release.
- MIDI Recorder screen shows.
I don*t have real buttons, only buttons on display
Me too! I did all of those actions with a 5" capacitive touch screen only, configured with V5 keypad on right. Touch screen button. Which step is behaving differently?
I followed in detail your procedure: it works! Sorry.
I remark that MIDI files is not in alphabetical sorted.
This fixed too.
Regards,
3 Likes
I found out that this is not working. When i reload the snapshot pads are still grey but the play mode is LOOP and playing phrases in sequence is chaotic, with patterns playing from different rows. It seems that setting again gray patterns in loop mode and giving them back colors can solve the problem, so i’m doing again everything in this way.