Recherche avancée

Médias (0)

Mot : - Tags -/tags

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

Autres articles (69)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

Sur d’autres sites (7451)

  • Hardware Accelerated H264 Decode using DirectX11 in Unity Plugin for UWP

    8 janvier 2019, par rohit n

    I’ve built an Unity plugin for my UWP app which converts raw h264 packets to RGB data and renders it to a texture. I’ve used FFMPEG to do this and it works fine.

    int framefinished = avcodec_send_packet(m_pCodecCtx, &packet);
    framefinished = avcodec_receive_frame(m_pCodecCtx, m_pFrame);
    // YUV to RGB conversion and render to texture after this

    Now, I’m trying to shift to hardware based decoding using DirectX11 DXVA2.0.

    Using this : https://docs.microsoft.com/en-us/windows/desktop/medfound/supporting-direct3d-11-video-decoding-in-media-foundation

    I was able to create a decoder(ID3D11VideoDecoder) but I don’t know how to supply it the raw H264 packets and get the YUV or NV12 data as output.
    (Or if its possible to render the output directly to the texture since I can get the ID3D11Texture2D pointer)

    so my question is, How do you send the raw h264 packets to this decoder and get the output from it ?

    Also, this is for real time operation so I’m trying to achieve minimal latency.

    Thanks in advance !

  • ffmpeg trimming audio WAV files and setting timecode

    14 juillet 2022, par user19551045

    I am currently trying to cut an audio file to match the length of a video (without combining the two...just looking at timecodes) and produce a trimmed audio file that has a timecode that will match up with the video, the video is considered the absolute truth.

    


    Currently, the issue is that the timecodes from the original audio file do not get carried over into the new cropped audio file. So, the starting timecode is now 00:00:00:00 instead of say 07:20:02:14. Even using the -timecode commands and trying to hardcode the timecode that way doesn't seem to do the trick. I am wondering if there is any way around this ? I just want to do as minimal to the raw audio as possible...just change the audio file's length while setting the timecodes so the new audio will line up with the video. Any thoughts/suggestions welcome !

    


    Currently I have tried two options that don't seem to work :
using ffmpeg cmds :

    


    
        cmd2 = r'{} -ss "{}" -i "{}" -codec copy -timecode "{}" "{}"'.format(
            FFMPEG_PATH,
            abs(tc_diff_in_seconds),
            audio_path,
            "17074647",
            out_path
        )


    


    and also using pydub :

    


            current_audio = AudioSegment.from_wav("{}".format(audio_path))
        start_time_in_milli = abs(tc_diff_in_seconds*1000)
        end_time_in_milli = start_time_in_milli + video_dur_in_seconds * 1000
        trimmed_audio = current_audio[start_time_in_milli:end_time_in_milli]
        trimmed_audio.export('{}'.format(out_path), format='WAV', parameters=["-timecode", "17:07:46:47"])


    


    Any thoughts/suggestions welcome ! Thanks

    


  • Why use sysconf(_SC_NPROCESSORS_CONF) to get the number of CPU cores in x264 ?

    5 novembre 2017, par bknieven

    I find x264 use sysconf(_SC_NPROCESSORS_CONF) instead of sysconf(SC_NPROCESSORS_ONLN) to get the number of CPU cores.

    Here is the code snippet in x264/common/cpu.c :

    ...
    #ifdef __ANDROID__
       // Android NDK does not expose sched_getaffinity
       return sysconf( _SC_NPROCESSORS_CONF );
    #else
       ...
    ....

    And I find the difference between _SC_NPROCESSORS_CONF and _SC_NPROCESSORS_ONLN in this manual :

    sysconf (_SC_NPROCESSORS_CONF) which returns the number of processors
    the operating system configured. But it might be possible for the
    operating system to disable individual processors and so the call
    sysconf (_SC_NPROCESSORS_ONLN) returns the number of processors which
    are currently online (i.e., available).

    I have two questions :

    1. What is the difference between "the number of processors the operating system configured" and "the number of processors which are currently online" ?
    2. Why x264 use _SC_NPROCESSORS_CONF in Android to get the number of CPU cores ?