The no sound thing is outputs quit, or don't even start, but an output channel can be fine one moment and gone the next. I spent all day and a save I made towards the end ot the day, the server project opened with the EQs and other plugins I had reworked in instance 3 x-d out again. But fortunately the instance saved correctly. But this instance finally wouldn't sound at all. I'm enabling 4 stereo outs, 0 giving me sound (it's all receiving MIDI and showing signal) and I simply gave up today. This instance would alternate with another group feeding the output working while drums don't. Rarely would both sound. The other instances have similar problems except its EQs and such loaded normally every time.
-
I can open my pre-ilok-projects with 1263, but except for straight-forward OUT1/2-Busses with no processing I don't get any sound into my DAW! OUT3/4 etc. DO NOT WORK
can't count on 1-2 working here. I'm beginning to think any processing effect stops the sound of the channel dead. I tend to have a MIRacle instance in the master bus.
-
it is completely useless as is.
Another thing which is just stupid is getting rid of any possibility to empty an automation slot.
EDIT again: today I have managed to hear all channels in the (3-instance) project. For this, one of my st. outputs works, not more than one, in an instance. In two of them it happens to be 7-8, the other 1-2. The Equalizer Pro in the integrated plugin blocks audio, in some cases (in one of them it absolutely does); this is definite. In some cases MIR instantiated on a ch. blocks audio, then it doesn't; this too is definite. The whys and wherefores of these, who knows.What does "Disable MIR AU Plugins mean" or supposed to DO? Why would disabled plugins be a default? I'm on a Mac, as far as I know the MIR is AU, what isn't AU about anything unless I have specified VST. So my obvious assumption is hell NO.
If I have to un/reinstall VEP, which is all the time now, I wind up having to scan plugins which I don't need to do otherwise at all, in any way whatsoever. A GIANT TIME SUCK.
-
This is a new one. BFD3 in VE Pro (yes it's a big instantiation of) made the project completely unable to perform.
I was waiting 7, 8 secs for playback to recover, hangs, can't view VE Pro for long periods...I finally went to using it in Nuendo and it performs very well, and the VE Pro project is performing, not well but I can stand it, without it. The opposite of my expectation. But I think this system runs very, very well, just this iLok (I think the layer of translation needing a Vienna Helper is the culprit) is ruinous.
-
I just installed 1298 and I am having the same problem. All my old projects come up as invalid. This is on Monterey,
I have a side PC running VEP 7.0.x, that one can read all the files still.
I will try rolling back for now. If any more info can help you guys fix it, please each out!
-
I have just read through this entire thread hoping to see how this problem has been solved (as it says in the header to the thread). But, I can’t see a solution.
I’m on a MacBook Pro running Big Sur after having had to downgrade from Monterey 12.3 with Apple’s help. Why? don’t get me started. But Big Sur is stable and working for me at the present time.
Now, having used Vienna Assistant to transition to iLok, (many more hours to go) my Vienna Ensemble Pro 7 software crashes as soon as I run a project in Digital Performer 11. The crash report is 151 pages of impenetrable code. The project uses 4 instances within VEP7. I’m wondering if the problem might be new locations for some of the libraries used. I had to be creative to free up enough space for the réinstallation of the now iLok encrypted files and some libraries are in new locations. I thought that was taken care of by Vienna Assistant after I changed the location before installing, but maybe I’m wrong.
Any ideas would be welcome.
Sigh…
-
The [SOLVED] heading was applied in early April when Paul was told that the latest version fixed "everything", but it did not, and that version on Macs is working very poorly if it works at all. On Windows I doubt the new version works (none of my projects would load when I used the previous version, and I find no mention of it working for Windows users anywhere in the forum still).
The long and the short of it is you will have to revert to the eLicenser versions of your libraries, Synchron Player and VEP plugins.
I will not trust any new versions for at least a year at this point. I have lost nearly a thousand dollars in billable hours in time wasted trying to get this to work. The eLicenser versions work just fine.
Do NOT try to install the Futanaro Flute freebie, as it only installs via the Vienna Assistant that that installation will break your Synchron Player if still using the eLicenser versions.
Terry
-
The projects invalid was fixed at that time, and very quickly. It's unfortunate that SOLVED in the title, as many problems appeared since.
I "lost" my dongle, and I didn't see it as too viable to buy Vienna Protection beforehand for such a short time so I was forced to go iLok. If I had jobs during this I would absolutely stick with what works. 1120 on the elicenser. Right now it's all functional, except that one of two instances in a Server Project load in the default window rather than remember both, for some reason. VSL advises the two can't be mixed.
-
-
the free flute has to be activated to disk, actually, so does the BBO free
Yes, that is what I did, but it installed the iLok version of Synchrony Player, so it could no longer see my eLicenser licensed Big Bang or introductory Synchrony libraries.
I will give the iLok installations a try one more time on a safe machine!
[EDIT: I have installed the LATEST versions using Vienna Assistant onto my Windows 10 machine and the MAS plugins are installed and are working.]
Terry
-
I am back up and running after downloading a pre-iLok VEP7. Incidentally the “rollback” option in Vienna Assistant didn’t work from me, but a manual uninstall followed by an install using the link below worked. (This is from an email I received from VSL support and it solved my problem.)
Please manually(!) uninstall VE Pro with the provided Uninstaller from your VE Pro application folder, then manually(!) re-install VE Pro 7.1.1263 from the direct link below. And of course please make sure that MAS is checked in the Installer:
https://beta.vsl.co.at/user/ViennaEnsemblePro-macOS-7.1.1263-iLok.zip
-
Hope this helps somebody:
After transitioning to iLok and updating VE Pro from 7.0.1120 to 7.1.1298, I was unable to open any of my VESP64 projects, and unable to import a single instance from any of those project to a new project. Tried everything suggested on various posts uninstalled/reinstalled around a dozen combinations of old/new versions of VE Pro 7, manually and via Vienna Assistant. None of it worked, just kept getting the dreaded "instance invalid" messages. For no logical reason whatsoever I decided to open the eLicenser Control Center (which should be redundant after having migrated to iLok, right?) on my server computer and check for updates. As soon as I updated eLicenser Control Center from v 6.11 to v6.12.8.3308, I was able to open every single project/instance!
So if anyone is having issues with invalid VE Pro 7 projects/instances after migrating to iLok, try updating eLicenser Control Center to the latest version (currently v6.12.8.3308) and see if it works for you too. Make sure you have the eLicenser dongle connected to your server computer when you try to open the FIRST project created in VE Pro 7.0.1120. I removed the dongle once I was able to open the first project, and was able to open all my other projects (each around 15-20 instances, with each instance having 10-16 instruments, i.e. not exactly small projects) without the dongle connected.