Ahh, thank you Michel, I had forgotten that!

Cheers,

Hugh

Done.
Let me know if you have any questions.

Dear All,

Well, this sounds like something that needs to be revisited. The thing is, I just couldn't figure out a scheme to do this so that the activated registration couldn't be put back into place. I put my thinking cap on for this... and see what I can come up with. Best Wishes, Mark

Hi Mark and all, thanks for your help. I couldn't find the source of the problem - yes there was a reference file, but I removed it from the media list, and it still crashed the same way. I decided to rebuild the project, instead of continuing to troubleshoot.

Yes I have that setting enabled.

Hi Mark,

Yes, Midi's working fine with different note numbers. Couldn't figure out the reason it was jumping so far ahead, but worked around by creating a new izzy file. Decided to go another route and render out the effects to bring them into qlab to have one interface.  Thanks, Alex

This bug should be solved in 1.3.0f25; it shows up when you capture at a resolution lower than "full.". Try this free upgrade. To get it, start here

Best Wishes, Mark

I can never re-create this problem.

For me it seems to be when i've installed a new version (often the beta versions you send me Mark) and for a day or two my machine can act strange and then it settles. Its nearly always the Stage Output going black.

I am never concered as I believe it is my old machine just being a grouch! I think its the graphics card. From the info above I think its the older machines.

@knowtheatre you may find the problem has stopped, or will do in a day or two. If not then my theory will clearly be wrong!

I think this was addressed in f25. I had this problem with short clips like drum sounds but it has been flawless now.

here it is http://forum.troikatronix.com/cgi-bin/forum/gforum.cgi?post=12886

@eric

There shouldn't be any problems on a MacPro using DVI to VGA.

Best,
Michel

Unfortunately there is no feature in Isadora that performs this function. I has been requested here and there over the years, but I've not prioritized it because it hasn't come up that often. But, if you like, you can add it as a feature request on this forum and people can vote for it. If I see enough action on this topic, I'll work on it.

Best Wishes, Mark

Sounds like it was a corrupt file. Probably was the Internet and a glitch. I get it now and again.

This bug has been solved. The fix will be available in 1.3.0f26.

so i fixed this by shifting the surface position to 100 and turning the absorption up to 100 to so the little particles can now wiggle all over the stage unhindered by floors or ceilings.

Since it runs OK on your desktop with the latest version there must be something with your laptop that is different.

BTW, do you have regular backups of your system?

thank you very much!

Dear Zola,

I'm glad you got it sorted. But I don't understand the purpose of your request: if the image isn't changing, why do you need to send it repeatedly? Best Wishes, Mark

Dear Martin,

In other words, it was a driver specific problem that was causing the crash. Thank you for explaining this; it will help me support other users in the future. Best Wishes, Mark

Dear All,

There was a very weird problem that people encountered when clicking the link to view the release notes and download links for 1.3.0f25. (Had to do with our embedded forum, iFrames and other web browser stuff.) Anyway, this has been fixed. Go to the original announcement of 1.3.0f25 at the top of the forum topics, and follow the link there.

Best Wishes,
Mark

Dear Mehdi,

What's happening under the hood is that I am changing the OpenGL "viewport" -- once for left, once for mid, once for right. I am surprised if there is a performance penalty for this, but I'm sure what you are reporting is accurate. I will check into it once I solve more urgent problems (i.e., a complete freeze up) in 1.3.0f25. Best WIshes, Mark