Commit e8ca8557 authored by Martin Finkel's avatar Martin Finkel

docs: small updates

parent b3564742
......@@ -18,7 +18,7 @@ Some advanced customizations and features are only accessible through LibVLC opt
> Note: Some options only work with the LibVLC constructor and some options only work with the `media.AddOption` API.
The list of such LibVLC string options can be found here https://wiki.videolan.org/VLC_command-line_help/
### The list of such LibVLC string options can be found here https://wiki.videolan.org/VLC_command-line_help/
## LibVLC Versioning
......
......@@ -2,6 +2,8 @@
[Back](home.md)
In addition to [official samples](https://github.com/mfkl/libvlcsharp-samples), you may explore the following opensource projects made by GitHub users:
## TwitchBot
Custom C# chat bot for Twitch TV
......
......@@ -17,7 +17,6 @@
- Cast button
- Errors display
- Lifecycle management
- Do an unique MediaTransportControls.xaml template
- Buttons content dependency properties
- Compact mode
- Keep screen on
......
......@@ -17,7 +17,7 @@ VideoLAN never created an official .NET libvlc binding so some dotnet folks crea
The first commit by [ZeBobo5](https://github.com/ZeBobo5) of [Vlc.DotNet](https://github.com/ZeBobo5/Vlc.DotNet) dates back to march 2009, though it was not the first version.
Later, [Jérémy](https://github.com/jeremyVignelles) became the de factor maintainer of Vlc.DotNet as ZeBobo5 had less time to spend on the project.
Later, [Jérémy](https://github.com/jeremyVignelles) became the de facto maintainer of Vlc.DotNet as ZeBobo5 had less time to spend on the project.
Mid 2018, VideoLAN started looking into .NET libvlc bindings. It was decided to create a new project, [LibVLCSharp](https://code.videolan.org/videolan/LibVLCSharp), instead of starting from Vlc.DotNet because we wanted to have a similar public API than [libvlcpp](https://code.videolan.org/videolan/libvlcpp) and design it to be crossplatform from scratch.
......
......@@ -4,16 +4,18 @@ A good first step is to try to identify whether your issue is originating from t
## Debugging with libvlc logs
To better understand what might be going on inside libvlc during playback in your application, verbose logs are helpful. To enable them, use this argument when creating your `LibVLC` object:
To better understand what might be going on inside libvlc during playback in your application, **verbose** libvlc logs are helpful. To enable them, use this argument when creating your `LibVLC` object:
```csharp
new LibVLC("--verbose=2");
```
They should be printed to your Console, if you are building a Console project, or to the Visual Studio Output Window. Alternatively, you may subscribe to the log messages in your code using `libvlc.Log += ...`
## Try your code on multiple devices and platforms
Some issues are platform specific, some are even device specific, or driver specific. Luckily LibVLCSharp runs on many platforms, so testing on various OSes is one way to try and pinpoint the original issue.
Some issues are platform specific, some are even device specific, or driver specific. Luckily LibVLCSharp runs on many platforms, so testing on various OSes is one way to try and pinpoint the original cause of the issue.
## Reproduce in official VLC apps, desktop and mobile
Enable debug logs in the official VLC apps and compare the logs with those from your application.
\ No newline at end of file
Enable debug logs in the official VLC apps and compare the logs with those from your application is yet another way to troubleshoot a problem.
\ No newline at end of file
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment