Reply to thread

Message: [QUOTE="Bombastus, post: 92272, member: 2178"] Kveik 1.3 fixes the Windows FL Studio freeze that could occur when you pressed the spacebar with Kveik’s interface open. Playback control is now safe, but FL Studio still needs one wrapper option enabled if you want the spacebar to reach the transport while Kveik has keyboard focus. The distinction matters because a dead spacebar can look like the old bug at first glance. In 1.3, pressing space with the Kveik window focused should no longer lock FL Studio. If nothing happens instead, you are dealing with keyboard routing, not the freeze that Bitlantis fixed. With [B][URL='https://goldmidi.com/community/threads/bitlantis-has-expanded-kveik-1-3-with-per-track-arp-mode.77646/']Kveik’s FL Studio transport fix[/URL][/B] installed, the remaining job lives in FL Studio’s Plugin Wrapper. Open the wrapper settings for Kveik, go to Troubleshooting, and enable “Allow FL Studio to process keyboard presses when the keyboard focus option is on.” FL Studio remembers the setting for Kveik once it is enabled. [HEADING=2]The freeze and the silent spacebar are separate problems[/HEADING] Before Kveik 1.3, a Windows 11 user reported a hard freeze when using the spacebar to start playback while the Kveik interface was open. Bitlantis addressed that failure in 1.3 and later confirmed that the same user’s setup was working after the update. The repaired behavior is simple. The plug-in can stay open without the transport keystroke locking the DAW. A silent spacebar after updating has a different cause. FL Studio decides how keyboard presses move between its own interface and third-party plug-in windows, and the focused window gets first claim on the input. A plug-in can therefore be perfectly stable while the DAW transport still fails to react to a key you expected FL Studio to receive. This is normal focus behavior rather than a Kveik-specific transport feature. [B][URL='https://patents.google.com/patent/US20080034304A1/en']Keyboard-focus control in graphical interfaces[/URL][/B] describes the same underlying rule at the interface level. One graphical component holds focus and receives keyboard input at a given moment. FL Studio adds wrapper controls so you can decide how unused keystrokes are forwarded when a plug-in window is active. [HEADING=2]One FL Studio option restores the transport shortcut[/HEADING] Open Kveik in FL Studio and use the gear icon in the plug-in window to reach the wrapper settings. Under Troubleshooting, enable the option that allows FL Studio to process keyboard presses while the keyboard focus option is on. The name is long, but the behavior is straightforward. When keyboard focus is active, keystrokes normally go to the plug-in first. Enabling this wrapper option lets the plug-in press the key without continuing to FL Studio. For Kveik, that is what allows the spacebar to behave as a transport command while you are still clicking and editing inside the sequencer. The setting is per plug-in rather than a universal fix for every third-party instrument already loaded in your projects. Once enabled for Kveik, FL Studio remembers it, so you should not have to repeat the same configuration every time you reopen the plug-in. Typing Keyboard Priority is related but not identical. FL Studio also provides a wrapper control that changes whether the DAW or the plug-in gets first use of keyboard shortcuts, and the application has broader focus options for difficult plug-ins. For the Kveik 1.3 spacebar case, Bitlantis specifically points to the Troubleshooting option that forwards unused keyboard presses to FL Studio. [HEADING=2]Focus problems are easy to misdiagnose as plug-in bugs[/HEADING] If Kveik 1.3 stays responsive but space no longer starts or stops playback after you click inside its window, do not treat the symptom as evidence that the freeze returned. First confirm that you are actually running 1.3 or later, then check the wrapper option. A working GUI plus an ignored transport key is a different failure pattern from a DAW lockup. Detached or bridged plug-in windows can complicate keyboard focus more broadly in FL Studio. Those window states may take focus in ways that affect keyboard behavior, so they are worth checking if the dedicated Kveik setting does not solve the shortcut problem. They are secondary checks, not replacements for the option Bitlantis specified. The practical test takes seconds. Click inside Kveik, press space, and watch whether FL Studio starts and stops cleanly while the plug-in remains responsive. If transport works, the focus path is configured correctly. If the spacebar does nothing but the DAW keeps running normally, revisit the wrapper setting rather than chasing the fixed freeze. A real recurrence looks different. FL Studio becoming unresponsive after the keystroke would no longer match the expected 1.3 behavior and deserves a fresh bug report with the Kveik version, FL Studio build, Windows version, plug-in format, and a reproducible sequence. Keeping those two symptoms separate makes troubleshooting much faster and prevents a simple focus setting from being mistaken for the crash that 1.3 already addressed. [/QUOTE]

Name