aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
...
* stream_dvdnav: more debugging outputGravatar wm42014-07-06
|
* demux: fix a corner case related to demux_discGravatar wm42014-07-06
| | | | | | It can happen that demux_fill_buffer() adds more than 1 packet, and then the packets would add up. Affects demux_disc.c only (nothing else uses this function).
* dvd: fix first subtitle with delayed subtitle streamsGravatar wm42014-07-06
| | | | | | This was accidentally broken with moving the DVD code to demux_disc.c. Also remove an abort() call meant for debugging.
* stream: remove now unused STREAM_CTRL_GET_START_TIMEGravatar wm42014-07-06
| | | | demux_disc.c takes care of this now.
* demux: minor simplificationGravatar wm42014-07-06
| | | | Oops, should have been part of commit 37085788.
* ao_pulse: set icon nameGravatar atomnuker2014-07-05
| | | | Will replace the generic XDG video icon inherited from media role.
* vf_vapoursynth: reset error state on seekingGravatar wm42014-07-05
| | | | | | | | | | | | When seeking, we violently destroy the filter, because vapoursynth has no proper API for terminating a video with unknown frame count. This looks like an error to vapoursynth, and the error is returned via the frame callbacks. The bug is that we remember this error state across reinitialization, so on the first filter call after reinitialization, we thought filtering the current frame failed. This caused a shift by 1 frame on each seek. CC: @mpv-player/stable
* build: allow compilation without any atomicsGravatar wm42014-07-05
| | | | | | | | | | | | | | | | | | | Not all compilers on all platforms have atomics available (even if they could, technically speaking). We don't use atomics that much, only the following things rely on it: 1. the audio pull code, and all audio outputs using it 2. updating global msg levels 3. reading log messages through the client API Just disable 1. and 3. if atomics are not available. For 2., using fake- atomics isn't too bad; at worst, message levels won't properly update under certain situations (but most likely, it will work just fine). This means if atomics are not available, the client API function mpv_request_log_messages() will do nothing. CC: @mpv-player/stable
* options: remove bogus replacement message for --fstypeGravatar wm42014-07-05
| | | | CC: @mpv-player/stable
* options: add --autosub-match to option replacement listGravatar wm42014-07-05
| | | | CC: @mpv-player/stable
* player: don't use stream position as fallback for percent-posGravatar wm42014-07-05
| | | | | | | | This should be unneeded, and the packet position is already sufficient for this case. Accessing the stream position directly is going to be a problem when the stream is accessed from another thread later.
* tv: move demuxer parts to separate fileGravatar wm42014-07-05
| | | | | Now all demuxer implementations (at least demuxer API-wise) are in the demux directory.
* demux: minor simplification to internal APIGravatar wm42014-07-05
| | | | Also some other unrelated minor changes.
* dvd: move angle switching codeGravatar wm42014-07-05
| | | | | No need to provide a "nice" API for it; just do this stuff directly in the command code.
* dvd: flush buffers properly on seekGravatar wm42014-07-05
| | | | | | | | | | | Suggested by tholin on github issue #882. This is not entirely clean, but the fields we're accessing might be considered internal to libavformat. On the other hand, existence of the fields is guaranteed by the ABI, and nothing in the libavformat doxygen suggestes they're not allowed to be accessed. CC: @mpv-player/stable
* dvd, bluray, cdda: add demux_disc containing all related hacksGravatar wm42014-07-05
| | | | | | | | | | | | DVD and Bluray (and to some extent cdda) require awful hacks all over the codebase to make them work. The main reason is that they act like container, but are entirely implemented on the stream layer. The raw mpeg data resulting from these streams must be "extended" with the container-like metadata transported via STREAM_CTRLs. The result were hacks all over demux.c and some higher-level parts. Add a "disc" pseudo-demuxer, and move all these hacks and special-cases to it.
* discnav: fix a commentGravatar wm42014-07-05
|
* demux: set filepos field when dequeuing a packetGravatar wm42014-07-05
| | | | Otherwise the position can be too far ahead.
* demux: cosmetics: minimize codeGravatar wm42014-07-05
|
* demux: make start time a simple fieldGravatar wm42014-07-05
| | | | Simpler, especially for later changes.
* demux, stream: change metadata notificationGravatar wm42014-07-05
| | | | | | | | | | | | (Again.) This time, we simply make it event-based, as it should be. This is done for both demuxer metadata and stream metadata. For some ogg-over-icy streams, 2 updates are reported on stream start. This is because libavformat reports an update right on start, while including the same info in the "static" metadata. I don't know if that's a bug or a feature.
* demux: make replaygain per-trackGravatar wm42014-07-05
| | | | | | It's unlikely that files with multiple audio tracks and with replaygain actually happen, but this change might help avoid minor corner cases with later changes.
* demux: move packet functions to a separate source fileGravatar wm42014-07-05
|
* demux: move packet list functionsGravatar wm42014-07-05
| | | | Move them to the only place where they are used, demux_subreader.c.
* demux_lavf: for now, ignore the new libavformat image demuxersGravatar wm42014-07-05
| | | | | | | | | | | | Recently, libavformat added demuxers to open image files like normal demuxers. This is a good thing, but for now they interfere with the operation of demux_mf. Add them to the blacklist until there is a proper solution. (The list doesn't contain _all_ recognized image formats, just those that might interfere with demux_mf.) CC: @mpv-player/stable
* demux_lavf: support OTF fonts in MatroskaGravatar wm42014-07-05
| | | | Apparently it's FFmpeg only.
* demux_lavf: don't dump transport stream programsGravatar wm42014-07-05
| | | | Probably useless.
* demux_lavf: cleanup debug outputGravatar wm42014-07-05
| | | | Remove unnecessary prefix, remove some messages.
* demux_lavf: fix read_seek return valueGravatar wm42014-07-05
| | | | | | | This returned a stream error value directly to libavformat, which can't make sense. For example STREAM_ERROR (0) means success in libavformat error codes. (The meaning of the libavformat read_seek return value is underdocumented too.)
* demux_mkv: cosmeticsGravatar wm42014-07-05
|
* DOCS, client API: add mpv release versionsGravatar wm42014-07-05
| | | | | | | | The intention is to make it obvious which mpv releases certain changes will apply to. Also attempt to fix RST formatting of the list. This is not very proper, but probably good enough.
* Merge pull request #909 from Nyx0uf/patch-1Gravatar Stefano Pigozzi2014-07-05
|\ | | | | OS X bundle: Add more imported UTI
| * OS X bundle: Add more imported UTIGravatar Nyx0uf2014-07-04
|/ | | Not that there are widely used formats, but it will allow to play them directly from the Finder.
* stream_dvdnav: check the length of all titles with dvdnav://longestGravatar tholin2014-07-04
| | | | | | | | The last title was ignored before. CC: @mpv-player/stable Signed-off-by: wm4 <wm4@nowhere>
* stream_dvdnav: free pointer to priv->filename on closeGravatar tholin2014-07-04
| | | | | | CC: @mpv-player/stable Signed-off-by: wm4 <wm4@nowhere>
* stream_dvdnav: make sure seeking bounds are within rangeGravatar tholin2014-07-04
| | | | | | | | libdvdnav returns an error is the seek position is out of range. CC: @mpv-player/stable Signed-off-by: wm4 <wm4@nowhere>
* DOCS/client_api_examples: add a Qt exampleGravatar wm42014-07-04
| | | | | This is pretty dumb and extremely basic. The main purpose is demonstrating how to integrate mpv into the Qt GUI thread.
* client API: allow calling mpv_terminate_destroy(NULL)Gravatar wm42014-07-04
| | | | | | This is an oversight and a bug. CC: @mpv-player/stable
* x11: avoid obscure behavior when --wid is partially garbageGravatar wm42014-07-04
| | | | | | | | | | | Cast away the "extra" bits (since apparently Window/XID is always 32 bit unsigned). This is not striclty needed, because you're not supposed to pass garbage to --wid, just because the upper bits are possibly not interpreted. But if you do so, this change increases consistency in behavior and removes a strange behavior that was thought to be a bug. Also see github issue #906.
* ao_coreaudio: report hardware latency to ao_read_dataGravatar Stefano Pigozzi2014-07-03
| | | | | Commit a6a4cd2c88 added reporting of playout latency, this commit also adds support for reporting hardware and constant audio unit latency.
* TOOLS/zsh.pl: complete URL schemes based on --list-protocolsGravatar Alessandro Ghedini2014-07-03
|
* TOOLS/zsh.pl: sort options in reverse order by lengthGravatar Alessandro Ghedini2014-07-03
| | | | | This stops options that are prefixes of other options from blocking completion of values for the longer ones.
* TOOLS/zsh.pl: untabifyGravatar Philip Sequeira2014-07-03
|
* TOOLS/zsh.pl: fix _arguments lineGravatar Philip Sequeira2014-07-03
| | | | | | | | | Don't use _x_arguments, as we don't support X arguments. Get rid of -s, because we don't support multiple single-letter options in one argument. Add -S, because we ignore options after "--".
* TOOLS/zsh.pl: don't consume extra argumentsGravatar Philip Sequeira2014-07-03
| | | | | | | | | | | | Completion now uses "--opt=value" instead of "--opt value". Once the user presses space and starts a new argument, the option just completed is out of the picture, whether or not it was given an argument. This handles options with no arguments or optional arguments much better; previously, completing such an option would effectively disable completion for the next argument. Custom completed options such as "--ao" and friends will no longer claim to consume an extra argument.
* TOOLS/zsh.pl: escape all colons in option descriptionsGravatar Philip Sequeira2014-07-03
|
* command: include new "playback-time" property in update mechanismGravatar wm42014-07-03
|
* DOCS: add a file listing API changes for the client APIGravatar wm42014-07-03
|
* manpage: reflect new coreaudio changesGravatar Stefano Pigozzi2014-07-02
|
* ao_coreaudio: report latency more correctlyGravatar Stefano Pigozzi2014-07-02
| | | | | | | | | | Previous code was completly wrong. This still doesn't report the device latency, but we report the buffer latency (as before the AO refactoring) and the AudioUnit's latency (this is a new 'feature'). Apparently we can also report the device actual latency and we should also calculate the actual sample rate of the audio device instead of using the nominal sample rate, but I'll leave this for a later commit.