Recherche avancée

Médias (29)

Mot : - Tags -/Musique

Autres articles (111)

  • Possibilité de déploiement en ferme

    12 avril 2011, par

    MediaSPIP peut être installé comme une ferme, avec un seul "noyau" hébergé sur un serveur dédié et utilisé par une multitude de sites différents.
    Cela permet, par exemple : de pouvoir partager les frais de mise en œuvre entre plusieurs projets / individus ; de pouvoir déployer rapidement une multitude de sites uniques ; d’éviter d’avoir à mettre l’ensemble des créations dans un fourre-tout numérique comme c’est le cas pour les grandes plate-formes tout public disséminées sur le (...)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

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

  • Selection of projects using MediaSPIP

    2 mai 2011, par

    The examples below are representative elements of MediaSPIP specific uses for specific projects.
    MediaSPIP farm @ Infini
    The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)

Sur d’autres sites (8723)

  • Sony Launches Less Useful Z5U

    18 novembre 2009

    Sony today announced the NXCAM, an AVCHD-based "professional" camera which bears a striking resemblance to the EX1 and Z5U.

    You get 1080p exmor CMOS chips (presumably 1/3" ?) and records AVCHD to the highly popular (sarcasm) Memory Stick media.

    Pricing hasn’t been announced, but presumably it’ll be in the $4000 range like the Z5U. I’ll be curious to see how this shakes out in the market.

  • bash loop through list of file paths - characters get removed when sending to ffmpeg [duplicate]

    9 octobre 2018, par Brad Johnson

    This question already has an answer here :

    I have a text file that contains a list of paths to flac files I want to convert to wav. Here is a small section of it :

    /mnt/nfs/Music/Rob D/1995 - Clubbed To Death/Rob D - 02 - Clubbed To Death _Kurayamino Variation_.flac
    
/mnt/nfs/Music/Blonde Redhead/2000 - Melody of Certain Damaged Lemons/11 - For the Damaged Coda.flac
    
/mnt/nfs/Music/I Monster/2001 - Daydream In Blue/01 - Daydream In Blue.flac
    
/mnt/nfs/Music/Moby/2002 - Extreme Ways/01 - Extreme Ways.flac
    
/mnt/nfs/Music/RJD2/2002 - Deadringer/01 - The Horror.flac
    
/mnt/nfs/Music/RJD2/2002 - Deadringer/03 - Smoke & Mirrors.flac
    
/mnt/nfs/Music/RJD2/2002 - Deadringer/06 - Ghostwriter.flac
    
/mnt/nfs/Music/RJD2/2002 - Deadringer/10 - Chicken-Bone Circuit.flac
    
/mnt/nfs/Music/FC Kahuna/2003 - Hayling/01 - Hayling _Original_.flac
    
/mnt/nfs/Music/Lamb/2003 - Between Darkness and Wonder/04 - Angelica.flac

    I’m trying to loop through it like so :

    while read -r line; do
    
 wavfile=$(basename "$line")
    
 wavfile="${wavfile%.*}"
    
 ffmpeg -i "$line" "$2/$wavfile.wav"
    
done <$1

    ...where $1 is where I would pass the name of the text file and $2 is the destination directory.

    Here is the output with the irrelevant ffmpeg junk pruned out :

    Input #0, flac, from '/mnt/nfs/Music/Rob D/1995 - Clubbed To Death/Rob D - 02 - Clubbed To Death _Kurayamino Variation_.flac':
    
...
    
Output #0, wav, to '/mnt/gray/Clubbed To Death/Rob D - 02 - Clubbed To Death _Kurayamino Variation_.wav':
    
...
    
/nfs/Music/Blonde Redhead/2000 - Melody of Certain Damaged Lemons/11 - For the Damaged Coda.flac: No such file or directory
    
...
    
Input #0, flac, from '/mnt/nfs/Music/I Monster/2001 - Daydream In Blue/01 - Daydream In Blue.flac':
    
...
    
Output #0, wav, to '/mnt/gray/Clubbed To Death/01 - Daydream In Blue.wav':
    
...
    
nt/nfs/Music/Moby/2002 - Extreme Ways/01 - Extreme Ways.flac: No such file or directory
    
...
    
Input #0, flac, from '/mnt/nfs/Music/RJD2/2002 - Deadringer/01 - The Horror.flac':
    
...
    
Output #0, wav, to '/mnt/gray/Clubbed To Death/01 - The Horror.wav':
    
...
    
nt/nfs/Music/RJD2/2002 - Deadringer/03 - Smoke & Mirrors.flac: No such file or directory
    
...
    
Input #0, flac, from '/mnt/nfs/Music/RJD2/2002 - Deadringer/06 - Ghostwriter.flac':
    
...
    
Output #0, wav, to '/mnt/gray/Clubbed To Death/06 - Ghostwriter.wav':
    
...
    
nt/nfs/Music/RJD2/2002 - Deadringer/10 - Chicken-Bone Circuit.flac: No such file or directory
    
...
    
Input #0, flac, from '/mnt/nfs/Music/FC Kahuna/2003 - Hayling/01 - Hayling _Original_.flac':
    
...
    
Output #0, wav, to '/mnt/gray/Clubbed To Death/01 - Hayling _Original_.wav':
    
...
    
/nfs/Music/Lamb/2003 - Between Darkness and Wonder/04 - Angelica.flac: No such file or directory

    If you pay attention to the paths that ffmpeg reports don’t exist, you’ll see that a seemingly random number of characters has been removed from the beginning. This appears to happen on even numbered lines, but odd numbered lines work. I can only reproduce this behavior when using ffmpeg. If I replace the ffmpeg line with a simple echo statement, every file path is shown to be correct. How can this be ?

    Other suggestions of accomplishing this are also welcome, however I do need the files processed in the order by which I have them listed in the file.

  • ffmpeg gets the wrong color_range [closed]

    16 avril, par Rems

    I have videos with incorrect color_range information.
Their mediainfo is like this :

    


    Color range : Limited
    
color_range_Original : Full

    


    The video is indeed limited, and one of our editing tools, for unknown reasons, adds this color_range_Original tag.
The problem is that when ffmpeg processes these videos, it sees the color range as Full. It retrieves the wrong information, which can lead to problems and color loss later on.
I know it's possible to specify to ffmpeg the input range with the scale filter, but in this workflow I don't re-encode the videos, so I can't use filters.

    


    Is there another way to specify the input range to ffmpeg ? Thanks

    


Navigation