I would imagine "low power bidirectional isolators" are the last things you would want to use here.
Whatever buffers you include to split the signal will introduce jitter and subsequent reclocking will, at least in concept, be needed if you aim for a low jitter system.
Otoh, i cannot imagine the need for a low jitter I2S signal at the input of the miniDSP - what you need is a reclock after the DSP.
Just realised the miniDSP does not have I2S outputs, so reclocking is obviously not possible.
Maybe Joro can advise on a suitable buffer ic for the MCK. The other signals... i wonder if both inputs cannot be supplied from the same set of outputs with just separate inline resistors...
Maybe Joro can advise on a suitable buffer ic for the MCK. The other signals... i wonder if both inputs cannot be supplied from the same set of outputs with just separate inline resistors...
Hi,
ISO1540 is not proper for I2S, it's too slow. If I haven't miss something from the link:
this device should have I2S input and outputs. I agree to analog_sa, in this case you can connect Buffalo directly and miniDSP through line resistors 100 - 150ohm. Exact resistances depend on input capacitance of I2S line of miniDSP. Buffalo doesn't need reclock, because it's "jitter free" I2S, but miniDSP must has reclock, because it will bring jitter. As for master clock transfer, I would recommend LVDS logic (maybe the line will be long).
Regards,
Joro
hi there
are the drivers on XMOS site WDM or not ? i'm mainly a linux user but here and there i reboot to windows and would like to know if it works with windows ?
are the drivers on XMOS site WDM or not ? i'm mainly a linux user but here and there i reboot to windows and would like to know if it works with windows ?
Hi Joro,
just discovered this thread ... will put myself on the GB tread for your XMOS board as is, but if you could implement the timings for the PCM56, that would be a clear additional value!
So one more further encouragement from my side for the implementation!
Also, if there would be an option to directly power the board from external 3.3V (A123 LiFoPo), that would be very welcome as well!
Keep up the good work,
Abel
4. ... or right-justified data
and
I was playing with the software and I succeeded to bring format for PCM1704
What is the difference?
and
I was playing with the software and I succeeded to bring format for PCM1704
What is the difference?
Dear Joro,
I will be immensely grateful if you can show me an example with a circuitry to give me a better understanding of what you are talking about! May I thank you in advance!
Last edited:
Hi,
USB AUDIO 2.0 REFERENCE DESIGN | XMOS
https://www.xmos.com/en/download/public/USB-Audio-2.0-Stereo-Driver-for-Windows-Overview.pdf
LP5900 requires 4.3V on input, but can tolerate up to 5.6V. Without changing components, 4 x LiFePo 1.2V will provide enough power for normal operation.
I attached a picture for you.
PS There is thread for PCM1704, PCM63, PCM56 and other DAC and there one can discuss only about DACs which requiring separate data channels:
http://www.diyaudio.com/forums/digi...56-pcm63-others-nos-mode-pc-oversampling.html
Regards,
Joro
USB AUDIO 2.0 REFERENCE DESIGN | XMOS
https://www.xmos.com/en/download/public/USB-Audio-2.0-Stereo-Driver-for-Windows-Overview.pdf
LP5900 requires 4.3V on input, but can tolerate up to 5.6V. Without changing components, 4 x LiFePo 1.2V will provide enough power for normal operation.
The difference is that RJ for one sample form of WS (L / R) is a meander, and the low level data is transferred to the left channel, the high data right channel, i.e. successively. If we want to have stereo PCM1704 without additional treatments, one has to use two separate parallel data channels.
I attached a picture for you.
PS There is thread for PCM1704, PCM63, PCM56 and other DAC and there one can discuss only about DACs which requiring separate data channels:
http://www.diyaudio.com/forums/digi...56-pcm63-others-nos-mode-pc-oversampling.html
Regards,
Joro
Attachments
Hi,
I will send you a PM.
I'm glad that everything is fine.
Regards,
Joro
I will send you a PM.
I'm glad that everything is fine.
Regards,
Joro
Drivers.
I was asked in another thread about the XMOS/Thesycon demo drivers.
They run for 1 Hour and then "beep" every 5 minutes.
Re plugging the device (no need to re boot) give you another "beep" free hour.
I have re plugged 5 times over 5 hours, still no "beeps".
I was asked in another thread about the XMOS/Thesycon demo drivers.
They run for 1 Hour and then "beep" every 5 minutes.
Re plugging the device (no need to re boot) give you another "beep" free hour.
I have re plugged 5 times over 5 hours, still no "beeps".
Hi Joro,
can you help me?
When i plug your kit to the laptop usb port there's a flashing beep and device is not recognized.
OS is win 2012 server.
Have you tried it with this OS?
Is there anything I can do?
Best,
Frank
can you help me?
When i plug your kit to the laptop usb port there's a flashing beep and device is not recognized.
OS is win 2012 server.
Have you tried it with this OS?
Is there anything I can do?
Best,
Frank
If I remember well power switch port was " self powered".
Shurely I should choose something like usb or bus powered Surprised.
What do you think about?
Next in the afternoon when I'll come back home.
Frank
Shurely I should choose something like usb or bus powered Surprised.
What do you think about?
Next in the afternoon when I'll come back home.
Frank
Leave the usb power jumper on. And please answer the question: USB chipset? The problematic one i had was made by Renesas.
Yes, same laptop and port.
Only Os are different.
I think I'll have a look at port power management and switch between Vista, W7 and server 2012.
Frank
Only Os are different.
I think I'll have a look at port power management and switch between Vista, W7 and server 2012.
Frank