CWITEC

lmh · Post by **lmh** » Fri Jul 26, 2019 10:52 pm

Yep, it starts up fine now!

It seems like there is an issue with the VST3i UI on Ableton 10.1 Win10 x64 on my setup.
https://snag.gy/vJrj0m.jpg

The plugin window initializes in a kind of "container" window with a black background at roughly the full size of the screen, inside of which the TX panel resides. Resizing the window results in the artifacts shown in the screenshot. Furthermore, mouse clicks do not register at the correct location (i.e., I could click a button 500 pixels away from it).

My screen resolution is 3840x2160, upscaled by Win10's display settings to 200%, so it looks like 1080p.

No problems with Reaper of course, where TX16Wx belongs ...

Thanks for the fix; I love this plugin.

elcallio · Post by **elcallio** » Sat Jul 27, 2019 5:19 pm

So it seems that Ableton 10, despite being application-wide HDPI aware, still assumes plugins are not, and run the plugins windows in low DPI. This confuses TX, which foolishly assumes that app DPI == window DPI.
Positive aspect is that it is a kick in the behind to finally support per-thread/windows/monitor DPI in TX. I'll have a build up soon.

What has me puzzled is more how/if Ableton intend to handle HDPI aware plugins. VST3 has some support for the host to communicate this, but they apparently did not implement this part of the standard.

elcallio · Post by **elcallio** » Sat Jul 27, 2019 6:54 pm

I've updated the beta builds (3.100.5321.1164). TX16Wx now supports per-monitor and per-thread HDPI awareness.
For Ableton 10 it means it will detect that the plugin thread is run in low-dpi mode, and thus the plugin will render in lowdpi (i.e. scaled) even on HDPI systems. So size and mouse etc works, but it looks not as nice. Complain to ableton to make them support HDPI plugins.

lmh · Post by **lmh** » Sun Jul 28, 2019 12:09 am

Hmm! So now, on 3.100.5321.1164, I have a similar sort of issue (huge initial "frame" window, TX UI stuck in lower-left) with the on macOS 10.14.4 and either Reaper 5.981 (VST3) or Ableton 10.1 (VST2 or VST3). At the moment, only the VST2 with Reaper is usable on macOS. Haven't tested AU.

I also experienced a crash on this version with the VST2 and Reaper 5.981 and macOS, when trying to use a factory sample from Madrona Labs's Kaivo synth.

Edit - removed irrelevant/misleading details, see below.

elcallio · Post by **elcallio** » Sun Jul 28, 2019 12:32 am

Can you send the sample?

lmh · Post by **lmh** » Sun Jul 28, 2019 1:28 am

enjoy: cats.wav

I think this might be caused by using more than two channels. Kaivo uses multichannel .wav files to blend between sample layers.

elcallio · Post by **elcallio** » Sun Jul 28, 2019 1:49 am

OSX dpi issue should be fixed now. I will look at the wave tomorrow.

elcallio · Post by **elcallio** » Sun Jul 28, 2019 8:35 am

Hm, I cannot provoke any errors with that particular sample (verified four-channel). It playes and displayes as expected for me (only first two stereo channels, but).

lmh · Post by **lmh** » Sun Jul 28, 2019 11:13 am

Whoops, I accidentally edited out the crucial step: it crashes when I click the "boost sample volume" button in the wave editor - on macOS or Windows.

elcallio · Post by **elcallio** » Sun Jul 28, 2019 7:28 pm

New build is up. This fixes the aforementioned editing of more-than-stereo-wavs, improves sf2/sfz import some more, and fixes occasional crashes in preview mode.

elcallio · Post by **elcallio** » Thu Aug 01, 2019 12:41 pm

New build up again. Numerous fixes for small regressions in the new code. Also improved import some more, as well as changed filter frequency modulation to use cents in stead of Hz as unit. The latter makes much more musical sense, since it means that you have a tonaly equal range in both positive and negative scale.

CWITEC

KVR Audio

TX16Wx 3.1 beta available (updated 2019-07-01)