Recherche avancée

Médias (91)

Autres articles (105)

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

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

Sur d’autres sites (10456)

  • Why is chrominance lost when i OpenSharedResource from a ffmpeg AVFrame resource ?

    19 avril 2022, par Logoro
    D3D11_TEXTURE2D_DESC texture_desc = {0};&#xA;texture_desc.Width = 640;&#xA;texture_desc.Height = 480;&#xA;texture_desc.MipLevels = 1;&#xA;texture_desc.Format = DXGI_FORMAT_NV12;&#xA;texture_desc.SampleDesc.Count = 1;&#xA;texture_desc.ArraySize = 1;&#xA;texture_desc.Usage = D3D11_USAGE_DEFAULT;&#xA;texture_desc.MiscFlags = D3D11_RESOURCE_MISC_SHARED;&#xA;&#xA;Microsoft::WRL::ComPtr<id3d11texture2d> temp_texture_for_my_device{nullptr};&#xA;my_device->CreateTexture2D(&amp;texture_desc, NULL, &amp;temp_texture_for_my_device);&#xA;&#xA;Microsoft::WRL::ComPtr<idxgiresource> dxgi_resource{nullptr};&#xA;temp_texture_for_my_device.As(&amp;dxgi_resource);&#xA;HANDLE shared_handle = NULL;&#xA;dxgi_resource->GetSharedHandle(&amp;shared_handle);&#xA;dxgi_resource->Release();&#xA;&#xA;Microsoft::WRL::ComPtr<id3d11texture2d> temp_texture_for_ffmpeg_device {nullptr};&#xA;ffmpeg_device->OpenSharedResource(shared_handle, __uuidof(ID3D11Texture2D), (void**)temp_texture_for_ffmpeg_device.GetAddressOf());&#xA;ffmpeg_device_context->CopySubresourceRegion(temp_texture_for_ffmpeg_device.Get(), 0, 0, 0, 0, (ID3D11Texture2D*)ffmpeg_avframe->data[0], (int)ffmpeg_avframe->data[1], NULL);&#xA;ffmpeg_device_context->Flush();&#xA;</id3d11texture2d></idxgiresource></id3d11texture2d>

    &#xA;

    I copy temp_texture_for_ffmpeg_device to a D3D11_USAGE_STAGING, it's normal, but when i copy temp_texture_for_my_device to a D3D11_USAGE_STAGING, i lost the chrominance data.

    &#xA;

    When i map the texture to cpu via D3D11_USAGE_STAGING :

    &#xA;

    temp_texture_for_ffmpeg_device : RowPitch is 768, DepthPitch is 768 * 720.&#xA;temp_texture_for_my_device : RowPitch is 1024, DepthPitch is 1024 * 480.

    &#xA;

    I think there are some different parameters between the two devices(or device context ?), but I don't know what parameters would cause such a difference in behavior.

    &#xA;

    my_device and my_device_context are created by D3D11On12CreateDevice

    &#xA;

  • Revision 1c396f3f8e : Merge "Fix a thread lost bug in frame parallel decode."

    5 février 2015, par hkuang

    Merge "Fix a thread lost bug in frame parallel decode."

  • Revision b104b84058 : Fix a thread lost bug in frame parallel decode. After syncing the frame worker

    4 février 2015, par hkuang

    Changed Paths :
     Modify /vp9/decoder/vp9_dthread.h


     Modify /vp9/vp9_dx_iface.c



    Fix a thread lost bug in frame parallel decode.

    After syncing the frame worker thread, avaiable thread count should
    increase by 1 even the worker thread does not have displayable frame
    to output.

    Change-Id : I9eeb87720fed82dfe38555286833ff88e8a8e746

Navigation