I don't know if this is actually a bug, but when double clicking on the octave knobs, if there is a detune applied, it resets both the octave and the detune knobs. Would it be nicer if the detune reset wasn't slaved to the octave?
also getting stuck notes when playing and changing voice mode (poly, mono, legato), and sometimes while tweaking FM. This doesn't happen while simply holding notes and changing, but rather, when playing a line while changing.
DIVA known issues
-
- KVRer
- 24 posts since 2 Jul, 2011
Last edited by mharnishfeger on Sun Nov 13, 2011 10:02 pm, edited 2 times in total.
edit: I got it to work... i just restarted my project 
-
Funkybot's Evil Twin Funkybot's Evil Twin https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=116627
- KVRAF
- 12454 posts since 16 Aug, 2006
1. GUI opens with the wrong size in Reaper (cuts of the black bar at the bottom to select which page you want to see and a few pixels from the far right).
2. This may be related to the multi-core functionality not being fully up and running but the CPU doesn't appear to be getting reported correctly in either Sonar or Reaper. For instance, at high res (especially with Sallen-Key filter rev. 2) my computer (i7) will choke up while playing polyphonic chords while in "great" quality, however the CPU meter has never shown more than 12.5%.
2. This may be related to the multi-core functionality not being fully up and running but the CPU doesn't appear to be getting reported correctly in either Sonar or Reaper. For instance, at high res (especially with Sallen-Key filter rev. 2) my computer (i7) will choke up while playing polyphonic chords while in "great" quality, however the CPU meter has never shown more than 12.5%.
-
- KVRAF
- 24414 posts since 7 Jan, 2009 from Croatia
Regarding 2, I believe that's because Reaper shows the CPU usage as the sum of the usage of all cores you have (so if you have 4 cores, maxing out one core would be at 25%, if you have 8 cores, then maxing out one core is at 12.5%, which is true for what you say). Since Diva uses only one core so far, that's consistent with the expectations... I think. Urs, please correct me if I'm wrong.
-
- KVRian
- 1112 posts since 26 Jun, 2008 from Czech Republic
i5, 4GB, Win, Live
Choosing Env1 modulation for OSC's always select one above on the first try. On second it's ok.
Choosing Env1 modulation for OSC's always select one above on the first try. On second it's ok.
-
- u-he
- Topic Starter
- 30194 posts since 8 Aug, 2002 from Berlin
My brain is fried for today... I can't even think about doing the mathsEvilDragon wrote:Urs, please correct me if I'm wrong.
-
- u-he
- Topic Starter
- 30194 posts since 8 Aug, 2002 from Berlin
Interesting... will check it out (and everything else of course)FarleyCZ wrote:i5, 4GB, Win, Live
Choosing Env1 modulation for OSC's always select one above on the first try. On second it's ok.
-
- KVRAF
- 2707 posts since 23 Mar, 2005 from Detroit
2 narrow white vertical lines show up sometimes when changing effect types in that effect box area
-
- u-he
- Topic Starter
- 30194 posts since 8 Aug, 2002 from Berlin
Eeeek. Win or Mac? Did you change the guy size? Do you have a screenshot?metalifuxx wrote:2 narrow white vertical lines show up sometimes when changing effect types in that effect box area
-
Funkybot's Evil Twin Funkybot's Evil Twin https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=116627
- KVRAF
- 12454 posts since 16 Aug, 2006
I thought of that, but in Sonar the CPU usage stays between 1-3% even as the audio stutters due to the CPU usage, which is clearly not accurate. My guess is that there's just something in DIVA that's not reporting CPU correctly to the host.EvilDragon wrote:Regarding 2, I believe that's because Reaper shows the CPU usage as the sum of the usage of all cores you have (so if you have 4 cores, maxing out one core would be at 25%, if you have 8 cores, then maxing out one core is at 12.5%, which is true for what you say). Since Diva uses only one core so far, that's consistent with the expectations... I think. Urs, please correct me if I'm wrong.
-
- u-he
- Topic Starter
- 30194 posts since 8 Aug, 2002 from Berlin
hahaha, I guess we rather have the host stunnedFunkybot's Evil Twin wrote:I thought of that, but in Sonar the CPU usage stays between 1-3% even as the audio stutters due to the CPU usage, which is clearly not accurate. My guess is that there's just something in DIVA that's not reporting CPU correctly to the host.EvilDragon wrote:Regarding 2, I believe that's because Reaper shows the CPU usage as the sum of the usage of all cores you have (so if you have 4 cores, maxing out one core would be at 25%, if you have 8 cores, then maxing out one core is at 12.5%, which is true for what you say). Since Diva uses only one core so far, that's consistent with the expectations... I think. Urs, please correct me if I'm wrong.
Plugins don't report cpu usage - it's up to the host to measure the time that a plugin needs to render a buffer...
-
- KVRAF
- 5948 posts since 19 Jun, 2008 from Melbourne, Australia
DIVA is sound great, Urs! And thanks for the intro offer 
1. Set GUI size to "Large"
2. Close GUI
3. Re-open GUI
The GUI is displayed using the default frame size, but the actual GUI images are "Large".
Peace,
Andy.
Similar GUI size problem in Live 8 / Mac / 10.6.8 / VST version:Funkybot's Evil Twin wrote:1. GUI opens with the wrong size in Reaper (cuts of the black bar at the bottom to select which page you want to see and a few pixels from the far right)..
1. Set GUI size to "Large"
2. Close GUI
3. Re-open GUI
The GUI is displayed using the default frame size, but the actual GUI images are "Large".
Peace,
Andy.
... space is the place ...
