
Recherche avancée
Autres articles (47)
-
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 (...) -
Mise à disposition des fichiers
14 avril 2011, parPar défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...) -
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 (...)
Sur d’autres sites (8010)
-
Trying to convert an mp3 file to a Numpy Array, and ffmpeg just hangs
5 juillet 2016, par RichI’m working on a music classification methodology with Scikit-learn, and the first step in that process is converting a music file to a numpy array.
After unsuccessfully trying to call ffmpeg from a python script, I decided to simply pipe the file in directly :
FFMPEG_BIN = "ffmpeg"
cwd = (os.getcwd())
dcwd = (cwd + "/temp")
if not os.path.exists(dcwd): os.makedirs(dcwd)
folder_path = sys.argv[1]
f = open("test.txt","a")
for f in glob.glob(os.path.join(folder_path, "*.mp3")):
ff = f.replace("./", "/")
print("Name: " + ff)
aa = (cwd + ff)
command = [ FFMPEG_BIN,
'-i', aa,
'-f', 's16le',
'-acodec', 'pcm_s16le',
'-ar', '22000', # ouput will have 44100 Hz
'-ac', '1', # stereo (set to '1' for mono)
'-']
pipe = sp.Popen(command, stdout=sp.PIPE, bufsize=10**8)
raw_audio = pipe.proc.stdout.read(88200*4)
audio_array = numpy.fromstring(raw_audio, dtype="int16")
print (str(audio_array))
f.write(audio_array + "\n")The problem is, when I run the file, it starts ffmpeg and then does nothing :
[mp3 @ 0x1446540] Estimating duration from bitrate, this may be inaccurate
Input #0, mp3, from '/home/don/Code/Projects/MC/Music/Spaz.mp3':
Metadata:
title : Spaz
album : Seeing souns
artist : N*E*R*D
genre : Hip-Hop
encoder : Audiograbber 1.83.01, LAME dll 3.96, 320 Kbit/s, Joint Stereo, Normal quality
track : 5/12
date : 2008
Duration: 00:03:50.58, start: 0.000000, bitrate: 320 kb/s
Stream #0:0: Audio: mp3, 44100 Hz, stereo, s16p, 320 kb/s
Output #0, s16le, to 'pipe:':
Metadata:
title : Spaz
album : Seeing souns
artist : N*E*R*D
genre : Hip-Hop
date : 2008
track : 5/12
encoder : Lavf56.4.101
Stream #0:0: Audio: pcm_s16le, 22000 Hz, mono, s16, 352 kb/s
Metadata:
encoder : Lavc56.1.100 pcm_s16le
Stream mapping:
Stream #0:0 -> #0:0 (mp3 (native) -> pcm_s16le (native))
Press [q] to stop, [?] for helpIt just sits there, hanging, for far longer than the song is. What am I doing wrong here ?,
-
Path to publish FFMPEG video files to Azure Blob Storage ?
25 janvier 2016, par CG-GuyPlease kindly help me get out of a bad situation with a very very unhappy client. I am using FFMPEG based app to publish video files to Azure Blob storage, but the files are not going through the network. FFMPEG app has full access to firewall ports. FFMPEG communication shell show files are published without errors. A look at TCP connections shows the app is making connection with Azure account remote address 104.208.XXX.XX and remote port 443. However, it drops the connection and starts repeating attempts over and over. It will then time out after countless attempts and crash the app. Here is my publish point. Is this the correct publish point for this kind of connection ? What is the proper connection string ? :
https://account-name.blob.core.windows.net/video/video.flv /DestKey :account-storage-key
I have also tried http:// without success. Same thing happens. It attempts connecting to remote address and port 80. Again, after several attempts it will timeout and crash. System is a Server 2008 R2 unit on-site, not VM. Your help is much appreciated. Thanks a lot !
-
How to upload files to Azure Blob Stotage like FTP ?
25 janvier 2016, par CG-GuyI am able to upload files from my
ffmpeg
app to an FTP using this path :ftp://[user:password]@server[:port]/MyFolder/video/video.flv
How do I achieve the same thing in Azure Blob ? I have tried this path :
https://[account-name].blob.core.windows.net/video/video.flv /DestKey:[account-storage-key]
But that doesn’t seem to work. TCP connection shows the app is making a connection with the Azure account to the remote address
104.208.XXX.XX
and remote port443
. However, it drops the connection and starts attempts to reconnect repeatedly. It will then time out after countless attempts and crash the app. I have also tried/>
without success. The same thing happens. It attempts connecting to the remote address and port80
.The FFMPEG app has full access to firewall ports and the app communication shell show files are published without errors. System is a Server 2008 R2 unit on-site, not VM.