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

[Turboscienziato]

Could you please provide a copy of the file that doesn't import properly?

These are filter file exported from the Console itself. Once imported, decimals are not included even if they are present in the file. I'm use latest Firmware and Console for Windows.

 

[Kingsnake]

Just wanted to share some updates on my current enclosure build. I’ve managed to take advantage of the new update and implement a master volume control using a rotary encoder, which now tracks properly with loudness compensation. The encoder’s push button also mutes the volume.

I’ve also added a small RF module with a four-button remote. At the moment, it controls volume and mute, and the fourth button will eventually be used for source selection once that’s implemented.

The remote works well with the enclosure open, giving me around a 3m range. However, once the aluminium lid is on, the range drops to about 0.5m, which obviously isn’t usable.
I’ve ordered a 170cm 90-degree antenna that I plan to mount on the rear of the enclosure—hopefully that will improve the signal.

There’s currently a bug in the firmware where the master volume isn’t saved to a preset. Troy has already identified the issue, so I’m holding off on sharing this build until that’s resolved and the master volume state is properly saved.

 

[Tell]

Looking at the roadmap it looks a bit outdated, you got any updated one? Personally looking forward to GPIO control with rotary encoders and buttons, SPDIF input and three channel stereo

 

[snk4ever]

Looking at the roadmap it looks a bit outdated, you got any updated one? Personally looking forward to GPIO control with rotary encoders and buttons, SPDIF input and three channel stereo

Waiting for I2S input on my side. I would like to use it with two I2S sources and one SPDIF output.

 

[markz]

Please, if you are posting photos, note that once you see them on the display in your post editor you can resize them with the border. For those of us browsing the forum a set of smaller photos makes life so much nicer than a half page of your rig.

It's always possible to click a photo and it will popup full size.

 

[Weeb Labs]

Looking at the roadmap it looks a bit outdated, you got any updated one? Personally looking forward to GPIO control with rotary encoders and buttons, SPDIF input and three channel stereo

Yes, the roadmap is in need of an update!

Users have also reported a couple of bugs (which are now fixed), so I'll be pushing a hotfix shortly and then finally merging the output-type-overhaul to main.

 

[Barrelhouse Solly]

Sometimes I feel like my subconscious is creating computer problems behind my back so I have something to occupy my time. Yesterday my office computer stopped recognizing DSPi devices. The mini-pc in my bedroom recognizes them. On the office box when I plug one in it throws an Error 43, "Windows has stopped this device because it has reported problems. (Code 43) The SuperSpeed link to the USB device keeps going to an error state SSInactive." I've tried the list of trouble shooting and repair recommendations available on line for this error and have come up empty. I've done things like going into Device Manager and deleting all USB devices. On both machines I'm using the Zadig provided libusb-win32 driver. v 1.4.0.0. While Windows fails to recognize the device when I connect it, my DAC believes it has a good connection and the DSPi console recognizes the device and can perform all its normal operations. The computer is running Win 11 Home, build 26200.8246, Windows Feature Experience Pack 1000.26100.297.0. I am current on OS updates; I apply them automatically. On the Pico I'm running firmware v1.1.3a and console v1.1.3-hotfix. I'm thinking of trying a "therapeutic" Windows reinstall that retains programs and data under the Use Magic protocol.

 

[Kingsnake]

Sometimes I feel like my subconscious is creating computer problems behind my back so I have something to occupy my time. Yesterday my office computer stopped recognizing DSPi devices. The mini-pc in my bedroom recognizes them. On the office box when I plug one in it throws an Error 43, "Windows has stopped this device because it has reported problems. (Code 43) The SuperSpeed link to the USB device keeps going to an error state SSInactive." I've tried the list of trouble shooting and repair recommendations available on line for this error and have come up empty. I've done things like going into Device Manager and deleting all USB devices. On both machines I'm using the Zadig provided libusb-win32 driver. v 1.4.0.0. While Windows fails to recognize the device when I connect it, my DAC believes it has a good connection and the DSPi console recognizes the device and can perform all its normal operations. The computer is running Win 11 Home, build 26200.8246, Windows Feature Experience Pack 1000.26100.297.0. I am current on OS updates; I apply them automatically. On the Pico I'm running firmware v1.1.3a and console v1.1.3-hotfix. I'm thinking of trying a "therapeutic" Windows reinstall that retains programs and data under the Use Magic protocol.

Try switching to WinUSB instead of libusb-win32

 

[Barrelhouse Solly]

Try switching to WinUSB instead of libusb-win32

It was worth a try. I got the same results.

 

[Kingsnake]

It was worth a try. I got the same results.

Go to:

Device Manager USB Root Hub / Host Controller
Disable:
Allow the computer to turn off this device to save power

 

[krisdeak]

Hey Troy, @Weeb Labs do you think you could help us less coding savvy with a current, most up-to-date compiled pre-release version of 1.1.3a PLUS SPDIF Input?
I think a lot of us would love to beta test it to help you squash all the bugs.
(Hands up folks, if your use case is also Wiim Mini to DSPi via toslink!)

 

[Barrelhouse Solly]

Go to:

Device Manager USB Root Hub / Host Controller
Disable:
Allow the computer to turn off this device to save power

Tried it on the hub to which the device is connected with the same results. It throws error 43.

 

[Weeb Labs]

Hey Troy, @Weeb Labs do you think you could help us less coding savvy with a current, most up-to-date compiled pre-release version of 1.1.3a PLUS SPDIF Input?
I think a lot of us would love to beta test it to help you squash all the bugs.
(Hands up folks, if your use case is also Wiim Mini to DSPi via toslink!)

I’m afraid the best I can do in that regard at the moment is to push an alpha release of v1.1.4, as it is a completely new branch with massive refactors and architectural changes in comparison to v1.1.3.

Once main is merged later this evening, I will look into pushing a v1.1.4-alpha release.

 

[Barrelhouse Solly]

The exciting saga of, well the events surrounding, continues. I did a therapeutic reinstall of Window$ on the picky machine. It's still picky. Because it was sitting on my desk, I tried one of the picos that the Window$ machine doesn't want to associate with on a Pi3A+ running Squeezelite. A few days ago they were incompatible. Now they interact companionably. I wonder if the firmware update yesterday made the pico more attractive to its distant relative. If nothing else it's a kind of validation for the USB cable I used. Fooling around with computing devices is for me what woodworking or fooling around with cars is for others. It's what people who care for animals call an enrichment activity. For me it's a way of avoiding heavy lifting and not having to suffer the limitations of my fine coordination.

 

[Weeb Labs]

The merge to main is now complete! I have pushed a small hotfix for DSPi Firmware v1.1.3a and DSPi Console v1.1.3a for Windows.

Here are the changes:

• Squashed a longstanding bug that could cause high volume at startup, depending upon preamp attentuation
• Master volume now has two modes of operation: global and per-preset
• Master volume now has a factory default value of -20dB for safety

Console has been updated to implement support for master volume mode selection and I took the opportunity to roll the new "copy to" function into it for presets. Commas are now supported as decimal points when importing filter text files, @Turboscienziato.

The readme has also received a much needed update and now includes a detailed list of all default pin assignments among other handy things.

This should be the last release for v1.1.3. Unless an urgent bug is identified, I will now be directing most of my effort toward v1.1.4.

 

[Rocky Maine]

Upgraded to DSPi Firmware v1.1.3a-hotfix and Tidal still won't play 24/96. I discovered that if I turn off Tidal exclusive mode it plays at that resolution.

I also updated the console to DSPi Console v1.1.3a-hotfix. The Update Firmware function now works and Stats for Nerbs shows values. Thanks.

 

[markz]

Interesting Project?
I've started a small application to help with DSPi pico and wonder if other people are interested. I can post it on Github for folks to play with but the Mac server is not yet talking to my Pico so I'm not quite there although this does work fine with Windows at the moment.

Anyway, here's the idea

1) There is a small command-line server that runs on your music computer that's plugged into the DSPi Pico USB. The server is standalone and talks to the USB port at the same low level as the DSPi Console. The server talks to a Network Port (i.e. a web service).

2) There is a (remote) Client application that can talk to the remote network port that the server lives at. The client sends control commands to the server which controls DSPi.

So, instead of running DSPi-Console on the computer (which in my case is a Mac) you can run this little server and talk to it from anywhere on your local network.

This is just two days of work for now so it's quite rough but the following photos should give you an idea of how it works. Currently it should run on Windows, Mac, and Linux (both the server and the client are multi-platform written in C#/Avalonia).

In the below example I brought up the client, typed a few commands (ping has it send back pong), then brought up the Device Control window and moved the volume slider.

The Server

The Client

Here as you can see the client comes up (shown on right) and lets you send Cli commands via text or pop up the Device Control window with a tiny GUI for volume, mute, loudness, whatever.

In the above photos the Server is running on my office desktop with my music running and the client is on my laptop.

Mark

Postscript: the Mac issue was simply solved by pointing it at the libusb folder
Postscript2: part of this is a simple gui via web so here's the web version of this delivered by that same command line server.

 

[olki]

Sometimes I feel like my subconscious is creating computer problems behind my back so I have something to occupy my time. Yesterday my office computer stopped recognizing DSPi devices. The mini-pc in my bedroom recognizes them. On the office box when I plug one in it throws an Error 43, "Windows has stopped this device because it has reported problems. (Code 43) The SuperSpeed link to the USB device keeps going to an error state SSInactive." I've tried the list of trouble shooting and repair recommendations available on line for this error and have come up empty. I've done things like going into Device Manager and deleting all USB devices. On both machines I'm using the Zadig provided libusb-win32 driver. v 1.4.0.0. While Windows fails to recognize the device when I connect it, my DAC believes it has a good connection and the DSPi console recognizes the device and can perform all its normal operations. The computer is running Win 11 Home, build 26200.8246, Windows Feature Experience Pack 1000.26100.297.0. I am current on OS updates; I apply them automatically. On the Pico I'm running firmware v1.1.3a and console v1.1.3-hotfix. I'm thinking of trying a "therapeutic" Windows reinstall that retains programs and data under the Use Magic protocol.

DSPi creates two different USB devices. Are you sure that you are setting the correct device in Zadig? It should be the input device 2 IIRC. I myself lost a lot of time by not realizing that.

 

[Barrelhouse Solly]

DSPi creates two different USB devices. Are you sure that you are setting the correct device in Zadig? It should be the input device 2 IIRC. I myself lost a lot of time by not realizing that.

Hmm...I did them both.... I'll try undoing zero. I updated the BIOS earlier today with no help resulting.

 

[Weeb Labs]

Hmm...I did them both.... I'll try undoing zero. I updated the BIOS earlier today with no help resulting.

This is quite important. If the interface 0 driver is replaced, Windows will never claim it and the audio device won't be able to start.

Today has been spent bringing DSPi Console for macOS up to date with the Windows version. The output channel routing preview has been implemented, along with the master volume state management. All that remains now is the input channel page.