IMS3000 Multiple Cues Not Aplicable.

[Shibu Paul]

Hi All,
I created a playlist on the IMS3000 server, added 5 seconds of black to it, and then inserted a 5.5-second fader cue. Similarly, I added another 5.5-second fader cue to a different piece of content within the same playlist. However, the second 5.5 fader cue appears in the first content instead. This issue only occurs on the IMS3000.

Are identical cues (e.g., multiple 5.5-second fader cues) not applicable within the same playlist? Could that be causing the issue?

Is anyone else facing the same problem? Images are attached.

[Ryan Gallagher]

Reads like a bug. what version is IMS on?

(Don’t have an IMS3000 to play with)

But, The language of the UI makes it seem like for whatever reason they are triggering off the CPL time code, and not uniquing the automation even to the SPL instance of that CPL.

Try putting the second one at 1sec and see if they are both still firing on the first black? (Just a test)

Try making the second black a different length to see if that splits them enough to cause unique behavior?

Also, for grins, try making your black long enough to cover the whole fader event? (Doubt this will change anything)

[Ryan Gallagher]

Apologies, I read your first post as putting the fader cue on two identical 5 sec blacks. But I see you mentioned the 2nd fader cue one is on a different piece of content but it attached to the first instead. Somewhat nullified my first suggestions.

Can you move the fader cue after it is created up or down the SPL? (I know doremi has that UI).

Basically, is it only placing it wrong at creation time, or it stuck on the wrong CPL item and unable to correct?

Are your fader cues using a built in library or are they macros you made to non-standard processors?

[Dave Macaulay]

I don't know what's happening to you - but multiple identical cues placed in different clips, black or CPLs, work fine for me. The IMS3000 has pretty much identical software to a CCP/SV but doesn't have a video console so no VNC, the webGUI is super similar though. Except for the optional audio processing of course.

[Shibu Paul]

In addition to using the standard library queues, we also use our own custom queues. The problem is that the same queues are being applied to different content within a single playlist. After checking the queues used in the last CPL in the playlist, the interface still shows the queues used for the first piece of content.playback mode some time not exicute the cues from 2nd one.

[Ryan Gallagher]

In addition to using the standard library queues, we also use our own custom queues. The problem is that the same queues are being applied to different content within a single playlist. After checking the queues used in the last CPL in the playlist, the interface still shows the queues used for the first piece of content.playback mode some time not exicute the cues from 2nd one.

Would help if you share what software version the IMS3000 is running. Perhaps some better screenshots. The one you shared only shows you creating a single automation event, and not the result you are describing. Are your fader cues for the internal audio handling, or an external processor?

Your last post make it sound like this behavior is even happening on your custom cues too, not just the fader cues.

Is it possibly user error? I know I often drop cues on the wrong CPL if I'm not careful about which item in the SPL is highlighted when I start the process.

[Dave Macaulay]

I have seen a situation where in trying to use eth2 for Atmos data two CP950 devices were set up: one RAW and one "sound processor" Trying to use the RAW for commands and pointing the CP950 Atmos data port at the "sound processor" with both on the same CP950 IP address (they have to be). Neither worked. No command success, no Atmos. Went back to just the sound processor device only, using management network for commands and Atmos data. That worked. I did see a single Atmos data error where a frame was skipped but nothing since that one after a full show.