and by the way, Kushview is also a great product..that is open source, with a great developer...and worthy of consideration also for numerous reasons...

Originally Posted by: inthefold

VSL's support staff was able to reproduce the bug that I reported. We'll see what comes out of it.

Nice!

Originally Posted by: Macker

I've used other DDMF products and find them to have some ingenuity here and there, but overall of somewhat hobbyist/amateur quality. 

That is absurd.  DDMF make terrific plugins.  MetaPlugin is awesome.  Happy to see VSL working with them on discounting.

If you want something free, I suggest KushView Element which can also host VST3.  Its free as donation ware right now. 

https://kushview.net/element/download/

'I don't have Kontakt7 right now in order to test it in either product and at times Kushview has had some issues with transport sync...but sometimes it works great.  But I still think DDMF MetaPlugin is probably your best bet for temporarily dealing with Kontakt7 until VSL can get VePro up to speed with VST3

VSL has responded to this request numerous times.  They are working on it.  

I have the same problem, but anyway you can just pinch to zoom in on the iPhone.  I suspect this is related to Retina display stuff various iOS zoom settings...  Whatever forum package that VSL is using is not that up to date.  It is what it is.

I did come up with a new question though..  I notice that under my normal Synchron libraries..there are some presets called "prime compatible" or something like that.  What is the purpose of those presets?

Originally Posted by: dfhage

I had an email from VSL support confirming it doesn't work, and there is no timeframe for a fix

Noted thanks.  I am rolling back LogicPro to 10.7.4 for this reason until further notice.  

ps - Just tried to create a new project using VePro.AU3 and immediately started getting wonky behavior with the plugin...so yea...something is broken with the plugin for sure.   GUI isn't redrawing correctly.  Also can't even use the the buffer muliplier control at all...  Well...I don't have any time to dig any deeper and this is not pressing for me so I will leave it to others to wort this out with Tech support....but I would say VePro.AU3 is not usable with LogicPro.AU3 until further updates from Apple and/or VSL.

Originally Posted by: dfhage

I am finding that my AU3 template won't work at all in Logic 10.7.5, confirmed with a few tests, the VEP works fine, the AU3 version doesn't even seem to receive any midi from Logic. Anyone else seeing this ?

Yea I think maybe it has.  I'm not getting some of my projects to play back now.  results are garbled audio at best, leading shortly to freeze or crash of logicPro.

However, keep in mind that this might be a case where Apple broke the project file backwards compatibility.  This would not be the first time they did that.  So opening older projects in LogicPro 10.7.5 might not always interpret them exactly correctly.  There is another reported bug I saw on LogicPro forum along those lines also, and I've seen this kind of thing in the past.  

Try to create a brand new LogicPro project from scratch with a a few dozen tracks feeding to VePro. AU3 and see if it works.  If that works, then it means LogicPro is confused about opening the older project files...  On the other hand if it also doesn't work to build it up from scratch, then more likely the actual VePro.AU3 plugin is no longer compatible with LogicPro 10.7.5 until it gets some update...or perhaps LogicPro broke AU3 mechanisms in some way also..always a possibility...I would leave that to Apple and VSL to figure out, but first...  try to create a brand new project in LogiPro using Au3 and see if it works normally or not.

Originally Posted by: dmansfield

I jumped in with Silicon because I need it for my workflow, my DAW no longer fully supports my 5,1 Mac Pro.

which DAW?  My 5,1 is still working quite well

That is absolutely what I would do, but I can give no advice about the M1 side and the plugin, which to use.

You could use The non pro version of Vienna Ensemble on your 5,1.  Send network midi to it...and mix the audio back into your M1 or wherever using various digital audio means rather then through the plugin...there might be some latency in there and you lose the elegant mechanism whereby normally VePro can do Plugin Delay Compensation to sync everything up perfectly.  But its certainly doable until VePro catches up with Apple Silicon.

Originally Posted by: Michael Canavan

While I can mostly agree with this, but it's been 2 1/2 years since Apple Silicon was announced, along with developer Minis, and 2 years since the first M1 Macs came out. I was around for the first transition from PPC to Intel machines, and I remember only NI dragging their feet a little, they had foolishly not headed Apples warnings to switch from Codewarrior to to Xcode. 

  Part of the problem is Rosetta this time works really pretty well, a maybe 10% CPU hit on average, but it doesn't work at all for VST and MAS if the DAW is not in Rosetta. So the hit is compounded when your DAW is also in Rosetta. Anyway I thought the VEP plug in would be a rather quick port considering the opportunity for VSL to pick up new customers as people used VEP to transition, but that's not the case apparently. 

The last transition from PPC to intel was not nearly as well executed.  Many people, including me, were left high and dry with expensive PPC Macs that would not run the latest tools and become worthless pieces of junk within one year.

This time around Apple handled things much better and the end result is that it is M1 users who ware still wanting and waiting for all of the software world to catch up.  Apple did things in such a way that Intel users would not be left behind..and so far 1.5 years later my Intel machine is still going very strong and still preferable to M1.  You must remember that software developers have to earn money and it costs them money to do any software change, including Apple Silicon.  They will always have to weigh all the factors of what is most important with the resources they have and do what is best for their business....this may mean that M1 users, whom are still the minority...have to keep waiting while other priorities still address the majority of users still using Intel.

I personally am thankful that Apple handled this transition much better then what they did last time from PPC.  We did not get left in the dust and all of us can transition to M1 in a more graceful manner when its time.  

Anyone that jumps onto M1 early and then complains that the software isn't ready, should look in the mirror and ask themselves why they purchased a new M1 before the software was ready.

Originally Posted by: Macker

• Logic can now capture MIDI data from AUv3 plug-ins as regions

This seems to work from AU2 plugins also, not sure why they mentioned AU3 in the release notes.  However, it only does this for live midi as you play it in.  You cannot process track midi regions through plugins and and have the result recorded back to a new region.  Its simply a way to insert part or all of the midi plugin stuck in front of the sequencer.

The first thing you mentioned regarding Create new track with next midi channel is great news, glad to hear they did that, it should be a lot easier for people to construct large multi-port AU3 templates now.

Regardless of what Apple has said so far, M1 users are still early adopters, especially with regards to audio production.  In my view, it's still most sensible to remain on Intel Mac hardware for serious audio production, for at least one more year.   This is not only because of VSL software which is clearly not transitioned yet, but numerous other software and plugins which are still not native.  You MIGHT be able to get some rosetta functionality, but me personally, I won't get an Apple Silicon Mac until I know that I can run pretty much everything I want or need to run in native mode without ANY rosetta shenanigans...which the industry is simply not there yet in many cases.  They will all get there eventually..including VSL, but all I can say is that you have to be patient.  I feel the pain for anyone that jumped on the M1 bandwagon, but what I can say is that my cheese grater is still running absolutely everything without problems...and that is a solution that anyone can still choose to follow today.  Even the current Apple MacPro is still Intel and will run everything just fine.  It was your choice to be early adopter.

Originally Posted by: Ben

You should be able to check it here yourself as well: https://www.vsl.co.at/MyVSL/MyProducts

I would not recommend to trash your eLicenser USB key, you never know when it might be useful (for example offline-converting old project save-files). Or sentimental value ;)

All green except for ViPro2 (which is new free) and VePro6...which I doubt I will ever need again.  But that would be one use case to keep the old dongle around for opening an old VePro6 project perhaps.  Maybe I'll have it framed then... lol

I have had completely great results from the iLok conversion...  Now that Imperial has been also converted to iLok I don't think there is anything left on eLicensor for me...but Ben...quick question...Before I basically throw away my eLicensor dongles or relegate them to a drawer somewhere...how can I verify for sure that all of my licenses have been transferred from eLicensor to iLok and therefore no reason to keep the old dongle around anymore?

Originally Posted by: DaveDrewry

On installing the new version using Vienna Assistant, I find that the standalone Vienna Imperial Piano works fine, but it's not configured correctly for using as a plug-in in Vienna Ensemble Pro.

When I look at the channel in the mixer Vienna Imperial Stereo is not listed under "Integrated" plugins and I get "Errors occured while loading plugin: Toolkit: Vienna Imperial <br><br> Could not open plugin.

Anyone else having this issue?

Seems to be working fine for me in VePro, Standalone and other hosts..all the same.

Does anyone know if there is any way to zoom in the GUI?  Supposedly this is HiDPI ready, but its rather small on my display...

Something else I want to point out.  It is NI's decision to drop their VST2 version of Kontakt7.  There are very few plugin developers who have made that decision so far.  Steinberg has of course been heavily pushing this, but there was no forced reason for NI to drop the VST2 version of Kontakt7 other then their own decision to do so.  

Additionally, I will just say that its highly probable it would have been much easier for them to continue supporting a VST2 version of K7 in addition to VST3....then it is for all hosts out there to upgrade to VST3 hosting.  The latter is a much much more complicated, difficult and expensive endeavor to do.  Perhaps Steinberg is behind pushing NI to do this, hoping it will force more hosts to get better at hosting VST3 (shrug)...we don't know....just speculation.  But anyway my point is, make sure to let your feelings known to NI also!  They could have just as easily, if not far more easily...released a VST2 version of K7, compared to expecting all hosts out there to drop what they are doing and implement full VST3 hosting...which is usually quite a complicated matter for some of them.  In fact its still not too late for NI to reconsider and release a VST2 version perhaps. It doesn't hurt to ask them too is all I'm saying.

presumably, this is mostly about iLok.  installing it now...

Originally Posted by: Lindurion

So I'd prefer to start using VST3 plugins in VEP as soon as possible, even when that means having to deal with annoyances like choosing keyswitches instead of MIDI CCs for more reliable articulation management because of those VST3 design quirks.

Oh and on this point there is something to point out.  Its good that you are aware of this!  In the case of Kontakt, it doesn't matter if you are VST2 or VST3; as Kontakt itself has some of the same design flaws as VST3 in the midi implementation of its VST2 version also.  In other words, some of the VST3 problems are also present in Kontakt VST2.  Not all..  but some.  So with Kontakt, avoid CC switches period.

I totally hear you.  All I can say is they are working on it and it will come when it comes.  But I suspect we still need to be patient.  The other work-arounds for now are what you can do at this time, or choose as I do to avoid VST3 as much as possible. 

To be honest, I am very much NOT looking forward to the day that I am forced to use VST3 instead of VST2.  In my opinion you will be far better off using VST2 instruments whenever possible...for the forseeable future.  Whenever possible, use VST2.  If you just must use K7...then perhaps you are now forced to use VST3, but there is really no rush to be using the VST3 versions.  They do not represent an improvement over VST2 in most cases, particularly for instruments.  That is a very lengthy discussion as to why.  But you are not missing anything, trust me.  You're better off running the VST2 versions for years into the future from here.  Its not like you will spend time setting up your templates and suddenly have to change them all to the VST3 version later....if you ever had to do that it would be years from now and probably not all your tracks, just a few as needed. 

I would not worry about it.  Use VST2 and love it!  VST2 is truly better!

I'm confident VSL is working on it and at some point they will deliver VST3 hosting

VSL has already stated numerous times on this forum that its on the roadmap, but there is no timeline they can give at this time for when exactly we will see it.  They have already told us a dozen times, they are working on it.

One thing you need to understand is that VST3 is a huge change from VST2 in terms of how its coded in any VST3 hosting app..  Its not a small change.  Its a very very large change, especially for a sophisticated host software such as VePro.  If it were an easy thing to add, I'm sure VSL would have released it already a long time ago.

In the meantime, I suggest you consider using a sub-hosting plugin for K7 as a work around.  DDMF MetaPlugin, DDMF SuperPlugin, Kushview Element, PlogueBidule, perhaps even KompleteKontrol, are all possible plugins which come in VST2 form and can host VST3 plugins inside of themselves..which will essentially allow you to use K7 inside VePro7 right now.

Myself, I am still basically avoiding VST3 plugins.  I'm still using K6 and have no "pressing" need to run out and get K7 any time soon.  The VST3 spec also has some interesting design problems that can sometimes affect midi in problematic ways that does not exist with VST2, so me personally I always choose VST2 whenever possible and I will continue to do that as long as I can until it truly becomes a situation such that for example, there may be some sample library that only works on K7 which is only VST3...  But we're just not there yet, there are really only a few isolated situations where VST3 is a hard requirement.  

Just a suggestion.