Re: [Muine] NEW PRERELEASE: 0.8.3pre2



Niran Babalola wrote:
Well now it looks like it didn't get completely fixed. Deleting the
database then playing an ogg file will show the right time for me. If
I go back to a song after it has played all the way through, the track
length says zero again. As long as the track doesn't completely
finish, it retains the correct length. Weird.

Same here. Didn't notice it as was just moving back and fore between
songs. It's not a problem with reading the information from the files
then as moving to a new album (atm) still gives time information.

The album I was playing alot last night now doesn't have any time
information associated with it. I've also loaded a disk, and songs that
have been played do have the time information associated with it (i.e.
when the second track started I went back to the first one and the time
was still there, same with when I went back to the second track). I'm
just waiting till the 3 songs complete (this is only a single) so see if
when the disc repeats the information is lost.

OK. Single finished and all time information is there :/ So what makes
it lose the time information? It's definitely something to so with the
storage in the database, because if I go back to the album that I played
last night it no longer displays the time information.

I've been looking into the code, but I can see anything that would
happen. Duration under Song has a 'set' method which replaces duration,
and calls Global.DB.EmitSongChanged(this). However I get confused under
SongDatabase - EmitSongChanges check to see if SongChanged == null,
which I think checks to see if the SongChangeHandler has a pointer to a
function, and only calling that function if it exists. Is this part of
the plug in system? I can't see where SongChangeHandler or SongChanged is
set and what's called beyond that. (This is my first time looking at C#
code, so some, well alot, of it is alien to me! :/).

Ah! :) Got it. My single has lost it's time information. I selected
another single and let it run straight though (not selecting another
track before it had played the whole album).

Now I'm playing a different single it's losing the information on each
song change. I've just restarted it aswell. Still deleting after every
song. So why not the first time around? It is only after the first full
album has been played? I'm just re-building the database to see what
starts it.

No. It's removing the all the time information now. Maybe I was quick on the trigger :)

Jorn - if you could give me some tips on functions/methods, etc to look at that would force a save in the song database or anything that would change the metadata about the song I'll continue to have a look! :)

--
Jonathan Wright <mail at djnauk dot co dot uk>
  Life has no meaning unless we can enjoy what we've been given
--
Running on Gentoo Linux
  (2.6.10-gentoo-r7-djnauk-b03 i686 AMD Athlon(tm) XP 2100+ GNU/Linux)




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]