Page 1 of 1
Posted: Thu May 30, 2002 8:15 pm
by casevanrij
Im interested in using the CW Pulsar as a replacement for the audioscience cards we're using in our audioservers. These cards have 8 analog inputs and hardware mp3 encoders, but are horribly expensive ($3000+ for 4 stereo in)
How realistic would it be to port an mp3 codec (like lame, or iso reference C) to the sharc dsp ? Would the 6 sharc dsps on the pulsar be fast enough to do realtime encoding of 4 or 6 stereo signals to 24-112kbps mp3 ?
And finally, if I were to port lame to the sharc using the analog devices sdk (free 30 day trial!) would I be able to load this code into the pulsar's dsps ?
Thanks.
Posted: Fri May 31, 2002 4:14 am
by kimgr
Besides the Analog Devices SDK, you'll also need Scope/DP AND Scope SDK.
But I think that Creamware would be VERY interrested in having mp3 enconding on the platform...
Kim.
Posted: Fri May 31, 2002 11:37 pm
by jupiter8
I have mailed Creamware about the possibility to use C++ code in Scope DP but i have'nt recieved any answer.
Personally i doubt it, but who knows.
Posted: Sat Jun 01, 2002 2:08 am
by kimgr
No doubt... You can with the Scope SDK.
But to create Sharc-DSP code in C++, you need the VisualDSP++ software from Analog Devices.
Kim.
Posted: Sat Jun 01, 2002 7:06 am
by jupiter8
So you can do that.
That is really excellent.
How do you "import" the C++ code into the Scope?
Then one should be able to more or less easily compile VSTi:s to the Scope platform.
This is an area that i think could greatly benefit our beloved platform.
Posted: Sun Jun 02, 2002 8:05 am
by kimgr
How do you "import" the C++ code into the Scope?
You simply "drag" the file into your device.
Then one should be able to more or less easily compile VSTi:s to the Scope platform.
This is an area that i think could greatly benefit our beloved platform.
Erhh, no. VSTi's are running on Intel & Motorola CPU's, Scope uses Sharc DSP's, so you'll have to rewrite most of the code. (AFAIK).
Kim.
Posted: Sun Jun 02, 2002 10:54 am
by jupiter8
The beauty of C++ is that it is platform independent.
To a degree.
VSTi code is except for the GUI completly platform independent.
You just compile it for a different processor.
I know there would be some work to do, perhaps a lot but most of the code is already written.
Maybe it is even possible to make a generic wrapper for VSTi:s. That is if you have the source code of course.