Legato notes not playing
I have this problem when I have successive notes adjacent to each other. The 'note on' doesn't light up for the second note, so the first note just keeps playing. Happens with Subtractor, Thor. I have polyphony at 1, mono retrig and legato both tried. Any clues?
IMHO the 2nd note have a too short decay - attack is too lazy ADSR make SURE there's no overlap.
verify http://www.reasontalk.com/viewtopic.php ... gato+notes
verify http://www.reasontalk.com/viewtopic.php ... gato+notes
My man, I'm guessing using Kong to trigger these sounds wasn't your problem then? The polyphony settings should work. Wat type of midi board are you using? Maybe it has some type of priority trigger mode?? Try programming the notes via the matrix (or drawing them in the sequencer with the pencil tool) and see if anything is different. Anyways, post the Thor or Subtractor patch you are referring to.
Reason is my girlfriend. Sometimes she mistreats me, but I still love her.
Checkout my tunes made with Reason: https://soundcloud.com/geez-musicals
Checkout my tunes made with Reason: https://soundcloud.com/geez-musicals
I can't recreate this no matter what I do. The Note On light ALWAYS lights even when you don't hear anything.alexfsu wrote:I have this problem when I have successive notes adjacent to each other. The 'note on' doesn't light up for the second note, so the first note just keeps playing. Happens with Subtractor, Thor. I have polyphony at 1, mono retrig and legato both tried. Any clues?
You'll have to give more info, maybe a screen shot of the note data in the sequencer, or a simple song file that exhibits this behavior? I can't for the life of me come up with any situation where this could/should happen.
Selig Audio, LLC
https://www.dropbox.com/s/0b3w4r1yhdss7r1/4.reason?dl=0
I have a Subtractor looped, it's being triggered by a Kong pad but it happens when triggered normally too. When the loop starts again, does the first Subtractor note not play for you too?
I have a Subtractor looped, it's being triggered by a Kong pad but it happens when triggered normally too. When the loop starts again, does the first Subtractor note not play for you too?
OK, you failed to specify that you were triggering Subtractor via CV... The thing is that when you trigger an instrument via CV, the only way for it to know that a new note is being triggered is that either 1) the Gate voltage drops to 0 and then goes positive again OR 2) a new pitch arrives at the CV input.alexfsu wrote:https://www.dropbox.com/s/0b3w4r1yhdss7r1/4.reason?dl=0
I have a Subtractor looped, it's being triggered by a Kong pad but it happens when triggered normally too. When the loop starts again, does the first Subtractor note not play for you too?
Kong doesn't send any pitch CV, just gates, so alternative 2 is out. And since you're playing legato notes on it, the extra note on information will "get lost" and you will get a continuous gate coming out from the pad, making it impossible for Subtractor (or any other instrument!) to detect any new notes... So you have to make sure there's a gap between the notes, or it won't work.
I think that ideally, Kong would ensure that there are gaps on the CV out (or at least offer an optional "retrig mode" with this behaviour), but unfortunately this is not the case. But I can think of three possible workarounds:
1. Make sure the note ends a fraction before the end of the bar, ensuring there's a gap.
2. Copy Kong's MIDI part to Subtractor's track and remove the notes that trigger the other pads.
3. Put Subtractor and Kong together in a combinator, and instead of connecting the pad to the Subtractor via CV, you define the key range for the Subtractor (in the combinator programmer) to match that of the Kong pad. (You may also have to adjust the Transpose setting to get the correct pitch.) This way, Subtractor will be triggered via MIDI instead of CV, and its Retrig mode will be in effect.
And finally, a recommendation: When you send a song to verify a problem, please don't assume that we all use separate outputs, or many of us will have to redo the audio cabling manually.
thanks for the reply, I'll utilize your advice for gate issues. But here' s a regular Thor patch sent to the master, legato notes (blank template with normal routing), and only the first note plays. Does it for you? Sorry for posting a lot, I just use repeat legato notes a ton, especially like in this project with repeating claps.
https://www.dropbox.com/s/uw2h9xt36thmp ... eason?dl=0
https://www.dropbox.com/s/uw2h9xt36thmp ... eason?dl=0
The problem here is that the handclap patches in Thor use the step sequencer to simulate the repeated envelopes found in handclap synths. If you take a look at the top of Thor you'll see that Trigger is set to "Step Seq"... So the legato/retrig settings won't apply.alexfsu wrote:thanks for the reply, I'll utilize your advice for gate issues. But here' s a regular Thor patch sent to the master, legato notes (blank template with normal routing), and only the first note plays. Does it for you? Sorry for posting a lot, I just use repeat legato notes a ton, especially like in this project with repeating claps.
https://www.dropbox.com/s/uw2h9xt36thmp ... eason?dl=0
But there's a workaround:
Create a new Subtractor while holding Shift so it doesn't auto route. Connect its Mod Env output to Thor's step sequencer Gate input (at the very bottom of the device, so you have to unfold it). Then move the MIDI part from Thor's sequencer track to Subtractor's sequencer track. You may need to turn down the decay on Subtractor's mod envelope a bit.
- tobypearce
- Posts: 576
- Joined: 28 Sep 2015
- Contact:
I've had this problem for a while, and I just realised what the problem is, at least in my case.
If you have groove applied to a midi track, Reason fails to take this into account, resulting in overlapping notes that don't play correctly.
I've just made a post on a feature request because I do think that Reason's behaviour could be smarter here, and it actually makes legato function much less useful if you regularly use groove.
If you have groove applied to a midi track, Reason fails to take this into account, resulting in overlapping notes that don't play correctly.
I've just made a post on a feature request because I do think that Reason's behaviour could be smarter here, and it actually makes legato function much less useful if you regularly use groove.
https://onetrackperweek.com
One year - 52 tracks - Electronic Dance Music
One year - 52 tracks - Electronic Dance Music
-
- Information
-
Who is online
Users browsing this forum: huggermugger, Sogou [Spider] and 33 guests