MartinusMagneson's picture

Magneson (@MartinusMagneson)

Groups

    Compositions

    MartinusMagneson's picture

    Mini recorder seems to work fine inputting HDMI, tackles loss and return of HDMI signal without restarting the comp, but not the box loosing connection.

    Didn't get SDI input to work in any config (only tried a couple). Pure SDI signal from Resolume via BM Decklink something something.

    MartinusMagneson's picture

    Thank you! I've tried a bit, but think I was stumbling across unrelated stupidity on my end. The instanceFini which I completely forgot about threw me for a loop for some time. Got it to work-ish, but not production ready for the test I had in mind.

    MartinusMagneson's picture

    I'll try when I get the chance! Maybe tuesday if it isn't too late. We have the ultra studio mini rec for the macs.

    MartinusMagneson's picture
    @MartinusMagneson posted a new Question, “Instance data explanation

    Hi! Diving ever deeper down the rabbit hole.

    I've been working with making a LED wall specific node set. One part of this I'm trying out is splitting images, crop them and shove them into layers. As crop isn't a native function, but a shader, I've been trying to merge a couple nodes into one. However, by making a function to crop rather than stuffing the shader part in the main node, I've stumbled across something I have dreaded a bit to get to (understand); the node instance data/event thingy.

    MartinusMagneson's picture

    I would guess it's slower since you're running multiple nodes/processes serially-but-also-paralell-kinda(?) inside a Process List node. In comparison the calculate list would only run through its calculations without having to consider the other nodes and synchronisation before outputting a value to the item.

    If it is an issue with one of the calculations taking a longer time than the rest, you can possibly try to remove one of the calculations at a time. If it improves efficiency you can take the worst culprit and split it to see if it helps.

    Addressing value.x/y/z/w inside both the calculate and the calculate list node would be great though.

    Pages