pi-fi
Hi Frank,
I've just installed the latest version for a test and I've noticed a couple of issues. I also have a question.
Once my library fully updated, I checked it. I've got alphabetically listed albums (sub folders) in 7 main folders.
As stored though, in each of the 7 folders, THE TOP ENTRY IN THE LIST HAD BEEN STORED INCORRECTLY (the top entry in each list had been transposed with a random title from partway down each list).
I rebuilt the library and double-checked my listings on a PC to ensure the problem was consistent and real.
Also, INCORRECT ALBUM ART WAS DISPLAYED on one album. Again, I double checked the jpeg image in the folder on a PC. The correct one was in the folder. Back on the Pi, the incorrect art was being displayed.
Now the question: You say that alsamixer can now be accessed from the UI Frank. Can you please advise where this can be found in the UI?
Thanks for your help and for the work of all the RuneAudio team.
hondagx35
Hi pi-fi,
As stored though, in each of the 7 folders, THE TOP ENTRY IN THE LIST HAD BEEN STORED INCORRECTLY (the top entry in each list had been transposed with a random title from partway down each list).
This only happens to me with Chrome, Firefox works as expected.
I have no idea what causes this behavior.
Now the question: You say that alsamixer can now be accessed from the UI Frank. Can you please advise where this can be found in the UI?
There is no menue entry or a button to access alsamixer.
- alsamixer now can be accessed via UI
Does not look good but sometimes very handy
http://yourIP:8080
This means there is a UI for alsamixer and is accessible that URL.
Frank
pastic
Hi Frank,
1) Is there any way to check if MPD is currently indexing/updating or if it is idling? (So as to know if it is 'safe' to reboot.)
2) Why does the RuneUI (menu navigation, start/stop playing) of 04beta version 20170229 freeze for long periods (>2min) when the RPi is blocked from accessing the internet (by a router block rule). Even before making any changes or adding music to a freshly flashed card, there are huge delays if the router block is active, but not if it is disabled. The older official release does not exhibit that behaviour.
hondagx35
Hi pastic,
1) Is there any way to check if MPD is currently indexing/updating or if it is idling?
There is an indicator on the library button (bottom left).
Why does the RuneUI (menu navigation, start/stop playing) of 04beta version 20170229 freeze for long periods (>2min) when the RPi is blocked from accessing the internet
Rune tries to get lyric and artist info from the internet.
Frank
pastic
hondagx35 wrote
Rune tries to get lyric and artist info from the internet.
Frank
HI, thanks for the quick response.
But why would it try doing so when I switch from menu option MPD to menu option network, and between other menu options, even before I have added any music to a freshly flashed SD card?
Ripa
Hi,
is it possible to have only this layout i love this ..
- Attachments
- new_knob-800px.jpg (24.34 KiB) Viewed 4931 times
parthabhatta
I love to use Runeaudio 0.4 beta version dated Feb, 2017, specially its sound signature - which is enjoyed more by me than the other similar OS. Runeaudio has a couple of unique features which are not available in the others namely volumio & moode, namely
1. Lyric feature
2.Change the sound hardware on the fly (between HDMI, PI, External DAC & USB DAC)
But there are quite a few bugs in RuneAudio which makes it difficult to use and has forced me to shift to other OS despite my unwillingness. More so, because there is no updates since long and moreover no news regarding what developments are going on and what will be available to us in future. A few months back in some thread it was said that RuneAudio 2 is in pipeline but no ETA was given. So in this darkness I was forced to use other OS. Some of the bugs which I detected.
1. WiFi - The connection with built in Wifi of RPi 3 Model B is very unstable and most of the time it stays unconnected. The Static mode is unusable as the settings doesn't stay in place. I bought a separate WiFi dongle to use RuneAudio and make manual edit of a file to disable the built in wifi whereas in other OS external Wifi dongle is much easier to use. The external wifi dongle is much stabler with runeaudio in DHCP mode.
2. The OS sometimes does not boot and gets stuck. After a couple of such instances which forces to shutdown the Pi forcibly resulting in corrupted OS. Reinstalling everything from start is a pain.
3. The USB HDD mounted by me is scanned on every restart which takes long with my 25000+ song database and one has to wait for it to finish before listening to a song. Disabling this feature needs manual intervention which again is difficult for many.
4. Expanding the SD card partition also appears buggy to me. Till the time I use Runeaudio without expanding, it works ok. Once the partition is expanded through ADDONS menu, the problem aggravates. OS halts on boot forcing to use forced restarts and after a couple of such restarts, the OS gets corrupted.
5. The Addon Kodi is not updated for this version of beta and is unusable.
I understand that its a free OS and so nothing is guaranteed and there is no ETA, but then I love its sound, so .....
I use a RPi 3 Model B with RPi official PS and a ALLO BOSS v1.2 DAC, which is separately powered. Two USB HDDs (1Tb & 2Tb) are connected with a powered USB hub.
Regards,
Partha
KENMAC
Hi cannot get this to work with my Raspberry Pi IQAUDIO DIGIAMP+. All seems ok, but I cannot unmute.
Vhond
parthabhatta wroteI love to use Runeaudio 0.4 beta version dated Feb, 2017, specially its sound signature - which is enjoyed more by me than the other similar OS. Runeaudio has a couple of unique features which are not available in the others namely volumio & moode, namely
1. Lyric feature
2.Change the sound hardware on the fly (between HDMI, PI, External DAC & USB DAC)
But there are quite a few bugs in RuneAudio which makes it difficult to use and has forced me to shift to other OS despite my unwillingness. More so, because there is no updates since long and moreover no news regarding what developments are going on and what will be available to us in future. A few months back in some thread it was said that RuneAudio 2 is in pipeline but no ETA was given. So in this darkness I was forced to use other OS. Some of the bugs which I detected.
Partha
I completely agree with Partha, I also wanted to stay using Rune as my first choice but 2 things keep me away:
1) better handling of Airplay: Shairport Sync instead of Shairport
2) not knowing when updates will be available for bugfixes
I understand that its a free OS and so nothing is guaranteed and there is no ETA, but I hope we will hear from you soon. Thanks for the good work.
dror
Vhond wrote
I completely agree with Partha, I also wanted to stay using Rune as my first choice but 2 things keep me away:
1) better handling of Airplay: Shairport Sync instead of Shairport
2) not knowing when updates will be available for bugfixes
I understand that its a free OS and so nothing is guaranteed and there is no ETA, but I hope we will hear from you soon. Thanks for the good work.
for #1 do this:
#611415
Dror
Vhond
dror wroteVhond wrote
1) better handling of Airplay: Shairport Sync instead of Shairport
for #1 do this:
#611415
Dror
Thx for this one, hope this will be already added in the final 0.4 release
salzi
I cannot get airplay working. Playing from NAS and radio works but somehow airplay doesn't give signal. I've tried to change mpd settings by ssh and googled a lot and tried different rune versions but nothing helps. I noticed is that rune says I've rpi 2, but I've rpi 3 b V1.2. May that be a problem?
gearhead
The Pi3 will boot with a Pi2 image. That is not the problem, If your pi boots. I was never successful in getting shairport to work reliably. What I did was uninstall shairport and install shairport-sync. This step means that the UI will not control shairport-sync and you will need to configure it from the command line. The configuration file is in /etc/shairport-sync.conf and the way to start it is by using systemd service files: i.e. 'systemctl start shairport-sync'. There is a link above where Frank outlines how to install shairport-sync.
ARFrater
HI any thoughts on the new RASPBERRY PI 3 MODEL B+
https://www.raspberrypi.org/products/raspberry-pi-3-model-b-plus/ is is a worth while upgrade and will the RuneAudio 0.4-beta OS/Image run with the new Pi.
Thanks
janui
Hi ARFrater,
No, it won’t work.
See here:
#62751
and here:
#62875
There is a version on the way which works.
Is it worth the upgrade? Probably not if you already have a Pi B2 or B3. However, it is more powerful and the same price as the older models, so no reason not to use it when a RuneAudio version is released which supports it.
janui
ARFrater
janui wroteHi ARFrater,
No, it won’t work.
See here:
#62751
and here:
#62875
There is a version on the way which works.
Is it worth the upgrade? Probably not if you already have a Pi B2 or B3. However, it is more powerful and the same price as the older models, so no reason not to use it when a RuneAudio version is released which supports it.
janui
Hi Janui
Thanks for the info looking forward to the new image and then will upgrade (already have a use in mind for my 3B once 3B+ is fully working).
Andrew
arnaldo
hi guys, i have a problem.
i have 04-beta with the last kernel (4.14.39), raspberri pi2(08).
in usb is ok, i would try to connect my dac via spdif.
I have a Allo Kali reclocker and a Digitale Interface I2S vers SPDIF BNC WM8804
which driver i have to use?
thanks,
Arnaldo.
Dave Platt
Hi, arnaldo! I don't know for certain, but after looking at the documentation for the WM8804 and the Kali, it looks to me as if using the HiFiBerry DAC driver would be a good place to start. This driver seems to work with a lot of DACs, as it appears to use the I2S interface in a fairly "vanilla" fashion - the Pi is the I2S clock master, and a 24-bit/sample frame format is used.
I have to question, though, whether the approach you're choosing is an ideal one. The Kali is going to be re-clocking the signal as it comes out of the Pi, and before it goes into an I2S-to-SPDIF converter. Converting the signal to SPDIF is necessarily going to merge the separate clock-and-data signals of I2S, into the single composite signal carried by SPDIF. When the SPDIF signal reaches whatever device you're sending it to (presumably a DAC or A/V receiver that contains one) this device is going to have to separate out the clock and data again using an SPDIF receiver with its own PLL... and this process can (and I fear it will) reintroduce the same sort of clock jitter that the Kali is intended to get rid of.
Any sort of re-clocking of a digital audio signal is probably best done as close to the final digital-to-analog conversion as possible - which in this case would mean after the SPDIF step.
The Kali seems to be made to be used immediately before a (slave-mode) DAC, so that the DAC can take full advantage of the stability of the re-clocked signal.
Dave Platt
Just wanted to report a newbie success with RuneAudio here.
I played around with Rune a bit on an old Beaglebone Black I had sitting around, liked it, and decided to build a more modern configuration that could take advantage of the improvements in 0.4 beta. I picked up a Pi2B on eBay and loaded it up - it worked very nicely with an old Creative Extigy USB audio box. I decided I wanted to build something more self-contained, so I bought an inexpensive I2S DAC module (based on the TI PCM5102A chip) and an AdaFruit HAT prototype board. I also dug out a nice metal case for it (an old Black Box GPIB-to-serial converter that I could junk).
Everything soldered together quite nicely. I put the DAC module in the center of the HAT board. For power, I decided to use a multiply-regulated approach for stability and low noise. The box takes in a 12-volt-DC supply from a fairly hefty switching power supply brick that goes through a 1-amp polyfuse and switch. This is then brought to a pair of separate 5-volt linear regulators - a 78L05 on the HAT which powers the DAC module, and a 7805-equivalent on a heatsink on the floor of the case which powers the Pi itself. Both regulators have 22 uF 'lytic caps wired across their inputs, for stability. The DAC module works fine with the HiFiBerry DAC driver, and ALSA reports it's being fed a 24-bit signal (which should mean that any quantization noise from the use of the ALSA softvol control is down well below audibility).
The resulting box looks good enough to pass muster, and it sounds fine (I'm using it with a small in-the-bedroom system, which is quality-limited by the speakers). The system has a dead-quiet background - there's no trace of digital switching noise, buzz, or hum that I can hear. Although the linear-regulation approach is somewhat energy-inefficient (the 7805 is dropping about 7 volts, at whatever current the Pi is drawing) the energy waste is negligible - the box isn't more than faintly warm to the touch even after playing Ogg Vorbis recordings for an hour.
I'm just hoping I don't get bitten (or bitten too frequently) by the notorious "Pi corrupts the SD card" problems. Gotta back up early and often.
My thanks to all who have worked on RuneAudio - it's a nice distribution and an excellent tool.
Kilgore
Any photos Dave? Share the love!
