The VideoLAN Forums

From what I recall, this A-B repeat functionality has never been available for the skins2 interface module. And there is no easy way to work around this missing functionality as a skin developer.

You should be able to use animated images with both the 'Button' and the 'Checkbox' tags. Please copy/paste the code that is not working to help figure out what is wrong.

The designer has offsetted the bottom panel by 1 pixel vertically. So this extra line is part of the design. But, I suspect this was not intended. So I just corrected the theme.xml description to remove this line. You can download the corrected skin here : https://www.dropbox.com/s/gewgxce5qx2x4dg/A...

Which OS (Linux or Windows) do you use ? which version ?

Anyway, I guess this may be related to HiDPI which is not implemented by the skin engine.

To my knowledge, at the core level, vlc only supports next frame, not previous frame. So, no button available for this feature.

I have got a modified version of this skin with art enabled. You can get it via the dropbox link :
https://www.dropbox.com/s/ik6z4ofqagp38 ... 3.vlt?dl=0

All skins should work with vlc3.0 the way they used to work in previous version. I did notice that loading a skin may be a bit longer. That has to be investigated.

You mean video filter versus video splitter. The former applies video filters to a given video output. The latter splits the video output into multiple outputs. The clone filter falls in the category of video splitters. As for skins, I was a bit too optimistic. The latest vlc I just tested now force...

Hello, This is a problem. Skin developers choose whatever fonts (.ttf, .otf, ...) they like best. But, those files don't necessarily have entries for all languages. The default skin uses the default font for the main window. The file is FreeSans.ttf. It works for Japanese but not for Korean. An easy...

Hello, Technically, this should work. At the core level, you have the clone video filter that create multiple outputs of a given video. At the skin level, you can devise a skin with multiple video controls in multiple windows and place these windows on any monitor independently. Yet, there may be so...

Hi, I'm not sure what shrunk down means here. Actually, the video within skins are a lot what designers decided it to be. They can implement or not resizing, hiding, maximizing, fullscreen in a single window or multiple windows. As for key accelerators (the Ctrl-something that you find advertized in...

Can you give me an example on how to block the Qt module? There is no way to block the Qt module and still use the skin engine in the current version. But, as I said, it should be easy to write a patch that makes the Qt module optional and therefore allows to disable all popupmenus, key accelerator...

Well, actually the easiest way to meet these requirements is indeed to remove the dependance on the Qt module. The only reason why the Qt module is launched by the skin engine is to provide popup menus, key accelerators and dialog boxes (preferences, message log, ....). No Qt module and you just dis...

Most likely, no video frames were provisioned for this skin when it was designed. So the video part is just kept hidden in non-fullscreen mode. The easy way to work around this problem is launch vlc with the --no-embedded-video parameter, or uncheck the "Embedded video" checkbox in Prefere...

A patch has just been applied in the dev branch that fixes the issue. Tested successfully with Windows10. A nightly build can usually be downloaded the next day, but unfortunately, new nightly builds haven't been issued for the last few weeks .... The fix will be available with the vlc3.0.0 branch o...

This feature is not implemented in the skin engine.
Unlike fullscreen that now supports mulitple screens, maximising a window is still very basic and the main screen is hardcoded as being the targeted screen.
Yet, it should be easy to code this new feature, since it already exists for fullscreen.

No nomenclature. the only prerequisite is to ensure ids are unique throughout the project. Otherwise, from what I recall, the skin engine doesn't complain very much. At run time, a lookup will always return the first id available. Subsequent ids with the same value will just never be accessible. Odd...

<Bitmap id="player.vfd.png" file="wave/playani.png" alphacolor="#000000"> <SubBitmap id="play.vfd.png" x="0" y="0" height="40" width="151" nbframes="8" fps="2"/> </Bitmap> Another mistake, id Must al...

Oops ... In fact, I was referring to subbitmaps. if you have one single png file image, let's say the aforementioned 10x200 png file, then width and height are automatically computed. So you just have to write : <Bitmap id="play.vfd.png" file="wave/playani.png" nbframes="20&...

That how I understand it, Height divided by nbframes. Not sure how to construe this last sentence ! Let's take an example. Suppose your frame is a 10x10 square, you've got 20 frames and you play 2 frames per second, then you provide a 10 x 200 png image (frames stored vertically) and eventually you...

A fix has just been applied that fixes the issue described in this thread (tested successfully with Unity and Gnome3)

This fix will be available in the next version of the 2.2 branch.

The short answer would be to file a bug report (with thorough description of the Window Manager brand and version as you did here) The long answer is that, from an application perspective in a X11 environment, requesting full screen is done via the ICCCM standard. And, in last resort, the Window Man...

two problems seen #1: the only valid name for the skin description file is theme.xml (Persona4_Style.xml is not a valid name !) #2: check the slider with id="Unnamed Slider #33". The image cannot be set to "none" in this context. A valid image has to be provided. Otherwise, skins...

Yes, vlc2.2.1 is the official current release and it still have the bugs that you described. Only the upcoming vlc2.2.2 (not yet released) should fix these bugs. If you wish to test it, vlc2.2.2 is rebuilt every night and can be downloaded for instance here : http://nightlies.videolan.org/build/win3...

Hello, The skins you provided did show two issues. Both of them are bugs. First issue, a wrong video control may be selected when vlc.hasVout() is used in the condition expression for visibility. This bug was already present in vlc2.1. I guess that is why you removed the 'and' keyword before vlc.has...