Menu
What's new
By:
Filters

VE Pro 6 automatic startup (with .vesp64 file) - SOLVED!

Skyroads said:
This is what I tried several times. Blank Projects, just some instruments or my full template won't open. Always the same error message. It's a bit frustrating but I really don't know what I do wrong. Could it be because of Win 7?
Click to expand...
It could be because of Windows 7 (I'm on Win 10), but I doubt it. Maybe someone else with Windows 7 can give it a try?
 
Skyroads said:
Thanks for that guide and it works too. Unfortunately it opens again the standalone version of VE Pro and not the server version.

In the meanwhile I even installed VE Pro 6 new to check if there is something wrong with the software itself. I still have this problem.
Click to expand...

I have been reading this thread as it has been developing with great interest. Sure sounds like something simple. At the very least it sounds like standalone is taking precedence over the server version which leads me to believe the issue should be simple to solve. However, this whole thread begs the question, have you taken this issue to the VSL forum for input?
 
Since I still haven't received a reply from VSL, I need to ask you again for some further help. It's really frustrating opening the template manually.:shocked:
 
Skyroads said:
Since I still haven't received a reply from VSL, I need to ask you again for some further help. It's really frustrating opening the template manually.:shocked:
Click to expand...

Sorry to hear about this. I still use VEP5.

However one work around that springs to mind would simply be to use something like autohotkey to make a macro of the steps you usually take to launch your template and then simply autostart that autohotkey routine upon boot. It should solve the issue you're having pretty easily.

Autohotkey itself is pretty straightforward (with a little bit of reading up).

best,
Chris
 
... and here's a link forum topic that will point you in the right sort of direction to program a routine to do what you want.

https://autohotkey.com/boards/viewtopic.php?f=5&t=43765&p=198515&hilit=launch+.exe#p198515

In your case, launch the VEP server app as you are currently, but also launch a hotkey script that waits until vep is active (as with linked forum topic) and then executes the commands you usually apply to open your template, for example in my case this would simply be to send "alt F", "down arrow", "down arrow", "right arrow", "enter", to load the most recently used metaframe.

Clunky but works.

Chris
 
Gosh I love this is sort of thing!! ;)

Sorry but as someone who works in IT, I LOVE problem solving

I will try this out in a windows 7 virtual machine when I get home and see what i can come up with

I will also test it on my Windows 10 slave and even perhaps on a Windows 8.1 VM
Really would like to find a resolution for this and I am sure there must be one. Windows is extremely tweak-able and I bet Powershell would have some answers if nothing else works

Will let you know some results soon :)
 
The "Vienna Ensemble PRO – User Manual" (v3.1), page 44 says:

Startup / Log-in Items
On Windows, you can place your favorite default Vienna Ensemble Server Project in your startup folder.
On OS X, it’s the Login Items defined in your “Accounts”, so that all samples and settings will be loaded up when
you come back from your morning coffee!​

Have you tried to simply copy your server project files (*.vesp32/64) in your startup folder?

The *.vep32/64 files are indeed single instances project files, so you don't want those in your startup directory.
 
Okay I've tried all your super inputs. Unfortunately none of them works.

I have to say: they actually do work but in the end it appears the same error message.

The server version of VePro 6 starts but is not able to load the .vesp64 project file. (all 64bit) I even tried another project to check if something is wrong with that file.

Autostart or autohotkey work fine but as I mentioned, the error occurs while VePro tries to open the project file. I really don't know whats wrong.. the file opens fine manually and even if loaded works perfectly on my main pc where my DAW is installed. Just the startup won't succeed.
 
Doing it via autohotkey is really the same as doing it manually, so i don't understand? Are you saying that the hotkey script you've written gets as far as prompting vep to load the metaframe, but then the load itself just fails?
 
Now this teases my curiosity. Being a software guy, investigating issues is what i do for a living :)

Would you have access to the VEP logs and see if there is anything reported there?
In windows they seem to be there
WIN: C:\Users\USERNAME\AppData\Roaming\VSL\Vienna Ensemble Pro\logs

Obviously, this is for VSL Support to take care of but if you are stuck, let's see if we can help.
 
chrisr said:
Doing it via autohotkey is really the same as doing it manually, so i don't understand?
Click to expand...
By manually I mean to open Ve Pro Server and than load the project file "File" -> "Open Server Project..."

That step will not work whether with autohotkey, an automatic generated batch file nor over the autostart placement.

antonyb said:
In windows they seem to be there
WIN: C:\Users\USERNAME\AppData\Roaming\VSL\Vienna Ensemble Pro\logs
Click to expand...
There is no log file listed but what I can show is the configuration file if that helps.

Edit: This autohotkey opens the right server version of VePro6.
#IfWinExist ahk_exe C:\Program Files\Vienna Ensemble Pro\Vienna Ensemble Pro.exe
Run, C:\Program Files\Vienna Ensemble Pro\Vienna Ensemble Pro.exe -server

My project file is located here: C:\Users\Andreas Trösch\Documents\Template_Slave.vesp64

If I try to link that path to the autohotkey it opens VePro Server but not the file.
 
Last edited:
Skyroads said:
By manually I mean to open Ve Pro Server and than load the project file "File" -> "Open Server Project..."

That step will not work whether with autohotkey
Click to expand...

Yes it will. That's exactly how autohotkey works. To the computer, it is just as if you have sat down at the machine and waited until you see the application open, then you moved your mouse over to the window and clicked on it to make it the active window, then you selected "File" etc etc... It doesn't do anything more than that, which is the beauty of the approach. It's mostly just sending the same instructions that you'd otherwise be sending with your mouse and keyboard - and the computer doesn't know or care if you're actually using your mouse and keyboard, or a script is pretending to be your mouse and keyboard.

If I may be so bold, if you'd care to post here the autohotkey script you made I may be able to help?
 
Thank you Chris!

You can find the script in my post before. As I said the script is working but it doesn't matter what I try next. It just doesn't open the project file. It's like VePro gets the command but can't read the file.
 
Skyroads said:
Edit: This autohotkey will open the right server version of VePro6.
#IfWinExist ahk_exe C:\Program Files\Vienna Ensemble Pro\Vienna Ensemble Pro.exe
Run, C:\Program Files\Vienna Ensemble Pro\Vienna Ensemble Pro.exe -server
.
Click to expand...


Thanks for posting that - helps me understand what's going on.

To me that code looks like it does nothing - it says something like: If VEP is open, open VEP. (I'm not even sure it says that!!)

(I'm guessing VEP is open (or in the process of starting up) already, if it's in your autostart...?)

So, I think you just want to do something similar to what's posted towards the end of that thread, saying : Open VEP, and wait until it's open (this example copied from above linked thread regarding cubase)
"Winwait, ahk_exe Vienna Ensemble Pro.exe -server ; Wait for VEP"

then something like:

winactivate Vienna Ensemble Pro - to make VEP the active window for keyboard input (you may have to query what the actual window is called - I'm note sure the macro will like all these spaces in the file/window names??)

then a simple series of keyboard instructions (with time for the vep software to respond) to mimic whatever you might type at the keyboard to load your template in VEP - probably something simple like...

send !f
sleep 50
send {down}
sleep 50
send {down}
sleep 50
send {right}
sleep 50
send {enter}
sleep 50

ExitApp

All those sends are doing is literally opening the "file" menu in VEP (alt F) and then hitting the down key / right key to browse to the recently opened projects and then moving across and selecting the first one.

As I say it's a very crude solution - just a bit of software pretending to be you sat at your keyboard ... but it will definitely work - which allow you to simply switch on the PC and then come back some minutes later and find your template automatically loaded.

It will be as if you had sat at the computer and carried out the key-presses yourself.

best,
Chris
 
Last edited:
Hey Chris

It's coming closer to an end:grin:

Here the new script:
Run, C:\Program Files\Vienna Ensemble Pro\Vienna Ensemble Pro.exe -server
Sleep, 7000
Send !f
sleep 50
send, {down}
sleep 50
send, {right}
sleep 50
send, {enter}
ExitApp

That way it works perfectly! There is only one thing left... when I start the PC (the autohotkey file is in the autostart folder) it only opens VEPro Server without the key commands or better said without the project.:shocked:

Do I need to add something to the script?
 
Hmm...

For some reason the key commands are not getting to VEP. Could be one of the following...

1) Is VEP also in the start folder? - if so remove it, and allow the .ahk script to start the vep server.

2) try a much longer sleep for the 1st sleep in case the machine as busy trying to do loads of other things at startup - if you make it veeerrry long that will give you some sort of answer at least.

3) also make sure that the VEP window is active - see below...

to find out the name of the vep window (usually just whatever is written in the window bar at the top) run the following as a .ahk script, to report the name of the active window:
------------------
1::
suspend On

DetectHiddenWindows, on
DetectHiddenText, on
wingetactivetitle vepwindowname
msgbox %vepwindowname% selected

suspend
return

------------------

start VEP (new blank instance), then run the .ahk script. when the script is running, and make sure the VEP window is active (click on it with your mouse)... then press the number 1 on your keyboard. this starts the above script and a message box will appear with the "official" window name. Make a note of it - it should be the same as what you see in the window itself but occasionally it's not - Protools I seem to remember liked to give unusual/hidden window names on a PC, which I suspect relates to being cross platform. Quit the hotkey script if it's still running - you'll find it in the hidden icon tray in your task bar.

You can also query a window name with window spy (??) but I just run that script 'cause I'm simple like that.

-------------------

add a winactivate command to your script like this:

Run, C:\Program Files\Vienna Ensemble Pro\Vienna Ensemble Pro.exe -server
Sleep 20000
winactivate Vienna Ensemble Pro Server [0110_C_IM_01] 5.4.14074 (64-bit)
Sleep 100
Send !f
sleep 50
send {down}
sleep 50
send {right}
sleep 50
send {enter}
ExitApp

-------------------

.... but where I've got the name of my v.old VEP5 (with a cue I'm supposed to be writing now!!) - you write whatever the name of your blank instance of VEP6 window is called in that line - it will always be the same for a blank instance.

That should ensure that the keyboard commands are definitely going to the correct application.

NB I changed that first sleep above to 20 seconds(!) which should be waaaay too long - but if you're sat watching, waiting to see if the script works, wait longer than 20 seconds before deciding it's not worked, obvs!


I'm no programmer, as I'm sure is quite apparent to all reading this - but over the years I've been able to cajole AHK into doing all sorts of weird and wonderful automation tricks with PT / Reaper / Vegas / XLS / Word etc etc.. It's archaic but surprisingly effective.

Good luck. I'm in the UK so it's evening but lucky me I'll be working on this cue for a couple more hours yet, so let me know how it goes if you try tonight (unless you're out at the pub yourself)...

Chris
 
Last edited:
... also there will certainly be more elegant ways (than a long sleep) of waiting for the application to load up before sending the key commands - a quick google turned up this :

nb - substitute your VEP window name where I've put "%VEP%"

------------------------------------
; WinWait, WinTitle, WinText, Seconds, ExcludeTitle, ExcludeText

WinWait, %VEP% ; Waits until the specified window exists
IfWinNotActive, %VEP%, ,WinActivate, %VEP%
WinWaitActive, %VEP% ; Waits until the specified window is active

----------------------------------

So your script (now without the long sleep) will read something like:

------------------------------------

Run, C:\Program Files\Vienna Ensemble Pro\Vienna Ensemble Pro.exe -server

; WinWait, WinTitle, WinText, Seconds, ExcludeTitle, ExcludeText

WinWait, %VEP% ; Waits until the specified window exists
IfWinNotActive, %VEP%, ,WinActivate, %VEP%
WinWaitActive, %VEP% ; Waits until the specified window is active


Sleep 100

Send !f

sleep 50

send {down}

sleep 50

send {right}

sleep 50

send {enter}

ExitApp

----------------------------

and if that doesn't work just go with the long sleep...

 
Can I ask which version of VE Pro 5.x, 6.x you are using?

For my testing
As I have my VM ready to test now

Thanks,

Christopher
 
You must log in or register to reply here.
Top Bottom