[SOLVED] VEP7 iLOK standalone crashes

[Witold Suryn]

Hi,

The iLOK version of VE Pro 7 standalone (7.1.1329) crashes every time I attempt to load an instance created in VEP 7 server iLOK version. It also happens when I try to load instances created with VEP7 eLicenser version. The only difference is that before the crash VEP runs for a second a helper. Restarting the computer and re-installing the app changed nothing (BTW, at this moment VSL must be flooded with crash reports coming from me as I tried several options, all ended by a crash). Interesting that nothing like that happens when I open any of these instances in VEP7 standalone eLicenser version. So, at its actual state an iLOK standalone is totally useless. All that is on Mac Pro 2020 with Big Sur on board.

Did anyone encounter such a problem? If yes and you know the solution, please, share.

Still on the note of VEP 7 iLOK, this time - server. Despite of the update the unnerving Automation Panel appears every time I load a project. All panels were meticulously closed before saving the project but when I reopened it, bang!!, at least one of them is open. Recently I was building a relatively big template containing 30 instances, all automation panels closed before saving, but this time all of them were activated when the project was opened. I checked some of the instances on VEP standalone eL and none had the panel opened, so VEP7 server has this bug still unattended. This is annoying not only because in some cases the panels mask a part of the mixer, but also because there is no logic in VEP7 behaviour. Sometimes only one panel is activated, sometimes a few and sometimes all. And in any case I don't need them. It would be very helpful if in settings there was an option Activate/Don't Activate Automation Panels.

Dear VSL Developers, You were able to create such a brilliant piece of art like VEP and you cannot correct such a small bug for almost a year? Please, help us, your loyal users... 

Witold

[Paul]

Hi Witold, 

Thanks for reporting!

Regarding the Automation Panel: Please send such a project to support@vsl.co.at, with a reference to this thread, so we can check. This should have been fixed quite a while ago. 

Regarding conversion: Seems like the automatic conversion with the VSL helper does not work on your computer. Not too many people working with the standalone version, we will also check your elicenser project here. 

Thanks for sending it over. 

Best, 
Paul

[Witold Suryn]

Paul,

I am not sure how to send the project. It loads 70GB of samples. I think that switching off all instances should unload samples but keep the project intact. Am I correct? If yes, I will try to send you the project saved with no automation and then the same project opened and saved again with automation that will appear. Would it be correct?

As for standalone I absolutely agree, not a very popular use, but extremely handy when working on expression maps for Dorico. I load and instance, have a full keyboard access, can play sounds, set up mixers, identify all switches and build an expression map. All without a host. Really handy and smart product. Just need it to work.😊

Witold

PS Thanks for reacting during weekend. Very, very appreciated.

[Paul]

Hi Witold, 

You can send the VE Pro Server project file, it doesn't contain any samples. 

Best, 
Paul

[Witold Suryn]

Paul,

You are absolutely right. I forgot that project is just information. So I attach the project that was saved with no automation panel, but when opened has one panel active. Its previous version had 7 of them, but to be sure that I give your untampered data, I closed them all and that is the project I attach. As I said in my previous post, I can't find any logic in this behaviour. Sometimes one, sometimes several, sometimes all, but always something.

16.06.2022

Today this project opened with 16 automation panels. Attached

Witold

projectU0020afterU0020closingU0020allU0020autoU002013.06.2022.vesp64.zip-1696490644860-yxymz.zip 16U0020unwantedU0020activatedU0020automattionU0020panels.vesp64.zip-1696490644860-5mhbo.zip

[DaveDrewry]

Is there an update on when VEP Standalone will work with iLOK?

As others have reported it either crashes uncontrollably immediately on opening older project files if eLicensor is installed or fails with an error message if uninstalled (not practical, as people may need it for other plug-ins).

The server version is fine for some scenarios e.g. Dorico, Cubase but there are others where the standlone approach is required.

It isn't practical to 'just carry on using the eLicensor' since people need the latest iLOK only versions of VEP if for example they're using MIR Pro 3D.

[smesser]

@DaveDrewry said:

Is there an update on when VEP Standalone will work with iLOK?

As others have reported it either crashes uncontrollably immediately on opening older project files if eLicensor is installed or fails with an error message if uninstalled (not practical, as people may need it for other plug-ins).

The server version is fine for some scenarios e.g. Dorico, Cubase but there are others where the standlone approach is required.

It isn't practical to 'just carry on using the eLicensor' since people need the latest iLOK only versions of VEP if for example they're using MIR Pro 3D.

I'm also curious about this, as I've just converted everything to iLOK and can no longer open VEP7 standalone mode (which I use for 99% of things). Has there been an acknowledgement somewhere that this is an established issue which is being corrected? I notice that some threads about the issue are not being replied to.

[Paul]

Hi, 

Just fixed with the current update 7.1.1390, in your Vienna Assistant!

Thanks for your patience!

Best, 
Paul

[DaveDrewry]

Yes, just tried V7.1.1390 and the standalone immediate crash issue is fixed - opened and saved successfully.

[Paul]

Great!

Thanks for the feedback!

Paul

[smesser]

@Paul said:

Hi, 

Just fixed with the current update 7.1.1390, in your Vienna Assistant!

Thanks for your patience!

Best, 
Paul

Hi Paul,

Seems to be fixed here too. Thanks to you & the team for all your efforts!

[Witold Suryn]

Paul,

The problem with automation panel being active despite of closing them all on exit is still there and definitely is NOT solved. To give more pertinent information I did a series of experiments and the findings are below.

1. For my experiments I used my existing project with 8 Synchron instances, 11 Opus/Play instances, 7 Spitfire Audio (BBC Orchestra), 1 SINE (Orchestral tools) and 2 Kontakts.

2. VEP with all automation panels closed on exit, on loading opens the panel for the instance being displayed during saving process. So, if I displayed first instance of synchron on saving, this instance will have automation panel open on loading.

3. I repeated this with first 2 synchrons without closing previous panels and then added the third and saved. What I got on loading was a disaster: all synchrons, all Opus/Play, Sine, both Kontakts and 4 out of 7 Spitfires had automation panels activated

4. Next I deactivated all automation panels, again displayed first synchron instance and saved the project. Then loaded the project, displayed Kontakt and saved. What I got after loading the project was ALL except one synchron instance having automation panel active.

5. In search for a "survival workaround" I once again closed all automation panels, displayed the first synchron and saved the project. Loaded, displayed all instances one-by-one, BUT before saving the project I displayed only first synchron and saved the project. When loaded the project had 22 out of 29 instances with active automation panels.

6. Next, again, I closed all automation panels, displayed the first synchron and then just saved and loaded the project 5 times without touching anything, just open and save. The 5th time ALL automation panels were active.

7. Finally, again, I closed all automation panels, displayed the first synchron, saved project and loaded it 5 times WITHOUT saving (just closing). This is the only situation when only one panel was active.

In conclusion I think that this bug is a non-trivial one, rooted probably not only in the process of active manipulations of/in instances (cases 3, 4 and 5) but also in saving process itself (case 6).

The project used in these experiments can be made available for your developers.

Witold

[Paul]

Hi Witold, 

Thanks for your input!

Please send those projects to us: support@vsl.co.at, so we can check it on our systems. 

Thanks, 
Paul

[Witold Suryn]

@Paul said:

Hi Witold, 

Thanks for your input!

Please send those projects to us: support@vsl.co.at, so we can check it on our systems. 

Thanks, 
Paul

Paul,

I sent you the project, but the file is 30MB, so may not have reached you. So I also attach it to this post.

Witold

MAXU0020FULLU0020STARTU0020(iLOK)U0020ONU0020CHANNELSU002013.07.2022.vesp64.zip-1696490646025-la1vm.zip

[Witold Suryn]

Hi Paul,

Is there any news about solving the issue of automation panels in VEP7? With every update I search for information about being able to deactivate the panels so they would not reappear until explicitly activated, but even the latest update still suffers the same problem. I imagine that this issue may be very low on development team's importance list, but on my list it is rather high, because it forces me to waste time for endlessly switching them off. 

The answer to the question why they have to be deactivated relates to the number of instruments in a given instance and the surface of a UI of an instrument. I sometimes have 16 or more instruments in one instance and some of them get masked by automation panel when opened as Mixer channels, so I need the panel closed. Some instruments, like OPUS ones, happen to have large UIs that again get partially masked by an automation panel.

I also tried the function of saving the window setup as default, but it seems to work for a single instance only.

I remember I sent you several projects as illustrations to this problem. Were they helpful? Can I expect aby news in the subject?

Witold