Bug in Kong where the CV gate out of the pads wired to another CV Gate input causes the dignal to be delayed, making the triggered sample sound like a flam/long delay.
Bug in Complex where the sound just stops and the only way to bring it back is to "reset device" and then Ctrl+Z to bring back the original patch. Sound stops again when I start/stop the sequencer.
Kong & Complex bug
- crimsonwarlock
- Posts: 2432
- Joined: 06 Nov 2021
- Location: Close to the Edge
Did you submit support tickets at the RS website?
-------
Analog tape ⇒ ESQ1 sequencer board ⇒ Atari/Steinberg Pro24 ⇒ Atari/Cubase ⇒ Cakewalk Sonar ⇒ Orion Pro/Platinum ⇒ Reaper ⇒ Reason DAW.
Analog tape ⇒ ESQ1 sequencer board ⇒ Atari/Steinberg Pro24 ⇒ Atari/Cubase ⇒ Cakewalk Sonar ⇒ Orion Pro/Platinum ⇒ Reaper ⇒ Reason DAW.
This is an obvious case of feedback, which is "forbidden" in digital signals and is solved by introducing delay, typically equal to the audio buffer size (but this time for MIDI).
I don't think this is a bug.
However, there's "link group" functionality in Kong precisely for triggering 2+ pads when only one is pressed.
https://www.google.com/url?sa=t&rct=j&q ... i=89978449
Can't reproduce either; Kong triggers via CV accurately and I'm not sure how to re-create the Complex bug but have never experienced it in my many explorations (including contributing to the original sound bank).
Here's the response with Kong Gate out on the default kit Kick to a copy of Kong Gate In, showing no delay at all.
Here's the response with Kong Gate out on the default kit Kick to a copy of Kong Gate In, showing no delay at all.
Selig Audio, LLC
-
- Posts: 415
- Joined: 09 Apr 2020
What Reason version, OS and chipset are you running? And is complex -1 up to date? Just curious if it’s specific to your system.
-
- Information
-
Who is online
Users browsing this forum: jengstrom and 30 guests