204,051 users have contributed to 43,358 threads and 259,683 posts.
In the past 24 hours, we have 8 new thread(s), 22 new post(s) and 53 new user(s).
Ok, thanks for explaining. I think I finally understand what you do: instead of having an audio instrument track you use a midi track with a multi instrument (that does offer custom bank selects) and then you cable it in the environment, with some midi processing, to an audio instrument with the VI instantiated?
Anyway, since you do not send any program change events to VI you should be fine and not affected by the bug.
you got it !
How did you make the instrument with the articulation selection that we can see in Kai attached the following image(s)
The smart controls panel in the picture is basically a monitor that gives me a dynamic directory of the banks and articulations in the library. I can’t memorize 100+ key/program change assignments and this way I have all necessary information right when I am about to select an articulation. It is realized via a script for the Midi-Scripter plug-in introduced in Logic X and the smart controls panel merely shows its control elements.
Under the hood, there is a little environment macro in between the Physical-Input and the Sequencer-Input that (among some other features) transforms the incoming key-switch events for bank and articulation selection into the proper program change events for the individual articulation matrices in VI pro and also sends control events to update the smart controls monitor shown in the picture. I.e. all the environment processing is done before the Sequencer-In and this way I can use ordinary audio instrument tracks. Moreover, I rely on Logic’s new automatic way of managing audio instruments, and load new instruments conveniently with Logic’s Library (Logic saves the entire channel strip including the smart controls panel and the midi-script required to control it). I.e. nothing has to be hard-wired in the environment and new audio instruments are automatically created and deleted as needed.
Thanks so much for the feedback, Ck!
After a month without a confirmation whether this is actually a bug or just a problem with my system (e.g. a corrupted settings file, …), this is an extremely helpful piece of information. I sent a bug report to Apple as well, but they write already in the online form that there won’t be any feedback.
If you have a backup, going back to 10.2.2 is a good workaround.
It would be great if someone could confirm that this is a bug,
Yes, it is a bug definitely. Your description is well done Kai. As a long time program developer I have an explanation about that bug. Here it is:
The Logic Sequencer object shown in Click & Ports Environment layer looks like a single object. In fact that single object is a powerful Macro which contains tons of audio and MIDI routings packed into that Macro.
The routings are based on the old garage studio setup (Input, Mixer, Recorder). In the Program Change bug scenario it is obvious that the Program messages go to the Recorder but they are not routed to the Mixer (Instrument Channel Strip). The direct Input->Channel Strip or the Recorder Thru function is broken regarding the Program Change messages Software Instrument pass Thru.
You can make a simple test which shows that no Program Change comes to the Software Instrument Channel strip if the Program message is sent from the Logic outside world.
1. Insert a default MIDI FX Scripter plugin.
2. Open the Scripter editor and have a look at the Trace sector.
3. Send any Note event or Modulation CC1 - the Scripter Trace Monitor will show those messages. Send a Program Change on any MIDI Ch 1-16 - nothing!
After Logic 8 Apple implemented the Channel Strip Performance Change. Program Change messages sent on Ch.1 were blocked to the Software Instrument Channel strip. They were reserved for the Performance Chanel Strip change so we could use Ch.2-16. Now it seems that all Ch.1-16 are blocked regarding the Software Instrument Channel Strip. There is another direct routing using Environment cable with a Transformer which only pass Program Changes. However the Channel Strip 100% blocks that workaround. For now my diagnose is that it is Software Instrument Channel Strip Program Change blocking.
BTW. There is no problem for the AG Articulation Switching system regarding the new Program Change bug. The AG Articulation system can be controlled directly via the Logic Controller Assignments which highjacks the Logic Sequencer engine. The other aid is the new AG Remote Control Enviro tool which converts the direct Program Change Messages into invisible data which is passed secretly thru the Logic Sequencer and re-converted into Program Change again. AG Articulation Maps can control the VSL Instrument Matrix switching (Logic 10.2.3 & 10.2.4) without any problems including a Program Change Message, KS1 & KS2 for X/Y axis (assigned in the Articulation Map) - for Dimension Brass for example.
Best,
AG Logic Articulation Toolkit (developer)
I have this problem and was trying to figure out what I was doing wrong. Thanks for posting.
I have a similar problem with program change in Digital Performer.
I haven't been able to get Prg Change to work since VIPRO vers. 2.4.14074
VIPRO responds correctly if I send PC from a control surface, but not as part of the DP sequence. Strange. It's worked perfectly for years. I've tried each new version of VI/VE Pro, without success. Keep reverting back.
Did you ever get it to work?
ddunn
Marnix,
Thanks for response. I must wait till I finish my current work with VIPRO ver. 2.4.14074 before I do anymore testing.
But I've not seen a control within VIPRO to enable/disable program change.
The "ksw" button in the matrix view was only for toggling keyswitch or PC views, as both were always active.
Not correct?
Also it's strange that an iPad controller sending PC to VIPRO works correctly, while it doesn't via playback from DP.
Thanks for your help.
ddunn
