Closed YoungjaeDev closed 7 months ago
@youngjae-avikus referring back to the table on the common sink properties
You can see that the max-lateness
is set to 20000000
by default. DSL was setting this to -1 (disabled) in all previous releases. I decided to go with the plugin default -- just as I did with the sync
and async
properties.
_The max-lateness property affects how the Sink deals with buffers that arrive too late. A buffer arrives too late in the Sink when the presentation time (as a combination of the last segment, buffer timestamp and element base_time) plus the duration is before the current time of the clock. If the frame is later than max-lateness (in nanoseconds), the sink will drop the buffer without calling the render method._
It appears this is causing the issue you're reporting. Try setting the property to -1
with dsl_sink_max_lateness_set
re: " However, it is surprising that this error does not occur when you set the sink size to 1280x720."
This makes sense, since the the Sink has less processing to do, it can service it's input queue faster and the max-lateness is avoided.
I will probably disable this by default again in the next release.
@youngjae-avikus referring back to the table on the common sink properties
You can see that the
max-lateness
is set to20000000
by default. DSL was setting this to -1 (disabled) in all previous releases. I decided to go with the plugin default -- just as I did with thesync
andasync
properties._The max-lateness property affects how the Sink deals with buffers that arrive too late. A buffer arrives too late in the Sink when the presentation time (as a combination of the last segment, buffer timestamp and element base_time) plus the duration is before the current time of the clock. If the frame is later than max-lateness (in nanoseconds), the sink will drop the buffer without calling the render method._
It appears this is causing the issue you're reporting. Try setting the property to
-1
with dsl_sink_max_lateness_setre: " However, it is surprising that this error does not occur when you set the sink size to 1280x720." This makes sense, since the the Sink has less processing to do, it can service it's input queue faster and the max-lateness is avoided.
I will probably disable this by default again in the next release.
I set dsl_sink_max_latenessset to -1 and ran the pipeline once again, but it still hangs. It was replayed in FHD. Frame suddenly drops The situation is **max-lateness=-1, sync=True_**
sionFpsAvg: : Source '0' session FPS avg = 30.2753
0:01:03.991429976 947146 0x561448bb8c00 INFO DSL src/DslSourceMeter.h:136:GetIntervalFpsAvg: : Source '0' interval FPS avg = 29.97
29.970030 30.275275
0:01:05.993565631 947146 0x561448bb8c00 INFO DSL src/DslSourceMeter.h:116:GetSessionFpsAvg: : Source '0' session FPS avg = 30.2649
0:01:05.993636799 947146 0x561448bb8c00 INFO DSL src/DslSourceMeter.h:136:GetIntervalFpsAvg: : Source '0' interval FPS avg = 29.9551
29.955067 30.264939
0:01:07.093088822 947146 0x561448bc6b60 INFO DSL src/DslSinkBintr.cpp:1352:HandleXWindowEvents: : Button '1' pressed: xpos = 1328: ypos = 441
0:01:07.995772862 947146 0x561448bb8c00 INFO DSL src/DslSourceMeter.h:116:GetSessionFpsAvg: : Source '0' session FPS avg = 30.2348
0:01:07.995795714 947146 0x561448bb8c00 INFO DSL src/DslSourceMeter.h:136:GetIntervalFpsAvg: : Source '0' interval FPS avg = 28.9456
28.945555 30.234792
0:01:09.997893755 947146 0x561448bb8c00 INFO DSL src/DslSourceMeter.h:116:GetSessionFpsAvg: : Source '0' session FPS avg = 30.2348
0.000000 30.234792
0:01:12.000013285 947146 0x561448bb8c00 INFO DSL src/DslSourceMeter.h:116:GetSessionFpsAvg: : Source '0' session FPS avg = 30.2348
0.000000 30.234792
0:01:14.002123936 947146 0x561448bb8c00 INFO DSL src/DslSourceMeter.h:116:GetSessionFpsAvg: : Source '0' session FPS avg = 30.2348
0.000000 30.234792
0:01:16.004232654 947146 0x561448bb8c00 INFO DSL src/DslSourceMeter.h:116:GetSessionFpsAvg: : Source '0' session FPS avg = 30.2348
0.000000 30.234792
0:01:18.006348650 947146 0x561448bb8c00 INFO DSL src/DslSourceMeter.h:116:GetSessionFpsAvg: : Source '0' session FPS avg = 30.2348
FPS 0 (AVG)
0.000000 30.234792
0:01:20.008461214 947146 0x561448bb8c00 INFO DSL src/DslSourceMeter.h:116:GetSessionFpsAvg: : Source '0' session FPS avg = 30.2348
0.000000 30.234792
0:01:22.010574568 947146 0x561448bb8c00 INFO
deepstream:6.2 dsl=commit: 0.27.b.alpha pipeline
The phenomenon is as follows: What's really strange is that my monitor is 1920x1080, and when I sink the window-sink to this size, the rendering suddenly stops, lags for about a few seconds, and then the rendering starts again and the freeze phenomenon repeats. However, it is surprising that this error does not occur when you set the sink size to 1280x720.
1280x720 UI
1920x1080 UI -> no toolbar