Inviato dal mio SM-N9005 utilizzando Tapatalk
Yes,
I second this, waiting for an update for UDOO quad.
Many thanks in advance…
Michelangelo how many time for udoo 1.3 ?
+1
Also waiting for newer version…
Fresh and new…
Let me know what do you guys think… If this is good I’ll publish…
2 news on that… Now it can read UPNP shares (just update the DB and your UPNP shared music will magically appear…) and you can control with upnp\dlna… Suggest to use bubbleupnp, its just amazing
Let me know !
MI
Ok mike, a link pleeeease!!! The main site link only the older version.
Another question bubbleupnp can stream flac?
Yep, sorry…
https://sourceforge.net/projects/volumio/files/Udoo/Beta1.3/VolumioBeta1.3UDOOQuad.zip/download
Flac should be supported, but this depends on your Server Settings
Hi Mike,
thank you for the update, BubbleUPNP with Volumio works fine.
Is SPDIF implemented yet?
Mmhhh the xmos problems is not resolved.
It work only with the workaround I am not able to reboot or power off with software because in this case I have to reformat and reinstall Volumio in the microsd.
Usb hardisk - Now I have in loop the database and only see a little part of my music files.
Bubble upnp don’t show volumio.
Now no nas access.
Positive:
The sound quality seems to my ears more enjoable than the earlier versions.
But in few words… a lot of problem.
I return to 1.0
Dr165 are you able to use bubbleupnp and listening music in udoo?
I was able to render the music only in my phone and not in udoo.
I have only the volumio library not option to render in udoo.
Yes, in BubbleUPNP on my Nexus 7 Volumio is shown as one of 3 renderer:
Local, Volumio and WDTV.
Another friend has the same problem with usb disk database loop and the upnpdlna goes and returns almost casually.
Hej!
I have tried 1.3 version…but still problems to get sound from my USB Audiolab MDAC (like with Volumio 1.0)
Still I get MPD error below (with log_level = Verbose)
Apr 27 18:53 : alsa_output: opened hw:2,0 type=HW
Apr 27 18:53 : alsa_output: format=S24_3LE (Signed 24 bit Little Endian in 3bytes)
Apr 27 18:53 : alsa_output: buffer: size=90..174762 time=2040..3962858
Apr 27 18:53 : alsa_output: period: size=45..87381 time=1020..1981429
Apr 27 18:53 : alsa_output: default period_time = buffer_time/4 = 500000/4 = 125000
Apr 27 18:53 : client: [10] process command "status"
Apr 27 18:53 : alsa_output: format=S24_3LE (Signed 24 bit Little Endian in 3bytes)
Apr 27 18:53 : alsa_output: buffer: size=90..174762 time=2040..3962858
Apr 27 18:53 : alsa_output: period: size=45..87381 time=1020..1981429
Apr 27 18:53 : alsa_output: format=S24_3LE (Signed 24 bit Little Endian in 3bytes)
Apr 27 18:53 : alsa_output: buffer: size=90..174762 time=2040..3962858
Apr 27 18:53 : alsa_output: period: size=45..87381 time=1020..1981429
Apr 27 18:53 : alsa_output: format=S24_3LE (Signed 24 bit Little Endian in 3bytes)
Apr 27 18:53 : alsa_output: buffer: size=90..174762 time=2040..3962858
Apr 27 18:53 : alsa_output: period: size=45..87381 time=1020..1981429
Apr 27 18:53 : alsa_output: format=S24_3LE (Signed 24 bit Little Endian in 3bytes)
Apr 27 18:53 : alsa_output: buffer: size=90..174762 time=2040..3962858
Apr 27 18:53 : alsa_output: period: size=45..87381 time=1020..1981429
Apr 27 18:53 : alsa_output: Failed to open "Output" [alsa]: Error opening ALSA device "hw:2,0" (snd_pcm_hw_params): Broken pipe
Apr 27 18:53 : output: Failed to open audio output
Apr 27 18:53 : player: problems opening audio device while playing "http://89.16.185.174:8003/stream"Additionally…dmesg shows the following:
205.450658] 4:2:1: cannot get freq at ep 0x1
[ 205.455323] cannot submit datapipe for urb 0, error -28: not enough bandwidth
[ 205.465404] 4:2:1: cannot get freq at ep 0x1
[ 205.469910] cannot submit datapipe for urb 0, error -28: not enough bandwidth
[ 205.479652] 4:2:1: cannot get freq at ep 0x1
[ 205.484132] cannot submit datapipe for urb 0, error -28: not enough bandwidth
[ 205.494030] 4:2:1: cannot get freq at ep 0x1
[ 205.498460] cannot submit datapipe for urb 0, error -28: not enough bandwidth
[ 205.508276] 4:2:1: cannot get freq at ep 0x1
[ 205.512681] cannot submit datapipe for urb 0, error -28: not enough bandwidth
[ 241.239671] 4:2:1: cannot get freq at ep 0x1
[ 241.244195] cannot submit datapipe for urb 0, error -28: not enough bandwidth
[ 241.254178] 4:2:1: cannot get freq at ep 0x1Any idea?
thanks
Stefano
Stefano, try to attach the USB DAC to the auxiliary USB port. You need an adapter to do that, which is included in the starter kit.
Let me know
Ciao…I am already using the ancillary usb port via loose cable got with udoo starter kit…but same issue like on other usbs ports.
What could be different to rpi, where my dac works greatly with volumio?
Could it be the different usb driver?
My dac is 1.1…a try could be go force usb to work at 1.1 rather than 2.0…but don’t know how to do it!
Or something to be changed in the initialization process to dac on alsa…but I don’t know where to look at…
…any other ideas?
Thanks
Stefano
Do you use lan or wifi with udoo? I have no volumio upnp render in bubbleupnp on wifi, but I have it if I use lan.
Hi Keres,
my udoo is connected via lan, the wlan of udoo is too slow for hires files.
Thanx
I have the DB update issue as well, otherwise everything is good. When scanning the files on Samba share it loops non-stop and on every reboot the DB is empty.
Origin of my update database issue:
Same music downloaded from qobuz have this format:
First album
01 01 track name
01 02 track name
01 03 track name
01 04 track name
01 05…
Second album
02 01 track name
02 02 track name
02 03 track name
02 04 …
third album
03 01 track name
03 02 track name
03 03 track name
03 04 …
All the flac files was in one folder
When I deleted or changed this format no more update database issue.