08/21/12 NEW Rev 903: Diva 1.1.1, Zebra 2.5.4
-
- KVRist
- 34 posts since 15 Feb, 2009
An advanced formant filter with a>e or e>o and all other possible combinations would make Zebra even more of a beast.
I would love to see this implemented into Zebra 3.
Look out Massive and Sugarbytes Wow!
I would love to see this implemented into Zebra 3.
Look out Massive and Sugarbytes Wow!
-
- u-he
- Topic Starter
- 30180 posts since 8 Aug, 2002 from Berlin
-
- KVRAF
- 1888 posts since 13 Aug, 2011 from Berlin
Please check this out:ddeez wrote:i get a runtime error when i try to install the newest diva on my 64 bit win 7 laptop. any ideas??
http://www.kvraudio.com/forum/viewtopic.php?t=306890
-
- u-he
- Topic Starter
- 30180 posts since 8 Aug, 2002 from Berlin
Hmmm, sounds more like a problem with the installer. IIRC this happens when it tries to create a shortcut to a location that doesn't exist yet. We've fixed this in our latest installers (not yet out...).
I'd suggest to install the data into Vstplugins directory and then move it according to Fritze's link.
I'd suggest to install the data into Vstplugins directory and then move it according to Fritze's link.
-
- KVRian
- 737 posts since 20 Sep, 2006
it wont let me install to any folder though...it either run time errors or it keeps bringing me back to the same install screen after it warns me not to install to the programs folderUrs wrote:Hmmm, sounds more like a problem with the installer. IIRC this happens when it tries to create a shortcut to a location that doesn't exist yet. We've fixed this in our latest installers (not yet out...).
I'd suggest to install the data into Vstplugins directory and then move it according to Fritze's link.
-
Tom Drinkwater Tom Drinkwater https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=283090
- KVRist
- 90 posts since 26 Jun, 2012
I am using Diva 1.1 rev 903 on osx 10.8 with reaper and a novation SL controller
I have the novation sending program change messages, but 9 sessions out of 10 diva is completely uresponsive to them. other plugins respond fine.
sometimes it will start working and then it works fine for a bit until I change something, and then it stops again and nothing i do will make it work again, until something i can't identify changes again and it starts working again.
it always works or doesn't for a period of time consistently, but I can't identify a consistent trigger that makes it start or stop working.
I am only expecting it to work on the patches in the midi folder
it doesn't see to make any difference whether I use the automap wrapped version of diva or not, in both cases it sometimes works but mostly doesn't.
when it is not working, the midi activity light in reaper flashes and midimonitor shows correct incoming program change messages, but the midi activity light in diva does not flash.
diva responds normally to other midi messages, just not program change.
this is kind of a big deal for live performance. any ideas?
I have the novation sending program change messages, but 9 sessions out of 10 diva is completely uresponsive to them. other plugins respond fine.
sometimes it will start working and then it works fine for a bit until I change something, and then it stops again and nothing i do will make it work again, until something i can't identify changes again and it starts working again.
it always works or doesn't for a period of time consistently, but I can't identify a consistent trigger that makes it start or stop working.
I am only expecting it to work on the patches in the midi folder
it doesn't see to make any difference whether I use the automap wrapped version of diva or not, in both cases it sometimes works but mostly doesn't.
when it is not working, the midi activity light in reaper flashes and midimonitor shows correct incoming program change messages, but the midi activity light in diva does not flash.
diva responds normally to other midi messages, just not program change.
this is kind of a big deal for live performance. any ideas?
-
Tom Drinkwater Tom Drinkwater https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=283090
- KVRist
- 90 posts since 26 Jun, 2012
update, I have the same problem with DIVA in cubase too.
-
- u-he
- Topic Starter
- 30180 posts since 8 Aug, 2002 from Berlin
We'll look into it tomorrow... maybe we need to send you the latest beta to see if that fixes it...
-
Tom Drinkwater Tom Drinkwater https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=283090
- KVRist
- 90 posts since 26 Jun, 2012
thanks! did you manage to reproduce it? is the latest beta changing something relevant?Urs wrote:We'll look into it tomorrow... maybe we need to send you the latest beta to see if that fixes it...
incidentally I'm not having the same problem with ACE, which surprises me a little since they are similar in the patch handling system. all other plugins I've tried respond to program change, just not diva. (except when it does)
is anyone else having this problem? I know there were problems in Diva with program change before 1.1, but I can't find any reference to problems like I'm having with the current version.
-
Tom Drinkwater Tom Drinkwater https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=283090
- KVRist
- 90 posts since 26 Jun, 2012
I'm an idiot. Diva works fine responding to program changes - once you work out what it is intended to do.
I won't bother explaining what i was expecting, but here is what it actually does.
* If all your patches are in the top level of the midi folder then program change works as expected. (ie bank defaults to bank 0)
* if you have subfolders then you have to send a MSB bank message (CC0) to select the folder - even if you have only one folder and no patches in the top level.
* the top level of the midi folder is bank 0 - folders start at bank 1 (MSB only)
* Diva does not respond to LSB bank messages
* when you send a bank change message the patch does not change to the same numbered patch in the new bank as you might expect (the patch doesn't change at all) - the bank select message merely prepares diva to select from that bank with subsequent program change messages.
* navigating through patches and folders with the mouse makes no difference to diva's focus over midi. If you want to select a bank/subfolder you have to send a MSB bank message, navigating to that folder with the mouse doesn't work.
maybe the manual could be updated to make this all more explicit.
I won't bother explaining what i was expecting, but here is what it actually does.
* If all your patches are in the top level of the midi folder then program change works as expected. (ie bank defaults to bank 0)
* if you have subfolders then you have to send a MSB bank message (CC0) to select the folder - even if you have only one folder and no patches in the top level.
* the top level of the midi folder is bank 0 - folders start at bank 1 (MSB only)
* Diva does not respond to LSB bank messages
* when you send a bank change message the patch does not change to the same numbered patch in the new bank as you might expect (the patch doesn't change at all) - the bank select message merely prepares diva to select from that bank with subsequent program change messages.
* navigating through patches and folders with the mouse makes no difference to diva's focus over midi. If you want to select a bank/subfolder you have to send a MSB bank message, navigating to that folder with the mouse doesn't work.
maybe the manual could be updated to make this all more explicit.
-
- KVRAF
- 4197 posts since 23 May, 2004 from Bad Vilbel, Germany
DoneTom Drinkwater wrote:maybe the manual could be updated to make this all more explicit.
- in the manual that comes with the next update. Thanks for the tip!