LibVLC Skill

Workflow

1. Confirm whether the target is libvlc 3.x or 4.x, then choose APIs and bindings that match that version.
2. Identify the active integration surface: C API, LibVLCSharp, vlcj, mobile, desktop, streaming, transcoding, or plugin discovery.
3. Load libvlc-skill.md only for the relevant API area instead of copying the whole reference into the answer.
4. Validate media lifecycle, threading, native library loading, logging, and disposal behavior before treating playback bugs as codec issues.

Validate

• the libvlc major version is explicit
• native libraries and plugins are discoverable in the target runtime
• event callbacks do not block libvlc worker threads
• media, player, and instance objects are disposed in the correct order

Sections in the reference:

• §1 Architecture Overview — pipeline, object model, single-instance rule
• §2 Core Concepts — lifecycle, threading rules, event system, error handling, logging, plugin discovery
• §3 API Reference — instance, media, media player, media list, events, dialog, discoverer, renderer, VLM, tracklist, program, GPU rendering, A-B loop, picture API
• §4 Language Bindings — C, C#/LibVLCSharp, Python, Java/vlcj, Go, C++/libvlcpp
• §5 Common Workflows — playback, metadata, thumbnails, playlists, Chromecast, transcoding, streaming, recording, track selection, mosaic, mobile lifecycle
• §6 Platform Integration — Windows (Win32, WPF, WinForms, D3D11), macOS/iOS, Linux (GTK, wxWidgets), Qt, Android, Avalonia
• §7 Streaming & Transcoding — sout chains, protocols, Chromecast
• §8 Troubleshooting — deadlocks, no audio/video, memory leaks, common pitfalls
• §9 CLI Options
• §10 Deprecated APIs
• §13 Migration Guide (3.x → 4.x) — signature changes, removed APIs, new APIs, type changes

Related skills