Recherche avancée

Sur d’autres sites (5345)

• FFMPEG Screen Flashing Green

  18 novembre 2022, par Devin Dixon

  I have this problem where my ffmpeg videos are flicking green. Example of the video is here :
https://www.glitch.fun/streams/31fea7e0-7523-4365-9780-31deee9e472c/watchrecording/efb841c0-4b87-4482-b165-990880a66f63

  


  My ffmpeg command is this :

  


  /usr/bin/ffmpeg -vaapi_device /dev/dri/renderD128 -y -v info -f x11grab -draw_mouse 0 -r 60 -s 1920x1080 -thread_queue_size 14000 -i :0.0+0,0 -f alsa -thread_queue_size 14000 -i plug:bsnoop -acodec aac -strict -2 -ar 44100 -b:a 128k -af aresample=async=1 -c:v h264_vaapi -vf format=nv12|vaapi,hwupload -preset medium -maxrate 14000k -bufsize 14000k -pix_fmt yuv420p -r 60 -crf 25 -g 120 -tune zerolatency -f flv rtmp://ingest.bingewave.com/live/[output_to_livestream] -pix_fmt yuv420p -r 60 -b:v 15000k -maxrate 15000k -bufsize 15000k -c:v h264_vaapi -vf format=nv12|vaapi,hwupload -preset medium -keyint_min 24 -level 3.0 -g 120 -tune zerolatency -f flv rtmp://127.0.0.1:1935/live/[output_to_recording]


  


  The reason why my fps and bitrate is so high and preset is so medium is because Glitch is an open source esports platform, and those kinds of settings are required for streaming of game graphics
The command has two outputs :

  


  

  • rtmp ://[output_to_livestream] goes to a livestream where users watch live

  


  • rtmp ://127.0.0.1:1935/live/[output to recording] goes a goes to a file

  


  


  And the output to the recording is captured by nginx and saved to a file as such :

  


  rtmp {
    server {
        listen 1935;
        chunk_size 4096;

        application live {
            live on;
            #Set this to "record off" if you don't want to save a copy of your broadcasts
            record all;
            # The directory in which the recordings will be stored.
            record_path /var/www/html/recordings;
            record_unique on;
            record_suffix -%d-%b-%y-%T.flv;
            on_record_done http://127.0.0.1:3000/recorded;
            # Turn on HLS
            exec /usr/bin/ffmpeg -vaapi_device /dev/dri/renderD128 -i rtmp://127.0.0.1:1935/live/$name -c:v copy -c:a copy -f flv rtmp://127.0.0.1/show/$name;
        }

        application show {
            live on;
            # Turn on HLS
            hls on;
            hls_path /mnt/hls/;
            hls_fragment 3;
            hls_playlist_length 60;
            # disable consuming the stream from nginx as rtmp
            deny play all;
        }
    }
}


  


  So the part that goes to the live is fine, no green flickering at all. But the part that goes to the recording is one that goes the above issue :

  


  -pix_fmt yuv420p -r 60 -b:v 15000k -maxrate 15000k -bufsize 15000k -c:v h264_vaapi -vf format=nv12|vaapi,hwupload -preset medium -keyint_min 24 -level 3.0 -g 120 -tune zerolatency -f flv rtmp://127.0.0.1:1935/live/[output_to_recording]


  


  I
s there something I need to be changing here ?

  


• Lib x : display problem related to window pixel color changes with the mlx_put_pixel() function [closed]

  15 janvier 2023, par Jordan Riga

  I'm stuck on a project that I have to return for school.
I have to make a 3D game with the minilibx in C, the problem being that I try to make the graphic part work but it doesn't work (display pixels on the screen).
And all this same with the examples that I found of school 42 on the internet in that link https://harm-smits.github.io/42docs/libs/minilibx.
All configuration has been done.

  


  Could there be a possible configuration problem ? I'm working on Kali Linux (Even using a VM on Ubuntu it didn't work).

  


  In short my question is what can be the different reasons why the graphical part of minilibx independently of events, loops and etc does not work without errors ?

  


• How to fix FFmpeg crashed in Android 4/5/6 by sws_setColorspaceDetails function ?

  8 février 2023, par hachman

  I have using FFmpeg(ver 4.2) with cocos2dx game engine, and it works well at all iOS version and Android above level 24(include level 24). However, it may be crashed in Android under level 23(Andorid version 6.0.1).

  


  I am using bugly to record this problem, it located at "sws_setColorspaceDetails" function as this :

  


  #00 pc 01297b38 sws_setColorspaceDetails + 2704 [armeabi-v7a]

java:
org.cocos2dx.lib.Cocos2dxRenderer.onDrawFrame(Cocos2dxRenderer.java:94)
android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1535)
android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1240)


  


  So, how can I solve this problem ? This function is in "libswscale/utils.c", and I can't use "try-catch" to get more infomation.