rework transcode plugin about castnow HOT 9 OPEN

This sounds like some good things apart from the second point. AFAIK the
chromecast can play both mkv and avi as long as the codecs are supported.
The detection should be of what codecs the file uses :-)
On Nov 23, 2014 7:47 PM, "Simon Kusterer" [email protected] wrote:

The transcode plugin has certain limitations at the moment:

• Some player controls like play/pause/seek don't work while
  transcoding
• There is no playlist support

Improvements that could be made:

• Instead of transcoding on the fly and piping the output directly as
  HTTP response to the user the output should be piped into an temp file
  which acts as some sort of buffer. While the transcoding is in progress the
  temp file can be piped to the user as HTTP response. This way
  play/pause/seek should work again. The temp files could be deleted on
  process.end().
• Don't know if this is too much magic: Instead of the --tomp4 option
  files could get transcoded based on the file extensions. For example .avi
  and .mkv would be transcoded but not .mp4 or .mp3. This way we should also
  be able to create playlists with files which need transcoding.
• Users should get an error message displayed if they try to transcode
  a file but don't have ffmpeg installed.

—
Reply to this email directly or view it on GitHub
#32.

from castnow.

Sounds like the correct way todo it :) The question is if there is a node-module to detect the codecs which not requires any additional tools to be installed.

from castnow.

I'm wondering how the Videostream Chrome extension handles this stuff.

from castnow.

Found this reddit thread: http://www.reddit.com/r/Chromecast/comments/22wbge/videostream_now_supports_all_file_formats/

from castnow.

http://stackoverflow.com/questions/10947896/seeking-video-while-transcoding-with-ffmpeg

from castnow.

Related discussions
#58

from castnow.

OK, there are a simple bin of ffmpeg (avconv) that can give all information about a media file: ffprobe (or avprobe, at the newest versions). There are node.js modules to parse the ffprobe information in a json file, but get that informations is a quite simples task even without this modules.

About how videostrem does what it does, i suspect they use some type of FIFO (first in first out file, or named pipe on unix SOs) to handle wiht play/pause situations, becouse sekking IMO is a simple question of restart the trasnconding process at the new point of video file (maybe with -ss on ffmprg).

from castnow.

@kriptolix:

About how videostrem does what it does, i suspect they use some type of FIFO (first in first out file, or named pipe on unix SOs) to handle wiht play/pause situations, becouse sekking IMO is a simple question of restart the trasnconding process at the new point of video file (maybe with -ss on ffmprg) explaining why.

I don't expect seeking to work like that with the -ss option. See my comment here and also another comment here.

from castnow.

"Using the -ss option doesn't output byte range of the original file, it creates a new file with a different byte stream entirely"

Yes @parshap, it's right, but I believe that is exactly what happen with videostream, a new request of a the new transcoding output ("new file") using the current session, only the transition is too fast and smooth to be noted. Play/Pause with this logic also is possible, just saving the current point of video file e restarting the transcode by this.

ps: I am novice in the trasconding chromecast world, so excuse if my theory not make sense, I could not try this yet.

from castnow.