Well, the last changes are listed as having been made on February 9. GitHub seems to have generously rounded up the creation date.The github folders are over 2 month old, this thread started on Feb 5, so ... intersting![]()
Well, the last changes are listed as having been made on February 9. GitHub seems to have generously rounded up the creation date.The github folders are over 2 month old, this thread started on Feb 5, so ... intersting![]()
That's interesting, if a little hard to read the schematic. I'd love to know if they got as far as building a prototype, also I wonder if the existing binary is usable with a Xiao-RP2350?I found this PCB idea doing a Google search
I2S switching now works as expected, but committing changed parameters (pin assignment, PEQs...) to board is still not possible on RP2040. Error dialog appears with "Failed to save parameters"I have just released DSPi Firmware v1.1.3-beta3 and DSPi Console v1.1.3a for macOS.
This release fixes the I2S switching issue on RP2040 ...
It operates in the opposite direction to that of a standard compressor. Rather than attenuating content above the threshold and applying makeup gain against a limiter, it amplifies content below the threshold and leaves content above it untouched.It looks like a normal compressor/limiter in use for PA reinforcement but instead of having adjustable attack and release parameters it has three settings for attack and release, interesting, I would like to see it work with an oscilloscope
Thanks for that. I will look into this.I2S switching now works as expected, but committing changed parameters (pin assignment, PEQs...) to board is still not possible on RP2040. Error dialog appears with "Failed to save parameters"
Yes. You can use up to four of these modules.Hello, a 'PCM5102A I2S DAC Decoder Audio Module' works very well here.
Is it already possible to use two of these I2S modules?
Thank you very much for the bug report. This is being caused by an oversight on my part. Each I2S state machine is attempting to drive the same clock pins when enabled. I need to implement some master/slave promotion logic for the I2S outputs.I added a second module and configured everything for a 2.2 setup. I split the BCK and LRCK pins and connected the DIN pins to two separate GPIOs.
As soon as I set the second output to I2S in the console, I get severe interference on the first I2S output. The interference occurs even when only one module is connected.
Both modules work fine when connected separately and with only one I2S output active.
I have attached an experimental revision, if you might be interested in testing it. I would recommend switching various slots between types. Whichever slot you first switched to I2S, switch it back to SPDIF and verify that other active I2S outputs continue to function correctly.I added a second module and configured everything for a 2.2 setup. I split the BCK and LRCK pins and connected the DIN pins to two separate GPIOs.
As soon as I set the second output to I2S in the console, I get severe interference on the first I2S output. The interference occurs even when only one module is connected.
Both modules work fine when connected separately and with only one I2S output active.
Only one USB input is possible but it will eventually support 8-channel input from the host. USB output from DSPi is not possible. I2S, SPDIF and ADAT input are all planned, though.Thanks for your great work Weeb Labs.
Did not read the whole thread back…
Questions:
- Is a second input pair of USB audio on your ToDo list and at which position?
- Will the other way around be implemented at some time (4ch I2S input -> 4ch USB output)?
Loudness compensation is currently controlled exclusively via the USB host volume control. It is unaffected by DSPi's input channel preamp or output channel gain controls. This will soon be configurable, as external control is being implemented.For instances when the player / renderer is not running on the USB Host device outputting to the DSPi but farther upstream
Does the loudness-compensation strength varying with volume, only work when using the DSPi's level control and/or USB Host's Master volume?
or can it adjust itself based on detected changes from volume controls on a device upstream of that USB Host?
this stability problem exists only for USB input, so I2S and SPDIF inputs will be permissive of higher clocks once implemented.
Turns out this last is false.So, my 3x SYN RCA analog output channel pairs – not all are stereo
each feed a miniDSP PocketADC which outputs digital via S/PDIF TOSlink optical at 24-bit / 96kHz
to HiFiMeDIY UR23 DDC which feeds a DSPi
yes these function as USB Host
www.audiosciencereview.com
SPDIF input is a priority and I have been working on it continuously. I expect to have a production-ready implementation by the end of the month but it is difficult to make guarantees.Turns out this last is false.
So, it seems I need to run each of these three DSPi's from full-fledged computers (thinking Raspberry Pi's)
Unless there ARE DDC units out there that can act as USB Host.
![]()
ISO DDCs with USB Output, act in USB Host mode, work without a computer
I thought one of the HiFiMe devices worked like this, turns out I was mistaken got bad info. Not looking for an ADC or audio interface, or hybrid DAC / mixers etc, but if these do exist with this capability, please do post. Technically the Wiim devices' USB output do qualify, but those are in...www.audiosciencereview.com
Or else I just wait for the new inputs to be implemented. Any ballpark timeline on that, as in weeks vs months?
Will it be possible to change the volume together with the loudness compensation from something connected with a SPDIF input?Only one USB input is possible but it will eventually support 8-channel input from the host. USB output from DSPi is not possible. I2S, SPDIF and ADAT input are all planned, though.
Loudness compensation is currently controlled exclusively via the USB host volume control. It is unaffected by DSPi's input channel preamp or output channel gain controls. This will soon be configurable, as external control is being implemented.
It doesn't perform any kind of level detection, as this would not produce accurate compensation.
Not even back to the host via current USB connection? So audio data would go both ways?Only one USB input is possible but it will eventually support 8-channel input from the host. USB output from DSPi is not possible. I2S, SPDIF and ADAT input are all planned, though.![]()
Or else I just wait for the new inputs to be implemented. Any ballpark timeline on that, as in weeks vs months?