Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
trigger Vs cv, mod arrival
#1
every once in a while I have time to try new set ups,  I seem to come back to old issues. Something I’ve run into in the past trying to set up voices works fairly well no audible issues.  But one style set up I consistently run into issues with is drums where the voice of samples is controlled by either the mod or the cv.

I use one of the first 6 channels, trigger controls the trigger.., mod or cv controls which drum hit or timbre, and the last remaining one controls some parameter of the sound. Every sound source I’ve tried has the same results. The nerdseq triggers the previous sound chosen, and then plays the choice on the next round. Meaning the cv is a step behind the trigger. I’ve tried this with numerous instruments

Er-301 sound computer:
Sample set up with slices
Cv is set up for picking samples per note(c = slice 1, c# = slice 2 etc)
Trigger is set to trigger, however trigger plays the previous choice and the current
For this module it’s solvable very easily by setting up a micro delay on the triggers input forcing the trigger to wait until the proper sample has been chosen by the cv. 

1010 bitbox
Same situation as er301, but had visual display of the previous trigger blipping before the current one would come up. I actually sent via email once. 
There was no hope for this thing, eventually sold it.

Assimil8or 
Same deal as the other two

Noise eng basimilus iteritas alter , or akemies taiko being controlled by Malekko voltage block 
Trigger triggers the drum source
Cv is sent to the voltage block to choose one of its 16 slots, then voltages are sent to the multiple input parameters of the drum modules.

Same deal, the trigger triggers the previous sound and not the current chosen sound, then waits to trigger it the next time around. 

Has anyone else had this problem. Am I doing something wrong? Or is there an option which I’m not taking within the nerdseq. This is the kind of thing that is small enough to push off and deal with later but sinister enough to prevent you from gettin any work done. 

Thanks
Reply
#2
I have an Erica Sample Drum with the exact same setup that you use for the ER-301 with no issues. The only thing I can think is to make sure you haven't somehow triggered a glide on the CV or MOD, as then the value you're expecting would be a bit behind.
Reply
#3
Do you fill in the trigger column or use the autogate note with kill?
Try the 2nd one. I think i made some scope measurings before and they showed that the trigger comes after the cv is stable.
Reply
#4
I just wanted to do a quick follow-up with my previous post: I forgot that my Sample Drum actually has a 1ms delay setting for incoming trigger settings. When I turned it off, I experience the same issue as you. I tested out XOR's above mention of autogate and kill but still couldn't get it to not have a delay (and would occasionally play the same value twice)
Reply
#5
I was planning also to include a little trigger delay on demand for modules which got problems with the CV vs tigger sampling. But still, the trigger would be then a bit too late which is not a wanted situation in several cases.
Reply
#6
(08-05-2019, 07:12 PM)XORadmin Wrote: Do you fill in the trigger column or use the autogate note with kill?
Try the 2nd one. I think i made some scope measurings before and they showed that the trigger comes after the cv is stable.

I do fill in the trigger column.   I tried the second one. Same results.

I tried it on the Assimil8or. The er301 is an easy fix. I think what skybox did with his Erica synths device. Same with er -301. The Assimil8or doesn’t have a trigger delay feature as far as I know but not so most samplers it would seem
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)