Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing audio transfer via RTMP in Majestic #93

Open
ystinia opened this issue Jan 6, 2023 · 18 comments
Open

Testing audio transfer via RTMP in Majestic #93

ystinia opened this issue Jan 6, 2023 · 18 comments
Labels
enhancement New feature or request majestic

Comments

@ystinia
Copy link
Member

ystinia commented Jan 6, 2023

I tried a few audio broadcast tests today and they were unsuccessful.
Authorization when transmitting to the server is disabled here (another Nimble).

Device: HI3516EV300

audio:
  enabled: true
  volume: auto
  codec: aac 
  srate: 48000
16:48:56  <       majestic> [    rtmp] log_rtmp@59                   HandleInvoke, onStatus: NetStream.Publish.Start
16:48:56  <       majestic> [    rtmp] try_connect@296               Connection to rtmp://159.223.19.145:1935/openipc successful
16:48:56  <  thread-pool-0> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=47, size=189, ts=0
16:48:56  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=47, size=46, ts=0
16:48:56  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=47, size=96745, ts=0
16:48:56  <       majestic> [    rtmp] log_rtmp@59                   WriteN, RTMP send error 32 (244 bytes)
16:48:56  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=47, size=33, ts=0
16:48:56  <       majestic> [    rtmp] log_rtmp@59                   WriteN, RTMP send error 32 (41 bytes)
16:48:56  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=-1, size=34, ts=0
16:48:56  <       majestic> [    rtmp] log_rtmp@59                   WriteN, RTMP send error 9 (42 bytes)
16:48:56  <       majestic> [rtmp-str] nal_cb@604                    RTMP stream disconnected
16:48:56  <  thread-pool-1> [rtmp-str] audio_cb@704                  Audio: RTMP stream disconnected
16:48:56  <       majestic> [    rtmp] try_connect@246               Connecting to RTMP URL rtmp://159.223.19.145:1935/openipc...
@widgetii
Copy link
Member

widgetii commented Jan 6, 2023

It would be very helpful to get error messages from the server side when it refuses the stream with audio

@ystinia
Copy link
Member Author

ystinia commented Jan 6, 2023

Device: T31X

audio:
  enabled: true
  volume: auto
  codec: aac 
  srate: 48000

We were unable to run the tests on the Ingenic device.
When selecting the AAC codec we get an error message.
It may be worth opening a separate ticket in the future.

root@openipc-t31:~# majestic
18:37:02  <       majestic> [    main] main@125                      Majestic Lite for Ingenic, version HEAD+3c84a34, built on 2023-01-05
18:37:02  <       majestic> [app_conf] load_config@89                Using /etc/majestic.yaml as main configuration
18:37:02  <       majestic> [app_conf] parse_app_config@282          Main audio codec is aac (other options: opus, pcm, alaw, ulaw)
18:37:02  <       majestic> [watchdog] watchdog_start@101            Detected jz Watchdog
18:37:02  <       majestic> [watchdog] watchdog_start@121            Watchdog timeout set to 30 seconds
18:37:02  <       majestic> [     sdk] try_sensor_config@172         SENSOR=sc5235
18:37:02  <       majestic> [     sdk] start_sdk@997                 Using sc5235 sensor
18:37:02  <       majestic> [     sdk] start_sdk@1079                CPU T31-ZX, SDK SYSUTILS-1.1.4, model Swan, devID 14994a08
---- FPGA board is ready ----
  Board UID : 30AB6E51
  Board HW ID : 72000460
  Board rev.  : 5DE5A975
  Board date  : 20190326
-----------------------------
18:37:02  <       majestic> [     sdk] imp_system_init@362           ImpSystemInit success
18:37:02  <       majestic> [     osd] init_osd@85                   OSD initialized
18:37:02  <       majestic> [   audio] init_audio_in@97              set ai 1 attr err: -1
18:37:02  <       majestic> [     sdk] start_sdk@1183                Failed to init audio.
18:37:02  <       majestic> [    main] main@209                      Shutdown main thread


@ystinia
Copy link
Member Author

ystinia commented Jan 6, 2023

It would be very helpful to get error messages from the server side when it refuses the stream with audio

Okay, I'll try to get the admin to give me the data.

@widgetii
Copy link
Member

widgetii commented Jan 6, 2023

Device: T31X

audio:
  enabled: true
  volume: auto
  codec: aac 
  srate: 48000

We were unable to run the tests on the Ingenic device. When selecting the AAC codec we get an error message. It may be worth opening a separate ticket in the future.

root@openipc-t31:~# majestic
18:37:02  <       majestic> [    main] main@125                      Majestic Lite for Ingenic, version HEAD+3c84a34, built on 2023-01-05
18:37:02  <       majestic> [app_conf] load_config@89                Using /etc/majestic.yaml as main configuration
18:37:02  <       majestic> [app_conf] parse_app_config@282          Main audio codec is aac (other options: opus, pcm, alaw, ulaw)
18:37:02  <       majestic> [watchdog] watchdog_start@101            Detected jz Watchdog
18:37:02  <       majestic> [watchdog] watchdog_start@121            Watchdog timeout set to 30 seconds
18:37:02  <       majestic> [     sdk] try_sensor_config@172         SENSOR=sc5235
18:37:02  <       majestic> [     sdk] start_sdk@997                 Using sc5235 sensor
18:37:02  <       majestic> [     sdk] start_sdk@1079                CPU T31-ZX, SDK SYSUTILS-1.1.4, model Swan, devID 14994a08
---- FPGA board is ready ----
  Board UID : 30AB6E51
  Board HW ID : 72000460
  Board rev.  : 5DE5A975
  Board date  : 20190326
-----------------------------
18:37:02  <       majestic> [     sdk] imp_system_init@362           ImpSystemInit success
18:37:02  <       majestic> [     osd] init_osd@85                   OSD initialized
18:37:02  <       majestic> [   audio] init_audio_in@97              set ai 1 attr err: -1
18:37:02  <       majestic> [     sdk] start_sdk@1183                Failed to init audio.
18:37:02  <       majestic> [    main] main@209                      Shutdown main thread

I guess it doesn't support srate: 48000

@ystinia
Copy link
Member Author

ystinia commented Jan 6, 2023

It would be very helpful to get error messages from the server side when it refuses the stream with audio

I hope this helps to understand the problem

[2023-01-06 17:01:33 P359917-T359932] [rtmp] E: [AM] aac data MUST follow aac sequence header
[2023-01-06 17:01:34 P359917-T359932] [rtmp] E: [AM] aac data MUST follow aac sequence header
[2023-01-06 17:01:35 P359917-T359932] [rtmp] E: [VM] AVC SEQUENCE header is required first for 'openipc/openipc'
[2023-01-06 17:01:35 P359917-T359932] [rtmp] E: [AM] aac data MUST follow aac sequence header
[2023-01-06 17:01:36 P359917-T359932] [rtmp] E: [VM] AVC SEQUENCE header is required first for 'openipc/openipc'
[2023-01-06 17:01:36 P359917-T359932] [rtmp] E: [AM] aac data MUST follow aac sequence header
[2023-01-06 17:01:36 P359917-T359932] [rtmp] E: [AM] aac data MUST follow aac sequence header

@widgetii
Copy link
Member

widgetii commented Jan 6, 2023

Can you provide RTMP URL for streaming again?

@ZigFisher
Copy link

Wow, you have a heated movement here... ;)

My progress is a little more modest.
When trying to transfer RTMP from audio to the MIST server, Majestic works,
but the video cannot be played on the remote side. It says this error:

The player has encountered a problem
CHUNK_DEMUXER_ERROR_APPEND_FAILED: Append: stream parsing failed. Data size=1235 append_window_start=0 append_window_end=inf

I think this is the same problem...

@ystinia
Copy link
Member Author

ystinia commented Jan 6, 2023

I guess it doesn't support srate: 48000

Thank you so much for the tip
Yes, using the default srate: 8000 or disabling it solves the problem.

@ystinia
Copy link
Member Author

ystinia commented Jan 6, 2023

Can you provide RTMP URL for streaming again?

It's a complicated question.
I have access to a server that has an administrator and access to logs, but he really doesn't like to be asked to disable authorization.

I emailed you the address earlier

There is the same server without authorization, but there are no nice logs because the paid error search module is not installed.

Nimble insecure

  • rtmp://159.223.194.146:1935/openipc

@widgetii
Copy link
Member

widgetii commented Jan 6, 2023

BTW, as you're both here, it would be nice to have prebuilt Docker images with all closed RTMP crap to do local tests (with authorization, audio/video and so on). We may change code in the future and don't know about something will break

@ZigFisher
Copy link

Okay, I'll try to solve the problem tomorrow with the server and its configuration, so that we have full access.

@mariarti
Copy link

mariarti commented Jan 6, 2023

YouTube here, packets go outside, but not in YT admin panel
16ev300
h264, aac

.audio.enabled: true
.audio.volume: auto
.audio.srate: 16000
.audio.codec: aac
.audio.device: 
.audio.outputEnabled: false
.audio.speakerPin: 
.audio.speakerPinInvert: false
  outgoing:
  - rtmp://a.rtmp.youtube.com/live2/1234-1234-1234-1234-1234

LOG

21:55:23  <       majestic> [    rtmp] try_connect@246               Connecting to RTMP URL rtmp://a.rtmp.youtube.com/live2/1234-1234-1234-1234-1234...
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Parsing...
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Parsed protocol: 0
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Parsed host    : a.rtmp.youtube.com
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Parsed app     : live2/1234-1234-1234-1234-1234
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_Connect1, ... connected, handshaking
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   HandShake: Type Answer   : 03
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   HandShake: Server Uptime : 0
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   HandShake: FMS Version   : 4.0.0.1
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   HandShake: Handshaking finished....
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_Connect1, handshaked
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=49, size=4, ts=0
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=49, size=231, ts=0
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Invoking connect
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ReadPacket: fd=49
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   HandleServerBW: server BW = 2500000
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ReadPacket: fd=49
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   HandleClientBW: client BW = 59768832 2
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ReadPacket: fd=49
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ReadPacket: fd=49
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ClientPacket, received: invoke 240 bytes
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   (object begin)
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., STRING:	_result>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., NUMBER:	1.00>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., OBJECT>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   (object begin)
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:             fmsVer, STRING:	FMS/3,5,3,824>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:       capabilities, NUMBER:	127.00>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:               mode, NUMBER:	1.00>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   (object end)
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., OBJECT>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   (object begin)
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:              level, STRING:	status>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:               code, STRING:	NetConnection.Connect.Success>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:        description, STRING:	Connection succeeded.>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:     objectEncoding, NUMBER:	0.00>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:               data, ECMA_ARRAY>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   (object begin)
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:            version, STRING:	3,5,3,824>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   (object end)
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   (object end)
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   (object end)
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   HandleInvoke, server invoking <_result>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   HandleInvoke, received result for method call <connect>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=49, size=53, ts=0
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Invoking releaseStream
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=49, size=49, ts=0
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Invoking FCPublish
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=49, size=25, ts=0
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Invoking createStream
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ReadPacket: fd=49
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ClientPacket, received: invoke 21 bytes
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   (object begin)
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., STRING:	onBWDone>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., NUMBER:	0.00>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: NULL
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   (object end)
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   HandleInvoke, server invoking <onBWDone>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=49, size=21, ts=0
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Invoking _checkbw
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ReadPacket: fd=49
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ClientPacket, received: invoke 29 bytes
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   (object begin)
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., STRING:	_result>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., NUMBER:	4.00>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: NULL
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., NUMBER:	1.00>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   (object end)
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   HandleInvoke, server invoking <_result>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   HandleInvoke, received result for method call <createStream>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=49, size=54, ts=0
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Invoking publish
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ReadPacket: fd=49
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_ClientPacket, received: invoke 73 bytes
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   (object begin)
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., STRING:	onStatus>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., NUMBER:	0.00>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: NULL
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:           no-name., OBJECT>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   (object begin)
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:              level, STRING:	status>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   Property: <Name:               code, STRING:	NetStream.Publish.Start>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   (object end)
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   (object end)
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   HandleInvoke, server invoking <onStatus>
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   HandleInvoke, onStatus: NetStream.Publish.Start
21:55:23  <       majestic> [    rtmp] try_connect@296               Connection to rtmp://a.rtmp.youtube.com/live2/1234-1234-1234-1234-1234 successful
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=49, size=9090, ts=0
21:55:23  <  thread-pool-0> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=49, size=342, ts=0
21:55:23  <       majestic> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=49, size=68642, ts=50
21:55:23  <  thread-pool-1> [    rtmp] log_rtmp@59                   RTMP_SendPacket: fd=49, size=339, ts=60

and very soon died

Jan  6 21:55:19 openipc-hi3516ev300 user.debug majestic[879]: RTMP_SendPacket: fd=58, size=350, ts=31940
Jan  6 21:55:19 openipc-hi3516ev300 user.debug majestic[879]: RTMP_SendPacket: fd=58, size=9254, ts=31922
Jan  6 21:55:19 openipc-hi3516ev300 user.debug majestic[879]: RTMP_SendPacket: fd=58, size=337, ts=32000
Jan  6 21:55:19 openipc-hi3516ev300 user.debug majestic[879]: RTMP_SendPacket: fd=58, size=10032, ts=32006
Jan  6 21:55:19 openipc-hi3516ev300 user.debug majestic[879]: RTMP_SendPacket: fd=58, size=364, ts=32060
Jan  6 21:55:19 openipc-hi3516ev300 user.debug majestic[879]: Terminated signal received
Jan  6 21:55:19 openipc-hi3516ev300 user.debug majestic[879]: audio system is deinitialized
Jan  6 21:55:19 openipc-hi3516ev300 user.debug majestic[879]: Stopped 2 channel
Jan  6 21:55:19 openipc-hi3516ev300 user.debug majestic[879]: Stopped 1 channel
Jan  6 21:55:19 openipc-hi3516ev300 user.debug majestic[879]: Stopped 0 channel
Jan  6 21:55:20 openipc-hi3516ev300 user.debug majestic[879]: Stop sdk Ok!
Jan  6 21:55:20 openipc-hi3516ev300 kern.emerg kernel: Watchdog is disabled!
Jan  6 21:55:20 openipc-hi3516ev300 user.info majestic[879]: Shutdown main thread

@widgetii
Copy link
Member

widgetii commented Jan 9, 2023

  • rtmp://159.223.194.145:1935/openipc

How I can playback a stream I'm sending there?

@ystinia
Copy link
Member Author

ystinia commented Jan 10, 2023

I created a test project in my sandbox with Nimble based on Docker container and maybe it will help in our experiments.

@ystinia
Copy link
Member Author

ystinia commented Jan 12, 2023

I found a second way to test RTMP streams, an example here

@ystinia
Copy link
Member Author

ystinia commented Jan 12, 2023

Beautiful informative logs:

[2023-01-12 17:02:26.452][Trace][1][fi440q3l] Hybrid cpu=1.00%,16MB, cid=20,4, timer=62,0,0, clock=0,48,1,0,0,0,0,0,0, free=1, objs=(pkt:0,raw:0,fua:0,msg:4,oth:0,buf:0)
[2023-01-12 17:02:26.811][Trace][1][52920gd4] RTMP client ip=172.19.32.178:58100, fd=11
[2023-01-12 17:02:26.818][Trace][1][52920gd4] simple handshake success.
[2023-01-12 17:02:26.860][Trace][1][52920gd4] connect app, tcUrl=rtmp://172.19.32.17:1935/openipc/openipc, pageUrl=, swfUrl=rtmp://172.19.32.17:1935/openipc/openipc, schema=rtmp, vhost=172.19.32.17, port=1935, app=openipc/openipc, args=null
[2023-01-12 17:02:26.860][Trace][1][52920gd4] protocol in.buffer=0, in.ack=0, out.ack=0, in.chunk=4096, out.chunk=128
[2023-01-12 17:02:26.911][Trace][1][52920gd4] client identified, type=fmle-publish, vhost=172.19.32.17, app=openipc/openipc, stream=openipc, param=, duration=0ms
[2023-01-12 17:02:26.911][Trace][1][52920gd4] connected stream, tcUrl=rtmp://172.19.32.17:1935/openipc/openipc, pageUrl=, swfUrl=rtmp://172.19.32.17:1935/openipc/openipc, schema=rtmp, vhost=__defaultVhost__, port=1935, app=openipc/openipc, stream=openipc, param=, args=null
[2023-01-12 17:02:26.911][Trace][1][52920gd4] source url=/openipc/openipc/openipc, ip=172.19.32.178, cache=1, is_edge=0, source_id=/m83wpm62
[2023-01-12 17:02:26.961][Trace][1][52920gd4] RTC bridge from RTMP, rtmp2rtc=1, keep_bframe=0, merge_nalus=0
[2023-01-12 17:02:26.962][Trace][1][52920gd4] hls: win=60000ms, frag=10000ms, prefix=, path=./objs/nginx/html, m3u8=[app]/[stream].m3u8, ts=[app]/[stream]-[seq].ts, aof=2.00, floor=0, clean=1, waitk=1, dispose=0ms, dts_directly=1
[2023-01-12 17:02:26.962][Trace][1][52920gd4] ignore disabled exec for vhost=__defaultVhost__
[2023-01-12 17:02:26.962][Trace][1][52920gd4] start publish mr=0/350, p1stpt=20000, pnt=5000, tcp_nodelay=0
[2023-01-12 17:02:27.043][Warn][1][52920gd4][11] avc ignore type=1 for no sequence header
[2023-01-12 17:02:27.043][Warn][1][52920gd4][11] avc ignore type=1 for no sequence header
...
[2023-01-12 17:02:28.201][Warn][1][52920gd4][11] avc ignore type=1 for no sequence header
[2023-01-12 17:02:28.201][Warn][1][52920gd4][11] avc ignore type=1 for no sequence header
[2023-01-12 17:02:28.284][Warn][1][52920gd4][11] avc ignore type=1 for no sequence header
[2023-01-12 17:02:28.284][Warn][1][52920gd4][11] avc ignore type=1 for no sequence header
[2023-01-12 17:02:28.368][Warn][1][52920gd4][11] avc ignore type=1 for no sequence header
[2023-01-12 17:02:28.368][Warn][1][52920gd4][11] avc ignore type=1 for no sequence header
[2023-01-12 17:02:28.440][Trace][1][52920gd4] 46B video sh,  codec(7, profile=Baseline, level=5, 2592x1520, 0kbps, 0.0fps, 0.0s)
[2023-01-12 17:02:28.454][Warn][1][52920gd4][11] VIDEO: stream not monotonically increase, please open mix_correct.
[2023-01-12 17:02:28.455][Trace][1][52920gd4] -> HLS time=25171677ms, sno=1, ts=openipc-0.ts, dur=0ms, dva=0p
[2023-01-12 17:02:30.524][Trace][1][52920gd4] 46B video sh,  codec(7, profile=Baseline, level=5, 2592x1520, 0kbps, 0.0fps, 0.0s)
[2023-01-12 17:02:31.453][Trace][1][fi440q3l] Hybrid cpu=3.00%,17MB, cid=4,1, timer=63,0,0, clock=0,49,1,0,0,0,0,0,0, objs=(pkt:63,raw:0,fua:63,msg:74,oth:0,buf:0)
^C[2023-01-12 17:02:31.645][Trace][1][1a863u6i] sig=2, user terminate program, fast quit

@widgetii
Copy link
Member

I created a test project in my sandbox with Nimble based on Docker container and maybe it will help in our experiments.

Great job, but consider improving it using https://12factor.net/ principles (make logs out to stdout, no to files within container). BTW, second streaming app uses exactly this way and that's why it's convenient to use.

I've made AAC stream format adjustment, and it seems for now audio is working everywhere: in both testing containers, YouTube and Telegram

@ystinia
Copy link
Member Author

ystinia commented Jan 15, 2023

Thanks for the review.
Yes, the second container is what I will strive for in my experiments.
I want to make another container project based on MistServer and will report later on its readiness.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request majestic
Projects
None yet
Development

No branches or pull requests

4 participants