- May 01, 2024
-
-
- Apr 30, 2024
-
-
The private control has been moved to struct vlc_input_es_out which is an internal interface used by the input only, removing the need for the modules using the vlc_es_out interface to know about this.
-
Every clients have switched to using the private control callback from the vlc_input_es_out interface.
-
Every clients are now using either the vlc_input_es_out priv_control callback or they fallback to the es_out_t implementation if not filled. Moving the call to vlc_input_es_out will allow removing the private control from the es_out_t callback interface.
-
Every clients are now using either the vlc_input_es_out priv_control callback or they fallback to the es_out_t implementation if not filled. Moving the call to vlc_input_es_out will allow removing the private control from the es_out_t callback interface.
-
Every clients are now using either the vlc_input_es_out priv_control callback or they fallback to the es_out_t implementation if not filled. Moving the call to vlc_input_es_out will allow removing the private control from the es_out_t callback interface.
-
Now that every private es_out_t clients are using the struct vlc_input_es_out type, we can remove those macros safely.
-
input_EsOutTimeshiftNew() is now receiving a vlc_input_es_out instance to initialize the next hop in the es_out_t chain, so we can use this internally. This will allow calling the vlc_input_es_out private control instead of the es_out_t one.
-
Now that every input es_out_t implementations are inheriting vlc_input_es_out and every locations in the input are storing vlc_input_es_out directly, we can forward the downclass to the es_out_timeshift vlc_input_es_out implementation so that it can forward the private controls to the next vlc_input_es_out.
-
Thanks to the compability macros, we didn't need to modify the client code, and now that every clients are using vlc_input_es_out, we can downcast directly when needed.
-
Setup compatibility path to redirect to vlc_input_es_out private control instead of using the es_out_t private control when it's available.
-
Setup compatibility path to redirect to vlc_input_es_out private control instead of using the es_out_t private control when it's available.
-
input_EsOutSourceNew() is now receiving a vlc_input_es_out instance to initialize the next hop in the es_out_t chain, so we can use this internally. This will allow calling the vlc_input_es_out private control instead of the es_out_t one.
-
Now that every input es_out_t implementations are inheriting vlc_input_es_out and every locations in the input are storing vlc_input_es_out directly, we can forward the downclass to the es_out_source vlc_input_es_out implementation so that it can forward the private controls to the next vlc_input_es_out.
-
Make input_source_t store a vlc_input_es_out directly instead of an es_out_t. Indeed, an input_source_t is always linked to an es_out_t which is able to execute private controls for the playback.
-
Now that the es_out is an instance of vlc_input_es_out, we want to use the new interface as much as possible. The es_out private callbacks will handle both types so the transition can be partial in this commit to keep it minial aand mostly change the stored variables and the other calls.
-
This commit provides temporary compatibility macros to be able to change the type used for the first parameter in each of the clients of the private control API. They will be removed in later commits.
-
Now that every clients are inheriting vlc_input_es_out, we can output a vlc_input_es_out object to the core input directly. For now, the input still upcasts to es_out_t to avoid modifying the whole file in this commit.
-
No functional changes for now, the ops are set to NULL. This will allow to move the private control callback out of the es_out_t interface.
-
No functional changes for now, the ops are set to NULL. This will allow to move the private control callback out of the es_out_t interface.
-
No functional changes for now, the ops are set to NULL. This will allow to move the private control callback out of the es_out_t interface.
-
The structure will replace the previous priv_control that was implemented mostly by input-specific es_out, and will allow to implement more controls through operations instead, when suited.
-
Switching to a designated initializer structure means that optional callbacks don't need to be specified during initialization. This simplify a lot adding and removing callbacks to the virtual tables since we don't need to modify every files using the table at the same time as changing the table itself.
-
Switching to a zero-initialized structure provides the same behaviour as designated initializers in C code, ie. optional callbacks don't need to be specified during initialization. This simplify a lot adding and removing callbacks to the virtual tables since we don't need to modify every files using the table at the same time as changing the table itself.
-
Switching to a zero-initialized structure provides the same behaviour as designated initializers in C code, ie. optional callbacks don't need to be specified during initialization. This simplify a lot adding and removing callbacks to the virtual tables since we don't need to modify every files using the table at the same time as changing the table itself.
-
-
characters as `?` or `&` remained encoded and were causing access issue for artwork from services discoveries such as jamendo
-
most network models are loaded asynchronously, if the cache is built right after the model initialisation, data isn't loaded yet and the first model version is built on an empty list, which can lead to a transitory state where the view assumes it's not loading anymore and that no data is present
-
* contentitem implementation aligns with IconToolButton * animation fades to transparent red rather than transparent black * animation will fade in then fade out
-
property requirement of IconToolButton changed since d6b6ac32
-
-
- Apr 29, 2024
-
-
Ignore qt6-assets_qrc.cpp, qt6-qml_qrc.cpp, qt6-shaders_qrc.cpp, qt6-windows_qrc.cpp.
-
We don't use the test with static Qt, and Q_INIT_RESOURCE should not be necessary with dynamically linked Qt.
-
- Split vlc.qrc into assets.qrc and qml.qrc. - Re-generate resource when qml files are updated. - Initialize all resources explicitly. - Split resource initialization in Makefile. - Include qml files in resources, regardless if qmlcachegen is used or not.
-
-
-
-
- Apr 28, 2024
-
-
It is (at least) part of FFmpeg 6.1 and can be used as DXVA/QSV output.
-
-
-
