The VideoLAN Forums

VLC media player 1.1.9 is fine but Version 1.1.10 has a bug, it cannot open DVD folders on hard drive using Media > Open Disc...

1. Can anyone confirm?

2. Won't you *please* give us the option to make VLC media player remember the last folder opened so we don't have to Media > Open Disc... > Browse to the same folder every time we use VLC to open the same DVD folder.

1. I confirm (same message error appears, always related to my DVD device letter H: , no matter I indicate a Video_ts folder on any partition of the hard drive)
The message error is : "Your input can't be opened: VLC is unable to open the MRL 'dvd://H:\'. Check the log for details."

Not only "Media > Open Disc..." is affected by this issue, but also "Media > Advanced Open file > Disc" because they're both ways to open a Disc (or any Video_ts folder)

Ticking "delete cache / preferences" during 1.1.9 uninstall / 1.1.10 install won't help

*********
2. I also asked this months ago, but apparently there's no change, though Vlc_Help found the idea interesting, here :
viewtopic.php?f=14&t=86250#p285882

Hopefully when this report is read by the authors, in addition to fixing this newly introduced bug which breaks the functionality of the player, we would also be grateful if you would allow us to set the player to remember the last opened folder because

C:\when\you\have\to\browse\to\a\folder\this\deep\down\you\have\no\option\but\to\switch\to\another\player\which\does\remember\the\last\folder\opened.

1.2 has it.

1.2 has it, I assume you mean version 1.2 of VLC Media player? I spent some time looking for VLC Media Player 1.2 and could not find it.

Did you mean "will have it" in the future? Or is there some kind of a beta download page for development versions?

Thanks.

Just for others reading this, if this is where the latest beta builds are http://nightlies.videolan.org/build/win32/last/
the latest beta dated June 7, 2011 does remember the last folder opened but it does not fix the Media > Open Disc bug. Functionality is broken in both 1.1.10 and the latest beta, you still get 'Your input can't be opened: VLC is unable to open... ' error message.

So waiting for the next version or reverting to v1.1.9 are the only options for now.

Hi c627627,
I don't know if they'll release an immediate patched version, due to this bug that didn't exist at all in precedent versions.

Until they fix it in the next stable version, I guess the only workaround is to right click the Video_ts folder directly from Windows Explorer, then choose "Play with Vlc" (just tried it and it worked, opening correctly on a DVD menu)

This works for me because during Vlc 1.1.10 installation, I didn't untick an option (don't exactly remember its name) that was related to integration with Windows Explorer context menus.

Yes, but some people are making permanent drive images and having a versions of VLC player with broken functionality as part of a permanent drive image is definitely not the way to go for them.


If anyone from the authors is still reading this:

1. Your uninstall.exe has exactly the same icon as the main program vlc.exe (!) Making the uninstall.exe icon be some sort of a trash can or it having no icon at all is definitely preferable to having identical icons for both vlc.exe as well as for something that kills your program. If for no other reason, think of the elderly and the plain low IQ Joe Six-Packs. They will uninstall the program just because you used the same icons for both starting as well as for killing the VLC media player.

2. I know VideoLAN has other software but from the point of view of expanding your user base, people can find C:\Program Files\VLC easier than C:\Program Files\VideoLAN.

Hmm, I know the bug and will fix it.
IN the mean time, use Open Folder in the main menu.
1. Uninstall.exe is generated at install time
2. Impossible to change now for legacy reasons.

This bug has not been fixed in the latest Beta version of the program 1.2.0 as of 21 Oct 2011. It worked in version VLC media player 1.1.9 but was broken after that to this day 1.2.0 Beta.

Can you consider fixing it in the next Beta?