@dusx

Thanks. I'm at Izzy 3.0.7

I also found that my problem wasn't needing preloading. I just needed to Initialize the Play Start for my video so it wouldn't have the black at the front end. I thought it was a loading problem. It wasn't. And thanks for sending me the link to the other info. I hadn't run across it before and it's very helpful.

Hi @Eva 

Resetting preferences is often a remedy: Resetting Isadora Preferences

Best Wishes

Russell

@weston said:

Attached below is a screenshot featuring my issue. As you can see, my zoom window features a warped video feed. Reboots of all systems haven't resulted in a fix.

Fixed in v0.9.5 - Download

Best Wishes,
Mark

@dbengali

Thanks for the bug report. This bug was in 2.6.1 as well... I guess no one encountered it before. I've fixed it in v3 and the fix will appear with the next point release (3.0.2) which is coming shortly.

Best Wishes,
Mark

Please submit a ticket so we can get this logged in our database.

Good find!

@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

@rbecker said:

I'm trying to play a video in a really simple patch (Movie player --> projector) in 2.6.1, and it won't play.

To be able to help you we need further information:

1) You say that you've tried several codecs, but can you please give us a list or at least tell us one of the codecs that won't play?

2) Similarly, can you give tell us the typical resolution of the clips you've tried? 1920x1080? Or?

3) I assume you're running Isadora in fully enabled mode (i.e., not in demo mode). Is that correct? Are you running the USB key version? If so, is your USB key inserted into the computer?

Best Wishes,
Mark

i seem to have noticed that occasional <SPACE> characters that remain attached to a variable name after dbl-click select and copy, when pasted into the preprocessor code // ISADORA_FLOAT_PARAM(name, id, min, max, default, "help text"); do create the corresponding inputs , but they do not react unless you cancel the <SPACE> character in the preprocessor statement. 

took me an hour to figure, one night. 

the GLSL editor is kind of tricky, but i attribute this mainly to my italian keyboard. the character '[' freezes the editor until i re-compile.

the find and replace is not working as it should. 

this on Win 10 with 2.60 

wish to have more time for the forum. 

cheers 

hairi