Hi
When using GOP abstractions with 'Hide object name and arguments'
checked, I seem to not be able to change the arguments after creation.
When rewriting the whole argument list in a new object is too tedious,
I sometimes revert to editing the patch file with a text editor.
Is there a way to ed
basically you want to rewrite an object - doesn't matter if it's gop,
subpatch, or something else - without editing it yourself. it's a nice
idea, maybe possible for now with some ugly message hackery, probably
involving mouse simulation?
instead of thinking it from the receiver end (editing s
On Fri, 2021-09-10 at 10:43 +0200, João Pais wrote:
> basically you want to rewrite an object - doesn't matter if it's gop,
> subpatch, or something else - without editing it yourself.
No, I simply want to edit it manually in the patch editor, but cannot
because the arguments are not visible. Als
On Fri, 2021-09-10 at 10:58 +0200, Roman Haefeli wrote:
> Ok, I could save
> with GOP disabled, edit it, enable GOP again. But that is still not a
> very good use experience.
It's even worse: When saving it, all (other) instances are reloaded and
therefore loose their state. This is definitely not
On Fri, 2021-09-10 at 11:00 +0200, Roman Haefeli wrote:
> On Fri, 2021-09-10 at 10:58 +0200, Roman Haefeli wrote:
> > Ok, I could save
> > with GOP disabled, edit it, enable GOP again. But that is still not
> > a
> > very good use experience.
>
> It's even worse: When saving it, all (other) instan
Hey all
I'm using current git master and found that the way color information
of iemguis is stored in the patch file has changed. The number
representing 6-bit-per-channel rgb values got replaced by a hexadecimal
encoding like '#dfdfdf'. That is a huge advantage, but how far back are
such patches
On 9/10/21 5:07 PM, Roman Haefeli wrote:
Hey all
I'm using current git master and found that the way color information
of iemguis is stored in the patch file has changed. The number
representing 6-bit-per-channel rgb values got replaced by a hexadecimal
encoding like '#dfdfdf'. That is a huge ad
On 9/10/21 8:37 AM, Simon Iten wrote:
hi there,
I am finding conflicting (unclear) info on readsf~ behaviour. I want to
loop a long 8 channel wave file.
here are my questions:
-once i open the file with a message and after a delay start playback and
it has finished (rightmost outlet bangs), can
On Fri, 2021-09-10 at 17:13 +0200, IOhannes m zmoelnig wrote:
> On 9/10/21 5:07 PM, Roman Haefeli wrote:
> > Hey all
> >
> > I'm using current git master and found that the way color
> > information
> > of iemguis is stored in the patch file has changed. The number
> > representing 6-bit-per-chann
Here's some more background info:
If [readsf~] notices that the read buffer is empty, it doesn't just
output silence, instead it signals the I/O thread and waits until data
is available. This means that the outpout of [readsf~] is always
deterministic!
Now, if you call [1( right after [open(
10 matches
Mail list logo