Thank you Mark

Joe

Another option would be to retrigger the video from Ableton via midi or osc.

weird, now is working again by itself...?

Hi @mark

Thank you for the response, I wasn't aware of the Alignment Grid feature, it will be useful for the future.  As an example I have set up a stage - with the alignment grid feature. I am using one stage and multiple grid mappers within it. Please see attached screen shot.  I would find it useful for each grid map to temporarily display it's edge via a perimeter colour just for reference - when I am a long way from the physical stage at the video control position it can be difficult to see if the physical surface is fully covered by the content, or if indeed the content has spilled off the edge of a physical surface. Perhaps I'm using Isadora incorrectly? As I said I'll adjust my workflow accordingly. Thanks to Mark and the Forum its guidance and advice is much appreciated.

f32109-screen-shot-2015-04-02-at-15.39.22.png

Hi

Just to close this thread. I am back here now and you were right @primaldivine  upgraded and it instantly snapped into dark awesomeness F

Ey Mark. thanks for your advice and solutions

It is indeed sorted out and I dont think this mechanism would consume a lot of resources, does it? Also, I detected the same bug in the metaimage actor and I sorted out the same way. Alles Liebe!

NOTE: the test file has the Actor Processing Mode set to v1.x

my tests show that the problem lies not with OSC but the processing mode.  Switching to the new and recommended default V2 Actor Processing Model works as expected. I have passed the bug report along to Mark, so that V1 can be corrected.

Thank you Michel !

Has this been officially entered as a feature request?
http://troikatronix.com/support/isadora/

Got it solved. My video capture setting were the reason. Thanks for looking into this.

blush

Thanks found the link here: http://troikatronix.com/troikatronixforum/discussion/1861/alpha-channel-blending-with-gpu Looking forward to trying it out

Yes sorry about that. I thought they came as standard now - my mistake. It's often the simplest things that trip us up! haha.

Dear All,

Please have this person file a bug report and supply two or three of the problematic GIF files. Isadora uses QuickTime to import and play the GIFs. So, one quick test would be to try and play them in QuickTime Player 7 and see if it also shows a glitch. To submit a bug report, go to http://troikatronix.com/support/isadora/ and choose "Bug Report" from the topic menu/dropdown. Best Wishes, Mark

@jbrem003

Have you submitted this via the support page? Do you have an active support ticket? If not I will set one up for you and wee can investigate this further.

@mark

I see that at least 1 syphon related ticket is marked as fixed for the current version. I am continuing with testing today. Perhaps @Primaldivine has additional information.

Dear @julio_parente

We received your email today via our "help desk" system, and I'm sorry for the delay. Something went wrong with your order because it was missing the license name you intended to upgrade. (The online store should ask for this information.) Someone from our team should have emailed you about this problem within 24 hours. I am checking with the team to find out if they did send an email or not. As I said in your previous post, the 2.0 update will address any negative experiences you've had with the Classic Movie Players under 10.9 and 10.10\. That was one of the main reasons for the 2.0 update. You can now use either AVFoundation -- the more modern system for playing video -- or QuickTime when you need certain kinds of interactive performance that AVFoundation doesn't do. But in both cases, the playback runs in a separate "faceless background application" to prevent these kinds of crashes. In any case, we will be in touch via the "help desk" system and resolve this issue presently. Best Wishes, Mark

Dear @kdobbe,

To test this I did the following: Create Movie Player -> Colorizer -> Projector Created a a toggle button, and linked it to bypass input Pressed button, turning 'bypass' on Take Snapshot 1 Pressed button again, turning 'bypass' off Take Snapshot 2 Click the two snapshots to test Everything worked as expected Is this any different than what you are doing? Best Wishes, Mark

Thanks @Interluder

Dear Eric,

Yes, I just found the same. But this is definitely a bug and needs to be fixed for the next release. Working on it right now. Best Wishes, Mark