BJZ

bitman
This isn't going to be the best because you have to know your plug settings used, but maybe load the offending old project in safe mode without permitting slate plugs from loading the same it as songname-noslate.cwp Then load that song in normal mode and reinsert FG if possible?

I will give that a try.

That did not work. Same issue.

Noel Borthwick [Cakewalk]
This would likely be a 3rd party issue rather than a CbB problem. Have you contacted the vendor to report it?

Why only some CbB projects and not others? If it were a vendor problem it would seem it would have to do it on all 
projects an all DAWs right?
 
I have zero problems in most CbB created projects, zero problems in all Splat (or earlier) created projects and I have zero problems in ALL other DAWS (Reaper, MIxbus, Studio One & Samplitude). 

BJZ

Hidden_Symmetry
This might be related to the iLok cloud feature.

But would that not affect *all* projects?

FWIW my DAW is online 24/7 and AFIK I'm not using the iLok cloud. I authorize all my iLok software to my iLok2.

Can't discuss it but as Noel said contact Slate keeping in mind FG-X & iLok cloud.

When running safe mode tests did you step through each plug-in
1) allowing them to load one at a time
2) allowing only slate plug-ins to load
3) allowing only slate fg-x to load
 
Prior to CbB 2018-09 CbB projects use the same project file version as the last Platinum. Do the project open OK in Platinum?

bapu
...If it were a vendor problem it would seem it would have to do it on all projects an all DAWs right?

 
Not necessarily.
 
DAWs don't know anything about plugin authorization. They just load the DLL and call its initialization routine. After that, it's all up to the plugin to do whatever it does inside that black box to set up shop. The DAW should literally be incapable of interfering with that process.
 
Which is not to say that external factors can't ever be involved, e.g. network issues, a failing disk drive, corrupt files, flaky RAM, VC runtime version mismatches, or intrusive anti-virus software. But those things do tend to affect every project and DAW.
 
The error message is probably misleading. It says the service isn't running, but I doubt the plugin actually checks for that. What it really means is that when the plugin attempted to call the service it got a failure code back. Since Pace isn't going to talk about what happens in that call, it'll be an unsolvable mystery without the involvement of Slate, who have paid for the right to get Pace to talk.
 
Has FG-X been updated since you created those problem projects? Could there be more than one instance of it on your system? 

There shouldn't be any difference between opening projects in earlier revisions of Cakewalk by BandLab or from SONAR. CbB won't have any control over the iLok drivers or any other plugin authorization. Individual plugin auth will get thrown when the plugins themselves are loaded, either from a VST scan or when the project loads, but how that behaves is independent from CbB itself.

Hidden_Symmetry

BJZ

Hidden_Symmetry
This might be related to the iLok cloud feature.

But would that not affect *all* projects?

FWIW my DAW is online 24/7 and AFIK I'm not using the iLok cloud. I authorize all my iLok software to my iLok2.

Can't discuss it but as Noel said contact Slate keeping in mind FG-X & iLok cloud.

Oh i so want to interpret the 'cant discuss' to mean FG-X v2 is in work.

bitflipper

bapu
...If it were a vendor problem it would seem it would have to do it on all projects an all DAWs right?

 
Not necessarily.
 
DAWs don't know anything about plugin authorization. They just load the DLL and call its initialization routine. After that, it's all up to the plugin to do whatever it does inside that black box to set up shop. The DAW should literally be incapable of interfering with that process.
 
Which is not to say that external factors can't ever be involved, e.g. network issues, a failing disk drive, corrupt files, flaky RAM, VC runtime version mismatches, or intrusive anti-virus software. But those things do tend to affect every project and DAW.
 
The error message is probably misleading. It says the service isn't running, but I doubt the plugin actually checks for that. What it really means is that when the plugin attempted to call the service it got a failure code back. Since Pace isn't going to talk about what happens in that call, it'll be an unsolvable mystery without the involvement of Slate, who have paid for the right to get Pace to talk.
 
Has FG-X been updated since you created those problem projects? Could there be more than one instance of it on your system? 

The answer to both final questions is no and no.

scook
When running safe mode tests did you step through each plug-in
1) allowing them to load one at a time
2) allowing only slate plug-ins to load
3) allowing only slate fg-x to load
 
Prior to CbB 2018-09 CbB projects use the same project file version as the last Platinum. Do the project open OK in Platinum?

WRT 1, yes. WRT 2 & 3, i will try those. I will try SPlat but Jon seems to indicate that should not make a difference.

FYI i have submitted a ticket to Slate.