I am creating an exporter plug-in. It works fine when I open Premiere, open a project and choose to export using my plug-in. But when i open a project directly by double clicking the project file (like untitled.prproj), my plug-in always show up a "Error compiling movie" message.
I use log4cxx to help track the plug-in, but no log was created, so my guess is that the plug-in has not even been loaded.
Could anyone tell be the differences between starting Premiere -> open a project and open a project directly by double clicking its .prproj file. In both case, which file is loaded and which file is not?
I'm very appreciated if anyone would have the same problem and tell me how to fix this. I'm really stuck here
The version is CS5.5.
And my steps are:
1. open the project by double clicking the .prproj file
2. select a file in the project
3. Choose File -> Export -> Media
4. Select my plug-in in the drop down list and choose Export
But if take these step:
1. Open Premiere Pro
2. select a project
3. select a file in the project
4. Choose File -> Export -> Media
5. Select my plug-in in the drop down list and choose Export
the plug-in run just fine.
So I think that there are something different between opening a project directly and open Premiere and choose a project. Could you verify this for me? Thanks.
That is pretty strange - there shouldn't be any difference. The "Error compiling movie" message is being shown because your exporter is returning an error from one of the selectors. Have you tried debugging it to see why it is returning an error?
The only thing that comes to mind is that when you double-click on a .prproj file the current working directory will be that directory. If you open Premiere Pro it’ll be that binary directory.
So… if your exporter has some directory dependence that would do it.
Thank you very much for your answer. That's true.
My plug-in loads an ini file to read some parameters. That file is put in the install folder (same folder with the .exe). So when I click on the .prproj file, the current directory would be the project directory, that makes the ini file not to be read and causes errors. I have fixed it now. Thanks again, man.