1256 NP not displayed after RS & could corrupt tags [#5783]

[Mizery_Made]

Same here actually, but I got to trying different things trying to reproduce this and eventually found it.

[rovingcowboy]

I am getting the reported behavior if I load tracks into NP and restart program without playing any track. If I start playing at least one track after loading into NP, when I restart program everything is fine.

sorry about it but even doing this in xp sp3 all the 472 tracks were still showing the full tag info in the now playing list.
so i am not getting this issue.

[ZvezdanD]

You don't need to start program with empty NP to be able to reproduce this problem. It is only important to clear NP list and to load new (or even same) tracks into it. If you don't start playing any of those newly added tracks, after restart you will get mentioned behavior.

[rovingcowboy]

i'm sorry i'm just not able to get it to produce the error here. i did what you said several times this morning as i was just testing the new stable version on different sizes of screens and different playlists and it never did what you are getting so this is really a strange error. but it might still show up here some time just not getting it to do it yet. i say that like i want it too? how strange this world of bug hunting in computer software?

[ZvezdanD]

1. Right-click on the Now Playing panel and choose Clear, or click on the Edit option in the NP menu bar and choose Clear.
2. Drag & drop some tracks from the main tracklist to the Now Playing panel WITHOUT playing any of them.
3. Restart the program.

[rovingcowboy]

1. Right-click on the Now Playing panel and choose Clear, or click on the Edit option in the NP menu bar and choose Clear.
2. Drag & drop some tracks from the main tracklist to the Now Playing panel WITHOUT playing any of them.
3. Restart the program.

did that still have not got it?

i think it might be do to the fact i never installed any of the beta versions and i just over installed 3.1 stable on to 3.0.3 version i had.

[Mizery_Made]

Messing with this even more, I see that it is reproducable as Z describes. No need to clear playlist, and restart before attempting this bug. Just stop whatever might be playing in the player, clear the list, add some new tracks without playing any of them, restart. Boom.

HOWEVER, I think I've narrowed this thing down even more. This has nothing to do with adding tracks. Load up a handful of tracks in your Now Playing list (I highlighted 6 and "Play Now"'d them). Once they have been added to the player and one of them is playing... delete whatever track is playing from the list. Simple as that. Doesn't matter if you stop the track playing in the player, stop it after removing it... or let it play. I find that if the currently playing track is removed from the Now Playing list and it's the last thing played (or in my previous discovery, if nothing has been played a.k.a empty player), then BOOM. On restart, your Now Playing list is hammered.

What makes this stranger is I find that if you stop the currently playing track and delete it from the Now Playing list... then drag a new instance of it into the Now Playing window before restarting, this behavior is still triggered. I see nothing in the M3U that denotes what was playing at the time of close, that would suggest this isn't happening because MM isn't finding this value in there, but there's something going on somewhere.

[chrisjj]

This is really serious and cannot believe that nobody noticed so far.

I take some blame for that I have seen it but left it on my list of issues I could not reproduce. Serious repect to ZD and Mizery_Made for tracking this down.

[Mizery_Made]

Did you see this behavior more than once, Chris? Or was it just a "Oh, that's odd. I should see if I can get it to do that again sometime"? If you saw it a couple times, suggesting it might be a recurring error but just wasn't able to find the specific steps to it, note it in here next time. You may not be able to reproduce it, but it might point someone else in the right direction of the trigger, you know? Though if it was just a one time occurrence, yeah, can't say I haven't written off some "one time occurrence" chalking them up to me losing my mind or something, haha.

[chrisjj]

> Did you see this behavior more than once, Chris?

No more than twice, for sure.

> Or was it just a "Oh, that's odd. I should see if I can get it to do that again sometime"?

"Oh, that's odd. I'll just finish off the issue I'm in the middle of, then go back to it... Oh, now it doesn't happen. ... and what exactly did happen anyway??"

> ... note it in here next time. You may not be able to reproduce it, but it might point someone else in the right direction of the trigger, you know?

Absolutely. If I'd realised the seriousness, I would not have let uncertaintly deter a report.

I'd like a way to snap-shot MM's entire state, so bugs wouldn't get away when they gang up on me. I've not yet found e.g. VM that can do this usably.

[rovingcowboy]

Messing with this even more, I see that it is reproducable as Z describes. No need to clear playlist, and restart before attempting this bug. Just stop whatever might be playing in the player, clear the list, add some new tracks without playing any of them, restart. Boom.

that did it this time. just not sure what was making it not show up before, but my word you guys are picky.

all that is going on is that monkey is not refreshing the now playing list that was not played. he is giving you one song in it which might be one you will play again. just go to the playlist node right click the playlist you had in there and click play now he reloads the info in the now playing window. but he ain't going to do work unless he's told too, my opinon on the error its just new way of making the monkey do less work trying to cut cpu cycles

but that is just my thoughts on it. this could really be an bug in the program but most features were bugs that were taken advantage off. like color tv or color on the computer monitor. an oops moument that was taken and ran with.

[ZvezdanD]

Sorry, but you are wrong. We are not picky if some "feature" could destroy someone's tags. You also forgot that some of us are using Now Playing panel only for creating playlists, but not for playing.

I know it is faster to load bunch of files into playlist without displaying there metadata, but some of us prefer to see them even with some delay. Winamp at least has the "Metadata Reading" option with which you could specify when it should read metadata - when files are loaded, when files are played or viewed, only when files are played...

[rovingcowboy]

i did forget some are using now playing to make playlists with, cause i do it with the listview area. it shows all the files tags and is not a m3u file it lists them from the database in the list view area which is faster.
so i am sorry i forgot you did it in the now playing list which is so strange to me i don't do it that way.

and i did not think of it losing the tag info because i don't save the songs from the now playing list i add them in to the database and then edit them in the listview area. i'm one that reads now playing list as meaning its the songs that are now playing which you can add too or remove from the list thats all i use it for.

[chrisjj]

> i'm one that reads now playing list as meaning its the songs that are now playing

As an aside, let's remember that "Now Playing" is a total misnomer - it often contains tracks that are not playing and sometimes does not contain the track that is playing. It has been so long since we experienced users learned to ignore the meaning of the title that we tend to forget that it stumps just about every new user. This is part of the bumpy learning curve that sends so many users back to iTunes. I would like to see MM overcome this one day. But the %age of existing users that would agree on an alternative term is I think very low. Especially the obvious (and original) term: "playlist"

[nohitter151]

"Now Playing" ... sometimes does not contain the track that is playing.

Care to explain?