Mirage 0.3 Doesn't compile....

[RustyNail]

When I try to compile Mirage, i get this rather simple error:
"
./PlaylistGeneratorSource.cs(67,35): error CS0506:
`Banshee.Plugins.Mirage.PlaylistGeneratorSource.TypeUniqueId': cannot
override inherited member `Banshee.Sources.Source.TypeUniqueId'
because it is not marked virtual, abstract or override
"
but the fun thing is that, when looking at the source code one *sees*
the 'override' keyword...
Any ideas?

[RustyNail]

Seems I recently upgraded to mono 2.0
could that be the problem? :-/

[Bertrand Lorentz]

Mirage 0.3 doesn't work with banshee 1.3.x, but it should work with
banshee 1.2.x.

There were some breaking changes in banshee's API, so mirage needs to be
updated. Those changes are in SVN (committed in rev. 57), but you
probably don't want to use SVN right now, because I just committed some
big changes that need some more testing.
Using SVN would also mean that you have to re-analyze your whole
library...

My current plan is to release a new version of Mirage right after the
release of banshee 1.4, which is planned for november 10th.

Regards,

--
Bertrand Lorentz <bertrand...@gmail.com>
> http://flickr.com/photos/bl8/ <

[RustyNail]

Thanks!
I'd have to re-analyze my whole collection anyway, recently moved from
Ubuntu to Arch Linux...
So i'll look at the SVN code.

[RustyNail]

Using Banshee 1.3.2, and rev. 60 of Mirage,
Mirage refuses to analyze my collection: When I click "Rescan Music
Library",
I see a scaning 1 of 2816... thingy,
CPU usage jumps to 100%,
and then the 'window' in the bottom left corner retracts, so to speak,
and a few seconds later CPU
usage goes down to the usual 3-4%...

[Bertrand Lorentz]

That's a known bug that I haven't fixed yet : in the new version, the
mirage DB is automatically reset, but not the table in the banshee DB
where mirage keeps track of the tracks that have been analyzed.

So you have to click on the "Reset Mirage" menu option, and then you
should be able to re-analyze your library.

[RustyNail]

> That's a known bug that I haven't fixed yet : in the new version, the
> mirage DB is automatically reset, but not the table in the banshee DB
> where mirage keeps track of the tracks that have been analyzed.
>
> So you have to click on the "Reset Mirage" menu option, and then you
> should be able to re-analyze your library.
>
> --

> Bertrand Lorentz <bertrand.lore...@gmail.com>
>
> >http://flickr.com/photos/bl8/<
>
>
>
>  signature.asc
> < 1KViewDownload

Oops. Turns out I kept clicking the wrong thing >_<
But thanks for the hint about reseting mirage...
I really need to sleep more.

[Bertrand Lorentz]

On Sat, 2008-10-18 at 17:59 +0200, Bertrand Lorentz wrote:
> > Using Banshee 1.3.2, and rev. 60 of Mirage,
> > Mirage refuses to analyze my collection: When I click "Rescan Music
> > Library",
> > I see a scaning 1 of 2816... thingy,
> > CPU usage jumps to 100%,
> > and then the 'window' in the bottom left corner retracts, so to speak,
> > and a few seconds later CPU
> > usage goes down to the usual 3-4%...
>
> That's a known bug that I haven't fixed yet : in the new version, the
> mirage DB is automatically reset, but not the table in the banshee DB
> where mirage keeps track of the tracks that have been analyzed.
>
> So you have to click on the "Reset Mirage" menu option, and then you
> should be able to re-analyze your library.

You and others might be interested to know that I just committed a fix
for the above problem.

The adventurous are welcome to test the new mirage from SVN, but be
aware that it requires banshee 1.3.2 and that it's still a work in
progress. Making a backup of your banshee DB
(~/.config/banshee-1/banshee.db) and your mirage DB
(/.cache/banshee-mirage/mirage.db) might be a good idea !

Please report any problems here or on the issue tracker :
http://code.google.com/p/banshee-unofficial-plugins/issues/list

Cheers,