Latest Core Update Issues?

I wonder whether it has created a mirror copy or it's just that it's indexed both locations (store and share), as it were, and thinks the same files are in both places, there being no way to know they are the same files.

If you have two music stores then there is room for confusion as to where the Core should store its own rips. What I don't know is whether it automatically demotes a store to a share if you set a new music store elsewhere. That would seem the logical thing for Naim to make it do. If you promote a share back to a store, I imagine (but don't know) that it will offer you the option of formatting the new store. But if you say no, then it shouldn't affect what is already in the new store.

The time to try all these things out is when the Core is new and the various store/share locations are almost empty of course.

best

David

When do you knock off for Christmas, David?

Seriously, Naim should be emptying the gold star locker for your support above and beyond.

Respect.

I just updated my Core fw and then also the App and, after a re-start, so far all is well...

David Hendon posted:

I wonder whether it has created a mirror copy or it's just that it's indexed both locations (store and share), as it were, and thinks the same files are in both places, there being no way to know they are the same files.

If you have two music stores then there is room for confusion as to where the Core should store its own rips. What I don't know is whether it automatically demotes a store to a share if you set a new music store elsewhere. That would seem the logical thing for Naim to make it do. If you promote a share back to a store, I imagine (but don't know) that it will offer you the option of formatting the new store. But if you say no, then it shouldn't affect what is already in the new store.

The time to try all these things out is when the Core is new and the various store/share locations are almost empty of course.

best

David

Hello David, Thank you for your help in recent times and Happy Christmas.

I used Windows explorer to see the files so there was no doubt. When I imported a Share with a Dowload folder it copied them to both!

I suspect the problem was the Music Store had the same name on the internal disk and the network share. Quite a nice feature! I didn’t really want it to doing anything on the network Music Store as I wanted an empty one to start ripping to.

I don’t know what to do other than backing up the network share before promoting it to Music Store. The UnitiServe did not do anything to network shares. 

One final thing about .png files. I think the Core defaults to coverfront.png whereas the UnitiServe looks for folder.jpg. The Naim App however supports both, but unfortunately the n-Serve App only support folder.jpg, which means Core rips don’t have covers if you share the Music Store on the UnitiServe!

Phil

Updated . All seems well apart from one bug.

CD library... Albums by location and it crashes the app on iPad and iPhone. I dont know what it is actually for, but i was inquisitive.

Phil

I have just read your original post again more carefully. It does indeed look as if the Core will now allow you to have two music stores and ensures that they are a copy of each other. I think this is new from the update....

in answer to your question, if you delete the internal Music Store location, the disc will sit there with files on but not be indexed. If you now set your NAS as a Music Store, and let the Core format it presumably, you should have an empty NAS Music Store with music and download folders. If you now go back to the internal disc and define it as a Music share, then the Core shouldn't be copying anything from it. But it will index It of course, because that is what it does with Shares. If the Core does now copy files across, that strikes me as unwanted behaviour and could be said to be a bug. The whole point about shares is that you leave the files where they are and the Core will serve any of them under control of the app.

best

David

David, many thanks for your help for fellow forum users of the Core, your help, has been invaluable in 2017. You have done this with a very professional manner, and have helped Naim users of this product that have had difficulty accessing fixes. Thank you from me...

Gazza

David Hendon posted:

Phil

I have just read your original post again more carefully. It does indeed look as if the Core will now allow you to have two music stores and ensures that they are a copy of each other. I think this is new from the update....

in answer to your question, if you delete the internal Music Store location, the disc will sit there with files on but not be indexed. If you now set your NAS as a Music Store, and let the Core format it presumably, you should have an empty NAS Music Store with music and download folders. If you now go back to the internal disc and define it as a Music share, then the Core shouldn't be copying anything from it. But it will index It of course, because that is what it does with Shares. If the Core does now copy files across, that strikes me as unwanted behaviour and could be said to be a bug. The whole point about shares is that you leave the files where they are and the Core will serve any of them under control of the app.

best

David

David, If I stick to the NAS then I can add Music Stores that have previously been used as Music Stores without loosing their content. It says it has found an existing Music Store, which is comforting. It removes from it indexes all the albums in the previous Music Store and loads the albums from the new Music Store. So that at least is logical. If you want the albums from the previous Music Store then it can be added as a share. As it knows the Store it does actually rebuild its database, but just includes it content.

I don’t want to repeat the experience with the internal Music Store!

Phil

Gazza posted:

David, many thanks for your help for fellow forum users of the Core, your help, has been invaluable in 2017. You have done this with a very professional manner, and have helped Naim users of this product that have had difficulty accessing fixes. Thank you from me...

Gazza

 

 

 

 

I agree GAZZA...David has saved the day for me,several times while stumbling to get my Core working,most helpful and patient...cheers David!

My core updated without a hitch.

Updated the Core all OK ripped 4 CDs yesterday one showed ripping errors on one track all OK.

@NICK LEES, @GAZZA, @NO QUARTER Thank you for the kind commments guys! It's been a voyage of discovery for me, so it's interesting to try to help others and swapping thoughts and experiences to help each other is what this forum is all about. Anyway it's very kind of you. I'm still learning as the exchanges in this thread with [@mention:66047985346995680]ILIPE show....

Happy Christmas everyone!

best

David

Filipe posted:

David Hendon posted:

Phil

I have just read your original post again more carefully. It does indeed look as if the Core will now allow you to have two music stores and ensures that they are a copy of each other. I think this is new from the update....

in answer to your question, if you delete the internal Music Store location, the disc will sit there with files on but not be indexed. If you now set your NAS as a Music Store, and let the Core format it presumably, you should have an empty NAS Music Store with music and download folders. If you now go back to the internal disc and define it as a Music share, then the Core shouldn't be copying anything from it. But it will index It of course, because that is what it does with Shares. If the Core does now copy files across, that strikes me as unwanted behaviour and could be said to be a bug. The whole point about shares is that you leave the files where they are and the Core will serve any of them under control of the app.

best

David

David, If I stick to the NAS then I can add Music Stores that have previously been used as Music Stores without loosing their content. It says it has found an existing Music Store, which is comforting. It removes from it indexes all the albums in the previous Music Store and loads the albums from the new Music Store. So that at least is logical. If you want the albums from the previous Music Store then it can be added as a share. As it knows the Store it does actually rebuild its database, but just includes it content.

I don’t want to repeat the experience with the internal Music Store!

Phil

Phil I really think there is no risk of deleting music unless you let the Core format a disc and yes the Core scanning of shares is quick. When I imported the files from my Unitiserve to the Core, I defined the US as a share because at that stage anyway (it is an early production unit), it was the only way I could make the Core offer me the US as an import source. The Core more of less instantly scanned and indexed all the files on the US and deleted the entries from the app when I unshared the US.

Anyway it's now time for both of us to listen to music!

best

David

 

Anyway it's now time for both of us to listen to music!

best

David

Thank you again and Happy Christmas

Phil

Filipe posted:

One final thing about .png files. I think the Core defaults to coverfront.png whereas the UnitiServe looks for folder.jpg. The Naim App however supports both, but unfortunately the n-Serve App only support folder.jpg, which means Core rips don’t have covers if you share the Music Store on the UnitiServe!

Phil

I hadn't noticed this interesting detail before, but as I was about to take the Unitiserve off-line, I just remembered to look at it with n-Serve first. It sees my Core's music store as a share, but as you say, the Core rips don't show cover art in n-serve. Incidentally n-serve is happy with cover.jpg as well as folder.jpg, not that that helps with this situation!

best

David

I had a www download from Sound Liaison that had a .png cover art.  Synology NAS would not play & I changed the art acceptance prog to take both .jpg & .png & that worked.  I also e-mailed Sound Liaison who admitted it was their error.   I have not noticed .png trends becoming the default format,  but its something to keep an eye open for.

Sometimes the Core does not group an artist,s albums together... not sure why. Did a database reset today and all is fine again.

David Hendon posted:

Filipe posted:

One final thing about .png files. I think the Core defaults to coverfront.png whereas the UnitiServe looks for folder.jpg. The Naim App however supports both, but unfortunately the n-Serve App only support folder.jpg, which means Core rips don’t have covers if you share the Music Store on the UnitiServe!

Phil

I hadn't noticed this interesting detail before, but as I was about to take the Unitiserve off-line, I just remembered to look at it with n-Serve first. It sees my Core's music store as a share, but as you say, the Core rips don't show cover art in n-serve. Incidentally n-serve is happy with cover.jpg as well as folder.jpg, not that that helps with this situation!

best

David

I converted using Photoshop Lite of some descriptionand nServe was fine. It would be nice if the Core satisfied all standards at some point to avoid the conversion. Anyone know whether there is a batch solution?

I imported an nServe Share with the Core and it did not convert, but does show the folder.jpg file. The Core puts imports into Downloads just copying everything. It does link to Rovi to get info and works out genre info. I hope Naim will sometime treat imports like rips to allow editing. Anyone know if this is planned?

Phil

I know that it isn't planned, because Trevor said so in a post in the forum a few months ago. Personally I think this is a daft decision, especially if the Core is altering the metadata or cover art in the downloads folder (I didn't think it did that) but it needs lots of us to request it before Naim will take any notice I think.

If you import from a US or HDX Music Store, the import of rips made by the US/HDX is put into the music folder. But recently Phil Harris said in a post about imports ending up in the Core's Downloads folder that the import strategy "plays safe" and only puts imports it is certain about into the music folder.

best

David

Kevin C posted:

I would be interested to hear if anybody else is now experiencing issues when ripping CD's following the latest release of firmware earlier today to version 2.5(9144).

The CD appears to rip fine, but then when completed it is not being ejected and requires a manual eject?

Dear Kevin C,

I have the same problem: after the update the machine does not eject the CD's automatically. I have alerted Naim Support three days ago, but no response yet (but it's Christmas time).

Best,

Johan

Ripped 4 CDs all ripped OK one I had to look up the Cover Artwork ad all ejected OK after ripping.

Strange how this isn’t a consistent issue though. Mine updated and to test I picked 4 well loved CDs, ripped and ejected them without an problems.

@Kevin C and [@mention:73511715426050383]

Much earlier in this thread if you look you will see a post from Tom @TJ at Naim who says that the fix for this issue of not ejecting CDs after ripping is to do a factory reset of the Core and he explains how to do that.

best

David

Johan59 posted:

Kevin C posted:

I would be interested to hear if anybody else is now experiencing issues when ripping CD's following the latest release of firmware earlier today to version 2.5(9144).

The CD appears to rip fine, but then when completed it is not being ejected and requires a manual eject?

Dear Kevin C,

I have the same problem: after the update the machine does not eject the CD's automatically. I have alerted Naim Support three days ago, but no response yet (but it's Christmas time).

Best,

Johan

I had a demo Core the day the firmware came out so did not know how things should look. The best thing to do after an update is to shut it down for 15-30 minutes and then reboot. The internal PS seems to take a while to fully discharge. That seems to sort a myriad of problems out. Then in standby it should only have the standby light on and should eject ok. Mine only turned off the eject light and did not rip at all. 

Phil

David Hendon posted:

@Kevin C and [@mention:73511715426050383]

Much earlier in this thread if you look you will see a post from Tom @TJ at Naim who says that the fix for this issue of not ejecting CDs after ripping is to do a factory reset of the Core and he explains how to do that.

best

David

Hi David, Thanks for bringing this to my attention. However, all three methods mentioned by Tom@TJ do not work for me? So, still waiting for a response by Naim staff?

Best,

Johan