RuneAudio 0.3-alpha for Raspberry Pi

Chanh

Hi Guys,

Any chance of knowing if 0.3-beta is coming out soon?

Any aupdate is kindly appreciated!

Cheers,
Chanh

Woodhouse

Haha.. You just asked that one big question that nobody dares to ask.....

The topic was effectively silenced.... let's take that as an indicator of the silence before the storm...

But in all seriousness, I am really looking forward to .3 beta...Somewhere in this forum I read that we can expect it in the beginning of October. This software is just great! It has revived my enthusiasm for audio and technology in general. I have at least one fellow raspberry audio enthusiast living nearby and another analog audio enthusiast that I hope to convince with a fine runeaudio 0.3 setup on hifi-berry dac platform.

Right now running 0.3 a and coping with the shortcomings.....

A big heads up to the devs, doing this all in their spare time and giving us a great platform.

J@r0d

Hi

I have problem with my ralink usb RT5370 with use hostapd

No problem for launch in 0.2Beta, the hotspot is up, but in 0.3alpha i have error when lauch hostapd

/hostapd-test.conf

#change wlan0 to your wireless device
interface=wlan0
driver=nl80211
ssid=test
channel=1

[root@runeaudio ~]# nano ~/hostapd-test.conf
[root@runeaudio ~]# hostapd ~/hostapd-test.conf
Configuration file: /root/hostapd-test.conf
nl80211: Could not configure driver mode
nl80211 driver initialization failed.
hostapd_free_hapd_data: Interface wlan0 wasn't started
[root@runeaudio ~]#

If disable wpa-supplicant and ntcl in systemctl i have other error:

[root@runeaudio ~]# hostapd ~/hostapd-test.conf
Configuration file: /root/hostapd-test.conf
Using interface wlan0 with hwaddr 7c:dd:90:5f:cxx:xx and ssid "test"
wlan0: interface state UNINITIALIZED->ENABLED
wlan0: AP-ENABLED
handle_probe_req: send failed

J@r0d

I progress

I resintall img alpha3

PluG RT5370

launch wifi-menu>>>>ok dongle view other AP

launchd hostapd

[root@runeaudio ~]# hostapd ~/hostapd-test.conf
Configuration file: /root/hostapd-test.conf
nl80211: Could not configure driver mode
nl80211 driver initialization failed.
hostapd_free_hapd_data: Interface wlan0 wasn't started

netctl list:
Wlan0
*Eth0

● netctl@wlan0.service - wlan0 connection
   Loaded: loaded (/etc/systemd/system/netctl@wlan0.service; enabled)
   Active: failed (Result: exit-code) since Thu 1970-01-01 00:03:38 UTC; 8min ago
     Docs: man:netctl.profile(5)
  Process: 1345 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 1345 (code=exited, status=1/FAILURE)
[root@runeaudio system]#

After netctl start wlan0:

[root@runeaudio system]# netctl status wlan0
● netctl@wlan0.service - wlan0 connection
   Loaded: loaded (/etc/systemd/system/netctl@wlan0.service; enabled)
   Active: activating (start) since Thu 1970-01-01 00:12:59 UTC; 19s ago
     Docs: man:netctl.profile(5)
 Main PID: 1930 (network)
   CGroup: /system.slice/system-netctl.slice/netctl@wlan0.service
           ├─1930 /bin/bash /usr/lib/network/network start wlan0
           ├─1936 wpa_supplicant -B -P /run/wpa_supplicant_wlan0.pid -i wlan0 -D nl80211,wext -c/etc/wpa_supplicant/wpa_supplicant.conf
           └─2286 sleep 0.2
[root@runeaudio system]#

Launch Hostapd:

[root@runeaudio system]# hostapd ~/hostapd-test.conf
Configuration file: /root/hostapd-test.conf
Using interface wlan0 with hwaddr 7c:dd:90:5f:xx:xx and ssid "test"
wlan0: interface state UNINITIALIZED->ENABLED
wlan0: AP-ENABLED

My android phone view AP

What solution for resolve my problem ?

For my caraudio application i want use only AP mod

challenge

Please if it's not ready/good enough for beta stage, release it and call it alpha1, at least we can test and report bugs

There are so many new functions on git after 0.3alpha we could try!
Are you planning to automate builds in future to let users build development snapshots from git?

Thx for the great job.

Peter

franz159 wrote:Is there any ETA for the 0.3 beta and 0.4 releases?

Respectively at begin and end of october, hopefully

???

Aquarius

Dear all,

I made my first serious high volume listening tests with 0.3 alpha yesterday and I have a problem.

On each and action on the playback change song/skip/start/stop, I have a very anoying high pitched pop (the kind of thing I don't want in the long run to not destroy my tweeters).

I tried every kernel profile, to check if one of them would make this pop disapear, to no avail.

I'm pretty sure it's a problem of buffer or a driver issue. The idea being that, basically, the first bits (after "play") or last bits (after "stop") sent on my Hifiberry Digi Coax output result in this pop.

- The issue also comes when using my Grado headphones.
- The issue is **not** present when using my streamer to feed the DAC directly. (the streamer feeds I²S directly to the DAC).

Cheers!

Peter

franz159 wrote:Is there any ETA for the 0.3 beta and 0.4 releases?

Respectively at begin and end of october, hopefully

??????????????

Peter

So Long, and Thanks for All the Fish

Devox

As I understood it, there are three guys who are spending their free time, beside their daily jobs, working on this rather complex Project.
I guess delays of the schedule they planned are totally normal under that circumstances, and you just can't hold them accountable for something they do for fun. Not even for talking much about those delays, because that would all end in senseless discussions with some users, keeping the Rune-creators even more away from accomplishing their tasks.

For my part, I'm just happy if 0.3beta gets released this Year. That's a rather healthy way of looking at the situation, i guess. Protects you from getting to anxious.

ACX

Hi everyone,
I can assure you we are doing our best to publish the new 0.3-beta as soon as possible, and that it will be worth the wait. We never set official release dates anyway, so please relax and wait for it

The release will simply see daylight when ready - and it will be soon.

For the record, both Orion and I have few free time, and we already spend it almost entirely into this project. I understand that someone could be impatient, so if you want to speed up the development there are many ways to help us, everyone can contribute in his own way.

johnbanks

@[deleted]

Yes we must be patient and we greatly appreciate what you guys have achieved so far and the effort you put in.

Gordon at IQaudio has suggested that to get DAC's for RPi B plus working, all that is necessary is to update the RPi firmware (rpi-update).

A general update (pacman -Syu) seems to be the preferred method but it crashes 0.3 alpha - so is there a way just to do rpi-update?

Thx

ACX

johnbanks wroteA general update (pacman -Syu) seems to be the preferred method but it crashes 0.3 alpha - so is there a way just to do rpi-update?

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.

cmh714

look at my pacman posts......I have been updating every few days, mostly with pacman -Syu but occassionally I test with rpi-update as that kernel is 1/3 the size of the normal kernel.

Again, in my experience its the ffmpeg package that is breaking the UI.......

After updating the kernel via either method, you will need to go to /boot and change the kernel name from kernel.img to the name rune is expecting....I am out of town so dont have access to Rune atm.

GL

itsikhefez

I'm trying to get the HifiBerry Digi+ to work.

I've updated my kernel to 3.12.29-1 and have done a pacman -Syu --ignore ffmpeg regardless.
I've renamed /boot/kernel.img to /boot/linux-rune-3.12.19-2-ARCH.img with the intention that rune loads that as the kernel.

I've selected I2S module HifiBerry Digi,
but in MPD I still only have RPI analog and HDMI outputs.

Any ideas?

cmh714

Sounds like youve updated properly. I dont know, nor have the DAC you do.....you can try some of the other "fixes", like trying to change the config being used. I know that was needed for my Dragonfly and my Rotel DAC's.

I am forgetting the various commands off the top to help you, maybe dmesg, or lsusb....

I cant help much better since I am on the road and not in front of my Pi.

Aquarius

Aquarius wroteDear all,

I made my first serious high volume listening tests with 0.3 alpha yesterday and I have a problem.

On each and action on the playback change song/skip/start/stop, I have a very anoying high pitched pop (the kind of thing I don't want in the long run to not destroy my tweeters).

I tried every kernel profile, to check if one of them would make this pop disapear, to no avail.

I'm pretty sure it's a problem of buffer or a driver issue. The idea being that, basically, the first bits (after "play") or last bits (after "stop") sent on my Hifiberry Digi Coax output result in this pop.

- The issue also comes when using my Grado headphones.
- The issue is **not** present when using my streamer to feed the DAC directly. (the streamer feeds I²S directly to the DAC).

Cheers!

It seems my issue was lost on the ETA discussion...

andy.room

ACX wroteTHE "GHOST MOUNTS" BUG
About the "ghost mounts" bug that is affecting many of you: it seems that's a visualization problem related to the UI, as the resources are correctly mounted (and browsable by the system and other clients) but not displayed in the Library home. The problem is that we are not able to reproduce the issue on our setups, that's because we never detected it before. So we need some hints from you to detect the cause.

To everyone having this issue
Please follow this steps to help us figure it out:
1) click on the Library tab in the UI to visualize the Library home screen
2) open the JavaScript console of your browser (usually pressing the F12 key and selecting the "Console" tab) and input this command:
getDB({path: 'NAS'});
Does it display your network mounts or not?

I experience the Ghost Bug only when I mount a shared folder of my PC running Windows XP.....Tried to use the above command in the Java console and what I get is the main folder of my network share....but EMPTY. If I force the folder update, it spin for a few minutes and finally I always get an empty folder. Tried to view the folder from the terminal window and /mnt/MPD/NAS/My_HD is also empty. Any idea? Thanks.

kodreaming

getDB({path: 'NAS'});
It returns
undefined

kodreaming

Anyone having issue with popping sound ? I want to switch to NFS to see if that would help, but when I use NFS, it doesn't show any error, but the updating won't get triggered. My NAS is Synology DS214.

Overall, the wifi just feel pretty slow with Edimax dongle.

« Previous Page Next Page »