@crystalhorizon said:

the beta 309b10 (ARM) doesn't recognize any of the plugins like rutt etra, grapher, etc

 We've got FAT (ARM-compatible) versions of the external plugins. I'll find out in a meeting in 45 minutes whether I have permission to distribute them.

FYI Aaron has it running perfectly fine on the less expensive instance without the elastic GPU, which I am incredibly excited to share once it is finished.

@juriaan hello, sorry for the late reply :) 

so far, as long as I don't mess with the ports each display is connected to the pc

turning on every display before the pc,starting the computer,opening the izzy file 

helped with keeping the stage setup with right displays assigned for each stage. Turning on the computer first and then projectors messes up with the display order and hence the stage settings, however once I restart everything and follow the above 3 steps in the right order, things do go back to the way I want them to be.

@woland, yes, sure I will open a support ticket, thanks! but the ctrl+z trick works too. 

lastly, about the hap codec: right now we are working with mp4 files since Isadora seems to be working just fine. Hopefully things will continue running smoothly as the number of the videos increase, if not, I will look deeper into this, many thnx for the tips! 

❤💚💛 emre

@ All

thank you very much for helping.

after some hours, installing nimate did the trick.

maybe a driver thing. 

r.h.

Works perfectly! Great work around.

@fred

I haven't been having as many issues since our last update. Reply generally works as expected for me now (chrome on PC).

The behaviour you are having sounds similar to what was happening to me previously. If you click on the forum menu, then recent, and then into the post you want to reply to, the cache seems to be corrected (it gets mixed up with forward/backwards moves thru the posts) and will let you reply as expected.

@mark_m Yes, thank you!

@jbbarriere said:

Where is it written,

 by default it will be the desktop, unless you changed it via the Output/Set Captured Media Folder... menu option

@kdobbe

Please open a support ticket (link in my signature) and provide a download link (dropbox or similar) if possible where one of us can take a look at one of the video files that is playing in this manner.
@Woland may be able to recreate your setup and debug the issue further.

@deflost NiMate gives an error on launch stating it wasn't shutdown correctly last time, and then goes to taskbar briefly, but then disappears. 

@eamonn

This is a known issue, and relates to the drawing width of the Scene list itself.
So, you can reduce the size of the panels (shortening the names is also useful) by hovering the mouse over the right side of the Scene and holding down Control (Ctrl on PC), watch for the cursor to change indicating that you can now left click and resize the scene tab.
By minimizing the width of each Scene tab, you can fit more scenes with in the drawing area available.

@benglover

It is true that the Direct Show based playback which is used in Isadora 3 on Windows doesn't provide seamless looping. We are working hard on a custom playback engine which is proving to work well, especially with Hap video.
Currently there is no perfect workaround to this issue. If you need seamless loops you may need to create a long video which contains multiple loops within the video itself. Still the end loop will not be seem-less. You may consider a very simple crossfade to smooth out the transition.

@juriaan @mark_m @eamon 

it's working now! Amazing! thank you so much for your time and suggestion! 

The most common cause I see for this is related to GPU configuration.
If you are running a PC laptop please read this. 

@mark_m I noted the same and also use GE.

@aidan said:

every minute

 That's going to be far to often for the reset. Especially since it takes a number of seconds to actually reset (maybe 10 secs of non responsiveness).

I would suggest running a timer in a Background scene and using the value of this timer to cause the reset on enter scene..

so:

on enter scenecheck value of timerif timer value is greater than ret time (defined by you.. say 5 mins)reset the Kinect (plus anything else you need to do to mitigate the non responsiveness of the kinect)restart the timercontinue at normal

this allows you to set a Reset interval.. and through some testing find the maximum value that is reliable.

@hamilton said:

Does Isadora 3.1 runs in Big Sur? The support ticket only lists Isadora 3.1 + Monterey.

 Absolutely yes, Isadora 3.1 runs in Big Sur. I will look at your ticket.

Best Wishes,
Mark

@aolis said:

@ianupstanderThere was a webcam driver package called Macam that used to be used to get it to work on Mac.It looks like someone has done the work of updating it to a 64bit setup for Catalina.

 As far as I can tell, the Catalina update offers a static library (i.e., a ".a" file) that one needs to compile into a program and use. I don't think it is a generalized library (i.e., a dylib file) that you can install somewhere and get macOS to recognize those old cameras in general. There is a link to a VUO plugin that uses this library, which implies a similar plugin could be built for Isadora. (Of course, time allowing... I've got a lot on my plate as usual.)

Best Wishes,
Mark

@dusx I didn't know that...thanks.

@barneybroomer

Isadora v3.1.1 solves this issue. You can download it now from the Get It page.

Best Wishes,
Mark