CESNET / UltraGrid

UltraGrid low-latency audio and video network transmission system
http://www.ultragrid.cz
Other
492 stars 53 forks source link

Scrambled logs with current continous build #256

Closed maybites closed 1 year ago

maybites commented 1 year ago

Hi

I have been using ultragrid with MaxMSP with the shell abstraction and this works just fine, including the printout for the console log ultragrid produces.

But with the current continuous builds the console logout get scrambled (both on windows and OSX):

print: UltraGrid 1.7+ (tags/continuous rev a3c3e339 built Sep 26 2022 12:19:24)
print: Display device : ndi
print: Capture device : syphon
print: Audio capture : none
print: Audio playback : none
print: MTU : 9000 B
print: Video compression: none
print: Audio codec : PCM
print: Network protocol : UltraGrid RTP
print: Audio FEC : none
print: Video FEC : none
print: This application uses NDI® available from http://ndi.tv/
print: NDI® is a registered trademark of NewTek, Inc.
print: Display initialized-ndi
print: Video capture initialized-syphon
print: Created new RTP session with SSRC 977703241.
print: [Syphon capture] FPS set to 60. Use override_fps to override if you know FPS of the server.
print: [Syphon capture] Using server - app: Simple Server name: 
print: [video dec.] New incoming video format detected: 420x900 @60.00p, codec UYVY
print: [video dec.] Successfully reconfigured display to 420x900 @60.00p, codec UYVY
print: [Syphon capture] 286 frames in 5.00013 seconds = 57.1985 FPS
print: [ndi] 286 frames in 5.01932 seconds = 56.9798 FPS
print: SSRC 0x3a469149: 25984/25984 packets received (100.0000%), 0 lost, max loss 0

This only happens when I run ultragrid within the shell object, but NOT inside the terminal or the cmd-tool.

And it doesn't happen with the most current official release.

maybites commented 1 year ago

Obviously this problem is very specific and not of high relevance for the development of ultragrid. I could imagine that the continuous build somehow differs from the official releases. I am just hoping for a confirmation in this direction :-)

mpiatka commented 1 year ago

Hi,

those strange symbols are the ANSI escape codes that are used for text formatting (colored output, boldness, etc.). It looks like the shell plugin doesn't support them. We recently switched away from the library rang to a simpler solution which doesn't check the terminal emulator against a whitelist, which is probably why it doesn't happen on the stable release.

As a workaround I've just added the parameter --param log-nocolor which will completely disable ANSI formatting.

maybites commented 1 year ago

many thanks.