SigmaStudio development
Is SigmaStudio still in active development with future releases planned? I've noticed a bunch of planned features over the last few years' worth of questions that haven't been implemented yet, but 4.6 is getting on for nearly 10 months now, and the beta version is for a lower release.
Hello,
SigmaStudio is still actively supported and ADI does have another SigmaStudio release planned.
Note that SigmaStudio 4.5.1 Beta release was an interim release between SigmaStudio 4.5 and SigmaStudio 4.6.
4.5.1 Beta included many bug fixes and improvements, but this particular release did not go through ADI's automotive release process; resulting in the "Consumer" categorization.
SigmaStudio 4.6 includes all the fixes from 4.5.1 Beta and more, and went through the automotive release process.
For the planned features you mentioned that haven't been implemented, are there any specific bugs or features that are critical for your application? We may be able to suggest a workaround.
Best regards,
Joshua
Hi there,
Well I know the option to make my own modules is probably not coming any time (though that will remain my number one wish on the wishlist), but a dual time-constant module (attack and decay) would be useful, as would a dedicated Antilog - also the frequency-domain analysis / fourier transform stuff being enabled for the ADAU1467 would be helpful.
Also a better way of viewing the numbers at any point - the 10hz refresh is better than nothing but isn't actually that useful when you're trying to tune sensitivities and can't see the result of every trigger because it doesn't fall on a measurement beat.
Hello David,
You can implement a dual slope time constant for decay easily with the external sidechain inputs on the compressors. The attack can be done the same way. You just have to set the internal compressor settings up out of the way so they do not kick in. This would be a good example project for me to work on. I will put it on my ToDo list that is getting long...
Regarding the refresh rate. This all boils down to exactly what you are looking at and details of your system. I have setup an extra DAC channel as a scope monitor and sent data out to the DAC and looked at it on a scope. That is one possible solution. You can implement a switch in the DSP to be able to select to "view" signals from any number of places in your signal flow. You also can just take over one of your outputs for this development use.
Then you can program the DSP to keep up with minimum and maximum values and counters to give you feedback on what is happening on a sample to sample basis. I have done this with error counters where readback cells will miss the quick one or two sample error but the counter will count them. So you can do a lot with these approaches.
Dave T
Please log in to reply.