Skip navigation

How do I resave .flv files to .mov?

465 Views 9 Replies Latest reply: Mar 20, 2013 4:19 PM by Jon Walker RSS
PeterBreis0807 Level 7 Level 7 (27,285 points)
Currently Being Moderated
Mar 19, 2013 1:54 PM

I have the latest version of Perian installed on both my Snow Leopard and Mountain Lion start up drives.

 

I can Save .flv to .mov fine in Snow Leopard, but in Mountain Lion the option is Export and after going through the motions it consistently fails.

 

Any recommendations?

 

Peter

iMac, OS X Mountain Lion (10.8.3)
  • Niel Level 10 Level 10 (234,595 points)
    Currently Being Moderated
    Mar 19, 2013 1:56 PM (in response to PeterBreis0807)

    Use the free MPEG Streamclip to perform the conversion.

     

    (79074)

  • Jon Walker Level 6 Level 6 (17,520 points)
    Currently Being Moderated
    Mar 19, 2013 5:05 PM (in response to PeterBreis0807)

    I have the latest version of Perian installed on both my Snow Leopard and Mountain Lion start up drives.

     

    I can Save .flv to .mov fine in Snow Leopard, but in Mountain Lion the option is Export and after going through the motions it consistently fails.

     

    Any recommendations?

    Read the information in the default "Export" window. If it looks something like this:

     

    Screen Shot 2013-03-19 at 7.56.44 PM.png

    (i.e., the export option is offering to save the file data to an "Movie" file container "file that contains media in the same format as the original file") then the data is not being re-compressed. On the other hand, if the window indicates the content is to be recompressed to H.264/AAC content, then the source compressed data is NOT QT compatible without conversions for one reason or another.

     

    SJAUG.png

    iMac, OS X Mountain Lion, 3.4 GHz Quad Core i7, 12GB 1333 MHz
  • Jon Walker Level 6 Level 6 (17,520 points)
    Currently Being Moderated
    Mar 19, 2013 6:21 PM (in response to PeterBreis0807)

    That is what I have done: "file that contains media in the same format as the original file". Goes through the motions of exporting then after a minute or so, reports that it has failed.

    Then it would appear that either

     

    1) the source file is not QT (MOV) file container compatible,

    2) the source content is not supported, or

    3) there is a conflict of com sort preventing the action on your system.

     

     

    As I said I can simply and neatly resave in Snow Leopard to mov. without any transcoding.

    And I had no trouble moving the data from the source FLV file in the screen example above to an MOV file container on my system without re-compressing the data. The function should still work on your system. If it does not, then the problem is either in your system or the file itself. In your place I would possibly retest this using a secondary user account to see if the problem is local or global. In fact, I keep one or two external drive configured as limited system "start-up" drives to run conflict/corruption tests when/if wierd things happening in my main user account on my primary start-up system. Or, if you prefer, you can post or upload a sample file the will not copy on system and I can test it on mine. Also, have you tried moving the FLV content to MOV files using any altenative apps like QT 7 Pro or the free MPEG Streamclip?

     

    SJAUG.png

    iMac, OS X Mountain Lion, 3.4 GHz Quad Core i7, 12GB 1333 MHz
  • Jon Walker Level 6 Level 6 (17,520 points)
    Currently Being Moderated
    Mar 20, 2013 7:20 AM (in response to PeterBreis0807)

    The question remains why does QT7 not appear on right click open on a movie file, and since QT7 works, why doesn't QT Player 10 open and resave the files correctly?

    Probably a current lack of active built-in recognition by QT 7. Native FLV support never exceeded v5. As you pointed out, QT 7 may not automatically open such files on a double-click or even recognized that QT 7 can play the file with Perian support until or unless the user forces/mandates an "Open With..." action for this class of media files. Perian supplies needed current codec support but this support may or may not extend to QT X in all cases and may well be the primary reason Perian is no longer being actively supported. If a file cannot be supported by QT X and you have QT 7 installed on your system, QT X may mecognize its own lack of support and ask the user if her or she whishes to open the file in the QT 7 player.

     

    As to QT X having an inability to properly execute a "Save As..." action and QT 7 Pro can, my guess would be that the source file may contain a proprietary or hybrid form of H.264/X264 compressed data. QT X only supports "standard" MPEG-4/AVC video content while QT 7 with Perian adds support for DivX, Xvid, 3ivX, and/or similar codecs, as well as, files encoded using non-standard Profile/Level crossover settings which QT would natively refuse to process.

     

    If you are satisfied with QT 7 Pro use at this point, I would suggest you simply reset all FLV files to automatically open in the QT 7 media app.

     

    SJAUG.png

    iMac, OS X Mountain Lion, 3.4 GHz Quad Core i7, 12GB 1333 MHz
  • Jon Walker Level 6 Level 6 (17,520 points)
    Currently Being Moderated
    Mar 20, 2013 4:19 PM (in response to PeterBreis0807)

    It is just QT 7 not QT Pro 7, that's what got me, I thought I would need the Pro.

    If QT 7 is working properly, it does require "Pro" use to be keyed. Either your registration key is being recognized contrary to your belief, you have a QT "Pro" app installed like the FCP suite which is activating the "pro" features, or your system is corrupted in such a way that QT 7 has somehow gained access to the "pro" features. If QT 7 was NOT keyed for "Pro" use, this is what you would see when you attempt to use the "Save", "Save As...", or "Export" File menu options:

     

    Screen shot 2013-03-20 at 6.48.50 PM.png

    In short, you would not be able to save the FLV content in an MOV file container.

     

     

    QT X is not recognising its own limitations.

    This is not unusual. QT X is a work still in progress. As such, each upgread seems to add increased ability to recognize and adjust for problems in the current and past releases. For instance, QT X can recognize and play "muxed" MPEG-2/AC3 content in an MPEG, MPG, or TS file container but is not programmed to play the same content in a VOB file container. In a silimar manner, QT X will not recognize/play an AIFF file resourced in an M2V video file but QT 7 still does. There are many such anaomalies in QT X which is why most serious QT users continue to us QT 7 as their primary QT media player and as their primary "quickie" video editing tool.

     

    SJAUG.png

    iMac, OS X Mountain Lion, 3.4 GHz Quad Core i7, 12GB 1333 MHz

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.