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

Cannot edit values using keyboard - DMG Audio in Bitwig #367

Open
1 task done
kuchtamartin opened this issue Sep 6, 2024 · 1 comment
Open
1 task done

Cannot edit values using keyboard - DMG Audio in Bitwig #367

kuchtamartin opened this issue Sep 6, 2024 · 1 comment

Comments

@kuchtamartin
Copy link

kuchtamartin commented Sep 6, 2024

Thanks for giving yabridge a shot!

  • I read through both the troubleshooting and the known issues sections, and my issue wasn't listed there

Problem description

When trying to edit values precisely using a keyboard in both DMGAudio Limitless and DMGAudio TrackControl, only the first keypress is registered. After the first keypress, the keyboard appears unresponsive. Values can still be changed by mouse. Happens on both VST2 and VST3 flavours. Nothing mentioned in Bitwig engine.log

Works as expected in REAPER.

What did you expect to happen?

I would like to key-in precise values. Other plugins in my collection don't have this issue.

What actually happened?

Nothing. After the first key is registered, nothing happens.

Operating system

Gentoo

How did you install yabridge?

directly from Releases page

yabridge version

5.1.0

yabridgectl version

5.1.0

Wine version

wine-staging-9.16

Plugin

DMGAudio Limitless

Plugin type

VST2

Plugin architecture

64-bit

Host

Bitwig Studio 5.2.3

Desktop environment or WM

KDE Plasma 6.1.4

GPU model

AMD RX6600

GPU drivers and kernel

mesa 24.1.6 on linux 6.6.38

Debug log

yabridge.log

Anything else?

There was actually more then 10000 lines of the:

18:08:11 [Limitless-4HLOWery]    dispatch() :: 0, <key_name>
18:08:11 [Limitless-4HLOWery] >> dispatch() effGetProgram(index = 0, value = 0, option = 0, data = nullptr)
18:08:11 [Limitless-4HLOWery]    dispatch() :: 0
18:08:11 [Limitless-4HLOWery] >> dispatch() effGetMidiKeyName(index = 3, value = 0, option = 0, data = <key_name>)
18:08:11 [Limitless-4HLOWery]    dispatch() :: 0, <key_name>

With the same timestamp. Thousands lines for each effGetMidiKeyName index. I redacted it.

@relaborn
Copy link

relaborn commented Oct 4, 2024

I can confirm this issue in the VST3 versions of Limitless and Track Control.

The workaround for me in Bitwig is to twiddle the value a bit and then use the bitwig device controls to type in a value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants