Recherche avancée

Médias (0)

Mot : - Tags -/api

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

Autres articles (62)

  • Le profil des utilisateurs

    12 avril 2011, par

    Chaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
    L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • Configurer la prise en compte des langues

    15 novembre 2010, par

    Accéder à la configuration et ajouter des langues prises en compte
    Afin de configurer la prise en compte de nouvelles langues, il est nécessaire de se rendre dans la partie "Administrer" du site.
    De là, dans le menu de navigation, vous pouvez accéder à une partie "Gestion des langues" permettant d’activer la prise en compte de nouvelles langues.
    Chaque nouvelle langue ajoutée reste désactivable tant qu’aucun objet n’est créé dans cette langue. Dans ce cas, elle devient grisée dans la configuration et (...)

Sur d’autres sites (4563)

  • Reading images from AXIS ip camera using OpenCV

    14 juin 2016, par batuman

    I am trying to access AXIS IP camera from my program using OpenCV.
    My OpenCV version is 3.1. I follow this tutorial link.

    I have all libraries installed.
    My following program can load mp4 video successfully. That means ffmpeg and necessary libraries are working fine.

    #include <iostream>
    #include <opencv2></opencv2>opencv.hpp>

    using namespace std;
    int main() {
       cv::VideoCapture vcap("test.mp4");
       cv::Mat image;
    //    const string address = "rtsp://root:pass@192.168.0.90/axis-media/media.amp?camera=1";
    //    if(!vcap.open(address)){
    //      std::cout &lt;&lt; "Error opening video stream or file " &lt;&lt; std::endl;
    //      return -1;
    //    }
       for(;;){
           if(!vcap.read(image)){
               std::cout &lt;&lt; "No frame" &lt;&lt; std::endl;
               cv::waitKey(0);
           }
           cv::imshow("Display", image);
           cv::waitKey(1);
       }
       return 0;
    }
    </iostream>

    When I tried to access the IP Camera as follow

    cv::VideoCapture vcap("rtsp://root:pass@192.168.0.90/axis-media/media.amp?camera=1");

    I have the following error

    GStreamer Plugin: Embedded video playback halted; module source reported: Could
    not open resource for reading and writing.
    OpenCV Error: Unspecified error (GStreamer: unable to start pipeline
    ) in cvCaptureFromCAM_GStreamer, file /home/Softwares/opencv/opencv/modules
    /videoio/src/cap_gstreamer.cpp, line 818
    terminate called after throwing an instance of 'cv::Exception'
     what():  /home/Softwares/opencv/opencv/modules/videoio/src/cap_gstreamer.
    cpp:818: error: (-2) GStreamer: unable to start pipeline
    in function cvCaptureFromCAM_GStreamer

    User is root and password is pass and ip 192.168.0.90 are all defaults.

    My if config gave me

    ifconfig
    eth0      Link encap:Ethernet  HWaddr b8:2a:72:c6:b8:13  
             inet6 addr: fe80::ba2a:72ff:fec6:b813/64 Scope:Link
             UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
             RX packets:723959 errors:0 dropped:0 overruns:0 frame:0
             TX packets:116637 errors:0 dropped:0 overruns:0 carrier:0
             collisions:0 txqueuelen:1000
             RX bytes:199422245 (199.4 MB)  TX bytes:13701699 (13.7 MB)

    lo        Link encap:Local Loopback  
             inet addr:127.0.0.1  Mask:255.0.0.0
             inet6 addr: ::1/128 Scope:Host
             UP LOOPBACK RUNNING  MTU:65536  Metric:1
             RX packets:24829 errors:0 dropped:0 overruns:0 frame:0
             TX packets:24829 errors:0 dropped:0 overruns:0 carrier:0
             collisions:0 txqueuelen:0
             RX bytes:2502903 (2.5 MB)  TX bytes:2502903 (2.5 MB)

    wlan0     Link encap:Ethernet  HWaddr a0:a8:cd:99:92:60  
             UP BROADCAST MULTICAST  MTU:1500  Metric:1
             RX packets:0 errors:0 dropped:0 overruns:0 frame:0
             TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
             collisions:0 txqueuelen:1000
             RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

    What could be the problem for this access to the camera ?

    Thanks

  • avutil/mips : refactor msa SLDI_Bn_0 and SLDI_Bn macros.

    6 août 2019, par gxw
    avutil/mips : refactor msa SLDI_Bn_0 and SLDI_Bn macros.
    

    Changing details as following :
    1. The previous order of parameters are irregular and difficult to
    understand. Adjust the order of the parameters according to the
    rule : (RTYPE, input registers, input mask/input index/..., output registers).
    Most of the existing msa macros follow the rule.
    2. Remove the redundant macro SLDI_Bn_0 and use SLDI_Bn instead.

    Reviewed-by : Shiyou Yin <yinshiyou-hf@loongson.cn>
    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] libavcodec/mips/h264dsp_msa.c
    • [DH] libavcodec/mips/h264qpel_msa.c
    • [DH] libavcodec/mips/hevc_lpf_sao_msa.c
    • [DH] libavcodec/mips/hevcpred_msa.c
    • [DH] libavcodec/mips/hpeldsp_msa.c
    • [DH] libavcodec/mips/me_cmp_msa.c
    • [DH] libavcodec/mips/qpeldsp_msa.c
    • [DH] libavcodec/mips/vp8_mc_msa.c
    • [DH] libavcodec/mips/vp9_idct_msa.c
    • [DH] libavcodec/mips/vp9_lpf_msa.c
    • [DH] libavcodec/mips/vp9_mc_msa.c
    • [DH] libavutil/mips/generic_macros_msa.h
  • FFmpeg playable MP4 segmented video from RTSP

    5 février 2021, par Michael Novotný

    I have problem with creating playable uncomplete MP4 file created from FFMPEG. In my case I have some infinite RTSP stream (h.264) from IP camera.&#xA;My target is record this stream to MP4 files for playback. If i use FFMPEG mp4 muxer, work correctly.

    &#xA;

    /usr/bin/ffmpeg -progress pipe:5 -use_wallclock_as_timestamps 1 -analyzeduration 10000000 -probesize 10000000 -fflags &#x2B;igndts -rtsp_transport tcp -hwaccel auto -loglevel warning -i rtsp://****:****@*******:****/ -y -an -vcodec copy -strict experimental -movflags frag_keyframe&#x2B;empty_moov -f segment -segment_format mp4 -segment_format_options movflags=&#x2B;faststart -segment_atclocktime 1 -reset_timestamps 1 -strftime 1 -segment_time 15 /Shinobi/videos/bWkwjTWdRt/Rm67cYyq50/test-%S.mp4&#xA;

    &#xA;

    FFMPEG will create one MP4 file which still increasing its size. If I try copy or simply open this (uncomplete, still increased ... of course :) ) file, it's correcly play. But it's still only one file ... still bigger and bigger. For long-term recording cam (few weeks) it's not good.&#xA;I want segment this stream to multiple smaller MP4 files (as you knows from another typical NVR systems). For example : segment for 30minutes.&#xA;I used "segment" muxer.

    &#xA;

    /usr/bin/ffmpeg -progress pipe:5 -use_wallclock_as_timestamps 1 -analyzeduration 10000000 -probesize 10000000 -fflags &#x2B;igndts -rtsp_transport tcp -hwaccel auto -loglevel warning -i rtsp://*****:****@*********:****/ -y -an -vcodec copy -strict -2 -movflags frag_keyframe&#x2B;empty_moov -f mp4 -segment_atclocktime 1 -reset_timestamps 1 -strftime 1 -segment_list pipe:8 -segment_time 15 /Shinobi/videos/bWkwjTWdRt/Rm67cYyq50/test-%S.mp4&#xA;

    &#xA;

    It looks like work correctly. New file with defined mask is created every 30 minutes. If I try copy or simply open(and play) anyone "completed 30min segment file" it"s works correctly. Problem is with last file (more precisely : newest, still uncompleted last segment file) - it's not playable (moov atom not found).

    &#xA;

    I Googled my problem many time with another keywords. I was try many my wonders. I readed FFMPEG documentation maybe 5times.

    &#xA;

    Problem is with second passthroug which "segment muxer" do (which do -movflags +faststart .. for example). It's logicaly, second passthroug not be did in last(newest) file yet.

    &#xA;

    Is there way to make it work ? If I want see time for 2-3 mins ago it's no possible wait up to 30minutes for "complete segment" ... and at the same time it is not possible to have a billion files with 2-3sec segments.&#xA;How did other NVR systems solve this ? Synology, Hikvision and more has in their file system recorded MP4 soubory which one of them is still uncompleted, still growing, but normaly PLAYABLE.

    &#xA;

    A few last days I tried this with no success. I'am absolutely angry and sad. I hope that my text is understandable

    &#xA;

    Thank you

    &#xA;

    This options has no effect in my case (tried) :

    &#xA;

    -movflags frag_keyframe+empty_moov

    &#xA;

    -movflags faststart

    &#xA;

    -movflags separate_moof

    &#xA;

    -fragsize *** / -fragtime ***

    &#xA;

    -strict -2 / -strict experimental

    &#xA;