Mozart Edition and Uniti Core
Posted by: MAB252 on 20 August 2018
I have started to rip the new 200 cd Mozart Edition on my Core. Each time I rip the next cd it obliterates the last one resulting in only a single cd being ripped. I do not understand how or why it would just overwrite and I have tried going back to rip an earlier cd again it just overwrites. Does anyone have any ideas other than going back to dppoweramp.
I don't have a Core so can only guess at this - I'd suspect that if chaniging the metadata doesn't appear to fix it that there is metadata you either think isn't connected to identifying the disks, or much more likely, there's metadata you're not being shown that would allow you to differentiate between the disks if you were able to change it manually.
As Chrissu suggests it's probably worth ripping a couple of the disks again, but with dBpoweramp and comparing the metadata with that produced by the Core - can you see differences ? If so, what happens if you edit the fields on the Core to match dBpoweramp ?
Are you able to look at the metadata from a Core rip using dBpoweramp ? That would be another way to see if there's a field you need to change after ripping weach disk, but before ripping the next.
Otherwise, if you can't see an obvious cause and discussing it with Naim doesn't being a quick solution again do as Chrissu says and rip using dBpoweramp and move to the Core's download folder.
In the end it's the music that matters, not where, or how, it's stored as long as it's accessible for you to play (I know that seems obvious, but it's easy to get so caught up in the "fault" that the reason you're doing it can be lost 
)
TallGuy posted:I don't have a Core so can only guess at this - I'd suspect that if chaniging the metadata doesn't appear to fix it that there is metadata you either think isn't connected to identifying the disks, or much more likely, there's metadata you're not being shown that would allow you to differentiate between the disks if you were able to change it manually.
As Chrissu suggests it's probably worth ripping a couple of the disks again, but with dBpoweramp and comparing the metadata with that produced by the Core - can you see differences ? If so, what happens if you edit the fields on the Core to match dBpoweramp ?
Are you able to look at the metadata from a Core rip using dBpoweramp ? That would be another way to see if there's a field you need to change after ripping weach disk, but before ripping the next.
Otherwise, if you can't see an obvious cause and discussing it with Naim doesn't being a quick solution again do as Chrissu says and rip using dBpoweramp and move to the Core's download folder.
In the end it's the music that matters, not where, or how, it's stored as long as it's accessible for you to play (I know that seems obvious, but it's easy to get so caught up in the "fault" that the reason you're doing it can be lost
Remember that you should never open a Naim CD rip on your computer and edit it, as this messes up the database. You can copy it to the Downloads folder or another location and edit it there, but do not then return it to the original MQ folder. Until such time as Naim can come up with a fix, simpler, I think, to use a different ripper in the first place.
ChrisSU posted:TallGuy posted:I don't have a Core so can only guess at this - I'd suspect that if chaniging the metadata doesn't appear to fix it that there is metadata you either think isn't connected to identifying the disks, or much more likely, there's metadata you're not being shown that would allow you to differentiate between the disks if you were able to change it manually.
As Chrissu suggests it's probably worth ripping a couple of the disks again, but with dBpoweramp and comparing the metadata with that produced by the Core - can you see differences ? If so, what happens if you edit the fields on the Core to match dBpoweramp ?
Are you able to look at the metadata from a Core rip using dBpoweramp ? That would be another way to see if there's a field you need to change after ripping weach disk, but before ripping the next.
Otherwise, if you can't see an obvious cause and discussing it with Naim doesn't being a quick solution again do as Chrissu says and rip using dBpoweramp and move to the Core's download folder.
In the end it's the music that matters, not where, or how, it's stored as long as it's accessible for you to play (I know that seems obvious, but it's easy to get so caught up in the "fault" that the reason you're doing it can be lost
Remember that you should never open a Naim CD rip on your computer and edit it, as this messes up the database. You can copy it to the Downloads folder or another location and edit it there, but do not then return it to the original MQ folder. Until such time as Naim can come up with a fix, simpler, I think, to use a different ripper in the first place.
Thanks, I was sure there was some sort of limitation - didn't realise it was that severe.
I think it's still a valid (quick) test to copy one or two albums out to Downloads so that you can look at the metadata (but not copy it back ) - you may see what the problem is, even though it looks as though you'll need to wait for a fix - it still feels good to know the cause, even if you can't rectify it and I'm sure there's people who would like to know the cause, not just that it will be fixed at some point... if for no other reason than to complain here about how stupid the Core/app (delete as appropriate) is compared to product X.