Can you send us a screenshot?phdsg vn chfhn wrote:having gui redraw/alignment issues with bazille.
basically some image elements are misplaced by one or two pixels.
its most noticeble @ 130% size (80% is also pretty messy) when clicking through presets fast.
also the preset-arrows at the top look weird (except in 100%,150%,200%).
host: reaper
screen: 1920x1080 nvidia gtx660
Latest Builds (revision 3819) of nearly every u-he plugin
- u-he
- 30206 posts since 8 Aug, 2002 from Berlin
-
phdsg vn chfhn phdsg vn chfhn https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=308608
- KVRist
- 74 posts since 14 Jul, 2013
sure. here you go. all screenshots done @ 130% gui-size.
these misplaced elements aren't static, meaning they appear in different places when i change presets.
this one is permanent, but the missing line is in different places for other gui-sizes. (except 100,150,200)
these misplaced elements aren't static, meaning they appear in different places when i change presets.
this one is permanent, but the missing line is in different places for other gui-sizes. (except 100,150,200)
You do not have the required permissions to view the files attached to this post.
- u-he
- 30206 posts since 8 Aug, 2002 from Berlin
-
phdsg vn chfhn phdsg vn chfhn https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=308608
- KVRist
- 74 posts since 14 Jul, 2013
ah, ok. no need then for screenshots of hive i guess.
- KVRer
- 28 posts since 18 Oct, 2012 from Finland
When the plugin is updated and I load project that had previous version used those have the setting "Base Latency" as 16 samples and it distorts the sound. I need to set it "off" and back to "16 samples" to get rid of the distortion. Other way is to set it "off" and set FL Studio vst wrapper settings to "use fixed size buffers" and "process maximum size buffers" to get clean sound, this way though my latency compensation is broken. So there is some bug in this version because it thinks that the latency setting is set to "off" though it says that it set to "16 samples"Urs wrote:In the configuration panel (in our plug-ins), is "Base Latency" set to "off"? - This would be the cause of the problem.satak wrote:These versions (vst 2 32bit) (Diva, Presswerk, and maybe Satin) are not working on FL Studio 32bit 12. They distort the sound, something went really wrong. You can sometimes get these versions to work without the distortion voices but still unusable. And I'm not using fixed size buffer. What did you change? Please fix this issue.
Btw. Fl studio manual says:
Use fixed size buffers - FL Studio shares data with plugins using variable sized chunks of data (buffers). Some plugins require fixed sized buffers (which is outside the VST standard but supported in FL Studio for your convenience).
If so, did you set it to that, or did the installer set it to that by itself?
- u-he
- 30206 posts since 8 Aug, 2002 from Berlin
Ok, we're looking into this. There might be a bug, if you have to switch it off and on again.satak wrote:When the plugin is updated and I load project that had previous version used those have the setting "Base Latency" as 16 samples and it distorts the sound. I need to set it "off" and back to "16 samples" to get rid of the distortion. Other way is to set it "off" and set FL Studio vst wrapper settings to "use fixed size buffers" and "process maximum size buffers" to get clean sound, this way though my latency compensation is broken. So there is some bug in this version because it thinks that the latency setting is set to "off" though it says that it set to "16 samples"
We'll also make all explanations a bit more clear, and we'll display a short message if the software glitches because of it. That should help us debug this and also fix the issue for people who accidentally set it to off
-
- Banned
- 3889 posts since 3 Feb, 2010
I can confirm that this happens, aswel this happens with Zebra 2.Urs wrote:Ok, we're looking into this. There might be a bug, if you have to switch it off and on again.satak wrote:When the plugin is updated and I load project that had previous version used those have the setting "Base Latency" as 16 samples and it distorts the sound. I need to set it "off" and back to "16 samples" to get rid of the distortion. Other way is to set it "off" and set FL Studio vst wrapper settings to "use fixed size buffers" and "process maximum size buffers" to get clean sound, this way though my latency compensation is broken. So there is some bug in this version because it thinks that the latency setting is set to "off" though it says that it set to "16 samples"
We'll also make all explanations a bit more clear, and we'll display a short message if the software glitches because of it. That should help us debug this and also fix the issue for people who accidentally set it to off
EDIT: Same with Hive
- KVRAF
- 3303 posts since 27 Mar, 2010 from UK
Question regarding new builds vs older builds.
I have historic projects (doing some house keeping) and noticed older versions the dll's are named ie diva(x64),ace(x64), etc. However older projects they are named diva, ace, etc without the (x64) suffix. It maybe a case I was using the vst3 versions prior to the later builds when the vst3 development was put on hold/shelved.
I haven't tried yet as newer projects have the later suffix names.
Would issues arise if I copied the existing dll's and renamed them as the older named dlls, side by side so new and older projects will load. I know I can change the dlls in the rack (Cubase), but this will lose the patch and settings used in the projects.
Would like to know what the best solution is please?
I have historic projects (doing some house keeping) and noticed older versions the dll's are named ie diva(x64),ace(x64), etc. However older projects they are named diva, ace, etc without the (x64) suffix. It maybe a case I was using the vst3 versions prior to the later builds when the vst3 development was put on hold/shelved.
I haven't tried yet as newer projects have the later suffix names.
Would issues arise if I copied the existing dll's and renamed them as the older named dlls, side by side so new and older projects will load. I know I can change the dlls in the rack (Cubase), but this will lose the patch and settings used in the projects.
Would like to know what the best solution is please?
-
- KVRist
- 107 posts since 8 Jan, 2008
Interesting. I am a Live (9.2) user and I have been using the block latency in default.h2p trick without noticing any major issues. My understanding from something I read on the Ableton forums is that these days the plug-in buffer is always the same as the audio buffer in the Live preferences (it used to be definable separately down to a certain minimum). Is this not the case, or am I confusing separate things? Anyway, since you recommend it I have now re-enabled the fixed buffer.Urs wrote: I'd always recommend to keep a fixed buffer size for our stuff, but it still depends on the host if that fixed buffer size is a multiple of 16. Ableton Live for instance gives us an irregular buffer on a loop end no matter what, thus the option shoudln't be used in Live. It's a pity. Other hosts such as Logic keep going normally on a loop, there's no issue at all.
Incidentally, I don't know if these issues have been reported yet but I've noticed a couple very minor things with the beta builds:
In Diva (have also tested ACE, but not all plugs), the patch information text gets chopped very slightly at the top of the first line. Just noticed the author does, too, at least in the attached example. Tried at different scaling settings.
In ACE when re-opening the plug-in window after it had been closed, some of the cable colors change.
Very minor, I know.
System: Mac OS X 10.10.5, Ableton Live 9.2.2 64-Bit
You do not have the required permissions to view the files attached to this post.
- KVRist
- Topic Starter
- 183 posts since 14 May, 2014 from Berlin | Germany
fixed. thanks!suthnear wrote:ACE: it says sub ocs instead of sub osc
-
- KVRAF
- 3817 posts since 8 Mar, 2006
Diva rev 3819, Win7, 32bit plugin, FL Studio 12
for example, take the Dual osc and adjust osc1 pitch to notice it goes lower than 32" (by one extra octave)
this is valid for osc2 also but it's a bit more strange since the detune knob is involved as it jumps...
if this is too vague, please ask questions to clarify "bug" , sorry if it was mentioned before.
PS I also get those line-glitches but I guess they are only there when using a different size than 100%
for example, take the Dual osc and adjust osc1 pitch to notice it goes lower than 32" (by one extra octave)
this is valid for osc2 also but it's a bit more strange since the detune knob is involved as it jumps...
if this is too vague, please ask questions to clarify "bug" , sorry if it was mentioned before.
PS I also get those line-glitches but I guess they are only there when using a different size than 100%
- KVRAF
- 3303 posts since 27 Mar, 2010 from UK
- KVRer
- 21 posts since 2 Sep, 2015 from worldwide
just bought presswerk. My goodness this compressor is amazing!
