Mpv – A free, open-source, and cross-platform media player

Post by Sophira » Sun, Aug 18, 2024, 4:46 PM UTC

namdnay wrote: post #268

kstenerud wrote: post #243

Earlier quoted context omitted.

> A playback architecture that can wrangle all of that cruelty into a consistent experience was hard won. No, it hasn't. The only reason I use mpv instead of VLC is because of the frame step feature. Everyone else has proven that it is possible and practical to do. Never let the perfect be the enemy of the good. If people don't use your product, it doesn't matter how right and pure of vision you are.

> No, it hasn't. The only reason I use mpv instead of VLC is because of the frame step feature You realise your requirement is important for less than 0.01% of users? For every requirement you have to balance future maintainability and the impact it has on the code base against potential revenue

Post by thiht » Sun, Aug 18, 2024, 5:00 PM UTC

The_Colonel wrote: post #199

justin66 wrote: post #161

Earlier quoted context omitted.

The developer responds to a comment: But many players are able to do it for years. with: If it's so easy, why are you not doing it? He's not just a butthole, he's a stereotypical open source developer butthole. On the other hand, if he worked for Microsoft, he'd be claiming that it takes a PhD to do it...

The dev said they are happy to accept patch for this feature. Remember that you're not entitled to demand new features, as a (non-paying) user, you can't allocate dev's time to work on what you want.

Post by eviks » Sun, Aug 18, 2024, 5:02 PM UTC

variadix wrote: post #111

sergiotapia wrote: post #83

Earlier quoted context omitted.

i wonder why he's such an ass about it, and totally adamant that it's impossible when multiple players already do this fast. ego?

I think technically he’s correct (I haven’t worked on media decoding code, but I understand how common video encoding formats work). If you have a long video with only a single key frame at the beginning then to step back you would need to, starting from the beginning of the video, decode every frame up to the previous frame you wanted to jump to in order to apply frame deltas, also assuming you have some sort of fra…

Post by arp242 » Sun, Aug 18, 2024, 5:13 PM UTC

latexr wrote: post #317

arp242 wrote: post #50

Earlier quoted context omitted.

I don't really know what "scrubbing" is, but If you add "exact" to seek then it will use exact (non-keyframe) seeks. I think that's what you want? For example from my input.conf: Right seek 5 # In seconds; these are limited by keyframes Left seek -5 Shift+Right seek 2 exact # Smaller non-keyframe-limited, seeks with shift Shift+Left seek -2 exact Obviously, this is slower. Sometimes much slower (depending on the file…

> Obviously, this is slower. Sometimes much slower (depending on the file). Anecdotally, I’d change that “sometimes” to “often”. After years of using `exact` I finally stopped. It always felt that the wait was longer than going to the previous keyframe and rewatching the bit. Now if I could only find the perfect timing to go back, though.

  Alt+Right        sub-seek  1   # Go to next/previous sub (within demuxer-readahead-secs)
  Alt+d            sub-seek  1
  Alt+Left         sub-seek -1
  Alt+a            sub-seek -1

  demuxer-readahead-secs=120     # sub-seek only works within this cache
  demuxer-hysteresis-secs=60     # Fill cache only if lower than this; saves battery

Post by amiga386 » Sun, Aug 18, 2024, 5:30 PM UTC

opan wrote: post #322

latexr wrote: post #319

Earlier quoted context omitted.

> I even use it when an image I saved ends up as .html for some reason and then use the info screen to determine the real extension it should be so I can rename it If you’re on Linux on macOS, you’ll have access to the `file` command-line tool which can do it effectively. In a couple of lines of shell scripting you can even have it auto-change the extension. https://en.wikipedia.org/wiki/File_(command)

I had someone try to tell me this or some similar alternative method once, but for this particular use-case my method seemed faster. Usually I'm viewing the dir with the file in ranger, hit r (shortcut for :open_with ), type mpv, enter, I in mpv for info, q to quit, a in ranger to rename the file with old name pretyped in. It's a pretty smooth workflow. Assuming I start from the same place in ranger I have to press c…

    #!/bin/bash
    # Usage: fix-extensions 
    # Renames the files to consistent file extensions based on content

    for file in "$@"; do
        [ -f "$file" ] || continue
        dir=$(dirname "$file")
        name=$(basename "$file")
        prefix="${name%.*}"
        ext="${name##*.}"

        magic=$(file -b "$file")
        newext=""
        case "$magic" in
        *"Apple QuickTime movie"*)        newext=mov;;
        "ISO Media, Apple iTunes Video"*) newext=mp4;;
        "ISO Media, MP4"*)                newext=mp4;;
        "ISO Media, MPEG-4 (.MP4)"*)      newext=mp4;;
        "Macromedia Flash data"*)         newext=swf;;
        "Macromedia Flash Video")         newext=flv;;
        "Matroska data")                  newext=mkv;;
        "Microsoft ASF"*)                 newext=wmv;;
        "MPEG sequence"*)                 newext=mpeg;;
        "Ogg data, OGM video"*)           newext=ogm;;
        "RealMedia file")                 newext=rm;;
        "RIFF "*" data, AVI,"*)           newext=avi;;
        "WebM")                           newext=webm;;
        esac

        if [ -z "$newext" ]; then
            echo >&2 "$file: not renaming, unknown extension for type '$magic'"
        elif [ "$ext" != "$newext" ]; then
            mv -v "$file" "$dir/$prefix.$newext"
        fi
    done