kark million

Fantastic! Let us know what they say. Thanx.

So to summarize - somehow since 10.7.5 if you have any external tracks coming in that are Input Enabled, your MIDI monitoring play through on any external MIDI tracks like VEP or your external MIDI to control your outboard synths or whatever, will not work. You'll hear nothing trying to play those tracks live. However, record some MIDI data in and then it will play the data fine on playback. This is clearly a bug and I'm not sure how to report it to a place that will actually take it seriously. I tried calling Apple customer service and well, lets just say I know way more about Logic than the poor soul I spoke to. That is a complete waste of time. Any ideas?

I thought I'd jump in here - the folks at VSL had a look at my template and impressively also figured exactly what Clintone has found, that having anything external coming in to Logic that is Input Monitor enabled, then your MIDI playthru monitoring is not working on any external MIDI, be it VEP or external MIDI tracks. Take a shot at this with my template - connect any of my VEP instances (all the orchestral stacks) to whatever instrument using VEP and you'll find there is no MIDI monitoring going on. However, delete my stack called 'LIVE TRAX' which is the external inputs from Ableton's Live (using Rewire) and you'll see it suddenly starts working correctly. That's because those are external tracks that are Input Monitored enabled. You'll see in my 'DIALOG,' 'TEMP' and 'PRINT BUS' tracks on top as well as the 'STEMS' stack those are all Input Monitored too but this doesn't affect the problem as those are all internal tracks, not external as is the case with the 'LIVE TRAX' stack. STUDIO TEMP JAN 2023 v41.zip

Hey Clintone nope have not solved it. Had someone else working on this and he was able to replicate my problem but also unable to solve it. Something has changed in the architecture of how MIDI thru is ported but so far no luck in figuring it out. I also sent the problem to VSL and they're looking into it too. I'll let you know if I find anything and please do the same!

Thanx Emanuel but the problem here clearly is not VEP. The same issue exists with any external MIDI track I try use in Logic. The 10.7.6 update somehow has changed something about how MIDI is routed/functions internally within Logic when using any external MIDI. (Again with internal software instruments I don't have this problem.) Maybe it's time though as you suggested to consider a template where I have all my samples loaded directly into my Logic template and do away with VEP all together. Not sure how well Logic with function with that amount (over 200) of Kontakt instruments loaded totaling over 100GB of RAM usage?

I have a big template with over 300 tracks with VEP. In 10.7.2 everything was peachy but with 10.7.6 opening this template the MIDI play thru doesn't work for VEP or any external MIDI. So, if I select one of those tracks and play my MIDI keyboard, it sends no MIDI out to the VEP as I'm playing it in real time. HOWEVER, if I record that MIDI data into the track and THEN play it back, it sends that MIDI to the VEP as normal. BTW the internal software instruments are just fine and don't have this problem. If I don't open my template and just go NEW and choose a VEP instance, it works as it should. So I've checked the Project Settings of the NEW file and compared them to those of my template and there are no differences. And I know it's not a VEP issue because the same problem occurs on an external MIDI track. So how on earth could this be happening? What am I missing? It is bending my brain and I've never had such an unfathomable issue with a Logic update before. Luckily I've kept 10.7.2 around but I'd really like to know what the problem is with 10.7.6 and my template as I'd like to use some of it's new features. Anyone else with a similar issue or able to explain this?

Ok so I think you helped me solve my problem! My template is confusing in that my master busses for separating strings, guitars, basses, drums etc etc were going to actual audio tracks so that I could print the stems. The Master busses then went to the outputs. However, what I've done is make all those master busses actual busses instead of audio tracks and then made a separate batch of audio tracks into which the busses feed but on those audio tracks the output is set to none. And that is then where I'll print my stems. Therefore I'm not actually hearing the outputs of those stem printing audio tracks but they're still getting the same information I'm hearing from the master busses. This has now resulted in my solo system working just fine. I don't know why the solo function wouldn't work going thru audio tracks, but whatever the reason I've solved my problem. So thanks!!!

Yes I see the output of your stack is set to the ST out. If you were to change that to a bus which then goes into the ST out you would (I think) lose the ability to solo. In my case my stacks go into buses which serve at Master groups which then go into buses which serve as stem groups and then finally into the ST out. So yes, a little more complicated but one still expects a solo button to do what a solo button is intended to do.

Does anyone know if there is just something I'm missing or can you still not solo a track in a summing bus? My entire template running VEP is using summing busses so in effect I have no solo ability within Logic which is nuts. Hitting the solo button just gets me silence. The whole point of a solo button is so that you can hear just that track. Surely they must be aware of this issue but in the meantime is there any way around this or some kind of workaround?

I've spent a lot of time building a new orchestral template using the VEP multi instrument it makes for you when adding new tracks and selecting 'software instrument' - choosing 'Vienna Ensemble Pro' as the instrument - selecting 'Multi-timbral' and choosing as many parts I need for that particular instrument on the VEP machine. It works great, is super simple and I don't have to deal with the environment. But ... I thought the lack of ability to do automation on the individual tracks within that multi or the inability to solo or mute individual tracks wouldn't be a big issue. But it is! What would the easiest way be for me to change my setup with minimal damage to what I've done already and get my solo/mute/automation happening on each track individually? Is it possible to do this without wizardry in the environment?

I'm on 10.2.4 now and this bug still has not been fixed. Grrrrrrrrrr!!!!

Yes I'm having this same problem since updating to 10.2.2. I can replicate it 100%. I think what it is is that previously whenever I hit stop or play from 'wherever' it would clear the buffer so every time 'capture last take as recording' is hit it would just put the notes from since the last stop or play. However, now it seems to not clear the buffer so if I've been rehearsing a part and then after say 5 passes I am happy and hit 'capture last take' - it puts all the stuff from the last 5 times into the one take folder. And the notes that are bunched on top of each other at the beginning of the take are notes I hit when the transport was not in play. It is a bug they need to fix and the only work around I've found is to 'capture last take' and then delete that before you do you thing. Highly annoying.