S?bastien Bourdeauducq wrote:
> (1) "Differentiate" the camera signal. Instead of drawing the direct
> picture from the camera, draw the difference between the last two
> frames, e.g. defined as:
> diff(x,y).c = |f1(x,y).c - f2(x,y).c| for each color channel c=r,g,b
That sounds interesting. It may
S?bastien Bourdeauducq wrote:
> (2) Provide pre-built maps for common MIDI controllers. Maps are
> already saved in performance files, but it could be convenient to
> have "partial" performance files that only alter the MIDI map. Maybe
> Werner is on this already.
Totally on my roadmap :-)
My ide
Great
On Tue, Dec 20, 2011 at 7:08 AM, Sébastien Bourdeauducq
wrote:
> Hi,
>
> I demoed the M1 to Peter Kirn and some of his friends last Thursday. He came
> up with a few interesting ideas:
>
> (1) "Differentiate" the camera signal. Instead of drawing the direct picture
> from the camera, draw t
Hi,
I demoed the M1 to Peter Kirn and some of his friends last Thursday. He
came up with a few interesting ideas:
(1) "Differentiate" the camera signal. Instead of drawing the direct
picture from the camera, draw the difference between the last two
frames, e.g. defined as:
diff(x,y).c = |f1
Hi
after I rebase the patches on rtems-yaffs2 on top of upstream yaffs2. and apply
this patch to rtems:
http://www.rtems.org/pipermail/rtems-devel/2011-December/87.html
now copy files by using 'filezilla' 'lftp' works fine now.
but it still give some error when using 'nautilus'.
rtems irc
