Linux Tips

[ChuckPa]

Transcoding and tone mapping with JasperLake / ElkhartLake CPUs

This tip / How-To is entirely NOT-SUPPORTED by Plex.

You, as the system’s owner/admin assume all risk/liability for the kernel integrity

It may work for you and it may not. There are no guarantees.
There has been success with for some users. Your results may vary.

This How-To is written for Ubuntu/Debian distributions but should be applicable to others.

1. Replace inte-media-va-driver with intel-media-va-driver-non-free

2. As root:

echo "options i915 enable_guc=2" >> /etc/modprobe.d/i915.conf
update-initramfs -u

3. Restart the host to make active

Forum Reference: Can Jasper Lake N6005 use hardware transcoding?

Back to top

[ChuckPa]

OpenSSL v3.0.0 and PMS.

For those using their own domains and certificates with PMS ,

PMS 1.32.0.6865 and above updates OpenSSL from v1.1.1 to v3.0.0 .
(changed the numbering scheme in the process)

The consequence of this is OpenSSL v3 removed several “less secure” encryption methods.

The impact on you, if you’re using an older distributions where openssl v3 is not the default, if not already doing so, you will need pay special attention to how your certificates are generated

As example, upgrade (specify) a better encryption

PREVIOUS

# Generate  p12 (Acme LE is valid until 2025)
openssl pkcs12 -export -out my-fdqn-tld.p12 \
	-inkey my-fqdn-tld.key -in my-fqdn-tld.crt \
	-certfile CertAuth.crt \
	-password pass:PASSWORD_HERE

IMPROVED

# Generate new p12 (Acme LE is valid until 2025)
openssl pkcs12 -export -out my-fdqn-tld.p12 \
	-certpbe AES-256-CBC -keypbe AES-256-CBC -macalg SHA256 \
	-inkey my-fqdn-tld.key -in my-fqdn-tld.crt \
	-certfile CertAuth.crt \
	-password pass:PASSWORD_HERE

The key change is to select a better encryption:

-certpbe AES-256-CBC -keypbe AES-256-CBC -macalg SHA256 \

To implement

1. Update certificate creation scripting to include AES-256 (or better) as shown above.
2. Regenerate P12 file and store where PMS expects it
3. Restart PMS after updated cert installation ( PMS loads certs at startup only)

The reason for this change is the inevitability of the current libraries being EOL.

Observe:

REF:

OpenSSL

Back to top

[ChuckPa]

Selectively changing directory and file permissions.

PMS 1.31.1 and above monitor your media for file permission changes in addition to media content changes.

This was provided so PMS knows when your media acquisition processes (DVR/other tasks) complete and the media is now ready for PMS to use.

Unfortunately, a number of our users have a “sledgehammer” approach where they just change all permissions for all media.

PMS is now sensitive to ALL permission changes (even for media already matched).

This results in the scanner activating.

The solutions here are:

1. Have your post-processing task apply permissions correctly to the item(s) you’re adding as you add them

2. Should you need to apply bulk changes, (which should be rarely), below is how to change only those files and directories which don’t match the desired permissions.

The two ‘find’ commands below scan for files whose permissions do not match the mode given and then performs a targeted -exec on that single file or directory to set to the appropriate value.

(Change the permissions below to be appropriate for your usage.)

find /directory-top -type d \! -perm 0755 -exec chmod 755 {} \; 
find /directory-top -type f \! -perm 0644 -exec chmod 644 {} \; 

Back to top