Photoshop File Error -1 ??????

[Stan Jones]

This error has nothing to do with PS version.

If at build, it is most often file names/paths too long or with problem characters (semicolon; ampersand by some reports spaces – go figure). While length alone just needs to be 80 or under, there are reports of fixes that reduced smaller names.

Stan Jones

[Ted Irving]

Has to be something else. My original files are just Contact.psd and Main.psd. All resaved. Restared Encore and still only this error when trying to build a Flash version. Error doesn’t occur when building DVD folders or Disc Images.

Ted Irving
ENG Cinematographer
http://www.tedtv.tv
tedirving@tedtv.tv

[Ted Irving]

Figured it out but still odd. I have music playing for each menu. They are mp3 files. If I remove the mp3 files then the flash build proceeds without error. I’ve placed music before. Weird. Thanks

Ted Irving
ENG Cinematographer
http://www.tedtv.tv
tedirving@tedtv.tv

[Stan Jones]

The files at issue are not the .psd files; they are the asset/timeline or other files.

mp3 files may have metadata or other info that can cause problems. Some may work; some not. But they are not a good idea for menu audio.

Can you confirm that the mp3 names were short and without special characters? I want to be more confident that it was the mp3 files themselves. I’ll try to test whether some mp3’s work and other don’t.

Edit: Also, I missed that this was a flash build. Did you get the same error for a DVD/BD build if attempted?

Stan Jones

[Ted Irving]

the mp3 had an underscore in the title. i removed it and uploaded the new version with a shorter name. still gave the error. i took them out completely and got a clean build. and yes, builds for folders and images worked fine regardless of music or file length names. this was just a flash build error. so what about using .wav files?

Ted Irving
ENG Cinematographer
http://www.tedtv.tv
tedirving@tedtv.tv

[Daniel Ludwig]

MP3 is no good idea as file-format for DVD/BD-autoring.

use AC-3-files or WAV/AIFF-files, but no compressed mp3.

[Frances Hill]

Hello,

I am also getting this error message in Encore 5.5

I am importing the video through the dynamic link from adobe premiere 5.5 and this seems to fine.

As soon as I choose a template menu and go to edit it, I get the Photoshop File Error -1 message and I get frozen out. The issue appears to be when creating the menu.

I am able to build and burn a DVD but only if I leave the template as it – with the exception of allowing me to delete some of the buttons.

The software was working fine until I updated to Maverick – which is what I am thinking the problem is. I am worried I am going to have to wipe my mac and reinstall mountain lion.

Can anyone help – as usual, big deadline and very stressed!

My thanks in advance.

[Stan Jones]

See this:

https://forums.creativecow.net/readpost/145/873115

Stan Jones

[Frances Hill]

Many thanks for your help and quick response Stan.

Unfortunately, after exhausting the suggestions in your link and some other ideas I found, I had no other option than to completely wipe this pesky operating system from my computer using internet recovery in order to revert to mountain lion.

I spent ages looking for ways around this and in the end, this was the only thing that worked. It was an option from the beginning and after all the time spent trying to troubleshoot the issues and then doing the recovery and reinstalling everything – I would urge people reading this as a way of solving this incompatibility issue to just downgrade from OS X Mavericks and take the hit if they want Encore working properly again.

[chris brown]

I ran into the same issue. I am building blue ray 50gb disk. I have one main motion menu and 30 motion submenus. I tried 2 things one of which fixed the issue. I initially tried to change the main motion asset to a different asset in the project and then Encore froze up. After closing out and re-opening, I then deleted the submenu that had that asset I tried to use for the main menu, and I also cleared some space on my C drive. After doing both, the issue resolved. Given that there were 31 different menu assets, I think it unlikely that I just happened to pick the correct one that had the issue, more likely it was a hard drive space issue, but who knows??