@Fred Thanks for your reply! I have no doubt about that, but maybe the fault is somewhere else. @DusX proposed, there might be "a potential conflict between your media framerates, capture devices framerate, and your output displays refresh rates" or maybe the problem is something different. However, I'm still hoping there would be a solution.

I've had mad trouble with transparency in Isadora on Mojave (I updated back in September, knowing I wouldn't need it until March by which point I would have migrated to Izzy3).

I narrowed my issues down to the zoomer actor pumping out premultiplied video, even when I was sending it straight alpha.

Adding an alpha tool actor in the patch (with action: premult) immediately after the zoomer fixed it for me.

@dusx

We gave up on Isadora for now. The installation opens tomorrow so we switched over to resolume. I'm off work until Wednesday. Once this and my other event close out I'll do a small test setup in my office to hopefully get Isadora working. Once I have it setup in my office I'll try completely disabling the audio hardware.

@julio_parente

Please file a bug report using the link in my signature if you haven't already.

Hello,

Thank you for your quick respons

The codec was Apple ProRes 422.

The residual sound I got was not from the scene A ( in the case of passing from scene A to scene B ) but from a video not activate  at first in the scene B . The movie player was initialized off.  I'll write a report ticket .

The funny think with the end trigger was that even  that the video didn't reach 100% but 99.9xxx % ,the end trigger was correct. The movie player was still  activ after the end of the video. Maybe the isssue of the sound came from that the movie player was still active when I passe to the next scene .

Thank you and have a nice day

alex

@dusx cool, I did not even try that- of course mark thought of almost everything.

So, this is the scene with the user actor.. Again it doesn't happen every time

trajectoryV13strobeTunner.izz

Hi there, Isadora doesn't like your way of sending data.. I would personally go for the following code :

void osc_doors(int i, int doorID) { OSCMessage msg("doors/" + doorID); if(debug == true) Serial.print("/doors"); if(debug == true) Serial.print(doorID); if(debug == true) Serial.print(","); if(debug == true) Serial.println(i); msg.add(i); Udp.beginPacket(outIp, outPort); msg.send(Udp); // send the bytes to the SLIP stream Udp.endPacket(); // mark the end of the OSC Packet msg.empty(); // free space occupied by message }

This will create the following :

Adress :

/doors/1

With value : i

Thanks for the input everyone, it turned out to be a problem the Isadora video preferences. Got it up and working 👍

@Woland 

Done

@laurentr Agreed with you, i had the same issue, you need pro version , + i have more and more crashes on IOS latest versions of epoc cam, it seems deveveloppement has stoped unfortunately... i suggest using epoc cam multicam without updating ios version for more safety

if you output 2 virtual stages first you might bypass this issue. (Bug fixed in Isadora 3)

@malibu

If you're willing to post your patch I can take a look. It may be that your approach is not optimal.

Best wishes,

Woland

@jjhp3

Just for your attention, especially because you use quite an old computer: https://community.troikatronix...

Best Michel

Hi there,

The best thing that you can do is make a support request at https://support.troikatronix.c...

The Isadora staff will help you further with your question.

With kind regards,

Juriaan

@eight your second gpu is compute only, so you won't see much there, that leaves one 3gb card, pretty easy to max out.

@michel said:

one scene only for the livecam feed and use the activate scene actor to always have the livecam scene active.

I just built an example file demonstrating this for someone else. Here's a gif demonstrating how to use it. (The stuttering you see in this is because the gif has a low FPS.)

 >>EXAMPLE FILE<<

@maximortal

I guess we have a slightly newer beta (2.9b16) in the team.

Best Michel

thanks for the info!

@Juriaan 

Thanks for help advice. Have contacted support 

Re this issue 

Arthur