Batch Process cannot continue

Report · Jul 11, 2017

I use Batch Process often because I work off an external hard drive and need all my session files to be in designated project folders. Occasionally I get this message - “Batch process cannot continue because one or more selected files have a location or filename which is too long. Try again after adjusting your export settings”. I have looked around but find nothing obvious that would allow me to change said export settings. Something it telling me that it's a Window issue, but any tips or clarification would be most appreciated.

Joey DiFazio

Report · Jul 11, 2017

Can you tell us the folder path and names of the files that are causing problems? And are you adding Prefixes or Postfixes to the Batch Process file names?

Report · Jul 12, 2017

Folder path always points back to the main session folder on my hard drive. For example > Sports Imaging Manager\01 Sports Imaging Manager\03) MP2 & misc\Desktop 7-10-16\Big 7 - NASCAR Brickyard 400.

I tried pointing back to the Imported Files folder, cause I noticed that’s where Adobe puts files when it does the batch automatically, but didn’t make a difference. I did notice that when I do accept the automatic export (“some files are located outside of the session - “click yes”) it exports fine.

I think it might be what SuiteSpot is describing, since the music bed files are usually the culprit. Their naming conventions are very long (FC_MH153_11_More_Gasoline_Vocal_Version_Herweijer_Sumner_Rossi_951882)

When I have the foresight to shorten the file names of the music, I never have a problem exporting. But it’s one more thing to worry about and I often forget to do it

Report · Jul 11, 2017

Chances are that this is a windows thing.

Windows has a finite limit to the length of paths and while Windows may let you copy something to a path that is beyond its limit it won't let you access it.

"In the Windows API (with some exceptions discussed in the following paragraphs), the maximum length for a path is MAX_PATH, which is defined as 260 characters. A local path is structured in the following order: drive letter, colon, backslash, name components separated by backslashes, and a terminating null character."

Edit:

"The 260-character path length limit in Windows can be removed with the help of a new policy, thus allowing you to run operations with files regardless of their path or file name. While this new rule is not enabled by default, admins can turn it on by following these instructions. Launch the Registry Editor by clicking the Start menu and typing "regedit.exe," and then navigate to the following path: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy Objects\{48981759-12F2-42A6-A048-028B3973495F}Machine\System\CurrentControlSet\Policies. Look for an entry called "LongPathsEnabled," and if it does not exist, simply right-click Policies, select New DWORD (32-bit), name it "LongPathsEnabled" (without the quotes), enter value 1, and you're good to go. The description of the preview reads, "Enabling NTFS long paths will allow manifested win32 applications and Windows Store applications to access paths beyond the normal 260 char limit per node. Enabling this setting will cause the long paths to be accessible within the process."

Report · Jul 12, 2017

Thanks – I have a note in to IT. When they get back to me I will refer to this. ‘preciate it!

-jd