
Paul Rourke
6 discussion posts
Is it possible to use wild cards in the command line properties in triggers? I want to set up two triggers one that works on an .mp3 extension and one that works on an mp4 extension, eg:- {--started-from-file "*.mp3"}.
This is to allow VLC to behave differently when opening video or audio files.

Paul Rourke
6 discussion posts
Thank you. I will await the reply with interest.

Paul Rourke
6 discussion posts
I tried that but vlc does not show the file extensionfor mp3's. When I copy the window text it looks like this for an mp3 - "herbie williams - lover who loves you not - VLC media player". For mp4 files it does actually display the extension. Like this -"double uni knot.mp4 - VLC media player". I have had a look through vlc's settings but cannot get the extension up for mp3 files. Very odd.

Paul Rourke
6 discussion posts
This is what am I am already doing as a workaround. I already have several vlc shortcuts/triggers that run security and webcams so I have re-ordered them to make it work as I want. Wildcards would have been easier though!. Thanks for the help.

Paul Rourke
6 discussion posts
Update. After messing around with tags I now understand why MP3's and MP4's appear to show different information in the vlc window title. I'm running the most recent 64 bit version of VLC and it appears that if the tags for "artist" and "title" are populated in the currently playing file, then the window displays {"artist" - "title" VLC media player} as the window title without showing the file extension. If however the same tags are blank then the window defaults to the full filename and displays that instead as {full filename.ext VLC media player}. In order to make this workaround function correctly it is neccessary to tweak the tags in the media files that you are playing. Hope this helps anyone else trying to do the same as am.