Uniti Core Shipping

yeti42 posted:

 I've only got a quick start guide to go on.

Have you looked at the Core web page? There's some extra info (instead of a full manual, I think) in the support section at the bottom of the page.

Phil Harris this one is for you....

OK, so I have a Core on 24 hour loan from my extremely helpful and accommodating dealer (because I thought it might do the job of an Atom now I have to wait another xx months) but I have some issues you may wish to help with or comment upon.  I've owned a Unitiserv since they were first released which I've mastered, love to bits and use on a daily basis. (over 5,000+ CD's ripped so far)

The Core is working OK with a USB stick plugged in the front, I have music playing from the digital output no problem.

1.  The Core cant seem to find my Synology NAS drive shares? Every other piece of hifi gear I have does with no issues, I am being stupid? is there something I need to do with the app for this to happen?

2.  I couldn't see a place where to directly enter the NAS shares url into the Core app, is there such a facility?

3.  I'm aware that there is currently no metadata editing right now but when there is will there be a PC application similar to what I currently use with Unitiserv? or will it be app based only? This is a deal breaker for me and I fact I can't sleep at night because of it.

4.  Why is the app so Spartan (features wise) compared to the *old* nserve app I used with Unitiserve?

Yours
JK

... and will Cores ever be delivered to Scotland (preferably before the 2nd referendum?!)

Cheers,

Stefan

Christine:

For a SYNOLOGY NAS drive:

 instructions are for current DSM 6.0.2-8451 Update 9

 Open DSM

Open Control panel

 Open File Services

Under ‘’Win/MAC/NFS’ : click ‘’enable Windows file service’’

 Open Advanced Settings

Click: ‘’Enable Local Master Browser’’

 Save it by clicking APPLY

Reboot your NAS drive(s).

When it is back on line (Status light green), reboot your Core: stand-by then pull the plug, wait 1 minute, re-plug it.

 Restart the Naim app (kill it and restart it new)

After about 5 minutes you should be able to see your shared folders, to enable your music shares and to promote some folders to Music Store

hi, cores are shipping everywhere at present

Trevor

What about the Atom and the rest of the range?

JK, it's possible that Phil may not see your post quickly so if you have any specific operating issues then best send an email to Naim support.

Phil will say the same thing as me...

MANU - Thank you for your reply, I can see how that would help but my problem was much more easily solved.  I simply had to reboot the network switch that the Core was connected to, even though every other network device using the same switch could access the Synology with no problems.  I can only guess that the switch had locked up the IP address of the Core at some point during initial installation.

Here is some initial feedback on Core, some of which I have already informed Naim about.

1.  The ripping speed of Unitiserv and Core is almost, to the second exactly the same speed, although thankfully the Core doesn't spit out the CD's like my Unitiserv does.

1a. Inserting a CD into the slot on a Core is slightly more difficult that the US, I've ripped 5,000 or so CDs on a US so far and can do it without looking.

1b.  For now due to the desktop software not working and the lack of Metadata editing I'm going to continue using my US to rip and the Core as a streamer / front end only.  When I rip a CD with US after a short time it automatically appears as a new CD on the Core app.

2.  The sound quality of each rip (US and Core) to the naked ear are identical but the file size produced is a bit bigger on the Core.  I've been informed by Naim that the Core produces better rips? Has anyone done a bit test or more in-depth comparison yet?

3. There is no power switch on the back of the Core, I wonder why?

4.  There is no web-page based app software on the Core like there is on US, I do hope this comes over time.

5.  The Desktop software for the US recognises automatically rips that have been done with the Core, but unfortunately if you try to right click to edit the metadata it won't allow you to do so.

6.  Whatever you do don't rub the Core with your hands otherwise you'll get a strange white mark on the unit which you can only remove with the supplied cloth.  Very strange!

7.  The ripping monitor part of the app doesn't work properly with the tracks list being ripped changing at random, although this doesn't affect the ripping in any way that I can see.

8.  For some reason rips with the Core name the album artwork coverfront.jpg and not folder.jpg as per US, which means that if you play an album with Windows media player (and perhaps other players) the artwork doesn't show.

I have much more to say but didn't want to make this post too long.

JK

I am finding that US files copied to the Core's internal hard disc and then played back by the Core via upnp streaming to my SuperUniti sound different to the same files played the same way from the US. The Core is a little brighter, even brittle sometimes. A friend who has done the same comparison on his system found the same difference. He prefers the Core but I'm not sure that I do. Anyway they do clearly sound different to each other.

best

David

Burn-in issue? Why not using the SPDIF connection if you are playing from an internal HDD? Have you compared SPDIF SQ with RJ45's? 

Chag -

Chag... posted:

Burn-in issue? Why not using the SPDIF connection if you are playing from an internal HDD? Have you compared SPDIF SQ with RJ45's? 

Chag -

Because it's in a different room. I have streamers all over the place....

Christine posted:

 

1.  The ripping speed of Unitiserv and Core is almost, to the second exactly the same speed, although thankfully the Core doesn't spit out the CD's like my Unitiserv does.

 

JK

 

 

 

The record eject for my UnitServe is 0.74m!

My core ejects the disc at the end of the rip

But not across the room I hope, though it would be funny.

There is a Major problem which how the app stores and indexes your music library.

I've got it pointing at my nearly perfectly arranged and metatag-ed Unitiserv share and the app randomly decides what to file the music under and how to display the track data.

Sometimes it takes into account the metadata sometimes not.

I'm currently trying to work out exactly what the logic is so I can report back to Naim.

For now they should implement a folder type browsing facility in the app (like you can do with a Sonos) because at least then I would be able to find my albums!!!

JK

Indeed across the room and this was after Naim had it in for repair! I've learnt to keep the carpet clear in front of the unit

Yes, it jumbled up my music albums, some are sorted under CD number, artist, work or composer, with no obvious logic.  Some of each disc's tracks are not sorted in the correct order either.  The sort under artist or conductor doesn't work.  I agree that until Naim introduces metadata editing, it should allow a folder browsing facility.  

I've worked out that the new Core App uses the cdddinfo.txt file as the source for album and track information and ignores the UserEdits.xlm file (which contains any corrections made manually via the Unitiserv desktop application)

This is totally different to the way the old n-serve app works which I believe ignores the cddbinfo.txt file and thus my metadata is perfect using the old app.

If I delete the cddbinfo.txt file from each folder then the new Core app displays my music data correctly.

So what we may need is an option in the new Core app to disable it looking at the cddbinfo.txt file if so required.

Alternatively I just delete all the cddbinfo.txt files from my complete music library???

Your comments please.

JK

The metadata editing is absent from the app at present. In the mean time can you rename the cddbinfo.txt so its still available should you need it later? 

Christine posted:

I've worked out that the new Core App uses the cdddinfo.txt file as the source for album and track information and ignores the UserEdits.xlm file (which contains any corrections made manually via the Unitiserv desktop application)

This is totally different to the way the old n-serve app works which I believe ignores the cddbinfo.txt file and thus my metadata is perfect using the old app.

If I delete the cddbinfo.txt file from each folder then the new Core app displays my music data correctly.

So what we may need is an option in the new Core app to disable it looking at the cddbinfo.txt file if so required.

Alternatively I just delete all the cddbinfo.txt files from my complete music library???

Your comments please.

JK

This isn't an app problem. I have both a Unitiserve and a Core and I imported the US music into the Core. The Unitiserve sees the Core as a music store (for some reason) and I can see two lots of music now when I stream using the new app if I look at the Unitiserve but only one if I look at the Core. The copy of the music stored in the Core has all the user edits in place if I stream it via the US but the default info which is often either wrong or unusable for other reasons if I stream it via the Core.

So this serious problem will need fixing by a firmware change in the Core. The app works fine.

best

David

Then it looks feasible to use the US or HDX as a possible front end for the Core (since JK and David said that the US see the Core as a music store). Not sure if this makes too much sense, but it's feasible, right?

Thanks,

Stefan

Christine posted:

Phil Harris this one is for you....

Hi,

As has already been flagged up, if anyone has a query for support then it is far better to contact us ( support@naimaudio.com / phil.harris@naimaudio.com / steven.hopkins@naimaudio.com ) than hope that we either see the posting in amongst everything else or that someone flags it up to us.

Christine posted:

OK, so I have a Core on 24 hour loan from my extremely helpful and accommodating dealer (because I thought it might do the job of an Atom now I have to wait another xx months) but I have some issues you may wish to help with or comment upon.  I've owned a Unitiserv since they were first released which I've mastered, love to bits and use on a daily basis. (over 5,000+ CD's ripped so far)

The Core is working OK with a USB stick plugged in the front, I have music playing from the digital output no problem.

1.  The Core cant seem to find my Synology NAS drive shares? Every other piece of hifi gear I have does with no issues, I am being stupid? is there something I need to do with the app for this to happen?

Try enabling the "Master Browser" option as has been posted up here already by Manu.

Christine posted:

2.  I couldn't see a place where to directly enter the NAS shares url into the Core app, is there such a facility?

No - this functionality does not exist...

Christine posted:

3.  I'm aware that there is currently no metadata editing right now but when there is will there be a PC application similar to what I currently use with Unitiserv? or will it be app based only? This is a deal breaker for me and I fact I can't sleep at night because of it.

There are no plans for any desktop application - portable device only.

Christine posted:

4.  Why is the app so Spartan (features wise) compared to the *old* nserve app I used with Unitiserve?

Core is a new product that will be built on and evolved over the coming years whereas the UnitiServe had had ten years of evolution and functionality bolt ons, aside from metadata editing (which is scheduled for the end of March), parallel MP3 creation (which is also due) and the loss of Internet Radio (not implemented as the Core is a ripper / server not a streamer) then there should be no other significant losses of actual functionality that I'm aware of. Are there any specific examples you can give me?

Best,

Phil

Christine posted:

MANU - Thank you for your reply, I can see how that would help but my problem was much more easily solved.  I simply had to reboot the network switch that the Core was connected to, even though every other network device using the same switch could access the Synology with no problems.  I can only guess that the switch had locked up the IP address of the Core at some point during initial installation.

As the app was still able to find and access the Core then I don't think it's likely to be specifically a "switch locking up the Cores IP address" issue. Does this network have any Windows PCs on it? It does sound like a Master Browser issue and if you do have any Windows devices then power cycling the switch could well have forced a re-election event which may have caused a resolution to the issue.

Christine posted:

Here is some initial feedback on Core, some of which I have already informed Naim about.

1.  The ripping speed of Unitiserv and Core is almost, to the second exactly the same speed, although thankfully the Core doesn't spit out the CD's like my Unitiserv does.

This is as we would expect but good to see it confirmed out in the field too...

Christine posted:

1a. Inserting a CD into the slot on a Core is slightly more difficult that the US, I've ripped 5,000 or so CDs on a US so far and can do it without looking. 

I think you'll get to the same point with the Core - I can mainly hit the slot without looking nowadays.

Christine posted:

1b.  For now due to the desktop software not working and the lack of Metadata editing I'm going to continue using my US to rip and the Core as a streamer / front end only.  When I rip a CD with US after a short time it automatically appears as a new CD on the Core app.

The Core accessing the UnitiServe music store as a share and doing a rescan as the UnitiServe updates its music store ...

Christine posted:

2.  The sound quality of each rip (US and Core) to the naked ear are identical but the file size produced is a bit bigger on the Core.  I've been informed by Naim that the Core produces better rips? Has anyone done a bit test or more in-depth comparison yet?

This has been discussed elsewhere however as the ripping engine is essentially the same underlying engine then the rips produced by the Core should be as good as those produced by the UnitiServe - both are capable of accurately ripping the audio data from a CD.

Christine posted:

3. There is no power switch on the back of the Core, I wonder why? 

Mainly because the core is intended to be left powered as it is intended to be used as a music server and should therefore be available permanently ... the unit can be put into "network standby" (front lights out but still servicing network requests) from the power switch on the front .

Christine posted:

4.  There is no web-page based app software on the Core like there is on US, I do hope this comes over time. 

It is not planned to support a web interface on the Core at this time.

Christine posted:

5.  The Desktop software for the US recognises automatically rips that have been done with the Core, but unfortunately if you try to right click to edit the metadata it won't allow you to do so. 

That's because the UnitiServe is accessing the "Music" folder on the Core as a read only "share" and therefore the UnitiServe won't be able to edit those files - your UnitiServe is accessing the Cores Music folder in the same way as it accesses its "Downloads" folder.

Christine posted:

6.  Whatever you do don't rub the Core with your hands otherwise you'll get a strange white mark on the unit which you can only remove with the supplied cloth.  Very strange! 

The Core does have a deep brushed finish which can pick up loose skin particles if you wipe your hand "across the grain" but it should wipe of easily with a cloth when wiped "along the grain".

Christine posted:

7.  The ripping monitor part of the app doesn't work properly with the tracks list being ripped changing at random, although this doesn't affect the ripping in any way that I can see. 

Could you possibly send me a video to show this as I'm afraid I don't understand what you are describing, in what way does the ripping monitor itself not "work properly". If you can give me some more information then I can look into it.

Christine posted:

8.  For some reason rips with the Core name the album artwork coverfront.jpg and not folder.jpg as per US, which means that if you play an album with Windows media player (and perhaps other players) the artwork doesn't show.

On the core we use coverfront.png as the cover art image file rather than folder.jpg.

Christine posted:

I have much more to say but didn't want to make this post too long.

If you have any specific issues then please contact us directly at support@naimaudio.com then we can attend to your queries in a timely fashion rather than having to keep an eye on this thread.

Best,

Phil

Regarding the track ripping monitor and Christine's comment, I don't see a tracks list at all on my Core. And it may start by ripping track 1of 14 say, then go to 2 of 14, all good so far, then it might go track 1 of 10, then track 6 of 14 then track 1 of 5.  And so it goes on. No artwork is showing usually, and then when you look after the disc has been ejected, and the rescan taken place, the correct 14 tracks show and the artwork is there too. (The above is a real example.)

best

David