I have to switch over to my M1 system this week, one way or the other. At the moment, I'm working on a small project in Pro Tools, which runs in Rosetta anyway. Is anyone having acceptable results with Pro Tools (latest version 2022.10.0.134) and the VEPro7 plugin?

Hoping that by the time I have a bigger score to write in DP they'l have the MAS plugin written-- and if not, I'll use the AU plugin for my VSL libraries (running on my Intel machine) and run everything else native on the M1. Thank god for DP's V-Racks...

I jumped in with Silicon because I need it for my workflow, my DAW no longer fully supports my 5,1 Mac Pro. I'm trying to figure out a strategy for getting along without a native M1 version of VEPro 7.

I've seen mention of the AU plugin working natively under Silicon-- is that correct? If so, is it possible to use it in Pro Tools and DP11? I imagine not, as people would be doing it, but if so, I could still run all my VSL software on my 5,1 slave.

If not I can run everything that's NOT vsl on my Mac Studio and give up my vsl libraries. Unless there's some convoluted way to get MIDI to VEPro 7 on my slave using Audio MIDI and the MIDI networking feature.

For example, could I run some kind of simple DAW in input mode on the 5,1 slave with the VEPro 7 plugin running, connected to the VEPro server on the same slave, and then send MIDI to the DAW from my Mac Studio? I could get the audio back to the Mac Studio either with Bidule or ADAT lightpipe between the slave interface and the master interface (MoTU 828es and 2408 Mk III). Is this crazy???

I'm limping along with my old Mac Pros waiting for this update, but clearly VSL has hit a wall somewhere with the M1 port, maybe multiple walls. I'm finishing up a score in the next few weeks but can not limp along with my bunch of old cheesegraters any more, I have to make the switch before the next serious project comes in. Does anyone have a workaround (compatible with DP 11)? A substitute for VEPro that can run native?

Haven't posted on this topic for awhile, but VEPro v7.1.1329 has been fixed. MAS works fine now.

Email VSL tech support, they'll send you a link. Hopefully they'll have a new version that fixes this in a few days.

I rolled back VEPro to the previous version and all is well. Caveat- you can't do it with Vienna Assistant, it won't install the MAS plugin. Use the old-school standalone installer.

From your mouth to God's ear 

This problem exists in DP with any VI. For example, we tested it with a basic MoTU VI, in the actual sequence on the host computer (no VEPro, Bidule, etc.), and it is still a problem. Take the VI out, and record into a MIDI track that's not connected to anything, and MIDI is recorded correctly, regardless of buffer setting. By the way, I can set Pro Tools up with the same parameters and it does not exhibit this problem. All modern DAWs compute where to record the MIDI note regardless of buffer size, latency, etc..

Finally, this problem does not exist with AMD PCs or M1 Macs. You can record MIDI with a VI and a 1048 buffer on a M1 MacBook Pro and the MIDI notes will be recorded exactly as you played them. Matt Batson and I did a lot of testing on this, and the engineers confirmed it.

Originally Posted by: evang42

I also use DP11 and am a beta tester and can report issues directly to the MOTU devs. What are the steps/circumstances that cause the midi timing bug w DP11/VEP you’ve found on intel???? This needs to be fixed asap regardless of AS transition.

With higher buffer settings (e.g. 1048), if you are routing a MIDI track to a VI (any VI, even a MoTU VI), MIDI records about 60 ms late. Also "Fine-tune Audio I/O Timing" does not work on these machines. The only workaround is nudging MIDI back into place after recording. I've been working extensively with Matt Batson in tech support, and the engineering team has been made aware of the bug. They have reproduced it on 2 different Intel machines, and confirmed that it does not happen on their AMD PC or their M1 Mac Mini. I don't know that it is a priority for them though.

There is an extensive thread about this on MoTUNation, "MIDI recording late", where I document what's going on in detail (though you may have to wade through some off-topic or uninformed posts to see it). If you have access to the engineering team and can help nudge them toward supporting the older Intel machines, that would be great!

+1. I am waiting for this to transition to M1, especially urgent because my DAW is DP11 and there is a MIDI timing bug with DP11 on older Intel machines, so until I switch I'm using annoying workarounds :(

Working under Rosetta 2 sounds too dicey, though if any of you have had good experiences, please post.

No ETA yet??

Thanks, Paul. I don't need to run my rig at 96k for scoring work, only for the occasional overdub on a record, where I don't need to run many VIs in VEPro.

Pardon my naivety, but do I have to run VEP standalone (on my slave computer) at the same sample rate as my DAW on my master computer? Or does the VEP plugin do all the work in matching sample rates? I've just started doing sessions on my DAW at 96k and want to make sure VEP will work correctly with it.

Hi-

I've seen a few other posts about this but they haven't help me to solve my problem. I usually use Digital Performer (v7 for a long time, and now the new v8), and have been using VEPro 5 to host both VSL instruments and PLAY instruments, both on my main computer and on my slave. I've never had a problem. Now I want to use ProTools 9 with VEPro 5 on a slave machine (mostly to use as a virtual effects rack with Altiverb, guitar amp simiulators and other stuff) and I can't get Pro Tools to "see" the slave machine (they are both 8-core Mac Pros running 10.6.8). Both machines are running the latest versions of VEPro 5. I've tried running both the 64-bit version and the 32-bit version on my slave machine. When I add an instrument track in ProTools and put VEPro on an insert slot and click "Assign" nothing shows up. If I quit PT and open up DP 8, it will find the VEPro instance on my slave machine, so I know the tow machines are communicating. Either it's something really dumb I'm missing or there's something about PT9 that's causing the problem. Any ideas???

Thanks-

David

The problem seemed to be when I was hosting the VSL instruments in VEPro 32-bit along with a lot of East-West PLAY instances. I just pulled all of my VSL instruments out of the 32-bit server and am now hosting them in VEPro 64-bit. The distortion went away on all of the sfz samples. Plus everything sounds better.

Thanks-
David

Digital Performer 7. I get distortion playing one note at a time, independent of whatever volume I play at (via MIDI CC # 7),

The sfz articulation is the only one this happens on; legato, portato, staccato all sound fine.

Hi,

Maybe I'm missing something obvious, but the sfz articulation on all my VSL woodwind libraries distorts. I have the SE WW bundle and standard download instrument libraries for flute, oboe, clarinet and bassoon.

I did a search here for "distortion" but didn't find anything, but did find the problem when I Googled it-- in an old Sound on Sound review of the VSL libraries for Gigastudio.

Thanks,

David Mansfield