Recherche avancée

Médias (29)

Mot : - Tags -/Musique

Autres articles (55)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

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

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

Sur d’autres sites (11074)

  • opus_pvq : fix PVQ search for K 5 and low Ns

    19 février 2017, par Rostislav Pehlivanov
    opus_pvq : fix PVQ search for K < 5 and low Ns

    If the PVQ search picked a place to increment/decrement on the y[]
    
vector which had no pulse then it would cause a desync since it would
    
change the sum in the wrong direction. Fix this by not considering
    
places without pulses as viable.
    

    This makes the PVQ search slightly worse at K < 5 which isn’t all that
    
common. Still, this is a workaround to prevent making broken files until
    
I can think of a better way of fixing it.
    

    Also add an assertion, which can be removed or moved to assert1/2 once
    
the PVQ search is stable.
    

    Signed-off-by : Rostislav Pehlivanov <atomnuker@gmail.com>
    • [DH] libavcodec/opus_pvq.c

  • Video upload size

    16 mai 2014, par Jonas m

    I’m having a hard time figuring this one out, so hopefully, some of you who has tried this before, will take the time to reply and share your knowledge.

    I’m working on a site, which after release, will be feeded in the television and other commercial places. The site asks the user to upload a video with a story, and we expect alot of people to do so.

    My problem is the whole storage/space talk. A normal, unencoded iPhone recording easily fills around 100-120 MB for a minute or two.

    I’ve tried setting up and using FFMPEG to re-encode the movies, but the problem is, that one encoding sucks up 100% of the CPU, leaving the site inaccisible for anybody else.

    Is there anything you could suggest, which would be sufficient for such a site ? The client is on a budget, so price is a consideration aswell. Best of all would be a free alternative to etc. FFMPEG, but with less CPU usage.

    My specs are as follows
    CentOs 6 on a
    1GB ram DigitalOcean cloud service with nginx + php-fpm and mysql.

    Im hoping for some cleaver folks to answer this !
    Thanks in advance.
    Jonas

  • Why is packet.pts != frame->pkt_pts in AVFrame ?

    1er juin 2015, par BlenderBender

    Trying to understand some audio/video sync issues via ffmpeg, I noticed the following. Running this code

    while (av_read_frame(formatCtx, &amp;packet) >= 0)
    
{
    
   if (packet.stream_index == videoStream)
    
   {
    
      avcodec_decode_video2(videoCodecCtx, frame, &amp;got_frame, &amp;packet);
    
   }
    

    
   printf("packet.pts = %d\n", packet.pts);
    
   printf("frame->pkt_pts", frame->pkt_pts);
    
}

    shows that frame->pkt_pts in general differs from packet.pts, despite the documentation claiming that frame->pkt_pts is the

    PTS copied from the AVPacket that was decoded to produce this frame

    Moreover I noticed that the difference between the two is big exactly at the places where audio and video are out of sync.

    So, why is packet.pts != frame->pkt_pts ?

Navigation