drum sequencer player, disable STICKY background routing?

This forum is for discussing Reason. Questions, answers, ideas, and opinions... all apply.
Post Reply
thumperjack
Posts: 3
Joined: 28 Aug 2022

15 May 2023

im using a drum sequencer player with redrum, but using the CV outs of the player into a spyder merge and into redrum. so i can use two channels of the player for the kick, and two channels of the player for the snare.


whenever you put player next to instrument or instrument next to player, it auto connects in the background without cables. you can disconnect device and route manually and it's ok.

but if you want to put the player and the redrum into a combinator, it reconnects the players invisible connection while keeping your manual cabling, and you have to disconnect and do the CV cabling again. that ok.

but um...if you so much as add an effect, anywhere, or move anything, way outside of the combinator, having nothing to do with the combinator holding the manually cv routed player and redrum...it automatically reconnects the player's invisible connections to redrum. that's where i ;ahsdf;lkajsdkfaj;ds lost it. :clap: you can't even move anything inside reason, or delete anything, without the player reconnecting. is there a way to disable the player auto connect? you can't even save it in that state, if you save it and close and reopen, the player is reconnected.



steps to reproduce:
1. load player drum sequencer, redrum, and spyder merge
2. disconnect all
3. player cv 1 and 2 to spyder merge, merge to redrum cv 1 (kick). player cv 3 to redrum 2 (snare), player cv 4 to redrum 3 (ghost), player cv 7 to redrum 10 (ride)
4. redrum audio out, make any pattern. load the attached redrum and player patch to get an idea where it was going
5. once the player CV is working right, try to add anything, anywhere, or delete anything. no matter what you do or where, any routing changes trigger the player to sticky reconnect itself, leaving the cv cables still going. if you also save once the cv cables are working, if you reopen the project the player reconfigures itself. i even just tried to add an audio track to make audio examples and the player reattached itself.

the zip file has a redrum patch and a player drum sequencer patch, the pngs shows what's in the zip file and what the cabling should be. audio examples too
attachments.png
attachments.png (11.15 KiB) Viewed 251 times
player says nope.zip
(15.51 KiB) Downloaded 14 times
what it should look like.png
what it should look like.png (834.61 KiB) Viewed 251 times

User avatar
selig
RE Developer
Posts: 11738
Joined: 15 Jan 2015
Location: The NorthWoods, CT, USA

15 May 2023

Simplest is to just let it route to ID8 and don’t connect ID8 audio. Below that add ReDrum and go nuts!
Selig Audio, LLC

thumperjack
Posts: 3
Joined: 28 Aug 2022

15 May 2023

how it started.mp3
(116.53 KiB) Downloaded 19 times
where it's going.mp3
(84.69 KiB) Downloaded 20 times

thumperjack
Posts: 3
Joined: 28 Aug 2022

15 May 2023

selig wrote:
15 May 2023
Simplest is to just let it route to ID8 and don’t connect ID8 audio. Below that add ReDrum and go nuts!
that works, thanks, just keep ID8 there as a screen. maybe a player switch would be less CPU intensive

User avatar
mimidancer
Posts: 666
Joined: 30 Sep 2021

21 May 2023

selig wrote:
15 May 2023
Simplest is to just let it route to ID8 and don’t connect ID8 audio. Below that add ReDrum and go nuts!
I was going to say set drum sequencer on the midi out device then connect the gates. In the end same solution. Great minds and apparently minds like ours too.

Post Reply
  • Information
  • Who is online

    Users browsing this forum: Chi-Individual and 30 guests