Audiogrocery

I disagree. Apple did their best to repair the environment (as much as possible) before the environment freezing. They also implemented all sort of new environment features in Logic X, related to the MIDI FX plugins and the Quick Controls communication, more than 128 values etc. As a long time Logic environment expert, I must say that this is still extremely useful system. For example, you can send and receive thousands of messages for a given environment tool in the Logic Mixer with zero CPU and no audio interruption which is not possible with the MIDI FX plugin.

Glad to hear that Logic => VEP AU3 (Multi Instance building) is in a big progression. Thanks to all here who did their best to help.

Hello All, The Topic is SOLVED! I provided a little instructional bundle to Leandro today and he reported that his requirements are solved (it was a matter of a small detail in the VEP Instance Combo setup). Leandro (the topic OP) is trying to build an universal VEP Multi Instance project where he tries to combine the AG beast called VEP Multi Instance with third party Instrument engines using the AU3 tech. I'd like to outline some info about VEP Combo Instance building and to reply to some AG product "guessing" posted here. Someone posted here, that the problem is related to an AG bug, Environment tools, Logic Scripter etc AG VEP Multi Instance (VEPM) Technical Info VEPM is a Kontakt KSP multi script which allows you to access all Kontakt A.B.C.D ports via a single track in your DAW which gives you tons of resources, saving CPU etc. The product is compatible with any DAW, so no Logic Scripter or Environment tools are used. All is done by the Kontakt KSP plugin. No bugs are guaranteed! Logic AU3 Compatibility VEPM v2 comes with giant VEP Instance templates which are supper time saving - you just drug & drop them from the Finder to the VEP Instance slot. For example, you can load up to 128 Kontakts (8192 MIDI Channels) for a second. The VEPM KSP plugin is loaded for each Kontakt instance. AU3 allows you to add additional third party Instruments (not Kontakt) into the same VEP Instance and combine them with the VEPM Kontakts. (This is the OP idea here). Note: the MIDI Channlel switching instruments such as EW Play can be combined with AG VEP Multi Instance (Kontakts). Logic AU2 Compatibility (Old) VEPM v1.0 was developed in 2017. The main concept was to ignore the 16 MIDI Channel switching limitation and allow you to load up to 16 Kontakt Instruments per VEP Instance (1024 MIDI Channels powered by all Kontakt ABCD ports). Smart Controllers (CC) Multiplication/Cloning This "Smart" tech was introduced by AG for a very 1st time in 2017. For example, you record/draw a single CC# automation via Ch.1 and the CC# stream is multiplicatived only to the current sustaining Note events MIDI Channels (not to all 16 MIDI Channels). The VEPM "Smart CC Cloning" saves a lot of MIDI bandwidth and CPU and works with all DAWs. VEPM Combo This is the OP question here. I confirm that VEPM can be combined with non Kontakt sample players or other engines in a single VEP Instance and work perfectly with AU3 articulation sets switching (no Logic Scripters needed). VEP Audio FX Tips I posted a non voice VEP Audio FX routing Tips in the AG Youtube channel some time ago. I'll do my best to post a complete Video tutor soon. Finally I wish to say "Good Luck" to Leandro. I'm sure he will achieve his dream to make the best VEP Combo Multi Instance. BTW. The topic is SOLVED, so I'll be highly appreciated if you stay away of off topic guessing, alternatives etc.

There are no issues with the AG Articulation Scripter. AG system is 100% compatible with Logic 10.4.5. BTW. Lets remind you that AG system offers an additional alternative (without Scripter) - saving the AG Editor Presets as Logic Art Sets.

AG articulation system offers a Program Change Articulation Maps triggering method. I.e the Program Change automation can be saved as a SMF and used in other DAWs or notation software. AG system offers a way which can transform the Program Change automation into Text Control Points automation (inside Logic). There is no problem to convert the old project Key Switches into Program Change (later into Text control points if you want) using "Project MIDI Transform - one go" method offered by AG.

I'm a cross Cubase & Logic user since the first versions of these applications. I admire that you have noted that the Steinberg Expression Maps are far away regarding your poor Logic articulation switching alternative. The Steinberg Maps (Art Mapping idea) is the best, because it is designed to work with all sorts of old, current and future Instruments and you do not have to wait for the next Scripter version (provided by your Art developer) which is specially designed for a specific Instrument. This is typical for all homemade Scripter based tools offered on the market or the free ones. At this moment, all Articulation switching systems which are based ONLY on the Scripter are absolutely poor and limited and cannot be compared to the Cubase Expression Maps. We at Audio Grocery (AG) clearly realized the technical limitation of the Logic Scripter MIDI FX plugin and decided to use it only as an Articulation Player and develop a powerful stand alone software Logic Articulation Maps EDITOR which is based on the Cubase Expression Maps technology. During the new AG EDITOR software development we focused on two important points: 1. We had to developed a similar EDITOR which can be used from the Cubase users (who are used to that system), knowing that one day we will create a hybrid Cubase/Logic compatible Articulation mapping software - we are working on that... 2. We had to develop a much better Articulation Maps system than the Cubase Maps which includes: lots of simultaneous Map selection & editing batch functions, powered by quick key commands (which is not possible in Cubase yet), as well as to create an unique iPad Articulation teleport system which exports the Articulation Maps to an iPad remote application and creates iPad remote layouts automatically with the correspondent Articulations Names, Group Names, Colors etc which correspond to the DAW ones - this is revolutionary! Regarding your Cubase migration. It as an awesome application which will give you more additional features for some specific projects. To be honest there is a problem with the Expression Maps time creation. The Maps Editor does not offer quick batch Maps creation and parameters multi selection editing, so you have to create Map by Map manually and this is really weird and takes 10 times more than the AG Maps Editor software for example. Note: My reply is related to "Cubase vs Logic Art Maps" mostly, just to give you a clear idea of the technical specifics. AG

Heh, it looks quite complicated cause the topic is labeled as "Not send back incoming Midi" and I read advices about Midi sending Skanker, I guess you have some midi feedback issues and you want to prevent that somehow? If so, here is something regarding the Logic user manual: Turning MIDI Thru Off Regards, A.G

Thanks Jordi for posing that as a basic Environment setup. By the way this is the most used one and I got it just to check it up if you use that known technique... I'd like to make a little note about that known technique using Transformers as "Top Cable" key range splitters. There is one major problem in that - the OTHER performance midi events like Pitch Bend, Modulation, Expression (if using any pedals) etc. The other events go to a certain channel - in your scenario that all are transformed to ch.3 right ? It is not the best but the very simple way is to just duplicate & channelize one midi path into 3 midi pats and set the wanted key range "Limit" in the duplicated/channelized paths. In this scenario the "Other events" will be copied and channelized as well. Let's say you play the upper piano range and use expression then the expression will be recorded to the three instruments cause it is copied to ch.1,2 &3 but it will affect only ch1 cause you play the upper part only. If you play simultaneously lower part and the upper part then the expression will be recorded on the all 3 midi channels but it will affect the playing instruments only etc. There are more intelligent solutions I guess, but I prefer to outline something very basic and simple like the setup I show in the image below . In this setup I use three Standard Instruments set to "No Port" and channels 1,2,3 per each instrument object so I can use them as Channel transformers and as Key range limiters using the "Lim" setting in the Inspector to set the Upper, Middle and the Lower key ranges you want. The "Autodemix by midi channel" project setting must be enabled to put Logic into a Multiplayer mode as was mentioned above and the Instrument tracks have to be set to midi channels 1,2,3 and armed ! There is a Bypass (On/Off) Cable Switcher button so you can use it to enable disable the Environment Key range channelizer (the button can be remote controlled via CC12). I have attached the template below. A.G key_range_channelizing.zip

Hi guys, My advice is to ask the Melodyne support team about this issue. Though I have been a Melodyne Demo maker long time ago (being familiar with that app in details), I'm used to bounce my tracks out of the DAW I use and fix them in Melodyne (like DanRad offered here). Personally, if I have to make a beat maping of any real time recorded tracks, I prefer to do that first in Melodyne and import the Tempo map into the DAW for later arrangements etc. A.G

To my opinion such extreme audio timestretching is dependable on the audio material and in many cases it may come to funny results. As a whole, forcing low to higher tempo time stretching works better until the allowable auditioning (regarding the audio Q artifacts and the singing speech if any ). For example the sample library developers could be very happy if they can offer one BPM sample version "Phrase" recorded in 72 BPM using some "Magic" Time Machine. Unfortunately there is no such magic TM yet, that's why they have to record the original at least in 72, 102 and 132 etc for instance... A.G

I guess you are talking about the slow envelope Attack right ? One alternative is to select the region(s) in question and set some (Negative "-" ) region Delay settings in the Track Inspector so Logic will play that region(s) earlier of the beat. In this scenario the note events inside the region can be 100% Quantized to the grid.

I'm away of my Logic right now, so I'll try to assist offline... In (Fig.1) I see "One shot" NRPN (Non-registered parameter number) midi events. The NRPN message pattern includes three Controllers like CC99,CC98,CC6. They can be sent in "One shot" (Fig.1) or one by one (Fig.2), where the Controller number message ORDER is the most significant factor -> # 99,98,6. If this order is OK then there are no problems. Note, sometimes there are some event duplications (Fig.1) like 99/17; 99/17; 98/31;98/32 etc. As you see CC98 is duplicated two times using values 31 after that value 32. In this scenario the last value update "32" is valid! As far as I see the same starting pattern shown in (Fig.2) CC98=31 may cause the problem i.e CC98=32 ( see Fig.1 last message update ) etc. Regards, A.G

This is correct, I found it out immediately (by chance) after the new forum look update. Lots of the other forum look templates do not support such feature so it will be good idea to place some label, or hint about that. This forum topic (started by the long forum user Ski) confirms that "hidden" feature.

Класная работа! Молодец A.G

One more alternative which works in the current and the former Logic versions is to create Text fader objects in the Environment (Mixer) and place them on top of each channel strip (each Arrange track is routed to a given channel strip in the Mixer). You can type some notes inside each text fader (label), make it to behave "As Menu" (by checking this option in the Text fader dialog), color the text faders "Note" labels, set the Environment mixer "As Float" and save as a Screenset (s) # etc.