Trying out the CS6 trial. I REALLY like what i'm seeing so far, as long as I can get past this issue.
I worked on a project, save it, then when I reopen I am given this load error:
/Volumes/Hildebrand 1tb/OverLords/Copy of Overlords Trailer.prproj
Audio Filter missing: 1095781937 DeNoiser1
Audio Filter missing: 1095915057 Reverb1
The audio filters are apparently missing, yet when I get in the project I can easily add the filter back in, but to have to do this and redo my filter parameters each time is not good.
Anyone know what may be causing this?
I'll give that a try here, the report is basically saying what you are seeing. What's interesting is the project is using the mono version (1) of the effects. These are 'internal' VST effects. What type of clips are the audio effects applied to? In particular I'm interested in knowing about the format, is it mono streams? Was the project converted from an FCP (or other) project type? Anything you can mention to help repro the issue would be awesome.
I actually have a new problem now.
Almost everytime I open Premiere CS6 it immediately crashes.
The only thing I did that I have never done before was import this project as an XML from Final Cut.
Here is what Final Cut says about the audio files I am applying the effects to
So right now I can't even open the project without Premiere crashing. I have CS5.5 installed, could that have anything to do with it?
No, having CS5.5 is independent from CS6 - they can coexist on the same computer without interference. Are you scrubbing the timeline where one of the missing audio effects is when the shutdown message happens? I'm curious if they are related. Any chance you can post your project (.prproj, no media) someplace so we can see what's going wrong?
Hopefully this link will work.
This crash seems to be kind of random. It happened once when copying an audio effect from the left channel to the right channel, once when using magic bullet looks, and several times when first starting up, without me actually doing anything.
Thanks! - I have the project and that's really helpful - one thing to try - doing a copy of the effect puts data onto the system clipboard, if you go to say, notepad, and select anything and copy it, then do your test again, do things work again? I'm thinking there might be something residual on the system clipboard.
I closed out Premiere and tried copying and pasting inside notepad, but I got the same notice relaunching the project.
Here is what the effect panel looks like for the clip with the effect applied.
This is a bummer because the DeNoiser works WONDERFULLY. I had pretty good headphones on and was able to get rid of all background noise without any vocal distortion.
Something else I noticed, is that at some point between bringing over the project XML and reopening just now (and between about 5 crashes), the transitional effects on all clips went away. Also, every piece of audio that was linked became unlinked.
I managed to grab a SS when transitions and links were present.
And taken just now.
This is all very confusing because some of it seems to be unpredictable. I didn't delete the transitions, nor unlink the files. I'm gad I have your attention though, hopefully we can sort this out.
Woops, the unlinking/transitions thing is my bad. I had forgotten that I had created a new sequence to try and match the ProRes settings of the clips (the sequence created with the xml used some kind of MPEG instead of quicktime/ProRes). I just copied everything to the new sequence, and apparently transitions and linking don't carry over.
Okay here is an update.
I created a test project from scratch rather than XML from final cut. Added a clip and some audio and applied the audio filters. Saved. Reopened, and everything reloaded properly.
Perhaps the issue here is with the way the xml transferred from final cut? It's the first time I had done anything like that, so maybe I just didn't do it properly (although it seemed pretty straightforward).
Not sure what was causing the crashes, but I haven't see anything else about CS6 crashing as much as it was for me, maybe again this was related to an XML error.
I'm having exactly the same problem with a project in CS6. Never saw this in CS5.5. The program crashed and next time I opened it got the "audio filter missing" message for every audio effect I had applied. When I reapply the audio filter, then save and close, it is once again missing when I reopen the program.
Mac OSX 10.7.4
Mac Pro 3,1
Project files stored on separate drive from program.
Looks like my problem is also related to XML import. I've been using PluralEyes to sync audio with video. The process requires exporting a FCP XML file generated by Premiere to PluralEyes, processing to sync, then importing the resulting XML file. Everything works great except that applying audio filters to any audio file imported as part of the XML process generates the "audio filter missing" message and cannot be successfully rendered.
Audio filters CAN be applied successfully to audio files within the same project, provided the audio files were not imported via XML.
Definitely XML, because when I recreated the project in Premiere without XML everything worked fine. Hopefully they find a fix for this though, as im sure not everyone can afford to recreate their FCP projects in Premiere!!
I just spoke to support today and they are obviously aware of it and still working on it.
I did notice that when you create a sequence to export to XML for pluraleyes that my audio comes in as a stereo track. When I import the new XML back into premiere it appears that pluraleyes has seperated them out to dual mono tracks. Can anyone confirm that this plays a part in the issue?
Any news on this? I have the same problem (applied VST audio fx dissapear after save/re-open). PPro CS 6 (no trial). My audio also went the XML path (PluralEyes), so it's obviously related to XML. Latest updates didn't help.
i got this from singular support (now red giant?) awhile ago, don't know about the Adobe end:
We reproduced the problem here too and are trying to find solutions to workaround the issue. If you are working with dual-system audio, the following workaround works:
1. Sync the sequence with the Replaced Audio sync option
2. In the "Replaced" sequence in Premiere, right-click on a clip with the replaced audio and select Merge Clips...
3. Drag and drop the newly created merged clips from the project panel into the timeline
thanks for the hint, but this workaround won't help me. First of all I already synced and cut the sequence, so I can't go back now. Furthermore I need to keep the audio indepentendtly in my workflow, so "Replace Audio" in PluralEyes wouldn't be a viable option.
So I still have to wait for a fix inside of Premiere Pro...
I am getting the same problem with the dynamics filter, but I built the project in Premiere. Whenever I open the project I get the "missing" error message and I have to reaply the filter - very annoying
Any news on a fix??
Most of the work we do with talking heads requires PluralEyes and XML imports, like David we often need the other audio tracks as well as the sync'd audio. But just wanted to say thanks to all the contribuitors above as this thread was easy to read and pinpointed our problem. However of course we still need that patch update to be able to work effectively. Just a note of interest is I've never seen this error when working from start to final render in one go, i.e. saving the project as it is built but never actually closing and reopening Premiere. It's only on the re-open that the audio filter errors become apparant. Also we're still using the PluralEyes 2 (i.e. the one before the latest version), just incase someone has tried version 3 and no longer finds this error?
I'm using Premiere CS6 and PluralEyes 3 and I can confirm that this issue is still present - I started my workflow in Premiere, importing all media into a timeline, and using the extension to bring the project into PE3. I exported a synced (but not replaced) timeline out of PE3 and brought it into Premiere.
I edited the project and didn't add a dynamics filter until the very end. After a save, close and reopen, the error comes up that the filters are unavailable, and in the effects panel they are offline.
I tried holding shift+starting Premiere mutiple times, including after a restart, audio effect (dynamics) still unavailable.
As per the discussion about the XML issue, I see that when I import the new synced XML into Premiere from PE3, a new folder with the media is placed in the project panel instead of the original media that I placed for step 1. So there are two copies of the same media essentially.
I am now going through the tedious process of replacing the 'synced' media with the original - which is proving extra difficult, because the options "replace with clip from source" and "replace with clip from source; match frame" aren't giving me the right portions of the audio clips.
I even tried to look at the timecode of my synced audio clips, copying that and inputting that TC into the original source audio files, to make the in and out points match, but for some reason that brings the playhead to a segment a few seconds off from the synced clips.
I would have saved more time not using PE3. Rage.
I have experienced this problem several times with Premiere Pro CS6 and PluralEyes 3.0 for Windows.
The problem is simple: when you apply an audio effect to a track that was synced by PluralEyes, Premiere Pro gets confused about whether the track is mono or stereo. Premiere Pro applies the effect properly, but when it saves this effect in its project file, it writes the incorrect filter name.
Then when you restart Premiere Pro, it reads the project file, extracts the incorrect filter name, and complains about the "missing" filter.
The solution is simple: just edit the Premiere Pro project file (which is in XML format) to contain the correct filter name. For example, when I added the Lowpass and Bass effects to a PluralEyes audio track, Premiere Pro wrote these to the project file:
<FilterMatchName>Internal Lowpass Mono</FilterMatchName>
<FilterMatchName>Internal Bass Mono</FilterMatchName>
When I changed those from "Mono" to Stereo with a text editor, then reloaded Premiere Pro, it solved my problem:
<FilterMatchName>Internal Lowpass Stereo</FilterMatchName>
<FilterMatchName>Internal Bass Stereo</FilterMatchName>
The trick, of course, was in discovering the correct names for these effects. To do that, I:
The filter names are not always this predictible; for example, when Premiere Pro wrote "<FilterMatchName>1095782705 EQ1</FilterMatchName>", it really meant "<FilterMatchName>1095782706 EQ2</FilterMatchName>". And when it wrote "<FilterMatchName>1094998321 Dynamics1</FilterMatchName>", it really meant "<FilterMatchName>1094998322 Dynamics2</FilterMatchName>".