The NP-30 is semi-weighted. I didn't test it, but I think it should work fine with Pianoteq. But if you're serious about learning to play piano, go for an hammer action keyboard.
Old Roland A-33 (A-30, A-37...) MIDI controller keyboards should be as fine as the NP-30, and are easy to find used. They have a light action, but in order to get high velocity values you have to hit really hard on the keys.

Exactly! I have this two keyboards models: an Yamaha NP30 and a Roland A-37. I tested it's two keyboards on Pianoteq v4, and the functionality of the keyboard action and velocity it's so good! Specifically about the velocity curves, i use the patch "Fast Keyboard" for two keyboard for more real action (i liked to the "closed" piano sounds), but i will test mapping keyboard velocity curves, possibly i search more better results in keyboard action.

I hope to have contributed!

Thanks!

aconnect -i
client 0: 'System' [type=kernel]
...

All seems fine.
I was afraid you were playing TiMidity++ or an OPL3 built-in synth instead of Pianoteq, but none of those is showing up.

Yes... "aconnect -l" does nothing, while "aconnect -il" and "aconnect -ol" show connection information along with available inputs and outputs.
Meanwhile, I realized the blue bars in Pianoteq's velocity diagram are indeed green!

gp

Go to File -> Audio/Midi setup -> Midi and see what MIDI codes your Pianoteq is receiving: that's how I discovered my A-33 was sending every note twice. Does your E313 send unwanted program change messages to Pianoteq, or other MIDI codes that modify parameters in an unwanted way? They should go away as soon as you switch to a different preset.

I don't see that my keyboard is sending every note twice.

aconnect -i
client 0: 'System' [type=kernel]
    0 'Timer           '
    1 'Announce        '
client 14: 'Midi Through' [type=kernel]
    0 'Midi Through Port-0'
client 24: 'ESI RoMI/O2' [type=kernel]
    0 'ESI RoMI/O2 MIDI 1'
    1 'ESI RoMI/O2 MIDI 2'

aconnect -o
client 14: 'Midi Through' [type=kernel]
    0 'Midi Through Port-0'
client 24: 'ESI RoMI/O2' [type=kernel]
    0 'ESI RoMI/O2 MIDI 1'
    1 'ESI RoMI/O2 MIDI 2'
client 128: 'Pianoteq Midi Input' [type=user]
    0 'Pianoteq Midi In Port'
client 129: 'Pianoteq Midi Input' [type=user]
    0 'Pianoteq Midi In Port'

EvilDragon wrote:

I did not say that E313 is gonna make Pianoteq sound awful. I just said that it's not the proper controller for the job, because you cannot control velocity as well with it as with a hammer action controller. There's a difference between the two statements.

No,no, I didn't mean  you. Sorry if you thought this. The problem is I'm a bit confuse now, because some say one thing and some another.

We talk about different problems and try to identify your problem.
You can send MIDI codes to Pianoteq by means of an external keyboard, a MIDI file, the on-screen keyboard, vmpk, Rosegarden, whatever... but Pianoteq should sound the same as long as the MIDI codes it gets are the same.
True, it's hard to enjoy Pianoteq with an E313, because you can't get the velocity values you expect. But wrong velocity values alone can't make Pianoteq sound like a trumpet.
Go to File -> Audio/Midi setup -> Midi and see what MIDI codes your Pianoteq is receiving: that's how I discovered my A-33 was sending every note twice. Does your E313 send unwanted program change messages to Pianoteq, or other MIDI codes that modify parameters in an unwanted way? They should go away as soon as you switch to a different preset.
Try typing "aconnect -l" (lowercase L) in terminal and see if you MIDI adapter is really connected to Pianoteq and only to PIanoteq...
I hope you'll be less confused soon...

gp

I did not say that E313 is gonna make Pianoteq sound awful. I just said that it's not the proper controller for the job, because you cannot control velocity as well with it as with a hammer action controller. There's a difference between the two statements.

No,no, I didn't mean  you. Sorry if you thought this. The problem is I'm a bit confuse now, because some say one thing and some another.

Thanks!

One thing I would like to point out is: you should get exactly the same sound from Pianoteq regardless if you're playing with the mouse on the screen or on an external keyboard, as long as the MIDI velocity values you feed to Pianoteq are the same. Look at the blue lines. If this rule does not hold, there's something broken in your setup (and I'm sure Linux is not the culprit, look elsewhere).
By the way... ASIO? Maybe you meant ALSA.

gp

Other people from this forum said that with my keyboard (yamaha psr-e313) pianoteq is going to make it sound awful. I'm happy that you and  azrael4 didn't think so.

The NP-30 is semi-weighted. I didn't test it, but I think it should work fine with Pianoteq. But if you're serious about learning to play piano, go for an hammer action keyboard.
Old Roland A-33 (A-30, A-37...) MIDI controller keyboards should be as fine as the NP-30, and are easy to find used. They have a light action, but in order to get high velocity values you have to hit really hard on the keys. They just don't make any sound on their own.
One thing I would like to point out is: you should get exactly the same sound from Pianoteq regardless if you're playing with the mouse on the screen or on an external keyboard, as long as the MIDI velocity values you feed to Pianoteq are the same. Look at the blue lines. If this rule does not hold, there's something broken in your setup (and I'm sure Linux is not the culprit, look elsewhere).
By the way... ASIO? Maybe you meant ALSA.

gp

You can see blue lines in the velocity-window while you play and there you see the actual velos of your playing. You have to adjust the lowest and highest velos that you play to the velocity curve from PTQ as long till you feel comfortable with it.
...
If you find a velo-setting for your keyboard I think you will get it done!

Y will try it.

Do you think a NP30 would do the same job?

I noticed that when playing the demos of my keyboard with PTQ the sound is good too, but when I play something the sound is not so good. Perhaps the info that is send with MIDI is different when I play the keyboard than when I play the demos?

You can see blue lines in the velocity-window while you play and there you see the actual velos of your playing. You have to adjust the lowest and highest velos that you play to the velocity curve from PTQ as long till you feel comfortable with it.

As I've said before I used a Portable Grand DGX 205 with no weighted keys at all, and had great fun with PTQ. But I DO absolutely prefer the weighted keys from the P85 now.

If you find a velo-setting for your keyboard I think you will get it done!

heinke

Perhaps the info that is send with MIDI is different when I play the keyboard than when I play the demos?

Yes, and velocity curve governs most of that behavior, along with the sensitivity of the keybed. Since non-weighted keyboards don't give you any resistance while playing, you cannot control velocity as precisely and neatly as on a real piano-weighted keyboard.

I really think this all boils down to non-weighted keys and weird velocity curves Yamaha built into that E313. It's perhaps good for organ and strings, but not for piano. My 2 cents...

2) If you use this internal audio card for your PTQ playback of course you can't switch it of, but maybe the incoming midi signal is triggering an internal sound on that sound card. (some of them have some built in sounds-GM copatibel- to play back midi files!) I don't know linux so you have to check that as far as you can.

4) How that ASIO works with an internal soundcard (maybe on linux?) I can't say, but if PTQ sounds good for you while playing back the demo song by Hugh Sung, it works. Is this the case? Does it sound OK for you with the demo file played back? (The one in the software, not on PTQ homepage!)

You should solve your problem, and maybe you need a different audio card?

Heinke

2) I will check this.
4) PTQ sounds good when playing the demos

I noticed that when playing the demos of my keyboard with PTQ the sound is good too, but when I play something the sound is not so good. Perhaps the info that is send with MIDI is different when I play the keyboard than when I play the demos?

Thanks for your support Heinke! I will try to answer your questions:

1) I use this MIDI interface http://www.esi-audio.com/products/romio2/. I don't know if it's good or bad.
2)Soundcard switched off??? I thought it must be on.
3) I use this notebook HP Pavilion dv4396ea, the internal soundcard is a 3D Sound Blaster Pro compatible sound 16 bit integrated.
4) I use linux, and the audio driver is ASIO.

Danke

to:

1) I think it should be no problem with this midi interface.

2) If you use this internal audio card for your PTQ playback of course you can't switch it of, but maybe the incoming midi signal is triggering an internal sound on that sound card. (some of them have some built in sounds-GM copatibel- to play back midi files!) I don't know linux so you have to check that as far as you can.

4) How that ASIO works with an internal soundcard (maybe on linux?) I can't say, but if PTQ sounds good for you while playing back the demo song by Hugh Sung, it works. Is this the case? Does it sound OK for you with the demo file played back? (The one in the software, not on PTQ homepage!)

There is left to say that I use often different presets while playing then while listening to PTQ. The standard presets which sound far distant are from a listeners perspective and do sound authentic while listening. I don't like that while playing because that makes me feel "split up" in some way. Playing while hearing it from a distance. But this are little problems that can be solved as long you are "overall" happy with the PTQ sound at all. It doesn't seem to be that way in your case. You should solve your problem, and maybe you need a different audio card?

Hope it helps in some way.

Heinke

1)Which Midi Input do you use? (MIDI interface)
2)Is there an onboard soundcard which isn't switched off?
3)What is your audio hardware?(in the computer)
4)Which audio driver is used in your computer system? (ASIO?)

Thanks for your support Heinke! I will try to answer your questions:

1) I use this MIDI interface http://www.esi-audio.com/products/romio2/. I don't know if it's good or bad.
2)Soundcard switched off??? I thought it must be on.
3) I use this notebook HP Pavilion dv4396ea, the internal soundcard is a 3D Sound Blaster Pro compatible sound 16 bit integrated.
4) I use linux, and the audio driver is ASIO.

Danke