Re: [PD] less intelligent patching for Pd

[Maximiliano Estudies]

This looks great!

I'm testing the osx/64bit build in Sierra.
The only thing that seems odd is the cycle-connect for the inlets, but
maybe I got it wrong. If I press tab the connection jumps to the next
inlet, but when I release the mouse it still connects to the inlet that's
nearer to the mouse, here 
a short demo.


El jue., 6 jun. 2019 a las 13:28, Roman Haefeli ()
escribió:

> On Thu, 2019-06-06 at 11:19 +0200, IOhannes m zmoelnig wrote:
> > On 05.06.19 23:21, Miller Puckette wrote:
> > > next release... I'll merge it as soon as it's done getting tweaked.
> >
> > in order to finish tweaking, i will need feedback. the more the
> > merrier.
>
> Thanks for your work. I find the short cuts memorable and think they
> work very well. I absolutely like the new features.
>
> > i'm especially looking forward to feedback from actually testing the
> > new
> > feature-branch (as opposed to watching the video and liking it).
> >
> > so if you you know how to run a compiler, please check out [575],
> > compile and test.
>
> I'm running this feature branch now and will keep using it and report
> back. So far, I can't see any problems. It seems to me you improved
> many little details, for instance when I undo a fan-out, I don't have
> to step through each individual connection anymore.
>
> Really nice work!
>
> Roman
>
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management ->
> https://lists.puredata.info/listinfo/pd-list
>


-- 
Maximiliano Estudies
+49 176 36784771
omslo.com
maxiestudies.com
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] status of leap motion controller in Pd, especially on Linux? - another way

[Peter P.]

Thanks Miller, I now found the time to try your approach and it is
indeed a nice one! Three quick questions arise:

If I don't terminate the output of the Sample.cpp program with a
semicolon it also works. Is there a difference?

What would be the best formatting to save as much network traffic as
possible? I discover that Pd (wish, for that matter) consumes quite a
lot of cpu when receiving tracking data. Do newlines make a difference?

Did you manage to get rid of commas or parentheses in Sample.cpp's
output? I can't seem to find a way to do it but it would help
tremendously to parse the data in Pd with [route] and [unpack].

Curious and excited, with thanks!
Peter

* Miller Puckette  [2019-03-12 17:22]:
> Hi all -
> 
> I didn't have much trouble ust compiling the "Sample.cpp" example in the
> 2.3 development kit; this prints lots of stuff on standard output.  I then
> changed the print statements in the code to only print out the numbers I
> cared about with a trailingsemicolon, then piped to "pdsend", giving it
> a UDP port in my patch.
> 
> Because the sample program sometimes just quits I make an auto-restarting
> script:
> 
> while true; do
> /home/msp/work/poolbox-leap/leap2pool |\
> /home/msp/pd/bin/pdsend 3000 localhost udp
> echo restart...
> sleep 1
> done
> 
> (where "leap2pool" is my version of Sample.cpp).  I think this is pretty
> robust - if a leap extern in Pd decided to crash it would takePd down but
> the way I do it I only lose a second of connection.
> 
> cheers
> Miller
> 
> On Tue, Mar 12, 2019 at 03:32:59PM +0100, Peter P. wrote:
> > * Max  [2019-03-12 15:18]:
> > > I think you need to start pd with the leap library preloaded:
> > > 
> > > LD_PRELOAD=~/path/to/LeapDeveloperKit/LeapSDK/lib/x64/libLeap.so
> > > ~/path/to/pd/bin/pd ~/path/to/patch.pd
> > Thanks Max, that's what I already did in the call to the debugger:
> > 
> > $ gdb --args 
> > LD_PRELOAD=LeapDeveloperKit_2.3.1+31549_linux/LeapSDK/lib/x64/libLeap.so 
> > /usr/bin/pd -path linux64bit Pd_leapmotion_0.1_mac/leap_motion_help.pd
> > 
> > Without debugger the external fails indeed without that line. 
> > 
> > 
> > 
> > ___
> > Pd-list@lists.iem.at mailing list
> > UNSUBSCRIBE and account-management -> 
> > https://lists.puredata.info/listinfo/pd-list
> 
> 
> 
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> 
> https://lists.puredata.info/listinfo/pd-list



___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] [PD-dev] First complete keyboard navigation prototype

[Christof Ressi]

Hi, this looks like wonderful! I'll try it out in a couple of days and give 
feedback. I can also help with code if needed.

My biggest issue with visual programming is the amount of mouse interaction 
needed in contrast to text based programming (especially when sitting in a 
shaky ÖBB-train with a tiny laptop). A keyboard workflow like yours could be 
extremely useful for power users.

Christof


Gesendet: Samstag, 08. Juni 2019 um 04:52 Uhr
Von: "Henri Augusto Bisognini" 
An: "pd-...@lists.iem.at" 
Betreff: [PD-dev] First complete keyboard navigation prototype

Hi!
 
I've finally managed to get time to finish a prototype for a keyboard 
navigation interface. I mixed some ideas i had with some I've seen in Desire 
Data's old screenshot gallery (http://artengine.ca/desiredata/).
 
I've recorded some gifs to demonstrate it. 
(https://imgur.com/gallery/WSB40P7[https://imgur.com/gallery/WSB40P7]). It 
shows me using the help patch (which i've put in 7.stuff/keyboard.navigation). 
You can read about which keys to use in the comments.
 
The source can be found on my GitHub, on the kbd_nav branch 
(https://github.com/HenriAugusto/pure-data/tree/kbd_nav[https://github.com/HenriAugusto/pure-data/tree/kbd_nav])
 
Basically I've wanted to try:
 
- navigating through objects/inelts connection with ctrl+arrows (cmd+arrows on 
Mac)
- automatically positioning new objects according to selected inlet/outlet
- a console bar to send messages to the focused patch
- ability to display each object index (to be used with the functionalities 
below)
- a new "goto" canvas message to select any object in the patch
- a "magnetic connector" that connects the selected in/outlet to the nearest 
ins/outs
- a "digit connectors" that displays indexes 0 to 9 for the 10 nearest possible 
connections. Just press the number and it will connect it for you
- pd can automatically fill for you a "connect" message in the console 
containing the info for the selected inlet/outlet. It will even select for you 
the part you need to fill
- You can click objects with shift+enter. Mostly useful for sending bangs and 
opening subpatches/abstractions
 
Everything is intended to be as minimal as possible and very easy to use. I 
wish to propose we study including it in vanilla.
 
Well, what do you guys think?
 
This is my first time working on a project this big so help me out if i did 
anything incorrectly. I've been testing the major functions on Win for a while 
now but couldn't test on mac/linux.
 
Cheers,
Henri.___ Pd-dev mailing list 
pd-...@lists.iem.at 
https://lists.puredata.info/listinfo/pd-dev[https://lists.puredata.info/listinfo/pd-dev]



___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] [pure-data/pure-data] a tutorial for internal messages (#651)

[Christof Ressi]

I also want to point to this PR of mine: 
https://github.com/pure-data/pure-data/pull/627

The idea is to finally stop people from abusing non-stable internal dialog 
messages like [donecanvasdialog( - I'm guilty of this myself - and instead 
provide a sane way to manipulate GOP rects via messages.
 
Christof

Gesendet: Samstag, 08. Juni 2019 um 12:53 Uhr
Von: "Fede Camara Halac" 
An: pure-data/pure-data 
Cc: Subscribed 
Betreff: [pure-data/pure-data] a tutorial for internal messages (#651)
There has been some improvements and discussions on dynamic patching lately and 
I would like to share a personal guide on how I managed to work with internal 
messages a couple of years ago, partly using existing information from 
puredata.info and from the g_*.c files. Perhaps this could be useful to tidy up 
with better instructions on what to do and what not do do.
https://github.com/fdch/fd_lib/tree/master/tutorials
I think it would be good to have some sort of guidelines help patch for this in 
the manual.
I'm up for that. I've been actually working on something like this in 
https://github.com/porres/Live-Electronic-Music-Tutorial[https://github.com/porres/Live-Electronic-Music-Tutorial]
 - but it's not icluded yet, will be in the next version!
Originally posted by @porres[https://github.com/porres] in #623 
(comment)[https://github.com/pure-data/pure-data/issues/623#issuecomment-491453716]
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on 
GitHub[https://github.com/pure-data/pure-data/issues/651?email_source=notifications_token=AD3BFKHEY5QOOEOTWHMBXS3PZOFT3A5CNFSM4HWG7ZIKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GYMFCCA],
 or mute the 
thread[https://github.com/notifications/unsubscribe-auth/AD3BFKHYOTEDLBWOPPP25ULPZOFT3ANCNFSM4HWG7ZIA].




___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list