REAPER for Linux bugs

[Jack Winter]

Please post bugs that you think are related to running REAPER on Linux in this thread.

[Glennbo]

The wet/dry sliders and highlights for them seem to be offset to the right in ReaComp.

Edit: This is on Xubuntu XFCE with an nVidia GPU.

[Andrew479]

No such issue on my arm install:

[Jack Winter]

Maybe themeing? Mine looks more or less ok too

[Glennbo]

Originally Posted by Jack Winter

Maybe themeing? Mine looks more or less ok too

It does appear to be theme related.

When I choose the stock theme, the fader handles are now in line, but overlaying large empty white vertical rectangles.



Choosing the 4.0 theme makes mine look like your screen shot. My normal theme is LCS Short Dark, which uses mostly UI bits from Imperial.

[kytdkut]

Not a bug, but I dont think this ruler font is configurable. It does not follow any font setting anywhere (theme tweak tool, libSwell.colortheme)

The small number is fine, also it's not theme related.



Anyone having this issue?

(obv a small thing, but it triggers my brain :P)

[lucas_LCS]

Originally Posted by Glennbo

The wet/dry sliders and highlights for them seem to be offset to the right in ReaComp.

Edit: This is on Xubuntu XFCE with an nVidia GPU.

looks like the fader section is being widened in Linux for some reason.
Look at the Threshold fader and you can see it has some of the same issue.
Looking at the other examples it is clear that the fader background is being stretched, but in a passable way.
This appears to be due the way the Linux version renders this part of the theme.
If it's not possible to fix in Reaper, then it may be possible to make a work-around with a different background.
These vertical faders would also need to be changed.
I'll see what I can do.
It may take a while, since I'll need to set up a Linux/Reaper install to make and test it.

[Glennbo]

Originally Posted by lucas_LCS

looks like the fader section is being widened in Linux for some reason.
Look at the Threshold fader and you can see it has some of the same issue.
Looking at the other examples it is clear that the fader background is being stretched, but in a passable way.
This appears to be due the way the Linux version renders this part of the theme.
If it's not possible to fix in Reaper, then it may be possible to make a work-around with a different background.
These vertical faders would also need to be changed.
I'll see what I can do.
It may take a while, since I'll need to set up a Linux/Reaper install to make and test it.

The stock default theme is kind of messed up too. It's missing the graphic slot on all faders, plus other UI elements, but the older 4.0 theme looks totally lined up with nothing missing or mis-aligned.

Makes me think there may be newer Walter functionality that wasn't yet in use in the 4.0 theme. I could be way off base too, but either way it's not keeping me from using it, and I totally prefer using LCS Short Dark as my one big screen theme. :-)

[JamesPeters]

I hope the theme I customized works well, lol. I spent a lot of time nitpicking the crap out of it.

I guess I'll find out soon enough...

[lilith93]

Reaper Version: v5.941 - August 4 2018

It happened to me already three times that REAPER crashes out of the blue when clicking into the time ruler while a song is playing. I didn't observe this with other versions and I can't reproduce it.

[lilith93]

Originally Posted by JamesPeters

I hope the theme I customized works well, lol. I spent a lot of time nitpicking the crap out of it.

I guess I'll find out soon enough...

Wow!!! This looks pretty awesome!

[Tobbe]

Originally Posted by JamesPeters

I hope the theme I customized works well, lol. I spent a lot of time nitpicking the crap out of it.

I guess I'll find out soon enough...

I also use Commala and I love the colors and layouts. Gonna try yours, it looks awesome.

//Tobbe

[shosty]

I've noticed that there is something not right with the midi editor and inline editing. If I have a project with quite a few Reaverbs or LSP Impulse Reverb using impulses for stuff like reverb then the playback is massively affected by opening a midi item or inline editing. I get stutters and slowed down playback when midi editing is enabled.

There is a particular some I am working on and it's nearly impossible to edit midi, even without the song playing when I open the editor my mouse goes slow and audio goes really slow. Now, this song is quite heavy with plugins and tracks but the performance meter only shows about 49% cpu use. I'm running jack at 1024 so certainly not pushing it.

The strange thing is that when you have the editor open and it is stuttering as soon as you close it the playback is fine, instantly. I would say it's like the midi editor is very cpu intensive but Reaper isn't using huge amounts of CPU when this happens.

The only thing I can pin it down to is using impulses. I noticed that in the LSP plugin if I change the FFT Frame to a high number across all instances it helps. Same thing with Reaverb.

[cfillion]

Originally Posted by shosty

The strange thing is that when you have the editor open and it is stuttering as soon as you close it the playback is fine, instantly.

Anticipative processing is turned off on tracks with open MIDI editors by default. Enable the corresponding option in Preferences > Audio > Buffering.

[Jack Winter]

And check out the zl/ll checkboxes

[shosty]

Originally Posted by cfillion

Anticipative processing is turned off on tracks with open MIDI editors by default. Enable the corresponding option in Preferences > Audio > Buffering.

Thanks, that seems to do the trick.

Originally Posted by Jack Winter

And check out the zl/ll checkboxes

That helps when using reaverb but shouldn't be acting like that with other plugins.

[Jack Winter]

Might help when rec arming tracks.

Edit: When I think about it, I guess it's tangential to the discussion, still a good trick to lower rt cpu in some situations.

[cfillion]

Speaking of Linux bugs: gfx.getfont from the API always returns an empty font name string. https://forum.cockos.com/showthread.php?p=2022793



(EDIT: FontConfig for font family recognition & flexibility instead of the hard-coded font filename scanning SWELL currently does would be nice too, I guess)

[Justin]

Originally Posted by cfillion

Speaking of Linux bugs: gfx.getfont from the API always returns an empty font name string. https://forum.cockos.com/showthread.php?p=2022793



(EDIT: FontConfig for font family recognition & flexibility instead of the hard-coded font filename scanning SWELL currently does would be nice too, I guess)

Would be nice if someone gave some example code of how to do it using FontConfig...

[cfillion]

Originally Posted by Justin

Would be nice if someone gave some example code of how to do it using FontConfig...

https://gist.github.com/cfillion/1a3...365f14958157fb

./a.out sans-serif serif monospace 'DejaVu Sans Mono' 'Andale Mono' 'Ubuntu Mono' UbuntuMono Lato
found font matching 'sans-serif': 'DejaVu Sans' in '/usr/share/fonts/TTF/DejaVuSans.ttf'
found font matching 'serif': 'DejaVu Serif' in '/usr/share/fonts/TTF/DejaVuSerif.ttf'
found font matching 'monospace': 'DejaVu Sans Mono' in '/usr/share/fonts/TTF/DejaVuSansMono.ttf'
found font matching 'DejaVu Sans Mono': 'DejaVu Sans Mono' in '/usr/share/fonts/TTF/DejaVuSansMono.ttf'
found font matching 'Andale Mono': 'DejaVu Sans Mono' in '/usr/share/fonts/TTF/DejaVuSansMono.ttf'
found font matching 'Ubuntu Mono': 'Ubuntu Mono' in '/usr/share/fonts/TTF/UbuntuMono-R.ttf'
found font matching 'UbuntuMono': 'Ubuntu Mono' in '/usr/share/fonts/TTF/UbuntuMono-R.ttf'
found font matching 'Lato': 'Lato' in '/home/cfillion/.fonts/Lato-Regular.ttf'

(bold/italic matching is commented out)

[vocalfons]

Every once in a while, Reaper doe snot respond to any keyboard input anymore. Closing Reaper and reapening it again solves. It can be quite annnoying though.....the WINE version of Reaper does not have this problem..

[clepsydrae]

Originally Posted by vocalfons

Every once in a while, Reaper doe snot respond to any keyboard input anymore. Closing Reaper and reapening it again solves. It can be quite annnoying though.....the WINE version of Reaper does not have this problem..

Shot in the dark: sometimes this can happen when a dialog window pops up that takes keyboard focus and won't release it, but the window manager has placed the window somewhere strange (e.g. behind the main window, or minimized, or off the screen, etc.) Next time you see it, try hitting escape or enter to see if it closes a dialog.

Or: try your window manager shortcut for "present windows". In Kubuntu, mine is meta-W. This usually shows all windows, visible and minimized, in a stack of some kind. You could also try alt-tab to cycle through. It will depend on whether the window manager is grouping all windows from the same application in the stack of windows, though, so you might need to tweak settings for this technique to be useful.

If you see a dialog window, you can then try to switch to it, move it, close it, figure out how to make it not appear invisibly, etc.

Just a guess; might have nothing to do with your issue. :-)

[Snap]

^ & ^^ Yes. If you are using LSP plugins, for example, they steal the cursor focus since they're not Reaper windows per se. Hover your mouse away from it and the focus wlll be back to Reaper if your window manager is configured to do that. Those kind of behaviours can be modified in WMs settings

[Glennbo]

REAPER doesn't have focus if I've been making adjustments on any Windows plugin that is bridged by LinVST, but that's not surprising since the plugin is running in WINE and not really being hosted by REAPER.

Clicking on REAPER gives it focus again, and then the keyboard works.

[stoman]

Originally Posted by Jack Winter

Please post bugs that you think are related to running REAPER on Linux in this thread.

Just noticed this thread after posting my bug finding:
https://forum.cockos.com/showthread.php?t=211174

[burtbick]

I've been working on setting up Linux Mint 18.3 to do some track editing.

I have Reaper for Linux (64 bit) installed and it works great on audio tracks, and I had one MIDI that plays just fine using FluidSynth (QSynth) with JACK. That MIDI has 8 active channels/tracks.

Then I tried another MIDI file and that one is erratic, with a bunch of stuttering and just not playing smoothly at all. This MIDI has 16 tracks

This happens either with the soft synth OR with an external HW synth through an Alesis IO2 as well as a no-name USB to MIDI interface that I have laying around.

This same MIDI plays smoothly in Ardour 4 with the soft synth. So the issue seems to be isolated to Reaper.

Using the virtual MIDI device in Reaper from a2j Virtual RawMIDI out to a2j FLUID Synth input ports. But I was NOT using a2j in earlier tests and the results were the same. In that earlier test routed from Virtual RawMIDI to FLUID Synth in the JACK ALSA tab.

I tested with Reaper (Windows 64bit) under Wine, and using the Qsynth as set up for my Linux test. In the Windows version running under Wine I have the Synth input port (number:0) and that is what I enabled and mapped to the MIDI tracks. It plays very smoothly just as the same MIDI does on my Windows machine.

Any suggestions on what I should look for to get this working smoothly with Reaper for Linux, or is this possibly a bug in Reaper for Linux?

Update: 9/17/18 Found the problem, or at least a solution.
In some earlier testing I had changed the Audio System from JACK to PulseAudio in Reaper's Preferences and had forgotten about it.
So on a hunch I changed it back to JACK and then changed the JACK MIDI routing to REAPER/MIDID Output 1 connected to a2j/FLUID SYnth input and that got rid of the stuttering. That may still not be the optimal configuration, but for now it is working.

Thanks,
Burt

[vocalfons]

I do not know if this is a bug. But in both linux-native Reaper AND under wine, my midi interface/controller bcf2000 is shown to be there in the system, it is shown in Catia, it is shown in the settings of Reaper....but it is not selectable as an in or output on a channel. It seems the system made an alias and doesnt know that it's not two devices. So now I have no more midi input or output and my mixing controller does not work either. So also in Catia I vannot connect anything to it. Anyone with a clever idea? Or maybe a dunb idea? By now I'd settle for any solution

[Tobbe]

Hi,

Add new instrument -> SFZero and Salamander Piano
Add new instrument -> Tunefish

Reaper freeze and I can't do anything but Force Quit, and restart my computer. Done this twice with same result but in different order. Both instruments are LinuxVST except soundfont in SFZ format for Salamander Piano.


Add new instrument -> SForzando and Salamander Piano
Add ner instrument -> Tunefish

Works! Well one time anyway


Updating Linux Mint Debian yesterday, that's all new. What was installed & updated I don't know. Didn't pay attention to the update.

[Jklitz]

HI

If reaper crashes the Interface will close after a wait with a wairning
asking if you want to close. But the reaper in jack server does not disconnect
and I have to kill jack and restart jack server. This happens very frequently
I use Vst plugins alot. using the Linsvt in bedded I not sure if there is a connection.

JK

[osxmidi]

Originally Posted by Jklitz

HI

If reaper crashes the Interface will close after a wait with a wairning
asking if you want to close. But the reaper in jack server does not disconnect
and I have to kill jack and restart jack server. This happens very frequently
I use Vst plugins alot. using the Linsvt in bedded I not sure if there is a connection.

JK

Why is Reaper crashing?

It could be due to a system/hardware thing or a particular plugin.

If the Reaper crash just seems to happen continually when a plugin is active then it might be that plugin and to find out if it is then the plugin needs to be removed and if Reaper doesn't crash anymore then that was it.

[osxmidi]

Originally Posted by Tobbe

Hi,

Add new instrument -> SFZero and Salamander Piano
Add new instrument -> Tunefish

Reaper freeze and I can't do anything but Force Quit, and restart my computer. Done this twice with same result but in different order. Both instruments are LinuxVST except soundfont in SFZ format for Salamander Piano.


Add new instrument -> SForzando and Salamander Piano
Add ner instrument -> Tunefish

Works! Well one time anyway


Updating Linux Mint Debian yesterday, that's all new. What was installed & updated I don't know. Didn't pay attention to the update.

I tested it on Debian stretch and I get a seg fault when Tunefish is added.

I can only use Tunefish 3 because Tunefish 4 gives an error about the glibc version.

I think it might be due to some library incompatibility because SFZero and Tunefish are ok by themselves but not when they are used together.

If Tunefish is loaded first then SFZero won't load and if SFZero is loaded first then Tunefish won't load.

[Tobbe]

Originally Posted by osxmidi

I tested it on Debian stretch and I get a seg fault when Tunefish is added.

I can only use Tunefish 3 because Tunefish 4 gives an error about the glibc version.

I think it might be due to some library incompatibility because SFZero and Tunefish are ok by themselves but not when they are used together.

If Tunefish is loaded first then SFZero won't load and if SFZero is loaded first then Tunefish won't load.

Thank you. I'm doing a reinstall just now of Mint Debian. To much garbage so I want it clean.

[osxmidi]

Originally Posted by Tobbe

Thank you. I'm doing a reinstall just now of Mint Debian. To much garbage so I want it clean.

Looking into it more, there seems to be some sort of problem with SFZero and JUCE5 (SFZero was updated to work with JUCE4 but JUCE5 seems to break it), so I would suggest not to use it until I (maybe) work out where the problem is which might take a while.

[Tobbe]

Originally Posted by osxmidi

Looking into it more, there seems to be some sort of problem with SFZero and JUCE5 (SFZero was updated to work with JUCE4 but JUCE5 seems to break it), so I would suggest not to use it until I (maybe) work out where the problem is which might take a while.

Thanks again. I was using the one with JUCE5. The one before worked perfect if I remember correctly.