Did you ever find the time to make it work on 22.04? I just recently started to try and get the server to work on 20.04 but having massive issues with X11 display not being available, since it is an ubuntu server. How did you get around this in your version?
Would love to see some in depth knowledge. It is something NRK has done that is unique to make it work on a server?
Blood, sweat and tears Honestly, I don’t remember. It’s been too long.
Not sure I understand the question. NRK version is based on the older CasparCG version. We are using it because we need more than 8 channels of audio, which the current CCG version can’t do.
The official 2.4 builds provide scripting for building for 22.04
I don’t expect there to be any more work on 2.1nrk, we are moving across to 2.4. We also didn’t try it on Linux, so I can’t help on getting that building or running.
Thank you all for the replies. I will continue tinkering with X11. My question about NRK was if Dimitry had done some amazing discovery in his build of ccg.
And I am aware that NRK Sofies upgrades are merged with the main branch.
The files on the build server are the results of adding a commit to the code base. These may be minor bug fixes or new functionality. The new functions may not have been through the rigourous testing applied to a stable release versions on the project releases page, but they can be as stable as such a release, but with extra features/functionality added to the base code.
The builds server means you can access a casparcg server version that has extra capabilities, but the end user is responsible for checking the stability of the version before releasing that version into day-to-day use - just as we should do with any software.
You can find out more about one of the files in the builds server through the commit history for the project. At the time I typed this note one of the files near the top of the builds for the server master branch is named:
The first 7 characters of the long string after “casparcg-server-” are a hook into more information. So in the above example the significant characters are d386856.
We now look at the project code home page, https://github.com/CasparCG/server, in this instance. A screen grab from part of this page this is shown below.
There is a tick mark towrds the right of the lower line, followed by 7 letters - in this instance the same letters that we see in the file name (d386856). Clicking the 7 characters switches the display to show the code changes applied to the source files. There is more detail from the commit process, in this instance the headline of the change (feat: Artnet Consumer) and a link to the discussion page about this feat (#1491). The has number is the Issues reference number.
If the build of interest is not at the top of the code page, you can click on the number of project commits (as displayed at the lower right of the screenshot above). This links to the list of commits for the project. You then need to find the 7 character value from the file name in the list of commits. The usual browser search can help locate on a page. The build data on the builds server can assist in finding the correct page in the commits history.
Hope this helps you find more information about the builds.
I actually got the server running on 22.04. I now know what you mean with blood sweat and tears. Using xorg, blackbox and rxvt-unicode as per your tips here: