Skip navigation
Home/Support/

Forums

2157 Views 14 Replies Latest reply: Sep 25, 2010 6:25 AM by Stan Jones RSS
Webshark2000 User 467 posts since
Mar 5, 2008
Currently Being Moderated

Mar 2, 2010 12:43 PM

Long file name caused Encore to crash during transcoding

I'm not sure if anyone else has experienced this, but I had some video and audio clips that I had to run through a converter and it added to their file names with their encode settings, etc.  When I went to burn the clips to a DVD using Encore CS4, it kept crashing on me when it went to transcode the files.

 

At first I assumed the files were corrupted or had some sort of problem with the way they had been encoded, so I re-exported them out of the conversion software a number of times using different settings.  Each time Encore would crash when it went to transcode them.  I even tried restarting the computer in Windows XP mode (rather than Windows 7 64-bit) where I have Encore CS3 installed and it was crashing as well.

 

Finally, I shortened the file names (just a guess on my part) and they all worked without a problem.

 

Has anyone else experienced this problem?  If Encore had an error message come up to indicate the file name were too long, that would have been helpful.

  • Bill Hunt All-Star 41,401 posts since
    Oct 10, 2002

    I have not seen it with long file names, but have with certain, seldom used characters (at least in file names), and also with spaces. I've taken to using the underscore, instead of spaces, like it used to be. So far, no issues. Now, I usually have rather short file names, so maybe I have just never exceeded some limit.

     

    Good luck, and thank you for reporting,

     

    Hunt

  • John T Smith Star 11,563 posts since
    Oct 26, 2006

    I of course do not have a link, but I do (vaguely) remember this being discussed on the old forum... along with what Hunt mentions about odd characters or spaces in the file names

     

    Since Encore uses Sonic parts for some (most?) of the work... and since Sonic does not communicate well with Encore when there are errors... bad or no error messages are simply a way of life when using Encore

  • Bill Hunt All-Star 41,401 posts since
    Oct 10, 2002

    John T., it was that discussion, between Jbowden, Neil Wikles and Jeff Bellune, IIRC, that led me to always use the underscore, though I had never encountered a problem myself. When those folk list possible problems, I try to listen. That was probably in the old forum and it's now lost and gone forever. Neil was citing several filename incompatibilities based on Sonic Scenarist, and it was postulated that similar issues could exist with the Sonic Authorcore. In that discussion, the underscore solved issues for the OP, and over time, many more dropped by to say thanks, as it had solved their problems too. Great thing about these fora, but brings sadness to me that so very much was lost.

     

    At least I was able to finally read every post (except for the Mac Error Messages sub-forum), so I did get a wonderful overview of Encore and found solutions to so many problems - now, if I could only remember what those solutions were...

     

    Hunt

  • John T Smith Star 11,563 posts since
    Oct 26, 2006

    >now, if I could only remember what those solutions were

     

    I sometimes can't even remember the Question, let alone the Answer!

  • Bill Hunt All-Star 41,401 posts since
    Oct 10, 2002

    John,

     

    I will second that.

     

    Hunt

  • warnergt User 3 posts since
    May 8, 2010

    I was using Encore CS3 on the Mac  and getting continual crashes.  So I bit the bullet and bought Encore  (i.e. Premiere) CS5 hoping that Adobe may have fixed the problem.  With CS5, the  crashes continued -- but at least I had a little more information:  Photoshop File Error -1. 

    That information was enough to  lead me to a forum discussing the long filename problem.

     

    I thought about  the long filename problem and decided to check my filenames and paths to  see what I had -- even though I use a Mac.

    My project folder was  named something like "Something Blitz 2006".  I changed the name to  simply "Blitz06".  You can guess what happened after that.  I was able  to build and write my Blu-ray disc perfectly. That was the ONLY change I  made.

     

    In hindsight, maybe I didn't need to buy Encore  CS5.  I wish I had known about this bug two days and $299 ago.

  • Bill Hunt All-Star 41,401 posts since
    Oct 10, 2002

    Three attributes that seem to get in the way for Paths and Project/Timeline names, seem to be:

     

    Long Paths/file names

    Spaces in these*

    Extended and even some regular, but uncommon ASCII characters

     

    Much of this can probably traced to the Sonic Authorcore, that is the base of Encore (and almost every other authoring program). These observations have come mostly from Neil Wilkes, and is based on his use of the larger Sonic Scenarist.

     

    In hindsight, maybe I didn't need to buy Encore  CS5.  I wish I had known about this bug two days and $299 ago.

     

    If it is any consolation, CS5 has been getting rave reviews, so all should not be lost.

     

    Good luck,

     

    Hunt

     

    * Mac's have had spaces in file names for a very long time, and Windows just a little less. It seems that something in the Sonic Authorcore just does not do well with them. Heck, as I do so much work in Encore, I find myself typing the old _ [Underscore], just like DOS days, even when the file will NEVER be used by Encore.

  • nathapushpa User 38 posts since
    Feb 27, 2010

    Hi Bill

     

    I also have the same problem now...

    I have shorten th paths names and file names to 6characters and as well as no spaces..Eg. Hant1&2

    I am still getting the  Encode Failed message just after Transcoding started on .prproj(video) file.

     

    What else I can try to get it going on Encode on Encore to make the DVD.  I have used ApproCS4 File >> Adobe Dynamic Link to Send to Encore.

     

    Any other advice would b highly welcome !!

     

    Thx

    Pushpa

  • Stan Jones Contributor 3,240 posts since
    Apr 24, 2007

    I recommend you avoid the ampersand; that's one of those odd characters that Hunt mentions.  I do not believe the underscore causes problems, and would use that.

     

    At least one user reported a problem because the name of the project in the build panel had spaces.  (I think that's what is was; I don't think the blank makes the length likely to be an issue.)  so I'd check that too.

     

    I don't recall if you said.  The best practice is to create a brand new Encore project with the newly named assets.  But revising an existing project often works.

  • nathapushpa User 38 posts since
    Feb 27, 2010

    Hi Stan

    Thx 4 ur input to my prob.

    I have removed the & from the file name..now it's Hant12..still does the same "Encode Failed" When start to encode the file.

    All the file paths been changed to Hant12 also...no difference..

    I have saved the file in Encore and started to Build..still the same error.

    What a drama !! Never had this problem before...

    The file size is 2.7GB out of 4.7GB DVD disk. Put a new disk also..still the same..

    What else I can try??

    Thx for giving me tips to  try out...

    Pushpa

  • Stan Jones Contributor 3,240 posts since
    Apr 24, 2007

    There are probably many causes for encoding failures.  I think long names is not a likely one, but one worth fixing, because it has fixed problems.

     

    Are you "building" the project (from the build tab), or just transcoding (from the project bin)?

     

    Is this a dynamically linked asset?

  • nathapushpa User 38 posts since
    Feb 27, 2010

    Hi Stan,

     

    Thx for the update.

    Yes, I am building the project using BUILD Tab and using File >>>Dynamically Link >>> to Encore in Premiere ProCS4.

    This is never happened to me before using CS4...do u think that I have to re-install the CS4 again..

    Whot a tragedy I am facing with !!

    Thx 4 all ur suggestions..

    Reg

    Pushpa

  • Stan Jones Contributor 3,240 posts since
    Apr 24, 2007

    If you have not, I would first transcode the assets before the build.  In the project bin, right click on one of them and pick transcode now.  Are they set to automatic for the setting?

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points