You most probably forgot -S in front of audio_dir.
I just copied and pasted this command on Linux with vlc1.1.7. It works fine. On Windows, it also should work (maybe { needs to be escaped ?)
Those entries are not yet implemented by default with the skins2 interface. Nevertheless, you can configure vlc to start them automatically and skins2 will display them together with Playlist and Media Library. Just run vlc for instance like : vlc -I skins -S audio_dir{longname=MyAudio},video_dir{lo...
Updated mine to the new features. Fullscreen controller works very well, no more artifacts on moving. Transparency and movement are smooth too. Tested on Win7 x64 with 1.2. nice to hear it works Btw: vlc.faster() and vlc.slower() broken? Can´t bring em to work, regardless of the version. Thanks for...
The skins2 interface doesn't use video-x and video-y.
All placements (window, video control, ..... ) are read from the theme.xml file. (attributes are x and y expressed in pixels).
Default values are (0,0) if not provided.
As of today, the skins2 interface does not manage multiple screens as far as fullscreen is concerned. This is not a bug per se, but a skins2 limitation.
Filling a bug does no harm, since it is a legitimate request.
weird indeed. I don't experience such a behavior on a large scale with WinXP and the latest 1.1.6 build, and I don't recall it not working on 1.1.5 You may come across a few alternative skins from the vlc website that have some problems (missing bitmaps, ....) but those are not that many, and proble...
There is indeed a limitation that could be worked out. As of today, a "window provider" is looked for with a whole set of initial parameters (x, y, width, height, is_standalone). Unfortunately, fullscreen is not passed at this level, but only in a subsequent call. This results in the inter...
The problem described in this thread was indeed a bit annoying and actually not very difficult to remedy. Starting with vlc1.2 (dev branch), a new attribute ' focus ' has just been added to a text control . It goes like this : - Default value is focus="true", which means that skins still b...
Catching mouse events over the video on Win32 is possible, but not an easy task. (both vlc1.1.5 and vlc1.2) VLC actually manages the video window in its own thread (with its own message queue). Therefore, the QT4 thread won't receive these events. The Win32 API provides "global hooks" to s...
Well, vlc1.2 is not yet out .... that gives time, I guess ! And the fullscreen controller transparency/fading-out is actually not so promising at least on WinXP : - fully functional with --vout wingdi (but who really uses it ?) - works weirdly with --vout directx - works wildly with --vout opengl So...
Hello, Here is a review of what has just been added in the dev branch regarding skins2 : - fullscreen controller : - it can now also be activated by mouse move - transparency and fading out are supported when the Window Manager supports it. - qt-opacity and qt-fs-opacity parameters are now recognize...
Oops ... I just discovered there are more than 4 actions available. One of them is 'dialogs.fileInfo()' that should help you (no more menus and submenus before accessing this info dialog box).
As for a dedicated hotkey, I'm afraid it is definitely not available as of today.
No, sorry, there are no such parameters at the command line to configure dialog boxes. And Skins designers long ago decided to expose only a subsets of menus/dialog boxes in the form of 4 actions (see previous post). I can see two things that can be only done at the dev level : - Extend the skins ap...
1)a Setting I am missing? No, the qt4 interface specific hotkeys (Ctrl-Something) are not available with skins. Only hotkeys managed by vlc core are available ( A for Aspect, C for Crop, ...). And Yes, this can be eligible as a new feature request. There are some alternatives to right-clicking to g...
Not sure I know the answer to your question, but I see two things that may be a problem .... - proper locking mechanism (first program) Since you're dealing with multiple threads, all threads accessing a common resource must lock it. Otherwise, your code is prone to crash (see code hereafter that hi...
On X11, special care must be taken with dealing with a multithreaded application (if several threads make calls to the underlying xlib library). A special function XInitThreads() must be called first things before any other call to xlib occurs. Here is a modified main.cpp. (tested successfully) /* l...