When loading uviworkstation-x64-3.0.18 Vienna Ensemble Pro7 crashes under Windows 7 x64!
(Everything is OK under Windows 10; different machine)
With uviworkstation-x64-3.0.17 everything was OK (I had to change back to this version).
What changed in the update from Version ...17 to ...18?
Vienna Ensemble Pro7 crashes when loading uviworkstation-x64-3.0.18
-
- KVRAF
- 2393 posts since 28 Mar, 2005
-
- KVRer
- Topic Starter
- 15 posts since 23 Apr, 2021
With the downloaded UVI-Version ...19 now the crashes of Vienna Ensemble Pro 7 (latest version 7.0.10.56) have disappeared under Win7x64 (not tested on Win10 until now).
HOWEVER:
When I try to elicit a vibrato with the Modwheel (cc1) I can SEE the modwheel react properly to the cc-value I have sent, BUT I DO NOT HEAR the vibrato!
With UVI-Version ...17 I can hear the vibrato!
P.S.: I use the UVI/GD-6 Guitar inside the Vienna Ensemble Pro 7 (x64) Server because my score program (Capella-8) is still 32-bit and thus cannot load 64-bit plugins directly. Capelly can load the VEPro7 32-bit .dll, which obviously sends everything neatly to the VEPro7 64-bit plugin!
I currently try to build an easily usable configuration for the use of your GD-6 Guitar with Capella.
HOWEVER:
When I try to elicit a vibrato with the Modwheel (cc1) I can SEE the modwheel react properly to the cc-value I have sent, BUT I DO NOT HEAR the vibrato!
With UVI-Version ...17 I can hear the vibrato!
P.S.: I use the UVI/GD-6 Guitar inside the Vienna Ensemble Pro 7 (x64) Server because my score program (Capella-8) is still 32-bit and thus cannot load 64-bit plugins directly. Capelly can load the VEPro7 32-bit .dll, which obviously sends everything neatly to the VEPro7 64-bit plugin!
I currently try to build an easily usable configuration for the use of your GD-6 Guitar with Capella.
-
- KVRAF
- 2393 posts since 28 Mar, 2005
Humm...strange.
Do this happen in Standalone too ?
Do this happen in Standalone too ?
-
- KVRer
- Topic Starter
- 15 posts since 23 Apr, 2021
Now I got a step further:
In "Show/Hide Transport bar" the "SyncToHost" button was ON --> NO vibrato heard.
With "SyncToHost" button set to OFF --> I hear the vibrato.
In "Show/Hide Transport bar" the "SyncToHost" button was ON --> NO vibrato heard.
With "SyncToHost" button set to OFF --> I hear the vibrato.
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- 2393 posts since 28 Mar, 2005
The difference with 3.0.17 is if the tempo was not available in the host(VEP Pro here), it was default 120, now it's 0.
Does VEPro reports correctly tempo ?
Looks like there was an issue in some version
https://www.vsl.co.at/community/posts/t ... post284512
Does VEPro reports correctly tempo ?
Looks like there was an issue in some version
https://www.vsl.co.at/community/posts/t ... post284512
-
- KVRAF
- 2393 posts since 28 Mar, 2005
Yep from what I read it was a bug in some VEPro version. Are you up to date ?
-
- KVRer
- Topic Starter
- 15 posts since 23 Apr, 2021
VEPro7 (x64) is the latest version (7.0.1076)!
I suggest that tempo is not sent by my score program, probably it regulates tempo internally (tempo changes work well).
(I am currently also in contact with the Capella programmers to get cancelled their still rather close restrictions of numbers of CCs sendable to plugins. I will have to wait with full use of your GD-6 until they solve these restrictions.) :=(
I suggest that tempo is not sent by my score program, probably it regulates tempo internally (tempo changes work well).
(I am currently also in contact with the Capella programmers to get cancelled their still rather close restrictions of numbers of CCs sendable to plugins. I will have to wait with full use of your GD-6 until they solve these restrictions.) :=(
-
- KVRAF
- 2393 posts since 28 Mar, 2005
-
- KVRer
- Topic Starter
- 15 posts since 23 Apr, 2021
The responsible Capella-developer has extended the VST-interface to send more CCs !
So it begins to work now as it should.
I am on 'heavy testing' now. Handling of the configuration has to be easy.
Maybe I can publish it on the CapellaWiki some time (where several of my VSL configurations are available).
So it begins to work now as it should.
I am on 'heavy testing' now. Handling of the configuration has to be easy.
Maybe I can publish it on the CapellaWiki some time (where several of my VSL configurations are available).
-
- KVRer
- Topic Starter
- 15 posts since 23 Apr, 2021
Concerning the VEPro7-crashes when loading Server projects/Instances with UVIWorkstation as Plugin:
I have pushed this project over to the Vienna Smyphonic Library programmers:
SUGGESTION:
If VEPro7 cannot find the Plugin(UVI)-DLL (because the path location changed after an update or a reinstallation) VEPro7x64 crashes when loading VEPro7-projects/Instances.
(After specifying the correct path in the VEPro7-plugin-settings on my Dell XPS15 Win 10 notebook the crashes disappeared and everything works fine (also on my older Win7x64 computer). The crashes had appeared there after updating to UVI v3.0.20 x64.)
I have pushed this project over to the Vienna Smyphonic Library programmers:
SUGGESTION:
If VEPro7 cannot find the Plugin(UVI)-DLL (because the path location changed after an update or a reinstallation) VEPro7x64 crashes when loading VEPro7-projects/Instances.
(After specifying the correct path in the VEPro7-plugin-settings on my Dell XPS15 Win 10 notebook the crashes disappeared and everything works fine (also on my older Win7x64 computer). The crashes had appeared there after updating to UVI v3.0.20 x64.)
-
- KVRer
- Topic Starter
- 15 posts since 23 Apr, 2021
QUESTION: Might it be that your (phantastic!) strumming engine needs some time to process all incoming VST information?
It seems that the engine starts processing/analyzing a chord before it has received and switched all incoming CC-values (???).
Is there a possibility to make it wait (introduce a delay) until it has received all incoming information/CCs sent with a note or chord before it starts playing?
I get a garbled FIRST chord after switching from the solo to the chord mode, or when trying to switch a capo with a CC.
This disappears if I send the CC-information before the chord where the switch is intended:
at tempo 120/min I need a 1/32 pause (where CCs are sent) in advance of the chord to get the correct switch (which would mean at least about 62 ms to have all information processed before correct playing starts).
{this does of course not look nice in a score!}
My computer: Dell XPS15 with current Win10 (should be fast enough).
It seems that the engine starts processing/analyzing a chord before it has received and switched all incoming CC-values (???).
Is there a possibility to make it wait (introduce a delay) until it has received all incoming information/CCs sent with a note or chord before it starts playing?
I get a garbled FIRST chord after switching from the solo to the chord mode, or when trying to switch a capo with a CC.
This disappears if I send the CC-information before the chord where the switch is intended:
at tempo 120/min I need a 1/32 pause (where CCs are sent) in advance of the chord to get the correct switch (which would mean at least about 62 ms to have all information processed before correct playing starts).
{this does of course not look nice in a score!}
My computer: Dell XPS15 with current Win10 (should be fast enough).
