(English translation below)

J'ai bien peur que non Cyril. Et c'est bien frustrant. 

Il semble que l'intégration des AU3 (dans Logic en particulier) soit encore inachevée. Si on peut utiliser des ports désormais, ils sont limités à 8 par instance et chaque port ne donne accès qu'à 16 canaux. Ça ne serait pas si mal si l'intégration était complétée, mais plusieurs briques de Logic ne gèrent toujours pas les ports. Le Scripter par exemple, qui est important pour moi en raison de l'utilisation d’ART Pro de Audio Grocery. Je pourrais sans doute me rabattre le système d'articulation de Logic, mais je préfère voir les changements en texte sur les régions midi.

Après plusieurs essais infructueux avec les AU3, j'ai donc décidé de conserver mon approche actuelle (pour un temps du moins). J'utilise les outils de AG avec des instruments multitimbraux de Logic VEP et les VEP Event Input (une instance par port). Ça me donne un maximum de 48 ports avec 16 canaux chacun. Donc, en pratique, 48 instruments multi-timbraux (pour un total de 768 instruments). Je dois, évidemment, prendre bien soin d'insérer un plug-in I/O de Logic sur chaqe instrument multitimbral sinon ça dérape complètement! Par ailleurs, j'ai eu souvent des soucis (latence, problème de synchronisation) lorsque j'utilisais des pistes audio en même temps que mes instruments VIP avec VEP/MIR. Mais Logic accepte mieux depuis l'année dernière cette dernière astuce imaginée par Vienna (à l'époque de VEP4, si ma mémoire est exacte).

Il faudra être à nouveau patient…

C.

=======

I'm afraid not Cyril. And it's very frustrating.

It seems that the integration of UA3 (in Logic in particular) is still incomplete. If we can use ports now, they are limited to 8 per instance and each port only gives access to 16 channels. It would not be so bad if the integration was completed, but several bricks of the software still do not handle the ports. The Scripter for example, which is important to me because of the use of ART Pro from Audio Grocery. I could rely on Logic's articulation system, but I prefer to see the text changes over the midi regions.

After several unsuccessful attempts with the AU3, I decided to keep my current approach (for a time at least). I use AG tools with Logic VEP multitimbral instruments and VEP Event Input (one instance per port). It gives me a maximum of 48 ports with 16 channels each. So, in practice, 48 multi-timbral instruments (for a total of 768 instruments). I must, of course, take care to insert a plug-in I / O of Logic on each multi-instrument or else it completely derails! In addition, I often had problems (latency, synchronization problems) when I used audio tracks at the same time as my VIP instruments with VEP / MIR. But Logic agrees better since last year this trick conceived by Vienna (at the time of VEP4, if my memory is correct).

It will be necessary to be patient again ...

C.

Originally Posted by: C.B.

I'm afraid not Cyril. And it's very frustrating.

 

It seems that the integration of UA3 (in Logic in particular) is still incomplete. If we can use ports now, they are limited to 8 per instance and each port only gives access to 16 channels. It would not be so bad if the integration was completed, but several bricks of the software still do not handle the ports. The Scripter for example, which is important to me because of the use of ART Pro from Audio Grocery. I could rely on Logic's articulation system, but I prefer to see the text changes over the midi regions.

FYI, Scripter has already been updated to be port-aware.  This is great news.  Unfortunately they entirely broke Scripter in other ways in 10.4.5, and in my opinion it should not be trusted at all in 10.4.5, hopefully they will fix those bugs in 10.4.6.  

Other parts of the enviornment, however, are not port-aware.

But if you setup Multi-timbral AU3 enviornment strips, like VSL's templates, then you will see a port parameter in track properties and it totally works fine.  Yes you're limited to 8 ports of 16 (minus one).  So 127 tracks per VEP instance, which is not 768 like Cubase and StudioOne and DP...but its sure better then what we had before with only single port of 16 channels.

what went wrong?  its working very well for me.

Originally Posted by: Cyril Blanc

Hi

I have my own big templates using IAC or 

Do I move them to AU3, this is the question !

Apple has clearly been making changes to LogicPro to support AU3.  There are still some more changes needed, but I think that is the general direction things are going.  I don't know what you're doing with IAC?  But I feel very good about discontinuing any further effort with the multi-port enviornment macros I was using before for my LPX-VEP templates.

I can say that if you can live with 127 tracks per VEP instance, what is there now in place works quite well you just need to start out with one of the templates, or create a bunch of channel strip objects in the enivornment on the fly as you build up your own template.  I don't know why anyone wouldn't use VEP AU3 honestly, but if you want more than 127 tracks per VEP instance, then maybe not.

Sorry AG, you don't know what you are talking about.  Yes Scripter is completely broken in 10.4.5 in a very fundamental way and is easily susceptible to event data corruption.  There are certainly possibilities that scripts might accidentally work ok without running into the problems in 10.4.5 Scripter, but its very broken in a very fundamental way.  If you have extensively tested your own scripts and are confident that your scripts are somehow not running into these problems than I take you at your word, but what I am saying is absolutely correct about Scripter being broken in 10.4.5 in a very fundamental way.  I find it hard to believe that your scripts are not runing into problems also, but hey...maybe they aren't, that's great news for your users, but still Scripter 10.4.5 is very much badly broken in 10.4.5 and if anyone is dependent on scripting for their work I would highly reccomend they stay on 10.4.4 for now.

Are you even aware of what the Scripter bugs are in 10.4.5 in order to be sure your own scripts are not suffering from the discovered data corruption?

You can read more information here:

https://www.logicprohelp.com/forum/viewtopic.php?f=45&t=142778

I highly encourage you to test  your scripts very thoroughly, try many situations and make sure it is actually doing what it is supposed to do in all situations, because without question the Scripter 10.4.5 engine is very broken.

and no I am not using your product.  I purchased it and immediately discovered it was not sufficient for my needs. I asked you for a refund and you said no.  So technically I am a registered paying customer, but I am not using it and will not be.  I'm glad to hear that apparantly your users are not being negatively effected by the horrible bugs in 10.4.5 Scripter.  Hopefully you are looking into the bugs I have documented and are checking to make sure your scripts are not running into them.

I haven't stated anything about AG.  I am stating emphatically that Scripter 10.4.5 has fundamental serious bugs that are very easy to cause event data corruption.  If your AG scripts are somehow by sheer luck missing those bugs, than as I said that is great news for your users.   This is way off topic of the thread.

Originally Posted by: A.G

You said: Scripter is completely broken in Logic 10.4.5 (see above). I did not agree and gave an example with AG Scripter.

yes it very much is.  I do not think you even understand how broken it is, but it sounds like your scripts might be accidentally be working ok...or they might not be and your users just don't realize it yet.  Data corruption can be happening and they don't even realize it until one day someone starts wondering why they are seeing the wrong keyswitches happening and they can't figure out why.  The bugs in 10.4.5 are very severe, I'm sorry you don't understand that, but that is true and in my opinion 10.4.5 Scripter should not be trusted by anyone for anything.  But if somehow your scripts are so bare bones simple that they are skating through without problems, then maybe you are lucky.  This is way off the topic of this thread.  The op did not ask about AG.