Here is an upload of the project I'm talking about. It isolates the issue.
The plugin is programmed to use:
Port: 0
The plugin's first knob is configured to drive a MIDI CC signal at:
Channel 1
CC number 127
Please, take a look at the first plugin, in channel rack, and confirm that this MIDI Out is configured that way... right click that knob, and click "configure", to see its settings. So moving its first knob should send out a MIDI CC Signal on Channel 1, CC Number 127, Port 0. Now hit "play" on the project, with "SONG" activated in the FL Studio transport controls. You should see the first knob in that MIDI Out plugin moving with the automation.
Now, in channel rack, there are two MIDI Out plugins. The second one has channel volume moving. The first one does not. Now, the first one SHOULD be moving, too... but MIDI CC signals are failing to move it, despite the fact that it's configured to move with MIDI CC's from the first knob in the top MIDI Out plugin.
Unless it's got to do with my FL config, or my system, I believe this possibly is a bug, (and a major one, for me, at least); my more complex projects are deeply dependent on MIDI CC signals WITHIN FL.
NOTES:
For what it's worth, the same thing happens when I try to drive the automation with MIDI CC automation signals from the FL Dashboard plugin, too. MIDI CC automation is failing, for me, overall.
Normal FL Automation is working, (as seen in the second plugin's channel rack volume knob moving) but this category of FL automation can't do what I need. It has to be MIDI CC.
Thanks for reading this. Please advise.
Oh, incidentally: My system is FL 64, on Windows 7-64.
Load that project first. Now, in the project, there is a Midi Out plugin in the channel rack.Midi CC automation is broken.
Return to “Technical Support (Windows)”
Forum rules
TECHNICAL SUPPORT HAS MOVED!
Technical support has moved to ticketing - START HERE
Some self-help links ...
NOTE: Technical Support is ONLY available Monday - Friday (9 am to 5 pm), it can take a few days to get a response depending on the level of demand. Thank you for your patience.
TECHNICAL SUPPORT HAS MOVED!
Technical support has moved to ticketing - START HERE
Some self-help links ...
NOTE: Technical Support is ONLY available Monday - Friday (9 am to 5 pm), it can take a few days to get a response depending on the level of demand. Thank you for your patience.
[You can only see part of this thread as you are not logged in to the forums]
Midi CC automation is broken.
You do not have the required permissions to view the files attached to this post.
Re: Midi CC automation is broken.
Incidentally, my efforts to understand this pro...
-
- Site Admin
- Thu May 09, 2019 12:51 pm
Re: Midi CC automation is broken.
HSJIII wrote:Please, take a look at the first p...
Re: Midi CC automation is broken.
reflex wrote:HSJIII wrote:Please, take a look a...
Re: Midi CC automation is broken.
You can use virtual MIDI drivers to do this in ...
Re: Midi CC automation is broken.
I use virtual ports often. Started having prob...
Re: Midi CC automation is broken.
NTO wrote:I use virtual ports often. Started h...
Re: Midi CC automation is broken.
NTO wrote:I use virtual ports often. Started h...
Re: Midi CC automation is broken.
The loopmidi is a bridged config. Easy to send...
You do not have the required permissions to view the files attached to this post.
Re: Midi CC automation is broken.
NTO wrote:The loopmidi is a bridged config. Ea...
Re: Midi CC automation is broken.
First, I would suggest you post your actual que...
You do not have the required permissions to view the files attached to this post.
Last edited by NTO on Mon May 27, 2019 8:32 pm, edited 1 time in total.
Re: Midi CC automation is broken.
Well, first off that plugin does not load, so y...
Re: Midi CC automation is broken.
HSJIII wrote:Well, first off that plugin does n...
You do not have the required permissions to view the files attached to this post.