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.
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!
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
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.
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
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'
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
Ok, so it seems that the amplificatin system built in your keyboard is not the best choice for you, choosing headphones as a better reproduction device instead. But this should be true only for internal PSR sounds.
_______________________
best acne products | provillus for women
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!