Just upgraded to DP 9.1.
First I noticed that any VST plugin, the window was all white. I'd hear the plugin, but couldn't access the controls as the window was blank white. Got the VST turned off now.
Seemed like the AUS plugins were fine except now I'm seeing every now and then, those window got white as well. Sometimes the window will come back when I click on it.
Plugins window turns white.
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
Plugins window turns white.
MacPro5,1 6-Core Intel Xeon, Processor Speed: 3.46 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Memory: 32 GB. Mojave. DP 9 and Apogee Duet.
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Memory: 32 GB. Mojave. DP 9 and Apogee Duet.
- mikehalloran
- Posts: 16192
- Joined: Sun Jan 25, 2009 5:08 pm
- Primary DAW OS: MacOS
- Location: Sillie Con Valley
Re: Plugins window turns white.
Are you using older VSTs?
If they do not support Cocoa graphics, they will not be visible in DP 8/9 64bit but you will hear them. The MDA freebies come to mind.
If they do not support Cocoa graphics, they will not be visible in DP 8/9 64bit but you will hear them. The MDA freebies come to mind.
DP 11.34; 828mkII FW, micro lite, M4, MTP/AV USB Firmware 2.0.1
2023 Mac Studio M2 8TB, 192GB RAM, OS Sequoia 15.4, USB4 8TB externals, Neumann MT48, M-Audio AIR 192|14, Mackie ProFxv3, Zoom F3 & UAC 232 32bit float recorder & interface; 2012 MBPs (x2) Catalina, Mojave
IK-NI-Izotope-PSP-Garritan-Antares, LogicPro X, Finale 27.4, Dorico 5, Notion 6, Overture 5, TwistedWave, DSP-Q 5, SmartScore64 NE Pro, Toast 20 Pro
2023 Mac Studio M2 8TB, 192GB RAM, OS Sequoia 15.4, USB4 8TB externals, Neumann MT48, M-Audio AIR 192|14, Mackie ProFxv3, Zoom F3 & UAC 232 32bit float recorder & interface; 2012 MBPs (x2) Catalina, Mojave
IK-NI-Izotope-PSP-Garritan-Antares, LogicPro X, Finale 27.4, Dorico 5, Notion 6, Overture 5, TwistedWave, DSP-Q 5, SmartScore64 NE Pro, Toast 20 Pro
Re: Plugins window turns white.
They probably are older.
But I noticed I had AU versions of the same VSTs so I disabled the VST ones.
That was okay except every now and then the AU ones are appearing as blank white windows.
With those, though, if I click on them the graphics come back.
So far it's not a major problem. Just wondering what's up with that.
Thanks.
But I noticed I had AU versions of the same VSTs so I disabled the VST ones.
That was okay except every now and then the AU ones are appearing as blank white windows.
With those, though, if I click on them the graphics come back.
So far it's not a major problem. Just wondering what's up with that.
Thanks.
MacPro5,1 6-Core Intel Xeon, Processor Speed: 3.46 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Memory: 32 GB. Mojave. DP 9 and Apogee Duet.
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Memory: 32 GB. Mojave. DP 9 and Apogee Duet.
Re: Plugins window turns white.
This may be related - I had an issue the other day with parts of the Kontakt 5 gui missing (I happened to be calling up the Rick Bass library at the time to get my Lemmy on). Parts of the library gui were missing and just to check I opened K5 in standalone with the Rick Bass library and it was fine; also okay in ProTools. Go back to DP9.01 and I start looking through the tracks for anything strange. What had happened was that my 2-bus output had changed from the legitimate output it had been assigned to to something that doesn't exist (I didn't make that change) and once I changed it to where it was supposed to be the entire gui came back no problem.
I'd check track routings throughout the whole project and see if a re-assignment didn't happen all by itself.
I'd check track routings throughout the whole project and see if a re-assignment didn't happen all by itself.