Well, sure. But the thing is: If I could call VLC instead of having VLC call me, it would work (at least under Windows). The way things are now I'm going to have to search for a different solution; only a very small percentage of people who use my software use the VLC integration, but the majority o...
That's the only way to be 100% safe, but my experience is that you can catch almost any crash and at least shut down gracefully (or restart) and write some logging using try/catch. So that's what I would like to do here as well.
I've made a program that uses libVLC to receive and decode audio streams. Sometimes - depending on the stream format - libVLC crashes, usually when for example some packages have been losts. This only happens for certain codecs. My problem is that - because libVLC is calling my code, and not the oth...
I'm adding VLC output audio streaming (to a Shoutcast server for example) to my software. I'm already using VLC to receive input streams and that works fine. Output streaming works fine as well, except when something goes wrong. I've subscribed to libvlc_MediaPlayerEncounteredError events using libv...
I found something that might be useful for other people who run into this issue. If you're feeding VLC with audio through IMEM, and you call libvlc_media_player_stop, it will NOT return unless you return some data via IMEM. If (as would be logical) you just reply that you have 0 bytes of data availa...