​[SOLVED, MEDIA FORMAT ISSUE] can't modify any scene wo overwriting all other

[Woland]

@markelinus

That sounds extremely bizarre. As far as I'm aware, there aren't any features that would cause modifications in one Scene to overwrite an entire Scene elsewhere in the file.

Could you please provide a more detailed description (How are you modifying the Scene? What are the precise steps to cause this problem?), perhaps screenshots of the issue, or a gif/video recording so that I can understand better what is happening?

[markelinus]

@woland:Current issue is all changes being processed in all scenes related to one file, cf. att. screen-rec..??..

[Woland]

@markelinus

Can you please give a more detailed description of the steps to cause the issue and perhaps screenshots of the different steps? Very brief, one-sentence summaries are not enough information for me to understand and diagnose an unknown issue like this.

[markelinus]

hey woland:  Try less brief, scusa:

Link: https://nextcloud.adk-bw.de/in...

The set is being used via osc-listeners-triggers send by qlab4 on one machine. This case is related to changes in one scene being transposed to all other scene, meaning while any change is being performed all scenes get hardly overridden immediately to my surprise. However further saved files get also overwritten, indicating kind higher order scripting being active wo sense. Any suggestion in global properties or else to check for proper usage..? Thx. 

[mark_m]

@markelinus

What's going on in your 'Start' scene, which is activated? 
Are there things happening in there that are having a global effect?

[Woland]

@markelinus

Based on the recording, while it visually looks like it's making changes to both Scenes, I believe it's actually a cosmetic failure and what's happening is that it is failing to draw the other Scene when you switch between them. I have only seen things like this when Isadora is unhappy about a piece of media that it will import just fine but has trouble dealing with when it attempts to play it. Usually, it's because the media was created with non-standard properties that Isadora doesn't know how to handle. I've only seen this a handful of times so we're still trying to isolate what it is about certain media files that causes these kinds of problems.

1. Could you please post the Isadora file here for me?
2. Could you please delete the media from your file (just select both video files in the Media View on the righthand side of the main application window and delete them) then try to switch between your Scenes to see what happens? (Feel free to do this in a copy of your file so that your original file remains unmodified.)

[Woland]

@mark_m said:

What's going on in your 'Start' scene, which is activated? Are there things happening in there that are having a global effect?

 Good point, it could be something messing with Scene Activation that's in the background Scene. Yet another reason I'd like to actually try the file myself to see what's in there.

[markelinus]

Hey mark_m: start scene is thought to inhibits the jump2scene actor to fade in, now just mirrored like all additional scene deleted by now, while only being able to work in 1 scene and thus being lost in creating any show w more than 1 scene {:.<[

[markelinus]

@Mark_m: Yep, certainly true - it is directly related to the video input- still wired }:≤> 

[Woland]

@markelinus said:

issue might be solved now

Let us know if and when you know for sure whether it's solved or not.

So was Isadora getting constant OSC messages to go to a particular Scene? I'm not sure if it's what you did, but putting a Jump actor in a background Scene is not best practice because in relative mode, the jump will always be relative to the background Scene, not any other Scene you may have active. You could use Activate Scene actors in a background Scene actors or make a User Actor with your OSC Listener and Jump actor set up inside it, then put that User Actor in every Scene so you can use OSC to cause a jump from any Scene you happen to have active as the primary Scene.

Also in cases like this, you could try going to Output > Pause Engine, then navigating through your Scenes to check for a group of actors that might be causing continuous jumps.

[markelinus]

@woland: nope, it appears again by using wired.sc.footage. Files being saved are empty.

[Woland]

@markelinus

What is "wired.sc.footage"?

Can you please provide your Isadora file so that I can take a look at it myself?

[markelinus]

@woland: determind scripted content at mp4 file, makes me a bit insecure work environment - better sandbox first ;>)

[markelinus]

@woland: Like noted previously the error occurs only with delivered footage. Also checked for virus possibly included to the 2 mp4 files, luckily negative...

 Pl. find att. link for the izz-file: https://we.tl/t-t0mtH4DWjq

Thx for having a look deeper ]:+>

[Woland]

@markelinus

I'll take a look later today

[Woland]

@markelinus

Looking at the media info for your two imported video files, they list the codec as "hvc1" which indicates that these are h265.mp4 video files, which are not officially supported and is probably the source of the strange behavior. If you convert your media to h264.mp4 you should have an easier time.

Thanks for the media and the very simple file though, it makes it easy for me to repro the problem and log this as a bug.

[markelinus]

@woland: Thx for looking into - with the converted footage working with Isadora is fine again..  

[mark_m]

@woland said:

log this as a bug.

 What's the bug? That Isadora doesn't like H265?

[Woland]

@mark_m said:

 What's the bug? That Isadora doesn't like H265?

Yes, or that it doesn't like something else specifically about these particular h265.mp4 video files (though h265 is most likely the source of the issue in my opinion). Either way, I now have media and clear repro steps to cause the problem, which made it easy for me to log this issue.