Port Runeaudio to Odroid C1 (Arm v7)

gkkpch

Hi,

RuneAudio has been running stably for days now without any problems whatsoever (using the XMOS DAC).
WifI was not very successful, the connection fails randomly, only restart can solve this.
Apparently because of a malfunctioning ENUP rt8192cu "compatible" adapter.
Switching to a TL-WN722N (I know, different chip set) solved all problems.
Anyway, reverted to a cable connection because that is the way I intend to use it.
RuneAudio plays anything I've got, very pleased with it so far.

Gé

Tinitus

Hi Thanh,

I already use a static IP address. I do not know why the connection to rune audio.local is less stable I do not mind anyway as long as connecting via the IP address is stable.

Hi Gé,

This is seems to be the same problem I am having the Realtek chip seems to be a mediocre solution in this case. Unfortunately I got two of them. Might order a TL-WN something.

Regards

Uwe

hondagx35

Hi all,

i have logged more than 50 downloads since first release (26 Mai).
It would be great to get more feedback from you.

For example:
Has someone tried the remote control feature?

I have installed lirc (ODROID C1 has an ir-receiver) to get this working all you have to do is:
- get a config file for your remote.
!!!!! irrecord does not work proper on arch linux arm !!!!!!
!!!!! so at the moment it is not possible to generate lircd.conf on this device !!!!!!
- adapt the lircrc configuration (nano /etc/lirc/lircrc)
- enable lircd (systemctl enable lircd)
- enable irexec (systemctl enable irexec)

Frank

Tinitus

Hi Frank,

personally I have not tinkered with that. I use my iPhone to connect to the UI that already makes one remote. I do not know which protocol the remote of my amplifier uses, would not be good if the IR signals would interfere with the Odroid if I used the IR receiver of the Odroid.
My next plan is to find out how to make scripts which allow me to just enter the name of the album folder in order to copy said folder to RAM or the emmc . One more script needed in order to delete the files from the emmc.

Thanks for bringing RuneAudio to the C1

It would be nice if others shared their experience

Best Regards

Tinitus

hondagx35

Hi Tinitus,

My next plan is to find out how to make scripts which allow me to just enter the name of the album folder in order to copy said folder to RAM or the emmc .

What is the reason for trying this?
The music is played from RAM anyway (you can tweak this with "Audio buffer size" and "Buffer before play")

Frank

Tinitus

Hi Frank,

I did not know that. Nevertheless my reasons for this are to be able to have the HDD spin down. In order to save energy, to make the HDD last longer and main reason noise. I mostly listen to music at low volume and I don't want to hear the noise of the HDD spinning. A 1 TB SSD is to expensive at the moment at least for my liking.

Greetings

Tinitus

djagab

Dear Ge,

In one of your messages you stated the odroid c1 completely crashed when using a FII0 E18 DAC connected to an ODROID-C1 and playing at 24 bit (24_3LE) format. I have similar results with the odroid c1 when connected to a DAC from HIFIMEDIY: ES9023/SA9023 that supports 24bit/96 kHz playback, or a FiiO E17 DAC. I did not use RuneAudio or Volumio but my own BASS based software player. In a search for a possible cause with the help from the BASS forum I discovered that the odroid c1 with its current kernel version 3.10.x does not support playback at 24_3LE rate using a USB DAC (of this kind). Did you ever manage to get it working without limiting the output to 16 bit?

Thanks in advance for your reply.

djagab

Tinitus

Hi Frank,

one question, is the value in kb the actual buffer size and the percentage value means how much of the buffer size is loaded into ram before play? What difference is there between 2048 kb 10 % and 1024 kb and 20 %?

Best Regards

Tinitus

hondagx35

Hi Tinitus,

What difference is there between 2048 kb 10 % and 1024 kb and 20 %?

2048 kb 10 % = nearly 12s of CD-quality audio and starts playing after 1.2s
1024 kb 20 % = nearly 6s of CD-quality audio and starts playing after 1.2s
So only the buffer size is smaller.

See here.

Frank

Tinitus

Hi Frank,

I see that you are a man of great patience preaching the gospel in the wilderness at least as far as I am concerned. Thanks for the link. My Audio GD DAC works well with 512 kb buffer size and 30 % "delay".
I understand better now what you meant with playing from Ram even if I do not load the music into Ram the HDD spins down. So it seems that not only the buffer is loaded into Ram. Unfortunately the HDD also starts at random probably when the C1 needs to get more data from it. I will still look into the matter of scripting the copying of files to Ram/emmc. 1 GB SSD is 500 € min and it is powered by USB I would prefer a self powered device like my 3.5" HDD.

Best Regards

Tinitus

gkkpch

Hi djagab,

djagab wrote In a search for a possible cause with the help from the BASS forum I discovered that the odroid c1 with its current kernel version 3.10.x does not support playback at 24_3LE rate using a USB DAC (of this kind). Did you ever manage to get it working without limiting the output to 16 bit?

Because everything just plays fine when I use my XMOS DAC, it would not be a 24bit playback problem only.
And yes, as long as I stick to 16bit or DSD in this case, it will work.
It looks more like the C1 in combination with the FIIO E18 or is it the driver used?

To make sure, I attached the FIIO to the ODROID X2 and tried the same.
That seems to work fine, so I'm a bit baffled.
Can you remember where you found the link to the C1 kernel and 24bit support (or lack thereof)?

Gé

Tinitus

Hi,

all my 24 bit .wav files play without any problem via the C1 to my Audio GD (PCM1704UK). I don't think it is a problem of C1 not being capable of 24 bit. Maybe it is something to do with the USB implementation in that particular DAC.

Best Regards

Tinitus

gkkpch

Hi Tinitus,
yes, seems so.
Comparing C1 and X2 was not quite correct though, but an indication that it is not the FIIO itself either.
Because C1 and X2 have different kernel versions, they probably have different driver versions too.

Gé

gkkpch

hondagx35 wrote Has someone tried the remote control feature?

Hi Frank,

Not yet, but could do some testing coming weekend, I have an mce remote here and have to see if that will allow the initial testing.

Gé

thanhvo31

hondagx35 wroteHi all,

i have logged more than 50 downloads since first release (26 Mai).
It would be great to get more feedback from you.

For example:
Has someone tried the remote control feature?

Frank

Hi Frank,

A little off topic but how about porting to Cubox i4pro?

hondagx35

Hi thanhvo31,

A little off topic but how about porting to Cubox i4pro?

Good idea, if you need help let me know.

Frank

gkkpch

Frank,

to be sure before I start, did you install 'plain' lirc or the Odroid C1 remote package?
You were planning for a MCE remote right?
Because "cat /proc/bus/input/devices" produces

I: Bus=0010 Vendor=1b8e Product=0cec Version=0001
N: Name="cec_input"
P: Phys=
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=20000000 0 0 0 0 0 0 0 0 0 0 3c004 2 0 0 1 4 10300 11fa 40000801 1e1680 0 100000 ffc

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="meson-ir"
P: Phys=meson-ir/input0
S: Sysfs=/devices/platform/c8100580.meson-ir/rc/rc0/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=100013
B: KEY=1000000 0 0 0 0
B: MSC=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="MCE IR Keyboard/Mouse (meson-ir)"
P: Phys=/input0
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=sysrq kbd mouse0 event2
B: PROP=0
B: EV=100017
B: KEY=30000 0 7 ff87207a c14057ff febeffdf ffefffff ffffffff fffffffe
B: REL=3
B: MSC=10

gkkpch

Frank,

lircd is running,

 lircd.service - LIRC Infrared Signal Decoder
   Loaded: loaded (/usr/lib/systemd/system/lircd.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 1980-01-01 00:01:27 CET; 35 years 5 months ago
 Main PID: 283 (lircd)
   CGroup: /system.slice/lircd.service
           ââ283 /usr/sbin/lircd --nodaemon

but irw is not echoing anything when I press a button on the remote.
I need some help to start...

EDIT:
OK, I stop the lircd daemon first.
- then I start lircd with '/usr/bin/lircd -n -d /dev/lirc0'
- then 'irw' and lirc shows me a new client connection.
So, basicly lirc works.
- pressing keys in irw does not give any echo
- then I start 'mode2 -d /dev/lirc0'
- then I press keys and: I get a load of pulses and spaces

So, receiver works, remote works, it must be a configuration then.
OK, stop the lircd daemon
- start lircd 'lircd --nodaemon ./lircd.conf'
- next tty session 'ir-keytable -t -d /dev/input/event1'
- and press some keys: also getting scancodes

And now I'm really stuck, I'm missing a link...

Any input will help, I will continue in the meantime and dig into lirc...

Gé

hondagx35

Hi Gé,

we only things you have to do is:
- get a config file for your remote
- adapt the lircrc configuration (nano /etc/lirc/lircrc)
- enable lircd (systemctl enable lircd)
- enable irexec (systemctl enable irexec)

as i described here.

Normally you can record your own configuration file with lirc on the device.
This does not work on Arch Linux Arm.
So you have to get a premade config file for your remote.

gkkpch

Hi,

Found the problem and created a new lircd.conf as a fix for an MCE remote, need a bit of time to consolidate and test.

Gé

« Previous Page Next Page »