Re: Calling all music fiends who have MBID tagged music collections!

Hi Frederic,
Thanks for all your work contributing to this. I'll send you an email
off-list to see if we can work out where your errors are happening (if this
is a bug that we should fix then we should try and work it out)

Alastair

On Fri, Oct 24, 2014 at 10:25 AM, Frederic Da Vitoria <[email protected]>
wrote:

> 2014-10-21 21:46 GMT+02:00 Frederic Da Vitoria <[email protected]>:
>
>> 2014-10-21 20:26 GMT+02:00 Ian McEwen <[email protected]>:
>>
>>> On Tue, Oct 21, 2014 at 08:17:01PM +0200, Frederic Da Vitoria wrote:
>>> > I have started the VM. I had a little issue with the folder name: my
>>> music
>>> > folder is named Music, and the VM already has a shared folder named
>>> Music.
>>> > VirtualBox wasn't smart enough to correct this automatically, all it
>>> did
>>> > was refuse to let me click on OK without any explanation. It took me a
>>> few
>>> > minutes to think of this and change the share name for my folder.
>>> Maybe I
>>> > could have removed the existing shared folder?
>>> >
>>> > The work is slow, really slow. On my i5-3210M, it takes close to 30
>>> seconds
>>> > to handle one track, and the software hasn't yet reached my classical
>>> music
>>> > tracks! I am going to have to stop it tomorrow morning. How should I
>>> do it?
>>> > Just stop the VM? If I restart it; will it automatically skip the
>>> tracks it
>>> > already analysed? Or should I fetch the list in submit.log and move
>>> those
>>> > files out of the way?
>>>
>>> It keeps track of what it's already done -- the tracking is by filename,
>>> so it's not necessarily useful if the sqlite DB is moved outside of the
>>> VM (though you could go in and fix it manually if you felt inspired to),
>>> but it should be fine as far as things done within the VM itself. The
>>> submit.log tracking is separate -- that's entirely human-oriented and
>>> for your own use.
>>>
>>> I'll let Rob or someone else more familiar with the particular VM setup
>>> address the question of stopping it (for running it directly, it's just
>>> ctrl-c, but since this is running automatically in the background that
>>> won't do anything).
>>>
>>
>> Thanks for the info.
>>
>> From what I read in the VirtualBox documentation, the vm should pause
>> automatically when I put my laptop to sleep and wake up properly when I
>> awake my machine. This means that I shouldn't have any more issues, until I
>> try to switch to the Windows.
>>
>
> I believe all my files have been analyzed but I am not quite sure. Here is
> my problem:
> Tail is still running. Most of the files scroll too fast to read, I am
> guessing the extractor already handled them, but it stops on some of them,
> and after a few dozens seconds issues an error. Sorry, my laptop is not
> currently beside me, so that I can't tell the precise error, but I remember
> there is "alloc" in it, maybe "bad_alloc".
>
> I checked a few of those files and it seems they are all large files (at
> least some of those I saw fail were around 20 minutes long). This evening,
> during my 3 hours train trip, I'll move the log file to Windows (as I said
> above, I don't know enough about Linux to do it inside the VM), check where
> the errors are, check the sizes for each. I'll report back tomorrow.
>
> --
> Frederic Da Vitoria
> (davitof)
>
> Membre de l'April - « promouvoir et défendre le logiciel libre » -
> http://www.april.org
>
> _______________________________________________
> MusicBrainz-devel mailing list
> [email protected]
> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-devel
>

_______________________________________________
MusicBrainz-devel mailing list
[email protected]
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-devel