The VideoLAN Forums

WHAT IS THIS CRAP?? The info window has changed now and ALL THE FIELDS ARE BLANK when playing a movie. I have depended on this tool for a long time to check info....you guys have totally f**ed it up...AGAIN!

The last FIVE letter releases have been TOTAL CRAP and crash all the time, almost constantly when closing a movie while it's playing. Now you do something IDIOTIC like screw up a staple part of the app. Good going. Time to start looking for something else for viewing, I'm tired of this caca for the last 6 months you are getting WORSE not better.

Classic example of open source being NOT good for end users. Too many contributors and NO chiefs, noone to answer to. The last time I tried to post here I got ZERO response from you people. Oh but WAIT when you got 100 developers NOONE HAS TO TAKE RESPONSIBILITY FOR SCREWUPS LIKE THIS...RIGHT??


This is supposed to be some kind of "release" version as opposed to a letter beta?? Puh-leeeze!

User base: 25 million. "ACTIVE" developers... euh 10 part timers ?

Just getting this back in perspective for a minute. patches welcome. if you don't like our player, please use something else.

WHAT IS THIS CRAP?? The info window has changed now and ALL THE FIELDS ARE BLANK when playing a movie. I have depended on this tool for a long time to check info....you guys have totally f**ed it up...AGAIN!

Select the right playlist item before you use the media info panel (Not that command-I does not pull the information for the "Currently playing item", but for the "Currently selected item" Sometimes this is the "Playlist" node (which will result in pretty much empty fields).

Select the right playlist item before you use the media info panel (Not that command-I does not pull the information for the "Currently playing item", but for the "Currently selected item" Sometimes this is the "Playlist" node (which will result in pretty much empty fields).

Why this change?
The logical behaviour is IMO to pull information for the 'currently playing item', not the 'currently selected item'.
This is also how the Windows version of 0.9.2 behaves, is there any reason why it was changed in the OS X version?
I think this is a major nuisance. Please consider fixing it

Thanks!

Why this change?
The logical behaviour is IMO to pull information for the 'currently playing item', not the 'currently selected item'.
This is also how the Windows version of 0.9.2 behaves, is there any reason why it was changed in the OS X version?
I think this is a major nuisance. Please consider fixing it

Thanks!

It's on my personal TODO list, but there were bigger fish to fry the last week

Why this change?
The logical behaviour is IMO to pull information for the 'currently playing item', not the 'currently selected item'.
This is also how the Windows version of 0.9.2 behaves, is there any reason why it was changed in the OS X version?
I think this is a major nuisance. Please consider fixing it

Thanks!

It's on my personal TODO list, but there were bigger fish to fry the last week

Thanks a lot - looking forward to it!

Well, we'll probably add the current item name in the window title name.

Inspector panel should inspect current selected item, and change accordingly to the selection. That is what is currently done, and IS the correct behaviour.

Anyway, limiting that to the current playing item is a mistake: You can't inspect something that you don't play.

Well, we'll probably add the current item name in the window title name.

Inspector panel should inspect current selected item, and change accordingly to the selection. That is what is currently done, and IS the correct behaviour.

Anyway, limiting that to the current playing item is a mistake: You can't inspect something that you don't play.

Why not support both?
Let the default be "inspect currently playing item" if no other item is selected in the playlist (or let the currently playing item be autoselected in the playlist).
This has been the behaviour until 0.9.2, and it´s still how the Windows version behaves.
As you have seen, several user have reacted to the change in 0.9.2.

Hum, this should be the default behaviour... So you can fill a bug for that.

Hello,
this issue is still present with the current version 0.9.8 under Mac OS 10.5.6.
Is anybody working on this?
Has a bug been filed?
Should I do this?
Can I do this?
I dont know how to append screen shots to my post in this forum,
but I am happy to deliver some of that demonstrate the problem
by private mail if that helps to fix the issue

Thanks, Christian