Problem with openSuseleap 15

Installation & Configuration Linux
#1

Hi I downloaded 3 days ago Ardour. Installed on openSuseleap 15.0
Ardour 5,12.0
Qjackctl 4.0
jackdmp 1.9.12

I used to work with Ardour some 4 years ago and did not expect any problems
I can create a session with Alsa
but the session basically doea not work eg. transport head moves very slow no audio out put.
Can not create a session using jack at all !!!

Where would I look for error msg ? Installation report was fine except the user has no "realtime " permission.

Any idea ? I am stuck at the very beginning .

Thank Otto

#2

Is Jack running and do you get sound through it with other applications? Is Jack2 installed?

http://jackaudio.org/downloads/
https://qjackctl.sourceforge.io

#3

Check this also: https://community.ardour.org/node/15690

#4

Jack is running.
…where could I find a log-file ?

#5

There is no log file. If you use QJackctl (and probably Cadence too) it does collect any output from JACK (if it started JACK itself).

#6

Hi
Out of the Ardour log window

[WARNING]: AlsaAudioBackend: Device Reservation failed.
[ERROR]: AlsaAudioBackend: failed to open device.
[WARNING]: AlsaAudioBackend: adjusted output channel count to match device.
[WARNING]: AlsaAudioBackend: adjusted input channel count to match device.
[WARNING]: AlsaMidiIO: Cannot acquire realtime permissions.
[WARNING]: AlsaMidiIO: Cannot acquire realtime permissions.
[WARNING]: AlsaAudioBackend: cannot acquire realtime permissions.
[INFO]: Loading bindings from /opt/Ardour-5.12.0/etc/ardour.keys
harvid version: 802
[INFO]: Loading menus from /opt/Ardour-5.12.0/etc/ardour.menus
[ERROR]: AlsaBackend::connect: Invalid Destination port: (ardour:Audio 2/audio_in 1)
[ERROR]: AlsaBackend::connect: Invalid Destination port: (ardour:Audio 2/audio_in 2)
[INFO]: Loading 88 MIDI patches from /opt/Ardour-5.12.0/share/patchfiles
[INFO]: Loading history from /home/hase/Linux/Ardour/nj/nj.history
[INFO]: nj: no history file “/home/hase/Linux/Ardour/nj/nj.history” for this session.

I did the realtime changes to my system but sofar no luck.

If someone has an idea thatt would be much appreciated.

Thanks

#7

I re-installed Ardour

linux-wkp9:/ # ‘/home/hase/Linux/Ardour/Ardour software/Ardour-5.12.0-x86_64.run’
Verifying archive integrity… All good.
Uncompressing Ardour 100%

Welcome to the Ardour installer

Ardour will be installed for user hase in /opt

Architecture is x86_64
Checking for required disk space
Bundle is on btrfs filesystem
Unpacking bundle for x86_64-gcc5
Bundle unpacked

Checking system libs to see if they are compatible with Ardour.

Installing Ardour 5.12.0 in /opt

Adding Ardour to the applications menu

Creating a desktop link for Ardour in /home/hase/Desktop

Copying uninstall script to /opt

Creating link Ardour5 in /usr/local/bin

Checking to see if Jack is installed

Jack already present

Jack Version Check OK (jackdmp version 1.9.12 tmpdir /dev/shm protocol 8)

System failed the quick sanity check… Looking for the cause

System does not allow realtime for the current user… Looking for a solution

!!! WARNING !!! - Your system seems to use frequency scaling.
This can have a serious impact on audio latency.
For best results turn it off, e.g. by choosing the ‘performance’ governor.

Press ENTER to continue:^CSignal caught, cleaning up
linux-wkp9:/ #

Same problem
Can’t create a session with jack at all

Can create a corrupt session with Alsa (no signal routing possible . no recording possible)

It looks like there is a corrupt file in the system which has not been deleted during uninstall and imports corrupt data into the new install.

I noted that the realtime issue has not been solved … will look into it.

Any idea … thanks

#8

Problem SOLVED !!!

Faulty Soundcard. Very annoying

Thanks for your help, cheers

#9

These messages:

[WARNING]: AlsaAudioBackend: adjusted output channel count to match device. [WARNING]: AlsaAudioBackend: adjusted input channel count to match device. [WARNING]: AlsaMidiIO: Cannot acquire realtime permissions. [WARNING]: AlsaMidiIO: Cannot acquire realtime permissions. [WARNING]: AlsaAudioBackend: cannot acquire realtime permissions.

have nothing to do with a faulty soundcard, but instead mean that your system is not configured to allow you access to realtime schedule (and probably memory locking).

#10

Unfortunately the soundcard was faulty… I continued testing with the motherboard native sound card and still cant open a session with jack as my audio system.
You are right pointing to the realtime issue. I did what was suggested in the Jack manual with no success.
I got rtkit-demon and polkitd running but have no idea how to let those processes know to give jackd realtime status.
Any idea how I could progress ?

Thanks for your help

#11

… PAM … is installed on my system

#12

You need to log out and in again after you’ve added the rtprio to limits.conf for it to take effect.

If you do that and then start a terminal, type ulimit -a and hit Enter you should see a “real-time priority” line with whatever you set the rtprio to.

#13

Solved it. At least one part
Now Ardour starts with the “Audio System” Jack ! (Alsa worked). What did I Do? There was a msg in the Ardour Window “Log” that the Alsa backend did not have realtime permission. After searching on the net I found an addon in “limit.conf” . I added
@audio - rtprio 95
@audio - memlock 512000
@audio - nice -19
… logged out …an then logged in…Ardour started with Jack Audio System. The operating system added the group “audio” to my user account.

Thanks and cheers