New BUG midi recorder broken seriously, will lock up

Development
1

recent Vangelis

  1. shortpress Alt
  2. shortpress record: records midi
  3. shortpress recors: recording stops
  4. boldpress play: MIDI recorder files dispayed
  5. select one recorded item
  6. press either play or yes
  7. try to leave the screen. → LOCKUP.
    Nothing works any more.
    No reaction to any input, keypress nothing total lockup.
    Pressing hardware power button on Pi several times will shut down with debug output.
    No erros shown on any logs.
2

Generally this sort of thing is best reported as an Issue using the Report Issue button described in wiki on webconf. It auto populates with your machine configuration which helps with bug tracking.

20241223_17h24m46s_grim
20241223_17h24m46s_grim1920×1080 247 KB

3

No, Sir!
So many bugs I filed already, no one ever took notice of them, I was the only participant. So I’m leaving it that way. Or leave it altogether. I’m not fussled. :upside_down_face:

4

More information:
Downloaded captures via Webconf, all ok.
Deleted all captures via Webconf.
Then Zynthian will never record anything any more.

I guess this related to the bug in the Audio Recorder. Looks like some output scrubing is doing wrong.

And there is no watchdog, nothing, that helps exit the lock-up state. I’ve encountered things like that in Oram, too.

My one cent (not more): For professional use this is a huge giant big NO-GO-Item. Imagine… full lockup, 20 seconds reboot on stage… Nay.

5

Nevertheless, the github system is what is used. It is a benefit to the community and reduced the effort of investigating faults.

6

There are only 24 hours in each day and only a couple of parts time developers who have day jobs and family and lives. I fixed several issues this week reported on the issue tracker. That is where we are able to triage and progress issues. I don’t see your same use name on GitHub. You must be reporting under a different name. So I can’t see if I have fixed any of your tickets or comment on why not.

2 Likes
7

Yes, different user name in github. I used an account I made for another project. Nevermind.

Anyway, a big THANK YOU to you @riban and @jofemodo and all the other developers of this great project.

8

Go on… Give us a clue!

9

A bug is a bug, names don’t matter. :dotted_line_face:

10

Well, if you don’t play the game then you won’t get a result.

11

Hi @fussl !

What is your hardware setup? Config options? Using touch buttons?

Having a total lock with no errors in the logs is quite strange. I will try to reproduce, anyway.

Regards

12

Please, if you tell what issues you reported in github, we could take a closer look. We use to fix issues, trying to prioritize serious bugs.

Thanks for reporting

1 Like
13

We fix this kind of issues as soon as we detect and reproduce it. Could you help us to reproduce the issue by describing your hardware setup and config options?

Thanks!

1 Like
14

Professional users are too serious for playing a game :wink:
Usually they are playing with professional gears that are in the professional price range

15

In my experience the game is usually “I’m not telling, because I lied about it”

1 Like
16

Professional simply means has been paid.

3 Likes
17

Do you mean that @fussl told he created bug reports in the issue tracker, but he didn’t and he is lying about it? What reason could a person have to do such a thing?

But the true is i was looking for these “so many” bug reports in the issue tracker and i couldn’t find them. I could be wrong, of course.

Regards,

1 Like