REAPER for Linux bugs

[SmajjL]

Not sure if "sometimes" is easier than "it never works" to problem find
Since Linux on a Live stick is so easy, can't you just do a quick check look see with a quick REAPER see if ReaSynth works, on the Live stick, no need to install the distro even
Mythbuster that one out

Also, REAPER have worked on all distros i tried with straight ALSA, so this would be news to me if it was a problem on the REAPER side.
I can on purpose screw up ALSA by installing and running Cadence or something like that, then ALSA could turn into wewwy busy/in use or something like an oopsie like that.

Think even Steam can do something if it is open in the background.. but that's another story

My gear/gizmo is straight USB though, hmm

[Rivereto Esplorado]

I have tried all that stuff. I downloaded afresh, moved the ".config/REAPER" folder so it was forced to create a new one. When I do that having already lost the keyboard in my regular install, the keyboard is still missing in the "portable" fresh install. Only a system restart fixes things.

I won't bang on about this much longer other than to repeat one last time that other DAWs continue to function with the MIDI keyboard as does aconnectgui even without a system restart. Cue the question "why don't you just use the other DAW?"

[Glennbo]

Originally Posted by Rivereto Esplorado

I won't bang on about this much longer other than to repeat one last time that other DAWs continue to function with the MIDI keyboard as does aconnectgui even without a system restart. Cue the question "why don't you just use the other DAW?"

What happens if you only use REAPER, and never launch the other DAWs?

I never lose communication with the 5 pin midi on my Behringer UMC1820 or the USB midi from my Akai MPD26 using REAPER, but I never launch any other DAWs. Just wondering if using one of the other DAWs could leave midi looking to the OS like it's still in use. Also, I leave my UMC1820 powered on pretty much all the time if that makes any difference.

[SmajjL]

I Believe you that you have these problems and good you have tried these rule out stuff so we can boil stuff down, very curious why myself and i think there is a reason somewhere, just need to find it, don't give up! info is good

--

Tried Ardour and LMMS that is new stuff to me, but got MIDI working in both and none of them destroyed REAPER, here.
Mixbus required mail and blabla just for a demo so, did not do that one

[Rivereto Esplorado]

Originally Posted by Glennbo

What happens if you only use REAPER, and never launch the other DAWs?

I never lose communication with the 5 pin midi on my Behringer UMC1820 or the USB midi from my Akai MPD26 using REAPER, but I never launch any other DAWs. Just wondering if using one of the other DAWs could leave midi looking to the OS like it's still in use. Also, I leave my UMC1820 powered on pretty much all the time if that makes any difference.

I only ever try Ardour and Mixbus if and when Reaper has lost the connection to see if the issue is system wide.

I plug and unplug my 204HD all the time given it has no power switch and I like to use my desktop speakers and internal soundcard with firefox.

I can have cadence open, pulseaudio killed, pulseaudio daemon running etc but only Reaper ever has the issue. I need to drill down when this happens but I think it is immediately after starting Reaper up versus it happening mid-session.

EDIT: Confirmed. As soon as I go to arm a track after startup some times (not all the time! ), I only see hw:virmidi stuff (plus the other virtual keyboards). Only a system restart fixed it temporarily.

[lilith93]

Originally Posted by JamesPeters

Cross-posting my reply here: I can't reproduce that with 6.10.

Are you running scripts or something?

I think it's due to my settings. I have another installation on a laptop and the problem does not occur there. I'll make some test with a fresh project and see.
I only have SWS and Reapack installed, but nothing is running by default.

Thanks.

[Held]

When you increase the default font size in libSwell.colortheme, many GUI elements don't scale accordingly. See the screenshot with examples from t preferences menu and the actions window.



Since fonts are really small on my screen, I really need to increase the font size considerable to work comfortably. A fix or solution would be greatly appreciated.

(I posted about this also in a new thread, but didn't get any responses. Maybe due to a poorly chosen title...)

[Hypex]

Another issue I have noticed. When quitting and a few project tabs are open. It will ask in turn to save each project. Some I do and some I don't. The first project seems okay but on the other ones the yes or no widget responds but Reaper sits there as if doing nothing. Sometimes I can keep pressing it and it will Reaper will continue. But most of the time I need to cancel it and quit again.

[Nixon]

Bug:

If I have the track fx window open and switch between vst and js plugins with down/up arrow the keyboard focus gets stolen when i stay for longer than ~ 1 second on a js plugin and i can't switch to the next plugin. This doesn't happen on a vst instance. Doesn't happen on mac (6.12 dev cycle)


reaper 6.12+dev0717
mx linux, fluxbox

[Nixon]

Bug:

If I press "show track fx window" on an empty track. The "add fx to" window (desired) has focus for a short period of time but then the "track fx" window gets focus. So I have to re-select "add fx to".


Reaper 6.12+dev0717
mx linux, fluxbox

[frol1607]

Hello,
I'm not quite sure how to generate a proper bug report so I'm posting here in the hope that someone can either point me in the right direction or otherwise correct the errors of my ways.

Anyway, as the title says, some Windows VST:s do not work properly in REAPER under the latest version of Linvst. For example, the VST BC Chorus 4 from Blue cat audio does work if loaded in a project, but only if a generic GUI is used. If I try to show the GUI Reaper for Linux (6.12c, under OpenSUSE Tumbleweed, Wine-staging 5.13) Reaper hangs.

I'm pretty sure the problem lies within REAPER - If the exact same plugin is loaded in Ardour the gui is shown.

The problem can be reproduced everytime. Other plugins work perfectly, for example Raum from NI, Azurite from Disorque (another nice Chorus), Sforzando from Plouge, etc.

Thank you for your time. Again, I'm quite a forum and bugreporting noob, so if I've done bad, feel free to correct the errors of my ways.

Best regards,
Fredrik.

P.S. Reaper for Linux really is completely awesome. Even with these minor annoyances. Like I said, the plugins from Blue Cat Audio work and sound great. You just have to use the generic GUI in Reaper to use them.

[Majesticzeo]

Linux version 6.14. In version 5.97 correctly.

[Hypex]

Hi guys. I've found a bug in the Track Manager. It opened fine but when I clicked on the window close widget Reaper locked up. It entered into some kind of endless loop as it stopped responding and my fan noise increased. I installed the latest 6.15 build and the problem still occurs. It prevents reopening the project as Reaper reopens the Track Manager window and immediately locks up again. It has to be force closed. Linux reports no crash log.

[shosty]

Originally Posted by Hypex

Hi guys. I've found a bug in the Track Manager. It opened fine but when I clicked on the window close widget Reaper locked up. It entered into some kind of endless loop as it stopped responding and my fan noise increased. I installed the latest 6.15 build and the problem still occurs. It prevents reopening the project as Reaper reopens the Track Manager window and immediately locks up again. It has to be force closed. Linux reports no crash log.

I've been seeing similar behaviour with the midi editor window recently. I thought it was just a particular project but I experienced with another project as well.

[Hypex]

Originally Posted by shosty

I've been seeing similar behaviour with the midi editor window recently. I thought it was just a particular project but I experienced with another project as well.

I wish I didn't open it now! I just found I can't reopen Reaper at all even if I tell it not to reopen the project. I'll need to check the Reaper config files for open windows and wipe it out. :-)

[Xasman]

Originally Posted by Hypex

Hi guys. I've found a bug in the Track Manager. It opened fine but when I clicked on the window close widget Reaper locked up. It entered into some kind of endless loop as it stopped responding and my fan noise increased. I installed the latest 6.15 build and the problem still occurs. It prevents reopening the project as Reaper reopens the Track Manager window and immediately locks up again. It has to be force closed. Linux reports no crash log.

Can't reproduce that here (Ubuntu 20.04 with REAPER 6.15). Track Manager opens and closes fine every time. Tried changing the visibilty of tracks in both TCP and MCP and also changing track colours - no probs at all. Can you provide any specific steps to reproduce the problem?

[shosty]

Originally Posted by Hypex

I wish I didn't open it now! I just found I can't reopen Reaper at all even if I tell it not to reopen the project. I'll need to check the Reaper config files for open windows and wipe it out. :-)

Ouch, that's not good!
I wonder if there is some wider problem. I saw a post on reddit about a user getting the same thing with Marker Manager in a dock.

[Xasman]

Originally Posted by shosty

I've been seeing similar behaviour with the midi editor window recently. I thought it was just a particular project but I experienced with another project as well.

Again, no probs here with that, either. Steps to reproduce?

[shosty]

Originally Posted by Xasman

Again, no probs here with that, either. Steps to reproduce?

Nothing special, simply open the editor and close it. It seemed to be fine with an empty or template project which is why I assumed it was just one project doing something weird. I can try to share the project without the audio when I get home next week, perhaps it will be reproducible then.

[Hypex]

Originally Posted by Xasman

Can't reproduce that here (Ubuntu 20.04 with REAPER 6.15). Track Manager opens and closes fine every time. Tried changing the visibilty of tracks in both TCP and MCP and also changing track colours - no probs at all. Can you provide any specific steps to reproduce the problem?

I'm using it on Linux Mint 19.3 Cinnamon x64. I just reopened it to see what I had opened. So I also had opened the Actions and Marker Manager windows previously if it helps. I also discovered the debugger console from the Actions window and had opened that to see what it was then closed it. When I opened up the Track Manager initially to check it out it was fine. I played with the colour widgets briefly. Then pressed "X" to close it. And the problem came.


Reaper is blaming the last project. But I can see no settings in there for the Track Manager. And Reaper already opens the window on start up so it's gone before it checks the project.

[Xasman]

Sorry, I tried all the things you mentioned - still no problems with closing the Track Manager window here.

One thought though, since you mentioned ReaConsole and Marker List from SWS - are you running the latest SWS extension (currently 2.12.1.0)?

[Hypex]

Originally Posted by Xasman

Sorry, I tried all the things you mentioned - still no problems with closing the Track Manager window here.

One thought though, since you mentioned ReaConsole and Marker List from SWS - are you running the latest SWS extension (currently 2.12.1.0)?

Actually I meant just the standard Reaper windows available from the View menu. I don't have SWS installed for Linux. My Linux install is almost as generic as you could get but I could do an isolation test. Okay finished. It found my settings and ruined it. :-)

[shosty]

SWS comes automatically bundled with the linux reaper builds doesn't it?

[Hypex]

Originally Posted by shosty

SWS comes automatically bundled with the linux reaper builds doesn't it?

On OSX it had to be installed separately. It added an SWS section. But I don't recall it being part of Reaper. I just cancelled the window in ini settings. No sign of SWS in my actions. But now I stuffed it up. The window opens and closes now, I changed too many projects I can see. I reloaded what was in the tab and now the bug doesn't occur. Why didn't Linux log a crash log! Maybe there is a force crash log somewhere.

[Xasman]

Originally Posted by shosty

SWS comes automatically bundled with the linux reaper builds doesn't it?

No, it doesn't.

[Xasman]

Originally Posted by Hypex

Actually I meant just the standard Reaper windows available from the View menu. I don't have SWS installed for Linux. My Linux install is almost as generic as you could get but I could do an isolation test. Okay finished. It found my settings and ruined it. :-)

Ah, I see - OK. In that case, did you try a portable install?

[Hypex]

Originally Posted by Xasman

Ah, I see - OK. In that case, did you try a portable install?

No, I thought I had, but I simply unpacked the Reaper archive and ran it from that location. It still found my normal config files. But I messed things up when I was backing up the bad config, because I managed to backup a good config and then fix the bad one, so now have no bad config example file left.


The reaper.ini did contain this:

[trackmgr]
wnd_vis=1

[Xasman]

Originally Posted by Hypex

No, I thought I had, but I simply unpacked the Reaper archive and ran it from that location...

You can try doing exactly that again, but after extracting, go to the REAPER sub folder (the folder named REAPER on the same level as the install-reaper.sh and the readme-linux.txt files). Inside that folder, create a new, empty file and name it reaper.ini (I do this using touch from a terminal, i.e. navigate to the REAPER folder and type "touch reaper.ini" without the quotes, then hit enter).

Now, simply run REAPER from the reaper executable file in the same folder and it will automatically populate the folder with everything needed for it to be a self-contained, portable install.

P.S. Sorry if I'm "teaching my grandmother to suck eggs" here - just wanted the explanation to be nice and clear...

[Hypex]

Originally Posted by Xasman

Now, simply run REAPER from the reaper executable file in the same folder and it will automatically populate the folder with everything needed for it to be a self-contained, portable install.

Okay that worked. Unfortunately a blank template wasn't much help. I haven't been able to reproduce it. I rushed to fix the broken config file so it would load but was too quick as I hadn't backed up an exact copy first. I haven't been able to duplicate another "broken" config nor the steps to reproduce it. It wouldn't go away at first but now it won't come back!

P.S. Sorry if I'm "teaching my grandmother to suck eggs" here - just wanted the explanation to be nice and clear...

LOL. Thanks. I can understand. :-D

[Xasman]

Originally Posted by Hypex

Okay that worked.

Glad to hear it.

Originally Posted by Hypex

...It wouldn't go away at first but now it won't come back!

Ah, 'twas ever thus...

[kfj452]

Originally Posted by Justin

That means that it could not load the plug-in. It might be helpful to remove that line, run REAPER from a terminal, and see if it prints any relevant output when scanning the plug-in.

I tried loading the plug-in, and on the first scan it reported:[code
swell: dlopen() failed: /home/deadbeef/.vst/sig/Signalizer.so: undefined symbol: glDrawArrays
[/code]
The cause of this is that the plug-in needs to be linked with -lGL, and was not (it assumes the host preloads GL). So, I edited reaper-vstplugins64.ini, removed that line, then ran REAPER using:

LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libGL.so ./reaper

(that path may vary on your system)

and lo and behold, the plug-in works. Maybe you can email the author and see if they'll add -lGL to the link line?

With your comment and some help from ChatGPT I got this working on Ubuntu 22.04 with fish shell:

env LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libGL.so.1 reaper

So we can contact the developer and have them do something to make this work without this step?

[chmaha]

Originally Posted by kfj452

With your comment and some help from ChatGPT I got this working on Ubuntu 22.04 with fish shell:

env LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libGL.so.1 reaper

So we can contact the developer and have them do something to make this work without this step?

You are responding to a 5-year-old post But Justin seemed to give you the answer already:

Maybe you can email the author and see if they'll add -lGL to the link line?