@milky301 said:

I have added value : integer = eol

 You might try:

msg:string={00-FF}

This should at least give you output that looks like what you are seeing in the Monitor Window (use this if your not to view your incoming serial data). This line sets a msg value to all values within the range of Hex values. This is generally my starring point.

@milky301 said:

if anyone can help with understand how the serial in watcher works

 If anyone can, it's probably @DusX so, if you're not going the Arduino route, he can probably share some wisdom about the Serial In Watcher - Binary actor.

@milky301

I'd suggest taking a look at the Arduino Firmata actor as it may be easier to work with than the Serial In Watcher - Binary actor.

If you right-click the Arduino Firmata actor and select the top option "Show Actor Help In Browser" you get a description of what all the inputs and outputs do.

The actor is included in Isadora 4 by default, but if you grab the download from the Add-Ons Page, I think the readme document might have some other helpful hints/resources.

Additionally, the ever-magnificent @bonemap was kind enough to post a detailed setup explanation on the forum here: https://community.troikatronix.com/topic/7643/arduino-firmata-sensor-setup?_=1739300021645

Thanks :)

Hello I am wounding if anyone can help with understand how the serial in watcher works. 

I am currently working on a university project, and I have been given the HC-SR04 Ultrasonic sensor to create an interactive project. 

I know nothing about coding however I have found this site user full to code the Arduino Getting Started with the HC-SR04 Ultrasonic sensor | Arduino Project Hub.  

I now am struggling to understand how this sensor works with Isadora; I have set up the port and have data coming in. In the serial in watcher, I have added value : integer = eol this is the part I really don't understand.  

When in Arduino software the distance seems to be accurate but then looking at the serial in water the value is jumping around, and this is the part I am stuck on.

If anyone could help it would be much appreciated :) 

@postl

I just turned this into an Add-On: https://troikatronix.com/add-ons/auto-re-launch-isadora-macos-applescript-for-installations/

It's basically the exact same as what I have here but I also provided the link to my macOS Isadora Production Computer Setup Guide

@woland

Works! Thank you again.

@woland
Hi L - I think I've worked it out. I had made a wrong assumption about the Screen Capture actor. I thought that you could select a display, and then select from the window list on that display. Now I realise that the window list overrides the display selection. My problem is that the zoom window that is pinned to the second monitor doesn't have a name. So I solved this by doing the opposite of your advice and using the display select with the window list set to 'none'. : )

@dbini

I just tried dual monitors with Zoom on Windows 10 with my desktop that has three displays hooked up and had no issues in Isadora 4  with the Screen Capture actor's the 'display input' (goes between my three displays no problem) nor its 'window list' input (the second monitor Zoom window is named "Zoom Workplace" for me).

Maybe I'm misunderstanding, but are you selecting "Zoom" in the 'window select' and expecting that changing the 'display' input will change to the Zoom window on the other display? If so, that's not how those inputs work. The 'display' input and the 'window select' input are independent.

@dbini said:

but it was difficult to select that screen in the Screen Capture actor's window list.

 Can you describe the problem with the window list in more detail? Because personally I'd enable CPU mode and use the window list instead of doing display capture.