What a novel and very useful piece of code! It can process a batch, runs fast, and is Portable. Fantastic. Thanks.
I was hoping you could entertain some suggestions...
Could the original video extension be included in the output filename. E.g., video.wmv_vcs.avi . Sometimes there are videos with the same names but with different extensions.
Would it be possible to provide an option to not overwrite existing _vcs files if one already exists.
The AVI (h.263) output is ok, but MP4 (MPEG-4) might be more 'universal'. Many TVs, for instance, can only accept MP4. I wonder if there's a way we could select our own codec and container. I know FFmpeg can do just about everything.
The app seems to choke on YouTube WEBM format videos. A short clip takes a long time, long clips take forever. Also, the output consists of only a single tile, not a matrix.
I discovered that dropping a folder of videos on VideoCS doesn't work. Any way that could be accommodated?
Thanks again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What a novel and very useful piece of code! It can process a batch, runs fast, and is Portable. Fantastic. Thanks.
I was hoping you could entertain some suggestions...
Could the original video extension be included in the output filename. E.g., video.wmv_vcs.avi . Sometimes there are videos with the same names but with different extensions.
Would it be possible to provide an option to not overwrite existing _vcs files if one already exists.
The AVI (h.263) output is ok, but MP4 (MPEG-4) might be more 'universal'. Many TVs, for instance, can only accept MP4. I wonder if there's a way we could select our own codec and container. I know FFmpeg can do just about everything.
The app seems to choke on YouTube WEBM format videos. A short clip takes a long time, long clips take forever. Also, the output consists of only a single tile, not a matrix.
I discovered that dropping a folder of videos on VideoCS doesn't work. Any way that could be accommodated?
Thanks again.
Thanks for the feedback, these are good suggestions. We'll look to incorporate these into an update soon.