Dewdman42 Posted June 20, 2019 Author Share Posted June 20, 2019 The stereo one? Are you on 10.4.5? Just need to know what worked or didn’t work Soni can update my template instructions Quote Link to comment Share on other sites More sharing options...
jmmusic Posted June 21, 2019 Share Posted June 21, 2019 So I've come across one issue while using the new AU3 template: even though VEP recognizes tempo info from LPX, my Kontakt instances do not. This is a big problem for libraries like Signal, Rise & Hit etc. Yes, "Ext" is selected in Kontakt's master pane. I haven't tested other tempo sync'd VSTs yet but I'd love for someone to see if they can replicate my issue. The issue is not present when I connect to my VEP server with the regular stereo VEP plugin, so maybe it has something to do with MIDI clock only being sent over certain ports. At this point I'm in over my head. Quote Link to comment Share on other sites More sharing options...
Dewdman42 Posted June 21, 2019 Author Share Posted June 21, 2019 (edited) It’s not midi clock, but "host transport sync"; but report this to vsl support it sounds like a bug either in vep AU3 plugin or lpx. I can confirm its not working for me too. Edited June 21, 2019 by Dewdman42 Quote Link to comment Share on other sites More sharing options...
Dewdman42 Posted June 21, 2019 Author Share Posted June 21, 2019 Also, you can still use the template, but whenever you need a track with clock sync, then you'll have to use a separate instance and the old VEP AU2 plugin. Quote Link to comment Share on other sites More sharing options...
Dewdman42 Posted July 24, 2019 Author Share Posted July 24, 2019 (edited) I replaced the AU3 templates. Some stuff changed in LPX 10.4.5 related to the way instrument channels are handled, and though these kind of worked, they were created in 10.4.4 and the project files were not in my view completely compatible with logic 10.4.5+. It mainly effected the click channel. Anyway, see post above for a better way to create AU3 templates ad-hoc as you go, and a new starting 1270 track starter template. VSL's AU3 templates are also negatively effected. Instructions: viewtopic.php?f=9&t=143416 Edited July 24, 2019 by Dewdman42 Quote Link to comment Share on other sites More sharing options...
Ashermusic Posted July 24, 2019 Share Posted July 24, 2019 works fine here. Something about how you're using Logic. Please provide more details about the exact steps you're taking. Hey Dewdman, thanks for all the heavy lifting you are doing on this and my apologies that I am dealing with other things and not giving feedback. In your opinion, if one s building articulation sets in Logic Pro for VE Pro with 16 articulations and is perfectly content with that, is there any advantage to using AU3 over AU2 or even VST in VE Pro 7? Quote Link to comment Share on other sites More sharing options...
Dewdman42 Posted July 24, 2019 Author Share Posted July 24, 2019 (edited) I just updated the post again with a 1270 track AU3 template that I recommend everyone start out with. Read new thread as of 1 minute ago to understand the issues. New thread here: viewtopic.php?f=9&t=143416 To your question.... If you are content to never use more than midi port 1, then I see no reason AU2 wouldn't be fine. AU2 also supports the undocumented aux track trick, which AU3 does not in Logic Pro as of this writing. With AU2, as you know, you can have up to 16 channels per VEP instance, so that could be 16 instruments or one instrument with up to 16 articulations, which is probably how you tend to use it in your one-track-per-vep-instance mode of operation. On the other hand, aside from the missing aux track trick, I have had no problems with the AU3 plugin and it does support up to 127 midi channels per VEP instance through 8 ports, so that gives you options for more articulations, or more instruments, etc.. It is for now slightly laborious to setup compared to 16 part multi-timbral, until Apple will hopefully figure out they need to give us the option to create up to 127 multi-timbral parts from the new tracks wizard. But that should not effect you at all if you are constrained to 16 parts anyway. I do think AU3 will be the future for VEP and I see no problem in using that version as long as you don't need the aux track trick. VST is not applicable to LPX. In Cubase S1 and other hosts, you can use VST3 to get 768 midi channels per VEP instance. Edited July 24, 2019 by Dewdman42 Quote Link to comment Share on other sites More sharing options...
Dewdman42 Posted July 24, 2019 Author Share Posted July 24, 2019 Also, the AU3 VEP plugin supports up to 25 stereo aux returns, I'm not sure what the old AU2 can do, it might be limited to 16 stereo returns. Quote Link to comment Share on other sites More sharing options...
Ashermusic Posted July 25, 2019 Share Posted July 25, 2019 OK, presently for me then no real advantage. Quote Link to comment Share on other sites More sharing options...
Dewdman42 Posted July 25, 2019 Author Share Posted July 25, 2019 I agree. Quote Link to comment Share on other sites More sharing options...
Dewdman42 Posted July 25, 2019 Author Share Posted July 25, 2019 well also, to be complete on the answer, we are unaware about internals of either AU2 or AU3 plugin to know if one is somehow more efficient or reliable then another, etc.. VSL is still calling the AU3 plugin "beta" FWIW. I haven't had any problems with it though and like I said, you can still use the AU3 in exactly the same manner as you've been using the AU2 one... no change in workflow. Might be worth trying it out for a while, even in your preferred workflow... I do think it will only be a matter of time, and not too much, before the AU2 version of the plugin will be deprecated. Quote Link to comment Share on other sites More sharing options...
Ashermusic Posted July 25, 2019 Share Posted July 25, 2019 well also, to be complete on the answer, we are unaware about internals of either AU2 or AU3 plugin to know if one is somehow more efficient or reliable then another, etc.. VSL is still calling the AU3 plugin "beta" FWIW. I haven't had any problems with it though and like I said, you can still use the AU3 in exactly the same manner as you've been using the AU2 one... no change in workflow. Might be worth trying it out for a while, even in your preferred workflow... I do think it will only be a matter of time, and not too much, before the AU2 version of the plugin will be deprecated. True, but since they are different plug-ins, I would have to rebuild the VE Pro templates and re-save the patches in the Logic Pro library. That's a lot of work unless there is a clear advantage. Quote Link to comment Share on other sites More sharing options...
Dewdman42 Posted July 25, 2019 Author Share Posted July 25, 2019 No doubt Quote Link to comment Share on other sites More sharing options...
srikantk90 Posted January 30, 2021 Share Posted January 30, 2021 @dewdman. Thanks for this wonderful template. I connected my VEP instrument to the VEP instance. Then, I hit the + sign to create AUX tracks for the VEP instrument. But I'm able to play only the 1st instrument of each port. Anything I'm missing ? Quote Link to comment Share on other sites More sharing options...
Dewdman42 Posted January 30, 2021 Author Share Posted January 30, 2021 Why are you using VePro6? Quote Link to comment Share on other sites More sharing options...
srikantk90 Posted January 30, 2021 Share Posted January 30, 2021 I'm tight on budget to upgrade now But, does it make a difference ? Quote Link to comment Share on other sites More sharing options...
Dewdman42 Posted January 30, 2021 Author Share Posted January 30, 2021 VePro7 added support for AU3 with multi midi ports in a much better way. So much better. Highly recommend you upgrade. You'll have to describe in more exact details what you have done and having a problem and/or post the LPX project you're having a problem with, in order to help you. make things work right. It works, but since its not working for you, then it depends on what you did to get where you are. Quote Link to comment Share on other sites More sharing options...
Dewdman42 Posted November 12, 2022 Author Share Posted November 12, 2022 (edited) This project is coming back alive now that Apple broke compatibility with VePro7.AU3 in the recent LogicPro 10.7.5 update. These multi port macro templates seem to work fine with LogicPro 10.7.5 and VePro7.AU2. I am updating one of the templates a bit and will post it later here. Hopefully Apple/VSL will fix AU3 compability soon in LogicPro though as I still feel that is preferred approach. Edited November 12, 2022 by Dewdman42 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.