• Thanks for visiting the Kaleidescape Owners' Forum

    This forum is for the community of Kaleidescape owners, and others interested in learning about the system, equipment, services, and the company itself.

    It is run by a group of enthusiastic Kaleidescape owners and dealers purely as a service to this community.

    This board is not affiliated in any way with Kaleidescape, Inc.
    For official technical support, product information, or customer service, please visit www.kaleidescape.com

  • You are currently in "Guest" mode and not logged in with a registered account.

    The forum is free to use and most of the forum can be used by guests who are not registered....

    ... but we strongly encourage you to register for a full account. There is no cost to register for a full account.

    Benefits of registering for a full account:

    • Participate in the discussions! You must have a registered account to make posts on the forums. You will be able to start your own thread on a topic or question, or you can reply to other threads/discussions.
    • Use the "Conversation" feature (known as "private messaging" on other forums) to communicate directly with any of the other users here.
    • Access the Files area. The "resources" area of the forum contains many "Favorite Scene" and Script files that can dramatically increase the enjoyment of your Kaleidescape system. Go directly to great scenes in your favorite movies, created by other owners, and add automation to playback of your system with Scripts.
    • You won't see this annoying notice at the top of every screen!😊

    It's easy and free to register for the forum. Just click the "Register" button in the upper right corner of this page, and follow the instructions there.

HDR Movie Tag or HDR Picture Correction for Projectors

Decided to write the extra code to track when the MX160 changes initially. Works great now and no more dropouts.
 
I did implement the configuration to audio based on MX160 audio type. It works well, but the main downside is that whenever you pause/skip in a movie, the MX160 audio type changes to no information and then when the movie starts back up, the system thinks it has been updated and sends the appropriate audio command again. Just results in a quick audio dropout/reset. Not an issue when just watching a movie. May need to write some more code to get it to stop that behavior if possible. Still think it would be great if this was done by the Strato on the start of a movie like they do with HDR, etc. SJ

Thanks for the update on this SJHT. I need to look at doing this.

John
 
Decided to write the extra code to track when the MX160 changes initially. Works great now and no more dropouts.

What did this involve? How do you distinguish “initial” changes from the pause/skip changes?

John
 
What did this involve? How do you distinguish “initial” changes from the pause/skip changes?

John

I had to write two events per audio type. One tracks the changes in audio type from the MX160 (e.g. DTS:X MA, 7.1.4), but instead of actually executing the needed MX160 post processing command, it instead just updates a state variable/key to what that changes was (e.g. DTS:X) . The second event tracks changes in that key/variable (DTS:X in my example) and executes the post processing command that I want. Since I have no events written for "no information" MX160 audio type, the post processing command doesn't execute again unless there was a real audio type change. Seems to work really well. I'm constantly switching post processing depending on the movie (e.g. Dolby Atmos I want set to NONE, but for DTS MA formats I liked to use DTS Neural:X). One less thing to think about! SJ
 
I had to write two events per audio type. One tracks the changes in audio type from the MX160 (e.g. DTS:X MA, 7.1.4), but instead of actually executing the needed MX160 post processing command, it instead just updates a state variable/key to what that changes was (e.g. DTS:X) . The second event tracks changes in that key/variable (DTS:X in my example) and executes the post processing command that I want. Since I have no events written for "no information" MX160 audio type, the post processing command doesn't execute again unless there was a real audio type change. Seems to work really well. I'm constantly switching post processing depending on the movie (e.g. Dolby Atmos I want set to NONE, but for DTS MA formats I liked to use DTS Neural:X). One less thing to think about! SJ

Thanks SJ! Sounds like this would work perfectly for Sripts too.

John
 
Back
Top