Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER for Linux

Reply
 
Thread Tools Display Modes
Old 03-24-2021, 07:49 PM   #1
Ral-Clan
Human being with feelings
 
Ral-Clan's Avatar
 
Join Date: Oct 2008
Posts: 141
Default Reaper isn't seeing my ALSA device

Hi,

I just upgraded my computer to a newer one (a used i5). I've installed Lubuntu 20.04 on it (my old machine had 18.04). Lubuntu is built on an Ubuntu core with a light user interface.

I transplanted my sound card into the new computer: a M-Audio 192 Audiophile.

With the old computer Reaper could "see" my audio card. On the old machine if I selected (in Preferences) "Audio System: ALSA", I would then see several options for hardware inputs and outputs in the "Input Device" and "Output Device" drop down menus.

With this new machine these dropdown menus are blank. Reaper also complains upon startup that "There was an error opening the audio hardware: ALSA: error opening input device".

Other software on this machine (like Audacity) detects the card and the inputs/outputs. For example, I have the input set in Audacity to:
M Audio Audiophile 192; ICE1724 (hw0:0)

Reaper used to show these types of selections on my old machine.

I'm using Reaper 6.25 (Linux version).

If anyone has a clue as to what I'm doing wrong I would appreciate the help!

Thanks!
Ral-Clan is offline   Reply With Quote
Old 03-25-2021, 07:35 AM   #2
JamesPeters
Human being with feelings
 
Join Date: Aug 2011
Location: Near a big lake
Posts: 3,943
Default

Once you select "Audio System: ALSA" in Reaper, did you click on the drop-down boxes for "input device" and "output device"? Some people see the blank default state of those boxes and assume there are no options, so they don't click on the boxes to see that the device options are there.

The error that Reaper provides is normal if you haven't explicitly selected input/output devices.

In Audacity does it say "ALSA" in the left drop-down box? I assume that it does, but for some reason if ALSA doesn't work in both programs that might be a hint about the problem.

Anyway you can try removing the card, blowing out dust from the slot, then re-seating the card in its slot (or try another slot). Also you can set PCIE_ASPM to "performance", in case that's causing an issue. I use TLP to do that (and its frontend TLPUI). I also set the CPU frequency governor to "performance" and because I use a USB audio device, I turn USB_autosuspend off (this is required, otherwise the USB device will be unreliable with ALSA).
JamesPeters is offline   Reply With Quote
Old 03-25-2021, 01:05 PM   #3
Ral-Clan
Human being with feelings
 
Ral-Clan's Avatar
 
Join Date: Oct 2008
Posts: 141
Default

Quote:
Once you select "Audio System: ALSA" in Reaper, did you click on the drop-down boxes for "input device" and "output device"?
Thank you. That was it ---- sort of.

I had been clicking in the drop down slot for input and output device. In fact I tried many times. However, I was apparently not clicking on the *exact* pixel area occupied by the tiny black down-arrow symbol at the right end of the slot.

By merely clicking in the grey bar of the slot (which is 95% of it) Reaper was expecting me to enter my audio card info manually (i.e. type it in) and indeed a cursor was appearing in the slot (although the cursor being very thin and light blue, it was not very obvious at first).

It was only when I clicked exactly on the black down arrow symbol at the very right end of the drop down bar that the choices for my hardware showed themselves.
Ral-Clan is offline   Reply With Quote
Old 11-18-2022, 10:31 AM   #4
nolman
Human being with feelings
 
nolman's Avatar
 
Join Date: Feb 2008
Location: ghent, Belgium
Posts: 336
Default

Just had that same problem, very unhelpfull design...
nolman is offline   Reply With Quote
Old 11-18-2022, 03:06 PM   #5
michael diemer
Human being with feelings
 
Join Date: Sep 2013
Location: Maine
Posts: 1,153
Default

It happened to me also awhile back. Nobody could figure it out, but eventually I did. Probably happens a lot, and it really should be fixed.
__________________
Go forth confidently in the direction of your dreams. Live the life you've imagined - Thoreau
michael diemer is offline   Reply With Quote
Old 02-10-2023, 10:22 AM   #6
jonboy3650
Human being with feelings
 
jonboy3650's Avatar
 
Join Date: Jan 2022
Location: England
Posts: 45
Default OMG Thank you!!!

Can't believe this is still an issue. First time Linux install - was just about to do all kinds of .conf edits to fix a non error!
jonboy3650 is offline   Reply With Quote
Old 02-10-2023, 10:52 AM   #7
Wallaby
Human being with feelings
 
Wallaby's Avatar
 
Join Date: Jul 2021
Location: Swiss Zürich
Posts: 813
Default Interface

Seems to be a driver problem.
The M-audio driver has not loaded.
Download the latest Linux driver for this interface and install it.
otherwise the interface is broken.
Wallaby is offline   Reply With Quote
Old 02-10-2023, 12:24 PM   #8
chmaha
Human being with feelings
 
chmaha's Avatar
 
Join Date: Feb 2021
Posts: 2,261
Default

Quote:
Originally Posted by Wallaby View Post
Seems to be a driver problem.
The M-audio driver has not loaded.
Download the latest Linux driver for this interface and install it.
otherwise the interface is broken.
Not a driver issue. This device works out of the box. Sounds like all that was needed was to select the card in the REAPER dialog box after choosing ALSA.
__________________
ReaClassical -- Open Source Classical Music Editing Tools for REAPER | Donate via PayPal, Liberapay or Stripe
airwindows JSFX ports | Debian & Arch Pro Audio Guides
chmaha is offline   Reply With Quote
Old 02-11-2023, 12:43 AM   #9
Mikobuntu
Human being with feelings
 
Mikobuntu's Avatar
 
Join Date: Nov 2020
Posts: 153
Default

**clicking on the *exact* pixel area occupied by the tiny black down-arrow**

I had this problem too when I 1st used Reaper, I'm unsure if this bug has been reported tho.
Mikobuntu is offline   Reply With Quote
Old 02-11-2023, 02:30 AM   #10
chmaha
Human being with feelings
 
chmaha's Avatar
 
Join Date: Feb 2021
Posts: 2,261
Default

Quote:
Originally Posted by Mikobuntu View Post
**clicking on the *exact* pixel area occupied by the tiny black down-arrow**

I had this problem too when I 1st used Reaper, I'm unsure if this bug has been reported tho.
This?:



There's no "exactness" needed as you don't even have to click on the black arrow itself to bring up the list of devices, just the general vicinity. Granted, it makes no sense to have the ability to click and type in the box (at least I don't think so) so a +1 to make it a simple dropdown However, note that in that Audio Device dialog every other box with an arrow behaves in the same way aside from the audio system dropdown which has a predetermined discrete set of options. Perhaps this is a limitation when the dropdowns are dynamically filled (or can accept other numeric values)? Note that in other options tabs, those with static discrete options do behave correctly.
__________________
ReaClassical -- Open Source Classical Music Editing Tools for REAPER | Donate via PayPal, Liberapay or Stripe
airwindows JSFX ports | Debian & Arch Pro Audio Guides

Last edited by chmaha; 02-11-2023 at 02:44 AM.
chmaha is offline   Reply With Quote
Old 02-11-2023, 10:37 AM   #11
michael diemer
Human being with feelings
 
Join Date: Sep 2013
Location: Maine
Posts: 1,153
Default

Yes it is a problem, because the fonts Reaper uses are ridiculously small, and the devs simply don't care about it, as the issue has been raised repeatedly. I have given up on it. They just don't seem to get that many people (older folks for example) don't have perfect vision.
__________________
Go forth confidently in the direction of your dreams. Live the life you've imagined - Thoreau
michael diemer is offline   Reply With Quote
Old 02-11-2023, 10:48 AM   #12
axel_ef
Human being with feelings
 
axel_ef's Avatar
 
Join Date: Jan 2007
Location: Erfurt
Posts: 787
Default

Quote:
Originally Posted by michael diemer View Post
Yes it is a problem, because the fonts Reaper uses are ridiculously small, and the devs simply don't care about it...
You can adjust font size in /home/username/.config/REAPER/libSwell.colortheme
axel_ef is online now   Reply With Quote
Old 02-11-2023, 03:57 PM   #13
dylan.w
Human being with feelings
 
Join Date: May 2021
Posts: 83
Default

Tweaking the libswell is unfortunately not enough to smooth out all of the UI quirks within Reaper's menus. Increasing the font size means some longer checkbox labels are cut off in the preferences menu and other menu dialogs within Reaper.

I've been caught out by that same drop down menu also.
dylan.w is offline   Reply With Quote
Old 02-11-2023, 04:06 PM   #14
dylan.w
Human being with feelings
 
Join Date: May 2021
Posts: 83
Default

The main issue is inconsistent behaviour for the drop down menus. Some drop downs work when clicking the label area, others require a more precise click on an arrow.

From memory (it's been a while since I looked at the libswell), there are actually 2 different kinds of drop down menus but there is no way for the user to distinguish between them, so the behaviour of the drop downs is basically unpredictable

Edit: looks like there's one drop down that accepts text entry and one that doesn't. The text entry kind is what is used for the input/output device menu. It's handy for things like the FX browser but not sure that it makes sense here.

Last edited by dylan.w; 02-11-2023 at 04:57 PM.
dylan.w is offline   Reply With Quote
Old 02-12-2023, 05:38 AM   #15
axel_ef
Human being with feelings
 
axel_ef's Avatar
 
Join Date: Jan 2007
Location: Erfurt
Posts: 787
Default

Quote:
Originally Posted by dylan.w View Post
Tweaking the libswell is unfortunately not enough to smooth out all of the UI quirks within Reaper's menus. Increasing the font size means some longer checkbox labels are cut off in the preferences menu and other menu dialogs within Reaper.
I have no problems with checkbox labels in Linux.
Attached Images
File Type: png reaper_3.png (84.7 KB, 59 views)
axel_ef is online now   Reply With Quote
Old 02-12-2023, 05:50 AM   #16
dylan.w
Human being with feelings
 
Join Date: May 2021
Posts: 83
Default

Quote:
Originally Posted by axel_ef View Post
I have no problems with checkbox labels in Linux.
It doesn't really look like you've increased the size of the font by much, if at all? But cool if it's working out for you.

When the there is enough room for the label there's no issue. When the font is bigger or the space is tighter, issues come up. Usually in the Media Item Properties menu, grid menu or routing window.

The libswell theme allows 1 default font size throughout all of Reaper's menus. On my system that means I can set it to 11pt without any quirks, but 11 is still pretty small on my screen, so I imagine for others it might be uncomfortable also.
dylan.w is offline   Reply With Quote
Old 02-12-2023, 05:56 AM   #17
axel_ef
Human being with feelings
 
axel_ef's Avatar
 
Join Date: Jan 2007
Location: Erfurt
Posts: 787
Default

my font size is 12 on 1440x900 screen

Code:
default_font_face Roboto
default_font_size 12
menubar_height 22
menubar_font_size 12
menubar_spacing_width 10
menubar_margin_width 6
scrollbar_width 10
scrollbar_min_thumb_height 4
combo_height 20
_3dface #eff0f1
_3dshadow #9AA4AE
_3dhilight #D0D0D0
_3ddkshadow #ffffff
button_bg #FCFCFC ; defaults to _3dface
button_text #000000
button_text_disabled #808080
button_shadow #9AA4AE
button_hilight #D0D0D0
checkbox_text #000000
checkbox_text_disabled #808080
checkbox_fg #262626
checkbox_inter #BFBFBF
checkbox_bg #ffffff
scrollbar #202020
scrollbar_fg #a0a0a0
scrollbar_bg #ffffff
edit_cursor #262626
edit_bg #ffffff
edit_bg_disabled #c3c3c3
edit_text #000000
edit_text_disabled #808080
edit_bg_sel #3daee9
edit_text_sel #FFFFFF
; edit_hilight #D0D0D0 ; defaults to _3dhilight
; edit_shadow #9AA4AE ; defaults to _3dshadow
info_bk #A3ACAC
info_text #2F3333
menu_bg #ffffff ; defaults to _3dface
menu_shadow #ffffff ; defaults to _3dshadow
; menu_hilight #dadada ; defaults to _3dhilight
; menu_text #000000 ; defaults to button_text
menu_text_disabled #808080
menu_bg_sel #3daee9 ; defaults to menu_text
menu_text_sel #FFFFFF ; defaults to menu_bg
menu_scroll #404040
; menu_scroll_arrow #606060 ; defaults to _3dshadow
menu_submenu_arrow #575757
menubar_bg #dee0e2 ; defaults to menu_bg
menubar_bg_inactive #eff0f1
menubar_text #000000 ; defaults to menu_text
menubar_text_disabled #EBEBEB
menubar_bg_sel #3daee9 ; defaults to menu_bg_sel
menubar_text_sel #FFFFFF ; defaults to menu_text_sel
trackbar_track #FCFCFC
trackbar_mark #606060
trackbar_knob #303030
progress #1A73E8
; label_text #000000 ; defaults to button_text
; label_text_disabled #808080 ; defaults to button_text_disabled
; combo_text #000000 ; defaults to button_text
; combo_text_disabled #808080 ; defaults to button_text_disabled
combo_bg #FCFCFC
combo_bg2 #ffffff
combo_shadow #9AA4AE
combo_hilight #D0D0D0 ; defaults to _3dhilight
combo_arrow #000000
; combo_arrow_press #FCFCFC ; defaults to _3dhilight
listview_bg #FAFAFA
listview_bg_sel #3daee9
listview_text #000000
listview_text_sel #FFFFFF ; defaults to listview_text
; listview_grid #FCFCFC ; defaults to _3dhilight
listview_hdr_arrow #606060
; listview_hdr_shadow #dadada ; defaults to _3dshadow
; listview_hdr_hilight #ffffff ; defaults to _3dhilight
listview_hdr_bg #ffffff ; defaults to _3dface
; listview_hdr_text #000000 ; defaults to button_text
treeview_text #000000
treeview_bg #FAFAFA
treeview_bg_sel #3daee9
treeview_text_sel #FFFFFF
treeview_arrow #404040
tab_shadow #9AA4AE
tab_hilight #9AA4AE
tab_text #000000
focusrect #d6d6d6
group_text #000000
group_shadow #CECECE ; defaults to _3dshadow
group_hilight #eeeeee; defaults to _3dhilight
focus_hilight #3daee9
axel_ef is online now   Reply With Quote
Old 02-12-2023, 06:07 AM   #18
dylan.w
Human being with feelings
 
Join Date: May 2021
Posts: 83
Default

Quote:
Originally Posted by axel_ef View Post
my font size is 12 on 1440x900 screen

Code:
default_font_face Roboto
default_font_size 12
menubar_height 22
menubar_font_size 12
menubar_spacing_width 10
menubar_margin_width 6
scrollbar_width 10
scrollbar_min_thumb_height 4
combo_height 20
_3dface #eff0f1
_3dshadow #9AA4AE
_3dhilight #D0D0D0
_3ddkshadow #ffffff
button_bg #FCFCFC ; defaults to _3dface
button_text #000000
button_text_disabled #808080
button_shadow #9AA4AE
button_hilight #D0D0D0
checkbox_text #000000
checkbox_text_disabled #808080
checkbox_fg #262626
checkbox_inter #BFBFBF
checkbox_bg #ffffff
scrollbar #202020
scrollbar_fg #a0a0a0
scrollbar_bg #ffffff
edit_cursor #262626
edit_bg #ffffff
edit_bg_disabled #c3c3c3
edit_text #000000
edit_text_disabled #808080
edit_bg_sel #3daee9
edit_text_sel #FFFFFF
; edit_hilight #D0D0D0 ; defaults to _3dhilight
; edit_shadow #9AA4AE ; defaults to _3dshadow
info_bk #A3ACAC
info_text #2F3333
menu_bg #ffffff ; defaults to _3dface
menu_shadow #ffffff ; defaults to _3dshadow
; menu_hilight #dadada ; defaults to _3dhilight
; menu_text #000000 ; defaults to button_text
menu_text_disabled #808080
menu_bg_sel #3daee9 ; defaults to menu_text
menu_text_sel #FFFFFF ; defaults to menu_bg
menu_scroll #404040
; menu_scroll_arrow #606060 ; defaults to _3dshadow
menu_submenu_arrow #575757
menubar_bg #dee0e2 ; defaults to menu_bg
menubar_bg_inactive #eff0f1
menubar_text #000000 ; defaults to menu_text
menubar_text_disabled #EBEBEB
menubar_bg_sel #3daee9 ; defaults to menu_bg_sel
menubar_text_sel #FFFFFF ; defaults to menu_text_sel
trackbar_track #FCFCFC
trackbar_mark #606060
trackbar_knob #303030
progress #1A73E8
; label_text #000000 ; defaults to button_text
; label_text_disabled #808080 ; defaults to button_text_disabled
; combo_text #000000 ; defaults to button_text
; combo_text_disabled #808080 ; defaults to button_text_disabled
combo_bg #FCFCFC
combo_bg2 #ffffff
combo_shadow #9AA4AE
combo_hilight #D0D0D0 ; defaults to _3dhilight
combo_arrow #000000
; combo_arrow_press #FCFCFC ; defaults to _3dhilight
listview_bg #FAFAFA
listview_bg_sel #3daee9
listview_text #000000
listview_text_sel #FFFFFF ; defaults to listview_text
; listview_grid #FCFCFC ; defaults to _3dhilight
listview_hdr_arrow #606060
; listview_hdr_shadow #dadada ; defaults to _3dshadow
; listview_hdr_hilight #ffffff ; defaults to _3dhilight
listview_hdr_bg #ffffff ; defaults to _3dface
; listview_hdr_text #000000 ; defaults to button_text
treeview_text #000000
treeview_bg #FAFAFA
treeview_bg_sel #3daee9
treeview_text_sel #FFFFFF
treeview_arrow #404040
tab_shadow #9AA4AE
tab_hilight #9AA4AE
tab_text #000000
focusrect #d6d6d6
group_text #000000
group_shadow #CECECE ; defaults to _3dshadow
group_hilight #eeeeee; defaults to _3dhilight
focus_hilight #3daee9


we could continue this conversation or we could just accept that we have different setups, different resolutions (2560 x 1440), sit at different distances from the screen...etc, etc.
dylan.w is offline   Reply With Quote
Old 02-12-2023, 11:00 AM   #19
michael diemer
Human being with feelings
 
Join Date: Sep 2013
Location: Maine
Posts: 1,153
Default

This all really comes down to the oft-criticized Reaper GUI. While some complaints are based on aesthetics, it's really more about ergonomics. The eyestrain that results from poor GUIs causes headaches, stiff necks and mental fatigue. this has to turn off a lot of folks to reaper. Which is unfortunate as it is such a great product.
__________________
Go forth confidently in the direction of your dreams. Live the life you've imagined - Thoreau
michael diemer is offline   Reply With Quote
Old 02-13-2023, 03:16 PM   #20
/AND/
Human being with feelings
 
Join Date: Aug 2022
Posts: 717
Default

Quote:
Originally Posted by michael diemer View Post
This all really comes down to the oft-criticized Reaper GUI. While some complaints are based on aesthetics, it's really more about ergonomics. The eyestrain that results from poor GUIs causes headaches, stiff necks and mental fatigue. this has to turn off a lot of folks to reaper. Which is unfortunate as it is such a great product.
Don't want for the thread to get sidelined, but I agree. A vectorial (and some stylistic) overhaul is long overdue. I like how they engaged with an external designer to vectorise and improve the GUI/UX of MuseScore, proving that they (Reaper devs) don't have to do it themselves.
/AND/ is offline   Reply With Quote
Old 02-13-2023, 03:35 PM   #21
michael diemer
Human being with feelings
 
Join Date: Sep 2013
Location: Maine
Posts: 1,153
Default

Quote:
Originally Posted by /AND/ View Post
Don't want for the thread to get sidelined, but I agree. A vectorial (and some stylistic) overhaul is long overdue. I like how they engaged with an external designer to vectorise and improve the GUI/UX of MuseScore, proving that they (Reaper devs) don't have to do it themselves.
Interesting suggestion. I've been working with MuseScore lately, and I am impressed with it so far. Easy to customize. Of course, Reaper is a much more complex piece of software, so who knows if that would be an option or not?
__________________
Go forth confidently in the direction of your dreams. Live the life you've imagined - Thoreau
michael diemer is offline   Reply With Quote
Old 02-14-2023, 02:04 AM   #22
Xasman
Human being with feelings
 
Xasman's Avatar
 
Join Date: Jun 2009
Posts: 673
Default

https://forum.cockos.com/showthread.php?t=251527

Last edited by Xasman; 02-14-2023 at 02:25 AM. Reason: Origianally posted a link to an individual post by mistake. Changed to link to the entire thread instead.
Xasman is offline   Reply With Quote
Old 03-13-2024, 12:09 PM   #23
amkangas
Human being with feelings
 
Join Date: Aug 2016
Posts: 5
Default Thank you!

I just installed reaper on Lubuntu. I bought a used Lenovo Thinkpad and a used Scarlett 6i6 for my band's playback rig. And, Lubuntu was seeing the 6i6 but Reaper was not, so I knew the problem was with Reaper. After reading this post, I went back and doubled checked that drop down box in the device settings in Reaper, and sure enough, that was it. Wow.

Thanks! We now have a rock solid track playback machine with 4 discreet outputs for under $250.

God bless everyone!

www.coyotes.band
amkangas is offline   Reply With Quote
Old 03-15-2024, 04:22 PM   #24
mindlessgenius
Human being with feelings
 
mindlessgenius's Avatar
 
Join Date: Aug 2023
Posts: 325
Default

Quote:
Originally Posted by /AND/ View Post
Don't want for the thread to get sidelined, but I agree. A vectorial (and some stylistic) overhaul is long overdue. I like how they engaged with an external designer to vectorise and improve the GUI/UX of MuseScore, proving that they (Reaper devs) don't have to do it themselves.
AFAIK their designers are their own staff. But more importantly, what the Musescore team did for the redesign was rewriting the entire interface from Qt widgets to QML, so it also took plenty of dev hours. All buttons/graphical elements had to be redesigned for this and in the end the effort took more than two years.

Rewriting the whole Reaper GUI from Win32 to whatever would also render SWELL useless, since that is an emulation layer for part of the Win32 API. I'm not too optimistic for this happening.
mindlessgenius is online now   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 02:39 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.