Skip to content

read-0nly/Datamoshing

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Datamoshing

Repo of my moshing resources

Good resources

  • FFGlitch - this is a fucking godsend Ramiro I love you
  • Some good examples of working with it from @tiberiuiancu
  • Librosa: Python library, great for audio analysis
  • Spleeter: For splitting tracks into components for analysis
  • Audacity: For processing audio pre-analysis
  • Avidemux 2.6.5 Every guide has their own preference, but this with libxvid works well as prep for ffglitch, save as mp4. if you pass it through ffglitch you can strip all the I-frames in the commandline so I often just rinse it through without checking settings.
  • XVid Codec: Avidemux might not have it by default

Basic concepts

  • mpeg has 3 frame types, I-frame, P-frame, and B-frame
  • I do not understand B-frames, so I just make sure I have none
  • They seem to be some sort of backwards P frame? Anyways, don't include them in encoding
  • I-frames are basically full images, all pixel data but compressed, think a jpg
  • P-frames contain some pixel data, but mostly contain motion data where possible. It'll try to generate the next frame by applying motion data to the result of previous motion data applied to the previous I-frame.
  • This is where the magic happens - by splicing two videos in the sea of P-frames between I-frames, you apply the motion and included pixel data of video 2 to video 1. This causes video 2 to "push through" video 1's last good P-frame, causing that delicious crunchy mosh~
  • Alternatively, duplicate P-frames to over-emphasize motion
  • or delete I-frames to cause a sort of internal corruption where motions get misaligned.

Quick start

image image

About

Repo of my moshing resources

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published