Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Osc: open stage device with stepped parameter reads out incorectly #55

Open
Sebastian-blu opened this issue Mar 15, 2018 · 7 comments
Open

Comments

@Sebastian-blu
Copy link

Using a vst3 plugin and mapping a macro to something on the instrument that is a selector type (fixed values) often the names reported back to the tablet are off from where the switch is

So if it’s a simple on off, the tablet will show on when it’s off. And it gets worse when it has more steps like models in fabfilter Saturn.

Might be a bitwig bug too I can’t tell

@git-moss
Copy link
Owner

git-moss commented Mar 16, 2018

But the value in Bitwig is displayed correctly?
Did you also experience that in other VST3s? (I do not have Fabfilter -> if there is a VST2 , is it correct there?)

@Sebastian-blu
Copy link
Author

I just checked and it happens on other brands like bx and others. anything stepped... the value is correct in bitwig. it tends to be correct when you first look at it but if you change it, the update process appears broken

@git-moss
Copy link
Owner

git-moss commented Mar 16, 2018

Hmm, I cannot reproduce that. I have VST3s from iZotope and u-he. Do you have any of those manufacturers and can give an example? Or a freeware?

@Sebastian-blu
Copy link
Author

Sebastian-blu commented Mar 16, 2018

img_0043
screenshot_2018-03-16 16 51 45_lahikr

these two photos of a mapping to izotope vinyl were taken at the same time

@Sebastian-blu
Copy link
Author

mapping to the warp model gets off too, it seems to be a problem with the bitwig popups as well

@Sebastian-blu
Copy link
Author

Sebastian-blu commented Mar 16, 2018

screenshot_2018-03-16 16 44 25_hmgyti

getting the tablet to match with the plugin almost never happens once it is. how quickly you switch seems to be part of it

moving the macro in bitwig linked to the year updates incorrectly on the parameter list in bitwig and on the tablet.

@git-moss
Copy link
Owner

I could reproduce it with the filter type of Ozone 8 but it happens also in the VST2 version. Also controlling it does not really work (tested with Push 2). Will report it to Bitwig.

@git-moss git-moss removed the bug label Mar 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants