@dodioflo

You can look at remote kvm control software. TeamViewer is one that is used widely and works well.

https://www.teamviewer.com/en/videos/

Remote kvm (keyboard, video, mouse) is also built in to some operating systems. Often called ‘screen sharing’. 

I have used the built in option in Mac OS to run remote Isadora patches. I have also used the  teamviewer software to work with clients remotely. It is also called Remote Desktop.

The only issue really is latency and dropping network connectivity. At this time with an exponential increase in network usage due to home isolation/working from home all over the world, latency and network quality is an issue. You will also want to ensure that your network ports are secure from potential hacking, which is also increasing atm. 

There are a number of different software that offer these Remote Desktop options.

Best wishes

Russell

@mark said:

Get the new JSON Parser Actor

 Hi Mark,

That is remarkable - I am spinning!! 

Best wishes

Russell

Thanks!!! I'll have a look on it

Have anybody ever used Moxa RS232 Servers to control shutter programming using Isadora?  I use them when I'm using Watchout, because there is a more robust set of settings you can change via RS-232 with Pansonic projectors than with straight TCP/IP control... specifically you can change the Shutter Open / Shutter Closed speed on the fly.

In Watchout you send a text string containing the RS232 control commands to the Moxa box via a TCP send message, and then the MOXA box converts the TCP string to a serial command for the projector.  I've tried using the TCP Stream Control actor to open a connection to the MOXA box, and then sending the string command through that stream using the TCP Send Data actor, but to no avail.

Has anybody every had any success with this?

@yjk said:

@craigalfredson Hi Craig, I am trying to have ION trigger Isadora for a show. Could you share the actors? 

Have a look at this thread for how to use OSC to do this. I have a basic setup and @Juriaan posted a patch that's probably better than my basic one.

I've also posted my MIDI Show Control System that I've used for this in the past (if you want to go the MIDI route): https://community.troikatronix.com/topic/5543/midi-show-control-scene-navigation-cueing-system

Best wishes,

Woland

Thank you so much @bonemap You are a lifesaver. I got this working in rehearsal and I'm about to put this tracking data to use!

Good to know.  I'm curious if it will work on an iMac 2017.  I'm thinking no because it only has 2 TB3 ports.  I actually only need 3 video outputs, so I'm hoping I can use one Sonnet and one "regular" USB-C to HDMI adapter.  I received the Sonnet today, so hopefully I can test it soon.

@mark said:

rely on Apple and Microsoft to adopt in the operating system

 Ah! OK it’s a watch this space...

Hey guys.  Back to troubleshooting this problem. I have disabled all extra network cards and double checked IP address.  Still nothing....

@michel said:

29da34-typewriter.izz

 really nice patch, thank michel!

Sorry, but I can't get this clear.

When I buy an affordable standard touchscreen like fi. the ASUS VT168H would it be possible to read the mouse values with the mouse watcher? And what will happen then if the screen is sensitive for 10 points, which the mouse watcher isn't (am I right?). In other words: will the USB plug form the monitor behave exactly like an USB-mouse?

By the way, I am on macbook pro / Mac Mojave

Thanks

Peter

Hi there, 

What version of Isadora are you using ?

@jandraka said:

slider is not very accurate

You can also:

1. Click on the green number itself and drag up and down to adjust the number

2. Hold Shift and click and drag up and down to adjust the number with greater precision

3. For the most precision, simply click on the green number and type in the value you want.

Thanks for all your explanations! I indeed see all four messages pop up at the same time in the monitor window, each carrying a different value (1,2,3,4). Splitting the messages up per DMX head is an option, that but makes it impossible to write up one single pattern in TidalCycles that turns on multiple heads simultaneously.

The solution to let the OSC monitor in Isadora output a buffer of all the values it has received during the processing cycle sounds like one that could work. The behavior that I expected as a user when I was patching things up, was for Isadora to run a new processing cycle for each OSC message that comes in (as in, event-based). I can imagine the latter option is quite intrusive on Isadora's current architecture.

For the piece I'm working on right now during Oulu Dance Hack it turns out we only want to run sequential patterns. But I can imagine I'd want to light up an array of lights simultaneously using TidalCycles patterns in a future project 🙂

@paispais

Mac or PC?

If there's not something out there already, I'd suggest creating an application that monitors your downloads somehow and sends that information over OSC to an editable OSC address.

@gunther

Thank you for your efforts. This may work for now, but the numbers you shared are not actually correct because of a bug in the Keyboard Watcher that I am in the process of fixing today. Your system above will work for Isadora 3.0.2 through 3.0.6 but it will break as soon as I fix the bug and we release Isadora 3.0.7.

Details: Because we switched all character input values to Unicode for Isadora 3, the constants used to represent special keys (arrow keys, escape, etc.) had to change. However, the output range of the Keyboard Watcher not properly upgraded from the eight-bit value (0-255) used by Isadora 2 to the required sixteen-bit value (0-65535) needed to represent Unicode characters in Isadora 3. So, the numbers you are getting is because the high 8 bits of the actual value is getting chopped off which is not at all correct.

Your workaround does in fact work, but it will stop working as soon as Isadora 3.0.7 comes out, which will contain the actual fix for the problem.

This morning I completed the hard part: extending the range and making a major improvement: you can now simply enter the name of the key you want and it will show up that way in the Keyboard Watcher. See below.

The other part which I will do now is to to automatically update those old constants to new values when importing a patch created in 2.6.1 or before. This will ensure that Isadora 2.6.1 patches continue to work.

If you need this functionality urgently, please to join the beta program by submitting a ticket. I will be getting 3.0.7b1, which will have these fixes, to relatively soon.

Best Wishes,
Mark

@mark 

Ok !!

now it is much clearer to me.

I said that there was a way to set the values, no, because it almost seemed like they were set up by magic ... ahahhaa !!!

Thank you very much Mark

best wishes

Giampiero

Just to shout out a thank you especially to you @Woland I've finally had some time to play around with your work and figured out a way to get MSC messages out using Oynx on a windows machine with loopmidi as a virtual hub. Very cool, this will be useful.

cheers

tim

@mark 

Thanks so much for the update news !!!

so quartz composer from vervione 3.0.3 will return to being able to produce actors for isadora ???

I will definitely consider the 3DS option for the cube.

Regards
See you soon
Giampiero Cinquepalmi

Just want to add to this ticket so that the solution is included.

After investigating the ticket, I found that an actor within the Enttec User Actor was experiencing a bug related to initial value parsing.
This bug is confirmed fixed for the upcoming 3.0.3 release, and the Enttec DMX User Actors I have posted to the Plugins Page are not affected by this issue in the current release.
see: https://troikatronix.com/plugin/dx-dmx-universe-enttec-compatible/