The dreaded black flash between movies
-
@Skulpture. Sorry, I didn't mean to be short. This is a great resource! BTW. the optimize for speed post is out of date (it does not recommend H264 for encoding, but Isadora 2.0.5 seems to like H264 if one is using AV foundation for playback; I am not as I am still using OS 10.6.8).
-
Hey @ursullivision no, no it didn't read as being short. It's all cool.
The only thing I can suggest is opening an ticket and getting the super clever dudes (DusX and Jamie) to check it out for you - maybe you can send them the movie and have a look into it for you. -
I see you only have 2GB of RAM from your computer description in your Sig line.
After the OS loads and Izzy that doesn't leave much left so I wonder if these flashes are to do with memory starvation? Does the MacBook Pro have a discreet GPU if not it's using system memory and the cliches causes by a clash on the bus.I'm just guessing as I haven't come across these flashes with Izzy. AV Foundation does give me juddery playback on my Mac Pro test machine so I tend to use QT playback. On my MBP that I use for development it doesn't matter what I use. -
@Unfenswinger Hmmm, My machine does have a discreet GPU. it could be RAM. But that wouldn't explain why it had the same problem on the MacMini (4 gigs ram). Also, this short "activation" of stage 1 is weird.
@Skulpture. I guess I'll try that. Thanks.
-
From personal experience one izzy project would regularly crash my Mac Pro but is stable as anything on my new MBP. The crashes seemed to be due to the timing of scene changes so there may be some timing issue within the project causing the flash frames. Since I moved my license over to my MBP there were no crashes running the project at all so I never followed things up. -
Your observation about the stage settings changing momentarily in the actor, makes me think it might be due to a recently identified and fixed bug.Unfortunately, we are still testing.. and its not ready for release. Of course I can't say for sure, so I can only suggest using a work around for now (use 2 players maybe?.. different layers? .... preload?)I will say that the next release is worth the wait! Awesome new features! -
@DusX, OK. I guess this show will just have a few black flashes. It's too close the performance date to fiddle too much.
Thanks for the info.
ur, ummmmm..........................eric
-
Sorry, I could be of more help.
-
Could you maybe post one of the videos here for us to try? Even just a 10second loop?
-
@Skulpture, Sorry it took me so long to get back to you. Lotsa work. The show went well despite the "dropouts". How (where) can I upload the file for you?
-
Do you have a dropbox or similar?
-
Yes, I can upload to Dropbox. I'll email you a link if that is ok.
-
Sure. Let me know when its up.
-
DB link sent to your email address at gmail.
-
Got it. Will look into this today for you.
-
Skulpture checked my patch and saw the same intermittent black flashes.
Have you sorted out the bug, and could I test a prerelease to see if that solves my problem.Thanks,
Ur,ummmmm.............................................eric
-
I have been experiencing the "black Flash" from time to time with the additional problem that deleting a cue is part of the event. I am using a Mac Pro 6 core matching
e with 16GB Ram and am sending content to a Christie 10KM and a Barco 20K unit. on most of the content feed to the Christie feed I am using two projector actors sending the same content to the same stage. This makes for a kind of pixel doubling except you need the intensity of the 2nd projector set to apron. 25% to keep the whites from being blown out.Additionally, I am using a DMX receive actor that Mark sent me over the summer that is receiving that data through an Enttec Pro MK2\. The strange ting that is happening is that I have one cue in which the actor does not see the serial data. Oddly, if you activate the scene and watch the data as the info comes from the lighting console (ETC Ion) the actor responds, meaning you see the "message received" X and the DMX levels change in the display. The moment the cue with the actor is executed, the "message received" display goes to "-" and you cannot execute the next jump except manually. Now I have deleted the actor in that cue and replaced it with one that works in other cues and also deleted the cue, inserted a copy of a known working cue and in every instance the actor does not receive the data. There are 0ver 70 cues and all but this one is executing. So it would seem that I am some software instability and I considering a reinstall.Your thoughts? -
Can you let me know how your tests go with the latest Beta? @Old_DogThe cue issue seems unusual. However, given your setup it seems like it would be hard to reproduce locally.Is the data being received for this 1 'dead' cue in anyway different than in others? The serial parsing strings are very particular.We think we may have the bug fixed, however, I haven't reproduced it myselft, so I am waiting for Skulpture to get back to me with updated test results. -
I am designing a show where I need to trigger movies on que with midi. These movies are progressive states of the same subject. I get the black flash when trigger comes(midi or when I trigger manually) and I just cant't have that. The effect does not work with flashes.
Movie are ProRes422 1280x768 10sec long.I wonder if I have the same problem and how the fix is coming along. -
please don't try any work arounds, keep your patch setup the way it 'should' work .. and hold on a little longer ;)
