Recherche avancée

Médias (91)

Autres articles (67)

  • Pas question de marché, de cloud etc...

    10 avril 2011

    Le vocabulaire utilisé sur ce site essaie d’éviter toute référence à la mode qui fleurit allègrement
    sur le web 2.0 et dans les entreprises qui en vivent.
    Vous êtes donc invité à bannir l’utilisation des termes "Brand", "Cloud", "Marché" etc...
    Notre motivation est avant tout de créer un outil simple, accessible à pour tout le monde, favorisant
    le partage de créations sur Internet et permettant aux auteurs de garder une autonomie optimale.
    Aucun "contrat Gold ou Premium" n’est donc prévu, aucun (...)

  • Dépôt de média et thèmes par FTP

    31 mai 2013, par

    L’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
    Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)

  • Activation de l’inscription des visiteurs

    12 avril 2011, par

    Il est également possible d’activer l’inscription des visiteurs ce qui permettra à tout un chacun d’ouvrir soit même un compte sur le canal en question dans le cadre de projets ouverts par exemple.
    Pour ce faire, il suffit d’aller dans l’espace de configuration du site en choisissant le sous menus "Gestion des utilisateurs". Le premier formulaire visible correspond à cette fonctionnalité.
    Par défaut, MediaSPIP a créé lors de son initialisation un élément de menu dans le menu du haut de la page menant (...)

Sur d’autres sites (10307)

  • Making a timelapse by drag and drop - A rebuild of an old script using ImageMagick

    14 août 2019, par cursor_major

    I have written an apple script previously to automate a task I do in my work many times.

    I shoot Raw + JPG in camera, copy to hard drive.

    I then drag named and dated folder eg. "2019_08_14_CAM_A_CARD_01" on to an automator app and it divides the files in to folders "NEF" and "JPG" respectively.

    I then drag the appropriate "JPG" folder onto my Timelapse app and it runs the image sequence process in QT7 and then saves the file with the parent folder name in the grandparent folder. This keeps things super organised for when I want to re link to the original RAW files.

    [code below]

    It is a 2 step process and works well for my needs, however, Apple are going to be resigning Quicktime 7 Pro so my app has a foreseeable end of life.

    I want to take this opportunity to refine and improve the process using terminal and ImageMagick.

    I have managed to work some code that runs well in terminal, but I have to navigate to the folder first then run a script. It doesn’t do the file renaming and doesn’t save in the right place.

    Also, when I try and run the simple script in an automator ’App’ it throws up errors even before trying to add anything clever with the file naming.

    Later, once I have recreated my timelapse. maker app I want to get clever with more of ImageMagicks commands and overlay a small super of the original frame name in the corner so I can expedite my reconnecting workflow.

    I’m sorry, I’m a photographer not a coder but I’ve been bashing my head trying to work this out and I’ve hit a brick wall.

    File Sorter

       repeat with d in dd
           do shell script "d=" & d's POSIX path's quoted form & "
    cd \"$d\" || exit

    mkdir -p {MOV,JPG,NEF,CR2}
    find . -type f -depth 1 -iname '*.mov' -print0 | xargs -0 -J % mv % MOV
    find . -type f -depth 1 -iname '*.cr2' -print0 | xargs -0 -J % mv % CR2
    find . -type f -depth 1 -iname '*.jpg' -print0 | xargs -0 -J % mv % JPG
    find . -type f -depth 1 -iname '*.nef' -print0 | xargs -0 -J % mv % NEF

    for folder in `ls`;
    do if [ `ls $folder | wc -l` == 0 ]; then
       rmdir $folder;
    fi; done;

    "
       end repeat
    end open```



    Timelapse Compiler

    ```on run {input, parameters}
       repeat with d in input
           set d to d's contents
           tell application "Finder"
               set seq1 to (d's file 1 as alias)
               set dparent to d's container as alias
               set mov to "" & dparent & (dparent's name) & ".mov"
           end tell
           tell application "QuickTime Player 7"
               activate
               open image sequence seq1 frames per second 25
               tell document 1
                   with timeout of 500 seconds
                       save self contained in file mov
                   end timeout
                   quit
               end tell
           end tell
       end repeat
       return input
    end run```


    Current code that runs from within Terminal after I have navigated to folder of JPGs

    ```ffmpeg -r 25 -f image2 -pattern_type glob -i '*.JPG' -codec:v prores_ks -profile:v 0 imagemagick_TL_Test_01.mov```
  • ffprobe -report not working correctly [closed]

    21 juin 2013, par casper

    For some reason calling this in Terminal :

    ffprobe -show_frames -report myfile.mkv

    does not include the frames info into the log file ? I could not find examples of -report usage, so I guess I am doing something wrong.

    simple "> myreport.txt" at the end of the command will save the output to a text file, but I assume -report feature should take care of putting everything together into one log file, no ?

  • Why is ffmpeg taking up so much memory when I try to stop a livestream ?

    4 juillet 2019, par FiskFan1999

    When the ffmpeg function is running, there are no problems with memory and everything runs smoothly. However, when I attempt to stop the stream/ffmpeg by pressing q (or ctrl-c), ffmpeg freezes, doesn’t take any other inputs, and suddenly takes up an obscene amount of memory.

    I am using ffmpeg to livestream on youtube. I am using a MacBook Mid 2015 running macOS Mojave.

    here is the function I am using with ffmpeg.

    ffmpeg -re -f lavfi -i testsrc2=s=1280x720:r=60 -re -i "INPUT FILE.mp3" -vcodec libx264 -pix_fmt yuv420p -preset "ultrafast" -r 60 -g 120 -b:v 6168000 -filter_complex "[0]scale=1280:720;[1]aloop=start=0:size=202*44100:loop=-1" -acodec libmp3lame -ar 44100 -threads 3 -b:a 640000 -qscale:a 5 -bufsize 512k -f flv ${YOUTUBE_URL}/${KEY}

    The command runs perfectly and as expected while it is running. At this point, in Activity Monitor I can see that ffmpeg seems to peak to about 101 MB. When I press q, which is the button to end the encoding, if the stream had been going for about ten minutes ffmpeg freezes and in Activity monitor the ffmpeg command appears to climb to several gigabytes of memory without any sign of stopping. The most I have noticed is about 6 GB before I killed the command. Ffmpeg seems to be writing almost a gigabyte of data into memory a second. In fact, this slows down my computer when it occurs and threatens to completely fill up my memory.

    When this occurs, there are no error messages (except for warnings about running out of memory) and the terminal running ffmpeg seems to not respond to any kill commands, and the only way to alleviate the situation is to force close the terminal window itself.

    I’m wondering if somehow I am creating a memory leak issue or if I wrote something wrong or didn’t include something that would be necessary for live-streaming with ffmpeg.