Forum Replies Created

Page 2 of 2
  • [Craig Seeman] “MainConcept, used by Telestream Episode and Sorenson Squeeze, are better as is x264 and hardware accelerated encoders like Matrox MAX.”I am not sure to fully understand :
    do you recommend me to use MainConcept or x264 ?
    (I use 1200kps and 700kps depending if the .mp4 movie is encoded for web browsers or for 3G smartphones)

  • [Paul Sellis] “So I am still for now using Compressor 4 as the better choice for me… “
    Not so sure now !
    😉

    I have seen that in case of low data rate (700Kps) and H264/AAC that Squeeze is better than Compressor…
    I just use filter to adjust sharp, saturation and gamma.

    I have to check again with bigger data rate 1200Kps

  • [Andrew Stuckey] “I can highly recommend using the x264 codec for H264/mp4 format video rather than Apple’s default H264 codec found in QT and Compressor. I’ve recently switched and seen far superior results.”
    I tried Handbrake but didn’t get a better result than Compressor 4…
    For what I have seen in my tests, contrast and chroma are better in Compressor 4. I got more details too in images.

    I tried also Squeeze and didn’t get much better results…

    So I am still for now using Compressor 4 as the better choice for me… but when I see you guys saying that Apple’s Compressor has one of the worst H264 codec I get confused…
    😉

    What would be your encoder chart for .mp4 …264/AAC for Web diffusion at 1Mbs ?
    For the moment, it could be something like that for me:
    1 – Compressor 4
    2 – Squeeze 8
    3 – Handbrake
    4 – MPEG Streamclip or ffmpegX

    I don’t have tested yet Episode…

  • Hum… let’s resume my “problem” :
    – I use RTMP streaming on Amazon CloudFront.
    – Compressor 4 .mp4 generated files are well played with RTMP. Good so far…

    – I only have a little problem with this file when it’s played on iPhone with HTML5: I get 15 seconds before playing…
    (I use JW Player with HTML5 fallback if RTMP isn’t supported)

    So I am looking for a way to compress the file which would make it fully optimized for RTMP and HTML5

    [Craig Seeman] “Look under the HTTP Live Streaming presets.”
    HTTP Live Streaming isn’t compatible with RTMP streaming, isn’t it ?

  • I use Compressor 4

    I’ll try to change .m4v to .mp4 and see if there is any improvement with Handbrake encoded file

    ON Amazon CloudFront, I don’t have noticeable delay when played with RTMP. It’s only when played on smartphone with HTML5 (I tested on iPhone)…

  • Thanks for your answer Andrew

    I tried Handbrake but I saw that resulted file would be a .m4v instead of a .mp4
    I am pretty sure that manually changing file extension after encoding would break compatibility at least with RTMP…
    🙁

    Am I wrong ?

  • [Paul Sellis] “I use JW Player so I use RTMP streaming and when platform doesn’t support it (smartphones) it fallbacks to HTTP streaming.”
    Oops… I should have said “… it fallback to HTML5”

    So my title of this post should be: “Compressor: .mp4 file H264/AAC optimized both for RTMP and HTML5 ?”

  • Paul Sellis

    January 1, 2009 at 9:54 pm in reply to: Compressor : FLV H264 + Metadatas ?

    You mean that with FFMPEG or Episode Metadatas are automaticaly injected in the FLV ?

  • Paul Sellis

    January 1, 2009 at 8:45 pm in reply to: Compressor : FLV H264 + Metadatas ?

    I need the duration to be able to do HTTP pseudo-streaming.

Page 2 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy