INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Broadcasting could not start on the 'ALSA' output  (Read 71 times)

JohnDoeSama

  • Member
  • *
  • Posts: 2
Broadcasting could not start on the 'ALSA' output
« on: June 30, 2024, 10:02:48 am »

Hello everyone,

After some fruitless research, I'm opening this ticket about a problem I'm having with JRiver on Linux Mint.

Indeed, after setting my audio output to my DAC in direct connection with ALSA, when I start playing a track, I get this error message :
Quote
Diffusion problem

Details :
Broadcasting could not start on the 'ALSA' output in 48hz 2ch format. [...]


To wit:
- I have no problems with the Windows version.
- I can use my DAC outside JRiver
- I've tried to authorize my various sample rates on the pipewire configuration
- It already worked! It didn't work at first, then it started to work, then it doesn't work anymore... I can't figure out what triggered these changes in behavior or how to make it work again.

Attached to the post:
- jriver's error message
- my pipewire config
- my audio output in jriver
- my configuration in dsp


I thank you in advance for your help and remain at your disposal to provide any further information.

EDIT : I corrected my pipewire config (196000 > 96000) but the problem is still there.
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13609
Re: Broadcasting could not start on the 'ALSA' output
« Reply #1 on: Yesterday at 11:24:51 am »

MC doesn't use pipewire, it uses ALSA.
Your settings look OK to me.
Try turning on logging and posting a log here or email to bob (at) jriver (dot) com.
The audio device open is extensively logged.
Logged

JohnDoeSama

  • Member
  • *
  • Posts: 2
Re: Broadcasting could not start on the 'ALSA' output
« Reply #2 on: Yesterday at 01:59:30 pm »

Thanks for your feedback Bob.
Attached are the logs.

The error seems to come from the fact that ALSA is already busy.
Code: [Select]
0005097: 140457560495680: Playback: CALSAPlugin::OpenALSA: Opening audio device hw:CARD=M2496,DEV=0 failed, Error = Périphérique ou ressource occupé
I've investigated and it seems to be coming from the EasyEffect application I'm using as a DSP. When I turn it off, MC works fine.

The problem is that I'd like to be able to cohabit the two.
Any leads?

Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13609
Re: Broadcasting could not start on the 'ALSA' output
« Reply #3 on: Today at 08:11:18 am »

Thanks for your feedback Bob.
Attached are the logs.

The error seems to come from the fact that ALSA is already busy.
Code: [Select]
0005097: 140457560495680: Playback: CALSAPlugin::OpenALSA: Opening audio device hw:CARD=M2496,DEV=0 failed, Error = Périphérique ou ressource occupé
I've investigated and it seems to be coming from the EasyEffect application I'm using as a DSP. When I turn it off, MC works fine.

The problem is that I'd like to be able to cohabit the two.
Any leads?
You can't do that if you want to use the hw: device. That's really specifying exclusive access by MC.
You could use the default or pulse audio server entries. That will require DSP studio in MC to be set to whatever the default pulse sample rate is (usually 48k but can be changed) for all sample rates.
Optionally there is a pulse pipewire pseudo device. I don't think you have that shim installed, I don't see it in you audio device list.
If you do a search for pipewire in this forum you'll see some previous topics that may be useful.
Logged
Pages: [1]   Go Up