moshy 1.0.2 → 2.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 01a2d4b1a7da07ede5233ef927810cc9c2ad22dc
-  data.tar.gz: 25f1da8cb50e198ff6d73e63cfdbda58ecdc0703
+SHA256:
+  metadata.gz: edf65fecfa904ea31534e576836c26e9e044bd98f1366effca7547202c099ac3
+  data.tar.gz: c5d56088d7a9c84c55720ee6fe839e88cbb1cd9af3eef7ba0f712496af867e85
 SHA512:
-  metadata.gz: 4e8ce36d5840438cf53541ad9ef9cd7b0f4f00cebea8819f33f45be8d6d1c43a795db9455b05648045042ff5408e59738e24a318f6ce045fae9540492801b998
-  data.tar.gz: 6ca6009760d2cea4a35792ba439054d4870a663dc27b8337d10d26df0d63212c1ed2026ac33b5f67cb00bdb24b4d5ea586017f08b4ae2d763a0bce378e11042f
+  metadata.gz: 38e68fc229fb0e00cafb669bb2239ac24ec982aef442dabbeba00c2647bf81270627c36eae86664f39e252dbba8e407f9427661a8f4201765c43bff6f2cb2ee3
+  data.tar.gz: a3656dfab4e713f695d443f825e46c92b3b3c4e6f93593b35034cb9118820c48b2370733b1c2ccfe3479650e517f89267050f8793116585537b91badb9aca310

data/.gitignore

@@ -1,22 +1,22 @@
-*.gem
-*.rbc
-.bundle
-.config
-.yardoc
-Gemfile.lock
-InstalledFiles
-_yardoc
-coverage
-doc/
-lib/bundler/man
-pkg
-rdoc
-spec/reports
-test/tmp
-test/version_tmp
-tmp
-*.bundle
-*.so
-*.o
-*.a
-mkmf.log
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp
+*.bundle
+*.so
+*.o
+*.a
+mkmf.log

data/DEVNOTES.md

@@ -0,0 +1,7 @@
+# Running on Windows 10
+
+Need to have PATH set up properly with ffmpeg
+
+```
+ruby -Ilib ./bin/moshy -m prep -i i.mp4 -o o.avi
+```

data/Gemfile

@@ -1,4 +1,4 @@
-source 'https://rubygems.org'
-
-# Specify your gem's dependencies in moshy.gemspec
-gemspec
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in moshy.gemspec
+gemspec

data/LICENSE.txt

@@ -1,22 +1,22 @@
-Copyright (c) 2015 Way Spurr-Chen <wayspurrchen@gmail.com> <http://wayspurrchen.com/>
-
-MIT License
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+Copyright (c) 2015 Way Spurr-Chen <wayspurrchen@gmail.com> <http://wayspurrchen.com/>
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -1,87 +1,94 @@
-# moshy
-
-![](http://imgur.com/OMLTr26.gif)  
-created with moshy's pdupe options
-
-**moshy** is a command line datamoshing utility kit for AVI files, based heavily on [aviglitch](https://github.com/ucnv/aviglitch).
-It's designed to make common datamoshing tasks easier without having to open avidemux or other GUI tools. It lets you do stuff like:
-
-- Convert video files into AVI video files with minimal I-Frames and no B-frames for ultimate moshability
-- Create P-Frame duplication effects quickly
-- Split a long video file into multiple clips based on its I-Frames
-- "Bake" your datamoshed video, encoding the corruption as actual video content for uploading to video services or moshing even further!
-- Identifying keyframe and deltaframe indexes in any AVI file
-- ...and more!
-
-If you don't know how to use the command line, this is a great opportunity to learn:
-
-- Mac OS X Tutorial: http://blog.teamtreehouse.com/introduction-to-the-mac-os-x-command-line
-- Windows Tutorial: http://lifehacker.com/5633909/who-needs-a-mouse-learn-to-use-the-command-line-for-almost-anything
-
-## Get it!
-
-You'll need to install [Ruby](https://www.ruby-lang.org/en/). If you're on Mac OS X, you probably already have a local version of Ruby installed. Once that's done, you can use Rubygems (which comes with Ruby) to install moshy:
-
-```
-gem install moshy
-```
-
-From there, you can use `moshy` from the command line.
-
-## What's it do?
-
-Moshy currently has six different modes:
-
-- `prep` - Preps a video file for datamoshing with moshy by converting it
-  into an AVI with no B-Frames (they're not good for moshing), and placing as
-  few I-Frames as possible. Requires ffmpeg be installed locally.
-- `isplit` - Extracts individual clips from an AVI where each clip is
-  separated by I-frames in the original AVI. Great for getting specific
-  clips out of a larger video and later doing I-frame moshing.
-- `inspect` - Reads an .avi file and prints which video frames are keyframes
-  (I-Frames) and which frames are delta frames (P-frames or B-frames). moshy
-  cannot tell the difference between a P-frame or a B-frame, so you will want
-  to use avidemux or another program if you need to know.
-- `pdupe` - Duplicates a P-frame at a given frame a certain amount. To find
-  out which frames are P-frames, use software like avidemux to look at the
-  frame type. WARNING: This mode is a little glitchy. You may need to set
-  the interval 1 or 2 above or below the frame number you actually want to
-  duplicate. I'm not sure why this happens, but try it with a small
-  duplication amount first. NOTE: This can mode take a while to process
-  over 60-90 frame dupes.
-- `ppulse` - Takes c number of frames and every n frames and duplicates them a
-  given amount, resulting in a consistent P-duplication datamosh that's
-  good for creating rhythmic effects. This was originally created to
-  create mosh effects in sync with a beat for a music video.
-- `bake` - "Bakes" your datamosh by creating a new video file from your
-  datamoshed .avi, causing the datamosh effects to be treated as the actual
-  content of the new video instead of an error. Requires ffmpeg to be
-  installed locally.
-
-You can access detailed info on how to use each of them from the command line with
-the command `moshy -m <mode> --help`.
-
-## Cool!
-
-If you think this is cool, you'll probably find my list of [glitch art resources](http://www.glitchet.com/resources)
-useful as well as the [Glitchet newsletter](http://www.glitchet.com/), a free weekly futuristic
-news and glitch aesthetic e-zine.
-
-## Quick tutorial
-
-Here's a short example of how you might use moshy to create a P-dupe mosh:
-
-1. Choose a YouTube video you want to mosh (I'll use "Charlie bit my finger": <https://www.youtube.com/watch?v=bnRVheEpJG4>)
-2. Download it with KeepVid (<http://keepvid.com/?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DbnRVheEpJG4>)
-3. "Prep" it with moshy to turn it into an .AVI with minimal I-Frames and all P-frames (because B-frames don't mosh well):  
-   `moshy -m prep -i charlie.mp4 -o charlie.avi`
-4. Open charlie.avi in avidemux and clip it down to the segment I want (moshy will soon be able to do this with a "clip" command): ![](http://i.imgur.com/OBy8pbB.png)
-5. Open charlie_clip.avi and find the frame I want to P-dupe mosh (here, frame 196): ![](http://i.imgur.com/aZsZIx6.png)
-6. Use moshy in pdupe mode to dupe frame 196 60 times:  
-   `moshy -m pdupe -i charlie_clip.avi -f 196 -d 60 -o charlie_clip-dupe.avi`  
-   Open it in a video player (I use VLC) and see if it looks good.
-7. Awesome, I love it, but I want to clip it down to size. However, since it has so few I-frames, if I just clip it anywhere, the beginning of the video will become corrupted because of lack of pixel data. Let's use moshy to bake the mosh:  
-   `moshy -m bake -i charlie_clip-dupe.avi -o charlie_clip-dupe-bake.avi`
-8. Done. Let's open it back up in avidemux, clip it down to size, and save our final result: ![](http://i.imgur.com/07abIqT.png)
-9. Looks good to me. Let's save it as an MP4 so that I can upload it to Giphy, which will convert it into a .gif for me. (I'm hoping to add modes to moshy that convert videos to .gif and .mp4 directly, too.)
-10. Done! ![](https://media.giphy.com/media/3o85xoWYyG1HEVs8Vy/giphy.gif)
+# moshy
+
+![](http://imgur.com/OMLTr26.gif)  
+created with moshy's pdupe options
+
+**moshy** is a command line datamoshing utility kit for AVI files, based heavily on [aviglitch](https://github.com/ucnv/aviglitch).
+It's designed to make common datamoshing tasks easier without having to open avidemux or other GUI tools. It lets you do stuff like:
+
+- Convert video files into AVI video files with minimal I-Frames and no B-frames for ultimate moshability
+- Create P-Frame duplication effects quickly
+- Split a long video file into multiple clips based on its I-Frames
+- "Bake" your datamoshed video, encoding the corruption as actual video content for uploading to video services or moshing even further!
+- Identifying keyframe and deltaframe indexes in any AVI file
+- ...and more!
+
+If you don't know how to use the command line, this is a great opportunity to learn:
+
+- Mac OS X Tutorial: http://blog.teamtreehouse.com/introduction-to-the-mac-os-x-command-line
+- Windows Tutorial: http://lifehacker.com/5633909/who-needs-a-mouse-learn-to-use-the-command-line-for-almost-anything
+
+## Get it!
+
+You'll need to install [Ruby](https://www.ruby-lang.org/en/). If you're on Mac OS X, you probably already have a local version of Ruby installed. Once that's done, you can use Rubygems (which comes with Ruby) to install moshy:
+
+```
+gem install moshy
+```
+
+From there, you can use `moshy` from the command line.
+
+For a couple commands (`prep` and `bake`), you need to have ffmpeg installed locally.
+[You can get it for your OS here.](https://www.ffmpeg.org/download.html)
+
+## What's it do?
+
+Moshy currently has six different modes:
+
+- `prep` - Preps a video file for datamoshing with moshy by converting it
+  into an AVI with no B-Frames (they're not good for moshing), and placing as
+  few I-Frames as possible. Requires ffmpeg be installed locally.
+- `isplit` - Extracts individual clips from an AVI where each clip is
+  separated by I-frames in the original AVI. Great for getting specific
+  clips out of a larger video and later doing I-frame moshing.
+- `inspect` - Reads an .avi file and prints which video frames are keyframes
+  (I-Frames) and which frames are delta frames (P-frames or B-frames). moshy
+  cannot tell the difference between a P-frame or a B-frame, so you will want
+  to use avidemux or another program if you need to know.
+- `pdupe` - Duplicates a P-frame at a given frame a certain amount. To find
+  out which frames are P-frames, use software like avidemux to look at the
+  frame type. WARNING: This mode is a little glitchy. You may need to set
+  the interval 1 or 2 above or below the frame number you actually want to
+  duplicate. I'm not sure why this happens, but try it with a small
+  duplication amount first. NOTE: This can mode take a while to process
+  over 60-90 frame dupes.
+- `ppulse` - Takes c number of frames and every n frames and duplicates them a
+  given amount, resulting in a consistent P-duplication datamosh that's
+  good for creating rhythmic effects. This was originally created to
+  create mosh effects in sync with a beat for a music video.
+- `bake` - "Bakes" your datamosh by creating a new video file from your
+  datamoshed .avi, causing the datamosh effects to be treated as the actual
+  content of the new video instead of an error. Requires ffmpeg to be
+  installed locally.
+
+You can access detailed info on how to use each of them from the command line with
+the command `moshy -m <mode> --help`.
+
+## Cool!
+
+If you think this is cool, you'll probably find my list of [glitch art resources](http://www.glitchet.com/resources)
+useful as well as the [Glitchet newsletter](http://www.glitchet.com/), a free weekly futuristic
+news and glitch aesthetic e-zine.
+
+## Quick tutorial
+
+Here's a short example of how you might use moshy to create a P-dupe mosh:
+
+1. Choose a YouTube video you want to mosh (I'll use "Charlie bit my finger": <https://www.youtube.com/watch?v=bnRVheEpJG4>)
+2. Download it with KeepVid (<http://keepvid.com/?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DbnRVheEpJG4>)
+3. "Prep" it with moshy to turn it into an .AVI with minimal I-Frames and all P-frames (because B-frames don't mosh well):  
+   `moshy -m prep -i charlie.mp4 -o charlie.avi`
+4. Open charlie.avi in avidemux and clip it down to the segment I want (moshy will soon be able to do this with a "clip" command): ![](http://i.imgur.com/OBy8pbB.png)
+5. Open charlie_clip.avi and find the frame I want to P-dupe mosh (here, frame 196): ![](http://i.imgur.com/aZsZIx6.png)
+6. Use moshy in pdupe mode to dupe frame 196 60 times:  
+   `moshy -m pdupe -i charlie_clip.avi -f 196 -d 60 -o charlie_clip-dupe.avi`  
+   Open it in a video player (I use VLC) and see if it looks good.
+7. Awesome, I love it, but I want to clip it down to size. However, since it has so few I-frames, if I just clip it anywhere, the beginning of the video will become corrupted because of lack of pixel data. Let's use moshy to bake the mosh:  
+   `moshy -m bake -i charlie_clip-dupe.avi -o charlie_clip-dupe-bake.avi`
+8. Done. Let's open it back up in avidemux, clip it down to size, and save our final result: ![](http://i.imgur.com/07abIqT.png)
+9. Looks good to me. Let's save it as an MP4 so that I can upload it to Giphy, which will convert it into a .gif for me. (I'm hoping to add modes to moshy that convert videos to .gif and .mp4 directly, too.)
+10. Done! ![](https://media.giphy.com/media/3o85xoWYyG1HEVs8Vy/giphy.gif)
+
+## Trouble?
+
+Having issues? Please [file an issue](https://github.com/wayspurrchen/moshy/issues/new)!

data/Rakefile

@@ -1,2 +1,2 @@
-require "bundler/gem_tasks"
-
+require "bundler/gem_tasks"
+

data/bin/moshy

@@ -1,105 +1,107 @@
-#!/usr/bin/env ruby
-
-require 'optparse'
-require 'slop'
-require 'moshy'
-
-module Moshy
-  def self.top_level_help
-    $options = {
-
-    }
-    opts = OptionParser.new do |opts|
-      opts.banner = "
-moshy, a Ruby utility for making it easier to datamosh AVI files. It has
-multiple modes that can be run with the -m or --mode option.
-
-  MODES DETAILS
-  -------------
-
-  \"prep\"
-  ------
-  Preps a video file for datamoshing with moshy by converting it
-  into an AVI with no B-Frames (they're not good for moshing), and placing as
-  few I-Frames as possible. Requires ffmpeg be installed locally.
-
-  \"isplit\"
-  --------
-  Extracts individual clips from an AVI where each clip is
-  separated by I-frames in the original AVI. Great for getting specific
-  clips out of a larger video and later doing I-frame moshing.
-
-  \"pdupe\"
-  -------
-  Duplicates a P-frame at a given frame a certain amount. To find
-  out which frames are P-frames, use software like avidemux to look at the
-  frame type. WARNING: This mode is a little glitchy. You may need to set
-  the interval 1 or 2 above or below the frame number you actually want to
-  duplicate. I'm not sure why this happens, but try it with a small
-  duplication amount first. NOTE: This can mode take a while to process
-  over 60-90 frame dupes.
-
-  \"ppulse\"
-  --------
-  Takes c number of frames and every n frames and duplicates them a
-  given amount, resulting in a consistent P-duplication datamosh that's
-  good for creating rhythmic effects. This was originally created to
-  create mosh effects in sync with a beat for a music video.
-
-  \"bake\"
-  ------
-  \"Bakes\" your datamosh by creating a new video file from your
-  datamoshed .avi, causing the datamosh effects to be treated as the actual
-  content of the new video instead of an error. Requires ffmpeg to be
-  installed locally.
-
-  \"inspect\"
-  ---------
-  Reads an .avi file and prints which video frames are keyframes
-  (I-Frames) and which frames are delta frames (P-frames or B-frames). moshy
-  cannot tell the difference between a P-frame or a B-frame, so you will want
-  to use avidemux or another program if you need to know.
-
-Run moshy with mode -m <mode> --help to see options for individual modes.
-  "
-    end
-
-    begin
-      opts.parse
-    rescue OptionParser::InvalidOption, OptionParser::InvalidArgument
-    end
-
-    puts opts
-  end
-end
-
-# Because we have multiple modes, we do some initial basic arg checking
-# to see if they specified a mode. If not, we show the top-level help menu.
-result = Slop.parse suppress_errors: true do |o|
-  o.string '-m', '--mode'
-end
-
-mode_classes = {
-  "inspect" => Moshy::Inspect,
-  "isplit" => Moshy::ISplit,
-  "pdupe" => Moshy::PDupe,
-  "ppulse" => Moshy::PPulse,
-  "prep" => Moshy::Prep,
-  "bake" => Moshy::Bake
-}
-
-if mode_classes.has_key? result[:m]
-  # We need to strip out the "m" otherwise our other arg parsers
-  # will choke on the extra parameter
-  ARGV.each_with_index do |o, i|
-    if o == "-m" || o == "--m"
-      ARGV.delete_at(i + 1)
-      ARGV.delete_at(i)
-      break
-    end
-  end
-
-  mode_classes[result[:m]].new.cli ARGV
-else
-  Moshy.top_level_help
+#!/usr/bin/env ruby
+
+require 'optparse'
+require 'slop'
+require 'moshy'
+
+module Moshy
+  def self.top_level_help
+    $options = {
+
+    }
+    opts = OptionParser.new do |opts|
+      opts.banner = "
+moshy, a Ruby utility for making it easier to datamosh AVI files. It has
+multiple modes that can be run with the -m or --mode option.
+
+  MODES DETAILS
+  -------------
+
+  \"prep\"
+  ------
+  Preps a video file for datamoshing with moshy by converting it
+  into an AVI with no B-Frames (they're not good for moshing), and placing as
+  few I-Frames as possible. Requires ffmpeg be installed locally.
+
+  \"isplit\"
+  --------
+  Extracts individual clips from an AVI where each clip is
+  separated by I-frames in the original AVI. Great for getting specific
+  clips out of a larger video and later doing I-frame moshing.
+
+  \"pdupe\"
+  -------
+  Duplicates a P-frame at a given frame a certain amount. To find
+  out which frames are P-frames, use software like avidemux to look at the
+  frame type. WARNING: This mode is a little glitchy. You may need to set
+  the interval 1 or 2 above or below the frame number you actually want to
+  duplicate. I'm not sure why this happens, but try it with a small
+  duplication amount first. NOTE: This can mode take a while to process
+  over 60-90 frame dupes.
+
+  \"ppulse\"
+  --------
+  Takes c number of frames and every n frames and duplicates them a
+  given amount, resulting in a consistent P-duplication datamosh that's
+  good for creating rhythmic effects. This was originally created to
+  create mosh effects in sync with a beat for a music video.
+
+  \"bake\"
+  ------
+  \"Bakes\" your datamosh by creating a new video file from your
+  datamoshed .avi, causing the datamosh effects to be treated as the actual
+  content of the new video instead of an error. Requires ffmpeg to be
+  installed locally.
+
+  \"inspect\"
+  ---------
+  Reads an .avi file and prints which video frames are keyframes
+  (I-Frames) and which frames are delta frames (P-frames or B-frames). moshy
+  cannot tell the difference between a P-frame or a B-frame, so you will want
+  to use avidemux or another program if you need to know.
+
+Run moshy with mode -m <mode> --help to see options for individual modes.
+  "
+    end
+
+    begin
+      opts.parse
+    rescue OptionParser::InvalidOption, OptionParser::InvalidArgument
+    end
+
+    puts opts
+  end
+end
+
+# Because we have multiple modes, we do some initial basic arg checking
+# to see if they specified a mode. If not, we show the top-level help menu.
+result = Slop.parse suppress_errors: true do |o|
+  o.string '-m', '--mode'
+end
+
+puts result
+
+mode_classes = {
+  "inspect" => Moshy::Inspect,
+  "isplit" => Moshy::ISplit,
+  "pdupe" => Moshy::PDupe,
+  "ppulse" => Moshy::PPulse,
+  "prep" => Moshy::Prep,
+  "bake" => Moshy::Bake
+}
+
+if mode_classes.has_key? result[:m]
+  # We need to strip out the "m" otherwise our other arg parsers
+  # will choke on the extra parameter
+  ARGV.each_with_index do |o, i|
+    if o == "-m" || o == "--m"
+      ARGV.delete_at(i + 1)
+      ARGV.delete_at(i)
+      break
+    end
+  end
+
+  mode_classes[result[:m]].new.cli ARGV
+else
+  Moshy.top_level_help
 end