KVR Audio

BDeep · Post by **BDeep** » Fri Mar 28, 2014 9:39 am

This is interesting, I found that the VST version (the 32 bit one in the 10.6 folder on Dropbox) also works in Live 64 bit. However, this does nog apply to the AU version.

martin_l · Post by **martin_l** » Fri Mar 28, 2014 10:00 am

BDeep wrote:This is interesting, I found that the VST version (the 32 bit one in the 10.6 folder on Dropbox) also works in Live 64 bit. However, this does nog apply to the AU version.

Did you pick up the files before I sent the post about he wrong compilation of the VST's? In this case, you would still have picked up a fat binary (i.e. 32/64 in one).

Otherwise, it is possible that the host automatically bridges. I don't know about Live, but reaper does that.

Martin

BDeep · Post by **BDeep** » Fri Mar 28, 2014 10:11 am

I thought I did. But to verify I just downloaded the file again and it doesn't work in Live 64 bit now. Must have been an error on my behalf.

lionscub68 · Post by **lionscub68** » Fri Mar 28, 2014 11:43 am

I believe Live automatically bridges or rather bufers automatically; Running Live 32-bit, hosting 32-bit plugins in a 64-bit OS, so I assume it's not the plguins that are bridged, but the audio output that's buffered. Or am I talking through my butt here?

Martin, unless you really feel the need to cater to the Mac PPC crowd... folks running Macs 2005/6 and older; you can drop the fat binary. Mac has been Intel-only since 2006/7, and the OS has been using Universal Binary (more or less) since then. The Universal Binary portion has been ignored for the last two years, OSX 10.8/10.9 runs only the x86 portion of the code. To best future-proof (in computer terms) the plugins, you can drop the fat binary part. (At least that's how I understand it).

martin_l · Post by **martin_l** » Fri Mar 28, 2014 12:26 pm

lionscub68 wrote:Martin, unless you really feel the need to cater to the Mac PPC crowd... folks running Macs 2005/6 and older; you can drop the fat binary. Mac has been Intel-only since 2006/7, and the OS has been using Universal Binary (more or less) since then. The Universal Binary portion has been ignored for the last two years, OSX 10.8/10.9 runs only the x86 portion of the code. To best future-proof (in computer terms) the plugins, you can drop the fat binary part. (At least that's how I understand it).

Maybe I was using the wrong terminology here. When I was talking about 'fat' binaries, I did not have PPC in mind. Simply the combination of 32bit and 64bit in one binary.

To be honest, I am still a bit puzzled about the settings in Xcode. There is the main target, which can be 32bit or 64 bit, and there is the switch in the architecture settings which can be either 32bit, 64bit or 32/64bit (standard). The latter is what I thought to be 'fat' binary.

Please, if anybody could enlighten me more on that...

Cheers,
Martin

lionscub68 · Post by **lionscub68** » Fri Mar 28, 2014 12:29 pm

Time to fire off a support email to Apple's bright boys.

martin_l · Post by **martin_l** » Sat Mar 29, 2014 4:20 pm

OK. New trial... I found some information on problems for the Mac on the wdl-ol forum, and tried to apply the patches to the compiler before building it.

The new builds are again combined 23/64 bit plugins, and are in the Mac-SDK10.6/Mac-32-64 folder.

I also included some smoothing of the parameters. Please, give these ones a try.

Thanks,
Martin

lionscub68 · Post by **lionscub68** » Sat Mar 29, 2014 4:29 pm

Checking it out now.
P.S. Martin - need to repost link to dropbox folder per update, otherwise I (we) have to go fishing back through the string to find the link

lionscub68 · Post by **lionscub68** » Sat Mar 29, 2014 4:37 pm

martin_l wrote:OK. New trial... I found some information on problems for the Mac on the wdl-ol forum, and tried to apply the patches to the compiler before building it.

The new builds are again combined 23/64 bit plugins, and are in the Mac-SDK10.6/Mac-32-64 folder.

I also included some smoothing of the parameters. Please, give these ones a try.

Thanks,
Martin

Reporting back:
No dice, neither VST nor the AU show in Live 9.1.1 (32-bit) on OSX 10.9.2.
The VSTs show in my audio editor VST list but neither work (same message as I had before, see my screenshot a few pages back), and the Au does not list there either.

Sorry for the bad news. (Now I gotta backtrack and find the ones that worked)

Spitfire31 · Post by **Spitfire31** » Sat Mar 29, 2014 4:52 pm

Some good news for a change: the 32 bit VST and AU both work in a 32 bit environment (Tracktion 5.2.4 32 bit and Audio Plugin Player) in 10.9.2.

I couldn't get them to work in 10.8.4, but I'll try again later.

The Mac 32/64 bit AU plugs likewise work in 64 bit environments (Garage Band and Tracktion 5.2.4 64 bit) in 10.9.2. Good work!

However, they don't work in 32 bit environments in the same Mavericks System. Again, I'll test later in 10.8.4.

Kind regards,

Joachim

lionscub68 · Post by **lionscub68** » Sat Mar 29, 2014 5:36 pm

Just a question about the combined 32-64 plugins:
Are they written/compiled like this, intermixed:

If 32 then, if 64 then (process A)
next
If 32 then, if 64 then (process B)
etc

or this (two distinct blocks of 'clean' code):
If 32 then (big block of 32 code only)
if 64 then (big block of 64 code only)
etc

If it's the former then one 'endif' brings the whole house of cards crashing down.
Hope the logic train helps a little here.

martin_l · Post by **martin_l** » Sat Mar 29, 2014 6:51 pm

lionscub68 wrote:Just a question about the combined 32-64 plugins:
Are they written/compiled like this, intermixed:

If 32 then, if 64 then (process A)
next
If 32 then, if 64 then (process B)
etc

or this (two distinct blocks of 'clean' code):
If 32 then (big block of 32 code only)
if 64 then (big block of 64 code only)
etc

If it's the former then one 'endif' brings the whole house of cards crashing down.
Hope the logic train helps a little here.

I am nt sure, to be honest. This fact is happening behind the scenes. In my code, there is nothing which is specific for 32bit or 64bit. As far as I understand, the binaries contain the complete code for both, and when the library is loaded, the correct block is chosen. But I might be wrong here.

Martin

lionscub68 · Post by **lionscub68** » Sat Mar 29, 2014 6:58 pm

So suffice it to say the Mac translation/compiler is to blame.

Maybe contact the TAL developer to see what he's using to compile all his OS verisons.

AdmiralQuality · Post by **AdmiralQuality** » Sat Mar 29, 2014 8:11 pm

martin_l wrote:
lionscub68 wrote:Just a question about the combined 32-64 plugins:
Are they written/compiled like this, intermixed:

If 32 then, if 64 then (process A)
next
If 32 then, if 64 then (process B)
etc

or this (two distinct blocks of 'clean' code):
If 32 then (big block of 32 code only)
if 64 then (big block of 64 code only)
etc

If it's the former then one 'endif' brings the whole house of cards crashing down.
Hope the logic train helps a little here.
I am nt sure, to be honest. This fact is happening behind the scenes. In my code, there is nothing which is specific for 32bit or 64bit. As far as I understand, the binaries contain the complete code for both, and when the library is loaded, the correct block is chosen. But I might be wrong here.

Martin

Ignore this, it's ridiculous. The code is the code, it's the compiler settings that determine whether it becomes 32 or 64 bit. (You might want to post in the Dev board. There's all kinds of wacky misinformation out here.)

lionscub68 · Post by **lionscub68** » Sat Mar 29, 2014 8:15 pm

I'm not a programmer beyond simple data processing at work.
Don't think it hurts to help in this community with these simple thoughts, even if my ideas are full of crap.
Just want Martin to clear this frustrating hurdle.

PG8X (inspired by the JX8P): new beta version uploaded