The VideoLAN Forums

Updated VLC player from V2.0.8 to 2.1.1 this morning and found the Video Snapshot file prefix commands $N-$T- doesnot work anymore. Instead to have the filename & time of the video as the prefix, the prefix is just showing $N-$T-(and the sequential number). Is there a fix to this ?

Thanks

I am having the same issue as well. VLC 2.1.1 Win7 Ultimate x64.
Refer to https://forum.videolan.org/viewtopic.php?f=7&t=103952

still no bugfix?

Did you file a bugreport?

I’m finding that it works sometimes and doesn’t work sometimes. I suspect it might have something to do with the type of the file being played. For example, DVDs never seem to work.

I’ll try to do a test with different types and different variables to see if I can figure out what might be wrong.

It looks like this issue has been going round and round on Windows for over four years. I certainly understand the pains of dealing with embedded metadata of various media formats, but would it be so hard to at least give us ONE token that resolves to the physical file name?

Just make $W (for Windows) resolve to the physical file name (no path) of the current file playing with extension, and $w to the file without the extension. I'm not a rocket scientist, but I believe it should be possible for VLC to figure out the name of the file it's playing?

Did you file a bugreport?

There is a bug report for this:
https://trac.videolan.org/vlc/ticket/9938

Can it be elevated? This is the most useful feature of VLC, and one I need weekly.

I am also waiting for this bug to get fixed, any idea when that will be?

Or do we have to go back to 2.0.8, where this feature still works?

As the bug report says, this was fixed several months ago already.

Well, I've got 2.1.5 running here and this bug is still there.

So if it's fixed, why hasn't the fix been implemented?

I second that - it's not fixed.

VLC 2.1.5

Windows 7 Ultimate x64

Config is Not being converted into correct string.

The bug report does say 2.2.0...

The bug report does say 2.2.0...

That's what I suspected, but did not have time to check. Thanks.

2.2.0 (stable) hasn't been released yet, so from an user point of view it is not fixed. And why couldn't the fix been implemented in the recently released 2.1.5?

2.2.0 (stable) hasn't been released yet, so from an user point of view it is not fixed. And why couldn't the fix been implemented in the recently released 2.1.5?

Because devs have plenty on their plate to deal with on every release LOL

I poked around and found this page with nightly builds. I checked the latest 3.0.0 build (9/6) and the latest 2.2.0 build (8/12). Neither were stable (crashed after awhile), but both addressed this problem of naming the snapshots properly with the file name using $N.