[vlc-devel] [PATCH 00/14] Move VLM implementation to a module

Rémi Denis-Courmont remi at remlab.net
Fri Sep 18 17:41:37 CEST 2020


Le perjantaina 18. syyskuuta 2020, 12.23.42 EEST Denis Charmet a écrit :
> IMO I think the first step should be to evaluate what is actually used
> of VLM (in VLC's code and user base) to determine which features are
> used and for what and then triage which ones should be in the core and
> which ones could benefit to be in a module.

Right. You can probably group direct VLM usage in two sets:

1) Uses that actually need VLM:
  - stream output bridge and mosaic bridge,
  - multiple pipelines on macOS,
  - multiple pipelines served on the same HTTP or RTSP port.

2) Uses that don't really need VLM, mainly single pipeline (per process) 
running in the background or on a schedule (except on macOS as noted above).

And then you have indirect uses: VLM is the backend, but the VLC 4.0 player or 
playlist could advantageously be used instead - HTTP interface and GUIs.

As Pierre said, it seems unreasonable to remove VLM in VLC 4. We don't have 
alternatives for the first group yet. And even if we did, there should be a few 
years advance warnings. But I also don't think that we should promote VLM any 
longer as we finally have better alternatives for programmatic use in 
vlc_player_t and vlc_playlist_t (at plugin API level) or libvlc_media_player_t 
(at LibVLC level).

-- 
雷米‧德尼-库尔蒙
http://www.remlab.net/





More information about the vlc-devel mailing list