Hi chuckkh, After reading your posts again I think you are headed in the right direction. The 16 bits per sample and the FS (LRCLOCK) of 44.1kHz should be fine, but the clock speed (BITCLOCK) that should be fed into the Raspberry Pi should be lower. When I make a quick calculation I get to: 16 bits ...

Okay, I fixed it... After wasting about 3 days trying to find the mistakes I made, I read something in chuckkh's topic here about bad timings on the Pi 3. I grabbed a Pi B+ and everything magically started working! The Pi now uses the 3.072MHz clock and the 48kHz LRCLOCK from the DSP4YOU DG unit wit...

Hi chuckkh, Thanks again for your reply! I'm going to implement all the new information into my software today. What I didn't know was that the I2S protocol handles a lot of stuff itself. I can only have 16 to 24 bits of data (firmware limitation of DSP4YOU DG) but since the bitclock runs at 3.072MH...

Thanks again for your reply! I have been thinking what to do now. The DSP4YOU hardware is master and outputs a 3.072MHz System Clock that I could use. It accepts 16 or 24 bit data input per channel. When using 24 bits, this corresponds to the 64 * Fs calculation you provided. 64 * 48KHz = 3.072MHz. ...

Hi Chuckkh! Thanks for your reply, could you explain the calculation you did for the clock speed? :) I didn't know the master clock wasn't needed in this case. I will try some other clock signal today. I'm also starting to wonder now if the Pi needs to be clock slave at all, or that only syncing on ...

Hi all, I'm currently working on a project where I want to connect the Raspberry Pi I2S bus to the DSP4YOU DG hardware. Additional info found here: http://www.dsp4you.com/products/avb-oem-series/avb-dg I've tried a lot of different things but I'm unable to get the Raspberry Pi to use the external cl...