Ok, back again in this thread...

Now unfortunately I could not replicate exactly the same problem yet, so I have no debug file, but I can replicate a bug that may be closely related to this one, so I thought I post it here:

Try and do this:

Display the songs of an album.

Select the first song, using the mouse.

Now click into the song window *below* the songs: The selected first song gets unselected, but the dotted frame (cursor) is stil above the title of the first song.

Now with the mouse start drawing up a selection window from the bottom below the last songs, selecting the last 2 or 3 songs of the album. Of course they get selected.

But strangely enough, at that moment the song where the dotted cursor stands (here the first one) *also* gets selected.

So if you press delete, because you wanted to delete the last 2 songs you just selected, the first song gets deleted too by accident.

I hope I was explicit enough.

For further questions, just ask and I will try to help, but I will only be back at the machine where MediaMonkey is running on thursday or friday.

bye
Wolfgang

I will try to make it happen.

But in any case: I just noticed that it is possible to select several files and then activate the node. The selection color of the tracks is changing, but still they look selected.

Now in any way if I press "del" now, from the visual impression I get, I do not expect to get all tracks deleted under this node.

So I guess it might be a good idea to catch this situation with a special warning message like

"Attention: Node deletion! By clicking OK, you will not only delete selected tracks, but *ALL* tracks under the selected Node."

bye
Wolfgang

I would very much appreciate a debug log--Thx.

-Rusty

rusty wrote:Any more info would be appreciated. e.g. does it occur in a specific node? Is there a way to consistently reproduce it?

To me it happened about 4-6 times while re-ripping about 600 CDs. So unfortunately I can't reproduce it consistently. If I could, I would have sent you a debug log long ago.

For me it always happened while I was looking at all tracks of an album of an artist under the artist node. Everything else has already been said from my side.

I still have to re-rip around 100 CDs. If you want, I can install the debug version and create logfiles all the time. Maybe I can catch it one more time.

bye
Wolfgang

Wolfzel, Cronblad,

Any more info would be appreciated. e.g. does it occur in a specific node? Is there a way to consistently reproduce it?

I've tried to replicate, (changing focus between apps) but can't!

-Rusty

rusty wrote:Are you certain that the node wasn't selected? If you have any additional insight, please share.

I don't know if the focus changed somehow, but for instance if I had 20 tracks displayed, then I was selecting the lower 10 of them either by hand or mouse, so half of the tracks were selected.

Then I press "del" and I watch how *all* files get deleted from the bottom to the top, not only the selected ones.

So maybe the node got selected somehow, but I can't say how this could have happened.

Here is a wild guess:

Maybe this can happen because the focus between the running programs had somehow switched in the meantime and I did not notice that.

I suppose that because it happened the most times, when EAC was initially handling a new CD in the Drive and looking it up in freedb. In that time, EAC is locking up the system for a short time. I suppose my selection and my keypress happened before that lock-up and the deletion is happening after the lock-up. So maybe the focus of the programs is switching here, leading to a change in focus in MM from tracks to the node and this way deleting all tracks of the active node although the tracks have been in focus right before.

bye
Wolfgang

I installed the new build just after I started to replace my ogg-files with flac. When I had done a few albums I suddenly reminded myself that backup maybe was a good idea before doing more with a Beta version. But too late, suddenly all my ogg-files were gone and I had no idea what happened. Maybe it was this thing that happened to me?

Wolfzell,

There were a couple of other reports in which users accidentally moved all files in a node rather than the selected files.

I had attributed this to a selection problem. i.e. that the user probably selected the _node_ rather than the files, and thus the action was performed on all files in the node.

Are you certain that the node wasn't selected? If you have any additional insight, please share. Thanks.

-Rusty

Teknojnky wrote:You would be far better off by using musicbrainz picard to tag new flacs than wasting time converting back and forth.


Alot less time consuming and annoying than the other way.

I just finished re-ripping my CDs using the process that Wolfgang described in another of his posts. It makes a lot of sense and really isn't that time consuming. One would have to try the process once or twice to see how it works.

Like him, I had a LOT of time invested in getting the tags for my mp3s the way I want them. Online database services get it mostly right, but they're far from perfect. Also for 'greatest hits' and compilation CDs, I like to use the year each track was released, not the year of the greatest hits CD, which took a great deal of time. All this would be lost.

Wolfgang's process essentially just borrows the tags, and the converted mp3> flac file is replaced with a CD>flac file. The original mp3 file is erased once the flac file is synchronized with MM. One thing I did different was use "flac" and "mp3" folders, so that I didn't have mixed formats in the same folder.

It would be better if MM could act as the CD database server for any re-rips, but that is a wish list item that has yet to become a feature.

You would be far better off by using musicbrainz picard to tag new flacs than wasting time converting back and forth.

I know this, because I started to do what the original posted was doing.

Now it's simple:

-rip/create flac's with eac/MM/whatever
-while you have the CD loaded, run picard and use the 'look up cd' button, this loads a webpage with the applicable musicbrainz release (if the cd id is already in MB). Click the "tagger" link to load the release to picard.
-drag/drop the finished flac files on to picard "New files (drag files to tag here)" node
-let it process the files, click the cluster button/drag the files to the album node added via the lookup cd + tagger link

-verify all the tracks line up, submit the puid's and save the tags.

Alot less time consuming and annoying than the other way.

It's a smart (but time consuming) way to transfer all metadata from the old mp3- to the new flac-files.


/Bex

Why would you be converting from MP3 to FLAC? You aren't gaining any quality, you're just increasing the file size. MP3 is a lossy codec, meaning data was lost while being encoded and compressed to mp3. Converting to FLAC isn't going to allow you to retrive that data, its just gonna make an exact copy of the mp3 with a larger file size.

I understand you are reripping the CD (I think), but what is the point of the conversion from MP3-> FLAC

Ok, I think this is severe:

I am still in the process of switching from mp3 to flac.

This is what I am doing:

I convert a whole album from mp3 to flac. So I have all entries doubled in the database. Then I rip the album with EAC and manually replace all the flac files in the directory of the album with the newly ripped files.

Now I want to get rid of the mp3-files. I display the album, then I see all songs two times. The upper half of the list are the flac files and the lower half are the mp3-files.

With the mouse I mark the lower half (the mp3-files) for deletion. I press "delete", the dialogue comes up, asking me if I only want to delete "library entries" or "entries and files", I choose "entries and files" and hit return and then....

I watch with horror that *all* displayed songs get deleted, not only the ones that are marked!

This happened several times with build 968, today I had it happen the first time with 971.

Unfortunately it happens only sometimes. Mostly when (so I feel) the CD is still active scanning the content of a newly inserted disc.

I did not loose files yet, I always found the deleted files in the trashcan, but I don't know what happens if this bug occurs when I have *all* files displayed. I don't even dare to think about that (ok, I *do* have a backup...), but still...

I remember several reports from people loosing all their files somehow, maybe they hit the same thing.

bye
Wolfgang