Graphics

 View Only
Expand all | Collapse all

Mosart to XPression

  • 1.  Mosart to XPression

    Posted 06-16-2023 06:34
    Anyone can help me out here?
    Moasart does'nt load fullscreen graphic on XPression
    Mosart would not load fullscreen graphic on XPRession.
    Probably a config thing, anoyone knows how to do?


    ------------------------------
    Tue Sandbæk
    Director / TV-Technician
    TV SYD
    ------------------------------


  • 2.  RE: Mosart to XPression

    Posted 06-16-2023 07:13

    The error says Take Item 0 does not exist. Do you have a take item 0? 



    ------------------------------
    Simon Redmile
    Senior Graphic Programmer & Designer
    Ross Video
    Bristol United Kingdom
    ------------------------------



  • 3.  RE: Mosart to XPression

    Posted 06-16-2023 07:51

    No, that's the problem.
    Mosart sends data to the XPression using the CII gateway.
    XPresion receives somthing, and creates a new line in the sequenzer, but not with 0 in take item.



    ------------------------------
    Tue Sandbæk
    Director / TV-Technician
    TV SYD
    ------------------------------



  • 4.  RE: Mosart to XPression

    Posted 06-16-2023 07:54

    The command is saying "0" 

     

    Show me the command which is creating the item? 



    ------------------------------
    Simon Redmile
    Senior Graphic Programmer & Designer
    Ross Video
    Bristol United Kingdom
    ------------------------------



  • 5.  RE: Mosart to XPression

    Posted 06-16-2023 08:22
    This should be were mosart sends commands to create the fullscreen graphic
    mosart sends create commands

    With an earlier version of XPression and Mosart we had no problem.
    Since we have upgraded both Xpression and Mosart we have had problems with fullscreen graphic.
    Don't know if it is a configuration in mosart or in xpression.

    Now I have testet with a newer version of mosart, and the old one, now I can't do it from any of them.
    Don't know if anyone have an explanation, or knows how to set it up?
    ------------------------------
    Tue Sandbæk
    Director / TV-Technician
    TV SYD
    ------------------------------



  • 6.  RE: Mosart to XPression

    Posted 06-16-2023 08:25

    So no item number "0" gets created in the sequence? 



    ------------------------------
    Simon Redmile
    Senior Graphic Programmer & Designer
    Ross Video
    Bristol United Kingdom
    ------------------------------



  • 7.  RE: Mosart to XPression

    Posted 06-16-2023 08:30

    No, first time, it's makes take id 5003 in the sequence.

    If I try again, it makes 5004 and so on.



    ------------------------------
    Tue Sandbæk
    Director / TV-Technician
    TV SYD
    ------------------------------



  • 8.  RE: Mosart to XPression

    Posted 06-16-2023 08:35

    So its making a item ID "0" from "5003"



    ------------------------------
    Simon Redmile
    Senior Graphic Programmer & Designer
    Ross Video
    Bristol United Kingdom
    ------------------------------



  • 9.  RE: Mosart to XPression

    Posted 06-16-2023 08:44

    NoMosart creates this in the sequence

    (this was before I tryed to rename, the scene number was 503)



    ------------------------------
    Tue Sandbæk
    Director / TV-Technician
    TV SYD
    ------------------------------



  • 10.  RE: Mosart to XPression

    Posted 06-16-2023 08:49

    So the lines MosArt is sending look something like this? 

    And you see in the sequence the item appear?



    ------------------------------
    Simon Redmile
    Senior Graphic Programmer & Designer
    Ross Video
    Bristol United Kingdom
    ------------------------------



  • 11.  RE: Mosart to XPression

    Posted 06-16-2023 09:03

    When we make overlay graphic, it looks like that, but not when I try to load a fullscreen.



    ------------------------------
    Tue Sandbæk
    Director / TV-Technician
    TV SYD
    ------------------------------



  • 12.  RE: Mosart to XPression

    Posted 06-16-2023 09:06

    What does the CII log say?



    ------------------------------
    Simon Redmile
    Senior Graphic Programmer & Designer
    Ross Video
    Bristol United Kingdom
    ------------------------------



  • 13.  RE: Mosart to XPression

    Posted 06-16-2023 09:25
      |   view attached

    Not very much more, i'm affraid of?

    I've collected the logs here.



    ------------------------------
    Tue Sandbæk
    Director / TV-Technician
    TV SYD
    ------------------------------

    Attachment(s)



  • 14.  RE: Mosart to XPression

    Posted 06-16-2023 10:07

    In all the instances I could see it was a problem with a scene ID 1003, is the a template number 1003? 



    ------------------------------
    Simon Redmile
    Senior Graphic Programmer & Designer
    Ross Video
    Bristol United Kingdom
    ------------------------------



  • 15.  RE: Mosart to XPression

    Posted 06-16-2023 10:52

    No, that is not the problem.

    From the log today you can see this, when I started this morning.

    *** xpciigateway v10.5 build 5535 started @ 16-06-23 03:02:22
    16-06-23 03:02:22.018: *** Started XPression CII Gateway v10.5 build 5535
    16-06-23 03:02:22.182: RS232 Port 1 was successfully opened.
    16-06-23 03:02:22.184: TCP Port 9090 was successfully opened.
    16-06-23 03:02:22.184: Gateway is up and running...
    16-06-23 09:20:04.648: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:20:10.563: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:21:04.656: noop...
    16-06-23 09:21:04.663: Client disconnected: 192.168.31.82
    16-06-23 09:21:04.692: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:21:10.706: noop...
    16-06-23 09:21:10.741: Client disconnected: 192.168.31.82
    16-06-23 09:21:10.769: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:22:05.036: noop...
    16-06-23 09:22:05.056: Client disconnected: 192.168.31.82
    16-06-23 09:22:05.087: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:22:11.080: noop...
    16-06-23 09:22:11.104: Client disconnected: 192.168.31.82
    16-06-23 09:22:11.133: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:23:05.498: noop...
    16-06-23 09:23:05.514: Client disconnected: 192.168.31.82
    16-06-23 09:23:05.544: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:23:11.555: noop...
    16-06-23 09:23:11.562: Client disconnected: 192.168.31.82
    16-06-23 09:23:11.590: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:24:06.031: noop...
    16-06-23 09:24:06.035: Client disconnected: 192.168.31.82
    16-06-23 09:24:06.065: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:24:12.072: noop...
    16-06-23 09:24:12.082: Client disconnected: 192.168.31.82
    16-06-23 09:24:12.111: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:25:06.510: noop...
    16-06-23 09:25:06.528: Client disconnected: 192.168.31.82
    16-06-23 09:25:06.559: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:25:12.561: noop...
    16-06-23 09:25:12.575: Client disconnected: 192.168.31.82
    16-06-23 09:25:12.604: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:26:06.968: noop...
    16-06-23 09:26:06.986: Client disconnected: 192.168.31.82
    16-06-23 09:26:07.016: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:26:13.006: noop...
    16-06-23 09:26:13.033: Client disconnected: 192.168.31.82
    16-06-23 09:26:13.062: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:27:07.494: noop...
    16-06-23 09:27:07.500: Client disconnected: 192.168.31.82
    16-06-23 09:27:07.521: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:27:09.488: Client disconnected: 192.168.31.82
    16-06-23 09:27:13.550: noop...
    16-06-23 09:27:13.568: Client disconnected: 192.168.31.82
    16-06-23 09:27:13.590: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:27:14.070: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:27:45.153: Incoming (raw): W\0\505\ \\
    16-06-23 09:27:45.153: Incoming: write page, source id: 505 target id: 0
    16-06-23 09:27:45.154: Executed: Created Take Item ID: 0 from Template ID: 505
    16-06-23 09:27:45.170: Client disconnected: 192.168.31.82
    16-06-23 09:27:45.191: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:27:48.192: Incoming (raw): X\RESUMEID\0\\
    16-06-23 09:27:48.192: Incoming: resume take id: 0
    16-06-23 09:27:48.193: Executed: Failed resuming Take Item ID: 0 (ID does not exist)
    16-06-23 09:27:48.196: Client disconnected: 192.168.31.82
    16-06-23 09:27:48.217: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:28:13.994: noop...
    16-06-23 09:28:14.006: Client disconnected: 192.168.31.82
    16-06-23 09:28:14.027: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:28:48.256: noop...
    16-06-23 09:28:48.271: Client disconnected: 192.168.31.82
    16-06-23 09:28:48.292: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:29:14.505: noop...
    16-06-23 09:29:14.524: Client disconnected: 192.168.31.82
    16-06-23 09:29:14.545: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:29:48.845: noop...
    16-06-23 09:29:48.851: Client disconnected: 192.168.31.82
    16-06-23 09:29:48.872: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:30:15.022: noop...
    16-06-23 09:30:15.037: Client disconnected: 192.168.31.82
    16-06-23 09:30:15.058: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:30:49.321: noop...
    16-06-23 09:30:49.329: Client disconnected: 192.168.31.82
    16-06-23 09:30:49.350: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:30:50.788: Incoming (raw): W\0\505\ \\
    16-06-23 09:30:50.788: Incoming: write page, source id: 505 target id: 0
    16-06-23 09:30:50.789: Executed: Created Take Item ID: 0 from Template ID: 505
    16-06-23 09:30:50.790: Client disconnected: 192.168.31.82
    16-06-23 09:30:50.811: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:31:15.555: noop...
    16-06-23 09:31:15.558: Client disconnected: 192.168.31.82
    16-06-23 09:31:15.579: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:31:27.660: Incoming (raw): W\0\503\ \\
    16-06-23 09:31:27.660: Incoming: write page, source id: 503 target id: 0
    16-06-23 09:31:27.662: Executed: Created Take Item ID: 0 from Template ID: 503
    16-06-23 09:31:27.663: Client disconnected: 192.168.31.82
    16-06-23 09:31:27.684: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:31:30.728: Incoming (raw): X\READ\0\1\\
    16-06-23 09:31:30.728: Incoming: read page take id: 0 (channel: 1)
    16-06-23 09:31:30.729: Executed: Failed reading Take Item ID: 0 (ID does not exist)
    16-06-23 09:31:30.735: Client disconnected: 192.168.31.82
    16-06-23 09:31:30.756: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:32:16.048: noop...
    16-06-23 09:32:16.071: Client disconnected: 192.168.31.82
    16-06-23 09:32:16.093: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:32:31.185: noop...
    16-06-23 09:32:31.200: Client disconnected: 192.168.31.82
    16-06-23 09:32:31.222: Client connected over TCP, address: 192.168.31.82
    16-06-23 09:33:16.507: noop...

    As you can see there is also problems with connecting and disconnecting all the time.

    From yesterday is an example when running a show, but this is only overlays from mosart.

    15-06-23 17:10:36.772: Incoming (raw): X\CLEAR\1\\
    15-06-23 17:10:36.773: Incoming: clear channel
    15-06-23 17:10:36.773: Clear channel: 1
    15-06-23 17:10:36.793: Incoming (raw): X\CLEAR\2\\
    15-06-23 17:10:36.793: Incoming: clear channel
    15-06-23 17:10:36.793: Clear channel: 2
    15-06-23 17:10:36.814: Incoming (raw): X\CLEAR\3\\
    15-06-23 17:10:36.814: Incoming: clear channel
    15-06-23 17:10:36.814: Clear channel: 3
    15-06-23 17:10:36.856: Incoming (raw): W\1192\100\Mark Bundgaard\mabu@tvsyd.dk\\
    15-06-23 17:10:36.856: Incoming: write page, source id: 100 target id: 1192
    15-06-23 17:10:36.857: Executed: Created Take Item ID: 1192 from Template ID: 100
    15-06-23 17:10:37.209: Incoming (raw): W\1193\602\f163.png\\
    15-06-23 17:10:37.209: Incoming: write page, source id: 602 target id: 1193
    15-06-23 17:10:37.210: Executed: Created Take Item ID: 1193 from Template ID: 602
    15-06-23 17:10:37.231: Incoming (raw): W\1194\200\Skrydstrup\Danmark l<C3><A6>gger op til at tr<C3><A6>ne ukrainske piloter\\
    15-06-23 17:10:37.231: Incoming: write page, source id: 200 target id: 1194
    15-06-23 17:10:37.231: Executed: Created Take Item ID: 1194 from Template ID: 200
    15-06-23 17:10:37.253: Incoming (raw): W\1195\602\vind3.png\\
    15-06-23 17:10:37.253: Incoming: write page, source id: 602 target id: 1195
    15-06-23 17:10:37.254: Executed: Created Take Item ID: 1195 from Template ID: 602
    15-06-23 17:10:37.283: Incoming (raw): W\1196\200\Esbjerg\Vindm<C3><B8>ller smadrer nattes<C3><B8>vnen\\
    15-06-23 17:10:37.283: Incoming: write page, source id: 200 target id: 1196
    15-06-23 17:10:37.283: Executed: Created Take Item ID: 1196 from Template ID: 200
    15-06-23 17:10:37.306: Incoming (raw): W\1197\100\Michael Tang Madsen\Hotlinekonsulent, Tj<C3><A6>reborg\\
    15-06-23 17:10:37.306: Incoming: write page, source id: 100 target id: 1197
    15-06-23 17:10:37.307: Executed: Created Take Item ID: 1197 from Template ID: 100
    15-06-23 17:10:37.329: Incoming (raw): W\1198\701\ADRESSESKILT\\
    15-06-23 17:10:37.329: Incoming: write page, source id: 701 target id: 1198
    15-06-23 17:10:37.330: Executed: Created Take Item ID: 1198 from Template ID: 701
    15-06-23 17:10:37.351: Incoming (raw): W\1199\104\Ellen Nybo\Vejrv<C3><A6>rt\\
    15-06-23 17:10:37.351: Incoming: write page, source id: 104 target id: 1199
    15-06-23 17:10:37.352: Executed: Created Take Item ID: 1199 from Template ID: 104
    15-06-23 17:11:00.471: noop...
    15-06-23 17:11:37.686: noop...
    15-06-23 17:12:00.829: noop...
    15-06-23 17:12:38.099: noop...
    15-06-23 17:12:46.992: Incoming (raw): X\READ\1192\1\\
    15-06-23 17:12:46.992: Incoming: read page take id: 1192 (channel: 1)
    15-06-23 17:12:46.994: Executed: Read Take Item ID: 1192 onto Channel: 1
    15-06-23 17:12:48.912: Incoming (raw): X\RESUMEID\1192\\
    15-06-23 17:12:48.912: Incoming: resume take id: 1192
    15-06-23 17:12:48.915: Executed: Take Item ID: 1192 was resumed.
    15-06-23 17:12:49.003: Incoming (raw): X\READ\1193\3\\
    15-06-23 17:12:49.003: Incoming: read page take id: 1193 (channel: 3)
    15-06-23 17:12:49.122: Executed: Read Take Item ID: 1193 onto Channel: 3
    15-06-23 17:12:49.143: Incoming (raw): X\READ\1194\1\\
    15-06-23 17:12:49.143: Incoming: read page take id: 1194 (channel: 1)
    15-06-23 17:12:49.167: Executed: Read Take Item ID: 1194 onto Channel: 1
    15-06-23 17:12:50.531: Incoming (raw): W\1193\602\f163.png\\
    15-06-23 17:12:50.531: Incoming: write page, source id: 602 target id: 1193
    15-06-23 17:12:50.531: Executed: Created Take Item ID: 1193 from Template ID: 602
    15-06-23 17:12:50.553: Incoming (raw): W\1194\200\Skrydstrup\Danmark l<C3><A6>gger op til at tr<C3><A6>ne ukrainske piloter\\
    15-06-23 17:12:50.553: Incoming: write page, source id: 200 target id: 1194
    15-06-23 17:12:50.553: Executed: Created Take Item ID: 1194 from Template ID: 200
    15-06-23 17:12:50.920: Incoming (raw): X\TAKEOFFLINE\1192\\
    15-06-23 17:12:50.920: Incoming: take offline take id: 1192
    15-06-23 17:12:50.925: Executed: Take Item ID: 1192 was taken offline.
    15-06-23 17:12:57.074: Incoming (raw): X\READ\1195\3\\
    15-06-23 17:12:57.075: Incoming: read page take id: 1195 (channel: 3)
    15-06-23 17:12:57.136: Executed: Read Take Item ID: 1195 onto Channel: 3
    15-06-23 17:13:01.252: noop...
    15-06-23 17:13:19.476: Incoming (raw): X\RESUMEID\1194\\
    15-06-23 17:13:19.476: Incoming: resume take id: 1194
    15-06-23 17:13:19.485: Executed: Take Item ID: 1194 was resumed.
    15-06-23 17:13:19.550: Incoming (raw): X\READ\1195\3\\
    15-06-23 17:13:19.550: Incoming: read page take id: 1195 (channel: 3)
    15-06-23 17:13:19.551: Executed: Read Take Item ID: 1195 onto Channel: 3
    15-06-23 17:13:19.573: Incoming (raw): X\READ\1196\1\\
    15-06-23 17:13:19.573: Incoming: read page take id: 1196 (channel: 1)
    15-06-23 17:13:19.583: Executed: Read Take Item ID: 1196 onto Channel: 1
    15-06-23 17:13:21.021: Incoming (raw): W\1195\602\vind3.png\\
    15-06-23 17:13:21.021: Incoming: write page, source id: 602 target id: 1195
    15-06-23 17:13:21.022: Executed: Created Take Item ID: 1195 from Template ID: 602
    15-06-23 17:13:21.044: Incoming (raw): W\1196\200\Esbjerg\Vindm<C3><B8>ller smadrer nattes<C3><B8>vnen\\
    15-06-23 17:13:21.044: Incoming: write page, source id: 200 target id: 1196
    15-06-23 17:13:21.044: Executed: Created Take Item ID: 1196 from Template ID: 200
    15-06-23 17:13:21.474: Incoming (raw): X\TAKEOFFLINE\1194\\
    15-06-23 17:13:21.474: Incoming: take offline take id: 1194
    15-06-23 17:13:21.475: Executed: Take Item ID: 1194 was taken offline.
    15-06-23 17:13:28.571: Incoming (raw): W\1195\602\vind3.png\\
    15-06-23 17:13:28.571: Incoming: write page, source id: 602 target id: 1195
    15-06-23 17:13:28.571: Executed: Created Take Item ID: 1195 from Template ID: 602
    15-06-23 17:13:28.592: Incoming (raw): W\1196\200\Esbjerg\Vindm<C3><B8>ller smadrer nattes<C3><B8>vnen\\
    15-06-23 17:13:28.592: Incoming: write page, source id: 200 target id: 1196
    15-06-23 17:13:28.592: Executed: Created Take Item ID: 1196 from Template ID: 200
    15-06-23 17:13:54.613: Incoming (raw): X\RESUMEID\1196\\
    15-06-23 17:13:54.613: Incoming: resume take id: 1196
    15-06-23 17:13:54.614: Executed: Take Item ID: 1196 was resumed.
    15-06-23 17:13:56.612: Incoming (raw): X\TAKEOFFLINE\1196\\
    15-06-23 17:13:56.612: Incoming: take offline take id: 1196
    15-06-23 17:13:56.613: Executed: Take Item ID: 1196 was taken offline.
    15-06-23 17:13:57.600: Incoming (raw): X\READ\1197\1\\
    15-06-23 17:13:57.600: Incoming: read page take id: 1197 (channel: 1)
    15-06-23 17:13:57.602: Executed: Read Take Item ID: 1197 onto Channel: 1
    15-06-23 17:14:01.703: noop...
    15-06-23 17:14:02.613: Incoming (raw): X\RESUMEID\1197\\
    15-06-23 17:14:02.613: Incoming: resume take id: 1197
    15-06-23 17:14:02.613: Executed: Take Item ID: 1197 was resumed.
    15-06-23 17:14:04.609: Incoming (raw): X\TAKEOFFLINE\1197\\
    15-06-23 17:14:04.609: Incoming: take offline take id: 1197
    15-06-23 17:14:04.611: Executed: Take Item ID: 1197 was taken offline.
    15-06-23 17:14:36.693: Incoming (raw): X\READ\1198\1\\
    15-06-23 17:14:36.693: Incoming: read page take id: 1198 (channel: 1)
    15-06-23 17:14:36.695: Executed: Read Take Item ID: 1198 onto Channel: 1
    15-06-23 17:14:38.197: Incoming (raw): W\1198\701\ADRESSESKILT\\
    15-06-23 17:14:38.197: Incoming: write page, source id: 701 target id: 1198
    15-06-23 17:14:38.197: Executed: Created Take Item ID: 1198 from Template ID: 701
    15-06-23 17:14:39.346: Incoming (raw): X\RESUMEID\1198\\
    15-06-23 17:14:39.346: Incoming: resume take id: 1198
    15-06-23 17:14:39.347: Executed: Take Item ID: 1198 was resumed.
    15-06-23 17:14:41.350: Incoming (raw): X\TAKEOFFLINE\1198\\
    15-06-23 17:14:41.351: Incoming: take offline take id: 1198
    15-06-23 17:14:41.351: Executed: Take Item ID: 1198 was taken offline.
    15-06-23 17:15:02.251: noop...
    15-06-23 17:15:04.019: Incoming (raw): W\1199\104\Ellen Nybo\Vejrv<C3><A6>rt\\
    15-06-23 17:15:04.020: Incoming: write page, source id: 104 target id: 1199
    15-06-23 17:15:04.021: Executed: Created Take Item ID: 1199 from Template ID: 104
    15-06-23 17:15:04.643: Incoming (raw): X\READ\1199\1\\
    15-06-23 17:15:04.644: Incoming: read page take id: 1199 (channel: 1)
    15-06-23 17:15:04.647: Executed: Read Take Item ID: 1199 onto Channel: 1
    15-06-23 17:15:09.648: Incoming (raw): X\RESUMEID\1199\\
    15-06-23 17:15:09.648: Incoming: resume take id: 1199
    15-06-23 17:15:09.649: Executed: Take Item ID: 1199 was resumed.
    15-06-23 17:15:11.652: Incoming (raw): X\TAKEOFFLINE\1199\\
    15-06-23 17:15:11.652: Incoming: take offline take id: 1199
    15-06-23 17:15:11.654: Executed: Take Item ID: 1199 was taken offline.
    15-06-23 17:16:02.793: noop...

    Then there is no problem.



    ------------------------------
    Tue Sandbæk
    Director / TV-Technician
    TV SYD
    ------------------------------



  • 16.  RE: Mosart to XPression

    Posted 06-16-2023 13:39

    I see, looks like a communication issue, have you called our tech support to connect to your machine and check it? 



    ------------------------------
    Simon Redmile
    Senior Graphic Programmer & Designer
    Ross Video
    Bristol United Kingdom
    ------------------------------



  • 17.  RE: Mosart to XPression

    Posted 06-16-2023 14:47

    No, I have not repported it to your tech support.
    Would that be better 2 make a ticket there?



    ------------------------------
    Tue Sandbæk
    Director / TV-Technician
    TV SYD
    ------------------------------



  • 18.  RE: Mosart to XPression

    Posted 06-16-2023 16:43

    This looks like either a bug in XPression...or...XPression isn't supposed to support Take Items with Take ID 0 at all. XPression always fails to create Take Items with Take ID 0 from CII commands.

     Whenever a write command using target ID 0 is used, XPression creates a take item with the same take ID as the source ID (scene ID). If you use any target ID besides 0, it always works correctly. 

    It could be a bug, but I think its more likely that Take Items with Take ID 0 are just not supported and shouldn't be possible to create at all. You'll notice that the Fast Recall system also fails to trigger Take ID 0 correctly as well. Can you use something other than Target ID 0 for your Mosart workflow? 

    Here is a example of how XPression corrects the wrong Take Item from the write command when the target ID is 0, but then functions correctly when the target ID is not 0. 

    These CII commands should have created Take ID 0 and Take ID 2 - both from scene # 5003. But instead the command using target ID 0, messes up and creates a Take ID matching the scene ID (5003). 




  • 19.  RE: Mosart to XPression

    Posted 06-16-2023 17:18

    I don't know if I can change what mosart uses, not sure how or where…

    How can XPression correct it?

    I don't know where there is a bug or config error, but seems something is wrong on either Mosart or Xpression, but can't find it…



    ------------------------------
    Tue Sandbæk
    Director / TV-Technician
    TV SYD
    ------------------------------



  • 20.  RE: Mosart to XPression

    Posted 06-16-2023 17:28

    Currently this is a bug or limitation of XPression, it won't be possible to correct on the XPression side without a new build of XPression. It looks like you are on 10.5 5535. I will investigate if this is something we can change.

    I think the fastest solution right now will be to change Mosart so that it doesn't use Target ID 0. 

    We can see from your logs that Mosart does use other target IDs, so it must be possible to change it from using target ID 0. 

    15-06-23 17:10:36.856: Incoming (raw): W\1192\100\Mark Bundgaard\mabu@tvsyd.dk\\
    15-06-23 17:10:36.856: Incoming: write page, source id: 100 target id: 1192
    15-06-23 17:10:36.857: Executed: Created Take Item ID: 1192 from Template ID: 100
    15-06-23 17:10:37.209: Incoming (raw): W\1193\602\f163.png\\
    15-06-23 17:10:37.209: Incoming: write page, source id: 602 target id: 1193
    15-06-23 17:10:37.210: Executed: Created Take Item ID: 1193 from Template ID: 602
    15-06-23 17:10:37.231: Incoming (raw): W\1194\200\Skrydstrup\Danmark l<C3><A6>gger op til at tr<C3><A6>ne ukrainske piloter\\
    15-06-23 17:10:37.231: Incoming: write page, source id: 200 target id: 1194
    15-06-23 17:10:37.231: Executed: Created Take Item ID: 1194 from Template ID: 200
    15-06-23 17:10:37.253: Incoming (raw): W\1195\602\vind3.png\\



  • 21.  RE: Mosart to XPression

    Posted 06-16-2023 17:50

    That's right, when mosart send commands for overlay graphic it's working, but when trying fullscreen, it doen't work.

    Back in june 2022 we upgraded from an older version of XPression, to a 10.0 as I remember.

    Since then, we have not been able to load fullscreen.

    Don’t know if anything changed since ver. 9 or what we upgraded from.



    ------------------------------
    Tue Sandbæk
    Director / TV-Technician
    TV SYD
    ------------------------------