RuneAudio 0.3-alpha for Raspberry Pi

popov

Hi everybody

I'm a dunny so this i can't do any comparaison with previous versions

Wifi Configuration
Work fine with Edimax nano adapteter
Just have a problem to save configuration with IE11 and Windows 8.1
With Chromium / debian ok

Swith from HDMI, USB, Rapsberry anloog out look fine

Sound quality, difficult to compare with previous versions, but with no DAC, the quality is not suffisent to stop my old Denon ....
I will received and Iquadio. If possible i will test with other usb dac

Updating mpd database look to be fast

Regards

apocalipsis1234

Cmedia CM2606 usb card: 5.1 analog output, spdif input and output (optical). Nice sound, work out of the box, but hardware volume doesnt work (in volumio it works, but perhaps this was the reason of "pops" into traks).

Reload of library is fast... good job.

Pasting my debug information:

http://pastebin.com/8TULy3hs

ACX

apocalipsis1234 wrotePasting my debug information:

Hi apocalipsis1234,
thanks for your feedback. Please edit your post putting a Pastebin link instead the whole debug info text, like suggested in the first post of this thread (that would save a lot of space in the database at the end).

apocalipsis1234

Done... sorry

AndreR

Reporting on this thread a possible visualization bug in RuneUI on RPi B+ running on 0.3alpha, as I am currently unable to test the behavior on 0.2 beta:
Visualization of files containing a colon (:) char in any of the three ID tags (Artist, Track title, Album title) displayed in Playback window gets truncated before the colon (:) character.
E.g.:
- if the full title track ID tag is something like 'Concierto de Aranjuez: I. Allegro con spirito', Rune displays only 'Concierto de Aranjuez'
- if the full album title ID tag is 'J.S. Bach, L'œuvre d'orgue - CD 10: Deutsche Orgelmesse (II) - Chorals Schüber - Variations canoniques' Rune displays only 'J.S. Bach, L'œuvre d'orgue - CD 10'

This does not seem to be a MPD issue as I am able to see the full ID3 tags querying the MPD db on the Raspberry from a Windows machine using an MPD client such as Auremo, therefore I tend to believe that this is more an issue with the ID3 string parsing in Rune, rather than a MPD limitation.

The aforementioned truncations also appear when browsing the Library.

ACX

AndreR wroteVisualization of files containing a colon (:) char in any of the three ID tags (Artist, Track title, Album title) displayed in Playback window gets truncated before the colon (:) character.
[...]
This does not seem to be a MPD issue as I am able to see the full ID3 tags querying the MPD db on the Raspberry from a Windows machine using an MPD client such as Auremo, therefore I tend to believe that this is more an issue with the ID3 string parsing in Rune, rather than a MPD limitation.

Thank you for the detailed bug report, I'm going to check this and see where the truncation happens (server side in PHP or client side in JS).

EDIT: I just checked and the problem is on server side parsing (PHP), the JSON response comes already truncated to the JS frontend parsing, so now we are going to fix it.

AndreR

ACX wroteI just checked and the problem is on server side parsing (PHP), the JSON response comes already truncated to the JS frontend parsing, so now we are going to fix it.

Excellent! Thanks a lot!

johnbanks

@[deleted]

In yr 9 Oct post you wrote ...

"Try to update the kernel alone, that's what you need to make I2S work on Rpi B+. I suggest you to use linux-arch-3.12.26-2-ARCH version, as 3.12.28 has problems with 24bit files on I2S."

I have tried for more than a day to do this - without success - but have learned a bit more about ArchLinux

I found a ref to linux-arch-3.12.26-1-ARCH on the Rune git site (not the -2 version)
Downloaded this .bz2 file with wget and then tried to install it with pacman -U

No success ... Unrecognised archive format

I'm a neophyte ... can you please give a bit more advice.

I know from the forum that there are several frustrated guys out there with RPi B PLUSses and xxxxx DAC plusses (iqAudio in my case)

If I eventually succeed then I'll take time to post my solution on this forum

Thx

ACX

@[deleted] and everyone is trying to manually update the system:

I'm sorry but at this time I can't test the procedure and see why that's not working, because we are totally focused the 0.3-beta release. Moreover, we made the last-minute decision to include a big surprise in the next version, and we are working even harder to deliver it in time.
So my advice is: please wait a bit more for the release of the 0.3-beta, and avoid messing the system with manual updates.
In the future we will structure everything better to allow system upgrades and UI upgrades via git in an easier and safer way.

johnbanks

@[deleted]

Thank you for your quick reply.

You are creating a great product - victims of your own success?

I have already sent a donation and encourage any guys reading this to do the same

sykodad

johnbanks wrote@[deleted]

In yr 9 Oct post you wrote ...

"Try to update the kernel alone, that's what you need to make I2S work on Rpi B+. I suggest you to use linux-arch-3.12.26-2-ARCH version, as 3.12.28 has problems with 24bit files on I2S."

I have tried for more than a day to do this - without success - but have learned a bit more about ArchLinux

I found a ref to linux-arch-3.12.26-1-ARCH on the Rune git site (not the -2 version)
Downloaded this .bz2 file with wget and then tried to install it with pacman -U

No success ... Unrecognised archive format

This procedure works on my system (not tested with 24bit files):

1. pacman -Sy
2. pacman -S linux-raspberrypi
3. renaming kernel.img in the /boot directory to replace the existing kernel
4. reboot

This installs kernel 3.12.29 (IIRC) which works for me.

Regards,

Jan

cmh714

I stay fully updated and have a pacman post that discusses this....it works fine for 24bit all the way to 192 at least for me it does

currently the main thing that breaks the UI is the update to ffmpeg so I have been ignoring that package.

matt

sykodad wrote
This procedure works on my system (not tested with 24bit files):

1. pacman -Sy
2. pacman -S linux-raspberrypi
3. renaming kernel.img in the /boot directory to replace the existing kernel
4. reboot

This installs kernel 3.12.29 (IIRC) which works for me.

Regards,

Jan

Can you outline how to rename the kernel in the boot directory, please. I presume it is renamed to 3.12.29?
Thanks

cmh714

Without looking since my Pi isnt running atm, I think you need to rename it to 3.12.19-1.ARCH.img or something like that.

sykodad

matt wrote
Can you outline how to rename the kernel in the boot directory, please. I presume it is renamed to 3.12.29?
Thanks

Hello Matt,

the name of the kernel image is linux-rune-3.12.19-2-ARCH.img (replacing the stock kernel).

Regards,

Jan

cmh714

just checked and Jan is correct.... linux-rune-3.12.19-2-ARCH.img

johnbanks

@[deleted]

Thx for your post which informed & motivated me. My RPi B+ with iqAUDIO DAC+ is now streaming wirelessly from my NAS and it sounds great.

This is what I did ....

Burned a fresh 0.3 alpha image. Plugged in a USB stick with a few test tracks. Plugged in an Edimax wireless dongle. Moved the unit to where I had an Ethernet connection. Booted and then PuTTy’d in ...

Did pacman -Sy
Did pacman –S linux-raspberrypi
Did rpi-update (thought that might be smart)

Figuring out the kernel renaming was a bit of a challenge ...

cd /boot followed by ls –l was informative. There was kernel.img with my current date/time. So how to fool 0.3 alpha into using it?
Being cautious, I did ....

mv linux-rune-3.12.19-2-ARCH.img linux-rune-3.12.19-2-ARCH.img.ORIGINAL and then ....

mv kernel.img linux-rune-3.12.19-2-ARCH.img

Rebooted and did MENU > Sources > Remount All Sources to be on the safe side. The Library quickly updated and then I played a track from the USB stick – no sound as no audio equipment was connected but the UI looked like it was playing.

Set up wireless – not always straightforward – but there other posts on this.

Powered down using RuneAudio, disconnected Ethernet and moved the unit to my ‘hifi’ location and connected up.

Powered up, waited for wireless to come up (it takes a while) and played a track but there was no sound immediately. Set the audio output interface to the iqAUDIO DAC under MENU MPD and selected it as the i2s kernel module under MENU Settings. It took a few attempts before the settings seemed to ‘stick’.

At one point doing mpc outputs showed that ALSA and the iqAUDIO DAC were both enabled.
Doing mpc enable only 2 fixed it (as the iqAUDIO DAC was output 2 in my case).

Set up my Network Mount using NFS and updated the Library.

All OK so far - then tried a 24 bit track – terrible distortion and it even sounded as if it was playing too fast.
Quite by chance I enabled Volume Normalization (under MENU MPD) and it sounded great – why this should be is beyond my level of understanding – perhaps other guys will contribute on this?

It’s taken many hours & the help of others to get to this point – so I powered down and made a backup copy of my SD card – probably the best suggestion of all.

Hope this helps

sykodad

johnbanks wrote@[deleted]

Thx for your post which informed & motivated me. My RPi B+ with iqAUDIO DAC+ is now streaming wirelessly from my NAS and it sounds great.

Hello John,

glad it worked for you.

Regards,

Jan

ACX

Here is a little surprise we prepared for you for the next 0.3-beta release:
Spotify support in RuneAudio 0.3-beta

Jorged

TP-link WN725N WiFi not working out-of-the-box with RuneAudio and when i try to install its driver, RuneAudio returns me this error message:

 [root@runeaudio ~]# pacman -Sy dkms-8188eu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 alarm is up to date
 aur is up to date
warning: dkms-8188eu-v4.1.4_6773-2 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...

Packages (1): dkms-8188eu-v4.1.4_6773-2

Total Installed Size:   8.43 MiB
Net Upgrade Size:       0.00 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring                                                             [#####################################################] 100%
(1/1) checking package integrity                                                           [#####################################################] 100%
(1/1) loading package files                                                                [#####################################################] 100%
(1/1) checking for file conflicts                                                          [#####################################################] 100%
(1/1) checking available disk space                                                        [#####################################################] 100%
8188eu, v4.1.4_6773: added

------------------------------
Deleting module version: v4.1.4_6773
completely from the DKMS tree.
------------------------------
Done.
(1/1) reinstalling dkms-8188eu                                                             [#####################################################] 100%

If your kernel is >= 3.12 and comes with
rtlwifi driver you will have to blacklist
rtlwifi for this driver to work

Creating symlink /var/lib/dkms/8188eu/v4.1.4_6773/source ->
                 /usr/src/8188eu-v4.1.4_6773

DKMS: add completed.
Error! echo
Your kernel headers for kernel 3.12.19-2-ARCH cannot be found at
/usr/lib/modules/3.12.19-2-ARCH/build or /usr/lib/modules/3.12.19-2-ARCH/source.
Error! echo
Your kernel headers for kernel 3.12.19-2-ARCH cannot be found at
/usr/lib/modules/3.12.19-2-ARCH/build or /usr/lib/modules/3.12.19-2-ARCH/source.
error: command failed to execute correctly
synchronizing filesystem...

« Previous Page Next Page »