2. X11 is outdated. Wayland is the de facto standard SINCE 15 YEARS! Using legacy software is a narrow usecase you may wanna do, but no beginner should use quasi End-of-Life software with outdated languages and featuresets and security and performance and compability...

3. as I stated, these modern Kernel flags apply to 6.14 onwards which is already "the oldest" 6.x Kernel as its the Long-Stability Kernel with every Distro...
You are supposed to have AT LEAST 6.14 or higher by now, up to 6.17.

Not exactly. Ubuntu Mate is quite popular, and for a project like this the LTS is absolutely needed because you want to "set and forget" and not having to reinstall and reconfigure things at all times. The most recent version is therefore 24.04 (which last time I tried had serious bugs which made it unusable) and the previous version is 22.04 which is supported until 2027 (see https://ubuntu.com/about/release-cycle for details).

Ubuntu Mate v22.04 uses x11 and runs Kernel 5.15 and works wonderfully well with Pianoteq. No need to chase the latest and greatest as far as I can tell.

Hello,

What should be really replaced in README_LINUX file is the reference to "cpufreq-set": in Debian this command is part of the package "cpufrequtils" that is not available anymore since Debian 13 Trixie.

...
just X11
...
With the two different kernel types installed, I can easily switch between both during boot (from Grub menu), and I'm able to "feel" noticeable difference in latency between PREEMPT_DYNAMIC and PREEMPT_RT kernels (version 6.12 in Debian 13;"

Mate... how to tell you really friendly because we are all PTQ and Linux lovers, that you wrote a bunch of stuff that is pretty bad advise:

1. Changing the Readme, for some boring util like cpufreq but saying all the rest is fine, is batshit crazy. Its just different pkg, if that was "hard" or "important" for you, than it shows some lacking priorities at best.

2. X11 is outdated. Wayland is the de facto standard SINCE 15 YEARS! Using legacy software is a narrow usecase you may wanna do, but no beginner should use quasi End-of-Life software with outdated languages and featuresets and security and performance and compability...

3. as I stated, these modern Kernel flags apply to 6.14 onwards which is already "the oldest" 6.x Kernel as its the Long-Stability Kernel with every Distro...
You are supposed to have AT LEAST 6.14 or higher by now, up to 6.17.

4. you (more or less legit) focus on some project you have with your debian setup + touch + whatever script. Yeah. Nice. But thats nothing universal.
Thats your distro + your usecase of 7" touch with no pointer ... whatever. Its welcome addition, but its not focusing on "how to make good sound with linux: latency + performance + no artifacts". So I hope every beginner who may gets confused by your post finds comfort in my words: Skip everything he said, go back to what I stated if you want performance in an actual production system that uses other modern software too.

5. Ps.: ALSA with no pipewire means you can only have 1 simultaneos audio source and it controlls everything.
So you need to run pipewire anyway... or do you wanna use legacy jackd2 and pulseaudio again and have the same issue everyone had the past 15 years that setting up all the different programs and audio services in parallel is hell of a mess and requires maintenance work with every new app you add? No. So pipewire it is anyway...

What should be really replaced in README_LINUX file is the reference to "cpufreq-set": in Debian this command is part of the package "cpufrequtils" that is not available anymore since Debian 13 Trixie.
In replacement, package "linux-cpupower" has to be used and the new command is:
$ sudo cpupower --cpu all frequency-set --governor performance

For the rest of the file README_LINUX, in my opinion it should remain as it is.
I'm using Pianoteq as embedded hardware in x86_64 mini pc running Debian 13 with no environment desktop, no window manager or tiling, just X11 in a 7 inch touchscreen and launching PTQ automatically during startup.

My procedure:
1) debian minimal install from "netinstall" or mini-gtk.iso with no desktop installation during "tasksel": I uncheck Desktop and Gnome, and check SSH server.

2) After installation, I create autologin files for tty1, tty2 and tty3:
file 1: "/etc/systemd/system/getty@tty1.service.d/myname-autologin.conf"
file 2: "/etc/systemd/system/getty@tty2.service.d/myname-autologin.conf"
file 3: "/etc/systemd/system/getty@tty3.service.d/myname-autologin.conf"
with following contents:
[Service]
ExecStart=
ExecStart=-/sbin/agetty --skip-login --nonewline --noissue --autologin myname --noclear %I $TERM
Type=simple

To switch between tty1, tty2 and tty3, just press:  CTRL+ALT+F1, CTRL+ALT+F2 and CTRL+ALT+F3

3) Reduce Grub delay to 2s instead of 5s:
$ sudo sed -i.bak 's/^GRUB_TIMEOUT=.*/GRUB_TIMEOUT=2/' /etc/default/grub
$ sudo update-grub

4) Install X11 + Alsa + CPU power
$ sudo apt -y install xinit alsa-utils
$ sudo apt -y linux-cpupower

5) Just for fun (optional):
$ sudo apt -y install crystalcursors
$ sudo update-alternatives --config x-cursor-theme

6) some utils:
$ sudo apt -y install --no-install-recommends udisks2
$ sudo apt -y install polkitd
$ sudo apt -y install x11-xserver-utils
$ sudo apt -y install xbanish sxhkd htop 7zip

7) And finally, yes I install RT kernel:
$ sudo apt -y install linux-image-rt-amd64

8) Create the file:   "$HOME/.bash_login" with following contents:
if [ -z "$DISPLAY" ] && [ "$XDG_VTNR" = 1 ]; then
    if [ -d "$HOME/.local/bin" ]; then
        PATH="$HOME/.local/bin:$PATH"
    fi
    exec startx &>/dev/null
else
    . "$HOME/.profile"
fi

9) Create the file "$HOME/.xinitrc" with the following contents:
export XDG_SESSION_TYPE="x11"
export XDG_CONFIG_HOME="/home/myname/.config/"

# xset and xsetroot provided by package: x11-xserver-utils
xset s off -dpms
xsetroot -cursor_name left_ptr

# xbanish hides mouse cursor, I use PTQ with 7" touchscreen
xbanish -a &
XBANISH_PID=$!

# my keyboards shortcuts to hide and show mouse cursor, poweroff and reboot pc
sxhkd &
SXHKD_PID=$!

# cpupower provided by package: linux-cpupower
sudo cpupower --cpu all frequency-set --governor performance
/home/myname/Programs/Pianoteq/x86-64bit/Pianoteq\ 9\ --fullscreen &
PIANOTEQ_PID=$!
echo $PIANOTEQ_PID > /tmp/pianoteq.pid
wait $PIANOTEQ_PID
sudo cpupower --cpu all frequency-set --governor powersave

if [ -n "$(ps -p $XBANISH_PID -o pid=)"  ]; then
   kill -9 $XBANISH_PID
fi

if [ -f /tmp/pianoteq_upgrade.tmp ]; then
   while [ ! -f /tmp/pianoteq_reboot.tmp ]; do
      sleep 3
   done
   sudo reboot
fi

while [ -f /tmp/pianoteq_stop.tmp ]; do
   sleep 3
done

if [ -n "$(ps -p $SXHKD_PID -o pid=)"  ]; then
   kill -9 $SXHKD_PID
fi

sudo poweroff

10) Create the file "/etc/sudoers.d/01_power"
myname myhost = (root) NOPASSWD: /usr/sbin/poweroff, /usr/sbin/reboot

11) Create the file "/etc/sudoers.d/03_cpu"
myname myhost = (root) NOPASSWD: /usr/bin/cpupower

12) Follow indications in README_LINUX file: "/etc/security/limits.conf" and "sudo usermod -a -G audio myname"

With the two different kernel types installed, I can easily switch between both during boot (from Grub menu), and I'm able to "feel" noticeable difference in latency between PREEMPT_DYNAMIC and PREEMPT_RT kernels (version 6.12 in Debian 13; I didn't try yet the version 6.17 from backports...): my PC is connected to Kawai CA63 via MIDI over usb and a Focusrite 4i4 3rd Gen. General latency is lower with PREEMPT_RT kernel which I believe is managing usb connection better than Dynamic kernel (default).
PTQ performance still the same (perf. index)  with both kernels and I didn't notice differences with and without "taskset" command (Intel Core i3-1220P).
Sample rate: 192 kHz, Audio buffer size: 256 samples (1.3ms)
Performance index: 89, Internal sample rate: 48 kHz, Max polyphony: 256
Mini PC: Asus intel NUC12WSK
Touchscreen: Waveshare 7inch Capacitive Touch Screen LCD (H) with Case, 1024×600, HDMI, IPS
Audio interface: Focusrite Scarlett 4i4 3rd Gen

Hey Stephan,

you are trying to explain the basics of Linux there, mh?

Not to you. But now that most of what I had learned about Linux has been forgotten or faded into irrelevance except for historical context, I'm empathetic to some of the basic questions or issues that might be encountered by those who have just begun to explore the Linux environment.

OK-- Good point.

From Google AI:

you are trying to explain the basics of Linux there, mh?
While we are at it: "in a terminal window" -> in a Terminal Emulator There is no Terminal any longer.

Ive actually never stated why we want PW-Jack and whats about the quantum and rates:
Long story short is that when using the PW-Jack Interface, you have more features than with PW-ALSA.
In addition, I use it as kind of "Group" for Apps in Music Production: With using the PW-Jack Server everything connected via PW-JACK will run the same rates and quantum, which can be set globally.

So for the sake of completion to my prior advise:

1. Determ best Audio Output (aka Soundsink):
$ wpctl status           -> list all devices. Check your Soundsinks. They list some ID.
$ pw-cli enum-params <ID> EnumFormat    -> see supported formats/rates. The best is true F32LE (32Bit Float -> native Signal stays the same as long as possible) if you want to output to a digital device (like HDMI, DisplayPort, SPDIF, USB Audio). Some actual analog output can only use S32 (String Integer), so you want that. Many consumer grade devices, like my Dockingstation, or the CPUs own I/O Pins only allow for S24_32 which is the best you can do. Everything less than this (S24, F16, etc.) will have less and less "quality" and requires computation

$ pw-cli enum-params <ID> Format        -> check the actual used Format when a Soundsink is Playing sound.

-> Do this to find at best some F32 or S32 Output device and use it as your output (can be set by various methods, I like Helvum as Patchbay for that) to spare all unnecessary computation.

2. Setup PW-Jack Parameter:
https://docs.pipewire.org/page_man_pipe...hatgpt.com

Create directory for custom config files
$ mkdir -p ~/.config/pipewire/jack.conf.d
$ nano ~/.config/pipewire/jack.conf.d/YOUR-CUSTOM-NAME.conf

This is my actual file content:

jack.properties = {
  rt.prio = 88
  node.lock-quantum = true
  node.force-quantum = 128
  node.latency = 128/48000
  jack.show-monitor = true
  jack.merge-monitor = true
  jack.show-midi = true
}

Save the file - done.
(The name of the file doesnt matter at all, every file in the folder will be loaded and you can create multiple ones).

-> Restart the System (systemctl restart services, logout/login, ... they should work, but safest bet is to restart).

3. Use PW-JACK
use "pw-jack" command to start your Apps like PianoTeq. I use .desktop files anyway for my start menu, therefor it was easy to just put "pw-jack" infront the exec path.
To save you some trouble, this is my actual /home/USER/.local/share/applications/PWJACK_PTQv843.desktop file:

[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
Terminal=false
Name=PWJACK Pianoteq 8 STAGE
GenericName=Pianoteq 8 STAGE
Comment=Selfmade Desktop Shortcut for Pianoteq 8
Exec=pw-jack "/home/USER/Music/MX/Programs/PianoTeq/PianoTeq_8_Stage_843/x86-64bit/Pianoteq 8 STAGE" %F
Path=/home/USER/Music/MX/Programs/PianoTeq/PianoTeq_8_Stage_843/x86-64bit/
Icon=/home/USER/Music/MX/Programs/PianoTeq/Extras/modartt.png
StartupNotify=true
StartupWMClass=Pianoteq STAGE

4. Enjoy your Harmonized Production!

5. Double Check
use
$ pw-top
to check for the Quantum (Buffer Size) and Rate (Sample Rate) and Format (F32, etc) of your applications. PW-JACK Applications wont show any format -> they run F32LE globally.

Check in PTQ Options for Buffer Size and Sample Rate -> if working properly, it must show the values from ~/.config/pipewire/jack.conf.d/YOUR-CUSTOM-NAME.conf

Why is this solution my preferred?
My non-Music-Production Apps like Firefox, Spotify, VLC Player ... do not get resampled and use native Pipewire (or PW-Pulse or PW-ALSA) -> no performance loss, no quality loss, no glitching.
PTQ, Ardour, etc. use PW-JACK and run at the Rates/Quantum I desire.

Which Rate and Quantum you pick is another question and is smth. I would love to find other "geeks" explaining why their calculation is the best.

PTQ uses Quantum 64, therefor we would like to use 64.

48kHz Rate on the other hand would divide Quantum of 48 to a perfect 1ms block size (48/48000Hz=0,001Hz=0,001s=1ms).

USB2 SuperSpeed Poll Rates of 1kHz (48/1=48) would match this quite well too, newer USB3 8kHz Hardware (its quite some time ago that I researched the MIDI-USB specs, were they even allowing for 8kHz?) would match nicely too (48/8=6) so we have nice whole numbers and no integers which take more computation to solve neatly.

That is actually the reason why we dont want 44100Hz, or the Quantum 64.

That is why we have to find gcd/gcm and look for other combinations that are elegant: The easiest solution would be to increase the Rate to smth like 384kHz and than enjoy that many natural numbers would fit as factor/divisor to receive some neat Quantum value, but this idea is limited by actual computational power.

The 128/48000 on my Laptop offers great Performance - but the latency is quite weird with 128/48000=0,002666s=2.66ms and therefor mismatches with its blocks other I/O blocks like the ones by the USB-MIDI controller.

But thats maybe just me and my desire for elegant numbers - as Im not aware of too many people probing with lsusb -v -d what Intervals/Poll Rates their MIDI Controller actually use, in an attempt to optimize for that.

Cheers

The README.txt is obsolete! So are 99% of suggestions here!
This comes from people repeating again and again what they pick up along the way - which is prone to be outdated knowledge.
You can skip everything you've read before and take the following as your new "base camp" for further exploration:

I wish I could "upvote" Vepece's post 10x+
Even though I'm a long-time Linux (and occasional BSD) user since 2000, I need to update my linux/Linux knowledge base too. Thank you, Vepece.

The "$" above just represents the terminal prompt. The actual command to type is: groups $USER
"$USER" is just a variable that contains/represents and substitutes the username of the current user (your username).

If the pipewire group is not listed for your username, in a terminal window, using the sudo (temporary administrator) command, you could add your username to the pipewire group with this command:

sudo usermod -a -G pipewire $USER

You can read about the usermod command with:

man usermod

because I read good intended advise like "Have you checked the README_LINUX.txt file?" and similar thoughts like "Have wondered whether I might have liked Ubuntu Studio a little better for what music stuff I do on the computer." and advise like "1. Installing the Low-Latency Kernel:" I like to share my concern and advise:

The README.txt is obsolete! So are 99% of suggestions in the forum.
This comes from people repeating again and again what they pick up along the way - which is prone to be outdated knowledge. Ive actually participated back in 2023 by myself, trying LowLatency Kernels, 1000hz Rates and different settings back than when pipewire was still in its roots.

But you can skip everything youve read before and take the following as your new "base camp" for further exploration:

So why is the README/suggestions here outdated?
They do not take into regard that Pipewire is de facto the new standard - exp. with Distro Flavors like Ubuntu Studio.
Therefor, the "@audio" usergroup is of no concern any longer - since Pipewire 0.3, since Ubuntu 22 LTS!, since more than 3 years ...

The new usergroup we need to care about is "pipewire" and we need to build around that.

First of all, make sure you run pipewire.
Check if "/etc/security/limits.d/25-pw-rlimits.conf" exists.
If so, you will see it cointains the rtprio, memlock and nice values.

Nice is obsolete: nice (POSIX-Nice) is for RT-Threads (SCHED_FIFO/RR) irrelevant.
But we want to use newer scheduler, which is why the entire config_hz=1000 (aka lowlatency kernel, Ubuntu Studio, etc.) is obsolete too:
We use newer Kernel flags to dynamically make our kernel highres/lowlatency when needed - actually we make them tickless which is beyond 1000hz... - so a regular Linux Kernel >6.11?/6.14 does not need further tinkering.

To check if we got what we are looking for:

$ grep PREEMPT /boot/config-$(uname -r)

look for "CONFIG_PREEMPT_DYNAMIC=y" -> your kernel is dynamic.

So: Your Pipewire makes Jack/audio Group obsolete, and your Kernel the 1000hz. All it takes is to check if your user is in the pipewire Group:

$ groups $USER

if your in pipewire group, your set. if not, add yourself.

Now that we know we are in pipewire group, check your RTprio levels!

$ ps -eLo pid,cls,rtprio,ni,cmd | grep pipewire

If you see FF or RR as designation, this means he tries to acquire the SCHED_FIFO Scheduler and seeks RealTimePriority.
If you see a value of >20, (80 to 90 to 95) you know the pipewire group RTprio are working!

But if you see TS, you know he tries to connect via RTkit -> User not in Pipewire usergroup.
If your value is <=20, even when its in FF or RR, you know your accessing pipewire by rtkit, which is way slower in priority and means greater latency. -> Rtprio via Pipewire Usergroup not working.

Summary:
If you run a stock Ubuntu 24, NixOS 24, or any other modern Distro with pipewire, all it needs is to add your user to the pipewire group - no Ubuntu Studio, and not tinkering with creating audio groups or kernel flags/schedulers/rates is required.

The rest of the README regarding using a stable cpu frequency and performance scheduler are legit, and can be achieved by the suggested commands, or by GUI with packages like CPUPower-GUI which offer convenient profiles. https://github.com/vagnum08/cpupower-gui

Another suggestion the README does not suggest is to use taskset as explained here: https://forum.modartt.com/viewtopic.php...3#p974513)

Another suggestion the README does not contain is that pipewire-jack bridge is no default with many modern Distros, so installing that package, using the JACK Server within Pianoteq, setting up your global "Jack Server" Parameters in Pipewire, optimizing Sample Rates and Buffer Size, to harmonize/optimize the Quantum , and therefor "syncing the timing" in the µs range to fit each other optimal is not explained so far (Im not even sure if the forum contains it?).

Cheers

Professor Leandro Duarte wrote:

First, congratulations on your success!
Second, welcome to the Linux world!
I've been using Ubuntu Studio for five years and I don't plan on ever going back to the slavery of Windows!

Thanks! Loving Pianoteq and liking Linux, too.

Have wondered whether I might have liked Ubuntu Studio a little better for what music stuff I do on the computer. I had downloaded Zorin 18 for my wife and had been playing with that with her in mind. And she is doing great with Linux.

I'm fine with normal computer stuff... web browsing, bill paying, that kind of thing. But I've spent more time tweaking for low latency, figuring out JACK and other things that are not quite as plug and play as I'm used to.

The idea that Ubuntu Studio is already tweaked a bit closer to what I'd like... Pianoteq, Reaper, OBS Studio, some of that stuff, I have wondered if I'd like to give that a try. Just haven't taken the time to do it yet.

I'm curious, did you try other distros before settling on Ubunto Studio? AVLinux? QStudio64? Mint? Or others?

Yes, I've used Debian with Pianoteq. I'm familiar with Mint and Suse. But if Zorin is working well for you, there's no reason to switch. The best system is the one that does what it needs to do.

However, for experimentation purposes, I'm sure Ubuntu Studio will bring you pleasant surprises.

Pianoteq is exceptionally well-designed and compatible with Linux. The main issues are not with Pianoteq itself, but in tuning Linux for audio use. Linux used to use ALSA and Pulse as the audio-management backend, but most Linux distributions (including Zorin) have now switched to Pipewire, which is considered superior. So learning a little about how to set up the system and Pipewire is helpful. There are many useful resources on the Internet, and the user forum at LinuxMusicians.com can be very helpful.
LinuxMusicians Forum: https://linuxmusicians.com/index.php

The main fine tuning for Linux is to install a "realtime" or low-latency kernel (the heart of the Linux OS) that does (or can be configured to) prioritize audio and other tasks that need very fast response times from the kernel. It also helps to eliminate CPU frequency-scaling or to set it to operate a maximum by choosing the "performance" CPU governor.

For conveniently setting the CPU governor, I recommend the app cpupower-gui:
cpupower-gui: https://github.com/vagnum08/cpupower-gui

The cpupower-gui app is usually included in the list of packages for the package manager your "flavor" of Linux uses (Zorin I believe uses the Debian based package managers (apt, apt-get, synaptic) that are used by many Linux distributions such as Ubuntu and Linux Mint (my personal favorite).

--- --- --- --- ---

Note: Ignore the following and refer instead to Vepece's post below--

The linux-lowlatency meta-package (a package that includes and installs several related packages/apps) is a popular option to replace the standard linux kernel with a realtime/low-latency version. The Liquorix linux kernel (originally produced by gamers for gamers, but also widely used for audio work in Linux) also works great.
Liquorix kernel: https://liquorix.net/

Be aware than anytime a new linux kernel is installed, it's necessary to update grub (GRUB is the bootloader, the app that begins at bootup and allows you to choose which linux kernel you wish to use/launch, if not the default). Most of the time, when installing a linux kernel from a package manager, the GRUB bootloader is automatically updated by the installer, but if not (or if you didn't look at the output of the installer to double check, and want to make sure) you could update it manually, using the "sudo" command that temporarily elevates your linux username to "superuser" or administrator) using the commands suggested by Google AI below:

After installation, update GRUB to ensure the new kernel is recognized:
Code

sudo update-grub

First, congratulations on your success!
Second, welcome to the Linux world!
I've been using Ubuntu Studio for five years and I don't plan on ever going back to the slavery of Windows!

Thanks! Loving Pianoteq and liking Linux, too.

Have wondered whether I might have liked Ubuntu Studio a little better for what music stuff I do on the computer. I had downloaded Zorin 18 for my wife and had been playing with that with her in mind. And she is doing great with Linux.

I'm fine with normal computer stuff... web browsing, bill paying, that kind of thing. But I've spent more time tweaking for low latency, figuring out JACK and other things that are not quite as plug and play as I'm used to.

The idea that Ubuntu Studio is already tweaked a bit closer to what I'd like... Pianoteq, Reaper, OBS Studio, some of that stuff, I have wondered if I'd like to give that a try. Just haven't taken the time to do it yet.

I'm curious, did you try other distros before settling on Ubunto Studio? AVLinux? QStudio64? Mint? Or others?

The Windows 10 end of life thing happened here. And my computer did not qualify to upgrade to Windows 11. I installed Zorin 18 and have been happy with that but have not made the switch with Pianoteq 8. Currently, it's a dual boot setup as I wanted to be able to go back to Win 10 if I really screwed something up but so far have not even logged back into Win 10 since installing Zorin. Running on Zorin now and happy as can be! But it's the same computer and the same hard drive.

I'm not sure how this works. I want to see if Pianoteq will work well on Zorin but don't know if that is considered a second instance of Pianoteq as it is the exact same hardware, just a new OS. And if I install it on the Linux side of the drive, how will that work as far as the licensing? If I deactivate the Windows version would I also deactivate the Linux version since they are both on the same hardware?

My intention is to make sure that Pianoteq works on the Linux side, then, erase Windows completely as that is the only thing left on Windows that I even care about. I'd also like to upgrade to Pianoteq 9 but I kinda wanted to tackle one thing at a time.

I do have an iPad that I have the iOS version of Pianoteq 8 on, that I'd like to upgrade but I'm not there yet as I feel like I need to figure out the current desktop first.

Confusing? Hope I was able to say it well enough that someone knows what I'm asking. Thanks for the help!

First, congratulations on your success!
Second, welcome to the Linux world!
I've been using Ubuntu Studio for five years and I don't plan on ever going back to the slavery of Windows!

I am not any expert, ...

Hi Beco,

me neither. ;-)

I already did what you suggested. PT drops a to me cryptic error massage which asked me to file a bug report at modartt, what i did. So i'm waiting.

Best regards
Bazzo

Hi all,

i upgraded (re-installed) my setup to debian 13 an ran PTQ9 in cage/wayland. (Minimal Window Manger)
The same crash occurs. But i noticed something strange, I can toggle Fullscreen while the app is running as long as the UI is not in "Compact Mode". I can toggle "Compact Mode" as long as its not in "Fullscreen Mode". But both together will trigger the crash. Nonetheless, when i start with --fullscreen option, it doesn't start at all and outputs no errors.

Regards
Bazzo

Hi bazzo,

I am not any expert, but when I have some problem like that, I usually run the app from terminal to check what it says. After that you will have some answers about the problem.

Hope this will help you.

Best regards.

Hi all,

i upgraded (re-installed) my setup to debian 13 an ran PTQ9 in cage/wayland. (Minimal Window Manger)
The same crash occurs. But i noticed something strange, I can toggle Fullscreen while the app is running as long as the UI is not in "Compact Mode". I can toggle "Compact Mode" as long as its not in "Fullscreen Mode". But both together will trigger the crash. Nonetheless, when i start with --fullscreen option, it doesn't start at all and outputs no errors.

Regards
Bazzo

Sorry you're having this issue, bazzo. Would help if I could but am pretty new to Linux myself.

I'm not sure how much support is available with Modartt directly for Linux as it does seem to be a bit of an oddity. (I wonder how many Linux users of Pianoteq there actually are? I wonder if they know?) There was a good bit of detail in a ReadMe file that came with the download, I didn't look at it that carefully. But I suspect Windows and Mac installs are much more plug n play.

Wishing you the best.

i upgraded (re-installed) my setup to debian 13 an ran PTQ9 in cage/wayland. (Minimal Window Manger)
The same crash occurs. But i noticed something strange, I can toggle Fullscreen while the app is running as long as the UI is not in "Compact Mode". I can toggle "Compact Mode" as long as its not in "Fullscreen Mode". But both together will trigger the crash. Nonetheless, when i start with --fullscreen option, it doesn't start at all and outputs no errors.

Regards
Bazzo