Verify remote HTTP and cue list functionality
Moderator: MADRIX Team
Verify remote HTTP and cue list functionality
Hello Madrix team. Excellent work on 3.0!
I am part of a small team developing a permanent installation driven by Madrix software. Your current release candidate works exactly as we want it to(!), and I just want to ask if our workflow will continue to function once you finalize your 3.0 release. We are building an interactive systembased on your excellent HTTP remote control, so we have to make sure everything is stable before we deploy.
Our installation is made of hundreds of short video clips, each one loaded into its own "storage place", and with all storage spaces added to a giant cue list. Each cue has a duration set to 30 seconds, and when we play the cue list, each clip plays in order until the cue list loops back to the beginning. So far so good.
We want a user to be able to select a single video using a web interface, which will play when they click on it, then return the system back to its cue list loop. Right now we're accomplishing that by sending a SetStorage command when the user clicks a link, and then 30 seconds later the system sends a SetCueListPlay command to start the cue list back up. So the system is on an eternal loop, then it plays one clip when a user clicks it, an finally returns to where it left off in the eternal loop.
It works perfectly an we love it! Do you intend to keep the cue list behavior the same for the final release? And if not, is there another way we can have the same final result?
Thank you for your time, and for maintaining this excellent software.
--David
I am part of a small team developing a permanent installation driven by Madrix software. Your current release candidate works exactly as we want it to(!), and I just want to ask if our workflow will continue to function once you finalize your 3.0 release. We are building an interactive systembased on your excellent HTTP remote control, so we have to make sure everything is stable before we deploy.
Our installation is made of hundreds of short video clips, each one loaded into its own "storage place", and with all storage spaces added to a giant cue list. Each cue has a duration set to 30 seconds, and when we play the cue list, each clip plays in order until the cue list loops back to the beginning. So far so good.
We want a user to be able to select a single video using a web interface, which will play when they click on it, then return the system back to its cue list loop. Right now we're accomplishing that by sending a SetStorage command when the user clicks a link, and then 30 seconds later the system sends a SetCueListPlay command to start the cue list back up. So the system is on an eternal loop, then it plays one clip when a user clicks it, an finally returns to where it left off in the eternal loop.
It works perfectly an we love it! Do you intend to keep the cue list behavior the same for the final release? And if not, is there another way we can have the same final result?
Thank you for your time, and for maintaining this excellent software.
--David
Re: Verify remote HTTP and cue list functionality
hi bfam,
sounds fantastic what you have done!
.
The most things in MADRIX 3 will keep the same as like as in MADRIX 2 except the parts which have to change.
So i am almost sure the control of the cuelist didn´t changed.
But to switch a storage place we have to change something because in MADRIX 2 there only exists 2 Storages with 60 Places each.
Now we talk about 256 Storages with 256 Places each.
So please check the documentation of the final release what you have to adapt in your http remote commands to get the same result.
.
THX
sounds fantastic what you have done!
.
The most things in MADRIX 3 will keep the same as like as in MADRIX 2 except the parts which have to change.
So i am almost sure the control of the cuelist didn´t changed.
But to switch a storage place we have to change something because in MADRIX 2 there only exists 2 Storages with 60 Places each.
Now we talk about 256 Storages with 256 Places each.
So please check the documentation of the final release what you have to adapt in your http remote commands to get the same result.
.
THX
LEDs are nothing without control 