The core problem is that many movies have the audio mixed for a movie theatre with multiple separately controllable audio channels. You might see this marked as 5.1 ; DTS; etc. In a typical home environment, you only have stereo sound. This means that the multiple audio channels have to be mixed down to two unless there is a separate stereo audio mix channel provided - basically never except commentary tracks. The shitty way to do it is to just take the left and right front channels which are mainly meant for sound effects and not bother to mix in the center channel which covers the dialogue. It’s still hard even if you mix in some of the centre channel.

Short version: asshole movie makers mix only for movie theatres, not stereo.

That’s Steve McQueen on the left. In the white shirt and glasses

https://en.wikipedia.org/wiki/M-DISC

Looks like it’s too easy to delete. I click on the link and I get a not found exception

Welcome

Depends what you want to play it on. In my house we have:

3 laptops 2 tablets 2 mobile phones (1 android, 1 iPhone) TV

Not all these devices support local storage for music and it’s a pain to sync files between them. With Jellyfin the complete library is in one location with a consistent interface. It can also be made available remotely if I choose.

Not how it works- licensing will be through a third party agency

GitLab just doesn’t compare in my view:

To begin with, you have three different major versions to work with:

• Self-Hosted open source
• SAAS open source
• Enterprise SAAS

Each of which have different features available and limitations, but all sharing the same documentation- A recipe for confusion if ever I saw one. Some of what’s documented only applies to you the enterprise SAAS as used by GitLab themselves and not available to customers.

Whilst theoretically, it should be possible to have a gitlab pipeline equivalent to GitHub actions, invariably these seem to metastasize In production to use includes making them tens or hundreds of thousands of lines long. Yes, I’m speaking from production experience across multiple organisations. Things that you would think were obvious and straightforward, especially coming from GitHub actions, seen difficult or impossible, example:

I wanted to set up a GitHub action for a little Golang app: on push to any branch run tests and make a release build available, retaining artefacts for a week. On merging to main, make a release build available with artefacts retained indefinitely. Took me a couple of hours when I’d never done this before but all more or less as one would expect. I tried to do the equivalent in gitlab free SAAS and I gave up after a day and a half- testing and building was okay but it seems that you’re expected to use a third party artefact store. Yes, you could make the case that this is outside of remit, although given that the major competitor or alternative supports this, that seems a strange position. In any case though, you would expect it to be clearly documented, it isn’t or at least wasn’t 6 months ago.

It’s very mass market, not particularly well informed general news source and this is a specialist community where this is relevant to its specialist field

Zim desktop wiki? I’ve used it for years. Cross platform, open source, lots of features. Bear in mind that there are a lot of plugins, including one specifically for journaling

Coming from what looks to me like a different perspective to many of the commenters here (Disclosure I am a professional platform engineer):

If you are already scripting your setups then yes you should absolutely learn/use Ansible. The key reasons are that it is robust, explicit, and repeatable- doesn’t matter whether that’s the same host multiple times or multiple hosts. I have lost count of the number of pet Bash scripts I have encountered in various shops, many of them created by quite talented people. They all had problems. Some typical ones:

The thing about Ansible is that it can be modular (if you want) and you can use other people’s code but fundamentally it runs one step at a time. You will know for each step:

• Are dependencies met?
• Did that step succeed or fail (in realtime!)?
• (If it failed) what was the error?
• (Assuming you have written sane Ansible) you can re-run your playbook at any time to get the ‘same’ result. No worries about being left in an indeterminate state
• (To an extent) It is self-documenting
• Host architecture doesn’t really matter
• Target architecture/OS is specified and clear

Great location for a music video

Are you able to provide an example as to how greater complexity makes it easier

Edit: Thanks for the explanations. I get that multiple languages use gendered nouns to mean something that is clearly not ‘gender’ in the biological sense but key to understanding context. Seems strange as an English speaker where noun gender is vestigial if it even exists at all and even then it doesn’t matter if someone gets it wrong

I think there’s a clear reason why the setting would be depressing for ‘the boy in the striped pyjamas’

Look into ssh

Blogrolls and webrings