thcilnnahoj.
abductedhello,
could someone please tell me why I can’t record vsti automation anymore?
Before, I could tweak any knob on my midi ontroller and the vsti parameter was recorded. Now I can only record pitch bend and modulation .
P.S. : when I tweak a knob directly on a vsti displayed on the screen, it is recorded but when I tweak it from my midi controller it is not recorded (although the knob is moving on the vsti)
ZynewaveDoes it happen with any VSTi?
I just tested with Nucleum, and when I have the VSTi track record armed, and started recording, then sending MIDI control changes from my keyboard records the VSTi parameter automation as expected.
abductedyes it happens with every vsti I have .
It’s incredible because everything was working fine before.
I thought maybe I accidently changed some settings but I don’t know where.
So when I move the vsti knobs directly with the mouse , an automation track for the parameter is automatically created but when I use the midi controller nothing is recorded although the vsti is responding to my tweakings because the knobs are moving and the sound is changing…
And I have a strange problem with a plugin called Drumatic 3 : when podium scans the folder where it is located, it is not detected ! so I simply can’t use it.
druidI use Drumatic 3 and when I scan the folder where it is located, it works fine. Do you have many plugins in the same folder as Drumatic? You can also import a plugin (instead of a folder) and point it specifically to Drumatic. If you can’t see it listed there, then you don’t have the .dll plugin that is required, which would be why it can’t be used. If you can see it listed, then you tell Podium to import it and it doesn’t work, let us know.
thcilnnahojI can only confirm that the newest version of Drumatic (3.0.2 – http://www.kvraudio.com/news/12577.html) doesn’t import at all in 2.27 beta 6, and an incorrect mapping is created for it in 2.26. The old version I use (3.0.1) still works fine in both.
druidI’m using 3.0.2 as far as I am aware. Might try downloading the latest version again and importing it, but so far, if I am indeed using 3.0.2, it’s working fine for me.
[edit]
Well hold on though, I didn’t really think properly, but I didn’t check the mappings, and I’m still using 2.26, I haven’t tried 2.27b6.
[edit2]
Oh my! I downloaded the 2.27b6 and I also cannot import Drumatic 3.
thcilnnahoj, can you tell me how the mapping is not created correctly, so I can double-check that on mine as well? I am not sure what to look for, as I often use energyXT as a VST bucket for everything I put in a track.
Zynewave@thcilnnahoj wrote:
I can only confirm that the newest version of Drumatic (3.0.2 – http://www.kvraudio.com/news/12577.html) doesn’t import at all in 2.27 beta 6, and an incorrect mapping is created for it in 2.26. The old version I use (3.0.1) still works fine in both.
Confirmed. I need to put in some further checks to make it import correctly. The plugin is unusual because it reports that it supports a 12 output multi-channel speaker configuration, which makes Podium skip the normal multiple stereo configurations. I’ll put up a new 2.27 beta later today.
Zynewave@abducted wrote:
yes it happens with every vsti I have .
It’s incredible because everything was working fine before.
I thought maybe I accidently changed some settings but I don’t know where.
So when I move the vsti knobs directly with the mouse , an automation track for the parameter is automatically created but when I use the midi controller nothing is recorded although the vsti is responding to my tweakings because the knobs are moving and the sound is changing…
To test if it is something that have gone wrong in your project, you could try to create a new project from scratch and reimport plugins. If you suspect something is corrupted in your project, then please email me your project file so that I can test it.
Malcolm Jacobson@abducted wrote:
hello,
could someone please tell me why I can’t record vsti automation anymore?Before, I could tweak any knob on my midi ontroller and the vsti parameter was recorded. Now I can only record pitch bend and modulation .
P.S. : when I tweak a knob directly on a vsti displayed on the screen, it is recorded but when I tweak it from my midi controller it is not recorded (although the knob is moving on the vsti)
I just tested this with 2.27 beta 7 and the Camel Audio Camel Space effect (as an effect on the same track as an instance of Alchemy).
When I tried the same test in another host, all MIDI data I sent from my controller was recorded, the UI movements were recorded and played back, and the MIDI Learn function worked as expected.
I’m not sure which part of this is/isn’t broken, as Podium doesn’t record all MIDI data by default, so I don’t know how much of this is by design and how much might be operator error. 😕
Cheers,
Malcolm.
pavouk100@Malcolm Jacobson wrote:
[*]When I moved a knob in the Camel Space UI the movements were recorded as a Podium parameter track, but they had no affect on playback.
I had similar problems with freebie Camel Crusher. Maybe that Camel Audio plugins are the culprit…
thcilnnahoj@Malcolm Jacobson wrote:
[*]The MIDI Learn function in Camel Space does not work in Podium.
[/list]
At least MIDI learn works fine here. Are you sure you assigned your MIDI input to the effect track, and not only to the instrument track (see http://www.zynewave.com/forum/viewtopic.php?t=2132)?
The automation tracks are automatically created for other effects’ parameters I’m trying to record, so it might be a possible cause.
Besides that, I can confirm all the other problems with Camel Space (demo).
It also takes away keyboard focus (spacebar, numpad 0/enter) from Podium. But I don’t use any of their plug-ins, so I don’t think I’ll bug Camel Audio about it.