Talk:VLC media player
I was just wondering if the addition of a corrupted audio fix (on my box Dvd audio was corrupted as the default playback was a mono source. The stereo channels being played through mono warped the audio) would be beneficial. I'm not sure if I was the only one with this problem —This unsigned comment is by Runny6play (talk) 22:13, 14 October 2012. Please sign your posts with ~~~~!
I have download probably all WSZ (almost 2000) and WAL (almost 900) skins from ru.winamp.com. I haven't direct URLs to them but I have uploaded all of them on one of my "empty" website. It is not as I understand can be used and installed same way as fonts, by copying in the "media player folder". The only way that I see is to download into "/usr/share/skins" or "/usr/share/skins/WSZ" or "/usr/share/skins/Winamp/wsz" folder. But to download all at the same time is also not good idea or is it (with one PKGBUILD file)? May be create a script that first will list only all available skins, download desired into some of the "/usr/share/skins/*" and then add option to create only symlinks to them in the chosen folder. There are still many media players that supports Winamp skins, including VLC. Andy Crowd - 蔡依林 13:51, 9 April 2016 (UTC)
- About creating an Aur package to include them all: I don't know under which license the skins are published at winamp, but it may be not possible/allowed to download/republish them via another site in one package.
- Additionally, having ~3000 skins installed when you only use one at a time seems excessive and not really Arch style. I think most Arch users prefer to customize their desktop/apps, i.e. make a choice before and then install the skin (or a few) that match their desktop best.
- Those who do probably prefer sites like deviantart to share creations. You also get wsz skins there for example:  Following that approach: To choose a skin, it seems preferable to browse them online, decide and download the individual ones.
- So, if you want to share that knowledge, you might help other users more by making a subsection under VLC_media_player#Skins to give the necessary hints to browse skins from different sites, download and install them for vlc. Maybe, if it can be helped with an Aur package, you want to write one which wraps the curl download to automate the download/install, e.g. taking a command line argument
wsz-skin-install url to download the wsz/wal skin file to install. Not sure how much such helps, that depends on how easy it can be used to download/install individual skins from different sources. Maybe it is faster to do manually once you have decided for one and using an Aur package makes more sense if you change them a lot.
- --Indigo (talk) 11:27, 15 April 2016 (UTC)
- Thanks for advice. To publish so many skins as I have will take a very long time to upload one by one. The winamp website will be closed soon and many skins will go into history, that's why I downloaded them and want to share. Many websites want keep users come because of making money on advertisement, but I will ask some of them about this idea, to provide "easy" access to Skins database/list/urls but will do it late. Even on torrent websites is relatively hard to find big collections with winamp skins.
- I have looked for licenses in *.wsz files and only few contains them but almost every of them contains readme.txt/rtf. Then the *.wsz list must contain additional information, such as availability of readme and license files. The tool can be used to preview desired within script,wsz-skin-install peview skin1,skin2... , the filename used for preview is "main.bmp"(you see it on websites as preview) and is part of *.wsz that makes it easy to "scroll" through skins. People are often looking for skins in categories or searching by names, script can only search by name. The readme files can be available online as an image as a small protection against spam bots.
- Andy Crowd - 蔡依林 18:23, 16 April 2016 (UTC)
I just added a section on streaming to chromecast devices. On my system, I just had to install
hosts line in the
/etc/nsswitch.conf file may be a necessary prerequisite. I already had that done as I use . Can someone drop a line here if they can't get chromecast streaming working right out of the box by just installing this additional package? I'll happily add that bit in (unless of course, if you beat me to it!). Thanks! Karthik Periagaram (talk) 03:54, 11 March 2018 (UTC)
How to compile VLC 3.0.3 tarball from scratch
I'm trying to report a crash to VLC, but compilation fails:
./configure CFLAGS="-g" CXXFLAGS="-g" --enable-debug && make […] CC codec/libx264_plugin_la-x264.lo In file included from ../include/vlc_fixups.h:31, from ../config.h:907, from codec/x264.c:29: /usr/include/features.h:381:4: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp] # warning _FORTIFY_SOURCE requires compiling with optimization (-O) ^~~~~~~ codec/x264.c: In function ‘Open’: codec/x264.c:849:26: error: ‘x264_bit_depth’ undeclared (first use in this function); did you mean ‘x264_picture_t’? const int mask = x264_bit_depth > 8 ? X264_CSP_HIGH_DEPTH : 0; ^~~~~~~~~~~~~~ x264_picture_t codec/x264.c:849:26: note: each undeclared identifier is reported only once for each function it appears in
There doesn't seem to be an x264 library package:
$ pacman --sync --search x264 extra/x264 2:155.r0a84d986-2 [installed] Open Source H264/AVC video encoder
How do I get past this step? I've already installed all the build dependencies of the vlc-git AUR package.