Play 4 AAX for PT 10 & 11

[jryser]

I had some of the more insidious issues and all is well in the beta that I tested. 4.0.16 will be next, and likely soon. Keep glued to the EWQL site.


Sent from my PT beating heart

[musicman691]

Originally Posted by jryser

I had some of the more insidious issues and all is well in the beta that I tested. 4.0.16 will be next, and likely soon. Keep glued to the EWQL site.


Sent from my PT beating heart

So they're skipping a few version numbers then? You just know there are people going to make hash of that

[demodigi]

Originally Posted by jryser

I had some of the more insidious issues and all is well in the beta that I tested.

Same here.

[demodigi]

Play 4.0.18 is up (though I didn't tested it, I'm still using beta 4.0.16 which solved distortion issues)

http://www.soundsonline.com/Support

[musicman691]

Originally Posted by demodigi

Play 4.0.18 is up (though I didn't tested it, I'm still using beta 4.0.16 which solved distortion issues)

http://www.soundsonline.com/Support

Just downloaded and installed. Crashed PT 10.3.7 (spinning beach ball of death and I had to force quit) first time I switched a Kontakt instrument to Play EWQLSO instrument. Second time with the same session, switched the same Kontakt instrument to a Play instrument and everything went fine. Other than that - so far, so good. But then again I never had the problems other people were having with Play 4.0.12.

[zion]

Originally Posted by musicman691

Just downloaded and installed. Crashed PT 10.3.7 (spinning beach ball of death and I had to force quit) first time I switched a Kontakt instrument to Play EWQLSO instrument. Second time with the same session, switched the same Kontakt instrument to a Play instrument and everything went fine. Other than that - so far, so good. But then again I never had the problems other people were having with Play 4.0.12.

How did you switch a kontakt instrument to a play instrument?

[musicman691]

Originally Posted by zion

How did you switch a kontakt instrument to a play instrument?

Easy. Change the Instrument track insert from Kontakt to Play and open the same patch in Play 4. I'm lucky in that I have both the old original Kontakt-engined version of EWQLSO (and Ra) and the new Play versions of the same libraries so I can do things like that.

[demodigi]

Originally Posted by musicman691

Just downloaded and installed. Crashed PT 10.3.7 (spinning beach ball of death and I had to force quit) first time I switched a Kontakt instrument to Play EWQLSO instrument. Second time with the same session, switched the same Kontakt instrument to a Play instrument and everything went fine. Other than that - so far, so good. But then again I never had the problems other people were having with Play 4.0.12.

Hi musicman691,

1/
I don't know if you replaced plug-in when you first use this release (or if you already opened Play4 normally, and then experienced this kind of crash when replacing Kontakt plugin).

Personally, after updating a Virtual Instrument (especially sample-based VIs), I always launch it as standalone* to be sure everything is fine. And then I'm using it as a plugin.

Though, I often experienced some crashes when replacing/moving some plugins in certain conditions (with T-RackS, Spectrasonics, etc). I don't know if it is an AAX bug or 3rd party bug. Most of the time, the bug comes from the replaced plugin (so Kontakt in this case).

2/ I wonder if you had any issue with menus and buttons.
With PT10.3.6 and Play4.0.18** AAX 32bits version, I was unable to get any windows and menu scrolls except the "main" Player window.

If some people experienced this, try to :
- Quit PT
- Launch Play 4 standalone in 32bit mode
(go to [system HDD]/Library/Application Support/East West/ and right-click on "Play.app" clic on "read informations" (cmd+I) and check "open as 32bits mode")
- Use the GUI (open all kind of windows and scroll menus)
- Quit Play (you can reset it to 64 bits mode if you want)
- Launch PT10.3

NB : Normally you just need to do this once and for all : there might be a kind of GUI reinitialization after the update which is not done correctly with the AAX 32bits version.

3/ I noticed a compatibility bug between RTAS and AAX version. When opening a session saved with Play4 AAX versions, Play RTAS version will open empty instances (no instrument loaded)**.

For PT10 and PT11, it is not really important because AAX is both 32bits and 64 bits. Except if you want to send a PT session to a PT9 (or less) user (ie : copy saved as .ptf), he will get empty Play instances.

I don't know if it was already the case with Play4.0.12.

* if this version exists of course.
** this was also the case with 4.0.16

[musicman691]

Originally Posted by demodigi

Hi musicman691,

1/
I don't know if you replaced plug-in when you first use this release (or if you already opened Play4 normally, and then experienced this kind of crash when replacing Kontakt plugin).

Personally, after updating a Virtual Instrument (especially sample-based VIs), I always launch it as standalone* to be sure everything is fine. And then I'm using it as a plugin.

Though, I often experienced some crashes when replacing/moving some plugins in certain conditions (with T-RackS, Spectrasonics, etc). I don't know if it is an AAX bug or 3rd party bug. Most of the time, the bug comes from the replaced plugin (so Kontakt in this case).

2/ I wonder if you had any issue with menus and buttons.
With PT10.3.6 and Play4.0.18** AAX 32bits version, I was unable to get any windows and menu scrolls except the "main" Player window.

If some people experienced this, try to :
- Quit PT
- Launch Play 4 standalone in 32bit mode
(go to [system HDD]/Library/Application Support/East West/ and right-click on "Play.app" clic on "read informations" (cmd+I) and check "open as 32bits mode")
- Use the GUI (open all kind of windows and scroll menus)
- Quit Play (you can reset it to 64 bits mode if you want)
- Launch PT10.3

NB : Normally you just need to do this once and for all : there might be a kind of GUI reinitialization after the update which is not done correctly with the AAX 32bits version.

3/ I noticed a compatibility bug between RTAS and AAX version. When opening a session saved with Play4 AAX versions, Play RTAS version will open empty instances (no instrument loaded)**.

For PT10 and PT11, it is not really important because AAX is both 32bits and 64 bits. Except if you want to send a PT session to a PT9 (or less) user (ie : copy saved as .ptf), he will get empty Play instances.

I don't know if it was already the case with Play4.0.12.

* if this version exists of course.
** this was also the case with 4.0.16

If a plugin has a standalone mode I always try it first that way to see if everything works like it should and then I use it in a PT session. Has always served me well. Actually this crash I mentioned happened the first time I used Play 4.0.12 in a PT session. What I didn't do that I should have done was to trash the PT databases before starting it up and trying Play 4.

No real problems with the menus or buttons - all work as expected. I thought I had a couple of issues with the menu selection accessing the menu with 'stream from disk' with the menu disappearing with 4.0.18 but that turned out to be a dirty trackball sensor.

[demodigi]

Originally Posted by musicman691

If a plugin has a standalone mode I always try it first that way to see if everything works like it should and then I use it in a PT session. Has always served me well. Actually this crash I mentioned happened the first time I used Play 4.0.12 in a PT session. What I didn't do that I should have done was to trash the PT databases before starting it up and trying Play 4.

So we agree. But the little subtle thing here is to open Play4 as standalone in 32 bit mode to properly initiate the plug in for AAX 32 bits to prevent from having potential random issues.

I don't know about trashing databases or preferences in this case, I rarely do it except if I experienced too much troubles. But of course, it often solves many issues too.

Originally Posted by musicman691

No real problems with the menus or buttons - all work as expected. I thought I had a couple of issues with the menu selection accessing the menu with 'stream from disk' with the menu disappearing with 4.0.18 but that turned out to be a dirty trackball sensor.

Ok Thanks.

I asked you this because I was still using PT10.3.6 when I installed both Play4.0.16 (beta) and Play4.0.18, and have this buttons/scroll menu issue (that's also why I tested RTAS version to sort this bug out). No pb with PT11 though.

I also experienced the same kind of bugs (scroll menus/buttons) with Spaces (beta) and PT10.3.6, but the tip I talked in my previous post doesn't work at 100% with Spaces. So, after reading your answer, I updated to PT10.3.7, and from now on, I didn't experience this issue anymore .