@jfg

Thanks that looks good and simple! And reminds me to refer to the parsing specification more often 🙂

Best wishes

Russell

@dusx This is amazing and super helpful. Thanks!

@eva how did it go?

Thanks Juriaan,

  As it happens, I have already opened a support ticket.  I'll wait for that the reply to that, I think, to answer your questions.

I.

 

@juriaan

I have added a new Feature request, linking to this forum thread. 
When we next review Feature requests I will push for this item.

@callie

Please open a support ticket. One of us will work with you to determine why 3.0.7 works for your and not the latest release.

Link to support is in my signature.

thank you for the help to solve such problems. 

@m_theater thanx for reply - I will check this when I`am back in the studio we have a 4k Monitor there...

@juriaan

I have done that in a past life (4 years ago) when I was using TCP Syphon to send video signals to RPI 1B+ units.  Unfortunately, my current receiver setup (https://dicaffeine.com/ running on a mix of RPI 3B and 3B+) don't have that capability.  The units are already at 75-80% CPU just decoding the SD NDI streams and the software doesn't support cutting things up.

Another option I am consider is forking my network and playback system into two layers. A master Izzy playback computer would send 2-4 NDI streams containing half or quarter of the wall's imagery to 2-4 matching second tier Izzy computers over network A.  The 2nd tier computers would then cut those images up and pop them out to all their respective RPI receiving nodes over network B.  Maybe a little crazy?  Maybe could work?

Hi there,
I was wondering or you found a proper solution, if not feel free to open a new support ticket at https://support.troikatronix.c... so that our technical team can assist further.

Thanks!

you could be having issues with your storage it could be due to low memory or you could be using an external hard drive as a storage device, I was having a trouble exporting logos for my site but try freeing up some space.. 

@rl said:

How could that have happened?

Hap is installed and registered along with Isadora. If something causes a failure during install, it's possible the codecs which are registered could be corrupted.
It sounds like re-installing Isadora corrected the issue.

@mark 

Thank you so much!

Right Mark, solved! The scale was 125%. I had tryed before but without succes, maybe your reset suggestion associated with the right scaling solved the problem. 

As always many thanks!

Francesco

@dariuspowell said:

<p>and 5.1 is playing fine, too. </p>

Great to hear!
And thanks for the update on the surround sound / multi-channel audio.

@bob288

Hi there Bob, 

It seems you already figured out the issue. Let us know how it happened. The article that you link has the correct code snippet?

Anyhow, I mark this question as Answered.

- Juriaan

Hi there @joshuawg, 

That sounds less than ideal. Let us get to the bottom of this, could you kindly sent us a support ticket at https://support.troikatronix.c...

Our support team is aware of this thread and will respond accordingly.

Thank you!

- Juriaan

@lpmode

Thank-you for making the screen recording. That is always a welcome help.

In this case, this is a known issue, and is in line for fixing.

@lpmode said:

I kind of remember this working fine in a previous version

 I don't think this should have worked previously.

The way to approach this is to put the media that needs to play across a scene transition in another background scene.

So, lets say we are in the show in scene 3. Scene 4 plays two videos, but one of these videos needs to play into the next scene.

We create Scene 4 and Scene 4b (background scene). When Scene 3 jumps to scene 4, an enterscene trigger in scene 4 activates scene 4b as a background scene. So both videos are now playing.

When we want to leave scene 4, using a Jump actor we transition to scene 5 (past scene 4b), in a future scene we use an enterscene trigger to deactivate scene 4b.

So we move through scenes like: Scene3 --> Scene 4 (activates scene 4b) --> scene 5 --> scene 6 (deactivate scene 4b)

In that flow, scene 4b plays through Scene 4 and 5.

This thread might help you: https://community.troikatronix...

Especially @DusX comment about load: "LOAD is a measure of how much time is being used to process each frame, based on the target frame rate. It is NOT a measure of your system resource usage. In Isadora it is most important to know if the scene can process at the selected framerate, LOAD provides that, a measure of 100% means that calculating/rendering the frame is taking all the time available between each frames delivery. This will lead to dropped frames."

On my system, the load is often above 100% and it doesn't create a problem until it gets up to 10 times that!

Cheers,

Hugh