Hi there all,

It seems when I create a local network, that doesn't has Internet Access that my Isadora Address is being put at 127.0.0.1. Still Isadora OSC commands are still being received at 10.0.0.2

Seems like a display bug in the Preference window.

Izzy version 2.6.1 (Windows 10, USB version)
With kind regards,

Juriaan

Try seeing if converting your video files to Hap (or Hap alpha) has any effect.

AVF.Batch.Converter.app.zip

SOLVED

I went on a long overdue uninstall binge and found the issue finally. 

LAV Filters - ffmpeg based DirectShow Splitter and Decode

Everything is working as it should now. I had the LAV filters installed for some ffmpeg work I was doing. I don;t think I need them for anything at the moment, but will flag this for the future.

- J

@juriaan said:

why aren't you using Artnet

 We did have a discussion about using Artnet, but as it turns out  we are sending the rgb values of the first and last led of each strand to the nodeMCU (9 led strands x 2). The code on the nodeMCU then produces an interpolation across the rest of the leds in each strand. So there is an efficiency with only providing parameters for 18 leds (they are linked to audio frequency analysis). Each strand is 9 led long and they have been wired to produce 9 x strands each 900mm long that will be sewn into a dancers layered tulle costume.

When we tested the OSC multi transmit starting with 54 values everything was working fine except for the missing values. We tried sending less in increments and it appeared that 49 was our maximum.

We have another set of wearable controllers that send accelerometer data back to Isadora also using OSC.

Best wishes

Bonemap

Deleting old prefs helped. Thanks very much for that tip.

Matthias

@eight I have determined this to be an issue with your Patch, not Isadora. Please see the edited file that I sent along yesterday, as I optimized it.

@kikko said:

Also I used Isadora 1.3.1 until 2 days ago on my Mac with High Sierra installed... so there's no reason why now it doesn't work properly.

For comparison, I couldn't even get this version of Isadora to open on El Capitan. There are many reasons why it wouldn't work properly, but none of them are documented because this is a depreciated version of the software that is no longer supported or recommended. I highly recommend upgrading to Isadora 2 in order to solve this issue.

@aled2305

Just tested on Mac with USB Version of Isadora. You are experiencing that issue because Adobe Creative Cloud is open. Close Adobe Creative Cloud (as recommended by the popup) and Isadora will open the file as expected.

Best wishes,

Woland

On Mac one can copy paste the Hex value from color picker to color picker (or keep the hex code pasted in a comment actor for easy access).

@dbini yeah, that's what I expected, sort of a discrepency in resolutions ( and probabley the resolutions changed after the mapping was setup). 

Thanks for digging in.

 2 sets of eyes are clearly better than 1.

Glad you found the issue.

@knowtheatre

Did you already submit a bug report for this already?

We'd like to nail down the cause and fix it.

Best wishes,

Woland

@ZALTProductions 

Did you submit a support ticket for this issue? We'd love to help you try to solve it.

Also, having looked up this error in our system, your error might be caused by overuse of the Preload Scene and/Picture Preload actors. Try removing any Preload Scene and Picture Preload actors from your project and see if that makes a difference.

Best wishes,

Woland

This issue was solved by doing a full delete + restore and reinstall of the operating system and after that the newly installed Isadora functioned just fine.

@mc_monte Can you please take a look at this on High Sierra?

@juriaan

Either that or inspecting the actual User Actor/Macro itself in the global folder I'd think

@fr4b3lo said:

I lost one of my remaining registration

 We'd be happy to reset that for you if you create a support ticket with our Sales/Orders department. :)

@sommerdi said:

I was testing some more cameras and found that all with apple driver are working and i tried to run the BM with apple driver and this solved this issue.Maybe this helps although for other setups

 Thanks! I'm sure this will be super helpful for other folks on the forum.

hey, cheers, from now on I'll go straight to a new line first.