![propellerhead reason 7 stuttering propellerhead reason 7 stuttering](https://www.reasonexperts.com/uploads/redrum-16-channels.jpg)
With some luck, maybe it'll happen to me too :)Īs I said earlier, my LoopBoxes are much simpler and basic devices (so much so, that I'm thinking of releasing some for free, because there's really nothing new there), so with those I use no CV, it's all done with the usual channel mute technic and Combinator Modulation Routing mappings.Ībout the BV512 not generating enough CV to mute a channel when inverted, that depends on the velocity you applied to it and also and most importantly, to the CV scale you set at the back of the device.Īre you sure your keyboard can generate a velocity of 127 ?
![propellerhead reason 7 stuttering propellerhead reason 7 stuttering](https://s3.amazonaws.com/audiotuts/133_reasonperformance/3.jpg)
I'll have to wait before someone else confirms what you describe and then I'll have a second look at it. One of the keyboards I can specify the value of the velocity, so I did force some values with it too, and still couldn't replicate what you describe :( The mixer levels keep stable too, I also used an external Signal Analysis, and I saw no progressive raise of the dB's.īesides synthetically generating the velocity values (using a RPG-8 to force them, or using the sequencer automation) I also tried it with 4 MIDI keyboards, all with different velocity curves, and still no problem. I did all of what you said, and again, I tried with various velocity values, from 32, to 64, to 100 to 127 and did the double and triple quick trigger of B1 and A#1 and hold it for more than 30 seconds and the device stays stable and does what I expect it to do. Thank you for describing the steps to replicate the bug. ( about this case, please contact with me on mail ) Reply Delete
#Propellerhead reason 7 stuttering for free
It will be problem if I and You will try sell it in the same time, or you will give it for free download. Īlso I still thinking about collab with you, because we are have very similar combinators. Now because I explain you how it works, can you show me why you use thor with aftertouch. Now in my combinator I don't control mute by cv. When you create/open vocoder it looks it is working, but when you play "voconote" and release it it will back to 98% or something like that.Ħ.Mute channel 14, play B1 one time, and when than maximize your sound output in os, or hardware. You can't make 100% mute using inverted vocoder cv.
#Propellerhead reason 7 stuttering how to
If you will see it, probably you will hit your had in to wall asking where is that evil bug and how to fix it. I find this bug in my own old combinator because i have in my WIN7 gadget with volume control and audio output display.
![propellerhead reason 7 stuttering propellerhead reason 7 stuttering](https://i.ytimg.com/vi/1X0kmWchpXM/maxresdefault.jpg)
Try connect reason output to audio analyzer or if you have very good years you will hear it. Tracks in preview can sounds different after render. ( probably reason have compression or something) Not always it want to grow, and it is hard to see it in reason mixer. (It will be easier when you fast click B1 2 times ) Use B1 and try glitch loop on 50% of velocity. If they work as expected, they get in on it too :) Reply Deleteĥ. V.8.0 is also planned to have some additional things I'm working on. I think I already mentioned, but there's still some features missing from ReGRAINZeR that I'll add in V.0.7 (external control of sister/companion FX boxes). The stage from V.0.9 to V.1.0 will be exactly that, optimization of the stable feature list implemented. Some cabling routes are still unnecessarily long, with extra hops that will disapear in the final version. A lot of spiders and CV in there is used simply for clarity while still in development stage. My LoopBoxes simply use Mix Mutes, with no velocity sensitivity.Īlso, right now, the demo uses V0.6.2 beta, and as I'm sure you already know, betas are pre-optimization, so this is why there's still so much CV cabling. I don't know if you noticed this, but the volume of the loop (the dry/mix) is driven by the velocity you apply.īy design, I made it this way, because you can on-the-fly, apply some effect where it applies the looping effect briefly while kicking in the original source (there's an example of it in the demo song, with the quick and brief stuttering of the guitar). I must check those then, thanks for the feedback! :)