Problems Using ROCK

Roon Core Machine

I have set up an NUC 16Gb M2 SSD 1tb with the ROCK image
This works - I can connect to the Web Interface

Networking Gear & Setup Details

Std lan - devices all ping and DHCP running

Connected Audio Devices

Working

Number of Tracks in Library

I want to add music files but cannot - see below

Description of Issue

I have connected to the Data directory using SMB and can read/write to this.
The web interface shows MISSING CODECS
I have downloaded the ffmpeg codec and copied this into Data/Codec/ and rebooted ROCK - still shows MISSING CODECS.

I can connect to the ROCK using Android and Apple - works but I now need to add my music files.
How do I do this for local storage? The roon app Storage tab only gives option for adding Network Storage.

Also - is it possible to connect to the device using SSH?

Many thanks,
JJ

Hi - if you want to use internal storage in your NUC you’ll need a second drive (presuming you have a ‘tall’ NUC - if you don’t, you’ll have to use external storage either connected via USB or across your network).
It’s not possible to use the drive ROCK is installed on for anything other than the OS.
As for ffmpeg - did you uncompress it twice? That’s caught a few folk over the years. It should simply be called ‘ffmpeg’ and be around 77mb.

Michael

First thing first, your 1TB SSD M.2 can only be used for ROCK OS. You cannot store any music files here. You have to use another drive (2.5" SATA drive for internal storage music files).

As a side note, you don’t need a 1TB M.2 SSD for ROCK OS. You only need a very small SSD for this.

Secondly, as far as adding a FFMPEG file, make sure the file is already uncompressed. Once uncompressed it’s name should be just ffmpeg and that’s it, without any file extension at all. If it has a file extension you might still to uncompress the file.

Once you copied the ffmpeg correctly to the Data\Codecs folder, you don’t actually need to reboot ROON. It will just work. You can verify by going to the Web UI and refresh the screen.

Hello Michael and Hogio,

Many thanks for your reply.

I can add a second drive (and use a smaller ssd for the OS) - problem solved.

I have uncompressed the archive ffmpeg-6.0-amd64-static.tar.xz using ARK

I get the uncompressed directory with ffmpeg in the root (no extension)

The ffmpeg file is not compressed - 78,683,840 bytes executable file.

This is the file I have copied - I don’t see where the second uncompress comes in.

Thanks for helping,

JJ

Info here about ffmpeg, including stuff about uncompressing twice:-

If it’s still not clear (Roon mean well but sometimes their documentation needs tweaking!) let me know and I’ll upload my copy to wormhole and pm you a link.

Michael

This is fine. I assume the ARK you are using is the KDE tool on Linux? Keep in mind that’s not what the instructions are written for, they target Windows/Mac users without much knowledge, and I think on Windows one my have to uncompress twice (depending on the tools one uses), once the xv to a tar and then the tar to a folder. Though on Mac it’s not necessary either and the instructions could do with some improvement.

Putting the ffmpeg file into /Data/Codecs should suffice, like others have written.

Though it should not matter that you used a 6.0 archive, I noticed that you did. Did you try with the version that is recommended in the instructions, https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-amd64-static.tar.xz ?

And no, it is not possible to SSH into ROCK, it only runs the bare minimum of things. To copy music there, use SMB:

1 Like

Thanks to everyone who has helped here. This is much appreciated.

I still cannot get the codec ffmpeg recognised - using either of the files. This is odd.

Actually I have been testing the ROCK image against a Ubuntu minimalist server image on a server box with four NICs @ 2.5GHz (I use these as a standard box for firewalls)

I cannot detect any difference at all audibly on the results - both installations feed a Cambridge Audio, Kef LSX, Naim MuSo flawlessly.

What I will say is that the limitations of the ROCK installation really don’t cut it for me.
With the Ubuntu server I can log in over SSH and see what’s going on, I can have the music files on the same SSD as the OS (with an M2 SSD of 1Tb the OS overhead is meaningless at M2 speeds).
I can add monitoring software, team the four NICs, and run test software etc…
All works great.
And this is all running on a $120 server box from Alibaba at under 7 Watts!

I know that most roon users will not need this sort of sophistication, but this has been a great learning experience for me - I understand roon on linux far better now.
Roon runs ROCK or Ubuntu Server on a $120 box.

Roon is a superb product…I wonder if the roon engineers will give any insight into their minimalist linux image - that would be very interesting.

Best Wishes,
JJ

ROCK is precisely for the people who don’t want any/most of that and the complexity that it inevitably brings with it, architecturally. For everyone who wants these things, Roon Server on Linux is great and already exists :slight_smile:

2 Likes

Hey @john_gillies,

Ben with the support team here, thanks for taking the time to write in, and for your patience! I’m glad to hear you were able to get things set up properly on a different core.

I did want to mention - if you had an interest in continuing to troubleshoot this issue with your previous ROCK core, we would need you to bring the ROCK back online so we could connect and enable diagnostics on the device.

Let me know if this is of interest, and I’ll be on standby for your reply. :+1:

Hi Ben,
Many thanks for the follow up.

I was assessing a new mini machine to replace my existing Roon setup - an old linux box running Roon on the Debian based Openmediavault NAS server with ~30,000 music tracks (all flac - mostly studio quality).

New Machine -

  • quad core N5105 cpu
  • 16Gb memory
  • 2.5G ethernet
  • 1Tb M2 SSD
  • Passive cololing
  • 8W max power.

I first loaded ROCK on the new machine and this worked perfectly but I like to mess about with Linux and I found the restrictions imposed by ROCK limiting - additional drive needed, no ssh access (the reasons for which I fully understand and applaud).
So an interesting exercise - easy and fun to do.

I then installed the Ubuntu Server minimalist image on to the new machine, stripped out everything I did not need, and installed RoonServer + my music files on the single SSD.
(I rsync my music on the SSD with the old NAS server as a secure backup.)

Performs faultlessly - this is now my Roon server for the house - fast and power efficient.
I now no longer need any WOL requests for the RoonServer sleeping to curb power use (I have suggested that WOL would be a good addition to the Roon server/clients) - I can leave the new machine running during the day - it sleeps automatically overnight and wakes in the morning.

I use iPhone and Android apps (and the excellent Roon Linux cli client deveoped by Ronald_Record) to control Roon to four endpoints - high quality Audio Equipment.

Roon is a superb product - my music experience with Roon is just wonderful.

The only functionality that I do not have is the ability to add filters into the signal path - while this is a superb feature integrated into Roon, it can only be accomplished using a windows machine.
I do not run windows - it is far too buggy, resource hungry, bloated, expensive, insecure, lacks privacy and moves continually down the road of monthly rent with intrusive advertising.
I experiment with using VMs to run old win versions but sadly Roon does not run well on this platform.

Is their an upgrade to Roon planned which will allow signal enhancement without windows?
This would be an excellent enhancement to Roon.

Best Wishes,
JJ

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.