funwithstuff's picture

@funwithstuff

Groups

    funwithstuff's picture

    I haven’t done anything special to cause it, just opened the Motion project and left it open (not playing) while working in other apps. At some point I came back to Motion and saw that. I can send my project if that might help?

    funwithstuff's picture

    One issue — I've seen this "plug in is not responding" error a couple of times now. Is this a fluke or something more serious?

    funwithstuff's picture

    With two displays, parameter edit fields can appear on the wrong screen

    Status: 

    Vuo version: 

    Fixed in Vuo version: 

    OS version: 

    • macOS 12

    CPU architecture: 

    Apple Silicon (M1/ARM64)

    How severely does this bug affect you?: 

    ●●○○ — It's annoying but I can work around it.

    Steps causing the bug to occur: 

    1. Open a Vuo composition on the internal display of my MacBook Pro.
    2. Move the composition editor window to a second connected display.
    3. Double-click an input port on a patch to change its value.
    4. The popup that lets me change the value appears on the internal display (at the left edge, closest to the other display) and not next to the patch on the second display.

    Have you found a workaround?: 

    Only to edit the comp on the internal display and use display 2 for the output.

    Other notes: 

    If it helps, I'm on a new MacBook Pro 16" M1 Max with a 4K display connected through a Thunderbolt dock and DisplayPort.

    funwithstuff's picture

    Thanks! I hope people like it. Re FxFactory, I suspect that perhaps since QC has been deprecated for so long (and buggy before then) it wasn't the safest idea to build products using it. I'll definitely ask about Vuo support when FxPlug4 becomes an option, because I have some ideas. FxFactory do have their own effects platform, though, so it might be possible to do something using that.

    Pages