event-table resolution confusion ???

In the manual it's said that after a song pos module ' typically connect this to A input of the modulo with a 6 at the B input to get a 16th note count at the div"

With the 'thingo' (can't call it something else so far) i've made, I can't use anything larger than 2 at the B input otherwise the triggered sample goes a sort of 'prrr'....

Now i could just leave it, but the question here is, is my bpm still right when using it in a host as a plug-in ??
And of course, if anyone knows, why does it go prrrr... ?

See also the JPG.

 

your bmp should be right. try a step filter after your modulo to fix the purrr.

 

Thanks, what would i set at the tolerance, or if this depends on the rate at which song pos is spitting, how can i see what that rate is ?
(exactly, not just about with hoovering over)

 

you can just leave the tolerance empty. the div output will only send whole numbers, so if you just really want to put something in there make it <= 1. the modulo sends an event for every calculation, you just want the first event when it changes.

 

When connecting the stepfilter, with or without tol, It stops making sound........
Everthing continues, except the sounds. (loose drumhits)

euhh ?

 

just to be sure, you have:
song position->modulo->step filter-> everything else?
that should work. maybe another .jpg? as jn mentioned in another thread you should use an order module to set the table read position before reading it.

 

Ok, i put in the order mod, doesn't seem to make any difference though..

here's the pic

 

But when i do this....

NO sound anymore, whatever i tweak...

really apreciate your help btw...

 

ok, back in black...
all i can tell you is that i tested this out (see jpg) and it definitely works, for all i can tell yours should too... *grasping at straws* i don't know, delete your step filter and insert a new one? i guess all you can really do is turn the info on and trace over the wires to try and see where the problem is.

 

Hello again, the forum went down last night, with a 500 error or something.

Fooling around a bit i found out the gate input at the sampler loop was causing the problem.
The gate starts the loop at an event > 0 and needs an event <or= 0 to start the release after that.. so after some empirical research i found out a 'A to gate' mod did the trick, no more 'prrr' at any value at the 'B' input at the modulo mod.

I'll have a try with a new Stepfilter, just because i'm curious to see if that's it.

 

forgot the picture.....

 

Yep, it works.
I put in a new stpflt and now the sound continues.....

Should be a line in the manual-addendum:

" When an imported module does not what it is supposed to do, delete it and import it again.... perhaps it will work as should."