Page 1 of 1

"core generic error" failures opening media in C++ LibVLC app

Posted: 30 Jan 2017 22:20
by opensoar
Have some code to playback media into a memory buffer and works as expected on Windows. Trying to port to OSX and the same code is not working. Output looks like this:

Code: Select all

[00007fde98c15cd8] core generic error: option vmem-chroma does not exist [00007fde98c15cd8] core generic error: option vmem-width does not exist [00007fde98c15cd8] core generic error: option vmem-height does not exist ... [00007fde98f063d8] core generic error: option amem-channels does not exist [00007fde98f18f58] core audio output error: no suitable audio output module [00007fde98f17c78] core input error: open of `https://localhost/test/test.mp4' failed [00007fde98f17c78] core input error: Your input can't be opened [00007fde98f17c78] core input error: VLC is unable to open the MRL 'https://localhost/test/test.mp4'. Check the log for details.
I've tried copying include, libs and plugins folders from an installed and working VLC instance as well as a fresh download.

I point to the "plugins" folder in the C++ code and I think it's working because if I remove it, I get a "No plugins found! Check your VLC installation."

Is there a way to get more information about what's failing?

Re: "core generic error" failures opening media in C++ LibVLC app

Posted: 31 Jan 2017 17:34
by RĂ©mi Denis-Courmont
Looks like some necessary plugins are missing.

Re: "core generic error" failures opening media in C++ LibVLC app

Posted: 01 Feb 2017 17:31
by opensoar
The log output suggests it's finding and loading (I think from memory) 324 plugins so it's partially finding them at least.

My guess is that's it's something to do with @loader_path but copying folder to where I think it's looking for them doesn't help either.

I'll keep digging.

Re: "core generic error" failures opening media in C++ LibVLC app

Posted: 03 Feb 2017 01:00
by opensoar
my executable loads a dynamic library that is located in the main .app file here: /Contents/Resources/flassm/foo.dylib.

Along side foo.dylib in that folder is the plugins and lib folders directly from VLC.app Contents/MacOS folder.

I know almost nothing about macOS so I'm struggling to make sense of the @... paths - if I'm reading the docs correctly, they appear to be right.