Plugins turn white

[bayswater]

I saw the post on Tapatalk which doesn't have a sig but regardless of the sig, I read what he posted, which states the OS & DP version.

Sorry all. I should have read more closely.

[synergy543]

I just found a more recent update (V1.36) for the Lexicon PCM Native plugin which I installed as that was the one that seemed to have the most trouble.

For a few minutes so far it seems to be behaving so maybe that solved the problem although there was no mention of this in the update history.

Keeping my fingers crossed....maybe this solved it?

NOPE That didn't do the trick. The problem continues....

Seems like it really only the Lexicon PCM Native that the problem. Eventide Plugin works fine.

[MIDI Life Crisis]

I saw the post on Tapatalk which doesn't have a sig but regardless of the sig, I read what he posted, which states the OS & DP version.

Sorry all. I should have read more closely.

You probably caught that from me!

[bayswater]

You probably caught that from me!

That would explain the sneezing.

But this problem is bugging me. It used to happen all the time in Cubase, especially with UAD, and was usually tracked down to graphics issue -- something like an unsupported resolution, a carbon/cocoa thing. Wish I could find or remember an instance.

[David Polich]

I just found a more recent update (V1.36) for the Lexicon PCM Native plugin which I installed as that was the one that seemed to have the most trouble.

For a few minutes so far it seems to be behaving so maybe that solved the problem although there was no mention of this in the update history.

Keeping my fingers crossed....maybe this solved it?

NOPE That didn't do the trick. The problem continues....

Seems like it really only the Lexicon PCM Native that the problem. Eventide Plugin works fine.

Sounds like you need to remove the Lex PCM Native software entirely from
your system and re-install it. That would include going to the Package Receipts folder on your Mac HD and deleting the Lexicon package, as well as
the plug-ins in all formats and any application support files for the Lexicon.

If that doesn't work, then you might try installing DP 8 (if you haven't already) and see if the problem persists in DP 8. I'll give you an example -
Melodyne 2.1 steals the transport in DP 7.24, but does not do this in DP 8.
Your Lexicon PCM Native might just work perfectly in DP 8.

[synergy543]

Do you have the very latest version of the Lexicon PCM Native software?

Yes, I believe so. Just this morning I downloaded and installed Lexicon PCM Native Reverb bundle V1.3.6

It seems to be a re-draw problem as it happens after I move to another app, or cover up the Lexicon plugin window inside of DP and then try to open it up. As long as I stay in DP and keep the Lexicon plugin window open, it seems to be OK. The real problem is that after the plugin window turns white, I can't make any more adjustments to the settings. And unless I recall which preset I was using, I have to start all over from scratch to make any changes.

I have seen the problem occur with other plugins such as PSP Zenon, although right now, that one seems to be behaving. I'm only having trouble with Lexicon PCM Native right now.

I submitted a ticket to Lexicon but haven't received and e-mail or a ticket receipt so I'm wondering if my ticket actually went through. I sure wish Michael Carnes was still at Lexicon as he was so responsive over on gearslutz.

[synergy543]

Sounds like you need to remove the Lex PCM Native software entirely from
your system and re-install it. That would include going to the Package Receipts folder on your Mac HD and deleting the Lexicon package, as well as
the plug-ins in all formats and any application support files for the Lexicon.

Yes, I suppose that's the next step. I was trying to avoid this for the time being as I'm also currently evaluating the Lexicon PCM Native Effect on its 14-day trial. So I don't want to disrupt that one. See the dilemma?

It does feel a bit lonely as it seems I am the only one with this trouble. Although I have yet to hear from someone one using the same setup who says its all working well.

And as far as DP 8 goes, I have so many 32-bit plugins I don't wish to part with yet (they are like family) so I've been putting off moving to DP8 and a complete 64-bit system. I run VE Pro and use that for my 64-bit plugins. Which reminds me, I can test Lexicon PCM native plugins in that environment too. I'll see what happens. I also have Logic which a loath to fire up.

And if all else fails, I could always migrate to Cubase.
(quickly ducks and runs for cover)

[synergy543]

Hmmm.....this seems to be a Digital Performer specific issue. I have the Lexicon PCM Native reverb running in Vienna VE Pro 4 (64-bit) successfully without its screen turning white. Yet in DP, with the same Lexicon plugin, the problem occurs. I really would prefer to use it inside DP though.

Again, is anyone successfully running the Lexicon PCM Native reverbs in DP 7.2.4 without this problem occuring?

[MIDI Life Crisis]

I now recall there were similar problems in MachFive - 2.

[Kubi]

Haven't had this problem, and I'm running the current version of PCM in DP7.24. I'm on OS 10.7.5, though.

[synergy543]

Thanks Kubi. Good to know its working on another system. That means there's light at the end of the tunnel in terms of finding a possible solution.

[Radiogal]

Had this problem with Sonalksis plugins on my former Mac G5. I wrote to them and Sonalksis fixed it in the next update.

[magicd]

One other thing to check. If the plug-in is on an audio track, the audio track must have a working output. If the plug is on an aux track, it must have a working input and output. If not, the plug is not active and many third party plugs will show an empty window or no window at all. Check your track I/O assignments.

Dave

[Gravity Jim]

One other thing to check. If the plug-in is on an audio track, the audio track must have a working output. If the plug is on an aux track, it must have a working input and output. If not, the plug is not active and many third party plugs will show an empty window or no window at all. Check your track I/O assignments.

Dave

Magic beat me to it. I just noticed yesterday that if I deactivated a track to save CPU, the UI panels for plug-ins on that track went white.