Thanks for the heads-up! I'm so used to seeing source on GH that it never occurred to me that binary thingies like PDFs might play differently. Oops.
The 4 FIR setup looks useful indeed...
@nec100,
you can find all at git, like this: freeDSP-aurora/ADDONS/AddOnB/KICAD/Board A at master * freeDSP/freeDSP-aurora * GitHub
You need also KiCad, to view all.
you can find all at git, like this: freeDSP-aurora/ADDONS/AddOnB/KICAD/Board A at master * freeDSP/freeDSP-aurora * GitHub
You need also KiCad, to view all.
@nec100,
maybe you don't know this, but if you own a Aurora DSP from auverdion.de there is also a german speaking forum => klick me soft
You can also make a git clone to your computer and the open the *.pro file with KiCad and then you can see the schematics, board, ... export to all formats. ;-)
maybe you don't know this, but if you own a Aurora DSP from auverdion.de there is also a german speaking forum => klick me soft
You can also make a git clone to your computer and the open the *.pro file with KiCad and then you can see the schematics, board, ... export to all formats. ;-)
Last edited:
What are you guys using for the USB connection? A hard-wired pigtail coming out of the enclosure, i.e. pin header at PCB to male USB Type A (C?) connector? Any specific make/model of cable assembly would be greatly appreciated.
EDIT: Would something like this work? USB 2.0 Hi Speed Panel Mount Cable 5 Pin Motherboard IDC USB Type A 1 ft (U024-001-5P-PM) | Tripp Lite
EDIT: Would something like this work? USB 2.0 Hi Speed Panel Mount Cable 5 Pin Motherboard IDC USB Type A 1 ft (U024-001-5P-PM) | Tripp Lite
Last edited:
Something similar. You need that cable with a B-connector.
Like this one: USB B Female socket Printer Panel Mount to Pitch 2.54mm 5pin Housing PCB Motherboard Cable - China STC Electronic(Hong Kong)
Like this one: USB B Female socket Printer Panel Mount to Pitch 2.54mm 5pin Housing PCB Motherboard Cable - China STC Electronic(Hong Kong)
USB 2.0 B Female Panel Mount To Pitch Dupont 5 Pin Motherboard Printer Cable 1FT | eBay
Cheapest I have been able to find.
Cheapest I have been able to find.
Do you think it would work if I got a male-to-male USB type A cable? I've been burned before with crappy USB cables and I usually have good experiences with Tripp-Lite.
So, I warned Raphael I was working on this: I plan to build a tool to generate the whole plugin (or most of it) from the SigmaStudio export. I have to be disappoint: It's still a long way getting there. This is merely a prototype - but still maybe of some limited utility for some people.
The current iteration can generate the plugin.ini for the 8channel and 4FIR plugins, so if you're adapting one of these, you don't have to manually copy the addresses from SigmaStudio to that file.
This is still fairly limited. If the plugin's structure differs, the whole program will probably explode (or produce garbage). Also, Crossovers (like in the 7.1 plugin) are hard to automatically detect, so that's not supported either (they will show up as a bunch of HP/LP).
The dsp.fw is assembled as well, so you don't need to build sigma2aurora (and hence no QtCreator required). There are no limitations here, I think.
So, the biggest caveat: You still need to write your own dsp.html to actually control the plugin. Or at least adapt the existing file, so you still need to have a pretty good idea how the whole thing works. The whole plan is to eventually do that automatically as well, but it's a really long way...
Because this should be usable for non-programmers, I added a simple GUI and build a single, self-contained Windows Exe-file. I'm afrad the GUI is ugly (1999 says hello). But well, better than nothing I guess. And I think I can improve it, but not tonight (it's 1 am here and I wanted to get the prototype out tonight).
Here is the link: Release v0.1-alpha * archi/aurora-tool * GitHub
Instructions:
1. Download
2. Unpack
3. Run aurora-tool.exe
4. Select the params-File from your SigmaStudio Export
5. Select the folder where to put the aurora plugin
6. Hit the Build button
7. Wonder what to do with dsp.fw and plugin.ini because you don't have the necessary dsp.html webinterface for it ;-)
The whole thing is written in Perl (I was too lazy to do it in C++), but since it's possible to build a self-contained Exe you don't need to have an idea what I mean with "Perl" ;-)
Anyhow, it's late, sleep tight
P.S.: If things are difficult to understand, I am *really* sleepy ;-) But I wanted to get this out because I don't think I can work on it the next few days.
The current iteration can generate the plugin.ini for the 8channel and 4FIR plugins, so if you're adapting one of these, you don't have to manually copy the addresses from SigmaStudio to that file.
This is still fairly limited. If the plugin's structure differs, the whole program will probably explode (or produce garbage). Also, Crossovers (like in the 7.1 plugin) are hard to automatically detect, so that's not supported either (they will show up as a bunch of HP/LP).
The dsp.fw is assembled as well, so you don't need to build sigma2aurora (and hence no QtCreator required). There are no limitations here, I think.
So, the biggest caveat: You still need to write your own dsp.html to actually control the plugin. Or at least adapt the existing file, so you still need to have a pretty good idea how the whole thing works. The whole plan is to eventually do that automatically as well, but it's a really long way...
Because this should be usable for non-programmers, I added a simple GUI and build a single, self-contained Windows Exe-file. I'm afrad the GUI is ugly (1999 says hello). But well, better than nothing I guess. And I think I can improve it, but not tonight (it's 1 am here and I wanted to get the prototype out tonight).
Here is the link: Release v0.1-alpha * archi/aurora-tool * GitHub
Instructions:
1. Download
2. Unpack
3. Run aurora-tool.exe
4. Select the params-File from your SigmaStudio Export
5. Select the folder where to put the aurora plugin
6. Hit the Build button
7. Wonder what to do with dsp.fw and plugin.ini because you don't have the necessary dsp.html webinterface for it ;-)
The whole thing is written in Perl (I was too lazy to do it in C++), but since it's possible to build a self-contained Exe you don't need to have an idea what I mean with "Perl" ;-)
Anyhow, it's late, sleep tight
P.S.: If things are difficult to understand, I am *really* sleepy ;-) But I wanted to get this out because I don't think I can work on it the next few days.
Last edited:
Ah, I can't edit anymore. I patched it to use the systems native file picker, feels much better now. The latest release can be found here: Releases * archi/aurora-tool * GitHub (in about 15 minutes, 0.1.1-alpha will have the better file picker).
Thanks so much for the contribution! I've already been using it on my end and it's definitely much faster!
Where is the doc for controlling ADC/DAC sample rates? And can they be different from the DSP sample rate?
I have a tool for generating minimum phase FIRs from their linear phase counterparts, and I'm somewhat curious about whether the lack of pre-ringing might be audible if I sample analog at 192 kHz, down-convert to 48 kHz, then resample back up to 192 before hitting the DACs.
I have a tool for generating minimum phase FIRs from their linear phase counterparts, and I'm somewhat curious about whether the lack of pre-ringing might be audible if I sample analog at 192 kHz, down-convert to 48 kHz, then resample back up to 192 before hitting the DACs.
I’ve discovered an interesting behavior of Aurora that appears to be related to WiFi operation. As soon as the access point is opened on Aurora the ESP32 starts drawing HUGE current spikes every 100ms (> 500mA at minimum). This 10Hz pulse frequency is creating a lot of low frequency harmonics that are severely limiting the output noise levels.
Below is a probing of the current consumption of Aurora showing the offending spikes. Note that this is with an additional 1,400 uF of bulk capacitance added, so the effects of the current spikes are actually rater muted.
Looking at D/A/D Loopback performance in REW, the noise apparent, and lowering the signal-to-noise (S/N) performance of Aurora from the expected loopback performance of 112dB S/N to only 83dB S/N (was even worse before adding the bulk capacitance).
Interestingly, this primarily seems to be affecting the DAC, rather than the ADC. As feeding the ADC stage with a muted signal generator produces 108dB S/N, much closer to the targeted 112dB.
I’ve not been able to diagnose this issue much further than looking at the serial monitor and narrowing it down to the ESP32 radios, as it appears immediately after “AP Open.” The pulsing then continues for the entire duration of operation.
Below is a probing of the current consumption of Aurora showing the offending spikes. Note that this is with an additional 1,400 uF of bulk capacitance added, so the effects of the current spikes are actually rater muted.
Looking at D/A/D Loopback performance in REW, the noise apparent, and lowering the signal-to-noise (S/N) performance of Aurora from the expected loopback performance of 112dB S/N to only 83dB S/N (was even worse before adding the bulk capacitance).
Interestingly, this primarily seems to be affecting the DAC, rather than the ADC. As feeding the ADC stage with a muted signal generator produces 108dB S/N, much closer to the targeted 112dB.
I’ve not been able to diagnose this issue much further than looking at the serial monitor and narrowing it down to the ESP32 radios, as it appears immediately after “AP Open.” The pulsing then continues for the entire duration of operation.
