Hi,
Thanks for posting this. I looked at the relnotes for 0.19.15 earlier today but did not connect the dots to HLS. Just to confirm we have the same understanding, HLS support should be enabled as a result of the following from the relnotes:
- ffmpeg: use as fallback instead of "mad" if no plugin matches
If this is the case then yes I'll definitely bump to 0.19.15 for TR3
Regards,
Tim
Btw: try TR2 and see of the issue you described is still present.
Hi,
Examine /var/log/mpd/mpd.log and look for indications as to why nothing past 'N'. Most common cause is insufficient permissions on folders/files.
-Tim
Hi Phil,
I'm not able to repro this on Pi-1/2/3. My resolve.conf's all look like below after autoconfig. The values for domain and nameserver come from my Router DHCP service.
# Generated by resolvconf
domain home.local
nameserver 192.168.1.1
Are u 100% sure your Router DHCP is configured to supply the name server addr?
For the failure condition "resolve.conf empty", I would check dmesg and /var/log/syslog on the Pi and also the DHCP log on Router.
Regards,
-Tim
Absolutely certain that DHCP is being dished out correctly. The device picks up the right IP address and is registered in the connections list on the router.
It also works for all other devices in the house.
Pi 1, 2, and 3 all have ethernet adapters on board. The Pi Zero doesn't.
I wonder if that's what is upsetting it?
I'll try to do some more digging as you've suggested.
Phil
Code:
pi@moode:~ $ cat /etc/resolv.conf
# Generated by resolvconfSame SD card works fine on my Pi 3, so it is to do with the USB Wifi dongle being initialised late in the boot sequence, I suspect.
Phil
Last edited:
Yes, that sounds like what I have been experiencing. Lots of hangs and pauses. When I get the time, I am going to try a ethernet connection and will also upgrade the borderline power supply I am using.
Andy
After a reboot of the Pi Zero:
Code:
pi@moode:~ $ ping [url=http://www.bbc.co.uk]BBC - Home[/url]
ping: unknown host [url=http://www.bbc.co.uk]BBC - Home[/url]
pi@moode:~ $ sudo ifdown wlan0 && sudo ifup wlan0
Killed old client process
Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit [url]https://www.isc.org/software/dhcp/[/url]
Listening on LPF/wlan0/00:13:ef:06:0b:0d
Sending on LPF/wlan0/00:13:ef:06:0b:0d
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67
Error for wireless request "Set Power Management" (8B2C) :
SET failed on device wlan0 ; Operation not permitted.
ioctl[SIOCSIWAP]: Operation not permitted
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit [url]https://www.isc.org/software/dhcp/[/url]
Listening on LPF/wlan0/00:13:ef:06:0b:0d
Sending on LPF/wlan0/00:13:ef:06:0b:0d
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPOFFER from 192.168.1.1
DHCPACK from 192.168.1.1
bound to 192.168.1.99 -- renewal in 685352531 seconds.
pi@moode:~ $ ping [url=http://www.bbc.co.uk]BBC - Home[/url]
PING [url=http://www.bbc.net.uk]BBC - Home[/url] (212.58.244.69) 56(84) bytes of data.
64 bytes from bbc-vip114.telhc.bbc.co.uk (212.58.244.69): icmp_seq=1 ttl=53 time =16.8 msHi, Tim,
Thank you so much for your wonderful work!
I have a feature request.
When resampling is turned on, DSD on DoP format will be changed.
About sound quality, original DSD is better than those resampled.
Could you make so that resampling and DoP function will operate independently?
Or, I’m happy if output of BCK would be 64fs all of the time, when source of 44.1kHz/16bit were played.
(My P2D device needs 64fs BCK)
//Rpi3(Moode2.6(TR2)/ RPi-DAC I2S driver) → P2D v2(Electart) → ES9018
Thank you so much for your wonderful work!
I have a feature request.
When resampling is turned on, DSD on DoP format will be changed.
About sound quality, original DSD is better than those resampled.
Could you make so that resampling and DoP function will operate independently?
Or, I’m happy if output of BCK would be 64fs all of the time, when source of 44.1kHz/16bit were played.
(My P2D device needs 64fs BCK)
//Rpi3(Moode2.6(TR2)/ RPi-DAC I2S driver) → P2D v2(Electart) → ES9018
I start from new Image 2.6 TR2.
First, my router set the Moode-Raspberry IP to 192.168.0.32
After config to static IP (192.168.0.15) and reboot, my router shows even 192.168.0.32 in DHCP List, but it is possible to get the moode player over both IP's (.32 and .15).
I am confused !?!?!?
With moode 2.4 I didn't have this effect.
My router config show dhcp address range from 182.168.0.20 to .100
Daniel
First, my router set the Moode-Raspberry IP to 192.168.0.32
After config to static IP (192.168.0.15) and reboot, my router shows even 192.168.0.32 in DHCP List, but it is possible to get the moode player over both IP's (.32 and .15).
I am confused !?!?!?
With moode 2.4 I didn't have this effect.
My router config show dhcp address range from 182.168.0.20 to .100
Daniel
Hi,
Thanks for posting this. I looked at the relnotes for 0.19.15 earlier today but did not connect the dots to HLS. Just to confirm we have the same understanding, HLS support should be enabled as a result of the following from the relnotes:
- ffmpeg: use as fallback instead of "mad" if no plugin matches
If this is the case then yes I'll definitely bump to 0.19.15 for TR3
Regards,
Tim
Btw: try TR2 and see of the issue you described is still present.
Yes i am not able to test but everything seems to indicate that this will enabled hls when reading the forum post. it might also allow me to listen to .ts radio
Hi Tim,
Thanks to a serendipitous email from another forum reader I've found the root cause of this and the fix.
In your auto-generated /etc/network/interfaces file you have the line
Code:
auto wlan0
Code:
allow-hotplug wlan0Thanks Nigel for the clue.
Tested on my Pi Zero with USB wifi dongle and on my Pi 3 with onboard wifi.
Looking forward to seeing the fix in TR3.
Cheers,
Phil
Congrats, Phil!
Sounds like a good catch. Knowing roughly what "allow-hotplug" signifies, this seems reasonable. I'm too lazy though to modify the iso to test this change in a virgin install (the line to fix is buried in a string in a .php file which generates the entries in /etc/network/interfaces). Gotta go do some volunteer work at Project Reboot to refurbish computers for others instead.
I'll wait for Tim to do the heavy lifting to make sure the change doesn't break something else, like the new AP code
Regards,
Kent
UAC2 test on Pi-B
Hi,
Tested TR2 on Pi (old one, not Pi2), out of the box:
a) CM-6631A, 24 bits still gives very loud digital noise without the USB fix line. Adding the USB fox to the config fixes this.
b) XMOS USB forces 32 bit format, even if the source is 24 bits. This works fine without the USB fix. Older versions of MoOde (like 2.4) occasionally give some clicks with XMOS, this issue seems gone in 2.6 TR2
Later will test Pi2
Rob
Hi,
Tested TR2 on Pi (old one, not Pi2), out of the box:
a) CM-6631A, 24 bits still gives very loud digital noise without the USB fix line. Adding the USB fox to the config fixes this.
b) XMOS USB forces 32 bit format, even if the source is 24 bits. This works fine without the USB fix. Older versions of MoOde (like 2.4) occasionally give some clicks with XMOS, this issue seems gone in 2.6 TR2
Later will test Pi2
Rob
Hi,
I have a TODO item titled "selective resampling". The idea is to provide some user settings for example "only resample 16/44.1, leave other sample rates unchanged", then the code would check the sample rate or format of the file before starting playback, then determine whether to turn on resampling based on user settings.
Would something like this fit your usage scenario?
-Tim
Yes i am not able to test but everything seems to indicate that this will enabled hls when reading the forum post. it might also allow me to listen to .ts radio
Hi,
Definately worth a try. I'll go with 0.19.15 for TR3.
-Tim