Recherche avancée

Médias (0)

Mot : - Tags -/diogene

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (108)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs

    12 avril 2011, par

    La manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
    Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras.

Sur d’autres sites (9807)

  • How to correctly setup Linker in Eclipse IDE 4.8.0M4 for ffmpeg development (Ubuntu)

    28 janvier 2018, par boergi

    I am using Eclipse IDE 4.8.0M4 on Ubunto 16.04. I try to compile the code from a FFmpeg tutorial on GitHUB : (https://github.com/leandromoreira/ffmpeg-libav-tutorial/blob/master/0_hello_world.c). For setting up FFmpeg in Eclipse i used this guide :(https://trac.ffmpeg.org/wiki/Setup_Eclipse_IDE_for_FFmpeg_(Linux)).

    The header files and libaries are all in the folder /home/git/ffmpeg. (e.g. avcodec.h and libavcodec.a is in the folder /home/git/ffmpeg/libavcodec). Included libs : -lavcodec -lpostproc -lz -llzma -lrt -lavfilter -lswresample -lavdevice -lswscale -lavutil -lavformat

    Console output :

    12:34:30 **** Incremental Build of configuration Debug for project ffmpeg_test ****
    
make all 
    
Building target: ffmpeg_test
    
Invoking: GCC C Linker
    
gcc -L/home/git/ffmpeg/libavcodec -L/home/git/ffmpeg/libavformat -o "ffmpeg_test"  ./src/simpletest.o   -lavcodec -lpostproc -lz -llzma -lrt -lavfilter -lswresample -lavdevice -lswscale -lavutil -lavformat
    
./src/simpletest.o: In function `main':
    
/home/boergi/eclipse-workspace/ffmpeg_test/Debug/../src/simpletest.c:141: undefined reference to `avcodec_parameters_to_context'
    
/home/boergi/eclipse-workspace/ffmpeg_test/Debug/../src/simpletest.c:163: undefined reference to `av_packet_alloc'
    
/home/boergi/eclipse-workspace/ffmpeg_test/Debug/../src/simpletest.c:194: undefined reference to `av_packet_free'
    
./src/simpletest.o: In function `decode_packet':
    
/home/boergi/eclipse-workspace/ffmpeg_test/Debug/../src/simpletest.c:214: undefined reference to `avcodec_send_packet'
    
/home/boergi/eclipse-workspace/ffmpeg_test/Debug/../src/simpletest.c:225: undefined reference to `avcodec_receive_frame'
    
collect2: error: ld returned 1 exit status
    
makefile:30: recipe for target 'ffmpeg_test' failed
    
make: *** [ffmpeg_test] Error 1
    

    
12:34:31 Build Finished (took 519ms)

    I found out that "int avcodec_parameters_to_context(AVCodecContext *codec, const AVCodecParameters *par)" is defined in utils.c (also in the /libavcodec folder), but i don’t know what can i do to get this running.

    boergi@Ubuntu-b:~/git/ffmpeg$ ffmpeg -version
    
ffmpeg version N-89895-g7723750 Copyright (c) 2000-2018 the FFmpeg developers
    
built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.5) 20160609
    
configuration: 
    
libavutil      56.  7.100 / 56.  7.100
    
libavcodec     58.  9.100 / 58.  9.100
    
libavformat    58.  5.101 / 58.  5.101
    
libavdevice    58.  0.101 / 58.  0.101
    
libavfilter     7. 11.101 /  7. 11.101
    
libswscale      5.  0.101 /  5.  0.101
    
libswresample   3.  0.101 /  3.  0.101

  • 5 questions you should ask yourself before defining a custom alert in Matomo

    24 janvier 2018, par InnoCraft

    In Matomo, you can create Custom Alerts to automatically be notified of important changes on your website or app. They are a great way to save time, but they also spam your mailbox quickly. Defining good custom alerts takes therefore time and requires some preparations. Here are recommendations on what you should focus on to only get the right alerts at the right time.

    There are several questions you should ask yourself before you define a custom alert :

    1. Do you really want to be alerted ? If the answer is no, then do not use this feature.
    2. What is the level of this alert ? Not important, interesting, highly critical… if it is not highly critical, do not define an alert for this. Probably the emailing report or custom reports feature will be a better fit.
    3. How would you like to be alerted ? SMS, email, sound, homing pigeon (unfortunately we do not support this feature at that time). If you are looking at your emails once a week, then defining a daily email alert won’t make sense.
    4. How would you like the alert to be named ? Give your alert the most explicit name, that’s the first information you will see when you get alerted.
    5. What will be the next step once the alert is triggered ? If you cannot find any action once the alert is triggered, then probably an alert doesn’t make sense.

    Once those questions are answered, you can start configuring custom alerts. There are many alerts you can define but as just mentioned, which alerts you should create always depends on your goals and what is critical to you, or your business. Let’s look at some custom alerts that we see quite often.

    No visit

    One of the easiest custom alert to define. You probably want to be alerted if your website did not receive any visit. As this alert is highly critical, you will want to receive an e-mail, even an SMS. This alert will trigger only if the number of visits is below 1 on a daily basis :

    Here the action we will take is to have a look at the website in order to see if it is still live. If the site still works, we will look at the tracking code in order to see if the website is still correctly tracked or not.

    Convinced of this custom alert ? Let’s look at another example.

    Target achieved

    Let’s say you gave a goal to one of your employee to reach a specific threshold in terms of conversions. You can then define a custom alert in order to inform you when the threshold has been reached.

    You can simply do this with an alert saying “Target achieved by Franck” where number of conversions equals the number of actions you defined with him. It takes you only a minute to define something you would have missed otherwise.

    Here the actions we can think of are either to congratulate Franck or to ask him what is going wrong if the target is not achieved.

    Did you know that you can also take advantage of Matomo premium features to define custom alerts ? Let’s see one of them.

    Lost SEO ranking

    If you are using the Search Engine Keyword Performance premium feature, there are really interesting combinations you can use to create custom alerts.
    For example, you can be notified when a specific keyword lost or reached a position :

    You will be alerted when your website is losing some positions within the search engine results for specific keywords. Here the action we could take is to investigate why we lost a position on Google for this keyword.

    There are many custom alert combinations waiting for you out there. Why not giving them a try ? If you have any questions, feel free to ask them on the Matomo forums.

    The post 5 questions you should ask yourself before defining a custom alert in Matomo appeared first on Analytics Platform - Matomo.

  • VLC can not play RTSP stream while mpv, ffplay can play RTSP stream video

    15 novembre 2018, par Harshil Makwana

    I developed ffserver based RTSP server which streams live video, I can able to stream and display video on mpv and ffplayer. but on VLC player I can see first image only then It wont show other frames.

    Here are logs of VLC -vvv output :

    [0x7846e8] main playlist debug: art not found for rtsp://127.0.0.1:1234/test.h264
    
Received 92 new bytes of response data.
    
Received a complete PLAY response:
    
RTSP/1.0 200 OK
    
CSeq: 5
    
Date: Thu, 15 Nov 2018 04:13:15 GMT
    
Session: 522d937eb678c50a
    

    

    
[0x7f9684000e38] live555 demux debug: play start: 0.000000 stop:0.000000
    
[0x7f9684000e38] main demux debug: using access_demux module "live555"
    
[0x7f96840246b8] main decoder debug: looking for decoder module matching "any": 39 candidates
    
[0x7f96840246b8] avcodec decoder debug: trying to use direct rendering
    
[0x7f96840246b8] avcodec decoder debug: allowing 3 thread(s) for decoding
    
[0x7f96840246b8] avcodec decoder debug: avcodec codec (H264 - MPEG-4 AVC (part 10)) started
    
[0x7f96840246b8] avcodec decoder debug: using frame thread mode with 3 threads
    
[0x7f96840246b8] main decoder debug: using decoder module "avcodec"
    
[0x7f9684034f68] main packetizer debug: looking for packetizer module matching "any": 21 candidates
    
[0x7f9684034f68] main packetizer debug: using packetizer module "packetizer_h264"
    
[0x7f9684150308] main demux meta debug: looking for meta reader module matching "any": 2 candidates
    
[0x7f9684150308] lua demux meta debug: Trying Lua scripts in /home/hashmak/.local/share/vlc/lua/meta/reader
    
[0x7f9684150308] lua demux meta debug: Trying Lua scripts in /usr/lib/vlc/lua/meta/reader
    
[0x7f9684150308] lua demux meta debug: Trying Lua playlist script /usr/lib/vlc/lua/meta/reader/filename.luac
    
[0x7f9684150308] lua demux meta debug: Trying Lua scripts in /usr/share/vlc/lua/meta/reader
    
[0x7f9684150308] main demux meta debug: no meta reader modules matched
    
[0x7f968c0009b8] main input debug: `rtsp://127.0.0.1:1234/test.h264' successfully opened
    
[0x7f9684000e38] live555 demux debug: tk->rtpSource->hasBeenSynchronizedUsingRTCP()
    
[0x7f968c0009b8] main input error: ES_OUT_RESET_PCR called
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9684034f68] packetizer_h264 packetizer warning: waiting for SPS/PPS
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9684034f68] packetizer_h264 packetizer warning: waiting for SPS/PPS
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9684034f68] packetizer_h264 packetizer warning: waiting for SPS/PPS
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9684034f68] packetizer_h264 packetizer warning: waiting for SPS/PPS
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9684034f68] packetizer_h264 packetizer warning: waiting for SPS/PPS
    
[0x7f9684034f68] packetizer_h264 packetizer warning: waiting for SPS/PPS
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9684034f68] packetizer_h264 packetizer warning: waiting for SPS/PPS
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9684034f68] packetizer_h264 packetizer warning: waiting for SPS/PPS
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9684034f68] packetizer_h264 packetizer warning: waiting for SPS/PPS
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9684034f68] packetizer_h264 packetizer warning: waiting for SPS/PPS
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9684034f68] packetizer_h264 packetizer warning: waiting for SPS/PPS
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9684034f68] packetizer_h264 packetizer warning: waiting for SPS/PPS
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9684034f68] packetizer_h264 packetizer warning: waiting for SPS/PPS
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9684034f68] packetizer_h264 packetizer warning: waiting for SPS/PPS
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9684034f68] packetizer_h264 packetizer warning: waiting for SPS/PPS
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9684034f68] packetizer_h264 packetizer debug: found NAL_SPS (sps_id=0)
    
[0x7f9684034f68] packetizer_h264 packetizer debug: found NAL_PPS (pps_id=0 sps_id=0)
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9694002718] main spu text debug: looking for text renderer module matching "any": 2 candidates
    
[0x7f9694002718] freetype spu text debug: Building font databases.
    
[0x7f9694002718] freetype spu text debug: Took 0 microseconds
    
Fontconfig warning: FcPattern object size does not accept value "0"
    
Fontconfig warning: FcPattern object size does not accept value "0"
    
[0x7f9694002718] freetype spu text debug: Using Serif Bold as font from file /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf
    
[0x7f9694002718] freetype spu text debug: using fontsize: 2
    
[0x7f9694002718] main spu text debug: using text renderer module "freetype"
    
[0x7f969400e408] main scale debug: looking for video filter2 module matching "any": 55 candidates
    
[0x7f969400e408] swscale scale debug: 32x32 chroma: YUVA -> 16x16 chroma: RGBA with scaling using Bicubic (good quality)
    
[0x7f969400e408] main scale debug: using video filter2 module "swscale"
    
[0x7f9694025cc8] main scale debug: looking for video filter2 module matching "any": 55 candidates
    
[0x7f9694025cc8] yuvp scale debug: YUVP to YUVA converter
    
[0x7f9694025cc8] main scale debug: using video filter2 module "yuvp"
    
[0x7f9694001428] main video output debug: Deinterlacing available
    
[0x7f9694001428] main video output debug: deinterlace 0, mode blend, is_needed 0
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9694001428] main video output debug: Opening vout display wrapper
    
[0x7f9674001248] main vout display debug: looking for vout display module matching "any": 12 candidates
    
[0x7f9674002618] main window debug: looking for vout window xid module matching "qt4,any": 4 candidates
    
[0x7f9674002618] qt4 window debug: requesting video window...
    
[0x6f3208] qt4 interface debug: Video was requested 0, 0
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9674002618] main window debug: using vout window xid module "qt4"
    
[0x7f96740027e8] main inhibit debug: looking for inhibit module matching "any": 2 candidates
    
[0x7f96740027e8] dbus_screensaver inhibit debug: found service org.freedesktop.ScreenSaver
    
[0x7f96740027e8] main inhibit debug: using inhibit module "dbus_screensaver"
    
[0x7f9674001248] xcb_glx vout display debug: connected to X11.0 server
    
[0x7f9674001248] xcb_glx vout display debug:  vendor : The X.Org Foundation
    
[0x7f9674001248] xcb_glx vout display debug:  version: 11702000
    
[0x7f9674001248] xcb_glx vout display debug: using screen 0x73
    
[0x7f9674001248] xcb_glx vout display debug: using GLX extension version 1.4
    
[0x7f9674001248] xcb_glx vout display debug: using X11 window 05400000
    
shader program 1: WARNING: Output of vertex shader 'TexCoord1' not read by fragment shader
    
WARNING: Output of vertex shader 'TexCoord2' not read by fragment shader
    

    
[0x7f9674001248] main vout display debug: VoutDisplayEvent 'fullscreen' 0
    
[0x7f9674001248] main vout display debug: VoutDisplayEvent 'resize' 1215x724 window
    
[0x7f9674001248] main vout display debug: using vout display module "xcb_glx"
    
[0x7f9694001428] main video output debug: original format sz 640x480, of (0,0), vsz 640x480, 4cc I420, sar 1:1, msk r0x0 g0x0 b0x0
    
[0x7f9694002718] main spu text debug: removing module "freetype"
    
[0x7f9694002718] main spu text debug: looking for text renderer module matching "any": 2 candidates
    
[0x7f9694002718] freetype spu text debug: Building font databases.
    
[0x7f9694002718] freetype spu text debug: Took 0 microseconds
    
Fontconfig warning: FcPattern object size does not accept value "0"
    
Fontconfig warning: FcPattern object size does not accept value "0"
    
[0x7f9694002718] freetype spu text debug: Using Serif Bold as font from file /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf
    
[0x7f9694002718] freetype spu text debug: using fontsize: 2
    
[0x7f9694002718] main spu text debug: using text renderer module "freetype"
    
[0x7f96840246b8] avcodec decoder debug: using direct rendering
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f96840246b8] main decoder debug: End of video preroll
    
[0x7f96840246b8] main decoder debug: Received first picture
    
[0x7f9674001248] xcb_glx vout display debug: display is visible
    
[0x7f9674001248] main vout display error: Failed to resize display
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[h264 @ 0x7f9684037e40] illegal short term buffer state detected
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f9674001248] main vout display debug: auto hiding mouse cursor
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    

    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    

    

    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    

    
[0x7f968c0009b8] main input debug: Buffering 0%
    

    
[0x7f968c0009b8] main input debug: Buffering 0%

    Here you can see, VLC is always waiting on buffering, while other players can get buffers from my RTSP server, also I can see RTP packets on wireshark that server is continuously sending data to VLC.

    Can someone help me on this issue ?

    Very much thanks in advance.

Navigation