Closed GoogleCodeExporter closed 9 years ago
Are you saying this only happens with a specific file ?
If yes, please check if mirage is able to analyze it properly :
- Start banshee from a terminal
- Remove the file from your library
- Import it again. Mirage should analyze it again. Watch the terminal output to
see
if there's any error.
Original comment by bertrand.lorentz@gmail.com
on 26 Oct 2009 at 8:37
I investigated further and found out that it happens only with certain files.
As you
supposed i removed the file from the library and imported it again. Mirage
correctly
analyzed it again:
libmirageaudio: rate=44100, resampling=0,500000
libmirageaudio: decoding /media/Data/backup_sync/Musik/Deutsch/Mia/Zirkus/10
Mia -
S.O.S..mp3
libmirageaudio: EOS Message sent
libmirageaudio: EOS Message received
libmirageaudio: time = 2630,000000
libmirageaudio: frames=2583 (maxhops=2583), size=513
Mirage - decoded frames=2583,size=513
Mirage - mfcc Execution Time: 100ms
Mirage - scms created in: 31ms
Mirage - Total Execution Time: 3076ms
The following discoverings could be helpful:
If banshee crashes when i drag a song on the mirage "Playlist Generator" i have
less
than 6 songs in the mirage playlist on next startup.
When it does not crash after i drag&drop a song it finds 6 songs and starts
playing
with the first one.
The number of tracks in banshee.db and mirage.db do not match (9186 in
CoreTracks
vs. almost 12000 in mirage). What does the "Status" column in the table
MirageProcessed describe? I found entries with Status == -2 and -1 and 0.
Original comment by times.pr...@googlemail.com
on 26 Oct 2009 at 11:02
This issue can be closed.
I finally recreated my databases from scratch and all works fine now with
newest
banshee (1.5.3) and mirage (0.6).
Original comment by times.pr...@googlemail.com
on 9 Feb 2010 at 8:46
Thanks for the heads up !
I also added some null check before the latest release, so if a similar
situation
happens, Mirage shouldn't crash.
Original comment by bertrand.lorentz@gmail.com
on 9 Feb 2010 at 9:14
Original issue reported on code.google.com by
times.pr...@googlemail.com
on 25 Oct 2009 at 4:31