pulseaudio-dlna to chromecast initialize time

Questions about codecs, DVD playback, web plugins...
Forum rules
Before you post please read how to get help
Post Reply
BlackJackMarcus
Level 1
Level 1
Posts: 11
Joined: Tue Feb 07, 2017 2:00 am

pulseaudio-dlna to chromecast initialize time

Post by BlackJackMarcus » Fri Aug 03, 2018 7:49 pm

Hello all,
I've been using pulseaudio-dlna to send sound media to a chromecast for over a year now. It has worked like magic. Using any media player (Audacious is my preferred) it would connect/play within 3 - 5 seconds max. However suddenly the connect/play has gone to a minute or more. Without success I have been trying to recall what I may have tampered with to upset the routine. A Google or forum search hasn't come up with a clue.

A clue is when pulseaudio-dlna --debug is run I get the following error: pulseaudio_dlna.streamserver CRITICAL The streaming server could not bind to your specified port (8080). Perhaps this is already in use? The application cannot work properly!
What is a suitable alternative port?

Another clue: When the pulseaudio-dlna service is initialized I get the following error
pulseaudio_dlna.streamserver INFO Requested file not found "/dHlwZT0iaW1hZ2UiLG5hbWU9ImRlZmF1bHQucG5nIg%253D%253D/"

So far I have:
Reset the Chromecast, tried another Chromecast
purged pulseaudio-dlna and reloaded
tried various puleaudio-dna settings (coder, encoder, port, gone back to defaults)
Used a different computer
Used various media players (Audacious/VLC/Rhythmbox)

So any solutions anyone for getting the connect/play time back to 3 - 5 seconds.

My system is
System: Host: MGT-PC2 Kernel: 4.10.0-38-generic x86_64 (64 bit gcc: 5.4.0)
Desktop: Xfce 4.12.3 (Gtk 2.24.28) Distro: Linux Mint 18.3 Sylvia
Machine: Mobo: ASUSTeK model: P8P67 PRO v: Rev 1.xx
Bios: American Megatrends v: 1502 date: 03/02/2011
CPU: Quad core Intel Core i5-2500K (-MCP-) cache: 6144 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 26486
clock speeds: max: 3700 MHz 1: 1967 MHz 2: 1976 MHz 3: 1924 MHz
4: 1994 MHz
Graphics: Card: NVIDIA GF108 [GeForce GT 430] bus-ID: 01:00.0
Display Server: X.Org 1.18.4 drivers: nouveau (unloaded: fbdev,vesa)
Resolution: 1920x1080@60.00hz
GLX Renderer: NVC1
GLX Version: 3.0 Mesa 17.2.4 Direct Rendering: Yes
Audio: Card-1 NVIDIA GF108 High Definition Audio Controller
driver: snd_hda_intel bus-ID: 01:00.1
Card-2 Intel 6 Series/C200 Series Family High Definition Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0
Card-3 GYROCOM C&C driver: USB Audio usb-ID: 005-002
Card-4 Microsoft LifeCam Cinema driver: USB Audio usb-ID: 002-003
Sound: Advanced Linux Sound Architecture v: k4.10.0-38-generic
Network: Card: Intel 82579V Gigabit Network Connection
driver: e1000e v: 3.2.6-k port: f040 bus-ID: 00:19.0
IF: eno1 state: up speed: 1000 Mbps duplex: full
mac: xxx
WAN IP: xxx
IF: eno1 ip-v4: xxx
Drives: HDD Total Size: 2565.5GB (38.7% used)
ID-1: /dev/sda model: WDC_WD400BD size: 40.0GB
ID-2: /dev/sdb model: WDC_WD20EZRZ size: 2000.4GB
ID-3: /dev/sdc model: Crucial_CT275MX3 size: 275.1GB
ID-4: USB /dev/sdd model: FreeAgentDesktop size: 250.1GB
Optical: /dev/sr0 model: ASUS DRW-1814BLT
rev: 1.13 dev-links: cdrom,cdrw,dvd,dvdrw
Features: speed: 48x multisession: yes
audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition: ID-1: / size: 244G used: 19G (9%) fs: ext4 dev: /dev/sdc2
ID-2: swap-1 size: 8.56GB used: 0.05GB (1%) fs: swap dev: /dev/sdc3
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 36.0C mobo: N/A gpu: 29.0
Fan Speeds (in rpm): cpu: 0
Info: Processes: 242 Uptime: 46 days Memory: 3820.6/7959.0MB
Init: systemd runlevel: 5 Gcc sys: 5.4.0
Client: Shell (bash 4.3.481) inxi: 2.2.35

User avatar
MrEen
Level 7
Level 7
Posts: 1706
Joined: Mon Jun 12, 2017 8:39 pm

Re: pulseaudio-dlna to chromecast initialize time

Post by MrEen » Fri Aug 03, 2018 9:59 pm

Hi BlackJackMarcus.

I hadn't heard of pulseaudio-dlna before your post so had to search for it. I'm wondering if it's having trouble figuring out your IP and that's causing the delay. From the authors github page, you can start it with pulseaudio-dlna --host ip (replacing ip with your network ip address I assume.)

If that doesn't solve it, see if deleting the files in ~/.config/pulse/ helps.

Oh. Further reading shows this: pulseaudio-dlna --port 10291 --encoder flac will start pulseaudio-dlna on port 10291 and stream your PulseAudio streams encoded with FLAC

There's your port solution I hope.

BlackJackMarcus
Level 1
Level 1
Posts: 11
Joined: Tue Feb 07, 2017 2:00 am

Re: pulseaudio-dlna to chromecast initialize time

Post by BlackJackMarcus » Sat Aug 04, 2018 1:48 am

Hi MrEen, thanks for that research.
1. I deleted the files in .config/pulse - no change
2. I started pulseaudio-dlna with the ip address of the chromecast - no change
3. I started pulseaudio using port 10291 - the error message re port 8080 disappeared so I will stick with port 10291 :) . No change to initialize/play time.

Since posting on this topic I have loaded Plex, initially on clicking play the media file would start playing immediately now Plex is exhibiting the same behaviour pattern. Some buffering must be going on somewhere.

With hindsight my initial write up is not quite accurate, pulseaudio-dlna loads immediately however when subsequently selecting play in audacious or any media programme it takes 20+ seconds to play when it was almost immediate.

User avatar
MrEen
Level 7
Level 7
Posts: 1706
Joined: Mon Jun 12, 2017 8:39 pm

Re: pulseaudio-dlna to chromecast initialize time

Post by MrEen » Sat Aug 04, 2018 12:07 pm

I'm afraid as I can't test it that everything I offer would only be a shot in the dark and could make things worse.

My only suggestion is try creating a device config and see if that helps.

EDIT: Also, pulseaudio-dlna --host ip I would think is the IP of your computer, not the Chromecast. The form would be pulseaudio-dlna --host 192.168.1.100 as an example.

User avatar
MrEen
Level 7
Level 7
Posts: 1706
Joined: Mon Jun 12, 2017 8:39 pm

Re: pulseaudio-dlna to chromecast initialize time

Post by MrEen » Sat Aug 04, 2018 12:41 pm

Here are some observations that may help:

You said:
Without success I have been trying to recall what I may have tampered with to upset the routine.
Used a different computer
To me, this would imply the Chromecast itself or whatever it's plugged in to might be the cause.

Another possibility, have you recently added something new to the network or to your computer?

Have you rebooted at all since this started?

If you're using the Chrome browser, did it update recently (or ever?)

Hopefully, one of these will lead you to the path that will resolve this issue.

Good luck.
phd21 wrote: I'm cheating here to get phd21 to look at this thread. phd21 has much more experience with dlna/streaming than I do.

BlackJackMarcus
Level 1
Level 1
Posts: 11
Joined: Tue Feb 07, 2017 2:00 am

Re: pulseaudio-dlna to chromecast initialize time

Post by BlackJackMarcus » Sat Aug 04, 2018 3:36 pm

Thanks for ideas.
I've rebooted more times than I can count.
Videostream Chrome extension for video files works perfectly, unfortunately it doesn't do audio only.
What's changed to induce the delay, well I've racked my brains over that one, nothing fell out tho ;-)
Like you suggest I'm beginning to believe I need to swap out the TV the chromecast is connected to, I'll try that.
Thanks for input.

BlackJackMarcus
Level 1
Level 1
Posts: 11
Joined: Tue Feb 07, 2017 2:00 am

Re: pulseaudio-dlna to chromecast initialize time

Post by BlackJackMarcus » Mon Aug 13, 2018 6:27 pm

An update, I've come across the pulseaudio-dlna delay issue in another forum, there was no solution there either.. Since then I installed VLC V3 via the Software Manager (Flatpak), audio casting to Chromecast works with no delay :D . Again VLC demonstrates how capable it is. Happiness is ......

User avatar
Joe2Shoe
Level 4
Level 4
Posts: 351
Joined: Wed Oct 18, 2017 8:12 pm
Location: Ozone

Re: pulseaudio-dlna to chromecast initialize time

Post by Joe2Shoe » Mon Aug 13, 2018 6:42 pm

VLC rules. Been using it for 10+ years. I was going to suggest that, and am glad it's working now.
I was going to suggest also to turn wifi power management off.
"Tolerance is the refuge of men without conviction."
"Common sense is not so common" - Voltaire

Post Reply

Return to “Sound, Multimedia, & Codecs”