@dusx said:

I found that it only occurred with 'some' hap codecs... so you could try the others, however, recording to Hap isn't recommended as its is rather CPU heavy, and this may be why the speed isn't correct (frames may drop if not compressed in time).

 @callie 

Certainly this is a bug and we will fix it as soon as we can manage. However, it simply comes down to this: compressing a HAP frame generally takes way longer than a the the frame time to accomplish. In other words, if you're running at Isadora at 30fps the frame time is 1/30 = 0.033 seconds. If it takes 0.1 seconds to compress a frame, then 0.1 / 0.33 = approx 3 Isadora frames will pass before the next frame is compressed. Isadora should realize this and insert 3 frames of the same material, but instead it inserts 1 and when it plays back it's too fast. In the end, HAP is not a good codec for real time capture.

That's why @DusX is recommending the Blackmagic codecs, as they take far less time to compress and will thus should give you a proper frame rate when you play back the recording. Try them and let us know here how it works for you.

Best Wishes,
Mark

@mark

If I recall correctly in Notch the execution order of nodes is affected by where they are placed so if what you’re doing requires a specific execution order you need to understand that where the nodes are placed does actually matter.

Dear @Lauri @martin_kemner @msanii and All,

As you already seem to know, this dialog was introduced to warn users that they were running a 32-bit app. This was in preparation for macOS Catalina, which is 64 bit only and will not run any 32 bit app.

After researching this a bit I found out that, for any given app, this warning is shown every 30 days. So that probably explains why you are seeing from time to time.

But the question remains, why is it being shown for a 64 bit app?

I can only guess that the answer lies in the two background applications used on MacOS to play movies -- the 64-bit IzzyMoviePlayer64 which uses AVFoundation, and the 32-bit IzzyMoviePlayer32 which uses QuickTime. When Isadora launches, it launches both of these apps and I suppose that the launch of IzzyMoviePlayer32 triggers the warning.

(While researching this I found a nifty app called Go64 that will identify all of your 32 bit apps so you'll know which ones you need to update for Catalina. It listed Isadora as a 64 bit app -- but of course isn't looking inside the "application package" to find IzzyMoviePlayer32.)

In any case, rest assured that Isadora 3 is in fact optimized for your 64-bit version of macOS. We know the 3.0.2 version crashes under Catalina because it tries to launch IzzyMoviePlayer32... but the 3.0.3 version, which does not attempt to launch IzzyMoviePlayer32, seems to be running well on Catalina so far. (We're continuing to test.)

I hope that answers your questions and lays to rest any concerns.

Best Wishes,
Mark

I've never noticed/experienced this, but I believe I understand what you are describing.

To be sure, I try to reproduce this correctly, please add a couple screen captures. 
Windows Displays dialog (showing placement, numbers) and the Stage Setup blend.

I think this is actually an issue with the Grapher plugin (another thread found a bug with its update rate when used with a square wave..  being drawn as a sine.) 

I think this is probably the same, since the sound drops near instantly. 

Change the sound watcher outputs to graphic mode and increase the size (drag them wide). Then test how the actors outputs display the data, I expect it's very quick. Shouldn't have any added decay.

ticket submitted, thanks!

[A ticket has been submitted and this is being handled there.]

@dbengali

Please submit a ticket with an example file, repro steps, (and also a gif screen recording would be very helpful). I don't think we need the media.

Link is in my signature.

Best wishes,

Woland

@craigw

@Woland will keep me informed about this. If we can find a way to reproduce the problem, I will fix it as soon as I'm able.

Best Wishes,
Mark

@dusx I get a frame or two, enough to re-identify the blob and interrupt tracking. Thanks for the priority, again it was for students who were confused that the IDs were changing.

@dusx yes it's all the settings in live capture settings. I can make it via work arounds, for teaching it's better to have a straight workflow. This came to my attention when students switched from Mac to PC. I knew it was a bug pre V3, I thought it might have been fixed and broken again.

@wwachalovsky

Note, all files are saved as AVI files. 
Perhaps you need to restart Isadora for your changes to be applied. I have had issue making changes, generally after a failed change (with or without error).

Just an update for everyone: The team is going through our internal beta (3.0.3b7) with Catalina, and things are looking good so far. Of course, there could be a surprise, but I just wanted to let you know we're making good progress on getting ready for the Catalina release.

Best Wishes,
Mark

@dbengali said:

Hi I've got a show with lots of pictures in it (in the thousands), and am finding that the picture player won't allow entering numbers more than 3 digits long for the file index.  Dragging a file into the scene from the media window such that it creates a picture player does bring it in with the correct index. Also, feeding it a number from another actor, like calculator, allows a larger number.  The same behavior seems to be true for the movie player.  Could this character limit on directly typed values be increased?

 I'll log this in our bug sheet

@dusx

Done !

Thank you very much !

Yes are right ... The file was in a file path with a danish letter... with out that it works

Thanks

@jrhooker 

Great to hear you could sort it out.

Best Michel

@jericksondesign said:

Now that we've switched from Classic Video In to the updated actor it's suddenly started jumping scenes.

 That's bizarre. Are you willing to post your patch so we can see? Is the video output or trigger output connected to a Jump actor by accident?

Best Wishes,
Mark

please submit a supoort request. Link in my signature.

This issue will probably need to be reproduced locally to really examine it.

@TimBrunsden 

you are welcome. Needed to figure out what could work for me