hcgilje

Forum Replies Created

Viewing 20 posts - 1 through 20 (of 25 total)
1 2
  • Author
    Posts
  • April 19, 2013 at 8:48 am in reply to: jit.gl.syphonclient #21301
    hcgilje
    Participant

    nevermind, it was quite easy to make a workaround, but maybe change the helpfile text?

    December 4, 2012 at 6:53 am in reply to: processing problem: syphonservers with appname #11173
    hcgilje
    Participant

    thanks for the quick answer!
    you´re right, it works fine when I use the appname instead of the servername.

    October 17, 2012 at 6:03 am in reply to: unstable syphon client in max #6384
    hcgilje
    Participant

    Not sure if this is 100% related, but I think this is related to an annoying bug in max 6.0.7. At least I have run into this issue quite often lately, also without syphon being used, where I get a stream of error messages before it crashes:
    jit.gl.fbo: unsupported framebuffer format!
    jit.gl.fbo: error initializing capture

    I reported this to the max beta list two weeks ago and they are working on a fix for this.

    • This reply was modified 8 years, 5 months ago by hcgilje.
    July 31, 2012 at 11:07 am in reply to: unstable syphon client in max #6252
    hcgilje
    Participant

    I am running the latest beta (when I do get info on the max objects it says version 5.1.1, but it´s from the public beta 2 r2 dmg).
    I am able to reproduce quite regularly just using the built in syphonclient helpfile and syphonserver helpfile and the simple server app to keep it simple.
    When I switch syphon source in the max-syphonclient between the max-syphonserver and the simpleserver app, at some point one of the sources turn black, and I get the error messages reported earlier. Sometimes when I then switch back to the other source it works again, sometimes not. The only way to get it to work again is to quit max and open it again.

    • This reply was modified 8 years, 7 months ago by hcgilje.
    July 28, 2012 at 10:52 am in reply to: 2 Jitter syphon server issues: upside-down + fullscreen glitch #6226
    hcgilje
    Participant

    In case it is useful for figuring out why jit.gl.syphonserver flips the image when connected to a jit.gl.node, here is a simple patch demonstrating how it behaves when connected to a jit.gl.texture (normal), jit.gl.node (upside down), jit.gl.node-jit-gl.slab (normal). When using the last option on a fullscreen syphon capture the slab seems to have a relatively significant effect on framerate on less powerful graphic cards, so if there could be a fix inside syphonserver that would be great.


    ----------begin_max5_patcher----------
    1235.3oc6Y1rbiiBDG+r8SAkNm0k.zm6oLuD6kslJE1BqPJIPCB6jYlZd2WA
    H43j0FowQA6CSkT1kPXwe9QS2Ms94xEAqEuPaC.+M3eAKV7ykKVXZR2vh9qW
    DTSdYSEo0zs.N8Yw5mBtydKE8EkoYE.BVCfCsuUvUsreP02ChVE12LeWMiWQ
    UlGE70FE6TCsh6a01j56MTq5BXbUvcff0Ddo9a8kfu124FhZyiLd4CR5Fks+
    nDX2vBhy0eFkn+DEtJ7vOgUXzc2b4uhNV0bRsYDC9hjQpBz23WKWp+3tOFgp
    DjBq3+nHBdNDYd7NgRNVCBbn9yjPWPANuPYintlpWAeGU1JE0fmXpUkU.tnf
    B1yHf1JxLfogttUVt1b8ge7IHSbT7JHJElm1gDTjlLPLxoUSz0gPWSvDlY.C
    L2IXv9GL5F2IulrAlilBaP9gMhsaulrH0.AbjSTLydXjjBlnTJ10DLCtRc5F
    MFYle8SSnYSQRxoml33fCOHY2jTQkOP4j0UziQLSQqGF8g1FVzh5udOoZG8X
    QWvZ0OmBqn5zP++fuNeQsZel0M8A3eGqon4D037ClU3XTeH83yaVggdIZt0u
    yptHUq+cPC5jnAcNzzMJOTV8vAuai.qzt7bN.KjEVot1Chx8Ir1yJnhlJBmB
    tWII71sBYcm7aoJ.5i6txIEqIJI6kwIX3qDDk1mfD1IBS8p812adTvaox8TI
    nah1rSAt2dodn6hC1p931iyvV0rXCzhhcliI5OleuM+7znUowQ37XczyjoX9
    4UDNaoYMWd7NFXnLSf3TmYsihmWdUSaaIkz+GvjTRw0ZiHJIeENsOULq4CNd
    HSkSFyLbdgh1Zo4YFuP7bvLXSLpU.NLdUxayCO6vQbOoimz4dsFTH9AUtpVr
    +pspmkbXqPmaX8z2dZ+yspCS7lqiuozjg043kTPZTyQchla2svXi6VHxo6VX
    nOc2ZJHxPT9Mcfqyk3mZM1Ng22QyXBl9ZFS1S7ASbdvu4Nh0t50T4mnA0wEd
    zIIrmFDZy61Yw0PYNXfqiKdA7gnTxcrKgOZyfGdlUndT2ZR1w89C6tBZrQvP
    CmfgVbAOyttSGz9enxBBmLbO8D0zdorKtyEF1ZaSa4kQq4JXlsh08G9vFFSG
    89jbIyadirQyO3LZaKg.ff6aDs5EOPTX3mHyFp4+HY8Xq4jMqYjyxvk4Su3R
    Ju3vo0t1TJxxEbevtXWa6vN20cAbRIJKqnyQ44F6s+fQG4K195NvmwVHetc3
    d12P15t+nRRK8SLB9fQvv21waBnxF8JMwkAQ5baPbFT8stkAo.D+IlJ8nQy6
    whc+RhSrjLUrX9wAUL96ekqlwW29aYUqXmbyfh6eSkfWkPAsUw3DESvOpO4u
    oOOxJJn7iKq7wUM9zl2SUMvInlHuoF8HgFQM5hw6Q4.GQN5Sf4I4jOg0J+ol
    zInFrWUC5lRMiZ3D5M4jLgkpTuol2sA9LqUP+omo3CTWlaeomvonG+Y8fmhb
    x7lbP4S07A6G8jMQ2xP+HmIu65FROH+s6BMU7ftYjCJ+lhNnTuJmwhihhusj
    i+LkgI2VAJfSYqt+BT.mRbTOZ8LI8.uzMW1ykRZZ1Sks8OSiT5Ns9SBSQUSt
    ybIiauz7DCjz8rg9mtT+z90x+C7bm9TL
    -----------end_max5_patcher-----------

    • This reply was modified 8 years, 7 months ago by hcgilje.
    • This reply was modified 8 years, 7 months ago by hcgilje.
    November 22, 2011 at 3:17 am in reply to: syphon max alpha #4957
    hcgilje
    Participant

    blendmode 1 7 solves the issue when working with a single layer, but it breaks everything else when working with multiple layers, transparency and alpha masks, so I guess there is a slight incompatibility when combining syphon sources with alpha masks and jitter alpha.

    To illustrate, I made two layers. Bottom layer is just a solid red, top layer is set to 50% opacity with a circular alpha mask.

    November 21, 2011 at 3:42 pm in reply to: syphon max alpha #4954
    hcgilje
    Participant

    I am still stuck in 10.6 and max 5, yes, I pride myself in not being an early adopter 🙂
    And it looks the same with either the geforce 9400 or 9600 graphic cards.

    If I clear it with 0,0,0,0 I get the typical jitter trail effect, so that wouldn