OK, I simply wasn't paying attention to proper structures with until and
a counter, I have worked it out now. Thank you for your patience
IOhannes, I will post some deliverables of this project soon.
Derek
On 17/07/2017 12.59, IOhannes m zmoelnig wrote:
ouch. that shouldn't work at all.
on
Sorry I guess I need a bit more help figuring out what you mean then
please.
Should I be banging the left most inlet of [pix_data] once every sample?
I am now sending the same until 64 counter to both the X and the Y
inputs. But I am still having trouble understanding how to synchronize
OK then I think I need a little more help understanding what is going on
here then please.
Should I be sending a bang every sample to the left most inlet of
[pix_data]? How do I synchronize all the reading counters so that every
sample I get a new value of the luma value at X and Y?
I have
On 2017-07-17 12:38, Derek Holzer via Pd-list wrote:
> Very interesting!
>
> However, what comes out is still limited by the block size to every 64
> samples as far as I can tell. I've tried every trick I can to send
> sample precise messages in, but all I ever get is 64 sample rate
> messages
Very interesting!
However, what comes out is still limited by the block size to every 64
samples as far as I can tell. I've tried every trick I can to send
sample precise messages in, but all I ever get is 64 sample rate
messages out.
Or am I missing something? See attached.
D.
On
On 2017-07-17 11:52, Derek Holzer via Pd-list wrote:
> Can anyone see how I could get audio rate data out of [pix_data], or if
> there might be another way to get luma values with an audio signal?
i've never had a problem with [pix_data] at audio rate, using something
like the following:
Dear PD folks,
I'm trying to cook up a Pd/GEM version of the Rutt-Etra scan processor,
which sends audio signals to an analog CRT vector
monitor/oscilloscope/etc to control the vertical and horizontal
positions of its beam, plus its brightness.
The video posted here is webcam->MaxMSP->MOTU
