[FFmpeg-devel] FFMPEG fails to convert .mov - "Cannot allocate temp picture"

Baptiste Coudurier baptiste.coudurier
Wed Dec 24 13:59:57 CET 2008

fcassia wrote:
> On Wed, Dec 24, 2008 at 8:15 AM, Baptiste Coudurier 
> <baptiste.coudurier at gmail.com> wrote:
>> fcassia wrote:
>>> On Wed, Dec 24, 2008 at 7:50 AM, Baptiste Coudurier 
>>> <baptiste.coudurier at gmail.com> wrote:
>>>> Hi,
>>>> fcassia wrote:
>>>>> On Tue, Dec 23, 2008 at 4:53 PM, fcassia <fcassia at gmail.com> 
>>>>> wrote:
>>>>>> Here is the problem file (it was a .mp4 recorded with the 
>>>>>> Neuros OSD Linux based PVR, and then opened and edited with
>>>>>>  Quicktime Pro for Windows version 7.5.5, then saves as 
>>>>>> .mov).
>>>>>> http://the13thfloor.org/4friends/tigani-mide2.mov
>>>>>> No matter what I try or the target format I choose, it 
>>>>>> always fails with the same error:
>>>>>> [...]
>>>>>> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x177a110]stream 0, error 
>>>>>> opening file //tigani-mide. mov: Invalid argument
>>>> Your file is a reference file pointing to external file, 
>>>> however an error occurs when opening external file. You should 
>>>> check the path and access to '//tigani-mide.mov'.
>>> Thanks for the pointer!. I knew something was odd, just wasn't 
>>> sure what. This is due to Qucktime PRO offering two choices when 
>>> saving files... either a "flattened" (wtf?) file (an individual 
>>> video) or a "pointer" (a file references a fragment of another).
>>> The question is... perhaps this is an opportunity to add a 
>>> warning or error message to FFMPEG when it encounters such .MOV 
>>> files?
>> Well, an error message is already printed if the file reference 
>> cannot be opened, the one I quoted.
> Yes, but it is mixed in the middle of a stream of errors.

Yes, some other problems are also present, all error messages are
printed when encoutered.

> I think it should just stop there and inform the user in more
> human-friendly terms that the file the user is attempting to convert
> has missing/unreadable parts.

Absolutely not, video track could not work while audio track could, so
there is no reason to stop there, and even when both tracks could not be 
opened, .mov could contain metadata interesting for the user, and 
furthermore, technically, the .mov file is valid and can be opened.

About the message, I think it is quite clear:
"[mov,mp4,m4a,3gp,3g2,mj2 @ 0x177a110]stream 0, error opening file 
//tigani-mide.mov: Invalid argument"

I believe you should just pay more attention to what is written.

Baptiste COUDURIER                              GnuPG Key Id: 0x5C1ABAAA
Key fingerprint                 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA
checking for life_signs in -lkenny... no
FFmpeg maintainer                                  http://www.ffmpeg.org

More information about the ffmpeg-devel mailing list