Thanks for the great work!

I compiled the sources, which went smoothly, but running the app or loading the AU, VST, … in a DAW caused crashes. I debugged on Mac with Xcode/lldb and found out that the crashes occur inside the routine that loads

source/jucePlugin/parameterDescriptions_C.json

since there are C++ comments (// …) in the json file. Removing all // comments (which I think are not allowed in json) solves the problem and then everything works fine.

Thus, I suggest to remove the // comments from the json file.

<@770574624953073665>,<#841809045505703956>,Re the .deb files for Linux. The install locations are not typically used (it’s dropping to /usr/local/lib/ which means users having to add additional DAW paths to plugins. Typically you want VSTs in either /home/username/vst or /home/.username/vst3 (which are the most convenient ones, doubly so because the Rom can then be put in the plug-in folder alongside without using sudo) or /usr/lib/vst /usr/lib/vst3 -less convenient because you then have to use sudo, plus a lot of users will copy the folders to home anyway to keep plugins out of root. Also I e noticed the file structure for the VST3 isn’t right. It only drops a .so file (as per vst2), vst3 files go in a /plug-in name.vst3/Contents/x86_64-linux/pluginname.so,Jump To

<@777578228859535410>,<#841809045505703956>,I think there is a bug in INPUT channels.. I was trying to figure out what is going wrong for about an hour and then I put a stereo track with different parts in each channel. The but is that LEFT is RIGHT and RIGHT is LEFT (reverse order).. When I enable the plugin the channels get reversed!,Jump To

When saving a patch with the save button on top, and then loading the patch, the semitone of -1 for some of the osc (might be all). I suspect there might be more off-by-one issues with saving/loading patches.

I think it is in the saving stage, not loading.

Version: v1.2.10 Platform: MacOS and Windows (Linux not tested) DAW: Bitwig ROM: Virus C 6v6

Hi, I have added a Skin2 to my fork. I have adapted the CMake file for this purpose. Maybe you can do the build process differently.

I hope you can take over the source code from me.

Greetings trancy

couldn't find an existing variable that tracked current bank/program per part and the data in the multi didn't seem to be correct so added some new variables to track it's when changed. if there's a better existing place to get that data let me know and i'll update this.

The parameter state is not getting saved in single mode. It appears to work in multi mode, however in single mode this functionality is broken..

Reproduce: Open new project, load plugin, switch to single mode, load init patch, tweak patch, close and save project. Open project, init patch comes up, but tweaks are lost.

Fixes #102

Problem:

In Bitwig Studio, under particular conditions, the VST3 plugin renders at more than twice the size, due to the host calling the plugin's JuceVST3Editor::setContentScaleFactor method during plugin setup. Unfortunately, setContentScaleFactor, as written, overwrites the user's scaling choice made in the GUI/saved in the config file.

Affects:

Bitwig Studio users (any DAW that sends setContentScaleFactor) -- specifically, Windows users who have display scaling set above 100% and Linux users who use a 4k display resolution.

Solution:

We patch JuceVST3EditController::setEditorScaleFactor to prevent overwriting the user's GUI scale choice. Now, it reads the 'user scale' and calculates the final scale as the 'user scale' times the display's 'content scale factor'. We also patch AudioProcessorEditor::setScaleFactor to memorise 'content scale factors' sent by the plugin host (via JuceVST3Editor::setContentScaleFactor) in the event the user wishes to change the editor scale manually but not overwrite the 'content scale factor' currently applied.

Fixes #102

Problem:

In Bitwig Studio, under particular conditions, the VST3 plugin renders at more than twice the size, due to the host calling the plugin's JuceVST3Editor::setContentScaleFactor method during plugin setup. Unfortunately, setContentScaleFactor, as written, overwrites the user's scaling choice made in the GUI/saved in the config file.

Affects:

Bitwig Studio users (any DAW that sends setContentScaleFactor) -- specifically, Windows users who have display scaling set above 100% and Linux users who use a 4k display resolution.

Solution:

We patch JuceVST3EditController::setEditorScaleFactor to prevent overwriting the user's GUI scale choice. Now, it reads the 'user scale' and calculates the final scale as the 'user scale' times the display's 'content scale factor'. We also patch AudioProcessorEditor::setScaleFactor to memorise 'content scale factors' sent by the plugin host (via JuceVST3Editor::setContentScaleFactor) in the event the user wishes to change the editor scale manually but not overwrite the 'content scale factor' currently applied.

I enabled this parameter by giving it a name and making it public. I hacked it into the hoverland skin, but feel free to reject that bit if you prefer to keep the right fonts in the skin.

<@301269194534682624>,<#841809045505703956>,ah, got it now 🙂 Yes that would be helpful. However, I noticed something else with regards to that: Semitone range is -48 +48 only, not -64 +63,Jump To

<@1007369959715909653>,<#841809045505703956>,If this means /Library/Audio/Plug-Ins/VST3/DSP56300Emu.vst3/Contents/MacOS/ then it doesn't work...,Jump To

<@786247470958116914>,<#978315928800485416>,I have an issue with the vst3 version in reason. As soon as I load the plugin i get a warning that the midi messages are about to overload and my hardware is not able to handle that. Havent had this with the vst2 plugin, anything i can do about it?,Jump To

<@1007369959715909653>,<#841809045505703956>,I've got some random cpu spikes about every minute or two. Didn't had this in 1.20. Bitwig Studio, Apple M1 Pro chip.,Jump To

<@771395420868968479>,<#841809045505703956>,<@301269194534682624> , please, if you have some free time, add the remaining 4 pairs of parameters to the right link toggle switch in the Filters section: Reso 1<->Reso 2, Env 1 Amt<->Env 2 Amt, Keytrack 1<->Keytrack 2, Res 1 Vel<->Res 2 Vel. The pair Env 1 Vel<->Env 2 Vel you've already done. Thank you!,Jump To

<@465564675182952469>,<#841809045505703956>,Bug: Latest version, Windows 11, Cubase 12 If you lower or raise the volume in the multis, all the knobs mimic each others. I never paid attention to this before but if the proper track isn't highlighted, you can't affect it's volume or panning properties. I'm a bit uncertain how it worked in previous version, I haven't seriously used the emu in awhile.,Jump To

<@930159337043800156>,<#841809045505703956>,In the latest release the GUI works faster and re-opens the tab you left with, not the first one. All good, but when re-opening, the delay/ reverb module doesn't work properly. Bottom parameters cannot be changed anymore, you can unblock them for a while by changing the skin. Not be able to work with the delay/ reverb is huge for me, hope it gets a fix.,Jump To