Well i was hoping i wouldn't have to use any kind of timers for that job... [int] followed by [change] do a good and (in terms of cpu) inexpensive job, but to "resample" my control flow i will need [metro] or [pulse] afaik... if i do that, of course i will not add a [metro] to each knob and envelope but i will set up a central "control clock" with a single [metro] and then i will feed this to every part that needs to "resample" control signals.<br>
This leads me to the question (i remember it coming up earlier but i cannot find the topic sorry), if i want to basically modify pd's own control rate, is there a more direct/general way to do it?<br><br>Thanks,<br><br>
Andras<br><br><div class="gmail_quote">2009/7/19 Alex <span dir="ltr"><<a href="mailto:x37v.alex@gmail.com">x37v.alex@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You could try making it so that you don't send sysex messages on every<br>
change.. just poll for changes at a certain rate.. and only sent the<br>
most recent change at that rate?<br>
<br>
-Alex<br>
<br>
2009/7/17 András Murányi <<a href="mailto:muranyia@gmail.com">muranyia@gmail.com</a>>:<br>
<div><div></div><div class="h5">[...]<br>
> Now that i'm trying with a Midisport everything is OK.<br>
> Another thing was that i was a bit lost in Yamaha's midi spec for the mu100<br>
> but i've found it out. ;)<br>
><br>
> However now i see that pd's performace is becoming really waving as i'm<br>
> tring to pump out more midi data.<br>
> My old-new questions would be:<br>
> - Provided that a knob is directly driving a sysex pattern which spits out<br>
> way more data than necessary, who do i best slow down my data, staying<br>
> realtime? I guess i shall drop some of it somehow, or i shall kinda resample<br>
> the datastream. Could you Sirs recommend an economic way to do this?<br>
> - My machine is a moderate powerhouse (Opteron 148 @2200, 4G), my kernel is<br>
> rt and audio in pd is off however performance is waving, and my simple<br>
> sequencer is becoming unstable. What are the crucial points of keeping the<br>
> patch 'fast', where do you think i generally lose the most cpu?<br>
><br>
</div></div></blockquote></div><br>