Sorry for my typo and poor english, I meant just "started". - In other words: In a terminal-window I typed "vmpk" at the user prompt (this starts vmpk). In a second terminal-window I typed my Pianoteq command ("pianoteq" for example). This starts Pianoteq.

"VMPK Output" is the MIDI-input shown in Pianoteq then, not a setting in vmpk! (see under options in PTQ).

Is your fedora up-to-date? The basic procedure of starting to binaries in terminal windows is not different.

OK. I understand. Thanks for the clarification. Yes, my fedora is up to date.
The only difference, I use one terminal window to start both applications.

I have filed a bug with vmpk.

Again, thanks.

groovy wrote:

I just installed vmpk just for interest. With its default settings and started from commandline with '$ vmpk" this virtual keyboard appears in the later startet '$ pianoteq' as "VMPK Output". Because I have listening Pianoteq "to all MIDI inputs", I get pianosounds from klicking the virtual keyboard vmpk. On my system it makes no difference, whether I quit Pianoteq or vmpk first (no segfaults).

Normally I always start the MIDI peripherals first (keyboards, controllers) and then Pianoteq. For quitting I choose the reverse order.

The distribution is Debian Jessie 64-bit.

Good luck

'startet'? Is that Debian?
man vmpk shows no 'output' option?

OK, there is something 'different' - it is not a pianoteq issue.

Thanks for your help.
Dave

Sorry for my typo and poor english, I meant just "started". - In other words: In a terminal-window I typed "vmpk" at the user prompt (this starts vmpk). In a second terminal-window I typed my Pianoteq command ("pianoteq" for example). This starts Pianoteq.

"VMPK Output" is the MIDI-input shown in Pianoteq then, not a setting in vmpk! (see under options in PTQ).

Is your fedora up-to-date? The basic procedure of starting to binaries in terminal windows is not different.

I just installed vmpk just for interest. With its default settings and started from commandline with '$ vmpk" this virtual keyboard appears in the later startet '$ pianoteq' as "VMPK Output". Because I have listening Pianoteq "to all MIDI inputs", I get pianosounds from klicking the virtual keyboard vmpk. On my system it makes no difference, whether I quit Pianoteq or vmpk first (no segfaults).

Normally I always start the MIDI peripherals first (keyboards, controllers) and then Pianoteq. For quitting I choose the reverse order.

The distribution is Debian Jessie 64-bit.

Good luck

'startet'? Is that Debian?
man vmpk shows no 'output' option?

OK, there is something 'different' - it is not a pianoteq issue.

Thanks for your help.
Dave

My bad. Thanks.
So which is the 'correct' order of quitting please?
I can only think an internal software connection is being made and broken when I quit?

I quit vmpk first - using the menu - still get the core dump.
Quit pianoteq first, then vmpk - still get the core dump.

Seems it is only vmpk. Thanks.

I just installed vmpk just for interest. With its default settings and started from commandline with '$ vmpk" this virtual keyboard appears in the later startet '$ pianoteq' as "VMPK Output". Because I have listening Pianoteq "to all MIDI inputs", I get pianosounds from klicking the virtual keyboard vmpk. On my system it makes no difference, whether I quit Pianoteq or vmpk first (no segfaults).

Normally I always start the MIDI peripherals first (keyboards, controllers) and then Pianoteq. For quitting I choose the reverse order.

The distribution is Debian Jessie 64-bit.

Good luck

pe2dave wrote:

How to quit without a core dump?

$ ./pianoteq  &
[1] 12269
$ Multi-core: got real-time scheduling with priority 65

then

$
[1]-  Done                    ./pianoteq
[2]+  Segmentation fault      (core dumped) vmpk

when I used quit from the menu?

The Segmentation fault is in vmpk, not pianoteq. Have you tried to start pianoteq in the foreground with just " $ ./pianoteq"?
Or quitting vmpk first before you quit pianoteq?

My bad. Thanks.
So which is the 'correct' order of quitting please?
I can only think an internal software connection is being made and broken when I quit?

I quit vmpk first - using the menu - still get the core dump.
Quit pianoteq first, then vmpk - still get the core dump.

Seems it is only vmpk. Thanks.

How to quit without a core dump?

$ ./pianoteq  &
[1] 12269
$ Multi-core: got real-time scheduling with priority 65

then

$
[1]-  Done                    ./pianoteq
[2]+  Segmentation fault      (core dumped) vmpk

when I used quit from the menu?

The Segmentation fault is in vmpk, not pianoteq. Have you tried to start pianoteq in the foreground with just " $ ./pianoteq"?
Or quitting vmpk first before you quit pianoteq?

I think you have to save it for each instrument voice.  <File><Save Preset As>

Be sure to rename it. (For safety's sake)

Thanks, I'll give it a try.

It seems to 'remember' the setting the second time round so that problem solved. Tks.

How to quit without a core dump?

$ ./pianoteq  &
[1] 12269
$ Multi-core: got real-time scheduling with priority 65

then

$
[1]-  Done                    ./pianoteq
[2]+  Segmentation fault      (core dumped) vmpk

when I used quit from the menu?

Be sure to rename it. (For safety's sake)