[fixed] Beta 2 - track properties change restarts the track

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: [fixed] Beta 2 - track properties change restarts the track

by tiagoclaus » Tue Oct 02, 2007 11:49 am

All fixed in B3 or reinstalling MM, I would not know.

by tiagoclaus » Tue Sep 25, 2007 3:23 pm

No, I have never used a clear instalation for MM3 because it was never necessary. But I agree that it is the case now.

I only use MP3. No other format.

I will try again uninstalling everything beforehand.

by jiri » Tue Sep 25, 2007 10:28 am

I think that it could be because there's something specific about your configuration. Do you use a clear MM installation? Or any other plug-ins? Does it happen with any audio format, like mp3, wma, or so?

Jiri

[fixed] Beta 2 - track properties change restarts the track

by tiagoclaus » Mon Sep 24, 2007 7:46 pm

Pretty weird behavior. I hope my English can explain it correctly.

When I change the properties of the currently playing track, MM3 restarts the track over the current one: it is like if a second instance of MM3 starts playing the same song from the beginning, while the previous one (or current, depends of your point of view) keeps playing for a few more seconds (10-12 seconds).

This "2nd instance" behavior is more clear when, for example, I rate the current track and pauses the music right after that: the "new" instance pauses immediately (actually seems like MM3 is only under control of this new instance) and the "previous" keeps playing for those seconds.

I first though it was a delay, as I was experiencing with tracks playing directly from my iPod, but that is not the case. I am dealing with local files this time. And, of course, that was not happening with beta 1.

I have made a few tests and this behavior happens when I change the properties from the "track properties" window, from the main track list or in the player. I basically mean "change the properties" by changing its rating, but it seems that any DB/tag change is valid here.

Sure, the bug reported here is the one from the title. I am also surprised that over 10 days after beta 2 release I am the first one reporting this bug. This might mean I am the only one, but that answer does not help me at all.

Let me know if I can provide any further information. I will try tomorrow beta 2 in the computer at work to see if there is anything new.

Besides this minor issues, great release! Thanks!

Top