OpenGL crash on Ubuntu 20.4, but not on AVLinux with same Notebook

[kjetil]

Oh, and yes, I got the crash report. That was a hard crash I haven't seen before. Unfortunately there wasn't enough information in the report to fix it.

[lilith]

Thanks, it seems to be more stable compared to last time I tried it. But I still got 3 crashes already after playing with it for some minutes.

I'm missing the possibility to render a track or a part of the track to audio and to preview the samples while the track is playing. I have a quite large sample libraries which seem to be loaded into the RAM. Can this be turned off?

Changing the volume automation points feels a bit sluggish with my mouse (possibly a graphic driver problem?).

When I add a bus and connect an instrument to that bus no lines are drawn. I that normal behaviour.

I also send a bug report via Radium. Hope it's useful. I'll keep on playing with it.

Sorry for late reply. Seems like email notifications doesn't work.

To show bus connections in the modular mixer you have to enable the "C2" checkbox in the top of the mixer.

When you say "render a track or a part of a the track to audio", do you mean like "bouncing" in protools?

I also don't understand what you mean by quite large sample libraries loaded into RAM. Are you talking about the "Sample player" instrument?

With rendering I mean something like bounce, yes. E.g. mark 4 lines and these 4 lines are bounced to a sample. Like it is working in Renoise.

Regarding samples scanning I mean this window:

https://imgur.com/5vQKt6U.png

[lilith]

Oh, and yes, I got the crash report. That was a hard crash I haven't seen before. Unfortunately there wasn't enough information in the report to fix it.

The second crash report I sent happend while clicking in the modular view to the Hive plugin to open the GUI.

[kjetil]

With rendering I mean something like bounce, yes. E.g. mark 4 lines and these 4 lines are bounced to a sample. Like it is working in Renoise.

Yeah, you can do that by selecting "export sound file(s)" in the file menu. But it's not available in the demo version:

export.png (46.95 KiB) Viewed 3075 times

Regarding samples scanning I mean this window:

https://imgur.com/5vQKt6U.png

Ah, but here the the program just loads into memory duration and number of channels for the samples. It doesn't load the samples themselves, so it shouldn't use much memory.

The second crash report I sent happend while clicking in the modular view to the Hive plugin to open the GUI.

Thank you for context. From the report and what you write here, there seems to be something wrong with undo-handling when opening plugin GUI. But the program didn't crash (it was an assertion reporter, not a crash reporter), it just informed that there was something wrong internally, but I think you should have been able to continue using the program after this report was shown.

[kjetil]

For the assertion reporter, what seems to have happened is that two mouse-press events where sent in a row, without a mouse-release event in between. This should not happen. Do you remember how you opened the plugin GUI? Did you double-click the module, or right-click and then "Open GUI" from the popup menu? Do you use a mouse/trackpad/etc?

[lilith]

With rendering I mean something like bounce, yes. E.g. mark 4 lines and these 4 lines are bounced to a sample. Like it is working in Renoise.

Yeah, you can do that by selecting "export sound file(s)" in the file menu. But it's not available in the demo version:

export.png

Regarding samples scanning I mean this window:

https://imgur.com/5vQKt6U.png

Ah, but here the the program just loads into memory duration and number of channels for the samples. It doesn't load the samples themselves, so it shouldn't use much memory.

The second crash report I sent happend while clicking in the modular view to the Hive plugin to open the GUI.

Thank you for context. From the report and what you write here, there seems to be something wrong with undo-handling when opening plugin GUI. But the program didn't crash (it was an assertion reporter, not a crash reporter), it just informed that there was something wrong internally, but I think you should have been able to continue using the program after this report was shown.

@memory: Ahhh..I see. I just wondered because it takes quite long. I think the program completely freezed during the crash and I clicked the Hive plugin with the left mouse button (possibly twice). My mouse is a Logitech G203. In some DAWs I have to activate the "Tablet" mode for the mouse as it sometimes behaves strange when I choose "Mouse".

This is my Renoise setting:

https://imgur.com/RrkittY.png