Possibly. They're supposed to show all non-h2p extensions, but that was a quick shot and maybe h2p is shown as well...zvenx wrote:btw, was seeking if anyone else can confirm that in the latest zebra and zebrahz if in the preset browser the names are shown along with their .h2p extension?
thanks
rsp
Public Beta: Everything u-he
-
- u-he
- Topic Starter
- 30180 posts since 8 Aug, 2002 from Berlin
-
- KVRAF
- 14436 posts since 16 Feb, 2005 from Planet Earth, Somewhere
hi Urs, non h2p stuff even show up in the preset browser?
Didn't know that...
but yes it is is the last build it started happening to me on both mac and pc, vst and vst3
rsp
Didn't know that...
but yes it is is the last build it started happening to me on both mac and pc, vst and vst3
rsp
sound sculptist
-
- Banned
- 85 posts since 2 Jul, 2011
you talking about rev 930 i think it was? even with multicore 1.1 was taking more cpu than needed? how much more are we talking?Urs wrote:The first public beta was slow by accident, revision 1331 is back to the original speed of Diva 1.1. There wasn't any notable speed improvement as far as I knowatraf11 wrote:did "faster diva" just slip by everyone?! is no one experiencing a difference in diva performance?
-
- u-he
- Topic Starter
- 30180 posts since 8 Aug, 2002 from Berlin
Yep, 1316 was the first public beta this month and it was accidentally built using the wrong compiler on Mac. 1336 is the latest revision, using the right compiler.
-
- KVRAF
- 3154 posts since 10 Jan, 2005
I experimented today a denormal problem with Uhbik-A 1.2; installing 1.3 cured completely the problem.
- Mario
- Mario
-
- KVRer
- 5 posts since 21 Jul, 2011
I have the same midi note stuck problem with the Diva beta but i run it in feeltune Rhizome LE.
A specific midi controller is assign to the track and not "all midi input".
I tried to uninstall the beta and reinstall the last official version of Diva and the problem disappear. I think it's a problem from the beta because i never have it before.
I'm on Mac OSX 10.8.2.
A specific midi controller is assign to the track and not "all midi input".
I tried to uninstall the beta and reinstall the last official version of Diva and the problem disappear. I think it's a problem from the beta because i never have it before.
I'm on Mac OSX 10.8.2.
-
- KVRAF
- 2960 posts since 9 Dec, 2011 from falling
I tried changing the midi controller assignment as well, but still experiencing stuck notes. In Cubase I've setup a midi reset key command, so relief is only a key command away.Ifury wrote:I have the same midi note stuck problem with the Diva beta but i run it in feeltune Rhizome LE.
A specific midi controller is assign to the track and not "all midi input".
I tried to uninstall the beta and reinstall the last official version of Diva and the problem disappear. I think it's a problem from the beta because i never have it before.
I'm on Mac OSX 10.8.2.
I also posted this in the Cubase 7 forum but nobody else there seems to be having the issue.
-
- KVRer
- 15 posts since 18 Jun, 2011
Maybe this has been noticed before: In Zebra on a Mac osx 10.75 with Cubase 6 I can't load waveforms to the oscillators anymore. They show up, but are not loaded if I choose them. It works ok in the older version of Zebra.
-
- KVRist
- 172 posts since 20 Aug, 2010
Is that in VST2 or VST3? (If it is in the vst3 version, using vst2 might be a work-around)orebronerd wrote:Maybe this has been noticed before: In Zebra on a Mac osx 10.75 with Cubase 6 I can't load waveforms to the oscillators anymore. They show up, but are not loaded if I choose them. It works ok in the older version of Zebra.
Cheers,
- Clemens
-
- KVRist
- 181 posts since 12 Mar, 2010 from Leeds, UK
Did this get covered? I tried the 1331 version. Multi-Threading is not working, just using a single core all the time. Even on Draft mode it maxes out a core on my i7 Macbook, 10.8.2 + Logic 9. Is fine with the release version.djanthonyw wrote:I experienced a problem with Diva were when I activated multi-threading, it didn't seam to actually be activated because it was using just as much CPU on Logic's CPU meter. Multi-threading seems to work great on my current stable release.
-
- KVRist
- 172 posts since 20 Aug, 2010
Is that by any chance with the DCO as oscillator module?qube123 wrote:Did this get covered? I tried the 1331 version. Multi-Threading is not working, just using a single core all the time. Even on Draft mode it maxes out a core on my i7 Macbook, 10.8.2 + Logic 9. Is fine with the release version.djanthonyw wrote:I experienced a problem with Diva were when I activated multi-threading, it didn't seam to actually be activated because it was using just as much CPU on Logic's CPU meter. Multi-threading seems to work great on my current stable release.
(I just fixed a Bug that resulted in awful performance in that case.)
-
- KVRist
- 181 posts since 12 Mar, 2010 from Leeds, UK
Hi,
yes correct.
Actually, looking at it, with DCO it doesn't do multi-threaded on the release version either, just uses much, much less CPU. I had assumed before that it was multi as it never maxed out the CPU before.
yes correct.
Actually, looking at it, with DCO it doesn't do multi-threaded on the release version either, just uses much, much less CPU. I had assumed before that it was multi as it never maxed out the CPU before.
-
- KVRist
- 172 posts since 20 Aug, 2010
Okay, that is good news, because the cpu problem will be fixed with the next release.qube123 wrote:Hi,
yes correct.
Actually, looking at it, with DCO it doesn't do multi-threaded on the release version either, just uses much, much less CPU. I had assumed before that it was multi as it never maxed out the CPU before.
About the general multi-core problem: The cpu load will only be lower if the sound plays in 'poly' mode and at least two notes are playing. Also, on some hardware multicore doesn't work as well as on others... Could that apply in your case?
Btw: Happy new year to everybody!
Cheers,
- Clemens