Since recent update (3.12.0.5738) I can no longer rip CDs. I get a message ‘Disc contains no tracks’ and CD ejects. What is going on?
Have you done the usual: switch off, unplug power, make a cup of tea, then reboot procedure? If so, have you tried factory resetting your Star?
Roger
No, but I will try that. Thanks
Uniti Star..
Bug.
Thanks for the link.
I did try a reboot leaving it off at the mains overnight. Made no difference.
From all that I read this is a software problem. I’m really not into fiddling around with another HD as some have done, this is up to Naim to resolve.
I’d appreciate a link for reporting to Naim direct. I don’t know how to do that. Thanks.
Hi, you can report this issue to support@naimaudio.com. Anyhow, as this problem is relatively new and I have not seen many owners reporting it in this forum, they will most likely ask you to try a different HD to see if this changes things with the ripping capabilities of your Star. If you have a spare one (or an SD card), why not try it out and set it up as the „new“ storage adress and then see if you can rip a CD. Worked of me and for @SFguy, so I keep my fingers crossed for you. Cheers, Clemens
I received the following from naim NA on June 9th. I’m still good after renaiming my music store. Eleven days later and naim “engineers” haven’t figured out their mistake or come up with a resolution??? Anyway, you could try this, as relayed to me by my naim contact in Canada –
I have received some feedback from Naim UK.
They believe they have isolated the bug that is causing the issue, it appears that it changes the Drive Properties to Read-Only rather than Read-Write. They are working on confirming this and the applying and releasing a Fix.
In the meantime a workaround that may work is the following:
-
remove the drive and plug it into a PC
-
once in the PC, and it has been recognized
-
eject it and plug it back into the Star
-
this should get it operational
Please let me know if you attempt the above steps and the outcome, I will also keep you informed with developments.
Sorry to have taken so long to reply. I tried the work-around today and although the PC recognised the existence of a drive it didn’t appear in file viewer.
Sadly it hasn’t solved the problem: I will try again just to be sure but it looks as if I must wait for the bug fix.
I must say that as one who spent much of their life looking for bugs in a certain system it seems odd that Naim didn’t test what to me seems obvious before the release.
@CatsWhisker updated to 3.12 today and was met the same issue when ripping a CD. Followed @SFguy advice which resolved the issue ![]()
I’m ripping to a Samsung T7 1TB SSD
- Placed the Uniti Star on standby
- Disconnected the T7 Drive
- Connected the T7 Drive to MacBook
- Accessed contents of the T7
- Dismounted the T7 from MacBook
- Connected the T7 to the Unti Star
I’ve not long ripped a CD with no errors. Playback of the rip flawless.
Hi
Yes I tried that a while ago, mounting on my iPad: it didn’t recognise the HD contents. Also tried on a W10 PC and neither did that recognise the drive contents.
Naim know that this is a problem but seem in no hurry to send out a fix. I can’t understand their customer-facing attitude. They might at least give us the opportunity to roll-back to the previous workable firmware but no, not even that.
I no longer recommend Naim to friends. It’s a pity, I really wanted to support a UK company.
Hi, I have a Uniti Core and started getting a similar issue. I don’t know how the Star works but I discovered the problem went away if I unplugged my backup drive from the core USB port. Don’t know why it caused issues with ripping but once I did that the issue went away. I just plug the backup drive in when I’m actually doing a backup.
If the Star has any other device plugged into it, maybe just disconnect while ripping and see if it works.
None of this may apply to a Star but thought I’d mention it just in case.
Hi. On my Uniti Star the external drive is what one rips to: there is no internal drive. So I can’t rip without the external drive connected.
I say again, though clearly no one from Naim actually reads these posts, give us the opportunity to revert to a working firmware version. Why should we have to find work-around to a commercial product? It really is not good enough.