@aolis said:

@ianupstanderThere was a webcam driver package called Macam that used to be used to get it to work on Mac.It looks like someone has done the work of updating it to a 64bit setup for Catalina.

 As far as I can tell, the Catalina update offers a static library (i.e., a ".a" file) that one needs to compile into a program and use. I don't think it is a generalized library (i.e., a dylib file) that you can install somewhere and get macOS to recognize those old cameras in general. There is a link to a VUO plugin that uses this library, which implies a similar plugin could be built for Isadora. (Of course, time allowing... I've got a lot on my plate as usual.)

Best Wishes,
Mark

@dusx I didn't know that...thanks.

@barneybroomer

Isadora v3.1.1 solves this issue. You can download it now from the Get It page.

Best Wishes,
Mark

@notdoc

Isadora v3.1.1 solves this issue. You can download it now from the Get It page.

Best Wishes,
Mark

@elena said:

OK it works

 Music to my ears. ;-)

Thanks @mark can confirm 3.1.1 has fixed this problem, many thanks for your speedy resolution

@luc

The crash actor has nothing to do with the automatic restart. That actor was only to test the restart function if Isadora crashes. With that method learned in Berlin Isadora only restarts when it crashes not when you close it normal. 
First go to the system settings of your Mac and look if there is an apple script in the "login items" that starts up automatically when you restart your computer. If yes remove it.
If this doesn't help go to "users/shared/" and look if you have a folder called "KeepIzzyUp" if yes create a new folder called "disable" and put the apple script in to that folder. Restart your computer. 

Best Michel

@mark Hi Mark thanks for your reply and clarification. Yes indeed, I was attempting to open these on Mac Mini M1. Everything was working fine on an Intel Mac. 

I have already opened a support ticket, so please ignore. 

Isadora continues to amaze me! Huge thanks to you and the team for all your hard work. Best wishes Simon

@elena said:

did download the latest version of RTMP for win10 and I only get to load in my patch the ALPHA version of it, which is not editable for some reasons.

Just so you understand: this is a complex actor that uses code we licensed from a third-party (i.e., we didn't write it). While we have tested it on our end and are satisfied that it is ready for release, it is a very complex actor – it is highly unlikely that we have tested _every_ possible configuration of the bit rates and other settings. Once our dear users have given us a good amount of feedback (hopefully a lot of successes) we'll remove the ALPHA from the name. The word ALPHA is there to let you know it's a really fresh module and you should keep your eyes open for issues.

Make sense?

Best Wishes,
Mark

@eamon and All,

So I worked with Eamon today via Team Viewer to address his issue and we got everything working. Mostly, the issue seemed be related to the fact he had scaled the two 4K displays (LG Televisions actually) to 50% using the Displays System Preference. (Eamon's instinct here was a good one: I don't have 4K content, so let's save some bandwidth.)

But, there were several other anomy'salies that were in macOS itself, e.g., the System Profiler reported the resolution of one of the displays to be 7680 x 4320, even that would be an 8K display not a 4K one; this finding was especially strange since two two displays were exactly the same make and model, and certainly do not offer an 8K resolution.

Our action item will be to double-check that using the scaling to something other than 100% will cause Isadora to do something wrong. But right now, I do not feel this is some widespread issue that others will face, especially Ince most users would not

Thanks to Eamon for getting me access to his machine and for standing by as I went through this process remotely.

Best Wishes,
Mark

@josharoo4

Hi there Josh, 

Let us know or your issue was resolved, if not please submit a Technical support ticket by using the following form.

https://support.troikatronix.c...

@gaspar

Hi there! 

Please submit a technical support ticket by using the following form;

https://support.troikatronix.c...

If you have dedicated Nvidia drivers, you can also force Isadora to use the dedicated Graphics card. More information can be found in our KB Article

@mark

I thought so! 

Thanks so much for clearing this up for me everyone, and for the tip about the User Actor. 

Can't wait to try it on my new laptop!

@andielloyd said:

I don't really know where place those limiters to get them to stop this specific issue?

 If you can email me your Isadora file, I can take a quick look and suggest where in the data flow you might need the actors to filter the data.
I will PM you with my email.

@dillthekraut
I believe the issue related to a mix of codecs. One was h265 (not supported) as well as heavy use of different mp4/h264 varieties which were being used for non standard playback. H264 doesn't like speed changes (non 1 speeds) and it doesn't perform well with start and end time changes. For these types of video adjustments a codec that is compressed frame by frame is recommended (Hap, Prores). H264 is compress in frame groupings, and requires loading multiple frame to decompress 1. This makes reverse playback a real problem, as well as trimming (start/end times)

@mockej

This is a know issue with capture from Black Magic devices. Your workaround is the recommended method at this time, and doesn't introduce much overhead or quality loss.

We hope to have this issue fixed in an upcoming release.

@mark many apologies for this extremely late response.  I got caught up in tech and then no longer had access to the systems where i was running into this.

Current tests with Mojave and the latest NDI Watcher 1.0.1 -

NDI 4 Watcher 1.0.1 on Mojave Isadora 3.0.8 reports correct resolution

NDI 5 Watcher 1.0.1 on Mojave Isadora 3.1.1 reports correct resolution

in brief test, all is working as hoped!

thanks so much

@jfg and @juriaan

WOW... Fantastic...
Fast and efficient response.
Problem solved.

Thank you very much.

@lpmode

Definitely open a ticket. And make sure to tell us if you're on Mac or PC.

In addition, it would be great if you could update your signature line as instructed here.

This helps us to help you faster on the forum.

Best Wishes,
Mar

@emtv

I just ran a few tests with my USB3 BM intensity shuttle.

Using a HDMI output from a mac mini (set to 30p and later 60i)
I am able to capture at the specified resolution from Live Capture, and have the HDMI output work as a Monitor feed (I had issues with some of my displays not supporting 60i)
I am able to output my stage to the Device HDMI output.

I can not:
- switch the output between being a Stage Output, and an Input monitor (requires stopping live capture, and toggling the checkbox on Stage Setup. So can be done manually)

The issue of the device being added on newlines, and with the offline suffix, I believe to be an issue that was fixed some time ago. (I remember testing this).
I would recommend updating your version of Isadora. (you list Isadora 3.0.7)

NOTE: your computer spec is very similar to my own, so I don't believe that will be a factor.