@rrberry2 said:

serious lagging

This might be the Adobe CC issue. Do the machines have the Creative Cloud desktop app running?

If so try quiting out of the CC app and Isadora might come good.

Best wishes

Bonemap 

@fifou

I just tested it and it only works on the rectangle bounding boxes, to be precise on the rectangle mapper and on the grid mapper but only the larger circles that manipulate the whole picture. It doesn't work on triangle complex mask (that is only changeable on the input) and the individual grids of the grid mapper.

Not sure if this is a bug or intended to be so. @mark, any insight on this.

Best Michel

@fifou said:

The culprit is 48KHz files.

 OK, will investigate.

@danielcorbani

I can confirm that this is happening to me too with .wmv files.
Clearly a bug: I'll report it.

Autocad have a great resource that I have referenced a few times when faced with this issue.
see: https://knowledge.autodesk.com...

@mark 

No problem, thanks for letting me know!

Best,

Lauri

@juriaan said:

@mark
Alright.. I also got that. But why does it work that way ? If I set the MAX / MIN in the double click dialog shouldn't it be the same as the LIMIT MIN/MAX ? Why are there 3 different limiters (MAX / MIN Dialog, The LIMIT dialog, and the external input Scale MIN / MAX)  inside a single Input value. In my opinion linking the LIMIT dialog to the MAX / MIN Dialog makes perfect sense.

 I don't see this as a bug. However I can understand the bigger picture and can see your POV.

Just an idea; but what if the external input scale(s) [MIN/MAX] was greyed out; so when you changed the inside scales [MIN/MAX] were grey so it was a visual indicator that it can't be changed.

Dear Maxime,

I have gone through your patch and -- as far as I can tell -- everything is working exactly as I would expect.

Unfortunately I cannot test your user actor in v2.2.2 to compare, because the file was saved with v2.5.2.

Do you have a v2.2.2 copy of the file?

Since you say "each time I go to next cue, the player doesn't take consideration of the position input (for the cue in)," can you tell me exactly what does not meet your expectations? For example, in your patch, one of the combinations is:

play start: 0, play length: 76, position: 51.

In both v2.2.2 and v2.5.2 and the current beta, if I setup a movie player with these settings, the movie starts playing at 51% within the loop 0 and 76, which is 38.76% of the total movie duration. (The exactly starting point within the total movie duration = looplen/100.0 x position/100.0 + loopstart/100.0.)

Can you explain in further detail the difference between v2.2.2 and the later versions?  

Best Wishes,
Mark

please open a support ticket (link in my signature) 

If possible share your simple project with us so that we can try to reproduce the issue and your fix.

Thankyou for the report.

@jxq said:

I followed the steps in the tutorial with the nebula - space shader and these errors showed up:

 Since the release of Isadora v2.5.2, ShaderToy changed several of their variable names. That causes the errors you're seeing above... and unfortunately we can't do much about that except to release updates when they make changes like that.

Isadora v2.6, which will absolutely positively be out by Dec 31st, 2017 will address these issues.

That said, please post the link to the shader you had trouble with so I can test it with the v2.6 beta. I'll make sure it's working before we release.

Best,
Mark

@blusound said:

WMV

 It's not the optimum codec/format for short videos or interactive playback.. it's intended for playing movies at regular speed. It will provide quality playback of long hd content if played normally. Additionally it provides small file sizes.

Hap is probably the best codec for smaller / Interactive content. However hap avi may not respond as well as quicktime for interactive work..  it's best to test for your specific usage.

@mark

I assumed the rest of @bonemap 's Patch would be complex, I just didn't know how much Pulse Generators contributed to the strain. Now I know, so thanks!

Hey Mark! 

Thanks for the reply. It looks like I have solved it.

It seems the problem was indeed an over-abundance of Pre-load Scene actors that I had not found my first few looks through. I've never had this sort of "build up" problem before but it may have something to do with the fact that I was using the JumpByName actor to trigger my cues. Also, to answer your question they were movies.

Thanks again!

@sommerdi said:

My patch is running  without crashes so far ....

Woohoo! Thank you for letting us know.

Best Wishes,
Mark

strange...now i can...

@artoo said:

I'm working under macOSX 10.9.3 would it be the begining of an answer?

One other thing: we've established a pattern of testing only with OS Versions that are two revisions back, which means 10.11, 10.12 and the current release of 10.13. We simply can't back further into the past given the resources we have. If we can't recreate the crashes on one of those operating systems, you may need to consider upgrading your operating system.

We've created an official policy on this, which you can read here. Specifically take note that we specify only officially support Windows 10 and Mac OS 10.10 and later. 

That said, I still want to see if we can recreate your crashes, so please file a ticket as soon as you can and we'll follow up quickly.

Best Wishes,
Mark

Thank you Juriaan, Ryan & Michel! Sorry that I went into full production mode and didn't get a chance to check the thread until now. The method of going into the ENTTEC Send Actor and changing the 'min period' has resolved the overloading issue. I just changed my number to "2ms" and the FPS went back up to 30 already. I will keep testing in real situations and let you guys know if anything else I found, otherwise this topic is resolved for now! Thanks so much!

@Lauri 

Your step by step did the trick. I see the problem and I'll fix it.

Best Wishes,
Mark

@dodioflo said:

Here is the file: resplendant.izz

I've sent the password to your gmail address.

Best Wishes,
Mark

@juriaan said:

Hi there,
This is NVIDIA GeForce Experience that is causing these overlays. You can disable it by going to your Nvidia GeForce Experience window > Click the little 'settings' icon at the topbar > General > Turn off the overlay setting.

 Thank you! I couldn't remember off the top of my head and I had left me Windows laptop at work.