Adding high res files to hdx or other naim servers

Claus,

Naim players with storage unfortunately does not allow import of files. I have found a way of bypassing this restriction, it works at least with Naim downloads. I am not sure if I would be allowed to explain it in this forum. However, I strongly urge Naim to provide this as a standard feature. It would add so much to the versatility of these players.

I would suggest a USB memory stick...

Phil

Is there not also the restriction that the Naim unit's internal drives can only store / play WAV files?

(Or does that restriction only apply to the HDX?)

A true hi-res download file is not guaranteed (in fact I'd say is unlikely) to be be a WAV one .....

Correct - the internal drives are only to be used for the storage of ripped CD audio files. Similarly any network shares that are being used as stores should only be accessed and modified by the HDX / NS0x / UnitiServe and not be modified or accessed by any other process.

Music that has been downloaded or obtained from other sources (such as having been ripped using another application) should be stored on either a shared network folder or a USB memory stick (however the USB memory stick is probably the easier of the two).

Cheers

Phil

Hi Tog,

Not really - the only real restriction is that the internal drive / ripped CD store structures are just to be used for the servers only ... any downloaded music / music from other sources can still be used by the system via either USB memory sticks or network shares.

It should simplify things - a store you leave alone - a share you can do what you want with.

Phil

Hi,

I do agree with Tog, I would like there to be a mechanism to load my hd files into the server. Although I have a NAS box I would like to store my music where I want and not be forced into a choice. I could then have the benefit of a single place where the rips are stored (and hence backed up from) and single unified track database utilising the extended database. At the moment, some of my files (especially those not purchased through Naim) seem a bit like second class citizens.

Thanks,

Rich

Mind you, as I recall, the usable storage capacity of the on-board HDD in my early(ish) HDX is only 400GB (which is then backed up every night internally on to an identical disk / partition of equal size). 

This capacity is so limited that I already had to to define an external store on a NAS device for the files resulting from the ripping of ordinary CDs.

So there'd be no chance to fit hi-res downloads on there too, especially not the monster ones that one sees with 192 kHz or even 96 kHz sampling rates. 2 GB per album is not unknown at this resolution level .....

That prompts a new question for the Naim support folk: have you yet managed to identify a suitable replacement *larger* internal HDD on to which I could migrate? If not, is there any outlook yet for when this might happen?

Since the original 400Gb units we have moved to 500Gb twin drives and now the HDX currently uses a single 1Tb drive and no secondary backup drive...

Phil

Phil,

I agree with you that having to use a memory stick or a NAS for downloaded music is not a serious restriction and not a loss of convenience, especially given that Naim Servers treat stores and shares equally well. The only reason to wish to migrate your files to the internal storage would be if you believe they would sound better that way. I tried this and will report on that next week. What was interesting for me, when I studied the file structure of the HDX Music Store on my laptop very carefully, and when I studied the files included in the Naim Label downloads, I seem to have found a hint that Naim may be planning an upgrade for its servers which would enable them to store Naim downloads internally. May this be true?

(It should be noted again, that Naim warns strictly against accessing and modifying the Store Folders, and whoever does this takes his own risk and should not complain by Naim!)

I carried out as much testing as I could to be sure (in my ears) that a file played from a store on NAS sounded identical to one played from a store on the internal HDD. If anything the NAS sounded better but I thought that was a silly notion so concluded that NAS = HDD for music stores - i.e. CDs ripped on the HDX. It was at this point that decided to do away with the HDD altogether and had the HDX converted to SSD. 

HiRes music obtained from downloads was stored on a USB drive but indexing and playback can be flaky. From what I can determine this is down to the size and type of USB device. So I simply have a share on the NAS containing my HiRes material. It's on the same NAS HDD as my music store so is backed up with everything else. This is a nice seamless way of browsing music on the HDX but if I wish to I can browse music by device which allows me to flip from store (serer) to share. I seldom use this unless checking something.

I can't think why I would want to mix everything together when it affects the operation of the HDX and its software. And the way the albums are presented when browsing there is no need to. Did we take our favourite CDs, rip them, store them, add in other music files in different formats from other sources, burn them all back onto a CD, load it in and then bitch when it didn't play? If we want more DIY facilities we have perhaps been hasty in purchasing a Naim solution which has been developed to be robust and not impose unnecessary comprimises.

In my opinion, having a single store (either on-board or off-board) simplifies my music storage, results in less management for me, gives me a single way to manage all of my music and simplifies my backups.

All I would like is a simple mechanism to upload files to the store via the HDX (thus preventing any corruption to the store). I would also benefit from the enhanced metadata that the HDX rips get but my network shares don't have.

I don't think that uploading purchased files is really a DIY solution, this is a common way of purchasing music and the only way to source HD files. As long as the upload mechanism prevents corruption of the database, I don't see how this is a compromise? Naim have listened to users about the HDX in the past and one of the benefits of owning one is that its functionality has steadily improved.

Older units can be updated to 1Tb and your dealer can arrange this or you can send an email to support@naimaudio.com for details...

Cheers

Phil

Phil,

As you see, there are actually quite a number of requests on that direction. I can add myself, too, since I don't have a NAS and I don't plan to own one in the near future. This feature could save some of us the investment on a NAS, and would be very practical. 1Tb is quite a big storage capacity for many of us with more modest music collections.

John,

According to HDX terminology, the folder where you hold your rips is called a "store", and the folder for your other music is called a "share". There is absolutely nothing inconvenient about this approach. On the contrary, it is a perfectly convenient database system if you already have a NAS. The discussions above referred more to members who do not have or wish a NAS.

Just plug a USB drive into the HDX. It's so easy and it does not interfere with the HDX's ripped/compiled data. As above, I don't understand why anyone would want to do this.

I guess the difficulty for naim is they could have a 'share' on the HDX or what ever that you could dump music into, but by its nature it would have to be either dynamic in terms of size or the user would have to dictate a size (partition) in order to achieve this,

It then becomes how long is a piece of string.

Hi funny,

The answer to your question is that although physically your 2Tb drives are the same dimensions as the 400Gb drives in your HDX it is not viable to simply replace one with the other.

Cheers

Phil

Would just like to add my support to the request for the Naim database to be able import music, e.g. hi-res downloads.  I have a 1TB HD Unitiserve, and with a modest CD collection have only used 1/3 of its capacity thus far. Of course, the combined database would have to be robust - if this isn't possible and there is a risk of b-----ing up the database then I wouldn't want it. 

Paul