Recherche avancée

Médias (91)

Autres articles (98)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 est la première version de MediaSPIP stable.
    Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Mise à disposition des fichiers

    14 avril 2011, par

    Par défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
    Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
    Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...)

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

Sur d’autres sites (9991)

  • Unable to build solution in Visual Studio 2019 : The BaseOutputPath/OutputPath property is not set for project

    23 juillet 2022, par mhadi

    In an effort to integrate FFmpeg with Unity, I have been trying to build a solution file in Visual Studio 2019. However, I am currently unable to resolve the following error when I try to build in Visual Studio :

    


    


    The BaseOutputPath/OutputPath property is not set for project
'FFmpegUnityInterop.vcxproj'. Please check to make sure that you have
specified a valid combination of Configuration and Platform for this
project. Configuration='Release' Platform='x64'. This error may
also appear if some other project is trying to follow a
project-to-project reference to this project, this project has been
unloaded or is not included in the solution, and the referencing
project does not build using the same or an equivalent Configuration
or Platform.

    


    


    I have tried a number of solutions, including :

    


      

    1. Manually adding the OutputPath in 'FFmpegUnityInterop.vcxproj'&#xA;<outputpath>bin/Build/</outputpath>.
    2. &#xA;

    3. In the FFmpegUnityInterop.vcxproj file, moving the ProjectProperty with my preferred configuration and platform combination to the very top of the list of ProjectProperties (there are 8 of them).
    4. &#xA;

    5. Building with different configuration and platforms.
    6. &#xA;

    7. Trying to build from VS Dev Command prompt using the following command :&#xA;MSbuild.exe "FFmpegUnityInterop.sln" /p:Configuration=Release /p:Platform="x64", as well as from the Visual Studio IDE.
    8. &#xA;

    9. Tried setting the OutputPath in the command line command&#xA;(>MSbuild.exe FFmpegUnityInterop.sln /p:Configuration=Release /p:Platform="AnyCPU" /p:OutputPath = bin\Debug), only to have&#xA;MSbuild throw error MSB1008 (MSBUILD : error MSB1008 : Only one&#xA;project can be specified.)
    10. &#xA;

    11. Setting the configuration and platform manually in the Configuration Manager GUI in&#xA;Visual Studio.
    12. &#xA;

    &#xA;

    I may have missed an attempted solution or two above, but I've tried most of the suggestions I found online, only to get the error pasted above. Part of me suspects that my compilation of FFmpeg libraries didn't execute fully, but I unfortunately do not have enough experience to verify that. Any suggestions to resolve this would be much appreciated.

    &#xA;

    PS. The project was developed privately by a private entity that is currently unreachable

    &#xA;

  • Error when transcoding MPEG-TS Stream with MISB KLV Data to HLS via FFM

    6 mai 2023, par Rockwell_Lancer

    I hope you are doing well !

    &#xA;

    I'm currently working on a project that is intended to receive, and store in HLS/H.264 format, an MPEG-TS video feed transmitted over UDP multicast. This video stream contains two channels ; a video-only MPEG-TS/mpeg2video (no audio) stream and a data-only MISB KLV datastream.

    &#xA;

    I receive this UDP stream, convert to HLS, and then parse the KLV data out of the generated .ts files as they are created, and use it further down the pipeline of the application. The timing of this KLV data is critical to the functionality of the application, as the data must remain synchronized with the video. As such, presentation time stamps (PTS) on KLV packets need to be relatively close to those of their corresponding video counterparts.

    &#xA;

    The current implementation makes use of the following Ffmpeg command :

    &#xA;

    ffmpeg -i "udp://239.255.0.1:10089?reuse=1&amp;fifo_size=5000000&amp;overrun_nonfatal=1" \&#xA;  -map 0:0 -noautoscale -profile:v main \&#xA;  -map 0:1 -hls_time 5000ms -hls_list_size 0 -r 30 -g 150 -f hls out.m3u8&#xA;

    &#xA;

    This command is very effective for handling the transcoding of the video under normal circumstances, however, the UDP stream is not guaranteed to be reliable, and can be expected to drop for several seconds at times. When this happens, and the stream resurfaces, the above command fails catastrophically with the output below :

    &#xA;

    [mpegts @ 0x7fce3a004a80] Packet corrupt (stream = 0, dts = 8949000).&#xA;udp://127.0.0.1:10089?reuse=1&amp;fifo_size=5000000&amp;overrun_nonfatal=1: corrupt input packet in stream 0&#xA;&#xA;frame= 2937 fps= 27 q=29.0 size=N/A time=00:01:55.36 bitrate=N/A dup=805 drop=0 &#xA;&#xA;[hls @ 0x7fce3a017240] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 10386000 >= 8829000&#xA;av_interleaved_write_frame(): Invalid argument&#xA;

    &#xA;

    Ffmpeg goes on to indicate Conversion Failed! and exits with code 1. The PTS difference in the error message appears to be approximately equivalent to the amount of time the UDP stream was interrupted.

    &#xA;

    Does anyone know what might be the issue causing, and if so, are there any suggestions that might help mitigate this issue ? The value of the PTS on the KLV doesn't matter so much as whether it matches the video PTS. Any assistance with this matter would be greatly appreciated.

    &#xA;

    Thank you in advance !

    &#xA;

  • yuv420p pixel format in GStreamer ?

    5 août 2022, par cubecubed

    I am trying to stream a video from opencv/python to rtsp-simple-server via GStreamer. I am able to view the video fine in vlc, but the online streaming application I am using is very picky. I need the stream to have a pixel format of yuv420p. How do I convert a stream to this format with GStreamer ?

    &#xA;

    This is my current code which creates a stream with the yuv444p :

    &#xA;

    out = cv2.VideoWriter(&#x27;appsrc ! videoconvert&#x27; &#x2B; \&#xA;&#x27; ! x264enc speed-preset=ultrafast bitrate=600 key-int-max=40&#x27; &#x2B; \&#xA;&#x27; ! rtspclientsink location=rtsp://localhost:554/video&#x27;,&#xA;cv2.CAP_GSTREAMER, 0, fps, (width, height), True)&#xA;

    &#xA;

    I am looking for the GStreamer equivalent of -pix_fmt yuv420p

    &#xA;