[L2Ork-dev] GSOC 2021 Introduction and queries

Jonathan Wilkes jon.w.wilkes at gmail.com
Tue Apr 6 17:57:56 EDT 2021


On Tue, Apr 6, 2021 at 7:20 AM Tanmay Gujar <tanmaygujar999 at gmail.com> wrote:
>
> Hello again! A couple of clarifications on the issue.
>
> I am running pd on Debian(Ubuntu 20.04.2 LTS) and used "make all" to build the project.
> I have had no trouble in communication when pd-l2ork is run without the nogui flag.
> The pd process with nogui flag exits as soon as I send a message through the socket connection. I have also tried to use the pdsend tool available in the puredata-utils package, but it leads to the same error.

Hm-- what audio backend are you using when you run it in normal mode?

-Jonathan

>
> Regards,
> Tanmay Gujar
>
> On Tue, 6 Apr, 2021, 1:43 pm Tanmay Gujar, <tanmaygujar999 at gmail.com> wrote:
>>
>> Hello I am Tanmay! I am a recently accepted student to the MS CSE program at UCSD. I am interested in contributing to purr-data and plan to submit a proposal for GSOC 2021.
>>
>> Specifically, I would like to work on the Terminal REPL project. I have been looking through the source code to find an appropriate way to execute the idea but I have hit a few roadblocks.
>>
>> Thoughts so far:
>> For communication between pd and the REPL I plan to use Internal pd messages as described on the Puredata info page and also in the purr-data Repo.
>>
>> I have managed to open a socket connection using nodeJS and I am able to send operations to pd using the [netreceive] object.
>>
>> Issue:
>> When I run pd with the nogui flag, as users would when using an embedded device, and send operations to it, the process exits with the message
>> Pd: signal 6.
>> What could be the potential problem?
>>
>> Feedback on approach:
>> Is this an appropriate approach to bridging the gap between the REPL and pd. i.e the REPL interface would be an abstraction over the Internal Pd message interface.
>>
>> Regards,
>> Tanmay Gujar [Github] [Gitlab] [Site]
>> UCSD MS CSE Fall 2021
>>
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> https://disis.music.vt.edu/listinfo/l2ork-dev


More information about the L2Ork-dev mailing list