Kategorie: Software

Leave a reply

Checksum – Check

If you want to compare to folder, which are not based on the same system you can create to text files with an command and the compare them.

Linux systems use md5sum:

find . -type f -exec md5sum {} ';' >source_md5.txt
find . -type f -exec md5sum {} ';' >target_md5.txt

Mac systems use md5:

find . -type f -exec md5 {} ';' >source_md5.txt
find . -type f -exec md5 {} ';' >target_md5.txt

Then you can compare this files using following command.

diff <(sort source_md5.txt) <(sort target_md5.txt)


Leave a reply

Mac – not verified developer

In the last days I wanted to install LR/Mogrify 2 in my Lightroom Setup on my Big Sur MacBookPro. After the installation of the Plugin I got following error:

“magick” cannot be opened because the developer cannot be verified.

macOS cannot verify that this app is free from malware

and after this I got this message.

Failed to run Mogrify aborting export

You can fix it by open the Security Settings in your System Preference Panel and click on „Allow Anyway“

Security & Privacy

Leave a reply

AXLE MAM – proxy workflow

You can import pregenerated proxy files into your AXLE media asset management system. This can speed up your workflow, when you do not generate the proxy files on the same machine where your MAM is installed.

First you have to set the „Existing Proxies“ path in the „Advanced“ settings. There you can set the „Location of Existing Proxies:“ to a folder which AXLE should observe.

You have to rename your pregenerated proxy files with the prefix „DC“
example: austria.mp4 -> DCaustria.mp4

Keep the same folder structure like your highres material. The you can move the proxy files itto the import folder. Important you have to create a parent folder with the same name like your catalogs name.

After this you can move the highres material to the AXLE catalog. Depending on the amount of data it should now start to sync the proxy files. Every successful imported file will get an „.done“ as prefix.

The technical specification of the proxy file are „mp4 file h.264 codec with aac audio codec downmixed stereo – The video is 1MB/s 480p“ according to AXLE Support

Where to buy AXLE in Austria: Tools at Work


Leave a reply

auto-convert to h265

My NAS has a lot of old privat video files and I want to convert them to the new h265-codec to save a lot of space. First thing to say is that you need a lot of CPU Power to process the video transcoding. Plan is to create a script that search the folder structure and then convert the file, remove the old (mov or mp4 file) and replace it with the new h265 encoded file.

After some research I got to following:
with help of Marcel in this post and Thomas Böhm

CPU rendering

find * -type f \( -iname \*.mp4 -o -iname \*.mov \) -exec ffmpeg -i {} -vcodec libx265 -crf 18 -vtag hvc1 temp_{} \; -exec mv temp_{} {} \;

If you just convert one file you use following command:

ffmpeg -i <path_to_orignal_file> -c:v libx265 -vtag hvc1 -crf 18 <path_to_output_file>

You can change the setting -crf to optimise you output files bitrate
If you want to know more about it visit Werner Robitza Homepage LINK

Apple T2 Chip – faster transcoding

If you use an Apple Mac Device with an T2 Chip (most OS devices after 2018) you can speed up the conversation a lot by using the hevc_videotoolbox of ffmpeg. This will increase the speed more than 30 times, compared to CPU rendering. BUT the quality is getting really bad. I would recommend to use the classical CPU rendering.

ffmpeg -i <path_to_orignal_file> -vcodec hevc_videotoolbox -vtag hvc1 -crf 18 <path_to_output_file>

After some testing and playing around I created following script. The logging is in englisch and german mixed, sorry for that.

You need to install ffmpeg and exiftool (this will help copy the metadata of the original video file to the new created one, so you do not lose the creation date). On a Mac you can use Homebrew to install the packages.

First install Homebrew:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

then ffmpeg:

brew install ffmpeg

and now exiftool:

brew install exiftool

Now you can create a new shell script and copy the content into your empty file. Move the file to the folder which you want to transcode (take care the it will automatically do it recursive). Then you have to change the last line in the script to the folder path you have stored the script. Now you can start the transcoding with

chmod + x <your-script-name>
#and then
./<your-script-name>
#!/bin/zsh
# this script can help you to convert files in folders and subfolder to h265 files (using CPU rendering, you can change the ffmpeg parameters if you need)
# copy the script to the folder you want to convert files, and change the path in the last lines of the script
# you need ti have ffmpeg and exiftool installed. On the mac you can use Homebrew

mkdir ~/Documents/log

machwas() {
    wo_bin_ich=$( pwd )
    echo $date "bearbeite Ordner ${wo_bin_ich}/ -------" >> ~/Documents/log/H265_transcoding.log
    SAVEIFS=$IFS
    IFS=$(echo -en "\n\b")
    for f in *; do
        # fuer alle Ordner
        if [ -d "$f" ]; then
            echo $date "habe Ordner $f erkannt" >> ~/Documents/log/H265_transcoding.log
            (cd -- "$f" && machwas)
        fi
                if [ $(find $f -type f -maxdepth 0 -iname "*.mp4" -o -iname "*.mov"| wc -l) -gt 0 ]
                  then
                    echo $date $f 'is mov or mp4' >> ~/Documents/log/H265_transcoding.log
                    if mdls -name kMDItemCodecs $f | grep -q "HEVC"
                      then
                        echo $date $f 'is HEVC' >> ~/Documents/log/H265_transcoding.log
                      else
                        echo $date $f 'is not HEVC, starting to prozess the files ATTENTION' >> ~/Documents/log/H265_transcoding.log
  #                      echo $f
                        name=$(basename "$f")
  #                      echo $name
                        ffmpeg -i $f -vcodec libx265 -crf 18 -vtag hvc1 /tmp/$name >> ~/Documents/log/H265_transcoding.log
                        exiftool -tagsFromFile $f -api largefilesupport=1 -extractEmbedded -all:all -FileModifyDate -overwrite_original /tmp/$name >> ~/Documents/log/H265_transcoding.log
                        mv /tmp/$name $f
                      fi
                  else
                    echo $date $f ' this is not an video file of the type mp4 or mov' >> ~/Documents/log/H265_transcoding.log
                  fi
    done
}
    IFS=$SAVEIFS

# Aufruf des Ganzen
cd  /Users/admin/Movies
machwas

Maybe I will get time in the next weeks to change the language to english and optimize the workflow.


Leave a reply

WireGuard VPN – Ubuntu Server

WireGuard is the most modern and easiest way to go if you want to create an VPN Server. The guys from PiVPN created a great installer for RaspberryPi’s. But I need some more Power 🙂 So here is the fast installation guide for this:

Update and Upgrade your Server

sudo apt update
sudo apt full-upgrade

Install all needed packages

sudo apt-get install --assume-yes iptables-persistent dnsutils iptables-persistent wireguard-tools qrencode  net-tools

Now you can use the pivpn.io script to install

curl -L https://install.pivpn.io | bash

After the successful install you can create the user by typing

sudo pivpn -a

now you can edit the user profile you have created right now

nano /home/pi/configs/vs_mbp.conf 

If you leave the last line „AllowedIPs = 0.0.0.0/0, ::0/0“ like it is. Every traffic will be routed in your WireGuard VPN. If you want to have only the packages for the destination network routed you have to change it to your ip address range. For example: AllowedIPs = 10.210.0.0/24

[Interface]
PrivateKey = kPcrDnyRhjhNh+g6x3iqSR6DrFj0jRiR2GbUNgc1qFDxx=
Address = 10.6.0.2/24
DNS = 10.210.0.1, 1.1.1.1

[Peer]
PublicKey = YoKGLSuXRxv2WcaSzyVCDkIRqCW+BxHuK5VYvZg/7w0=
PresharedKey = hPvRvm5DqEreE8EXydEczi9R7Ygn4qKcrVKAVxvgH+W8=
Endpoint = X.X.X.X:51820
AllowedIPs = 0.0.0.0/0, ::0/0

I tested this installer with an Synology Virtual Machine Manager and Proxmox installation

If you don’t install the needed packages then you get following errors:

:::
::: sudo will be used for the install.
::: Hostname length OK
::: Verifying free disk space...
:::
::: Checking apt-get for upgraded packages.... done!
:::
::: Your system is up to date! Continuing with PiVPN installation...
:::    Checking for git... already installed!
:::    Checking for tar... already installed!
:::    Checking for wget... already installed!
:::    Checking for curl... already installed!
:::    Checking for grep... already installed!
:::    Checking for dnsutils... not installed!
:::    Checking for whiptail... already installed!
:::    Checking for net-tools... not installed!
:::    Checking for bsdmainutils... already installed!
:::    Checking for iptables-persistent... not installed!
/usr/bin/debconf-apt-progress: can't open /tmp/tmp.0xfbAZFK8b: Permission denied at /usr/bin/debconf-apt-progress line 249, <STDIN> line 3.
:::    Failed to install dnsutils!
:::    Failed to install net-tools!
:::    Failed to install iptables-persistent!

Durch die weitere Nutzung der Seite stimmst du der Verwendung von Cookies zu. Weitere Informationen

Die Cookie-Einstellungen auf dieser Website sind auf "Cookies zulassen" eingestellt, um das beste Surferlebnis zu ermöglichen. Wenn du diese Website ohne Änderung der Cookie-Einstellungen verwendest oder auf "Akzeptieren" klickst, erklärst du sich damit einverstanden.

Schließen