Introducing DSPi | A powerful, user friendly and open source DSP for less than a cup of coffee

[Weeb Labs]

yes ground is connected neg terminal of RCA with the attached components connected as shown in ATT

Could you verify that you are using GPIO 10 and not simply pin 10? One might assume they mean the same thing but they're actually different pins. GPIO 10 is on physical pin 14.

 

[Barrelhouse Solly]

Got a pico 2W today and am running into a problem installing the firmware. I downloaded DSPi-refactor.zip and expanded it. I copied DSPi-RP2350-v1.1.0.uf2 to the drive named RP2350. The drive icon disappeared. I unplugged and replugged the USB cable (holding down the Bootsel button. The drive reappeared as RP2350. The timestamp on INFO_UF2.TXT and INDEX.HTM are both 9/5/2008. In Device Manager it's listed as RP2350 Boot. I assume I've made an obvious mistake. I'd appreciate direction to the right path. Oh, the Pico works. I installed MicroPython and ran a print statement as a test.

 

[Weeb Labs]

Got a pico 2W today and am running into a problem installing the firmware. I downloaded DSPi-refactor.zip and expanded it. I copied DSPi-RP2350-v1.1.0.uf2 to the drive named RP2350. The drive icon disappeared. I unplugged and replugged the USB cable (holding down the Bootsel button. The drive reappeared as RP2350. The timestamp on INFO_UF2.TXT and INDEX.HTM are both 9/5/2008. In Device Manager it's listed as RP2350 Boot. I assume I've made an obvious mistake. I'd appreciate direction to the right path. Oh, the Pico works. I installed MicroPython and ran a print statement as a test.

After writing the UF2, the drive should disappear and you should then find that you have a new audio device available called Weeb Labs DSPi. That's all you need to do.

Bootsel only needs to be held while connecting the device when you intend to flash the firmware.

 

[Wesseling Audio Lab]

Could you verify that you are using GPIO 10 and not simply pin 10? One might assume they mean the same thing but they're actually different pins. GPIO 10 is on physical pin 14.

View attachment 511763

Looks right to me.

 

[Wesseling Audio Lab]

I checked it at the pins with AC meter with music playing and 0.00v. should be some sort of fluctuating reading. I could scope it but I'm certain there's no output

I keep thinking there's something in console I should be adjusting but PDM bar shows output so?

 

[Weeb Labs]

I checked it at the pins with AC meter with music playing and 0.00v. should be some sort of fluctuating reading. I could scope it but I'm certain there's no output

I keep thinking there's something in console I should be adjusting but PDM bar shows output so?

My apologies. As it turns out, the mistake is entirely my own.

Prior to the new architecture, PDM was on GPIO 21, not GPIO 10. I even made this mistake in the version of my own documentation that was available at the time.
I have just flashed a Pico 2 with v1.0.7 and confirmed that PDM is on GPIO 21.

 

[Barrelhouse Solly]

After writing the UF2, the drive should disappear and you should then find that you have a new audio device available called Weeb Labs DSPi. That's all you need to do.

Bootsel only needs to be held while connecting the device when you intend to flash the firmware.

Thanks, I hoped it was as simple as that. I have a new audio device. Is my next step hooking up a toslink port? I guess the thing that threw me when I was trying before was the error message in the console that says "no USB device visible." That's still there. I do have a USB device called Weeb Labs DSPi that I didn't see previously in Device Manager. I'll have a chance tomorrow to see how I'm doing.

 

[Wesseling Audio Lab]

My apologies. As it turns out, the mistake is entirely my own.

Prior to the new architecture, PDM was on GPIO 21, not GPIO 10. I even made this mistake in the version of my own documentation that was available at the time.
I have just flashed a Pico 2 with v1.0.7 and confirmed that PDM is on GPIO 21.

No problem at all and many thanks! I have PDM out now. Tomorrow acoustic measurements and work at integrating an SB Acoustics sub with stereo pair at sides of TV

 

[Wesseling Audio Lab]

Is Linkwitz transform coming in the future
Also, wondering if the loudness compensation is the same as what I was mentioning earlier.
I was thinking woofer protection from over excursion. When volume increases, bass is rolled off increasingly higher in step with increased volume

 

[Weeb Labs]

Thanks, I hoped it was as simple as that. I have a new audio device. Is my next step hooking up a toslink port? I guess the thing that threw me when I was trying before was the error message in the console that says "no USB device visible." That's still there. I do have a USB device called Weeb Labs DSPi that I didn't see previously in Device Manager. I'll have a chance tomorrow to see how I'm doing.

The current Windows release still exhibits the USB descriptor bug that was fixed in the newer versions, which prevents Windows from knowing which driver to install for the control interface. This is assuming you are using firmware v1.0.7, which is the correct one for the current Windows release.

Simply grab this application, launch it and select "Weeb Labs DSPi (Interface 2)" from the dropdown box. Make sure "WinUSB" is selected next to the green arrow and then choose "Install Driver". Give it a few minutes to install.

Once installed, everything should be working and you should have two DSPi devices; one under "Sound, video and game controllers" and the other under "Universal Serial Bus devices".

DSPi Console will then work correctly.

 

[Weeb Labs]

Is Linkwitz transform coming in the future
Also, wondering if the loudness compensation is the same as what I was mentioning earlier.
I was thinking woofer protection from over excursion. When volume increases, bass is rolled off increasingly higher in step with increased volume

Yes, the Linkwitz transform filter type is still on the way.

Loudness compensation is similar in principle to dynamic range compensation but it offers fewer parameter constraints. It raises bass and certain treble frequencies (see Fletcher-Munson equal loudness contour) as volume is reduced in order to produce the same perceived response at lower listening levels. It does not offer manual control over target frequencies or SPLs.

Dynamic range compensation is planned but will come after DSPi Console for Windows is brought up to feature parity with the macOS version.

 

[Luffy]

Ah, I see. Could you confirm which version of the firmware you are using? For the current Windows release, you should be using firmware v1.0.7.

Speaking of the DSPi Console for Windows, I am now in the process of bringing it up to feature parity with the macOS version. This will be the next major release.

View attachment 511625

Hey, I tried using firmware version 1.0.7, and now I’m facing a new issue, there’s no audio coming out of the speakers.

In the console, I can see the signal meters responding, so the input signal is definitely reaching the DSP, but there’s no actual audio output from the speaker.

And for comparison, when I switched back to firmware version 1.1.0, the audio was coming out properly. So any help would be really appreciated.

 

[Weeb Labs]

Hey, I tried using firmware version 1.0.7, and now I’m facing a new issue, there’s no audio coming out of the speakers.

In the console, I can see the signal meters responding, so the input signal is definitely reaching the DSP, but there’s no actual audio output from the speaker.

And for comparison, when I switched back to firmware version 1.1.0, the audio was coming out properly. So any help would be really appreciated.

The output pins for v1.0.7 are different. SPDIF is GPIO 20 and PDM is GPIO 21.

 

[Sonic-Wall]

I highly recommend to use a Pico breakout board. The yellow LEDs indicate the active GPIOs and any changes can be easily accommodated without soldering. You can also easily switch between the 2040 and the 2350!

 

[m_g_s_g]

View attachment 511578

Fork with OLED SSD1306 supported VU meter added here.

If somebody has a spare OLED SSD1306 with default 0x3c address and wants to try, testing should be quick with the provided RP2350 compiled uf2.

- For now, CH_MASTER_L is shown.
- Bitmaps have been converted using a low quality utility; better ones without noise pixels should be possible, all limited to the (very) low 128x64/32 resolution.
- Two (or more) displays should be possible, but to change the I2C address of cheap SSD1306 oleds, cutting traces might be needed (most of them ship with a hardsoldered address).

 

[TurtlePaul]

I am working on a case. I didn't consider that the light weight wouldn't be able to hold down the rather thick Toslink cable. Still a work in progress. Can't wait for Windows console 1.1.0.

 

[Weeb Labs]

I am working on a case. I didn't consider that the light weight wouldn't be able to hold down the rather thick Toslink cable. Still a work in progress. Can't wait for Windows console 1.1.0.

View attachment 512020
View attachment 512021

DSPi Console v1.10 for Windows will be released within the next couple of days. I can't wait to hear everybody's opinions.

 

[capslock]

Could you please explain whether the 16 bit input limitation is fundamental or tied only to USB 1.1 or just temporary or not applicable to SPDIF input. I'd like to understand before I try to hop on the train. Thanks

 

[Weeb Labs]

Could you please explain whether the 16 bit input limitation is fundamental or tied only to USB 1.1 or just temporary or not applicable to SPDIF input. I'd like to understand before I try to hop on the train. Thanks

The 16-bit input limitation is not a hardware performance limitation. Support for 24-bit input and output are planned but this will require a refactor of some core components.

 

[Kingsnake]

I highly recommend to use a Pico breakout board. The yellow LEDs indicate the active GPIOs and any changes can be easily accommodated without soldering. You can also easily switch between the 2040 and the 2350!
View attachment 511873

I am assuming the rca out is a subwoofer LFE and toslink is a stereo pair. How can one GP06 do both? Or is the the RCA a second SPDIF out?