Reach out to the plugin developer (what plugin is it)
If you’re hearing sounds when you switch back then the plugin is not properly clearing its audio buffers when it is sent a reset request.
It’s mainly with Arturia Solina. But I can also hear it with pianoteq and some Roland string plugin, when I bypass and power it on.
Regarding the big pops at first loading, no way to delay the sound engine starting once all plugins are loaded ?
Crazy thing, you are not supposed to hear anything. Does this happen with only one GP instance too? Does it happen when one GP instance is started and you start the second one?
This probably not a good idea, as if you are using the Prédictive Loading option, the sound engine has to be active anytime because you are playing while GP is loading the next song.
It happens with only one instance just after booting the PC. Once it has been launched one time it doesn’t glitches anymore on next loadings.
I have the same cracks issues when moving from one rack space to the next, happens with different plug ins
It’s best to create a new thread and explain what is exactly happening.
OK, so if I understood well, everything is OK when RDP is not active?
When RDP is active, you hear a crack when you first run Gig Performer?
Can you try VNC or VPN connection instead?
Or AnyDesk, there is a client for Android.
Will do cheers
Ok I’ve fiddled with audio params of the Firerface (unchecked all useless input/output, restricted fw bandwidth to analog signals). I’ve rebooted the pc a lot of time, checked with win10 rdp, Android rdp…
I’ve also restricted GP to 2 of the 4 cores with Process Lasso, optimized PSU performance…
Glitches at the first launch are gone !
Now the remaining concern : audio tails!
In fact the phenomenon happens when I use a bypass widget to turn off a plugin.
For instance, I’ve a rackspace with piano and strings layered. Two widjets buttons are bypassing bith plugins. When I bypass the string as sound is still in the release phase, it is cut. But when I reactivate the plugins, I can hear the remaining sound tail that was cut at bypass. Even if it’s 2 minutes later !
Is there a trick to mute and de-mute audio when bypassing/reactivating plugin ?
This can only be solved by the plugin. It should be clearing its buffers when it’s bypassed. You should contact the plugin vendor.
1 Like
Hi all,
Still on my audio glitches problem at GP startup.
I’ve still sometimes glitches when I launch a gig file. When it happens (only while loading the project), I can play rackspaces without a flaw. But as soon as I open a second instance, I’ve loud cracks staying all the time (it’s like 20hz continuons pulses).
I have to close both instances and when I launch GP again, all is always working nice.
These glitches only happen at the first time I launch GP after PC booting. Sometimes it happens, Sometimes it doesn’t… But once GP has been launched and closed one time, it never appears again.
CPU is 6700k with 12GB RAM (8+4)
My soundcard is an RME FF400. It works well at 48k with a 128 buffer (3 instances without any glitch).
I’ve tried many things without consistent results :
- Windows sound parameters, untick all shitty options (effects, exclusive mode…)
- Reducing FW bandwidth (enabling only analog channels) in RME control panel
- Enabling MMCSS in RME CP
- Enabling/disabling gig autolaunch in GP
- Enabling only used analog channels on GP
The last thing could be the RAM… I’ve read that it’s not recommended to mix different size of RAM.
I’ve only two slots of RAM on the mb (HP ProDesk 400 G3)
Any advice ?
But overall, appart from these weird glitches, GP is very stable and playable.
It is not, indeed, especially if they work on different speeds.
What happens if you remove the 4 GB module?
As for the instances, are they all running at the same buffer size/sample rate?
Exactly the same sample rate and buffer settings for the 3 instances.
I will try to remove the 4gb module. Are there ‘‘usual’’ reported troubles with RAM in real time audio ?
I’d move to 44.1k and 192 samples. You cant tell the difference between 44.1k and 48k during live performance, and you’ll save yourself some CPU cycles. 192 samples shouldn’t affect your realtime playing either.
2 Likes
Also make sure that windows itself is NOT using your audio card as it’s device .
What do you mean? Should I disable the FF400 in the device manager ? It will also disappear in GP no?
Actually the FF400 in active in the taskbar (speaker icon).
It seems that there are other people complaining on the crackling noise coming from FF400
Link: Crackling Noise Coming from FF400 - Gearspace.com
1 Like
No - disabling the interface will disable it for everyone.
Make sure that windows system sound device is not your audio interface but built in sound card.
I thank that’s In windows system preferences / audio or sound settings
djogon, I think you nailed it !
I’ve tried many things : operating the PC directly with keyboard, mouse and display (no RDP), removing the 4GB RAM module, disabling MIDI-OX, Process Lasso, fiddling with RME device parameters… without any success.
But, as you noticed it, the FF400 was also my sound device for Windows (I disabled the Realtek audio chipset in the device manager). So I have reactivated it and assigned it for windows sound system.
Since then, no more cracks! I’ve tried to start GP many times, after maybe 20 reboots, and cracks seem to be gone!
Thank you so much because I would have never thought to deal with the Realtek chipset.
Finally, it seems to be quite logical : the onboard Realtek chipset dedicated to windows sounds, the RME for GP realtime audio.
Regarding the sound tails problems when switching back and forth rackspaces, I finally solved the problem by using dedicated reverb/delay plug-ins instead of using the onboard effects of my synths VST. No more tails with these plug-ins. Maybe they are better managing the output buffer clear.
JB
3 Likes
Great stuff. Thanks for the update.
2 Likes