Actually, I am on sub; just missed that one. Thanks for the link!
On Thu, May 29, 2014 at 8:47 AM, Stephen Blair <[email protected]> wrote: > Assuming you are not subscription... > > As previously posted on this list April 30th, by Jill Ramsay > > http://download.autodesk.com/us/support/report_a_bug.html?SelProduct=Softimage > > > > On Thu, May 29, 2014 at 8:01 AM, Ed Manning <[email protected]> wrote: > >> The real issue is not that it fails to release the movie file (though >> that's an issue too) -- it is somehow asserting control of the actual >> render output stub file, and failing to release *that.* That and the fact >> that the mediaParserServer.exe process keeps running after the abort -- try >> doing an abort of a frame in progress and you'll see a *second* >> MediaFileParserServer.exe process open up. Trying to kill the zombie >> process kills both, and then of course the Softimage instance that's >> running loses its ability to read movie files. >> >> But thanks for logging the bug! >> >> Is there no other way for us to report SI bugs? I could find nothing on >> the Autodesk bug report page that would allow me to do so. >> >> >> On Wed, May 28, 2014 at 10:17 PM, Hsiao Ming Chia < >> [email protected]> wrote: >> >>> MediaFileParserServer was introduced in 2012. >>> It was added as a way to support Quicktime for the 64-bit version of >>> Softimage. >>> >>> I will log an issue with it not releasing the movie file on abort. >>> >>> Thanks, >>> Hsiao Ming >>> >>> From: [email protected] [mailto: >>> [email protected]] On Behalf Of Stephen Blair >>> Sent: Thursday, May 29, 2014 12:30 AM >>> To: [email protected] >>> Subject: Re: MediaFileParserServer.exe not releasing on aborted renders >>> >>> It's a 32-bit app for dealing with Quicktime. I don't see it in the 2011 >>> install folder, but I do in 2012 SP1. >>> >>> C:\Program Files\Autodesk\Softimage 2012 >>> SP1\Application\bin\MediaFileParserServer >>> >>> >>> >>> On Wed, May 28, 2014 at 11:43 AM, Ed Manning <[email protected]<mailto: >>> [email protected]>> wrote: >>> definitely part of XSI, and I'm nearly certain it's new in 2014. >>> >>> On Wed, May 28, 2014 at 3:13 AM, Ales Dlabac <[email protected]<mailto: >>> [email protected]>> wrote: >>> Are you sure it's part of XSI? We are dealing with locked files too(even >>> without using any mov file in scene) but I never noticed that application. >>> >>> On Tue, May 27, 2014 at 3:31 PM, Ed Manning <[email protected]<mailto: >>> [email protected]>> wrote: >>> Hey -- >>> >>> I guess this is the only place to bring up bugs for Soft now?!? >>> >>> Okay, Soft now starts something called MediaFileParserServer.exe >>> whenever any sort of movie file is present in a scene. If you start a >>> render and then abort it, for some reason, even though there's no obvious >>> reason for an executable that deals with input formats to care about output >>> images, you can't delete the stub file that an aborted render often leaves >>> behind; Windows thinks MediaFileParserServer.exe is using that stub file. >>> >>> You can't kill the MediaFileParserServer.exe process without putting >>> Soft in an unstable state, so you have to kill Soft in order to release the >>> lock on the stub file. >>> >>> I don't recall ever seeing this executable in the process viewer -- is >>> it new for 2014? My workaround will be to not use movie files, which will >>> be inconvenient as a lot of image sequence assets from my clients get >>> delivered to me as .mov or .avi. >>> >>> >>> >>> >>> >>> >> >
