admin said

Getting really close to release...

exciting!

I'm planning to use Udoo with eSATA HDD and Kingrex Slap! Batterry PSU

yeah!!!

admin said

1- New website and porting to Udoo, Beaglebone black and Cubox
2- Android app
3- i2s dac

I wonder do you plan to also support odroid (http://hardkernel.com)?

RaspyFi is working great for me since a week on my raspberry pi B but some times it lags when there is to much IO or CPU utilization. So more power would be great and that is exactly what the odroid can deliver.

I'm using a Schiit modi DAC and a TP-Link wireless adapter at the moment.

I had to add the kernel module manually for the wireless adapter, maybe you can add it out of the box?

http://www.raspberrypi.org/php.....88#p454488

looking forward for the new version and great work, this distro looks awesome.

admin said
Were you using Voyage Mubox?
RaspyFi on Cubox works like a charm for me....
Yep, udoo is the most interesting platform out there... Spdif out, i2s out, quad core, an excellent analog out... It's a game changer
Also the new cubox-i looks really promising as well. In my opinion these are the 2 best board available as of now. I speak for audio purposes obviously...

Yes I was using Voyage Mubox. Headache... just headache.
RaspyFi + Wavelength Proton (Hardware Volume Control) = nearly perfect.
I'm REALLY looking forward for your Udoo port.

Cheers

admin said

1- New website and porting to Udoo, Beaglebone black and Cubox
2- Android app
3- i2s dac

Nice
When's the ETA?

yoghurtlidlicker said

admin said
1- New website and porting to Udoo, Beaglebone black and Cubox
2- Android app
3- i2s dac

cool,
i just sold cubox
it was cracking/zapping more that raspberry pi.
I hope that reaspyfi going to work well with async dacs on cubox!
fingers crossed

Were you using Voyage Mubox?
RaspyFi on Cubox works like a charm for me....
Yep, udoo is the most interesting platform out there... Spdif out, i2s out, quad core, an excellent analog out... It's a game changer
Also the new cubox-i looks really promising as well. In my opinion these are the 2 best board available as of now. I speak for audio purposes obviously...

admin said

1- New website and porting to Udoo, Beaglebone black and Cubox
2- Android app
3- i2s dac

cool,
i just sold cubox
it was cracking/zapping more that raspberry pi.

I hope that reaspyfi going to work well with async dacs on cubox!

fingers crossed

admin said

Be patient then, I'm still here. Just preparing something big for all of you guys .

This made me curious, could you give a hint on what it might be?

I will investigate WiFi bandwidth and data rate.

see here:

http://en.wikipedia.org/wiki/Procfs

So these files are just controlled by alsa. Alternatively we can use a custom script to handle them. But I doubt it would be useful. This is just a bandwith problem. Is your wireless network going at N speed? And your dongle?

This suggests that the presence or absence of the prealloc and prealloc_max files are controlled by alsa based on what it thinks is required for the device,

Another setting I'm investigating that involves dropouts caused by buffer underrun is in alsa files named prealloc and prealloc_max in the directory /proc/asound/card*/pcm*p/sub0$.

The setting in prealloc defaults to 64 (64K) and some forum posts indicate that bumping it up can resolve audio dropouts for high bit rate files, In my configuration however, the file does not exist for card0/pcm0p/sub0 (my HRT MSII DAC) but does exist for card1/pcm1p/sub0. In either case I am unable to add or edit prealloc, probably because of permissions.