Closed CasparCGImport closed 11 years ago
Submitted by nirklas
Thank you for reporting a CasparCG bug!
Please read through these tips for useful bug reports, and feel free to add more to your report!
When Reporting a Bug - please provide the log file! The log is found in the log folder configured in the casparcg.config file.
Please list as many details of your system, version and what you are trying to do and how the bug manifests itself. In order for us to be able to help you, please describe what you are trying to do, what happens and what you expected to happen.
Here are some examples of the minimum amount of info we need:
Please attach screenshots, screen capture videos, the files you are using, and more which show your problems and/or what you are trying to accomplish. Please provide the log file (found in the log folder configured in the casparcg.config settings file) and put it inside code tags.
Our mind-reading abilities are limited, so the more you can tell us, the greater the chance that someone will be able to help you!
Submitted by nirklas
Sending linefeed-characters instead of linefeeds encoded as "\n" is actually the desired behavior. That way all xml returned from caspar is serialized the same way (xml in reply to info-commands for instance is already serialized like this).
Converted from SourceForge issue 3599247, submitted by None
For V203.3590 I found out that in the server log the send messages (as reply on DATA RETRIEVE) are the same containing \n (for new line). But tracing the ip contents (wireshark) these \n ('x5C6E as in V202.2592) is missing and replaced by LF ('x0A).
caspar-log (both versions log the same!) [12/21/12 12:13:29] [0C882BD8] [info] Sent message to 192.168.178.26: #\n#c:info\nc:version\n#f:news\n\n\r\n
wireshark trace 203.3590 0000 00 16 0a 07 d3 7d 84 8f 69 b0 bb 32 08 00 45 00 .....}.. i..2..E. 0010 00 53 18 ed 40 00 80 06 fc 25 c0 a8 b2 26 c0 a8 .S..@... .%...&.. 0020 b2 1a 14 82 b3 84 bc 40 d9 6a 62 fa ce 43 80 18 .......@ .jb..C.. 0030 01 04 f6 d2 00 00 01 01 08 0a 00 02 28 0d 00 2c ........ ....(.., 0040 15 ca 23 0a 23 63 3a 69 6e 66 6f 0a 63 3a 76 65 ..#.#c:i nfo.c:ve 0050 72 73 69 6f 6e 0a 23 66 3a 6e 65 77 73 0a 0a 0d rsion.#f :news... 0060 0a
wireshark trace 202 0000 00 16 0a 07 d3 7d 84 8f 69 b0 bb 32 08 00 45 00 .....}.. i..2..E. 0010 00 56 16 99 40 00 80 06 fe 76 c0 a8 b2 26 c0 a8 .V..@... .v...&.. 0020 b2 1a 14 82 b3 5e 87 dc 15 16 69 b9 4e ad 80 18 .....^.. ..i.N... 0030 01 04 07 b7 00 00 01 01 08 0a 00 01 cd e5 00 2b ........ .......+ 0040 34 66 23 5c 6e 23 63 3a 69 6e 66 6f 5c 6e 63 3a 4f#\n#c: info\nc: 0050 76 65 72 73 69 6f 6e 5c 6e 23 66 3a 6e 65 77 73 version\ n#f:news 0060 5c 6e 0d 0a \n..