serial communication, processing libraries

[Hairi Vogel (airi)]

Hello. I am new to PraxisLive, but a long-time professional SuperCollider, Processing  and Isadora programmer. I am truly fascinated by the approach implemented by praxis and learning to use it now.

Question: What is a smooth way to implement serial communication ??

I tried fooling around with RxTx.jars with no luck and wonder whether I could use the Processing Serial library, but how ???

Anyway one would like to use Processing libraries like Minim, PixelFlow, Physics and so on.

Seems easy unless they rely on .dll(s).

Other question:

What would be the approach to writing a video-delay (minutes) ?

Just put the PImages in a huge ring-buffer in java ??

Thanks for your patience with a newbie :-)

hairi

[Neil C Smith]

Hi Hairi,

Welcome! Thanks for your email. Some thoughts inline ...

On Wed, 19 Oct 2022 at 18:46, Hairi Vogel (airi) <hairi...@gmail.com> wrote:
> Hello. I am new to PraxisLive, but a long-time professional SuperCollider, Processing and Isadora programmer. I am truly fascinated by the approach implemented by praxis and learning to use it now.

Glad you like what you see. Do ask if you have any questions about
the approach. This video of my Write Now, Run Anytime talk might be
of interest too -
https://skillsmatter.com/skillscasts/14039-london-java-community-june

> Question: What is a smooth way to implement serial communication ??
> I tried fooling around with RxTx.jars with no luck and wonder whether I could use the Processing Serial library, but how ???

Haven't used serial with PraxisLIVE for a long time - I'll see if I
can find anything useful in my archive.

> Anyway one would like to use Processing libraries like Minim, PixelFlow, Physics and so on.

Libraries can be added to projects, either from a local file or using
a Maven dependency. See https://docs.praxislive.org/coding-libraries/

Using libraries can require some unusual code sometimes. Check out
the PeasyCam example here
https://github.com/neilcsmith-net/praxislive-iclc2019/tree/master/Projects

I'm working on some things that will make working with libraries a
little easier. Development is picking up again now, having been
stalled by some other work for a while.

PixelFlow might be difficult - had a feeling there were some
assumptions in it that make working with the offscreen buffers in
PraxisLIVE a little awkward.

Why Minim? Is there something specific missing for you in the
built-in audio library? It's also available as a standalone project
at https://github.com/jaudiolibs/pipes Audio is a big part of my own
creative use of PraxisLIVE, such as from the end of the above talk -
https://youtu.be/tkJxd2IOQQY

> Other question:
> What would be the approach to writing a video-delay (minutes) ?
> Just put the PImages in a huge ring-buffer in java ??

That will likely have memory issues after a few seconds of storage. I
have a component somewhere that does this, which I thought had been
added to the additional components but can't find it.

For longer delay, it might be better to look at some way of writing
the frames to disk, possibly using the GStreamer support. If you
check the archive at https://gitter.im/praxis-live/development there's
a bit of discussion about a component that pushes images to a
GStreamer pipeline.

Hope that helps!

Best wishes,

Neil

[Hans Heinrich Vogel]

Great stuff Neil !
I will work with your hints and once familiar with PraxisLive
find out if there is a way to contribute for me.
Modules and Patching delight and inspire me in many ways for 50 years now.

cheers
Hairi

> --
> You received this message because you are subscribed to a topic in the Google Groups "PraxisLIVE discussion group" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/praxis-live/gogvz1dS1uY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to praxis-live...@googlegroups.com.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/praxis-live/CAMYaZEs%2B%3Dq_Us2JM%3DrL59tuZMRRyfLRrTRNL5_qgZwfMoBO1-g%40mail.gmail.com.