- Feb 17, 2023
-
-
This is how it's enabled in the Platform SDK
-
The defines may already be set to 0/1 in the build environment.
-
- Feb 16, 2023
-
-
Fairly straightforward as libplacebo currently ignores most metadata fields and only cares about the OOTF (bezier anchors) and global scene brightness/average measurements.
-
The assert() calls are based on hard-coded guarantees in libavcodec.
-
Following the precedent set by the DoVi metadata, we encode this as an ancillary attached directly to the frame, since it contains frame-dynamic data. We make the decision to follow ATSC A/341 Amendment 2094-40 instead of the original SMPTE ST2094-40:2016 specification, because the latter includes a lot of extra metadata fields which the former intentionally leaves unused, and which are also unused in practice (both in implementation and in files). We can easily add them later should a need arise. Also, again following the precedent set by `vlc_video_dovi_metadata_t`, we encode AVRationals directly as `float`. This saves us from having to do another unnecessary conversion step in the actual usage site (e.g. the libplacebo vout) by allowing the use of `av_q2d` directly.
-
Tristan Matthews authoredNote that there is a slight change in behaviour here, before if i_read was 1 greater than a power of 2 (e.g., 257), it would evaluate to the *previous* previous power of 2 (e.g., 128). Now in those cases it will really be the previous power of 2 (e.g., 256).
-
-
-
- Feb 15, 2023
-
-
Enforce the restart of VideoToolbox when a data / codec error happens. Usually, it was triggering a fallback (typically on avcodec) every time an error happened within the played stream, which can happen when corrupting the input stream. It was done to protect the decoder against non-playable files for which the decoder would announce the support but would not be able to decode a single frame ever. VideoToolbox seems to behave correctly on those files now so we can make it a default.
-
-
Steve Lhomme authored
The Direct3D9SetupVertices() call needs the size of the raw texture. It is not the visible parameters when cropping. fixes #27632
-
Steve Lhomme authored
-
Fix a regression from edf50ce0 where sample rate wasn't set properly after the setting call was moven up. Fixes #27687
-
fixes #27826
-
Signed-off-by:Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by: -
Signed-off-by: -
macosx: Add method to VLCInputNodePathControl to clear path control items ahead of given path control item Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
macosx: Build needed path items for path contorl in VLCMediaSourceBaseDataSource rather than spoofing a URL Signed-off-by:
-
- Feb 14, 2023
-
-
This provides experimental support to play again all available video resolutions, by combining audio and video "adaptive" elementary streams using an input slave. Not in use by default; use at your own risks. Again, by allowing to select resolutions lower than 360p, this also provides mitigation against the throttling issue. Ref #10237, #27227
-
-
This extends the old &fmt=[itag] URL syntax that we still supported all along to force format selection, and allows choosing from "adaptive" elementary streams without knowledge of itag specifics and in accordance with normal resolution preferences. This also allows playing only the audio part of music videos and skipping the download of the video part entirely, greatly reducing bitrate and providing mitigation against the throttling issue. Ref #10237, #27227
-
Formats listed under that label are audio-only or video-only elementary streams, but offer choice encompassing the full array of supported resolutions, qualities and codecs; whereas classic multiplexed formats have long been dwindling down to only two formats now, 720p and 360p, or even 360p only for some content. For now, these "adaptive" formats are only used if explicitly requested by itag number. Ref #10237
-
-
This makes more sense and will simplify code flow.
-
Link to old Wikipedia page revision where itag parameter formats were actually still described.
-
-
-
All it achieves at the moment is wasting CPU time, slowing down playback startup, and distracting users with extraneous warnings. Ref #27227
-
-
