Le 16/09/2016 à 10:08, Roman Haefeli a écrit :
> On Thu, 2016-09-15 at 23:52 +0200, Jack wrote:
>> Le 15/09/2016 à 20:58, Roman Haefeli a écrit :
>>>
>>> On Don, 2016-09-15 at 18:45 +0200, Jack wrote:
>>>>
>>>> Hello Roman,
>>>>
>>>> First, you should try with [text3d] instead of [text2d], on my
>>>> configuration, [text3d] is faster.
>>> You right about [text3d] being faster. It's even a lot faster, but
>>> also
>>> dead ugly. I prefer the rendering result of [text2d]. I don't
>>> understand what the difference between those is, actually. Does
>>> [text3d] render the text onto a texture on a plane? Does [text2d]
>>> render the font as 3d vector?
>> With the default settings, [text3d] (if i remember right) create a
>> texture for anti aliasing. So you can change anti aliasing with the
>> message "alias". If you send [alias 0(, you work with vertices (if i
>> am
>> right here again), then you can ask to your driver to use anti-
>> aliasing,
>> or not.
> 
> I'll look into anti-aliasing settings. Thanks.
> 
> 
>>>
>>>
>>>>
>>>> About single buffer mode.
>>>> Did you send à [0( to the [gemhead] at startup ?
>>> Yes.
>>>
>>>>
>>>> Look at the patch attached, everything is ok in 0 logical time.
>>>> On my side, it is strange that i need to send 2 [bang(s to
>>>> [gemwin]
>>>> to
>>>> clear the buffer.
>>> Your patch works for me, too, as you probably intended it to work.
>>> What
>>> I want is actually the buffer to be cleared before each step, so
>>> that
>>> the result looks similar to double buffer mode, where only one word
>>> appears at the time.
>>>
>>> See attached patch. I get only a blank screen and occasionally a
>>> single
>>> word appearing. It works somewhat more reliable when I insert a
>>> [delay
>>> 50] between [t b b b] and [gemhead].
>> OK. see patch attached. It seems to work in 0 logical time.
>> The 'bang' to clear the buffer is sent just after the 'bang' sent to
>> gemhead (it is weird, and i can't remember if the behavior was like
>> this
>> before ?). 
> 
> Ah.. it didn't occur to me to try this. Thanks!
> 
>> So yes, it could be a bug because now to clear the buffer,
>> you need to :
>> 1) send a bang to gemwin
>> 2) send a bang to gemhead
> 
> You mean the reversed order, right?

What i expected to clear the buffer is to send a bang to gemwin (and
only that). I just verified with the GEM: ver: 0.93.git 374f713, and it
worked like that before.
++

Jack


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


Attachment: signature.asc
Description: OpenPGP digital signature

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

Reply via email to