Posts: 114
Threads: 30
Joined: Nov 2017
I've searched the manual and also some old threads, but that is still not clear to me.
I'm particularry interested in knowing if this field has any relevance when synchronising devices. My use case: I'm having all kind of problems after updating songs with more than one version on the DB (same song name, but different key, or artist, for example) and synchronizing. Would Song ID be helpful in this case? Is it best practice to assign different Song IDs to different versions of the same song or should (hopefully not) just use different names to avoid sync conflicts?
Thanks
Posts: 179
Threads: 19
Joined: Nov 2024
The file name is the only way to avoid creating a "hell machine"... Simply add "V1, V2, etc." systematically and you'll avoid problems...
Posts: 114
Threads: 30
Joined: Nov 2017
Yesterday, 06:43 AM
(This post was last modified: Yesterday, 06:48 AM by Cerio.)
To clarify, PDF files have all an unique name, that's not the question.
Posts: 1,020
Threads: 87
Joined: Feb 2017
Just checking - are you using custom formatting when displaying the songs on the library screens?
i.e. although the files might look different on these screens, they could have identical physical names.
Geoff
PS: I don't use sync but as I understand it, unique names shouldn't cause an issue.
Samsung Galaxy Tab A6
Posts: 114
Threads: 30
Joined: Nov 2017
Yesterday, 07:34 AM
(This post was last modified: Yesterday, 07:36 AM by Cerio.)
(Yesterday, 07:15 AM)Geoff Bacon Wrote: Just checking - are you using custom formatting when displaying the songs on the library screens?
i.e. although the files might look different on these screens, they could have identical physical names.
Geoff
PS: I don't use sync but as I understand it, unique names shouldn't cause an issue.
All my pdfs are in the same folder in all my devices, so that's definitely not the problem (I don't use the
Create subdirectories for songs option anymore)
In any case, I was referring to identical
Song Names (Title field on the database), not to
PDF filenames. I would expect that the program is smart enough to handle database syncs without conflicts when two or more songs share the same title (but different other metadata, as key, collection, type, artist, etc), but maybe I'm just wrong. Wondering if Song Id field can be used for this purpose.
Posts: 1,020
Threads: 87
Joined: Feb 2017
As I understand it, the matching is on the physical filename and not any metadata
As your phyical names should be unique (they are all in the same folder), I would expect what you are doing to work.
Guess you will have to wait for Mike to respond
Geoff
Samsung Galaxy Tab A6
Posts: 44
Threads: 4
Joined: Feb 2024
I remember Mike advising us to not use the Song ID field but cannot remember why as I believe him and so have simply not gone there. It is a bit odd that the Song ID field is editable for us users if we should not be using it. Maybe Mike can explain.
Posts: 1,129
Threads: 114
Joined: Dec 2015
Posts: 114
Threads: 30
Joined: Nov 2017
After reading those posts... I'm even more confused.
If the field is designed for syncing, why is it user editable? And why duplicated ID are allowed?
Posts: 179
Threads: 19
Joined: Nov 2024
49 minutes ago
(This post was last modified: 46 minutes ago by Swiss1000.)
(2 hours ago)Cerio Wrote: After reading those posts... I'm even more confused.
If the field is designed for syncing, why is it user editable? And why duplicated ID are allowed?
Absolutly nothing could be a "Unique Index" in a file system except the file name...
All the rest is a "complex machine"...
Lot of programmers lost themself in trying that concept.
The weel is a really old invention.
In addition, the "Song ID" is not the same in music industry between China, UE aud US...
Forget it...
Posts: 1,020
Threads: 87
Joined: Feb 2017
As I understand it:
By default, MS uses the song title (possibly with file name) to sync
If specified, the Song ID can be used to override the default mechanism i.e. you could have different names on each device and it would still sync them as long as they used the same id.
What one could perhaps do is use two different ranges of Song Id when creating new files e.g. 10001 to 19999 on device one and 20001 to 29999 on device 2 (first digit indicates device on which file first created). Synching from one tablet to the other would then be based solely on the Song Id (assuming all songs are given ids.
e.g
A Song Id on device 1 of 10500 would get transferred to the same id (10500) on device 2
An id of 21000 on device 2 would tranfer to 21000 on device 1
ie. each device may have songs from both devices but they are unique because you are using different ranges on the devices
The main problem with this is that you would need to keep track of the used ranges so that you know which number to add to the next file you create.
Seems a lot of effort to me - probably much easier to make sure that the (physical?) names are unique.
Caveat - As I've said before, I haven't used synching
Geoff
PS Might be a good idea to show some of your names that are causing issues.
Samsung Galaxy Tab A6
