Dynamic Collection: Conflicting Mount Points

[Bradley Pesicka]

Maximilian Kossick wrote:

>Hi
>So Amarok removes the files on the first CD from the database after putting in 
>the second CD? I'm not quite sure why that happens at the moment. Amarok 
>currently uses the CD's label to identify it (it probably won't stay that 
>way. Dynamic Collection isn't intended to work with CDs at the moment because 
>we haven't figured out a good way to identify CDs yet). There definitely will 
>be problems when your two CDs use the same label.
>
>But I consider it likelier that the rescanning is the cause of your problem. 
>Amarok drops the whole tags table and scans all collection directories again 
>when you tell it to rescan the collection. Was that what you did when you 
>wanted it to scan the files on the second CD? In that case its a known 
>problem and I already have a few ideas how to solve it, but I need to talk to 
>some other Amarok devels some more. Rescanning and watching for changes in 
>directories doesn't work correctly with Dynamic Collection at the moment.
>
>If that is what happened I can give you a manual workaround. Otherwise please 
>tell me some more details about the CDs you use (volume label, where on the 
>CD the music is stored, and I'll try to figure it out)
>
>Max
>
>  
>
>>have found a problem I cannot quite find a good solution for.
>>    Last time we talked, amarok would crash whenever a cd was put in.  I
>>was working with cd's because I have a few cd's with mp3's burnt on
>>them.  I would like to be able to put a cd in the drive and have the
>>songs show up in the collection.  However, when I put in a different cd
>>in the drive, the old files are removed and the new ones are added.
>>    As far as I can tell, this happens because, while dynamic collection
>>in it's current state handles missing mounts by not including them in
>>any queries, different collections or devices with the same mount point
>>conflict with each other.
>>    I spent a couple of hours trying to find a solution, but I think it
>>will take a little more work than that to get it working.  Any help
>>would be greatly appreciated.
>>    Thanks for the help so far.
>>
>>    - teknomunk
>>    
>>
I was doing a manual rescan to get the files from the new cd to show up 
in the collection.  The volume label is, I believe, "volume_label_" for 
both cd's.  This is what shows up at the end of the hal device id.  I 
made the cd's a while ago and I think I just threw files at them.  The 
directory structure is rather hodge-podge, with files everywhere.

I would be very interested in the workaround to get it working for now, 
and also your ideas on how to solve the problem permanently.

- teknomunk