AAXVersion.h missing, build failed

[Morphoice]

@d-healey the SDK itself seems to build error free, when using the 2.7.0 SDK instead of 2.8 then again the plugin build fails with

ld: library 'AAXLibrary_libcpp' not found

so probably it wasn't built correctly or needs to be copied somewheren.

then again plugins need signing by avid anyways and wont run otherwise, so it's a pass on AAX

[d.healey]

@Morphoice If you ever feel like using Rhapsody you get all this for free.

[DanH]

@Morphoice get an avid account.

[Morphoice]

@DanH I do have one, that's how I got the SDK

[DanH]

@Morphoice sorry I meant Pace, so you can do the signing

[Lindon]

@DanH said in AAXVersion.h missing, build failed:

@Morphoice sorry I meant Pace, so you can do the signing

yeah but that wont stop him compiling it, or shouldnt

[DanH]

@Lindon I was responding to his post about needing to sign aax plugins and therefore passing on aax altogether

then again plugins need signing by avid anyways and wont run otherwise, so it's a pass on AAX

[HISEnberg]

@DanH @Morphoice @Lindon Apologies to hijack this thread in advance, is it a huge pain to acquire and start compiling for AAX? I have been looking into it lately and wondering what your experiences are with it?

[Dan Korneff]

I don't remember it being too hard to setup. I'll boot up a virtual machine and run through the process to see if I hit any issues and post the results here.

[Lindon]

@HISEnberg said in AAXVersion.h missing, build failed:

@DanH @Morphoice @Lindon Apologies to hijack this thread in advance, is it a huge pain to acquire and start compiling for AAX? I have been looking into it lately and wondering what your experiences are with it?

Well the actual download and compile of the AAX library is pretty simple, but to get there and beyond.....

Its pretty easy to become a member of the Avid developer sect(whatever its actually called i cant remember)..

which gives you access to the Avid AAX lib. Once downloaded you next have to build the Avid plugin library... for your platform (following the Avid instructions closely..), once that's done you can build an AAX plugin - but it s not going to run in a commercial release of proTools so now you have to do the signing...

..so its a couple of weeks of back and forth with PACE to get access to the tool kit to do the signing with...

Once you have the signing stuff next you need to get access to the Avid/Pace web site to allow you to generate the required keys... again an admin pain really...

Once you have access its a royal pain of reading thru the endless cryptic instructions from Avid/pace about where on the web site you need to go, what you need to fill in etc. to generate keys.... and frankly I can never remember from instance to instance what Im supposed to do. I promised myself that next time i work thru this I will write it down in some simple instructions for myself...

once you have the keys and the signing tool kit its the usual "codesigning-like" process you are used to in Apple...

So is it worth it? cant say I think that it is...

[DanH]

@Lindon I concur, its a colossal b*allache... I think once your plugin is 100% finished and you have your VST3 and AU etc out of the way, then consider doing aax. Defintely not before.

[HISEnberg]

@Lindon Fantastic reply, I thought there would be some labyrinth of hoops to jump through here so thanks for taking the time to let me know! It isn't clearly stated anywhere (as far as I have seen) that this would be the procedure.

[Morphoice]

@Lindon good to hear from you all about this, exactly my initial experience, good to know I can save myself the effort for a free plugin, although my 2 pro-tools friends are crying for me to make it AAX. they can get a vst wrapper ;))))