#18 Too picky about filename extensions for a Mac app
First off, it's great to see so much progress on both the player
and the GUI ! Good work guys! But...
I couldn't understand why some of my files were not being
accepted by the MPlayer OSX utility (v. 1.0) that shipped with
mplayer .9b5 I couldn't drag and drop some movie files onto
the GUI or Icon...
It tuned out that it was because the movie filename extension
was ".mpeg" instead of ".mpg" !!!
ALSO, i have several movies with no extensions or made up
ones (like .iv50, .mplayer, .i263 etc). These are not accepted
by the Mplayer OSX gui at all unless i change the extensions.
* It would be VERY nice to have the _option_ to turn off this
filename bulletproofing and allow any file to be dropped onto
the icon/GUI. This preference is commonly found on other
drag-n-drop utilities.
FIX #1 ----------------------------
Otherwise, the immediate fix is easy. In the Info.plist file, add
the following line:
<string>mpeg</string>
after the line
<string>mpg</string>
I believe that the mpg/mpeg contention is pretty isolated (like
jpg/jpeg). If there are any other common 4 letter extensions,
they can easily be added. Perhaps "mpg4" and "oggv" might
be wise?
FIX #2 ----------------------------
The option to turn off filename bullet proofing (effectively
setting CFBundleTypeExtensions to "*" would still be
appreciated. It only needs to be a checkbox in the
preference pane.
FIX #3 ------------------------------
Also, the finder knows that all these files with made up
extensions are indeed movie files. It would be nice if
Mplayer OS X honored the Finder's file type codes.
Apparently you need to add a section to the Info.plist AND
implement something in the code.
I sat down and gathered the file types for the supported file
extensions. It's a start for you:
<key>CFBundleTypeOSTypes</key>
<array>
<string>MPEG</string>
<string>VfW </string>
<string>ASF_</string>
<string>MooV</string>
<string>FLI </string>
<string>VCD </string>
<string>PNRM</string>
<string>mpg4</string>
<string>oggv</string>
<string>OGGV</string>
<string>Oggv</string>
<string>OggV</string>
</array>
This goes right after or before the CFBundleTypeExtensions
array.
If file type mapping was enabled, all my movie files would be
playable no matter what i name them. But remember that in
OS X, some files actualy do not have a file type (This was
illegal in OS 9)
All in all, this is just adding the gravy, I think the application,
overall, works very well these days. Thanks for all the hard
work!
~p@
Logged In: YES
user_id=657081
This is the only way the GUI app distinguish between audio,
video and subtitles files, so I can't remove the extension
filter. I can simply add support for any extension and then
it depends on mplayer. Problem is that there is no standard
in extensions. The extension should describe the media
container instead of codec used to compress the video
content and in this case the extensions like .iv50, .i263
are not valid for describing the media container.