[Ticket Submitted] Crash when moving 3D object on background video

[dritter]

I have a problem with a patch in Isadora 2.6.1(PC, Windows 10) involving 3D  objects and video. The patch has 120 3D objects placed on top of a 3840x1080 HAP MOV file, organized as follows:

3D player #1 -->Virtual stage 1--> projector stage 1
3D player #2 -->Virtual stage 1--> projector stage 1
etc
3D player #41-->Virtual stage 2--> projector stage 1
3D player #42-->Virtual stage 2--> projector stage 1
etc
3D player #81-->Virtual stage 3--> projector stage 1
3D player #82-->Virtual stage 3--> projector stage 1
etc
movie player #1-->projector stage 1

stage 1-->Spout -->projector stage 2-->video projector A
                        -->projector stage 3-->video projector B
                       -->projector stage 4-->video projector C

This arrangement worked well with input from three Kinects for the last 12 months, but now the patch crashes when the 3D objects are moved using the inputs on the 3D player actors, but only when the rotation/translate inputs are changed on all three virtual stages simultaneously. The patch runs fine when only two virtual stages are modified. I found that I can modify all three virtual stages successfully if the background video is off and then turned on after the continuous modifications begin. I also found the patch is stable if the background video is HAP AVI. My workflow is set up for MOV, so It would be more efficient to use HAP MOV rather than HAP AVI. I would appreciate it if anyone has any suggestions about this.

many thanks,

Don

[Woland]

@dritter

Please create a support ticket using the link in my signature so that we can get the details of your system.

Best wishes,

Woland

[mark]

@dritter said:

I have a problem with a patch in Isadora 2.6.1(PC, Windows 10) involving 3D  objects and video.

Don, for specific crashes like this, it is best to open a ticket and send us the relevant crash reports, which I believe you know how to do. (If not, read here)

https://support.troikatronix.c...

Please make sure to send the original .crash files only. Do not paste them into another word processing document or otherwise modify them. Remember to .zip them all together as well.

Best Wishes,
Mark

[dritter]

@mark 

thank you Mark, I looked at the crash report yesterday as a .dmp file, but it was unreadable when I loaded it into a Notepad. Is that correct? Should it be readable at text? The computer I am using for this project is in a studio without internet, but I get a copy and send it later tonight.  

Don

[Woland]

@dritter said:

Should it be readable at text?

I believe that only we have the tools to parse them but this is in the Windows world so it's all Greek to me. Please zip them and send them along in a new support ticket so we can track the conversation and log the information better than we can on the forum.

Best wishes,

Woland

[mark]

@dritter said:

thank you Mark, I looked at the crash report yesterday as a .dmp file, but it was unreadable when I loaded it into a Notepad. Is that correct? Should it be readable at text? The computer I am using for this project is in a studio without internet, but I get a copy and send it later tonight.  

Oh I didn't realize you are working on PC now. Please update your signature line to include the type of machine you're using and which version of Isadora. For example, this is one person's signature line:

Izzy 3 USB | MBP (mid 2015) 2.5GHz i7 16GB AMD Radeon R9 | OSX 10.14

ReplyHaving this information is a convention in this forum to help us give better responses to you.

That said, no. If you are on Windows and have a crash dump file (.dmp) then only we can decode that. You need to pass this on to us for analysis.

Also keep in mind that we Isadora 2 is no longer supported in terms of bug fixes. If there is a bug that is unavoidable in v2.x, I won't be updating that version to solve it.

Best Wishes,
Mark

[dritter]

@mark said:

thank you Mark, I have submitted a ticket and the crash report.