Hi!

I have windows 11 x64. Live's version is 11.0.6.

When I play my MIDI keyboard with VSTi instruments I have dropouts. But I see that the MIDI keyboard is connetced and sending its signals correctly to a VSTi. But there's no sound.

I've found that it happens when high velocities are played (ff or fff). So I have to reload VSTi - that's the only way to repair sound from it. But Nexus has different behavior. It just makes itself a lot quiter. And I just should stop playback and play it again (2x on the spacebar).

Any thoughts?

 

it sounds like you are seeing what the vst you are using is really hitting your resources like, and the other stuff is overload protection sorts of behavior. buffers set correctly? everything else working correctly under windows 11 already?

 

yes, I tried 64-512 buffer size settings. The higher values cause a big latency when playing. Yes, everything else I use is working correctly on Win 11

 

there are so many details that you shouldn't skip any. I don't use nexus, but in falcon I have single patches that hit my cpu like 25%. like 16 voices x4 or 5 keys per chord. then something on top, things go pretty quickly. connecting it via Komplete Kontrol or something would be interesting.
someone with a pc could narrow it down for you but...

what daw, plugin, any plugin wrapper like Komplete, what model kb, cpu specs, 401k number,
that would help you get a better answer.

 

You're right. I should give more detailed specs.

System: Windows 11 x64 21H2
Motherboard: Fatal1ty Z170 Gaming K4 (ASRock)
CPU: Core i5 6400 (overclocked to 4 Mhz)
Memory: 16gb
The Live's version: 11.0.6
Keyboard: M-Audio Oxygen 61 (silver)
Audio Interface: SC Signature Series MTK 22 with its native driver

P.S. I've tried FL Studio, Cubase, Studio One. And there was no problem on these DAWs.
The VSTs I've found the problem in: True Piano, Garritan Abbey Roads Piano, Nexus 3. Still haven't tried others

 

Last edited: Oct 11, 2021

Did the problem occur before Windows 11 or after installing Windows 11?
I would take back the overclocking and set the C-stats correctly in the bios.
Download the PDF and read it through. Use LatencyMon.

Deactivate CPU Power Saving Management in the BIOS
In some cases it is recommended to deactivate the power saving settings of the CPU in the BIOS. In this article we will show you where you can find the options and how you can deactivate them so that the power management options CPU P State Control and CPU C State Control are completely deactivated in the BIOS.

Deactivate CPU power management
1. Press the Delete key during the boot process to enter the BIOS
2. Go to -> Advanced CPU Configuration -> Advanced Power Management Configuration
3. Change Power Technology to Custom and Energy Efficient Turbo to Disable
4. Switch to CPU P State Control, deactivate EIST (P-States) and Turbo Mode
5. Then switch to CPU C State Control, change Package C State Limit to C0 / C1 state and deactivate CPU C3 Report, CPU C6 Report and Enhanced Halt State (C1E).

Don't let audio glitches ruin your performances!
An in-depth guide to tuning Windows for reliable real-time audio performance. A free eBook.
https://www.cantabilesoftware.com/glitchfree/

LatencyMon
https://www.resplendence.com/latencymon

LatencyMon checks if a system running Windows is suitable for processing real-time audio and other tasks. LatencyMon analyzes the possible causes of buffer underruns by measuring kernel timer latencies and reporting DPC and ISR execution times as well as hard pagefaults. It will provide a comprehensible report and find the kernel modules and processes responsible for causing audio latencies which result in drop outs. It also provides the functionality of an ISR monitor, DPC monitor and a hard pagefault monitor.

LatencyMon will display the highest latencies of a kernel timer and report the highest execution times of ISR and DPC routines as well as hard pagefaults. In most cases it will also find the drivers and processes responsible for executing them. It will create a comprehensible report which also displays all sampled data in a detailed manner allowing you to perform in-depth analysis.

 

Beat16, you forgot to mention to disable Windows 11.

Nothing good comes from a Microsoft beta OS. I'd go with W10 LTSC and "lite" as possible, or W10 Pro, also as "lite" as possible.

You see, with Microsoft, it's always been this formula to makes things work best: be at least one version of Windows behind.

I'm still happily using W7. Just for making music, of course.

 

Online or offline that is the question.

 

Thank you for the detailed reply! I've already known must of this and already been set long ago. I've searched lots of information about overclocking and stuff. Actually there was no such problem on FL, Cubase, S1 even on Windows 11 (my own version)

 

Hi! Now I found that sound drops out even when I play with QWERTY keyboard. And even on 'Wavetable' synth.

 

Is the problem only with these 3?

In my opinion this is either a memory or a CPU problem. Possible solutions see my post before.

Obviously one of these "standard" problems:
- Inappropriate Audio interface (USB->Audio)
- setting a too small buffer size (latency)
- too low CPU performance
and/or
- Windows system not tweaked for audio performance, Other software running in the background using too much CPU at certain points in time

 

Last edited: Oct 14, 2021

I've installed Live 11 v 11.0.11 (the lastest version) and the problem is gone! Finally! I'll write here if the problem would appear again.