Endless Loop Opening Remote

🖥️ Audirvāna Core Player
1

I’m running Audirvana Studio Linux on a sonicTransporter from Small Green Computer. The sonicTransporter is running a Ravenna ALSA driver to send audio over the network.

When I open Audirvana remote, select the sonicTransporter as the computer, it works great. As soon as I select the Ravenna driver as the output device, the remote quits. Re-opening the remote app results in an endless loop because it mustn’t like the Ravenna device and I can’t change it.

I’m running the remote on my MacBook Pro M2. I’ve uninstalled the remote, but nothing changes.

I uninstalled Audirvana from the sonicTransporter and it defaulted to the onboard audio when I reinstalled. Now I can get in, but it doesn’t explain why the Remote app quits when I select the Ravenna device.

Screenshot 2024-08-01 at 3.53.57 PM
Screenshot 2024-08-01 at 3.53.57 PM2040×1542 138 KB

2

Hi @chris, do you see something in the logs of Audirvāna when you select the Ravenna device in the Remote?

In the Audirvāna settings > My Account section you should have 'Open Log Folder’ button to access to it.

3

Hi Antoine, once I select the Ravenna device, I can no longer use the Remote app. Thus, I have no way of going to Settings > My Account > …

4

Before you select the Ravena then, do you see something in the log file?

5

I just tried Starting a Log Session, opening the log (which opens via web browser) so I could see the activity (which worked good), then selecting the Ravenna device. As soon as I selected the Ravenna device the remote quit and the log was no longer accessible.

The only way to get back into Audirvana is to uninstall it on the sonicTransporter and reinstall.

6

Ok, so It’s either Audirvāna Linux or the Remote that crash. Can you copy and paste everything you have the logs in a text file and send it at [email protected] so I can review your logs with Damien?

7

Sure, but it will be pretty plain because I can only access the log before the crash.

8

:notes: :eye: :headphones: :eye: :notes:

9

That’s of course the driver that’s installed, but I don’t follow the reason for your post.

10

The Butler daemon part is responsible for:

  • Communication and configuration of the LKM
  • High level RAVENNA/AES67 protocol implementation
    • mDNS discovery
    • SAP discovery
  • RAVENNA devices sample rate arbitration
  • Web server
  • Remote volume control

Note : The Butler daemon cannot be launched if the LKM has not been previously inserted. The LKM cannot be removed as long as the daemon is running

11

Again, that’s the driver that’s installed and working, but I don’t follow the reason for your posts. It’s Audirvana that’s quitting when I select the Ravenna driver.

The driver works with other apps.

12

ALSA (Linux) AES67-RAVENNA Driver Forum
https://forum.merging.com/viewforum.php?f=73

:notes: :eye: :headphones: :eye: :notes:

13

I will contact Merging about it since I gave them access to Audirvāna Studio in May so they can reproduce issues their users could come up to them.

They can probably reproduce the behavior you have.

14

Hi @Antoine I’ve been testing the sonicTransporter further this week and have other apps successfully using the Ravenna output. It seems to be an Audirvana issue.

I’m unsure if the issue is related to Audirvana’s Remote app or Audirvana on Linux. In any case, it seems like the remote app should at least be able to function so I can select a different output device, rather than have to uninstall Audirvana and reinstall, to get it back up.

It would be great to get Audirvana on Linux working with a Ravenna output.

15

To be sure about this case, do you have to install a driver to use Ravenna?

16

The Ravenna driver is installed via the sonicTransporter web interface, just like Audirvana is installed.

IMG_2958
IMG_29581290×2796 396 KB

1 Like
17

OK, I will contact Merging to try this out on our side.