Modartt user forum - Pianoteq 8 = Way to much hassle to upgrade if problems occur.

Re: Pianoteq 8 = Way to much hassle to upgrade if problems occur.

2022-11-26T15:17:24Z

Pianoteq 7 was built on ubuntu 16.04 , while Pianoteq 8 is now built on ubuntu 18.04. This change was required because our tooling needs more modern features. The libmvec, which is part of glibc (so it is a very low level part of the linux system), was introduced between ubuntu 14.04 and ubuntu 16.04.

Re: Pianoteq 8 = Way to much hassle to upgrade if problems occur.

2022-11-26T14:58:36Z

groovy wrote:

Indeed, while Pianoteq 8 is running that lib is used:
(snip)
With Pianoteq 7 the output of lsof (list open files) is empty.

Perhaps PTQ7 was statically linked and PTQ8 dynamically linked to shared libraries? You can investigate if that is the case with ldd and nm.

Re: Pianoteq 8 = Way to much hassle to upgrade if problems occur.

2022-11-26T11:04:33Z

Indeed, while Pianoteq 8 is running that lib is used:

lsof | grep mvec
Pianoteq 1422 mi mem REG 179,2 174488 682973 /lib/x86_64-linux-gnu/libmvec-2.31.so
Pianoteq 1422 1429 JUCE\x20A mi mem REG 179,2 174488 682973 /lib/x86_64-linux-gnu/libmvec-2.31.so
Pianoteq 1422 1430 JUCE\x20M mi mem REG 179,2 174488 682973 /lib/x86_64-linux-gnu/libmvec-2.31.so
Pianoteq 1422 1431 Pianoteq mi mem REG 179,2 174488 682973 /lib/x86_64-linux-gnu/libmvec-2.31.so
Pianoteq 1422 1452 jq-1 mi mem REG 179,2 174488 682973 /lib/x86_64-linux-gnu/libmvec-2.31.so
Pianoteq 1422 1453 jq-2 mi mem REG 179,2 174488 682973 /lib/x86_64-linux-gnu/libmvec-2.31.so
Pianoteq 1422 1454 jq-3 mi mem REG 179,2 174488 682973 /lib/x86_64-linux-gnu/libmvec-2.31.so
Pianoteq 1422 1455 jq-4 mi mem REG 179,2 174488 682973 /lib/x86_64-linux-gnu/libmvec-2.31.so
Pianoteq 1422 1456 Pianoteq mi mem REG 179,2 174488 682973 /lib/x86_64-linux-gnu/libmvec-2.31.so
Pianoteq 1422 1457 vpuptthd mi mem REG 179,2 174488 682973 /lib/x86_64-linux-gnu/libmvec-2.31.so
Pianoteq 1422 1458 tith mi mem REG 179,2 174488 682973 /lib/x86_64-linux-gnu/libmvec-2.31.so
Pianoteq 1422 1459 JUCE\x20T mi mem REG 179,2 174488 682973 /lib/x86_64-linux-gnu/libmvec-2.31.so

With Pianoteq 7 the output of lsof (list open files) is empty.

Re: Pianoteq 8 = Way to much hassle to upgrade if problems occur.

2022-11-25T21:16:53Z

i confirmed on my system (rather old version of Ubuntu, actually 16.04 ... i know i know, very embarrassing) that Pianoteq v 7.5.4 is not looking for libmvec.so whereas Pianoteq 8 is. but since my system is so ancient and it works (libmvec is there), undoubtedly you'll be able to install this missing dependency and it will work, no problem.

Re: Pianoteq 8 = Way to much hassle to upgrade if problems occur.

2022-11-25T20:26:51Z

The most generic way to install Pianoteq I know is to just unzip the downloaded archive in the HOME directory:

p7zip -d pianoteq_linux_v802.7z

The unpacked default path of the startable binary (with all those ugly blanks) then is:

./Pianoteq\ 8/x86-64bit/Pianoteq\ 8

The shared library libmvec.so.1 is in the installed Debian package libc6, which should exist on a Kubuntu too. Check as root:

# dpkg -l libc6
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-===============-============-=================================
ii libc6:amd64 2.31-13+deb11u5 amd64 GNU C Library: Shared libraries

Check, which libmvec is contained in your libc6, example on my system:

# dpkg -L libc6 | grep libmvec
/lib/x86_64-linux-gnu/libmvec-2.31.so
/lib/x86_64-linux-gnu/libmvec.so.1

Note that libmvec.so.1 is just a symbolic link to the actual version libmvec-2.31.so.

Re: Pianoteq 8 = Way to much hassle to upgrade if problems occur.

2022-11-25T14:49:38Z

GRB wrote:

jl@jl-Inspiron-7548 ~ $ cd Pianoteq8
jl@jl-Inspiron-7548 ~/Pianoteq8 $ ls
arm-32bit arm-64bit Documentation Licence.rtf Pianioteq terminal output.txt README_LINUX.txt x86-64bit
jl@jl-Inspiron-7548 ~/Pianoteq8 $ cd x86-64bit
jl@jl-Inspiron-7548 ~/Pianoteq8/x86-64bit $ ls
extra Pianoteq_8 Pianoteq 8.lv2 Pianoteq 8.so
jl@jl-Inspiron-7548 ~/Pianoteq8/x86-64bit $ ./Pianoteq_8
./Pianoteq_8: error while loading shared libraries: libmvec.so.1: cannot open shared object file: No such file or directory
jl@jl-Inspiron-7548 ~/Pianoteq8/x86-64bit $
# Pianoteq 8 does not run

That looks like a bug, which might be caused by a mismatch between your Linux and what Modartt used to compile Pianoteq. I'm still using v7 so I have not tried this myself yet, but if you are still experiencing it, and if you are using a Linux that is not too old and not too new, I suggest you contact them for a bug report since they may well miss your post here among a gazillion of others. Just paste the above into the form at https://www.modartt.com/support

Re: Pianoteq 8 = Way to much hassle to upgrade if problems occur.

2022-11-25T13:22:32Z

groovy wrote:

Usually Pianoteq is installed in your HOME-directory. Then you can open a terminal window on your desktop and type the command:
./Pianoteq\ 8/x86-64bit/Pianoteq\ 8
Alternatively the full path, if known, for example:
/home/GRB/Pianoteq\ 8/x86-64bit/Pianoteq\ 8
Watch the error messages in that terminal, if something goes wrong.

Thanks. I found out that to launch a program in Linux from the terminal you have to put "./" without the quotes, simply ./

Any way there's a shared library that it cannot access.

to Modartt

jl@jl-Inspiron-7548 ~ $ cd Pianoteq_7_5

jl@jl-Inspiron-7548 ~/Pianoteq_7_5 $ ls

arm-32bit arm-64bit Documentation Licence.rtf README_LINUX.txt x86-64bit

jl@jl-Inspiron-7548 ~/Pianoteq_7_5 $ cd Pianoteq_7_5

bash: cd: Pianoteq_7_5: No such file or directory

jl@jl-Inspiron-7548 ~/Pianoteq_7_5 $ cd Pianoteq_7_5

bash: cd: Pianoteq_7_5: No such file or directory

jl@jl-Inspiron-7548 ~/Pianoteq_7_5 $ ls

arm-32bit arm-64bit Documentation Licence.rtf README_LINUX.txt x86-64bit

jl@jl-Inspiron-7548 ~/Pianoteq_7_5 $ cd x86-64bit

jl@jl-Inspiron-7548 ~/Pianoteq_7_5/x86-64bit $ ls

extra Pianoteq7.5.4 Pianoteq 7.lv2 Pianoteq 7.so

jl@jl-Inspiron-7548 ~/Pianoteq_7_5/x86-64bit $ ./Pianoteq7.5.4

Alsa thread could not acquire real-time scheduling, error 1 -- Operation not permitted

Midi thread could not acquire real-time scheduling, error 1 -- Operation not permitted

Multi-core: could not acquire real-time scheduling, error 1 -- Operation not permitted

# 7.5.4 actually does run in spite of error messages

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

jl@jl-Inspiron-7548 ~ $ cd Pianoteq8

jl@jl-Inspiron-7548 ~/Pianoteq8 $ ls

arm-32bit arm-64bit Documentation Licence.rtf Pianioteq terminal output.txt README_LINUX.txt x86-64bit

jl@jl-Inspiron-7548 ~/Pianoteq8 $ cd Pianoteq8

bash: cd: Pianoteq8: No such file or directory

jl@jl-Inspiron-7548 ~/Pianoteq8 $ cd x86-64bit

jl@jl-Inspiron-7548 ~/Pianoteq8/x86-64bit $ ls

extra Pianoteq_8 Pianoteq 8.lv2 Pianoteq 8.so

jl@jl-Inspiron-7548 ~/Pianoteq8/x86-64bit $ ./Pianoteq_8

./Pianoteq_8: error while loading shared libraries: libmvec.so.1: cannot open shared object file: No such file or directory

jl@jl-Inspiron-7548 ~/Pianoteq8/x86-64bit $

# Pianoteq 8 does not run

Re: Pianoteq 8 = Way to much hassle to upgrade if problems occur.

2022-11-24T16:34:49Z

Usually Pianoteq is installed in your HOME-directory. Then you can open a terminal window on your desktop and type the command:

./Pianoteq\ 8/x86-64bit/Pianoteq\ 8

Alternatively the full path, if known, for example:

/home/GRB/Pianoteq\ 8/x86-64bit/Pianoteq\ 8

Watch the error messages in that terminal, if something goes wrong.

Re: Pianoteq 8 = Way to much hassle to upgrade if problems occur.

2022-11-24T14:21:20Z

sandalholme wrote:

Same issue with accessing my account to upgrade from 7 8 even after getting my password changed. (That worked) Awaiting response from support. NB to Modarrt. Sent email to Niclas on Nov 20th. I agree with MrRoland that Modarrt support is very good.

They say they are going to work with me. Does anyone know exactly how you launch Pianoteq from the Linux terminal? I can only do it by clicking on the executable in the file manager. That's with 7.5.4 and 8.x, however 8.x doesn't run. Neither one launch from the terminal. There's not much output from the terminal, at least nothing that points to a direction to go. Mostly it just doesn't work.

Re: Pianoteq 8 = Way to much hassle to upgrade if problems occur.

2022-11-23T17:36:08Z

Same issue with accessing my account to upgrade from 7 8 even after getting my password changed. (That worked) Awaiting response from support. NB to Modarrt. Sent email to Niclas on Nov 20th. I agree with MrRoland that Modarrt support is very good.

Re: Pianoteq 8 = Way to much hassle to upgrade if problems occur.

2022-11-23T14:11:04Z

GRB wrote:

I cannot log into the Pianoteq user area on the computer that has been running Pianoteq since version 5. The computer is connected to the internet, and other sites do work. There is some sort of manual activation which is very complicated and requires many complicated steps. I'm 80 years old and I'm honestly overwhelmed by the complexity. I feel very frustrated. It does not make sense that a computer that works with the Internet in general cannot log onto the Pianoteq user area any longer.

I think you could best contact Modartt support. I've got good experiences with their assistance.

Pianoteq 8 = Way to much hassle to upgrade if problems occur.

2022-11-23T14:06:00Z

I cannot log into the Pianoteq user area on the computer that has been running Pianoteq since version 5. The computer is connected to the internet, and other sites do work. There is some sort of manual activation which is very complicated and requires many complicated steps. I'm 80 years old and I'm honestly overwhelmed by the complexity. I feel very frustrated. It does not make sense that a computer that works with the Internet in general cannot log onto the Pianoteq user area any longer.