Apple TV - h264 MP4 AAC.

I recently purchased an Apple TV and am now taking the opportunity to convert all my videos to mp4, just so I can have a universal format across the board.
I have been using ffmpegX to convert them. For video I pick the mp4 codec (the H264 [.MP4] (mencoder) one). I set the video size to be the same as the source (and this also dictates which frame rate is chosen) - just click on best which normally uses something very close to the source frame rate. (There's probably not a lot of point in changing the frame rate and aspect ratios, since the information isn't there to begin with, so it's not going to look any better (ie: for most files are going from xvid to h264). I suppose that also depends on the aspect ratio and whatever TV you have, but whatever...). For the audio codec I use AAC (MOV/MP4/3GP) at 192kbit/s.
At the end of the day I want all my videos to be the same frame rate and aspect ratio, but in h264 video format and aac video format.
It's all working fine. The thing is, it's going to take about 2 months I reckon, to do all my videos on my mac; so I'd like to speed the process up a bit by using my Gentoo box.
Can someone give me a command I can use which will do all the above options? I've spent hours looking at threads citing ffmpeg, transcode, mediafork and handbrake as solutions for iPod and DVD conversion... but no one seems to have a good answer for high quality mp4 h264/aac encoding which can be used for the Apple TV (and will of course also look good on the computer).
Obviously, by the command above, I'm using mencoder to do this, and am getting good results, so lets stick with that shall we?
MacBook Pro 15.4" - Intel Core Duo 2.0   Mac OS X (10.4.9)   1GB RAM

I can't give you any help using mencoder, I don't use the application. However it is an application with a basket full of options, so I have to assume you are reasonably familiar with encoding digital video. However I noted couple of things in your post that I thought I'd mention.
For the audio codec I use AAC (MOV/MP4/3GP) at 192kbit/s.
I'm assuming you mean audio only files and not the audio track of a video since 192 kbps is to high a bitrate for video files and won't play on the tv.
At the end of the day I want all my videos to be the same frame rate.
This isn't a good idea. I'm not sure where you are from, is that Townsville in Oz, if so your likely to have a mix of 25 and 30 fps videos and maybe some 24 fps ones, despite mencoder apparently having good filters for changing framerate, I doubt the change will be unnoticeable.
Mencoder seems to have a number of filters which if used properly will help produce better quality video, even so bitrate and the number of passes the encoding process takes should still be your major settings when it comes to quality.

Similar Messages

  • H264 MP4 rendered in Premiere CC isn't playable on iPad1

    For some reason iPad1s cannot play videos that I render in Premiere CC as H264 MP4 (960x540 at 29.97fps).  I've tried both Main and Baseline profiles.  I had read somewhere that iPad1s can only play baseline H264.... but it seems not even them.
    What other settings can I change that would enable playablility on iPad1s?
    Any help would be greatly appreciated.

    Here are Apple's specs for the iPad1:
    H.264 video up to 720p, 30 frames per second, Main Profile level 3.1 with AAC-LC audio up to 160 Kbps per channel, 48kHz, stereo audio in .m4v, .mp4, and .mov file formats; MPEG-4 video, up to 2.5 Mbps, 640 by 480 pixels, 30 frames per second, Simple Profile with AAC-LC audio up to 160 Kbps, 48kHz, stereo audio in .m4v, .mp4, and .mov file formats; Motion JPEG (M-JPEG) up to 35 Mbps, 1280 by 720 pixels, 30 frames per second, audio in ulaw, PCM stereo audio in .avi file format
    Make sure both your video and audio meet those specs.
    Cheers,
    Jeff

  • Data below black level 0 in h264 mp4 files.

    I'm a little confused about black and white levels in video.
    I have two questions. If you bare with me for a second I can demonstrate what I mean.
    I created gradient with values from 0,0,0 to 255,255,255 in Photoshop and saved it as sRGB jpg file.
    I imported the file to Premiere and added Fast Color Corrector to the file and changed black input level from 0,0 to 16,0
    So now everything below value 16 is cutted to black.
    I exported the edited gradient as h264 mp4 videofile.
    Now things got interesting.
    I imported the edited videofile back to Premiere, added Fast Color Corrector to videofile and changed black output level from 0,0 to 16,0
    The information that I thought was lost is there!
    I tried to to the same thing for the same video file with Photoshop and I'm not able to get the lost information back.
    Why is there information below 0? And how am I able to rescue it with Premiere, but not with Photoshop?
    Does this have something to do with YCbCr black and white levels that are 16-235?
    This whole question came up when I calibrated my Samsung lcd-tv. I used AVS HD 709 mp4-calibration videos.
    There are black level calibration videofile. Which is exactly like my gradient video file where there are black values below 0.
    If you lift your tv's brightness below certain levels you are able to see the black values that are below 0.
    I'm able to see these "blacker than black" values with tv's own videoplayer and with xbox videoplayer.
    However, if I try to see these values with my macbook pro  which is connected to tv I can't get them visible.
    It doesn't matter if I play the video with quicktime, vlc or premiere.
    So the second question is why the macbook pro does not send any "below black" information to tv?
    PS. I'm using latest premiere CC.
    Thank you in advance!
       In this image you can see from Premiere Scopes what is happening.

    Does this have something to do with YCbCr black and white levels that are 16-235?
    No and yes.
    When you manipulate levels values within 0-255 (0.0-1.0) range, you don't clip existing data, you simply compress/decompress contrast, while information is still there (to some extent). By the way, data outside 16-235 range, but inside 0-255 are not super-blacks or super-whites (underdarks or ovebrights), they are just broadcast safe values. Super-blacks or underdarks are values below 0.0, while super-whites or overbrights are values above 1.0. The nature of YCbCr does allow to store some real super-blacks and super-whites even while encoding to 8-bit codec.
    Why only some codecs are able to preserve this "illegal" values?
    MOV container is... um-m-m... quirky. For example, exactly the same data encoded to e.g. mp4 and MOV with exactly the same codec (e.g. H.264), may be decoded/interpretted differently. So as to have some fun, create a copy of an mp4 clip, which contains some super-whites, rename file extension of one copy to MOV, import both mp4 and fake MOV footages into After Effects, set your project to 32-bit, sRGB or Rec.709 and linearise working space in order to get precise result while blending layers. Then drop both clips into the same composition and set blending mode to Difference. Enjoy!
    Why I'm only able to access these values inside Premiere and not with Photoshop. Is Photoshop unable to access these illegal below 0 values?
    Try setting Photoshop to 32-bit first. If that doesn't help, then yes, Photoshop clips values outside 0-255 (0.0-1.0) range on importing. Similarly you won't be able to get super-whites or super-blacks back in PrPro with 8-bit effects.
    When i export with codecs that can preserve superblacks should I still get rid of them with videolimiter. Do they cause any problems in youtube or broadcast environments?
    No. Moreover, you should take care of broadcast legal range in case of delivering to a broadcaster only, YouTube 'broadcasts' on the web and targets regular computer monitors, which operate on sRGB 0-255 range.
    why the macbook pro does not send any "below black" information to tv?
    That has probably something to do with Apple colour management workflow. Since I'm not on a Mac, I can't comment this on

  • Big Color Shift between exported H264 mp4 and Program Monitor

    I get a big Color Shift between exported H264 mp4 on Vimeo/Youtube and Quicktime X and Program Monitor.
    There are quite a few posts on Quicktime gamma issues, but there seem to be no solutions and the other editors I know don't seem to have this problem.
    I know there will be a bit of a shift but this is MASSIVE. At the moment I add a whole extra adjustment layer to all my clips to get it approximately right, but ofcourse this does not solve the issue nor does it give proper results.
    Please do not reply with the "You need a real reference monitor via SDI etc etc ..."
    By my logic on the same screen the program monitor should resemble what is going to be the final result in a relevant player like Quicktime X which all normal apple consumers use to watch their films.  I know VLC and Mpeg streamclip gives different results, but mostly when playing Quicktime/h264 files Quicktime will play it thus average users ( the people I'd like to downwload/buy my films )will watch it in Quicktime.
    Furthermore, Quicktime X's gamma/color looks very similar to the image I get on Youtube or Vimeo - which is where all my current work is going. I'm not outputting to boradcast or DVD etc.
    Strangely enough the MPEG 2 stuff I've done for DVD matches the Youtube output with the Program monitor.
    What am I doing wrong?
    I have a Dell 2711 wide Gamut Display which is calibrated with an SPyder 3 Elite using its full colour gamut ( close to 90% of Adobe RGB - thus bigger than sRGB or Rec709) Could Premiere be ignoring the calibration in the Program monitor and making the image values 16-235 and then Quicktime uses all  values 0-255? If so, how can I fix this?
    Any help will be much appreciated!

    I know this has been a while so hopefully you found some help by now, but maybe this will help anyone stumbling across this.
    What people seem to be missing in what you are asking is... this is the same file, on the same monitor, but with a different appearance in different software.  It is not a question of whether the overall monitoring is GOOD, and it is not a matter of hardware settings (as that would most likely propogate across all software) it is that it is not CONSISTENT side by side on the very same monitor.
    I had very similar issues that really seemed to get worse when we got new monitors, which is what lead me to chime in here.  The monitors were also wide gamut displays.
    The problem is likely this...
    1. The difference being shown are the difference between software that properly color manages (i.e. Premier or After Effects) and software that does not (i.e. Quicktime or some web browsers)
    2. The reason it is so severe is that the wide gamut monitors are able to show many more colors and thus the difference between the managed and unmanaged software is much more exagerrated than on regular gamut monitors.
    I found this great link that helped calm my nerves and helped me get handle on much of what is going on.
    http://www.artstorm.net/journal/2009/07/color-management-wide-gamut-dell-2408/
    Now that is not to say that the 0-255/16-235 issue is not also involved here.  It is definitely possible that a specific codec or compressor is part of the problem, but it sounds like it starts with the color management issue first.
    I hope this helps. 
    Andy

  • Apple Lossless vs. AAC 256k - and best way to change

    I originally imported all my 1500 cds as Apple lossless files figuring that would give me the best audio quality for playing back through my AppleTV. But I have realized that sometimes my bandwidth is not enough (when other are downloading from their computers in the house) and the playback stutters. I also want to be able to fit more songs on my iphone.
    So now I am thinking about re-encoding using AAC 256khz - I do not think I can really hear much difference.
    Firstly what are your opinion on the relative quality of AAV vs. Apple Lossless files....
    and secondly is it best to re-encode by ripping all my cds again (please say no) or can I just select all the lossless files in itunes and have it convert them all to AAC - and if that is the best way how do it do it....?
    Many thanks for your help...

    Well, I have the same question. So last night I compared the original CD vs. Apple Lossless vs. AAC 256kbit/s.
    And to be honest: I cant really hear a difference between AL & AAC@256.
    When I knew which version I was hearing I felt that AL is a bit more clear in the highrange. But when I closed my eyes and asked my girlfriend to randomly pic a quality, I only guessed right in 6 out of 10 trys. So I guess I cant tell the difference.
    My heaphones are Audio Technica: http://www.audio-technica.com/cms/headphones/e69d047fa2f50ad9/index.html
    The tested music was electronic/trance & pop/rock.
    In case I later start hearing classic music or jazz, I might do this test again.
    Kind regards,
    Jan
    Message was edited by: Jan Riggert

  • Adobe Media Encoder creates corrupt H264 mp4 file

    I am using Premeire Pro CS5 and exporting an H264 mp4 file from a 720x480 timeline.  For one of the files I am exporting, AME completes the export, i.e. I see a green check mark.  But the file is corrupt.  When I try to open the file with Quicktime, I get the following error:
    "The operation couldn't be completed - (OSStatus Error - 12848)"
    The strange thing is that other timelines exported without any problem.  And this particular timeline I could export using different (but very similar) export settings.  The only thing I'm changing is the video bitrate.  I'm actually creating three different videos for adaptive bitrate streaming, 300k, 550k, and 800k, all from the same video.  The 300k version is the only one that won't work.  But again, what is strange is that other timelines export out fine using the same exact 300k export settings.  It's just this one timeline that won't export without getting the mentioned error.

    I having the same issue. 
    Any insight on a solution?

  • H264 mp4 gamma fine in sizes under 720x576, blown out any size above

    Hi, I've been banging my head against a wall til the early hours of the morning trying to work out why the encoding of my H264 mp4 is behaving how it is. Can anyone shed any light on whether this is normal behaviour, or a bug?
    Basically, I've been trying to render to a 1280x720 mp4 H264 file from an After Effects Quicktime (100 animation) mov, I've tried various presets and was getting a colour blowout, colours becoming far brighter and more neon. I tried all 3 profiles, and all levels. After many many trial and error I have worked out that a file that is of the dimensions 720x576 or below will have a very close result to the source file, anything above that will have inaccurate blown out colours.
    Why would physical dimensions alter colour values? Is this a bug?
    Near deadline on a job, doing my head in, any help would be appreciated
    Chris

    The only thing that comes to mind is that 720 x 576 is SD, which uses the REC. 601 color space, and 1280 x 720 is HD, which uses the REC. 709 colors.  Maybe the original is incorrectly using the 601 space and it's not getting properly 'converted' to the newer and broader 709 colors.

  • H264 MP4 PAL to NTSC DVD

    Im having issues convertin an H264 mp4 PAL file to an NTSC DVD.  Im getting blocking and stuttering on playback after I use Toast to burn the DVD.  Ive tried to convert the files in mpeg stream clip and in QT but to no avail.  Getting errors with both.  This is an odd scenario in my book, so I figured I would put it out there to see if anyone has had any luck.  Thanks All.

    Have you tried JES Deinterlacer? Much better for transcoding.
    Also, it might be advantageous to convert first into an editable video (anything with low compression) before transcoding. The way you do it, you are asking for two major steps simultaneaously.
    Also, do the encoding to MPEG2 (for the DVD) as a separate last step (in Compressor)

  • Why does apple only support mp4 videos?

    It's not really a problem, i usually use my friends computers to convert my videos since mine is so slow.
    But why does apple only support MP4 and MOV formats? Why not MPEG or DivX?
    I know they cannot use WMV because it is a Microsoft format.
    It's just sometimes when i convert videos, the audio becomes out of sync or iTunes complains it's not playable on my iPod.
    I would just like to know why?
    Thanks for your time.

    If Apple chooses to go with H.264 or MP4 or whatever else they want to support, maybe it would be real nice if iTunes could automatically convert to those formats. So if I dropped my universally standard (and supported by most DVD players) DivX video clip in the library, iTunes would convert and format the video to an iPod friendly format.
    So, let me see if I understand this correctly. You want Apple to pirate proprietary codecs from DivX and build them into iTunes QT access. Tell me, does this mean that Apple is working as your agent and you will be the one spending time behind bars or paying the fines. Or, are you saying that Apple should act as an agent for DivX and charge you for a version of iTunes with legal codecs installed. How about Windows Media? Want to double the cost? What about Real? Or maybe Apple should have different versions of iTunes -- one for you and one for the guy who lives next door who uses old Indeo files?
    I have tried several 3rd party converters and they all suck.
    Perhaps you should be more selective in choosing a converter or invest in a commercial product which is supported by the people selling it.

  • Amarok1 - can't seem to enable mp4/aac tagging support

    I have libmp4v2 and taglib-extras installed, but compiling with the default --with-mp4v2 and even trying to set the --with-mp4v2-dir=/usr/lib or /usr/include, amarok1 (from AUR) will not compile with mp4/aac editing support. Is there another package that I need?
    Thanks!
    Scott

    I did the ./configure --help -- that's where I also found the --with-mp4v2-dir setting. Would building it manually without the PKGBUILD change anything? I can scroll up during the compile and see all the options it's building with ... they're the same options I would set if it's being built manually. The only thing I can see is that it doesn't find mp4.h (I think that's file...on a different computer at the moment). mp4.h exists on my system, and I tried setting the path to it with the --with-mp4v2-dir. Not sure if that's even why it's not working, but I can't see anything else during the ./configure that looks like it's missing! I'll pastebin the output of ./configure when I get back to my other computer.
    Thanks!
    Scott
    edit: forgot to add, I'm on x86_64 if that makes a difference.
    This is the output of ./configure with the default --with-mp4v2 setting in the PKGBUILD. I'm browsing through the configure file, but I can't pick out exactly what's going on. I'm not quite where I can troubleshoot code like that!!
    checking systems.h usability... no
    checking systems.h presence... no
    checking for systems.h... no
    checking for mp4.h... no
    checking for MP4Read in -lmp4v2... yes
    Hope this helps. This is on two machines now. Anyone else using amarok1 care to test their mp4/aac tag writing ability?
    Last edited by firecat53 (2009-07-18 20:50:43)

  • Premiere is making corrupted H264 Mp4 files,  why?

    I am exporting a series of [nested] sequences as H264 NTSC Mp4s.
    If I export one sequence then it works fine and I can play it in Quicktime etc.
    If I export this nested sequence of five timelines, then it produces a corrupted file that no program can use.  It complains that the file is unsupported or corrupt.
    I have noticed at the end , Premiere is stuck on 99.9% progress for 18 minutes.  So I don't think it's finishing the file off properly.
    Any ideas?

    Mr Bansaw, did you sort out your MP4 export problem? I have a single non-nested 10 minute sequence. Using a slightly modified AME HDTV 1080p 25 HQ preset to export to H.264 mp4 as follows:
    PAL, 1920x1080, 25fps, progressive, VBR, 1 pass, Target 10Mbps, Max 25Mbps, AAC 160kbps, 48kHz. (I dropped the target bitrate from 35Mbps in the preset thinking that might be the problem, but it didn't make a difference).
    The export seems to go fine ie without errors, but playing back the exported mp4 gives the occasional but noticeable stutter using VLC or WMP (ugh).
    I will be projecting the video on a large screen so need the best quality.
    I am using PPro 5.0.3 on an Intel i7 920, 12GB RAM, 4 x 1TB 7200 HDD, ATI Radeo 4870 1GB, Windows 7 Ultimate SP1.
    Any suggestions will be welcome.

  • Improting H264 MP4 format video

    Hello.
    I have been trying to import videos that I recorded of my gameplay with AverMedia Live Gamer HD capture card.4
    I have used H264 format and m.mp4 file extension. In older version of CC Premiere Pro videos did work just fine now in 2014 version I just get green screen in videos and I have no idea why.
    Interesting is that I tried to transcode one video with media encoder to mp4 format and that did work out.m
    So I am wondering that what is going on here.
    If you do need any more details please ask and I provide. I just can't figure what would be useful at this point.

    Here is MediaInfo details
    General
    Complete name                            : D:\Live Gamer HD\20140716141715.mp4
    Format                                   : MPEG-4
    Format profile                           : Base Media / Version 2
    Codec ID                                 : mp42
    File size                                : 19.8 GiB
    Duration                                 : 58mn 45s
    Overall bit rate                         : 48.1 Mbps
    Encoded date                             : UTC 2014-07-16 11:17:20
    Tagged date                              : UTC 2014-07-16 11:17:20
    Video
    ID                                       : 2
    Format                                   : AVC
    Format/Info                              : Advanced Video Codec
    Format profile                           : [email protected]
    Format settings, CABAC                   : No
    Format settings, ReFrames                : 1 frame
    Format settings, GOP                     : M=1, N=30
    Codec ID                                 : avc1
    Codec ID/Info                            : Advanced Video Coding
    Duration                                 : 58mn 45s
    Bit rate                                 : 47.9 Mbps
    Width                                    : 1 920 pixels
    Height                                   : 1 080 pixels
    Display aspect ratio                     : 16:9
    Frame rate mode                          : Constant
    Frame rate                               : 25.000 fps
    Standard                                 : NTSC
    Color space                              : YUV
    Chroma subsampling                       : 4:2:0
    Bit depth                                : 8 bits
    Scan type                                : Progressive
    Bits/(Pixel*Frame)                       : 0.924
    Stream size                              : 19.7 GiB (99%)
    Language                                 : English
    Encoded date                             : UTC 2014-07-16 11:17:20
    Tagged date                              : UTC 2014-07-16 11:17:20
    Color primaries                          : BT.601 NTSC
    Transfer characteristics                 : BT.601
    Matrix coefficients                      : BT.601
    Audio
    ID                                       : 1
    Format                                   : AAC
    Format/Info                              : Advanced Audio Codec
    Format profile                           : LC
    Codec ID                                 : 40
    Duration                                 : 58mn 45s
    Source duration                          : 58mn 45s
    Bit rate mode                            : Constant
    Nominal bit rate                         : 256 Kbps
    Channel(s)                               : 2 channels
    Channel positions                        : Front: L R
    Sampling rate                            : 48.0 KHz
    Compression mode                         : Lossy
    Source stream size                       : 106 MiB (1%)
    Language                                 : English
    Encoded date                             : UTC 2014-07-16 11:17:20
    Tagged date                              : UTC 2014-07-16 11:17:20
    mdhd_Duration                            : 3525243
    And here is details from From Premiere Pro CC 2014
    File Path: D:\Live Gamer HD\20140716141715.mp4
    Type: QuickTime Movie
    File Size: 19,8 GB
    Image Size: 1920 x 1080
    Frame Rate: 0,00
    Source Audio Format: 48000 Hz - 16 bit - Stereo
    Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
    Total Duration: 00;58;45;11
    Pixel Aspect Ratio: 1,0
    QuickTime Details:
    Movie contains 1 video track(s), 1 audio track(s), 0 closed caption track(s), and 0 timecode track(s).
    Video:
    Video track 1:
    Duration is
    Average frame rate is 0,00 fps
    Video track 1 contains 1 type(s) of video data:
    Video data block #1:
    Frame Size = 1920 x 1080
    Compressor =
    Quality = Least (1,00)
    Audio:
    Audio track 1 contains 1 type(s) of audio data:
    Audio data block #1:
    Format = 16 bit - Stereo
    Rate = 48000 Hz
    Compressor = MPEG-4 Low Complexity AAC
    Now strange thing is that when I change video format to TS (H.264+AAC) videos are working with latest premiere pro... what is causing that ?
    Also if I use Premiere pro CC (OLD ONE) with that .mp4 files work as well.
    Sorry for wall of text but I thought to paste all data I get from those spots.

  • Converting "Apple Lossless" back to "AAC" - More than 1 track at a time...

    Hello,
    Short version: I have hundreds of tracks that need to "Create AAC Version", and I can't right-click 8,536 songs in my library one at a time to find them all.  Is there a method to sweep the entire library and convert all songs to this format if they are not already? 
    The problem with this is it still creates a duplicate of the song and the other original needs to be deleted. 
    Note - the file name changing (it appends a "1" on the M4A file), the "tag" displayed in iTunes retains the song name.
    Thanks!,
    Joseph
    Long version:  For the benefit of people facing the same problem and combing the forums for help, here's the rest of the story...
    I'm not entirely sure when this changed (and I've reset my Import settings back to AAC 128-bit now), but I've managed to import a good number of CDs at this higher quality "Apple Lossless" format.  Essentially, that's overkill - I listen to an iPod classic with headphones the majority of the time (98%) and I won't hear the difference.
    CHECK:  Edit | Preferences | "General" tab | "Import Settings" button
    Essentially my hard-drive space has been disappearing at a rapid rate.  I downloaded a tool (WinDarStat) and found my iTunes folder is 50% of my 200GB used.  (Yes, I'm on an older laptop -- HD=220GB -- and am getting the 'out of space' warnings.)  I found some folders for recent CDs were over 1GB alone and started digging. 
    I happend to have REM's studio "Man on the Moon" on here twice.  The IN TIME version is AAC 128-bit and only 4.9MB in size, whereas the PART LIES version is Apple Lossless 1068-bit and 8x's larger at 39.9MB. 
    If you right-click a track, it provides option to "Create [other] version.", depending on going to/from ACC to Lossless or vice-versa.
    Once I did this for "Man on the Moon", I got 75% of the song's space back ... from approximately 40MB to 11MB.
    It does create a second copy of the song, so the original has to be deleted - be certain to "Move the song to the Recycle Bin" when warned.
    A better option - all be it more time consuming - is to re-import the CDs.

    For backup see this user tip.
    The Create <Format> version tool uses whatever the current import settings are.
    You can create a playlist of things that need converting as Ed says above.
    To ease the conversion process, and keep your current ratings, playcounts, and playlist membership, plus recyle the old files automatically see my script ConvertFormat. Test on say a single album first to make sure it works as you expect/need.
    tt2

  • A media for an HD wedding file H264 .mp4

    Hi guys,
    Maybe I'm a little dummy but....
    I have a 4,90Gb Mp4 (h264) HD file.
    Is the result of a 27min wedding video project.
    And now?
    How to let bride and groom see their wedding on their own HDTV?
    I bought a 8 Gb pen drive to put it on but of course....a single 4,90Gb file....file is bigger than pen drive system file...(Fat32)
    Do I have to format the pen drive with NTFS bein sure it will be ok with an HDTV?
    Do I have to cut in pieces the file and put  pippo01.mp4 - pippo02.mp4 - pippo03.mp4 etc on the fat32 pen drive?
    What's the way to give friend or customer a file to be seen on their HDTV?
    Thanks for any advice

    NTFS will be fine. Yes certain TVs will have no problem with NTFS (the Samsung ones I have used), others will have issues (PS3). You will find most production companies will upload their edits and even sometimes rushes to Vimeo for clients to look at. That is certainly not unheard of and is very common practice. You could provide a USB pen and burn it to a DVD for compatibility sake. Obviously it would then be DVD MPEG 2 PAL DV, not HD H.264, but it's better than nothing.

  • Itunes match replacing Apple Lossless Files with .AAC

    I have coverted my entire music library to apple lossless.. it appears that iTunes Match over time downgrades my music files to 256kbp .AAC files. 
    Is anyone else seeing this?  How can I get iTunes Match to STOP doing this?

    Michael Allbritton wrote:
    iTunes Match does not touch the files on your computer. These files will be "downgraded" only if you delete the original file and download the matched track. The service does not upload ALAC files to the cloud. It converts the ALAC to a temporary AAC file, which is uploaded to listen to on iOS devices. On your computer, the ALAC files stay ALAC.
    Hmm, that's interesting because on Apple's iTunes Match page it says (my emphasis):
    Which music formats can iTunes Match handle?
    You can match or upload music formats that can be played with iTunes. That includes AAC, MP3, WAV, AIFF, Apple Lossless, and more.
    which clearly suggets that it will upload ALAC to iCloud

Maybe you are looking for