2-Pass Encoding

Yea its been in my thought process. I have been thinking on making "actions" and then defining an action to a video field. So you can add unlimited passes if you wanted to... I just haven't quite got the UXP figured out yet. Needs to have an "easy" work flow that isn't confusing. And then we need a formatter that's going to be able to handle this output.

Maybe instead of giving too much rope in this, we create a framework that extends/creates pre defined actions for us. So we could have HTML5 action (this action creates an ogg,mp4 with a fall back of flv)... etc. High Res / Low Res action. 2/3 different sizes? HD Quality Action? Then each of those will have their own formatter to accommodate the specific action? Inside each action displays the passes and the command that's to be ran, here you can customize it for each...

Thoughts and ideas?

I don't think you gave this much thought :p.

Let me sleep on this and think about this some more.

I was being sarcastic when I said you haven't given this much thought lol. You have thought about it way more than I have.

I'm thinking why can't we have a default, that plays on page load, or loads (instead of a thumbnail) and then just have options to change to a higher resolution? Maybe spit out each resolution as links in the them and let the themer do what they want with them?

So new tab in admin, why not call it "2 Pass Encoding" or "2 Pass" or something, that has predefined actions. Create a class file "action" that will extend for each action we do. Put in some hooks for the current system to integrate/extend the current functionality (need to do this anyway).

When setting up the field in the content type, I guess add a new area to either use default encoding, or use a 2 pass action? If using a 2 pass action, we need to make sure the right cck formatter is selected as it will have different options than the regular video formatter.

What else we got to think of?

Subscribing.

I agree with having some kind of framework for preset encoding types, even multiple video types per video, for different platforms.
We could also integrate this with Rules.

We will have separate section to create video profiles, it can be a another tab in video settings. There you can create custom video profiles, underneath transcoder tab you can see presets you already have for the selected transcoder, it can be Zencoder, FFMPEG or whatever.

Initially we will have profiles

- 720p (just to be future proof :-P )
- HQ (VGA, H264, medium encoding quality)
- LQ (QVGA/VGA, H264, low encoding quality for small bandwith users)

Users can create custom profiles and those also will be showing there, create custom profiles interface same like current transcoder settings interface which is to add video bitrate bla bla.

I thought of implementing this one soon, but issues is how can I handle n-pass encoding, is it better to integrate with rules? but I don't like end-users to mess up with loads of modules.

subscribing

Mobile profile which I'm going to add in to profiles

audio_bitrate: 128 (or less)
audio_sample_rate: 44100 (or less)
size: 480×320
max_framerate: 30
video_bitrate: 1500 (or less)

subscribing

subscribing

+1 :)

Few days back I committed a FFMPEG profiles code, which is working as below.

The video module do have presets (by default HTML5 mp4, HTML5 ogv, HTML5 webm), all those presets are .inc files you can find them in presets folder, but if you want to add another preset then you can create a folder called presets and add your .inc file according to same standers in default presets.

HTML5 webm preset as below.

//$Id: html5_webm.inc,v 1.1.2.1 2010/11/17 15:32:28 heshanmw Exp $
/*
 * @file
 * Class file used to store metadata on the video.
 *
 */
class html5_webm implements video_preset_interface {

  protected $name = 'HTML5 WebM';
  protected $value = 'html5_webm';

  public function __construct() {

  }

  /**
   * Interface Implementations
   * @see sites/all/modules/video/includes/metadata_interface#get_name()
   */
  public function get_name() {
    return $this->name;
  }

  /**
   * Interface Implementations
   * @see sites/all/modules/video/includes/metadata_interface#get_help()
   */
  public function get_help() {
    return t('<b>HTML5 WebM Video</b><br> Dimention : 640*340<br>Video Codec : AAC<br> Audio Codec : MP3', array());
  }

  /**
   * Interface Implementations
   * @see sites/all/modules/video/includes/metadata_interface#get_value()
   */
  public function get_value() {
    return $this->value;
  }

  public function get_properties() {
    $properties = array(
      'extension' => 'webm',
      'width' => '640',
      'height' => '340',
      'quality' => '',
      'speed' => '',
      'upscale' => '',
      'stretch' => '',
      'frame_rate' => '',
      'max_frame_rate' => '',
      'keyframe_interval' => '',
      'video_codec' => '',
      'video_bitrate' => '',
      'aspect_mode' => '',
      'bitrate_cap' => '',
      'buffer_size' => '',
      'h264_profile' => '',
      'h264_level' => '',
      'skip_video' => '',
      'audio_codec' => '',
      'audio_quality' => '',
      'audio_bitrate' => '',
      'audio_channels' => '',
      'audio_sample_rate' => '',
      'skip_audio' => '',
      'start_clip' => '',
      'clip_length' => '',
      'command' => array(
        'ffmpeg -pass 1 -passlogfile !videofile -threads 16  -keyint_min 0 -g 250 -skip_threshold 0 -qmin 1 -qmax 51 -i !videofile -vcodec libvpx -b 204800 -s !widthx!height -aspect 4:3 -an -f webm -y NUL',
        'ffmpeg -pass 2 -passlogfile !videofile -threads 16  -keyint_min 0 -g 250 -skip_threshold 0 -qmin 1 -qmax 51 -i !videofile -vcodec libvpx -b 204800 -s !widthx!height -aspect 4:3 -acodec libvorbis -ac 2 -y !convertfile'
      )
    );
    return $properties;
  }

}

You can see there command array which is actually to run commands, now video module is designed to run with any type of installed Transcoders. Eg, in this case its using ffmpeg but you can see we are using ffmpeg2theora, mcoder and HandBrekeCLI too.

So to enable 2 pass encoding what you want to do is set the command parameters as appropriate.

Welcome your comments!!