I'm having a bit of trouble sending through pedalling from MPT to Kontakt (via Chainer...) What's the correct way to do this? I can automate parameters happily enough, but I just can't seem to get a pedal signal through, which is a pity, because some of the pianos do all sorts of nice things with pedalling (like sympathetic vibrations in neighbouring strings).
Hmm, I have no experience with this, but I think that it simply isn't possible.
I once tried to use MPT with Xlutop Chainer to play a VSTi using my piano. I couldn't do a simple sustain with the pedal. When I started Xlutop Chainer stand alone, I could however.
I guess this is a midi message that doesn't get forwarded.
Quote from: "LPChip"I guess this is a midi message that doesn't get forwarded.
Yes, it seems so.
Oh, thanks. Could we move this topic into the feature requests, then? It'd be great to be able to send pedal messages... =D
Quote from: "bvanoudtshoorn"Oh, thanks. Could we move this topic into the feature requests, then? It'd be great to be able to send pedal messages... =D
isn't this more or less the same as my midi-mapping request (http://forum.openmpt.org/index.php?topic=2015.0)?
Actually, I just got it working! =P (This is for use through Xlutop Chainer). Here's how you do it:
1. In the Zxx configuration, change one of the SFx options to be CC64 (which is pedalling, even though I don't think it says so).
2. Put in some messages for that SFx (Z7F is full on, Z00 is full off)
3. In Xlutop, on controller 64 (in the alternate editor), click on "learn".
4. There you go! It *should* work (at least, it seems to be working for me at the moment... =D
I knew that I'd figure out how to do it once I posted the original message. Always happens!
And we thank you for that X)
Perhaps that CC message should be renamed to pedalling then. :)
Quote from: "LPChip"Perhaps that CC message should be renamed to pedalling then. :)
The name is wrong due to a bug, and actually all but a few first ones in the midiCC list have wrong name - to be fixed in .50. While waiting for the fix, here's a more correct midiCC list:
0 BankSelect [Coarse]
1 ModulationWheel [Coarse]
2 Breathcontroller [Coarse]"
4 FootPedal [Coarse]
5 PortamentoTime [Coarse]
6 DataEntry [Coarse]
7 Volume [Coarse]
8 Balance [Coarse]
10 Panposition [Coarse]
11 Expression [Coarse]
12 EffectControl1 [Coarse]
13 EffectControl2 [Coarse]
16 GeneralPurposeSlider1
17 GeneralPurposeSlider2
18 GeneralPurposeSlider3
19 GeneralPurposeSlider4
.
.
.
32 BankSelect [Fine]
33 ModulationWheel [Fine]
34 Breathcontroller [Fine]
36 FootPedal [Fine]
37 PortamentoTime [Fine]
38 DataEntry [Fine]
39 Volume [Fine]
40 Balance [Fine]
42 Panposition [Fine]
43 Expression [Fine]
44 EffectControl1 [Fine]
45 EffectControl2 [Fine]
.
.
.
64 HoldPedal [OnOff]
65 Portamento [OnOff]
66 SustenutoPedal [OnOff]
67 SoftPedal [OnOff]
68 LegatoPedal [OnOff]
69 Hold2Pedal [OnOff]
70 SoundVariation
71 SoundTimbre
72 SoundReleaseTime
73 SoundAttackTime
74 SoundBrightness
75 SoundControl6
76 SoundControl7
77 SoundControl8
78 SoundControl9
79 SoundControl10
80 GeneralPurposeButton1 [OnOff]
81GeneralPurposeButton2 [OnOff]
82 "GeneralPurposeButton3 [OnOff]
83 "GeneralPurposeButton4 [OnOff]
.
.
.
91 EffectsLevel
92 TremuloLevel
93 ChorusLevel
94 CelesteLevel
95 PhaserLevel
96 DataButtonIncrement
97 DataButtonDecrement
98 NonRegisteredParameter [Fine]
99 "NonRegisteredParameter [Coarse]
100 RegisteredParameter [Fine]
101 RegisteredParameter [Coarse]
.
.
.
120 AllSoundOff
121 AllControllersOff
122 LocalKeyboard [OnOff]
123 AllNotesOff
124 OmniModeOff
125 OmniModeOn
126 MonoOperation
127 PolyOperation
Thanks!