7 hours ago
You would use synchronization ID for matching songs in setlists. The existing Song ID field would be just like the Custom field - used for informational purposes, but that's it. I would just prefer this because it will prevent people from incorrectly using the song ID field.
BRX - You could update the existing song through .msf, but the problem is it may not keep the file/folder structure intact, as it most likely does not match between iOS and Windows. If it does currently match between the two, then it would work just fine.
Yes the song ID is currently checked when importing a .msf and overrides any other logic for matching up the song in the .msf to the existing song in the library.
Mike
BRX - You could update the existing song through .msf, but the problem is it may not keep the file/folder structure intact, as it most likely does not match between iOS and Windows. If it does currently match between the two, then it would work just fine.
Yes the song ID is currently checked when importing a .msf and overrides any other logic for matching up the song in the .msf to the existing song in the library.
Mike