
gentleclockdivider
Awesome , it works prefectly now
I wonder since the selector~is a cyclone module , how would one achieve this with pure data vanilla ,iow build an audio rate selctor ? 
gentleclockdivider
I am trying to recreate the cyclone custom kink module , which distorts the phase of the phasor
This is the implementation in reaktor primary
A comparitor compares the incoming phasor sig X ( range 01) against variable D .
When x > d , then green field algo , when X<D blue box algo .
The output of the comparator~ ( which is square wave ) should then open route the algo's to an audio rate selector ( just like reaktor °) , but this just isn't working .
The algo's are correct , could it be that the selector module is not selecting it's input at audio rate ?
Here's the patch
customkink.pd
Result ( in reaktor °)

gentleclockdivider
@whaleav said:
@KMETE I cannot find a reference to a cold inlet of a message object in Max....... only https://docs.cycling74.com/max7/refpages/message
If you can post a link that would be useful.In Pd a list..... like 1 2 3.... is distributed to the inlets of most objects. You can see that in use when you send a message into [line]. Is that what you mean by "connecting outlet of an object to multiple inlets of another object in one go"?
If not then maybe you are looking for a shortcut method for patching....https://forum.pdpatchrepo.info/topic/13471/shortcutreplacingwires
David.When using the right inlet of a message in max, the message box kind of behaves like a float module , a verry handy feature and strangely enough not really documented .
https://www.google.com/search?q=max+msp+right+inlet+of+message&rlz=1C1QPHC_nlBE953BE953&oq=max+msp+right+inlet+of+message+&aqs=chrome..69i57j33i160.4914j0j7&sourceid=chrome&ie=UTF8#fpstate=ive&vld=cid:58116efb,vid:5gFHaOQwBuE 
gentleclockdivider
@jameslo said:
@gentleclockdivider OK, since you know that the slope of the line determines the frequency, the next question to ask is where is the slope the greatest, and where is the slope decreasing. And I suppose to drive the point all the way home, what would you expect if the slope is 0, i.e. the line was flat? And would your answer change if the value of the flat line was 3 vs 3000?
Asnwer 1 , the slope is the greatest at the beginning , and decreasing shortly after that .
If the slope was 0 and the line flat the cos~ would not be driven .
If the slope was on existent and the line linear we would have a steady cos~pitch 
gentleclockdivider
Now I'v got it ..( I hope )
The line~ into sqrt does phase distortion
I compared it with ( cyclone ) kink~ (phasor into kink~) which adds a variabe breakpoint to the linear ramp of the phasor
First screenshot shows phasor into sqrt~(upper ) and lower phasor into kink~ .
Second screenshot shows both outputs (left sqrt,right kink ) multiplied and into separate cosines .
The cosine when driven by kink ~ is obviously played a higher pitches before the breakpoint ( steeper rise ) and a steady lower pitch .after that . ( when using mul*)
The sqrt ~ becasue of the conitinous rise has a fallen pitchbend
Always worked with phase disrtion to distort ramps into lookuptables , kind of asurprise its capable of pitchbend

gentleclockdivider
I know it determins the frequency( that's w hy I posted the screeshots )
, I am just wandering why the frequency is going from high to low ( pitch bend down ) while the envelope clearly shows it's rising .from 0 to 1 , fast in the beginning = high pitch ° , slower at the end )
DId the same in reaktor ( replaced the line with a ramp wave going from 0 to 1 ) going into a sine function
I think I found it but not sure
The envelope going rom 01 is rising the pitch because for the sine fuction it doesn' t really matter , iow it runs backwards .
Does that make sense ?

gentleclockdivider
I saw some one using a line~ into a sqrt~ to create a kick and something is still not right to me .
First screenshot shows line~ going from 0 to 1 in 222 ms I recorded straight to dac
Left shows linear curve and the sqrt~function makes it curvy and thus a faster rise in the beginning.
The puzzling part is when driving this into a cos~ ,
Left shows the actual pitch bend ( after multiplying the sqrt~output ) and right shows the actual curve ( without mutliplying since this would be a huge DC signal )
I don't understand why the pitch ( or rather the phase ) of cos~ is falling instead of rising , tbf I really feel like an idiot for not grasping this 
gentleclockdivider
When feeding a line~ with message 0, 1000 1000 into a cosine
So , play 1000 during 1000 ms there is severe aliasing but only after 500 ms of playing ( see sidebands )

gentleclockdivider
Interesting use of the s/h~
I guess it's just a matter of preference of using a comparator or S/H
The ~ 0.25 in your example is exactly what solved it
Thanks 
gentleclockdivider
I have created a kind of pulse width sine thingie where I can define the nr of sine waves in one period by use of a comparitor
Works great , more or less
Obviously the sine needs to be stationary (0hz° ) and the phase input is modulated by a phasor .
The issue is settting the starting phase of the sine because when it's a cosine there are discontinuties ( becasue it starts from 1) , the starting phase sometimes works with the nr. 1.429 ,but most of the time not (blue rectangle on picture )
Max msp obviously suffers from the same issues with cycle~ but it has a sinx~ object which takes 2*pi as input.
Here's the stuff
narrow sine.pd