@jlarsen

If create a support ticket via the link in my signature, send us your Isadora Patch, and tell us the sequence of cues that were going wacky, we can have a look and make sure that it's not something strange in the Isadora Patch itself.

Best wishes,

Woland

Thanks a lot.

That solved the problem.

Thank you again for the quick response!!!

OK I GET THE PRIZE FOR BEING SLOW...

I forgot that since Sierra there is also the System Prefs option to hide the menu bar in the General tab. Rusty... what can I say!! LOL

I am running a Trashcan with 6 HDMI outputs. In my case it worked only with the  MDP2HDSW from StarTech. Belkins not and even not Apple ones. SwitchResX helped me a lot to get everything tidy with different monitors.

@jjhp3 said:

I've been doing a bit of movie to projector mapping lately and have noticed that sometimes, not always, the connected video doesn't appear in the mapping windows. If I close the project and reopen it works. Slightly frustrating. See sig for equipment.  And thanks!  - John

 Could you please make a screen recording with quicktime or a gif with Recordit of this issue happening so that I can get a better idea of what might be going wrong? This is strange behavior.

Ideally a view like this where I can see the Movie Player and the IzzyMap window at the same time.

Best wishes,

Woland

@dusx

Great, that was it. When I changed the display resolution to 3840x2160, Windows changed the display scaling to 300%. 125% does not work, but 100 is good.

thank you,

Don

I really don't know why your setup has this issue. This isn't an issue that we have found on any official Mac hardware.
The stages really all work in the same manner, so it is very unusual that one would not work while other above and below do.

@danielcorbani said:

SSD HD

 What SSD? If the transfer rate is slow, you could be running into a bottleneck there during Scene transitions. If each Scene is playing 4 movies, then during the transition your computer has to play 8 movies at once because both Scenes are active.

Also when is Isadora getting hung up? The same Scene every time, or is it different? If you create a support ticket with the link in my signature and send us your Isadora Patch I can take a look at it and see if it hangs up while running on one of our test machines.

@tgtmedia

This solution looks like a good option, since the url parameters should make it clear that the page data may be changing.

Do you have control over what caching setting the web server response with?

You could try to connect to the web-server via the TCP-IP actors, this may give you more control over how the Http request is sent.
see: http://www.dusxproductions.com...

Thank you Woland! You know so much about MSC... I was already aware of your posts. : )

It was the Device ID in the EOS. Once we set that from 0 to 1 suddenly I had communication to the Watchers. I was thrown off by MSC working for triggering scenes and so thought all the MSC settings in the EOS were correct.

Thank you for your thoughtful reply.

Barry

Ok, no video preload, only scene preload.

Thanks

Yes, this is a known issue that will be fixed for Isadora 3.

Hi guys, i have some trouble opening Isadora. When i try to start the program, i will get this error report:

(it says: the named modul was not found)
The program will ask for every single plugin and after like 5 minutes of hitting enter, the program will start. i already checked for the plugins, but they are there where they should be.
Do you have any suggestions how i can fix this problem? Thank you in advance and have a nice day :)

Hey guys,

i got some problems starting Isadora. When i want to boot the program i get this error message: 

it seems that he cant load the actors at all. when i look into the plugin folder, they are where they should be. i already tried reinstaling it and start it without any firewal, nothing works.
I use an quite new windows 10 laptop and the newest version of isadora. do you have any ideas how i can solve this problem? Thanks a lot!

ok, I just finished testing.

I was routing audio in the movie player to a display port, once I put it back to default and then router the audio via OS to the Display port the problem went away.

@Woland Thank you for your reply!

It’s true that sometimes it’s handy to have the tool-tip info, for instance actor input/output value info, or actor’s input/output name when actor is collapsed.

However, if I put the mouse cursor over an actor in the “Toolbox”, it says “Click to select, then move mouse to editor and click to deposit”. This tip has no value for me and it displays over the actor name covering it all or part (depending cursor location).

Also, sometimes after hovering over an actor and moving cursor elsewhere, the tip message comes visible there (the new location of the cursor that might be outside the interface area) and stays there for a while even I move the cursor. This happens at least when having an external monitor hooked on a MacBookPro. (Well, this misbehavior might be part of the misfit between Isadora v2.x.x and Mojave?)

Lauri

I bit the bullet, sold the Z820 and am going to stick my current 5960x workstation into a 4U shorty case with a 1080 and assign it double duty as a render node and traveler workstation. While less portable than a laptop (I work 99% of the time in Toronto), I have become increasingly interested in (obsessed with) Isadora and think this change will make for a very sizable change in performance. Thanks again @DusX for the information you shared. 

thanks @DusX 

I indeed did a mistake in my first attempt with if statement and then jump to Juriaan solution with the switch without spending much time on my first attempt.

So the "or" operator works properly in the "if" statement when properly repeating the condition each time (well explained by Juriaan in his second comment)

While the switch case like in @Juriaan first comment doesn't work because switch doesn't take "or" operator ( as explained here ) , instead, you must do something called a "fall-through":

function main() { var step = arguments[0]; switch(step){     case 'seq1A':     case 'seq1B':     case 'seq1C':         return 1;     case 'seq2A':     case 'seq2B':         return 2;     default:         return 100; } }

I've got it mixed up by trying several solutions in parallel without understanding the specificities of each one, but it's all working now. 

Thanks for your help, I've learned something today! :)

@dillthekraut

Hi,

You have put a crop actor and set the resolution. Now is inf×inf.

Best

@misnia

Opening a support ticket is probably your best choice as Juriaan has said.
However, I wonder if your system might be pausing due to the autosave feature.
Please check your Isadora Preferences, and deactivate the autosave features, and let us know if that solves your problem.