[PD-dev] Pd running on external scheduler changed

[Lucas Cordiviola]

Ok, no rushing if you are traveling.

> First, what exactly does "not work"? 

---
;
pd dsp 1;
---

does not start dsp (the toggle in the main Pd window never gets to "on")

> Second, these two message should obviously be equivalent. Are you 
> really sure that they behave differently?

yes.

[dsp 1(
|
[s pd]

works.

> If yes, that would be a bug in Pd's message system, not in my 
> scheduler updates.

I could check that the messaging system for other receivers work like [; 
foo 3( works as expected with [r foo].

> When I made the updates, I tried not to break the external scheduler 
> mechanism and checked that pd~ still works.

yes. pd~ still works.

> Maybe it's an issue in your scheduler implementation? 

nothing changed in pdvst~ scheduler implementation (well yes, but using 
the unchanged version the issue is still there on current master Pd and 
not with Pd 0.54-1).

> I'll need to have a look at your code, ...

sure: 
https://git.nubegris.com.ar/lucarda/pdvst-0.52/src/branch/sq-fudi/vst-scheduler/vstschedlib.c

you could also see the "master" branch but as mentioned it also exhibits 
the issue.



--

Mensaje telepatico asistido por maquinas.

On 24/04/2024 06:40, Christof Ressi wrote:
>
> On 24.04.2024 09:45, Lucas Cordiviola wrote:
>> Hi,
>>
>> I'm working with some new feature of pdvst~ 
>> (https://git.nubegris.com.ar/lucarda/pdvst-0.52/compare/master...sq-fudi) 
>> this runs Pd via external scheduler "vstscheduler.dll"
>>
>> I hit some strange issue with current Pd (Merge branch 
>> 'scheduler_fix' 2bea249)
>>
>> this message no longer works
>>
>> ----------
>> ;
>> pd dsp 1;
>> ----------
>>
>>
>> while this one works
>>
>> [dsp 1(
>> |
>> [s pd]
>
> First, what exactly does "not work"? Second, these two message should 
> obviously be equivalent. Are you really sure that they behave 
> differently? If yes, that would be a bug in Pd's message system, not 
> in my scheduler updates.
>
> When I made the updates, I tried not to break the external scheduler 
> mechanism and checked that pd~ still works. Maybe it's an issue in 
> your scheduler implementation? I'll need to have a look at your code, 
> but I'm travelling right now.
>
>>
>> is not something I changed in pdvst~. Is something that only exhibits 
>> with the newest Pd.
>>
>> I can live with it but may be this is some "peak of iceberg" ?
>>
>>
>> -- 
>>
>