@seandavidbacon

Ok, here is my Powerpoint to Isadora solution. Its a few years old now and I added a few lines in the VBA script today, to correct some instances that may appear when people are creating PowerPoints that interfere with a smooth transition. Please follow the guide I have added. There are also two PowerPoint examples you can use to test. Unfortunately you don't get around to convert the file to UTF-8 because I couldn't find a way to tell Powerpoint to do so. Its all explained in the guide. 

To go back and forth in the presentation press the left and right arrow keys, or klick the spacebar to go forward. To scroll forward quickly klick into the current slide number and scroll up or down with the mouse. You can also type a slide number into that field to directly jump to a slide.

Best Michel

surtitles-v2.zip

@dusx

Ok, I reset my preferences, and it works now.  Must have been a corrupt preference file.  Thanks for the help, DusX!

@dusx Thanks a lot ! I wasn't aware of those tools. The verifier spotted out usb problem immediately.
Cheers to you all.

@mr_j I just took a look at this, and what I see is that the Monitor does respect the framerate set. I am however testing this with lower framerates so that I can see the difference clearly. If I set the framerate of a monitor to 1fps, its clear that it runs at 1fps, and if I then increase this to 4fps, the difference is also clear.
Will a 30fps video playing, it appears to me that the monitor is playing at the same rate (perhaps a frame of latency).
I have seen your VJ project, so I know its pretty heavy. You may experience better performance reducing your cycle rate from 30x to perhaps 5X. This number is how many times per video frame the patch is processed, and generally this has little effect on the output as long as it remains above 1x the framerate (I use 2X as a point to auto reduce my projects.. eg: switching on some downsampling)
What cycle rate does your project report to you when you are running it?
In Isadora 3 the UI have been decoupled from the playback engine. This helps ensure that interacting with the Isadora UI won't delay video playback. It also means that data is passed between the playback engine and UI thread. Its possible that this becomes a bottle neck in your case when you are using numerous monitors and have a heavy load. It might be possible to optimize somewhat by combining videos in the patch into a single video (eg: 2x2 quad) that is sent to a single monitor. I have not tested/confirmed this optimization, but it seems feasible.

@juriaan 

hey you all. thanks for the quick replies. We actually solved the problem already by finally updating isadora from 3.0 to 3.1.1. and So far it hasn't crashed on us anymore. 

fyi its a mac runnig on  10.13 high sierra.

thanks again and have a great week

kindly

Chris

@mark Many thanks to you and the team - working great, and now can't wait to get all creative☺

@citizenjoe

There are EDID Managers which fake a monitor/projector and even more forces the resolution and framerate (EDID) to the Windows PC. They are very helpful in general, as this keeps your windows from flipping around, if you play around with the projectors. It could even maybe help you with your issues, as it helps keeping a clean and defined signal. At least, you'd have some devices always connected when starting the PC, and can start up projectors afterwards without worrying.

https://lightware.com/edid-man...

@woland

i will try to reproduce the issue after the show on thursday....

@jtoenjes

Open Task Manager and see if Isadora.exe is still up. If it's there, end the task and you'll be able to re-launch Isadora.

@jandraka

As long as you look at what the slider says, that will always be accurate, because any change you make on the slider immediately takes effect on the actor (even if the input on the actor doesn't update visually to tell you that). If the slider for a Movie Player actor's "Loop Enable" input says "on", then "Loop Enable" is "on", even if the actual input on the actor has not updated visually yet and still says "off": https://recordit.co/WBFctO5IUA (You can also see that the input on the actor updates visually once you close the slider.)

As you said you can also type into the field and press enter, or click on the field and hold down the mouse button to drag up and down through the various settings: https://recordit.co/0EAekYF41O

@dusx I ended up doing a clean install of Windows. Apparently the problem was on system level. Still have no clue what caused the problem, but a clean install finally worked

@gaspar said:

This is not too bothering, but it does not happen on 308 and since I work very often with this setup it prevents me from switching to 311, because that flickering is annoying and distracting.

This is a known bug though in our experience it did happen in 3.0.8f12... at least in some situations.

The team has a beta that fixes it. If you're a beta tester, you can ask for it. Otherwise the fix will be in available in a point release we want to make available as soon as we can possibly manage.

Best Wishes,
Mark

@margie

Hi there Margie!

Welcome to the TroikaTronix Community forum. Glad to have you here.

Normally in this kind of situations it is best to open a new support ticket, you can do so by filling out the following form;

https://support.troikatronix.c...

Our technical team will reply to your ticket and get over some details with you to get to the bottom of this!

Thanks and a happy new year for you too!

@emtv said:

comes back in next 3.1.x update

 We are investigating options for expanded support. A change was made to update the software interface used for Live Capture connections when 3.0.8 was released. So 3.0.7 uses an older interface and has some issues with modern 4k capture devices (elgato cam4k is one which we tested), so 3.0.8 was updated. This update removed some legacy Direct Show support which didn't effect any beta testing, but became apparent after release to the public.
We are aware this change has affected some users and are working to fix this for a future version.

@reinhard

Hi there Reinhard, 

We are looking into it.. Sadly it is an issue with jQuery (an animation library that we use for the website)

Possible things that you could try;

1. Log out / Clear cookies for TroikaTronix / Log back in (I can also force this if you wish as Forum moderator)

2. Try an different browser and see or you have the same issue.

Anyhow, we will get you back replying asap!

@trevorn1

We updated this article just for you ❤

https://support.troikatronix.com/support/solutions/articles/13000040390-isadora-2-3-installing-external-plugins

@alice

OK, please open a support ticket. We will need to take a closer look at what types of media/codecs you are using.

The Support Link is in my forum signature below.

@eva

I think you are just finding the edges of the Kinect OpenNI interface. It can be very picky about initiating. You need to activate things in the correct order. If it does crash, you will be best served to power off all parts and start them up again in sequence. I suspect that if you are careful about doing this you will find it becomes more reliable.

Isadora 3.1.1 may include some fixes that help you, but nothing I can think of that is specific to OpenNI.
You can install 3.1.1 and keep your current installed version. (yes the download link is now the latest version).
This article will help you install a second copy of Isadora (useful for testing): https://support.troikatronix.c...
NOTE: the file format will be updated for Isadora 3.1.1 so if testing a current project file PLEASE save as a new file (dialogs will warn you) so that you have a safe backup

@soniccanvas

Please read the post I made today about this.

Best Wishes,
Mark

@mark

Hi here are a few images to help:

First the resolution setup:

This is what the preview look like, Isadoras NDI is on the right, my c++ NDI is on the left, both are 150*5 resolutions:

When I use the Isadora stream and scale it up I get these jagged edges (the black bars on the right of the stream and also the stream is rotated 90°:

My 150 * 5 stream under the same scaling (it does miss the bottom row of pixels, but I guess NDI wants only even numbers of rows and columns:

I guess this does not happen at all scales, but for these small streams Isadora does not seem to output NDI correctly.

Fred