After installing Everett, my PC2ALevelingAmplifier fails to load. Do I reinstall it? or what?
Some of my audio is missing and some that show waveforms aren't playing.
 
So, is my only option rolling back? I'd rather go forward!
 
Thanks
Michael
 ***********edit      I used CCC to install the update, by the way.
 
Reinstalling CA2A took care of it, apparently. The audio that won't play is because of Melodyne Region FX. When I bypass it those clips play. I've started a new thread in Feedback Problem Reporting for that.

Whoops. That's no good. Have not installed Everett yet and use the PC2A extensively. Looking forward to hopefully a good resolution on this not jsut for you but for all our sakes.
 
I have not seen any other reports of this yet so maybe something funky happened with your specific install. Maybe try a rollback then reinstall Everett from scratch? Or maybe a reinstall of the PC2a/Ca2a is in order?
 
Good luck and let us know if (and how) you get it sorted.
 
Cheers.

No joy yet, Beep.
Just further weirdness. I bypassed the PC2A and then clicked it back on and that track played. But after closing the project the same thing happened again, only the 2nd time bypassing and then engaging it did nothing, ie no audio from that track (waveform visible).
 

Gonna ask a few troubleshooting questions... not that I'll be able to help but might give a clearer picture.
 
 Do you own the CA2A or just the PC2A?
 
Is this occurring on all your projects (ones with and without PC2A/CA2A)?
 
If you own both does there seem to be a difference in the problem between projects that use or originally used the PC version (PC2A) of the VST version (CA2A)?
 
Have you tried to open earlier versions of the project (that still incorporate the plugin)? What is the result?
 
If this is only happening on one specific project then obviously the immediate conclusion would be that somehow that project has been corrupted and I'd try reverting to an earlier working version and rebuilding if possible (you can just yank any new recordings/waves out of the audio folder for the project).
 
You could aslo try opening the project in Safe Mode and disabling the PC/CA2A (or any other plugs that may be the issue) to see if that corrects the problem. Then maybe try reinserting them as needed (which would mean having to redo you settings but at least the project might be salvaged). I'd probably do a Save As on the project before fiddling around too much. Might want to do a back up in another location to send to tech support too.
 
Feel free to ignore all that as I am not a tech. I do not want to send you on a wild goose chase but those are just some things I might check out.
 
Cheers.

I'm on Everett and having no issues with the PC2A loading as a VST. I'll check the PC module and see if it's any different.

I own both but the CA2A is not on this (new)desktop, but there are no projects that have that. They all have the PC2A version. Also, it seems to be vocal tracks with Melodyne RE the PC2A., but I'll try to track it down further. My projects are safe regardless, as each is on 2 drives per computer and an external backup drive too. (all Seagates)
 
The other missing audio tracks are acoustic guitars, and I'll check some other projects later today.
Thanks for the suggestions, and that you're not having issues, either.

So the problem tracks have open Region FX/Melodyne active on them? That might be the issue... as in maybe you saved the project with open instances of Melodyne/Region FX.
 
If that is the case... yeah I learned my lesson about keeping wave/transient editing stuff open with Audiosnap back in X2. When you save and close with stuff like that open things can get a little hairy when reopening the project. In fact it does sound similar to what I was experiencing back then. Weird graphics, sluggishness, seems like the project is acting buggy in general and ready to crash?

No, none of that so far, but what do you mean by open, exactly? Do you have to bounce each edited region before closing?
 

I checked the PC module and it's working as expected in Everett. I don't use Melodyne so I can't help with that.

pentimentosound
No, none of that so far, but what do you mean by open, exactly? Do you have to bounce each edited region before closing?
 

Well I don't think that anywhere it says you HAVE to but I certainly would. As I said I am no tech but have had major problems saving/closing then reopening with those types of edits open. I think until you bounce it it will save the settings/edits but of course reference the original, unedited wave. So when you reopen it tries to recalculate all those edits at once and bork out the project
 
That is just a guess at how it works but yes... definitely I would bounce any open Region FX or Audiosnap type stuff before closing. Unfortunately if that IS what is happening you may have already corrupted the project to the point you'll have to revert... unless of course someone knows of a way to get around that.
 
Not sure if region FX edits can be bypassed using Safe Mode. If so then maybe you could do that and only lose you Melodyne Edits.
 
Cheers.