Darn it. Have been waiting for this.
Disappointing.
The VI app was a lifesaver for those of us that use VSL on a remote computer.

I had really hoped this would be on the docket. Sticking with VI for now I guess.

Yup, confirmed working for me as well now

Thanks guys!!!!!

Hoping sooner than later :)

Originally Posted by: santamorphic

 

Hi magnumpraw - 

It's a drag huh. Did you have any issues moving back to VEP6 with projects saved in 7?

Thanks!

No, anything saved with 7 would not open in 6. Luckily I discovered this in a week where I was strictly doing upgrades and testing. I had only made an hour's worth of changes to one of my templates when I found the issue. It was an invonvenience to revert and recreate what I had done, but not the end of the world. I am running 6 for now while in production deadline mode. 

Will look at 7 again once this gets sorted.

***I should also mention that I found the load time was greater relative to the size of the VEP project.
-When unfreezing the VEP instance in Cubase and connecting to my Synth-5 computer that has only 25GB of RAM loaded, VEP7 connects in 30 secs or so (still longer than on VEP6 though).

-However, when unfreezing the VEP instance in Cubase and connecting to my Synth-1 computer that has about a 100GB RAM footprint, it can take up to 7mins to unfreeze and connect.

Both of these processes only take seconds in VEP6

I have experienced the same issue on Cubase 10/Mojave (Main DAW) and W10 (slave comps)

My template has my 6 slave VEPro instaces saved in a Freeze state (this is for various workflow reasons).

When I unfreeze an instance, VEP6 only takes a couple seconds to unfreeze and connect to the slave comp.

VEP7 takes over 5 mins!!! It is also much slower when refreezing that instance in a project.

I had to just revert to VEP6 on all my computers for now. Hoping this gets resolved.

yeah, it's strange. When I unfreeze an instance connected to my Strings slave computer, VEP6 takes 5 secs to connect. VEP7 takes 7 mins!!! to connect to the same slave computer when unfreezing. 

If I just have the VEP7 plugin loaded on my host but not connected, it only takes a few seconds to connect. But something about coming out of a frozen state and connecting brings VEP7 to its knees. It also is MUCH slower to initiate the freeze process than VEP6.

I upgraded to VEP7 a couple weeks ago, but have run into a major stumbling block.

I work in Cubase 10 and have 7 VEP instances connected to slave computers running a rather lage orchestral template. I keep the instances frozen until needed (for a few different reasons).

The problem is that when unfreezing VEP7, it takes upwards of 7 mins!!! to reconnect to the slave computer. I rolled back to VEP6 and have no issues unfreezing and getting an immediate connection. 

However before discovering the unfreeze issue, I did a fair amount of modification to my VEP slave templates and VEP6 won't load them up. Is there anyway to access those templates from VEP6, or do I need to reconstruct the changes?

Thanks!

Main Comp: Mac Pro Trash Can (Mojave)

Slave Comps: Win 10 PC's 

Originally Posted by: A.G

Originally Posted by: magnumpraw

This is good info. Does it work with Cubase? At first glance it appears like it’s Logic only.

SY ART Tools v1.0 is for Logic indeed. We are working on our Articulation Maps Editor so it can save the presets as Cubase Expression maps format (i.e it will by multi DAW compatible Logic <=> Cubase). After the Editor update we will be able to convert the SY Art Sets into Cubase Esp.Maps and update SY ART Tools as well.

Looking forward to this happening. Have bought all the Synchron stuff so far, but it's still sitting in the proverbial box.

Originally Posted by: mh-7635

I'm not Synchronised yet, but iPad control is so entrenched in my workflow that I wont even consider purchase until it is in place in one form or another so this is a +1 also.

Yeah, I bought SY perc and strings, but sadly they have sat completely unused since the new contextual paging system (which would be awesome BTW with a dedicated app) is too complicated for me to figure out a way to control it with lemur.

My workflow kind of requires manual control of articulation switching. Hopefully we'll have something from VSL sooner than later. wink wink.

Originally Posted by: FabioA

well, I definitely add my vote here. But I see Paul's point here.

Honestely, how many steps back should be expect with the new player? If the goal is following the interest of the majority of people, I'd say many. If the goal is to deliver a professional and handful product, other than of course following the interests of the majority of users and trends, I'd say not much.
I know the remote app was a pretty unkown feature, I also started using it after years it was released. But I really hope I will not have to program a lemur patch for VSL instruments as well.

Don't get me wrong, if VSL will decide not to implement it since many users just don't use it and users which use it already have a dedicated software for that porpuse (and they may prefer to control every VSTi they have within the same software), I perfectly understand.
But be sure every professional user has a touch screen with a sort of remote control to navigate its huge templates.

This is probably true when figuring the vast majority of users, but I can't imagine most people using VSL as a professional endeavor don't have Lemur or other touchscreen templates to navigate their libraries (every single person I know does). As for myself, I haven't really put Synchron into use yet cause I haven't had time to program a lemur set for it yet.

The reason I started the thread in the first place is because I wasn't sure how hard it would be to implement with each layer being contextual depending on the previous layers' selections. This feature is amazingly powerful, but reasonably complex to implement a physical interface for.

Has anyone got a working lemur set going for SY Strings?

Ha! ok, thanks for the feedback Paul.

I changed the title of the thread to be more specific. Comon people! Let's hear your +1's!

The Synchron Player is so awesome!

But please tell us there's an iPad app that well be available to harness it's power? 

The VI Pro Remote was very useful for Navigating patches on a remote machine.

I have had this exact same issue. If I disconnect a VEPro instance while the session is active and then try to reconnect, the slave instance registers as connected, but no MIDI data is transferred. In Cubase, the plugin no longer sees the slave computer in the list of available instances, but it does not register as being connected to any instance.

This happens in Digital Performer as well as Cubase.

I think I just wet myself a little.

I have run into the similar issue in DP and Cubase. Its been happening for at least 8 months now.

When I load a template that has a Decoupled VEPro, it connects fine to the slave computer. BUT if I have to disconnect the instance for any reason, I get the issue as mike harper described above.

When I press the connect button on the VEPro plugin and connect to the SLAVE instance, the SLAVE computer shows a connection, but the plugin in DP or Cubase does not show anything connected and still has the connect button active.

I am using static ip's for all my computers.

William. I sympathize with your headaches, but this thread is specifically for those having issues with stuck notes in DP as the thread title suggests.

You may want to start another thread to discuss with other users solutions to stuck notes with the standalone version. If there are many others out there with the same issue, I'm sure they would appreciate discussing solutions and findings with you.

Let's keep the threads on topic though so that those experiencing this specific issue with DP in particular can share information and findings that will be more likely to be specifically helpful since they will have similar setups.

Thanks so much!

Has there been any progress on this? I know VSL's stance has been that it's a MOTU issue, but it is still going on. Things seem to work fine as long as we only use certain plugins that come in contact with the VEPro returns. IE we can get away with sending a VEPro return to a ProVerb or Waves RVerb plugin, but instantly get stuck notes if we make it an Altiverb or Lexicon Plugin.

This has been going on ever since DP 8 and has been a real drag as we are limited in what we can mix with.

Any updates would be appreciated. Thanks!

excellent. Thanks!

Thanks Paul. I had seen that one too, but what is confusing is that I read several posts like this:

http://community.vsl.co.at/forums/p/36285/223392.aspx#223392

which seem to encourage jumbo packets. Seems like mileage may vary. I came across one where someone said said VE Pro "supports" jumbo frames, but I can't find it now.

Didn't know if there was an official recommendation from VSL or if we just try and see what works better?

I've been scouring the forum trying to find a definitive answer to this, but so far it seems there are mixed thoughts. Several posts say don't turn on Jumbo frames, that it causes problems. Then others say to absolutely turn it on and that VE Pro specifically takes advantage of jumbo frames.

I realize that JF's are an all or nothing setting meaning all the computers/switches have to use them or not. But I've also read that with current gen processors, it's possibly not even an issue?

I have 1 main 3.33 GHz Xeon 6 core Mac Pro running W7 (Bootcamp) and Cubase

I have 4 slaves all with i7 processors and intel network cards

I am using a Netgear Prosafe Gigabit switch.

Is it beneficial to use Jumbo Frames?

Thanks!!!!

Just adding my voice to the conversation and confirming that we have the same issue. 

After extensive testing we were able to confirm that the stuck midi notes were indeed an issue brought on my certain plugins being anywhere in the signal path with a VEPro instance. Altiverb was one of those. MOTU's proverb and the Waves verbs seem to operate correctly. We tried with both VST and AU getting the same results.

Hoping for a fix on either end to make it work.

If VSL would like, we have a session that almost 100% of  the time will exhibit stuck notes within a certain 8 bar stretch that we could send.

I updated the VI Pro software as well but had the same problem.

I however resaved the session on my Home studio computer and my Studio computer will now open the session.

Thanks for the help and ideas!

Ok, so I have downloaded and reinstalled VEP 5 on each computer.

I have downloaded and reinstalled elicenser on both computer. 

I have made sure preferences including audio/midi channels were the same.

Still having issues. I've been doing this for years and have had no problems till now. Dunno what it is about this build. Is it possible to revert to a previous one? I'm on OSX 10.8.3

I have run into an issue with VE Pro 5.1.12167. I have 2 identical setups at my home studio and my recording studio. I am trying to load a Pro Tools (10.3.2) session at my recording studio that I made at my home studio. There is 1 instance of VE Pro in the session. When I try to open it I get the error:

"The project you are trying to load was created with a newer version of Vienna Ensemble Pro."

Both machines are running 5.1.12167 6(64-bit) server. I have tried redownloading the VEP 5 installer and reinstalling, but am having the same issue. 

Help! I can't do my recording session. 

Thanks!

(OSX 10.8.3)