license

3 posts / 0 new
Last post
TheiWXS
Offline
Last seen: 3 weeks 4 hours ago
Joined: 11/05/2019 - 3:23pm
license

Hello audio friends!

 

We have been learning and working to get a ST F407 board running for over a week now.

There is a lot to take in for an AUDIO engineer. Not the AWE-designer side off things, we have been working with this type of open platforms (like BSS soundweb) for more then 2 decades: it is the Embedded C stuff that does our head in...

But finally we got it all running and where able to flash a design!

Alas after an hour or so nothing more then beeep...beeep...beeep.. That must be the audio-core license expiring as mentioned in manuals..

Now did we understand wrong?:

<snip> AWE Core ST can be integrated and shipped in products for free <snip>

We can't use it for longer then 1 hour?

 

 

Matt
Offline
Last seen: 5 days 5 hours ago
Joined: 09/19/2016 - 4:27pm

Hi Thei!

Glad you were able to get it working. We'd love to learn where you were struggling - how can we improve our sample-app/docs to better guide future travelers through the dark and mysterious lands of real-time embedded coding?  I presume you were trying to modify the provided sample app in some way?

As for the ST AWE Core - you're understanding is correct! It's free to use it in production systems! Here's the deal: Our public downloads include a 'development' version of the ST AWE Core library, which includes a 1hr timeout.  (Reboot the board to restart the 1hr timer.) To get the full, free, production version of the ST AWE Core library, please contact sales@dspconcepts.com; they'll walk you through a simple licensing process and then deliver the new library (which you can just drop-in, then rebuild your app.)

 

Thanks,

Matt

TheiWXS
Offline
Last seen: 3 weeks 4 hours ago
Joined: 11/05/2019 - 3:23pm

Now that's what you call a quick response!

big cheers!

I do understand that the whole idea off Audioweaver is making life more easy for us sound designers !

Few off us work in the lonely field off live-sound-reinforcement (aka rock 'n roll ;).  No big development teams here, just some fanatics with a bad karma, making gear for the most critical customers: soundengineers

I do recognise that same obsession in your crew: let's make the best sounding audio objects without being restricted by profit maximisation. kudoz!

Now what to do to make things a bit easier for those coming in from my angel?

The problem is not the documentation (a lot!) or the sample apps. It is the whole concept of how Audioweaver works based on the server/client setup..I have been scrolling through the forums and a lot off questions like "where can I find the .bin file"..If you haven't seen any C directory before you just don't now what an IDE is or where those abbreviations like lib or src or inc stand for.

On the other hand, like I said, working with audio objects as biquads, delays, FIRs, AGCs  and how you can connect them in a most interesting way is pretty trivial for us. We have been doing that on platforms that might not be known in the consumer world: BSS soundweb, Mediamatrix, Biamp tesira to name a few.

Maybe a youtube video or a tutorial with this in mind would make a better entry point for us sound engineers.

In fact I was planning to do a blog on my own blogspot (with your consent naturally), but that won't reach that many people.

I also do realise that if we want to take this further we either need to consult some C guru or have to bite the bullit ourselves, something like mentioned in this forum "free up cpu resources used by the asrc for the on board mic" we totally understand, but have not a single clue how to go about...