Search found 347 matches

by Arne Scheffler
Fri Sep 20, 2019 12:44 pm
Forum: VSTGUI
Topic: IPlatformFont issue when upgrading VSTGUI4.0->4.6
Replies: 7
Views: 670

Re: IPlatformFont issue when upgrading VSTGUI4.0->4.6

Regarding CFrame it's correct what you wrote. Otherwise read thru vstgui/doxygen/page_changes.h. Most breaking changes are written down there.

Cheers,
Arne
by Arne Scheffler
Fri Sep 20, 2019 9:22 am
Forum: VSTGUI
Topic: IPlatformFont issue when upgrading VSTGUI4.0->4.6
Replies: 7
Views: 670

Re: IPlatformFont issue when upgrading VSTGUI4.0->4.6

I still think that the issue is that the compiler needs the

Code: Select all

vstgui/lib/platform/iplatformfont.h
include.
What happens if you add it to that file where the CFontDesc are used ?
by Arne Scheffler
Fri Sep 20, 2019 8:32 am
Forum: VST 3 SDK
Topic: Mapping VST 2 parameters to VST 3
Replies: 3
Views: 484

Re: Mapping VST 2 parameters to VST 3

What exactly is not in the FAQ? The persistent state stuff or the parameter stuff ?
by Arne Scheffler
Fri Sep 20, 2019 8:31 am
Forum: VSTGUI
Topic: IPlatformFont issue when upgrading VSTGUI4.0->4.6
Replies: 7
Views: 670

Re: IPlatformFont issue when upgrading VSTGUI4.0->4.6

So, you're compiling vstgui_win32.cpp ?
Then I don't know how this header:

Code: Select all

1>c:\<projectfolder>\<product>\source\wsplashwnd.h(37)
could be included other than changing the vstgui sources. And then I think you have a wrong order of includes in this file.

Cheers,
Arne
by Arne Scheffler
Thu Sep 19, 2019 9:17 pm
Forum: VSTGUI
Topic: IPlatformFont issue when upgrading VSTGUI4.0->4.6
Replies: 7
Views: 670

Re: IPlatformFont issue when upgrading VSTGUI4.0->4.6

Hi,
without seeing the compiler output I can only guess that an include to vstgui/lib/platform/iplatformfont.h is missing.

Cheers,
Arne
by Arne Scheffler
Thu Sep 19, 2019 8:56 am
Forum: VST 3 SDK
Topic: Mapping VST 2 parameters to VST 3
Replies: 3
Views: 484

Re: Mapping VST 2 parameters to VST 3

Hi,
the state persistence is described in the FAQ section in the documentation.
A plug-in has to set the VST3 parameter ID to the index of the VST2 parameter when updated to VST3. Otherwise automation is not compatible.

Cheers,
Arne
by Arne Scheffler
Mon Sep 16, 2019 8:58 am
Forum: VSTGUI
Topic: Bitmap with 2 frames issue
Replies: 2
Views: 388

Re: Bitmap with 2 frames issue

You can play with the bitmap interpolation quality if you can get rid of this artifact:
https://github.com/steinbergmedia/vstgu ... rame.h#L52

Cheers,
Arne
by Arne Scheffler
Thu Sep 12, 2019 11:45 am
Forum: VST 3 SDK
Topic: Attention: macOS code signing!
Replies: 0
Views: 577

Attention: macOS code signing!

Hi, please make sure that if you code sign your plug-ins that the code signature is valid. We now see plug-ins that are signed, but with an invalid code signature which will trigger a crash on load in any hardened runtime enabled host. To verify that your code signature is valid please run codesign ...
by Arne Scheffler
Thu Sep 12, 2019 6:39 am
Forum: VST 3 SDK
Topic: findParameter test tool?
Replies: 2
Views: 434

Re: findParameter test tool?

Hi,
it's inside the VST3PluginTestHost in the SDK. Look under the view menu there is an entry "Enable Parameter Popup". If you enable it and move your mouse over the plug-in you will see the parameter ID under the mouse in an overlay window.

Cheers,
Arne
by Arne Scheffler
Fri Aug 30, 2019 8:06 am
Forum: VST 3 SDK
Topic: VST and HiDPI
Replies: 5
Views: 778

Re: VST and HiDPI

The IPlugView should only create hardware resources when the attach() method is called. So you should be safe to first create the plugview instance and then check for the IPluginViewContentScaleSupport interface before calling attach().

Cheers,
Arne