After Effects Error No Such Volume
10.0.2 » After Effects error: making file specification – no such volume (-35) 1stMar. × ’10 By Eric Bowman Have you come across this error before in After Effects? After Effects error: making file specification – no such volume (-35) Yeah, it sucks. Well, today was my first time experiencing this error. I was opening an archived After Effects project, and as soon as it started to open I saw the error message. I racked my brain trying to figure out why it was missing media because I was opening the project from a collected files folder. I kept saying to myself,"This is what collected files is for…I shouldn't be missing ANYTHING!". To top it all off, I had to continuously click the button as it tried to open the project because it was missing every single asset. Finally it opened in After Effects and all assets were missing so I relinked everything and saved the project. Fast forward 10 minutes later, AE crashed on me and I had to restart the program only to be welcomed by that annoying error message AGAIN! So I got smart and googled the error message. Well it turns out that the HFS file system on Mac has a 32 character limit on any Volume Name. My external drive was exactly 32 characters. I simply closed After Effects, renamed the external drive by shaving off a few characters of the Volume Name and TADA…Everything was fine! So lesson of the day: Don't make your Volume Names longer than 32 characters! This entry was posted in After Effects, Mac Stuff and tagged After Effects, hfs, mac, no such volume, volume name. Bookmark the permalink. Post a comment or leave a trackback: Trackback URL. « Opening Maya projects from a newer version in older versions. After Effects CS5 Update / 10.0.2 » 8 Comments Jenn Posted May 20, 2010 at 6:57 pm | Permalink Thank you thank yo
Forum -- Avid DS -- Avid Free DV -- Avid iNEWS Developer Forum -- Avid Interplay -- Avid Interplay Central Devel -- Avid Interplay MAM Developer -- Avid ISIS | 2500, 5500 and 7 -- Avid Liquid / Avid Liquid Pr -- Avid Liquid Chrome HD -- Avid Media Composer - Mac -- Avid Media Composer - PC -- Avid Motion Graphics -- Avid NEXIS | PRO -- Avid Open I/O Forum -- Avid Pro Video Events and We -- Avid Product Feature Request -- Avid Symphony -- Avid Unity / Workgroups / Lo -- Avid User Groups -- Avid Worldwide Training Tips -- Avid Xpress DV - http://www.ericsbowman.com/after-effects/after-effects-error-no-such-volume/ Mac -- Avid Xpress DV - PC -- Avid Xpress Pro - Mac -- Avid Xpress Pro - PC -- Avid Xpress Studio - PC -- Broadcast Newsroom -- Chat With Avid -- Community 101 -- Community Issues and Suggest -- Community Test Posts -- Complete Your Suite -- Film and 24p -- Foro en Español -- General Discussion & Off -- Get Started Fast -- Interplay Production Develop -- Licensing Help -- Licensing http://community.avid.com/forums/p/627/2607.aspx Options -- Media Composer First | Commu -- MetaFuze Forum -- Xpress / Media Composer / Sy Blogs Video Exchange Tips and Tutorials Home Blogs Videos Forums User Groups Tips and Tutorials Portfolios Forums » Professional Video Editing & Finishing Forums » Avid Media Composer - Mac » errors rendering out of after effects with avid uncompressed codec Latest post Fri, Oct 21 2005 5:35 PM by zack. 12 replies. Page 1 of 1 (13 items) Sort Posts: Oldest to newest Newest to oldest Previous Next Wed, Oct 19 2005 1:20 AM zack Joined on Tue, Oct 18 2005 los angeles Posts 5 Points 60 errors rendering out of after effects with avid uncompressed codec Reply Contact Hello, not sure if I posted to the right area - I'm trying to render out of After Effects with the Avid Uncompressed codec, but keep getting the error "After Effects error: compressing frame of movie - no such volume (-35). (44$ 39)" I downloaded the latest "Avid Media Codec for Post Products on Mac OSX, Mac OS9, and Win 2000/XP"... read up a little on everything, checked all my settings, and found that it only works 1 out of every 15 tries or so. The "Avid compressed" codec works everytime, it's only the uncompressed that seems to be having tr
6.5 is much improved over 6.0, mainly under OSX the GUI no longer pops open during rendering (although AE still accesses the window manager, the GUI is just 'hidden'). However, some issues with 6.0 still carry to 6.5.. Windows: Problems with http://seriss.com/rush/rush-current/issues-afterfx-6.5/index.html running After Effects on multiple processors under Rush. Only use one entry per comp in the AE Render Queue 'Use storage overflow' and 'Skip existing frames' should be un-checked in the AE Render Settings 'Use Comp Frame Number' should be checked in the Output Module Settings. You can leave the 'Output Path' blank in the Rush Submit-AfterFX form. Make sure your 'Project Settings' has 'Start numbering frames at:' set to zero Steps for submitting a after effects job in Rush Getting AfterEffects rendering on two or more procs under Windows OSX: Window Manager Errors (eg. "INIT_Processeses [sic]") Error messages and their meanings Windows: Prevent more than one aerender from runningon Windows machines. Currently there's a bug in AE (under Windows only) where running more than one AERENDER process per machine under the Rush service either hangs or crashes aerender, causing either or both processes to fail with this 'Application Error' from AfterFX.EXE: after effects error Adobe is trying to fix this in a future release or update. This shows up ONLY on multi-processor /Windows/ machines using After Effects for rendering. You can work around the problem in either of these ways: Reconfigure the Rushd service to run on the desktop using these instructions, then you can use all processors. Limit your After Effects renders to use one processor on each machine (see below) #1 is probably the most desirable for farm machines, since you can get use of all processors for rendering. However, it does mean those machines need to be left logged in at all times with the 'Rushd' running in a stowed DOS window, instead of as a service. To prevent Rush from assigning all processors to an AfterFX render, you can use the 'Ram' value in the submit-afterfx 'Advanced Options' to prevent more than one aerender from running on the machines. To do this, assuming your render farm is configured in Rush to have 2048 of ram on each machine, then submit your job to the farm with the 'Ram' value in the submit form set to 2047. This will prevent rush from starting more than 1 AERENDER process per host, because Rush will think the AfterFX job needs all of that ram to run each AERENDER process, preventing it from starting another AERENDER on the sam