- Sep 28, 2024
-
-
michel promonet authored -
fixes new indicator not visible anymore fix regression from cbc63a0a since the commit, content item is raised you can't put element there anymore
-
- Sep 27, 2024
-
-
It was only used by synchro.c.
-
It was a libmpeg2 specific option, not used anymore.
-
It was only used by libmpeg2.
-
cf. previous commit.
-
Lower priority than avcodec since VLC 3.0, so never used by default since then.
-
cf. previous commit.
-
Lower priority than avcodec since VLC 3.0, so never used by default since then.
-
cf. previous commit.
-
Lower priority than avcodec since VLC 3.0, so never used by default since then.
-
Use newest version without a52 forced build.
-
Binding on `state` property was needed to avoid activating the visual transition when component loads fix: #28804
-
when a video becomes embed the playlist is hidden, the playlist visibility state is kept but the playlist was hidden, clicking the playlist button was toggling the playlist visiblity. As a result, if the playlist was visible, it required the user to click twice to show the playlist. Now when the button is clicked with video embed, it will visually toggle the playlist and update the playlist "visible" value to the visual state.
-
fix: #28803
-
Undefined symbols for architecture arm64: "_CACurrentMediaTime", referenced from: -[VLCPictureInPictureController pictureInPictureControllerTimeRangeForPlayback:] in libpictureinpicturecontroller_plugin_la-VLCPictureInPictureController.o "_CMTimeGetSeconds", referenced from: -[VLCPictureInPictureController pictureInPictureController:skipByInterval:completionHandler:] in libpictureinpicturecontroller_plugin_la-VLCPictureInPictureController.o "_CMTimeMakeWithSeconds", referenced from: -[VLCPictureInPictureController pictureInPictureControllerTimeRangeForPlayback:] in libpictureinpicturecontroller_plugin_la-VLCPictureInPictureController.o "_CMTimeRangeMake", referenced from: -[VLCPictureInPictureController pictureInPictureControllerTimeRangeForPlayback:] in libpictureinpicturecontroller_plugin_la-VLCPictureInPictureController.o "_kCMTimeNegativeInfinity", referenced from: -[VLCPictureInPictureController pictureInPictureControllerTimeRangeForPlayback:] in libpictureinpicturecontroller_plugin_la-VLCPictureInPictureController.o "_kCMTimePositiveInfinity", referenced from: -[VLCPictureInPictureController pictureInPictureControllerTimeRangeForPlayback:] in libpictureinpicturecontroller_plugin_la-VLCPictureInPictureController.o -
Undefined symbols for architecture arm64: "_CGRectZero", referenced from: -[VLCVideoUIView viewContainerBounds] in libuiview_window_plugin_la-VLCVideoUIView.o -
Steve Lhomme authored
This reverts commit 94db2f10. These patches seems to break DVD playback with gcc on Linux. It has not been merged upstream anyway. For Windows LLVM builds !2400 is still necessary. Signed-off-by:
Steve Lhomme <robux4@ycbcr.xyz>
-
Current pts/dts are bogus (pts < dts). It should not depend on frame rate, but only source pictures.
-
Qt 5.15 used to cause `QDragEnterEvent` to be posted before `QDragLeaveEvent` is posted. The ordering seems to be fixed with Qt 6. Qt 6.2 and 6.7 are checked.
-
Now that the interfaces are not run from the main thread directly, it's possible to dispatch the QApplication startup and UI creation to the main thread directly on Darwin. It matches the behaviour of the interface on other platform that Darwin, where a thread is created to handle the interface, except that the thread is already existing as the main thread for Darwin. It means that there won't need any specific code (except for Thread() startup) to handle the specificities of the Qt interface startup on Darwin anymore. Ticket #27103 showed issues when leaving the interface with the medialibrary, because the path releasing the medialibrary was not taken correctly, but other issues could arise, including deadlocks. Fixes #27103
-
Interfaces from libvlc were started from the main thread directly. But UI inserting their own event loop inside the main runloop like Qt were taking over the interface insertion. It was preventing other interfaces to load correctly, required dedicated code to handle the startup in the Qt interface and it was not possible to exit the interface correctly. By moving the creation of the interfaces in a dedicated thread, we can ensure all UI are created and destroyed correctly, but the macosx interface must now dispatch its own creation into the main thread to match Cocoa requirement on main thread usage for UI components. Note that libvlc_new itself must be moved to the intf_queue given that it starts additional extraintf. The macosx interface must now start its own NSApp inside the main loop, via a dispatch call, which simplify the main loop into running the default main loop.
-
VLA are not compatible with blocks, and error handling is pretty simple here, so there's no reason not to use dynamic allocation instead.
-
- Sep 26, 2024
-
-
Steve Lhomme authored
Includes our UWP patch and some CVE fixes from 3.7.4 and 3.7.5.
-
refs #28799
-
- Sep 25, 2024
-
-
-
-
-
-
-
libx265 will bail out when hitting the limit x265 [error]: frameNumThreads (--frame-threads) must be [0 .. X265_MAX_FRAME_THREADS)
-
- Sep 24, 2024
-
-
Steve Lhomme authored
We can return that directly.
-
Steve Lhomme authored
It doesn't seem to be using the placement values, which is wrong.
-
Steve Lhomme authored
-
Steve Lhomme authored
Vertically swapping the position of the video keeps the place "height". The vertical position use the inverted position of the bottom position rather than the top position of the video.
-
Steve Lhomme authored
-
Steve Lhomme authored
ResetPictures and Control are always called in the vout thread, so they are always in sync.
-
Steve Lhomme authored
-
Steve Lhomme authored
Display, ResetPictures and Control are always called in the vout thread, so they are always in sync.
-
Steve Lhomme authored
Prepare and CreateBuffers are always called in the vout thread, so they are always in sync. The original placement is set when the module is opened.
-
