Solved! I updated to Monterrey (not Mohave sry) and its working! Yay world! 

@dillthekraut

Thank you, that all makes sense.
Making progress :-)

@Fred @Juriaan Thanks for your suggestions. I'm finding a way through...

Will post results and workings when I've got the final thing going.

Much appreciated everyone.

@dusx Great thanks Ryan !

@nic

Can you tell use the make and model that didn't work for you? It may help others in the future, and will allow us to expand our testing.

Did you ever figure this out @Aolis ? I am looking for something similar! 

@landschrap said:

The msg:string={00-FF} parsing pattern is nearly always my starting point when I am trying to receive Serial text data.

This parsing pattern will output a string made up of any of the Hex values 00 through FF (all of them). This works often to get you started since you can see the full message received eaisly.

You will want to watch your incoming serial data in the Monitor window to see how this output matches with the input.

@faebske

Welcome to the Isadora forum!

A couple of things: firstly please have a look here:

https://community.troikatronix...

Secondly, did you see this article which is linked to in the release notes?

I think the article needs a little update for Windows 11 and perhaps a link to the AMD instructions, but that's basically the way to do it.

@callie

Have you tried my DMX input user actor (32 channels)?
You can get it here: TROIKATRONIX : ISADORA - DX – DMX 32 Channel Receiver – Enttec Compatible

It connects and works much like the DMX out actor. Instructions are on the download page.

@jfg said:

<p>@skulpture</p><p>I already use EDID and this is not a problem of unreliability of the order. I just wish that when the System Preferences for a device give the number 1, I would also find in Isadora #1 and not #4. It also seems that monitors are numbered before projectors even if the projectors were connected first. </p> <p>It would also be helpful if the device (monitors, projector or internal display) with the system (primary) was numbered last in the chain, so we would have the chance to have stage 1 on device 1 and not basically on 2.</p> <p>I would also like the list of displays in Stage setup to show the names of the devices , like the ‘Display Overview’. If all devices have the same resolution it is not easy to know which one is which, even more so that they do not show the same number as in the system prefs.</p><img src="/assets/uploads/files/1727267685655-bildschirmfoto-2024-09-25-um-14.22.31.jpg" /><p>Best regards, </p><p>Jean-François </p>

 Ah I see - slightly misunderstood. I will leave my original post for others as it might be useful for future readers.

@mark

First off -> signature updated. Thanks for the reminder!

Second, thanks for the help and information -> we did verify all configuration was unchanged between I3 and I4. I managed to solve it yesterday after checking Windows Firewall settings. During the upgrade, they had gotten messed up and weren't allowing any incoming data on private networks. After enabling data transmission, OSC resumed complete functionality. Apologies for the raised issue!

@reload2024

Can you open a support ticket (link in my signature)? 

I will want to reproduce the issue on one of my test systems, and may need access to you show file, as well as your system specifications.

@gertjanb said:

Are there ways to know what might brake when upgrading?

 I think the release notes are probably the best documentation of any breaking changes. In the case of Isadora 2 to 3, we had the shift to 64bit which killed some 32bit fx (thinking about FFGL 32bit here), these where really beyond our control. We don't get rid of things as we add updated/replacement features, instead we take the approach of making things 'classic' and phasing them out so that projects have an easier update path. 

Some search features would be helpful. I would love to get a report for any given actor that provides the breadcrumb path to any instance of an actor. These are things we have talked about and I hope we can get into the software.

@dusx said:

msg:string={00-FF}

 Thnx, that works! Now i can cut the last part of it. And  compare it! So different tag's will do different things!

Also tried to use: 'value1 : string =  EOL' in serial in watcher - binary. It gives me some text output. But different with the msg len set on 4 or 8!

@joshuawg

These systems shouldn't have changed between Isadora 3 and Isadora 4.

The first thing I would look at is drive health. 

Please open a support ticket and I can see if I can reproduce the issue with your help.

Hi everyone! I'm trying out my new MacBook Pro M3 Pro Sonoma

Playing with the speed of the movie player in interactive mode I find that it doesn't play an mp3 audio file smoothly compared to my old MacBook Pro 2015 which has the possibility of using the Quick Time playback engine.
Is there any way to improve this? any settings? maybe a specific codec?
Thanks a lot
Maxi

@reload2024

Hi,

You can find a Sharpen actor in the glsl set provided by TroikaTronix: https://troikatronix.com/add-ons/tt-glsl-shaders-for-isadora-2-3/

These glsl modules are now an optional download when you install a new instance of the Isadora app.

Further to @mark_m advice about previews. You can also monitor any video output through the controls. The Monitor is a control panel object that can be resized in the control pane. 

Best wishes

Russell

I use both a older Behringer UMC404 (which is 4 channels in and out) and the MOTU Ultralite MK5 which is has an easy analog 8 in and 10 out. Both work great with Isadora.

@tingkumajique said:

also wondering why the text output from Isadora looks a little jaggy and not clean even when the resolution is set to 1080P

 To add to Marks thoughts, do remember that in the screen captures shown the Preview Windows are scaled down from the target size. Text will look cleanest when rendered to the full stage output.

@dusx I just tested it and crashed again after set ON on the broadcast input. BUT if I turn On the broadcast input without the video input receiving any source and then I the conect to the video source it doesnt crash but still doesnt transmit...strange

Maybe someone in the forum with a Macbook Pro M3 (2023) with Sonoma who can confirm ? Or a "check step" to rule out possible problems...

(thanks for the Rosetta tip...shoud I leave always checked that option ? or only when Im going to use the Kinect?) 

Best,

Maxi RIL