Open kramlie opened 1 month ago
Thanks for the thorough report. I'm not able to reproduce though. Maybe you can make a more complicated example that is more likely to reproduce the warning? Also, maybe you can just paste the output of the warning window here? (I didn't get an email in case you clicked "Send", sometimes the email server doesn't work, although it seems to work right now.)
Thanks for the quick reply!
Darn, I thought the example was a sure thing, so I skipped the app-report to keep the noise level down. I have sent it now!
Thank you. Got it. Yes, I've seen that one a few times. But I don't understand what happens. I probably need to be able to reproduce it.
Maybe these configurations can make me reproduce it:
On Tue, Jul 16, 2024 at 8:39 PM kramlie @.***> wrote:
Thanks for the quick reply!
Darn, I thought the example was a sure thing, so I skipped the app-report to keep the noise level down. I have sent it now!
— Reply to this email directly, view it on GitHub https://github.com/kmatheussen/radium/issues/1437#issuecomment-2231573667, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIX3J5SAOZIJQYBAYUBQLLZMVSG7AVCNFSM6AAAAABK6YIWTGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZRGU3TGNRWG4 . You are receiving this because you commented.Message ID: @.***>
What the...
Github really messed up the rendering there. Again:
Hmm! I still can't reproduce it. Can you post which version of jack you are using, and the command line you use to start jack? Also, can you try to temporarily rename your ~/.radium catalog to something else, and see if the problem goes away?
Also, can you try to temporarily rename your ~/.radium catalog to something else, and see if the problem goes away?
Nice, this worked!
I'll dig a little bit, diff the configs and see if I can find out which option is causing it.
Maybe jack transport? (under preferences -> sequencer)
On Wed, Jul 17, 2024 at 10:42 AM kramlie @.***> wrote:
Also, can you try to temporarily rename your ~/.radium catalog to something else, and see if the problem goes away?
Nice, this worked!
I'll dig a little bit, diff the configs and see if I can find out which option is causing it.
— Reply to this email directly, view it on GitHub https://github.com/kmatheussen/radium/issues/1437#issuecomment-2232762372, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIX3JZ7BHAXYZ7QH7SHCODZMYVAJAVCNFSM6AAAAABK6YIWTGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZSG43DEMZXGI . You are receiving this because you commented.Message ID: @.***>
Yes, that's it!
I am indeed using Jack1 :see_no_evil:, even though Radium advises me not to. Unfortunately, for reasons unrelated to Radium, I'm not able to upgrade to Jack2 at this time, at least not without significant effort. It has worked perfectly well apart from this issue though. Do you think Jack1 could be the reason, or is it the Jack transport in general?
PS! The reason I had it on in the first place is because of #1436. I was trying to record MIDI into a different DAW, export it as a MID file, and then import that into Radium. An extremely inconvenient workaround, but it does work. That is, except for the crash we're talking about above.
Yes, I can reproduce it with jack2. It seems to always happen when jack transport is enabled. I did try to enable jack transport earlier, don't know why I didn't see it then, but I see it now.
Anyway, the code looks wrong, it's using the special "play block"-seqtrack for timing when sending out midi messages from plugins, when playing song. So it doesn't look like something is very wrong underneath.
Until the bug has been fixed, you can probably just safely ignore the warning window when it pops up. There will (almost) never be more than one warning window open at the same time, so when you see it, just hide it somewhere, and things should work fine.
And by "fine", I meant "almost fine". The only problem you will have is that you won't get sub-block accuracy for the timing of the messages sent out from the plugins. I.e. the granularity will be 64 frames, which is almost always more than good enough.
On Wed, Jul 17, 2024 at 11:13 AM kramlie @.***> wrote:
Yes, that's it!
I am indeed using Jack1 🙈, even though Radium advises me not to. Unfortunately, for reasons unrelated to Radium, I'm not able to upgrade to Jack2 at this time, at least not without significant effort. It has worked perfectly well apart from this issue though. Do you think Jack1 could be the reason, or is it the Jack transport in general?
PS! The reason I had it on in the first place is because of #1436 https://github.com/kmatheussen/radium/issues/1436. I was trying to record MIDI into a different DAW, export it as a MID file, and then import that into Radium. An extremely inconvenient workaround, but it does work. That is, except for the crash we're talking about above.
— Reply to this email directly, view it on GitHub https://github.com/kmatheussen/radium/issues/1437#issuecomment-2232825320, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIX3JY2XWNNJO7NFUAIDRDZMYYSRAVCNFSM6AAAAABK6YIWTGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZSHAZDKMZSGA . You are receiving this because you commented.Message ID: @.***>
Thanks @kmatheussen, hiding the window works!
1. Steps to reproduce the problem.
Alternatively, you can also load the track I have provided here: crash-example.rad.gz
I expected this to happen: The song plays.
This is what actually happened: Soft crash with the "Radium is in a state it should not be in" message, and the song does not play.
I've tried this recipe 1 time + the provided file 2 times.
The unexpected behavior happens approximately 50% of the times. It seems to alternate between success and failure. However, when using heavier tracks with more content, it seems to fail every time. It may also be related to whether the first automation point has been reached or not (not 100% sure).
2. Which version of Radium are you using? Do you know if an earlier version has worked?
Radium version 7.4.79. I have not tested earlier versions.
3. If relevant, which operating system did you run Radium on?
Ubuntu 20.04 x86_64.