Tested with a jack 3.5 to USB adapter + headset with microphone and jack 3.5 connection: it works much better. Some background noise can be listened, but nothing very important. I suppose, with the right headset, sound would be event much better.

@asyxcv, you should compile it manualy, next link will be usefull: How to compile C/C++ native applications You are trying to use old manuals about LEDE. Another way your project has also special manifest for the OpenWRT system (see snapcast/openWrt/Makefile.openwrt) it needs to make .ipk-files (packages) for the opkg util. But this file is old and needs to be fixed. And last: making your own packages for opkg is very difficult task for masters. More infirmations about it you can get from OpenWRT official documents, community and examples.

Yes, I've already started looking at webcams (on Amazon), and definitely found a few that have built in microphones. I was just hoping to hear from someone who can confirm that they've already tried it and that it does in fact work. What about connecting 2 different USB devices to the Onion (ie: a webcam + audio device)? Does anyone here know of some kind of USB splitter or hub that doesn't require an external power source? -- Yvan

@Felipe-Duque Hi, indeed Omegas need a complete support for I2s audio. Someone did output some time ago,but apparently vanished...

Apparently, I am seeing the same thing also. Investigating.

Any update about I2S on latest firmware ?. I'm also trying to configure I2S audio with omega2S+.

No feedback from Onion in 30d? Pity.

Yes about sign : drivers which were used as bases of our omega simpleaudio driver seemed S16 as normal but if Andrew is sure it actually sends unsigned then that is the problem : If the maxxxxxx driver actually uses the unsigned (weird unstandart and rare) 16bit format then we need to switch our firmware to builds using an asoc/alsa wm8960 or pcm5102 or whatever else is available as nearly ALL OTHER i2s drivers would provide us the usual/standart (i2s meaning signed) our DAC chips need. "MCK lack" subject is not the problem here because I also use a i2s DAC chip that features an MCK generation builtin because MT7688 chip does not have any MCKout. These 2 matter would make me much regret the former ar9331 soc chip...

Edit: for reference, see here,

Thank you! Just don't wanna spend money on something that won't work is all so I figured I'd ask the experts here

New demonstration video: There are random corruptions happening on the SPI display, where some other pixels outside of the normal rectangle are overwritten. I don't know yet if that's an issue in my driver (timing violations maybe?) or with the SPI interface, but because the entire frame is overwritten each tick, the corruption is only visible for a short amount of time.

This thread probably is the closest one to get I2S based audio codec to work: http://community.onion.io/topic/1761/resolved-attaching-pcm5102-to-omega2-i2s You'll have to get your own inspiration. BTW, since there is no OSC_out pin brought out to be exposed in the PCB (most won't, it is not a good idea w/o termination anyway), you might just as well put your own oscillator on the SGTL5000 codec board.

It does not say that your file does not exist - this message says that ash cannot find any executable in bin named foghorn1.wav, which should be run. The same way when you write eg. ls - ash then looks for a proper executable in bin and if no results are yielded, returns an error message. If you want to run a file from current directory, you'd need to write ./my-file, but it only works for executables, which - clearly - a music file is not. I dont see what the converter has to do with not finding and playing a file You cannot play music without a music player, look at examples: https://www.raspberrypi.org/documentation/usage/audio/ https://superuser.com/questions/276596/play-mp3-or-wav-file-via-linux-command-line Nowhere there you'll find ./my-file.mp3 nor pure my-file.mp3. You'd need to install some music player and hope it gets along with your converter.