hello. sorry it is allways nearly impossible for me to find time to too it. the computer i run the most shows from never gets internet. so how form shout a ha dmade bugreport have in this case. also the perhaps bug with the cues are not ge erating a crash. so no crashreport too. thx r.h.

@mark_m – it's the external hard drive. This issue has come up from time to time before (it's not specific to the beta), but I've never been able to repro it.

Some questions. 1) What is your main hard drive letter? Is it C:\ or something else 2) What letter does the OS assign to the external drive when it mounts? (@Armando, It's a windows issue only.) Best Wishes, Mark

thanks for all of your posts and advices. As I had written in post nr. 4 I had solved the promblem already. It was the upgrade to windows 10 and then the missing update of my grafic card.

@DusX that is brilliant! Have you tried anything with naviar - stokes or other fluid dynamics by any chance? We are part way through developing a naviar-stokes plugin and have it running through QC at the moment.

yes, I tried the short transition but still the same. And anyway I also need the smooth transitions. By the way I used wav-files.
I now tried an mp3-file which is played only in the movieplayer, not in the sound-player. But this seems to works fine now for me.

Cheer to all, I know that inserting an actor between two patched and linked actors has been requested before and I know that Mark has others more pressing things to do (Sierra stuff), but  [please see this very short and clear video](https://cycling74.com/2016/10/25/patching-mechanics-in-max-7/?utm_source=Max+Friends+List&utm_campaign=dbcc881c6e-Newsletter_79_10_26_2016&utm_medium=email&utm_term=0_6c6d94f223-dbcc881c6e-67181309#.WBDjzncZOEJ) posted yesterday by Cycling 74 (max/msp/jitter producers) to show how they did it. And they did it right! Easy and versatile, very isadorian. Happy patching! (max joke) Armando

perfect!

adding a bug report.

I recently encountered this also while working on a project. 

Dear @DusX & @AshChristopher,

I'm sorry that I did not see this earlier. But the problem is simple: the file has YUV Mode enabled in the file you attached. (We really need to remove this from Isadora, as it is no longer viable.) You shouldn't be using YUV mode with v2.0.  If you turn of YUV mode (**File > Disable YUV) **the PNGs immediately loaded as expected for me. Could that be the case for you too @wassarts? Best Wishes, Mark

There is a 2.5 pre-release version you can try posted at the top of the forum Also try running Isadora and pausing the engine then opening the show.

Hi,

I'm not working with the sassafras keyserver,  Maybe I hade something installed wrong. I deleted everything en reinstalled. I don't get the popup if I crash it bud maybe the counter is back to zero. if it comes back up I'll let you know. I also got the firewall pop up back when i start up so i think the problem won't come back. Thank you for the help With kind regards Groeten Gertjan

This plugin should be fine.. the new SDK will change mostly in regards to Video (gpu vs cpu).
If you can get the available sdk running, and compiling, you should be able to port this.

@DusX Thank you for the detailed description. I think I understood now that my original issue is a by Izzy intended behavior, but can be switched by the 'grouped' setting. In this case the "(v1.x Compatible)" extension in the menu is a bit disturbing, as it could mean this feature might disappear in future versions.

@Dusx I can do some screencaps shortly that may shed some light on this. It seems like a simple enough setup, I agree!

@Skulpture yes, I am making the stage change in the projector actor but I think it's a deeper issue because "show grid" will not even show the grid on that projector. 

Figured it all out! Thanks

Thank you very much Ryan, I'll try this and let you know.

Best, Alberto

I am a complicated person…

@Skulpture, but when you publish the points and use the offset how do you map again? The image in the mapper where you grab the points no longer corresponds to the output. Especially if you use the offset on just one slice. in the mapper it may sit right next to another slice but on the projection it is a completely different place. For me this feels like a bug, even if it is deliberate and I cannot see the use case, but maybe there is something I missed?

@selittle 

Glad you could fix it.  Best Michel @Mark

Glad you figured it out.