Recherche avancée

Médias (91)

Autres articles (63)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • Formulaire personnalisable

    21 juin 2013, par

    Cette page présente les champs disponibles dans le formulaire de publication d’un média et il indique les différents champs qu’on peut ajouter. Formulaire de création d’un Media
    Dans le cas d’un document de type média, les champs proposés par défaut sont : Texte Activer/Désactiver le forum ( on peut désactiver l’invite au commentaire pour chaque article ) Licence Ajout/suppression d’auteurs Tags
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire. (...)

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

Sur d’autres sites (9693)

  • Adding ffmpeg OMX codec to Genymotion Android 4.4.2 emulator

    22 avril 2016, par photon

    Basic Question :

    Is there a way to add a new audio codec to the Genymotion Android emulator, short of downloading the entire Android source, learning how to build it, and creating my own version of Android ?


    Context :

    I have written a java Android app that acts as an audio renderer, as well as being a DLNA/OpenHome server and client. Think "BubbleUpnp" without video. My primary development platform is Win8.1. The program started as an ActiveState "pure-perl" DLNA MediaServer on Windows, which I then ported to Ubuntu, which I got working under Android a few years ago. It was pretty funky ... all UI being presented thru an HTTP server/jquery/jquery-ui, served from an Ubuntu shell running under Android (a trick in itself), serving up HTML pages to Chrome running on the same (Android) device. Besides being "funky" it had a major drawback that it required a valid IP address to work ... as I could not figure out how to get ubuntu to have a local loopback device for a 127.0.0.01 localhost I use the app as a "car stereo" on my boat (which is my home), which is often not hooked up to the internet.

    I had a hard time getting started in Android app development because the speed of the Android emulators in Eclipse was horrid, and the ADB drivers did not work from Win8 for the longest time.

    Then one day, about a year ago, I ran into Genymotion (kudos to the authors), and all of a sudden I had a workable Android development environment, so I added a Java implementation of the DLNA server, which then grew into a renderer also, using Android’s MediaPlayer class, and, adding the ability to act as a DLNA control point, and more recently also added OpenHome servers and renderers to it.

    In a separate effort, I created a build environment for this program called fpCalc, based on ffMpeg, on a variety of platforms, including Win, Linux, and Android x86, arm, and arm7 devices (bitbucket.org/phorton1/) and did an extensive series of tests to determine the validity, and longevity of fpcalc fingerprints, discovering that the fpCalc fingerprint changed based on the version of ffmpeg it was built against, a separate topic to be sure, but in the process, learned at least a bit about how to build ffmpeg as well as Android shared libraries, JNI interfaces, etc.

    So now the Android-Java version of the program has advanced past the old perl version, and I am debating whether I want to continue to try to build the perl version (and or add an wxPerl UI) to it.

    One issue that has arisen, for me, is that the Genymotion emulator does not support WMA decoding ... as Android dropped support for WMA due to licensing issues, etc, a ways back in time ... yet my music library has significant numbers of tunes in WMA files, and I don’t want to "convert" them, my carefully thought-out philosophy is that my program does not modify the contents, or tags, or anything in the original media files that I have accumulated, or will receive in the future, rather treating them as "artifacts" worth preserving "as is". No conversion is going to make a file "better" than it was, and I wish to preserve ALL of the original sources for ALL of my music going forward.

    So, I’m thinking, gee, I can build FFMPEG on 7 different platforms, and I see all these references to "OMX FFMPEG Codec Support for Android" on the net, so I’m thinking, "All I need to do is create the OMX Component and somehow get it into Genymotion".

    I have studied up OMX, OpenMaxIL, seen Michael Chen’s posts, seen the stack overflow questions

    How to make ffmpeg codec componet as OMX component

    and

    Android : How to integrate a decoder to multimedia framework

    and Cedric Fung’s page https://vec.io/posts/use-android-hardware-decoder-with-omxcodec-in-ndk, and Michael Chen’s repository at https://github.com/omxcodec , as well as virtually every other page on the net that mentions any combination of libstagefright, OMX, Genymotion, and FFMPEG.

    (this page would not let me put more than 2 links as i don’t have a "10" reputation, or I would have listed some of the sources I have seen) ..

    My Linux development environment is a Ubuntu12.04 vbox running on my win machine. I have downloaded and run the Android-x86 iso as a vbox, and IT contains the ffmpeg codecs, but unfortunately, it neither supports a wifi interface, nor the vbox "guest additions", so it has a really funky mouse. I tried for about 3 days to address those two issues, but in the end do not feel it is usable for my puproses, and I really like the way genymotion "feels", particularly the moust support, so I’d like to keep genymotion as my "windows android" virtual device under which I may run my program, deprecate and stop using my old perl source,

    except genymotion does not support WMA files ...


    Several side notes :

    (a) There is no good way to write a single sourced application in Java that runs natively in Windows, AND as an Android app.

    (b) I don’t want to reboot my Windows machine to a "real" Android device just to play my music files. The machine has to stay in Windows as I use it for other things as well.

    (c) I am writing this as my machine is in the 36th hour of downloading the entire ASOP source code base to a partition in my Ubuntu vbox while I am sitting in a hotel room on a not-so-good internet connection in Panama City, Panama, before I return to my boat in remote Bocas Del Toro Panama, where the internet connection is even worse.

    (d) I did get WMA decoding to work in my app by calling my FFMPEG executable from Java (converting it to either WAV/PCM or AAC), but, because of limitations in Android’s MediaPlayer, it does not work well, particularly for remotely hosted WMA files ... MediaPlayer insists on having the whole file present before it starts to play, which can take several seconds or longer, and I am hoping that by getting a ’real’ WMA codec underneath MediaPlayer, that problem will just disappear ....


    So, I’m trying to figure this whole mess out. There are a lot of tantalizing clues, and suggestions, but what I have found, or at least what I am starting to believe, is that if I want to add a simple WMA audio decoding codec to Android (Genymotion), not only do I have to download, basically, the ENTIRE ASOP Android source tree, and learn a new set of tools (repo, etc), but I have to (be able to) rebuild, from scratch, the entire Android system, esp. libstagefright.so in such a way as to be COMPLETELY compatible with the existing one in GenyMotion, while at the same time adding ffmpeg codecs ala Michael Chen’s page.

    And I’m just asking, is it, could it really be that difficult ?


    Anyways, this makes me crazy. Is there no way to just build a new component, or at worst a new OMX core, and add it to Genymotion, WITHOUT building all of Android, and preferably, based only on the OMX h files ? Or do I REALLY have to replace the existing libstagefright.so, which means, basically, rebuilding all of Android ...

    p.s. I thought it would be nice to get this figured out, build it, and then post the installable new FFMPEG codecs someplace for other people to use, so that they don’t also grow warts on their ears and have steam shooting out of their eyeballs, while they get old trying to figure it out ....

  • Winamp and the March of GUI

    1er juillet 2012, par Multimedia Mike — General, ars technica, gui, user interface, winamp

    Ars Technica recently published a 15-year retrospective on the venerable Winamp multimedia player, prompting bouts of nostalgia and revelations of "Huh ? That program is still around ?" from many readers. I was among them.



    I remember first using Winamp in 1997. I remember finding a few of these new files called MP3s online and being able to play the first 20 seconds using the official Fraunhofer Windows player— full playback required the fully licensed version. Then I searched for another player and came up with Winamp. The first version I ever used was v1.05 in the summer of 1997. I remember checking the website often for updates and trying out every single one. I can’t imagine doing that nowadays— programs need to auto-update themselves (which Winamp probably does now ; I can’t recall the last time I used the program).

    Video Underdog
    The last time Winamp came up on my radar was early in 2003 when a new version came with support for a custom, proprietary multimedia audio/video format called Nullsoft Video (NSV). I remember the timeframe because the date is indicated in the earliest revision of my NSV spec document (back when I was maintaining such docs in a series of plaintext files). This was cobbled together from details I and others in the open source multimedia community sorted out from sample files. It was missing quite a few details, though.

    Then, Winamp founder Justin Frankel — introduced through a colleague on the xine team — emailed me his official NSV format and told me I was free to incorporate details into my document just as long as it wasn’t obvious that I had the official spec. This put me in an obnoxious position of trying to incorporate details which would have been very difficult to reverse engineer without the official doc. I think I coped with the situation by never really getting around to updating my doc in any meaningful way. Then, one day, the official spec was released to the world anyway, and it is now mirrored here at multimedia.cx.

    I don’t think the format ever really caught on in any meaningful way, so not a big deal. (Anytime I say that about a format, I always learn it saw huge adoption is some small but vocal community.)

    What’s Wrong With This Picture ?
    What I really wanted to discuss in this post was the matter of graphical user interfaces and how they have changed in the last 15 years.

    I still remember when I first downloaded Winamp v1.05 and tried it on my Windows machine at the time. Indignantly, the first thought I had was, "What makes this program think it’s so special that it’s allowed to violate the user interface conventions put forth by the rest of the desktop ?" All of the Windows programs followed a standard set of user interface patterns and had a consistent look and feel... and then Winamp came along and felt it could violate all those conventions.

    I guess I let the program get away with it because it was either that or only play 20-second clips from the unregistered Fraunhofer player. Though incredibly sterile by comparison, the Fraunhofer player, it should be noted, followed Windows UI guidelines to the letter.

    As the summer of 1997 progressed and more Winamp versions were released, eventually one came out (I think it was v1.6 or so) that supported skins. I was excited because there was a skin that made the program look like a proper Windows program— at least if you used the default Windows color scheme, and had all of your fonts a certain type and size.

    Skins were implemented by packaging together a set of BMP images to overlay on various UI elements. I immediately saw a number of shortcomings with this skinning approach. A big one was UI lock-in. Ironically, if you skin an app and wish to maintain backwards compatibility with the thousands of skins selflessly authored by your vibrant community (seriously, I couldn’t believe how prolific these things were), then you were effectively locked into the primary UI. Forget about adding a new button anywhere.

    Another big problem was resolution-independence. Basing your UI on static bitmaps doesn’t scale well with various resolutions. Winamp had its normal mode and it also had double-sized mode.

    Skins proliferated among many types of programs in the late 1990s. I always treasured this Suck.com (remember them ? that’s a whole other nostalgia trip) essay from April, 2000 entitled Skin Cancer. Still, Winamp was basically the standard, and the best, and I put away my righteous nerd rage and even dug through the vast troves of skins. I remember settling on Swankamp for a good part of 1998, probably due to the neo-swing revival at the time.



    Then again, if Winamp irked me, imagine my reaction when I was first exposed to the Sonique Music Player in 1998 :



    The New UI Order
    Upon reflection, I realize now that I had a really myopic view of what a computer GUI should be. I thought the GUIs were necessarily supposed to follow the WIMP (windows, icons, mouse, pointer) paradigm and couldn’t conceive of anything different. For a long time, I couldn’t envision a useful GUI on a small device (like a phone) because WIMP didn’t fit well on such a small interface (even though I saw various ill-fated attempts to make it work). This thinking seriously crippled me when I was trying to craft a GUI for a custom console media player I was developing as a hobby many years ago.

    I’m looking around at what I have open on my Windows 7 desktop right now. Google Chrome browser, Apple iTunes, Adobe Photoshop Elements, and VMware Player are 4 programs which all seem to have their own skins. Maybe Winamp doesn’t look so out of place these days.

  • 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.