
Recherche avancée
Autres articles (66)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, 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 (...) -
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 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 (...)
Sur d’autres sites (8454)
-
Making a timelapse by drag and drop - A rebuild of an old script using ImageMagick
14 août 2019, par cursor_majorI 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``` -
How can I make windows "like" the mp4 files I create in Linux and sync with Rsync
17 juillet 2019, par Geoff FoxI am a meteorologist on TV remotely from a studio I built. My control room uses a TriCaster, an amazing studio-in-a-box which runs on a Windows 7 variant. I make my weather maps myself on a Centos 7 machine — around 40,000/day.
I don’t entirely understand the problem, but here’s a quote from someone helping me at NewTek (the TriCaster company)
Rsync is built on a *nix based environment where all the file permissions and attributes are based on the Linux environment. There is no meaning for this in NTFS and Windows. The result is you get files that will most likely have the read-only flag set or no flag at all. Other attributes will be delivered as null. I’m sure from your own programming experience, programs don’t like null values and they generally have to be accounted for very specifically.
And so the finely tuned TriCaster stumbles, meaning lost frames or other problems caused by my short weather animations.
Here are some samples of the Rsync code I use
rsync -r -t -s -v --no-p --chmod=ugo=rwX /var/www/html/output/loops/mp4/conus*.mp4 /mnt/tricaster/Clips/Import
rsync -r -t -s -v --no-p --chmod=ugo=rwX /var/www/html/output/loops/mp4/nebraska*.mp4 /mnt/tricaster/Clips/Import
rsync -r -t -s -v --no-p --chmod=ugo=rwX /var/www/html/output/loops/mp4/northernplains*.mp4 /mnt/tricaster/Clips/ImportThese are mp4 files. They are only used locally. I really don’t care what flags are checked and permissions filled as long as Windows 7 doesn’t care.
At this point I always like to tell folks, though I do write some code my last computer class was in high school,’67-68 semester. Thanks in advance for your help.
-
ffmpeg - Invalid report file level (windows)
24 octobre 2019, par Pedro Lobitoffmpeg
is giving me an error and I couldn’t get much help googling it, besides a thread on ffmpeg mailing list dated 5 years ago which doesn’t address the exact same problem.No matter which ffmpeg version or build for windows I use, the error is always :
c:\>ffmpeg.exe
Invalid report file levelI’ve been using
ffmpeg
on the same computer for years and I’ve no idea where the problem started and how to debug it. Any help is welcome.
Notes :
- No antivirus is running
ffmpeg.exe
is on windowspath
- I’ve tried installing
ffmpeg
withchoco install
ffmpegbut it reports the same error.