you can remove your music and send me your empty song VE and will look at it

@htokieda said:

@Cyril-Blanc said:

16 GB is not much, MAC OS uses most of it.

16 GB is ok if you do office work on a Mac, but not music with VSL instruments.

Replace your VSL instruments with Logic instrument and see if you have the problem.

Then do another trial and you use VI in Logic and test it

If you have no experience with Environnement you are going to sit down and cry !

What you can try :

place a monitor object before the VE instrument , Just play one note and see what is send. Post a screen copy of the content of the monitor object

You need to clear the display of the monitor object by clickink on it's window

@htokieda said:

@Cyril-Blanc said:

How much memory ?

You can check that you do not have a loop by placing a "monitor" object in you "Environnement" at different places.

If you want you can also post a reduced project, so I look at your Environnement ?

Thank you for your comment. I have 16GB ram.

I've never dealt with "Environment" in logic but will look into it.

Yes, I've tested with logic instruments as well as loading the same instruments directly within logic but the issue didn't occur so I came to realize that it was most likely caused by VE Pro.

I know 16 GB is not enough but I doubt it's because of that since it happens with very small projects too.

I'll try looking into Environment setting.

Thanks for your help.

@Cyril-Blanc said:

you can remove your music and send me your empty song VE and will look at it

@htokieda said:

@Cyril-Blanc said:

16 GB is not much, MAC OS uses most of it.

16 GB is ok if you do office work on a Mac, but not music with VSL instruments.

Replace your VSL instruments with Logic instrument and see if you have the problem.

Then do another trial and you use VI in Logic and test it

If you have no experience with Environnement you are going to sit down and cry !

What you can try :

place a monitor object before the VE instrument , Just play one note and see what is send. Post a screen copy of the content of the monitor object

You need to clear the display of the monitor object by clickink on it's window

@htokieda said:

@Cyril-Blanc said:

How much memory ?

You can check that you do not have a loop by placing a "monitor" object in you "Environnement" at different places.

If you want you can also post a reduced project, so I look at your Environnement ?

Thank you for your comment. I have 16GB ram.

I've never dealt with "Environment" in logic but will look into it.

Yes, I've tested with logic instruments as well as loading the same instruments directly within logic but the issue didn't occur so I came to realize that it was most likely caused by VE Pro.

I know 16 GB is not enough but I doubt it's because of that since it happens with very small projects too.

I'll try looking into Environment setting.

Thanks for your help.

I just messaged you privately.

Thank you very much!

Hello

I had a look at the files received,

I had 3 crashes on "plug-in validation".

There is nothing weird in your environment

You use a lot of busses.

You need to narrow down your problem you have to find out if it is a Midi or an Audio Problem

What I will do :

• find you which instrument is causing the problem and if there is only one instrument check you do not have overlaping of the same notes. You can insert "force all note off" messages in your piece to narrow down the part. (I had this problem on a KT library)

i.e. Some players do not like not to receive a C3 "note off" message before a C3 "note on" one !!!!!😤 they think that the 1st C3 is not finished !

Otherwise :

• disable all effects plug ins
• If you still have the problem, disable all the Kontakt instrument and just keep VSL instruments
• if your problem is not solved, "sit down and cry"😀 and trash VE, use VI instead. It's very rare not to find a VST and an AU version of the same "professionnal" plug-ins

Good luck

P.S. Sorry for the typo, VSL should add a spell checker in the great new editor

I'm having the same problem with a note hanging on a new, clean and simple project. Extremely frustrating.

Did you find out ?

@htokieda said:

Hi,

I've been experiencing this issue where MIDI notes get stuck and won't stop playing when I run VE pro in Logic.

It continues even after sending discrete note offs and only stops when I play exact notes that are hanging on my midi keyboard.

It has nothing to do with the size of my project because the issue still happens with small projects.

I've also try running the same instruments directly wthin Logic and it worked no problem.

I know some people have already talked about the same issue in the past but I coundn't find any solutions so I decided to post again.

My specs are: Apple M1 Pro, OS Ventura, Logic 10.8.1

Thank you in advance.

Would love some communication from the developers with an ETA on a fix for this. Know it might be tough if the problem is on Apple's end, but an update would be nice. I've just had to rebuild my entire template without VEP. It works, but loading each project now takes an extra few seconds/minutes to load up depending on how many tracks I have activated...which isn't a huge deal, but those extra few moments of having to wait and load a track really can take me out of the zone. Hopefully a fix is coming soon so I can continue to use VEP!

@mileece said:

I'm having the same problem with a note hanging on a new, clean and simple project. Extremely frustrating.

I just want to say FWIW, I am not having this hanging note problem at all on my system. I know that doesn't help you solve your problem per say, but perhaps it may help to isolate the issue. I am testing this with LogicPro 10.7.9 on MacOS Monterey 12.7.3, and its all running on Intel, not Apple silicon. That is also using AU3 with multiple midi ports in action into a single vePro instance with around 100 tracks.

I think I heard you say you're on Apple Silicon, probably using newer version of both MacOS and LogicPro...but anyway, maybe that can help isolate the problem. Unfortunately i can't replicate it here.

Hey @Dewdman42,

I just moved from my old 5,1 running pretty much the same setup as you. Old system had no issues. Only bought the M2 Mac Studio at the end of last year for tax reasons. The fact you can't replicate it and that my old rig was solid as a rock definitely makes me think it is due to Apple silicon and the newest versions of Logic. Appreciate you chiming in, and hopefully a resolution is on the horizon!

@Dewdman42 said:

I just want to say FWIW, I am not having this hanging note problem at all on my system. I know that doesn't help you solve your problem per say, but perhaps it may help to isolate the issue. I am testing this with LogicPro 10.7.9 on MacOS Monterey 12.7.3, and its all running on Intel, not Apple silicon. That is also using AU3 with multiple midi ports in action into a single vePro instance with around 100 tracks.

I think I heard you say you're on Apple Silicon, probably using newer version of both MacOS and LogicPro...but anyway, maybe that can help isolate the problem. Unfortunately i can't replicate it here.

I think probably at least one of those things, I would probably exclude the MacOS version from the equation and say most likely its related to either LogicPro or AppleSilicon. You can eliminate LogicPro as the culprit by running version 10.7.9 and see if that is still a problem for you on your system. If it works fine on your system with Logicpro 10.7.9, then we will know the problem is LogicPro version 10.8. If it continues to be a problem, then personally I think that would eliminate LogicPro as the culprit as a general case....however...

Apple silicon as the culprit is interesting, hard to say why that would happen under Apple Silicon and not with Intel, but it's certainly possible that either LogicPro or VePro has some kind of Apple Silicon bug in there, ....but I am also suspicious that the problem might be created by Rosetta plugin interactions from either LogicPro or VePro...so what you would want to do is to try to run tests with enough tracks to stress it..but eliminating all plugins that are not native Apple Silicon, in order to see if Rosetta handling of Intel plugins in some way is dropping some NoteOff events somewhere in there. Just a theory.. I don't have an Apple Silicon Mac to try any of this.

Otherwise, I feel for those of you struggling with this. Any other information you can provide about you specific VePro templates, if you are using AU3 or multiple midi ports, enviornment use, etc.. might help, but so far it seems like this is isolated to Apple Silicon mac's, which are usually also running a newer version of Logicpro and MacOS.

So I just built a few small templates. One using multis and the other with just one individual instrument per instance. I used Berlin Woods in the SINE player for some of the tests, and Spitfire Chamber Strings in Kontakt 7 for some others. I used AU3 plugins in Logic for them, then another test with just the regular old VEP plugin. Guess which tests had hanging notes? Every test that used multis created hanging notes, regardless of AU3 or not. Every test I did with individual instruments didn't. Looks like Logic's multis are not only broken when dealing with adjusting negative track delays, but they give ya hanging notes with VEP as well! lol. Don't have a version of Logic 10.7.9 handy to see if it's a Logic version issue or not unforunately. So all tests were done on the newest versions of all systems.

@Dewdman42 said:

I think probably at least one of those things, I would probably exclude the MacOS version from the equation and say most likely its related to either LogicPro or AppleSilicon. You can eliminate LogicPro as the culprit by running version 10.7.9 and see if that is still a problem for you on your system. If it works fine on your system with Logicpro 10.7.9, then we will know the problem is LogicPro version 10.8. If it continues to be a problem, then personally I think that would eliminate LogicPro as the culprit as a general case....however...

Apple silicon as the culprit is interesting, hard to say why that would happen under Apple Silicon and not with Intel, but it's certainly possible that either LogicPro or VePro has some kind of Apple Silicon bug in there, ....but I am also suspicious that the problem might be created by Rosetta plugin interactions from either LogicPro or VePro...so what you would want to do is to try to run tests with enough tracks to stress it..but eliminating all plugins that are not native Apple Silicon, in order to see if Rosetta handling of Intel plugins in some way is dropping some NoteOff events somewhere in there. Just a theory.. I don't have an Apple Silicon Mac to try any of this.

Otherwise, I feel for those of you struggling with this. Any other information you can provide about you specific VePro templates, if you are using AU3 or multiple midi ports, enviornment use, etc.. might help, but so far it seems like this is isolated to Apple Silicon mac's, which are usually also running a newer version of Logicpro and MacOS.

can you explain in more detail the exact setup of your multi's? I can try to replicate the issue on 10.7.9. Please describe exactly how the various tracks are feeding the tracks. Unfortunately I would probably not be able to open your LogicPro 10.8 project file, but you can always try to send me that too and I can just look at it myself if it will load, I would have to swap in different software instruments since i don't own the ones you mentioned.

I would be curious if you get the hanging notes using those same multi instruments directly in Logicpro without VePro at all.

we might be able to really narrow this down and pinpoint the exact problem

what are the midi out channel and port out settings for each of those tracks in LogicPro?

also how many tracks do you have feeding into each vePro instance through AU3?

@Dewdman42 said:

what are the midi out channel and port out settings for each of those tracks in LogicPro?

So if I have the instrument set to MIDI Out Port: 1 (regardless of MIDI Out Channel) we get hanging notes.

Setting the instrument to MIDI Out Port: 2 (also regardless of MIDI Out Channel) looks like we don't get hanging notes.

@Dewdman42 said:

also how many tracks do you have feeding into each vePro instance through AU3?

Happens regardless of how many tracks you're feeding into vePro through AU3. If it's on Port 1, it seems to hang.

Also, when using any other MIDI Out Port besides 1, creating Aux tracks from the instrument track doesn't seem to work. Are Aux tracks created from the Instrument track in Logic (or vePro) not linked to the MIDI Out Port? And by Aux track, I'm talking about hitting the little (+) button on the Instrument track in the mixer. Not a huge fan of using Multi-Timbrel setups in Logic. I like the freedom to adjust individual instrument faders (unless there's a way to do that with multi-timbrel instruments I have overlooked without mucking about in the Environment).

KeplersConundrum, in your picture of Logic, in the Track Inspector I notice MIDI In Port is set to All (the default setting). Unless you have an exact and specific reason for having that default or any other active setting there, I'd strongly suggest you set MIDI In Port to Off on all tracks. That way you eliminate the possibility of an inadvertent howl-round event loop occurring, however momentary it may be. No guarantees, but at the very least it's good practice in terms of 'realtime-system hygiene'. I've no idea why Apple would choose the most potentially disruptive setting there as default. (It's embarrassing now to think of the many times I fell foul of that problem when I first started working with IAC Busses - or "ports" as they're now called - back in the old days when eMagic's Logic behaved impeccably! Lol.)

Anyway, you've done well to isolate your problem to your usage of Out Port 1. Now you have the option of simply avoiding usage of that Port - unsatisfactory and even annoying though that may be. Otherwise you might get caught up in endless nugatory investigations at home and fruitless dialogue here (likely as not for the benefit of some interlocutor's ego and public image cultivation rather than actual benefit for you.)

Oh, also, in answer to your last question above, the additional mixer tracks that get inserted each time you press the little + button on the 'mother' instrument track strip are in no way interactive with the track's Port setting. This feature - sometimes flakey in recent Logic versions - has to do with separately-numbered audio channels returning from VEP. It could of course become part of a special - 'virtual' - multitimbral setup a user might organise for Logic and VEP; but that setup and usage can be tricky and, as far as I'm aware, is very far from typical usage. Have a read of Logic's Help files on instrument mixer-strip aux tracks, etc.; that should set you on the right path without you having to answer endless questions about what you're doing and how you're going about it.

Thanks for chiming in Macker.

As for the MIDI In Port - Setting that to Off means I can't use any of my MIDI interfaces (MIDI keyboard, faders, etc…) And even when I turn it off, stuck notes still happen. Good to know that could be a thing to check if I run into problems later on though, so thanks.

I'm pretty read up on Logic's manual, and I've been using Logic's multis and aux's for a few years now in tandem with VEP with no issue until now. So I'm gonna go out on a limb here and guess that most of the problems I'm facing right now are on Logic's side of things, and not VSL. So until there are some fixes from either end, I'm unfortunately going to just put VEP on the shelf for now and go with a disabled track template in Logic.

Thanks to everyone who tried helping solve and narrow down these issues with me!

@Macker said:

KeplersConundrum, in your picture of Logic, in the Track Inspector I notice MIDI In Port is set to All (the default setting). Unless you have an exact and specific reason for having that default or any other active setting there, I'd strongly suggest you set MIDI In Port to Off on all tracks. That way you eliminate the possibility of an inadvertent howl-round event loop occurring, however momentary it may be. No guarantees, but at the very least it's good practice in terms of 'realtime-system hygiene'. I've no idea why Apple would choose the most potentially disruptive setting there as default. (It's embarrassing now to think of the many times I fell foul of that problem when I first started working with IAC Busses - or "ports" as they're now called - back in the old days when eMagic's Logic behaved impeccably! Lol.)

Anyway, you've done well to isolate your problem to your usage of Out Port 1. Now you have the option of simply avoiding usage of that Port - unsatisfactory and even annoying though that may be. Otherwise you might get caught up in endless nugatory investigations at home and fruitless dialogue here (likely as not for the benefit of some interlocutor's ego and public image cultivation rather than actual benefit for you.)

Oh, also, in answer to your last question above, the additional mixer tracks that get inserted each time you press the little + button on the 'mother' instrument track strip are in no way interactive with the track's Port setting. This feature - sometimes flakey in recent Logic versions - has to do with separately-numbered audio channels returning from VEP. It could of course become part of a special - 'virtual' - multitimbral setup a user might organise for Logic and VEP; but that setup and usage can be tricky and, as far as I'm aware, is very far from typical usage. Have a read of Logic's Help files on instrument mixer-strip aux tracks, etc.; that should set you on the right path without you having to answer endless questions about what you're doing and how you're going about it.

Setting the instrument to MIDI Out Port: 2 (also regardless of MIDI Out Channel) looks like we don't get hanging notes.

That is indeed very strange. I really wish i had a newer version of LogicPro so that you can send me a project to look at it, because i just really think there must be something else that is being left out of this discussion, but its hard to guess just based on your description and not being able to inspect your problem project directly. I find it very odd that Port 1 out would not work and Port 2 would work. please make sure you are not using more than 127 tracks feeding a single VePro instance with AU3.

Also, when using any other MIDI Out Port besides 1, creating Aux tracks from the instrument track doesn't seem to work. Are Aux tracks created from the Instrument track in Logic (or vePro) not linked to the MIDI Out Port? And by Aux track, I'm talking about hitting the little (+) button on the Instrument track in the mixer. Not a huge fan of using Multi-Timbrel setups in Logic. I like the freedom to adjust individual instrument faders (unless there's a way to do that with multi-timbrel instruments I have overlooked without mucking about in the Environment).

Definitely do not mess around with AUX tracks right now. I really don't think those are going to work with AU3 at all.

AUX are working fine for me with VEP AU3, also no hanging notes, but i'm on Intel, Ventura, Logic 10.8.1, multiple instances, ports and channels

KeplersConundrum, you're right: of course switching MIDI In Ports to Off blocks everything - including MIDI keyboards!

Sorry about my stupid mistake - working long into the nights on a major design update of my monster subsystem in Logic's Environment is not conducive to clear thinking during the day! I'd forgotten I typically don't use my keyboards at all when working with symphonic scores and so usually have all MIDI In Ports off to catch any accidentally unmanaged loops in my Environment design (which actually relies on carefully managed IAC Bus loops using non-standard routing).

Anyway, it's interesting that you've not eliminated stuck notes by switching off all MIDI In ports. And I agree with your pragmatic decision to shelve VEP, at least until we know the stuck note problem with Logic & VEP AU3 in Apple Silicon is history.

BTW I'm working with latest VEP AU3 with latest Logic in latest Ventura on an Intel iMac and haven't yet encountered stuck notes (although of course that's of no direct relevance to the issue in your Apple Silicon machine).