Few questions about the ADA1701 SigmaDSP

Hello,

Here is my take based on my experience, in the same numbered sequence:

1. Yes, it is a very realistic goal and SigmaDSP is THE perfect platform

2. I would try to use the GPIOs as much as possible (Too bad AD, the IR algorithm is still not added). However, for an external interface, you would need to create your own GUI

3. AD does not recommend/allow giving SigmaStudio to end users. So without it, basically you can use anything that can, at the processor end, talk I2C or SPI

4. For 2 x analog in and 6 x analog out there already is ADAV4601. For other, I find it cost effective and real-estate effective to use ADAU1701/2 a SMART 2 x In, 4 x Out CODEC that could interface to something like ADAU1442 or ADAU1452 for more processing power. The latter chips also have a built-in SPDIF decoder and an encoder

5. Confirmed! It can be done!! Just don't get too greedy to add more and more features/ delay or you could run out of resources.

Oh! and for your other thing....try this link: http://www.analog.com/en/dsp-software/ss_sigst_02/sw.html>;

I hope that this helps.

1: Certainly a great chip for this solution, with some caveats later about memory/feature creep

2: The chip can be completely controlled "real time" via i2c or SPI. Those busses aren't generally available on a PC in a meaningful way, so if you want to use USB or RS232, you will need to put some chip in there to translate. Analog Devices use a Cyprus USB-i2c/SPI bus converter chip, in our own products, we use an Atmel or Freescale microcontroller with a USB interface. This allows us to do things like store a copy of the current settings in a more friendly manner on the target device so that you can plug the computer in, and it will pull the settings the DSP is currently using to populate the GUI so you can continue where you left off.

3: You will want to make your own GUI for your application. Sigma Studio would be a nightmare to support for most end user applications. Even if it were allowed by the EULA. We have done our GUI in C#, however, your choice of language for the GUI is pretty unlimited, as long as you can talk to the driver for your communications method.

4: Our OEM solution is 6in/6out with the ADAU1701 which, is probably about the limit for features vs channels for our market. To get this, we use 2 external ADC's and an external stereo DAC. This gives us 4, 12dB crossovers, 6 bands of eq, 5mS of delay, volume, phase, and a noisegate,limiter or compressor on each output channel. With a 2/4 or 6ch input, and a small mixer for 2 channels to sum inputs 1-4 into 5 and 6. If a full 6x6 mixer was needed, that would use more memory/mips which would have to be taken from those features. Going to 8x8 we would have to use a more capable chip. Your ADC/DAC combination may limit your options for sampling speed. Because of the clock options for our selected ADC, we can not use the 96kHz mode of the DSP. Which is ok, as we need the mips anyhow, but do pay attention to that if you need all of the clocking options, or go for a bigger chip with the sample rate converter.

5: Well, I think my answer to #4 answered that. I don't know what quantities you are looking for, but if they are high enough, there are some OEM bare board solutions out there you can just grab and use to implement your design with.

Richard

Hello KKSL and Richard

Wow great answers thank you

Response to KKSL

Message understood about using SigmaStudio for End Users that wasnt the plan it was just more the idea of

being able to use elements of the code streams to patch into your own GUI. Or at least if you cant patch anything

get an idea of how its done

I see so the I2C and SPI input is the control so effectively once this USB/RS232 bridge is created its just a case

of sending the relevant strings to control the DSP. Of course this will require a fair bit of fiddling around but hopefully

not too much.

"For 2 x analog in and 6 x analog out there already is ADAV4601. For other, I find it cost effective and real-estate effective

to use ADAU1701/2 a SMART 2 x In, 4 x Out CODEC that could interface to something like ADAU1442 or ADAU1452 for

more processing power. The latter chips also have a built-in SPDIF decoder and an encoder"

nice I didnt see that one. The AD info about "which device is suitable for me" is pretty USELESS I did look but was none

the wiser after seeing that list. not sure why that one is specifically a TV processor?? however it looks ideal.

So are the ADAU1442 and ADAU1452 generally used for ofloading type tasks as I see on those no ADCs/DACs. but OMG

a mountain of channels on the ADAU1452. I would assume at that number we are in the realms of digital mixers etc but

I would assume in most cases you would use other chips to port all those channels of audio in?

"Confirmed! It can be done!! Just don't get too greedy to add more and more features/ delay or you could run out of resources"

Duly noted i have a yamaha synth in my studio that often hits this threshold and its not nice puts a serious dampner on the

whole plus of using a DSP. I see you mention delay is this generally more gruesome in terms of gobbling resource than other

functions?

"I hope that this helps."

It really does thanks for taking the time out answering this

Response to Richard

"Certainly a great chip for this solution, with some caveats later about memory/feature creep"

Second person mentioned resource issues mmm in my experiences of life so far if something is mentioned to you multiple times by

more than one person open your eyes or ignore at your peril

"The chip can be completely controlled "real time" via i2c or SPI. Those busses aren't generally available on a PC in a meaningful

way, so if you want to use USB or RS232, you will need to put some chip in there to translate. Analog Devices use a Cyprus

USB-i2c/SPI bus converter chip, in our own products, we use an Atmel or Freescale microcontroller with a USB interface.

This allows us to do things like store a copy of the current settings in a more friendly manner on the target device so that you can

plug the computer in, and it will pull the settings the DSP is currently using to populate the GUI so you can continue where you left off.

How did you find development of the code to communicate to the i2C/SPI input once you had the convertor USB232>i2C SPI built?

Was this straight forward or a lot of head banging? So im guessing the command routines for this would be identical to effectively

a button push sequence with hardware switches right? if so I would assume relatively simple. However, with all these kind of things i

chose the word "assume" with care.

"You will want to make your own GUI for your application. Sigma Studio would be a nightmare to support for most end user applications.

Even if it were allowed by the EULA. We have done our GUI in C#, however, your choice of language for the GUI is pretty unlimited, as

long as you can talk to the driver for your communications method."

Yes message understood about sigmastudio sorry i wasnt clear in my question. The reason for the question about source code was more

to get a feel for how the communication strings are made not so much to rob code from Sigma or replicate it in any way. On the basis this

controller would be used in pro audio the custom interface would be essential. I am a big fan of really easy to understand code and hardware

so a customized GUI would be a number 1 priority.

"Our OEM solution is 6in/6out with the ADAU1701 which, is probably about the limit for features vs channels for our market. To get this,

we use 2 external ADC's and an external stereo DAC. This gives us 4, 12dB crossovers, 6 bands of eq, 5mS of delay, volume, phase, and a

noisegate,limiter or compressor on each output channel. With a 2/4 or 6ch input, and a small mixer for 2 channels to sum inputs 1-4 into 5

and 6. If a full 6x6 mixer was needed, that would use more memory/mips which would have to be taken from those features. Going to 8x8 we

would have to use a more capable chip. Your ADC/DAC combination may limit your options for sampling speed. Because of the clock options

for our selected ADC, we can not use the 96kHz mode of the DSP. Which is ok, as we need the mips anyhow, but do pay attention to that if

you need all of the clocking options, or go for a bigger chip with the sample rate converter.

I would definitely be more interested to know more about this product of yours I will send you a PM to discuss

I am clocking the words "OEM Solution"

"Well, I think my answer to #4 answered that. I don't know what quantities you are looking for, but if they are high enough, there are some

OEM bare board solutions out there you can just grab and use to implement your design with."

I will send you a message about this.

Thanks for all the info Richard and KKSL