AAX windows wdl-ol

[bozmillar]

Hey Guys,

I'm curious to know what the status is for AAX 64 in windows. I'm having linker errors saying it can't open 'wininet.lib'. I always assumed that AAX 64 was kind of on the back burner for windows, but I can't figure out why I assumed this.

Does AAX 64 work for anyone else on windows with wdl-ol? If so, what changes do I need to make to get it to compile?

[bozmillar]

ah ha. I think I got it. I had to add $(x64_LIB_PATHS) to my additional libraries for the linker.

[random_id]

Thanks for the fix. Are you using the latest "Next" branch of WDL-OL?

[onqel]

How does AAX respond to IPlug's mutex-addiction compared to RTAS, is it a Pro Tools issue ?
(I know the over-usage of mutex'es in IPlug is an IPlug-issue, but interested anyway..)

[olilarkin]

I've said already i'm not happy with the AAX and RTAS wrappers, which don't seem to work very well on windows with the latest versions of ProTools. They cause audio glitches when altering parameter values. So if you're going to go ahead anyway I'd make sure you test them extremely thoroughly with your beta testers.

[bozmillar]

oh, I see. is it the latest version of protools that causes the issues? I haven't had much of a chance to test the AAX version at all yet, so I'll get back to you tonight after I do.

I've never had glitch issues with RTAS before in protools 10.

[stw]

Sorry for digging this out...
but i was trapped in the same wininet.lib error. After adding the x64 dir (thanks bozmillar) i got a bunch of double defined symbols linker errors. Sort of "defaultlib 'MSVCRT' conflicts with use of other libs; use NODEFAULTLIB:library". After some googleing and changing the aax project setting: Code Generation->Runtime Library to "Multi-threaded (/MT)" everything builds fine (FYI: using VS Express 2015 with Windows7.1SDK platform toolset).

Just in case somebody gets the same errors.

Going to test the performance now...

[Andi!]

Also sorry for warming up this thread again. But to question the remark of stw: Is it really necessary to use an old platform toolset in VS 2015 if you want the plugins to run on Windows 7 ? In my opinion by now the platform toolset is a build toolset and not a runtime toolset - not to mistake with the .NET Framework runtime version.

[random_id]

I never had issues with VS 2015 and 7. The issues I ran into were the few people that were using XP. I didn't delve into a bunch of research about it, but using the v120_xp toolset appeared to work (from VS 2013). I don't have (nor do I want to find) XP to test.