
Recherche avancée
Médias (3)
-
MediaSPIP Simple : futur thème graphique par défaut ?
26 septembre 2013, par
Mis à jour : Octobre 2013
Langue : français
Type : Video
-
GetID3 - Bloc informations de fichiers
9 avril 2013, par
Mis à jour : Mai 2013
Langue : français
Type : Image
-
GetID3 - Boutons supplémentaires
9 avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
Autres articles (39)
-
Les tâches Cron régulières de la ferme
1er décembre 2010, parLa gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
Le super Cron (gestion_mutu_super_cron)
Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...) -
Les formats acceptés
28 janvier 2010, parLes commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
ffmpeg -codecs ffmpeg -formats
Les format videos acceptés en entrée
Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
Les formats vidéos de sortie possibles
Dans un premier temps on (...) -
Librairies et binaires spécifiques au traitement vidéo et sonore
31 janvier 2010, parLes logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
Binaires complémentaires et facultatifs flvtool2 : (...)
Sur d’autres sites (5544)
-
Specifying FFMPEG in the requirements section of 'buildozer.spec' causing [libavformat/network.o] Error 1
18 juillet 2022, par GJ78My question relates to how to mitigate an ffmpeg requirement listed in a buildozer.spec that is causing compile errors using buildozer.



GOAL :



Using buildozer to ensure FFMPEG can be embedded within a small Kivy app so i can utilise youtube_dl functionality on my android phone.



THE ISSUE :
Specifying FFMPEG in the requirements section of 'buildozer.spec' causes the following error message :

common.mak:60 : recipe for target 'libavformat/network.o' failed

make : [libavformat/network.o] Error 1

make : Waiting for unfinished jobs...


What have I done to resolve myself :

1. Ensured LOG LEVEL 2 is specified.


- 

-
Upgraded cython from Version 21 to 27. Then downgraded to 25, then 21 then 20 to see if this resolved anything. It didn't.
-
In BUILDOZER.SPEC, switched between Android NDK crystax-ndk-10.3.2 and android-ndk-r16b. (Note have reverted back to Crystax 10.3.2) in my NDK PATH.
-
In BUILDOZER.SPEC, changed android.api from 19 to 15 (just to see if this has any positive effects).
-
executed : rm -Rf .buildozer between each compiling attempt.
-
Part extract of Buildozer.log :



In file included from libavformat/dump.c:37:0 :

libavformat/avformat.h:893:21 : note : declared here

 AVCodecContext codec ;
 ^

CC libavformat/format.o

CC libavformat/golomb_tab.o

CC libavformat/h264dec.o

CC libavformat/hevc.o

CC libavformat/http.o

CC libavformat/httpauth.o

CC libavformat/id3v1.o

CC libavformat/id3v2.o

CC libavformat/img2.o

CC libavformat/isom.o

CC libavformat/log2_tab.o

CC libavformat/m4vdec.o

CC libavformat/metadata.o
CC libavformat/mov_chan.o

CC libavformat/mov.o

CC libavformat/movenc.o

CC libavformat/movenccenc.o

CC libavformat/movenchint.o

CC libavformat/mpegvideodec.o

CC libavformat/mux.o

CC libavformat/network.o

In file included from libavformat/network.h:29:0,

 from libavformat/network.c:22 :

libavformat/os_support.h:67:32 : error : expected declaration specifiers or '...' before '(' token

 # define lseek(f,p,w) lseek64((f), (p), (w))

 ^
libavformat/os_support.h:67:37 : error : expected declaration specifiers or '...' before '(' token

 # define lseek(f,p,w) lseek64((f), (p), (w))

 ^
libavformat/os_support.h:67:42 : error : expected declaration specifiers or '...' before '(' token

 # define lseek(f,p,w) lseek64((f), (p), (w))

 ^
common.mak:60 : recipe for target 'libavformat/network.o' failed

make : [libavformat/network.o] Error 1

make : * Waiting for unfinished jobs.... -
Part extract of Buildozer.spec



(str) Title of your application



title = myapplication



(str) Package name



package.name = myapp



(str) Package domain (needed for android/ios packaging)



package.domain = org.test



(str) Source code where the main.py live



source.dir = .



(list) Source files to include (let empty to include all the files)



source.include_exts = py,png,jpg,kv,atlas



(list) List of inclusions using pattern matching



source.include_patterns = assets/,images/.png



(list) Source files to exclude (let empty to not exclude anything)



source.exclude_exts = spec



(list) List of directory to exclude (let empty to not exclude anything)



source.exclude_dirs = tests, bin



(list) List of exclusions using pattern matching



source.exclude_patterns = license,images//.jpg



(str) Application versioning (method 1)



version = 0.1



(str) Application versioning (method 2)



version.regex = version = '"['"]



version.filename = %(source.dir)s/main.py



(list) Application requirements



comma seperated e.g. requirements = sqlite3,kivy



requirements = ffmpeg,python2,hostpython2,kivy,youtube-dl



(str) Custom source folders for requirements



Sets custom source for any requirements with recipes



requirements.source.kivy = ../../kivy



(list) Garden requirements



garden_requirements =



(str) Presplash of the application



presplash.filename = %(source.dir)s/data/presplash.png



(str) Icon of the application



icon.filename = %(source.dir)s/data/icon.png



(str) Supported orientation (one of landscape, portrait or all)



orientation = portrait



(list) List of service to declare



services = NAME:ENTRYPOINT_TO_PY,NAME2:ENTRYPOINT2_TO_PY



OSX Specific



author = © Copyright Info



change the major version of python used by the app



osx.python_version = 3



Kivy version to use



osx.kivy_version = 1.9.1



Android specific



(bool) Indicate if the application should be fullscreen or not



fullscreen = 0



(string) Presplash background color (for new android toolchain)



Supported formats are : #RRGGBB #AARRGGBB or one of the following names :



red, blue, green, black, white, gray, cyan, magenta, yellow, lightgray,



darkgray, grey, lightgrey, darkgrey, aqua, fuchsia, lime, maroon, navy,



olive, purple, silver, teal.



android.presplash_color = #FFFFFF



(list) Permissions



android.permissions = INTERNET



(int) Android API to use



android.api = 19



(int) Minimum API required



android.minapi = 9



(int) Android SDK version to use



android.sdk = 20



(str) Android NDK version to use



android.ndk = 10.3.2



(bool) Use —private data storage (True) or —dir public storage (False)



android.private_storage = True



(str) Android NDK directory (if empty, it will be automatically downloaded.)



android.ndk_path = /home/gjones/Downloads/crystax-ndk-10.3.2



(str) Android SDK directory (if empty, it will be automatically downloaded.)



android.sdk_path =



(str) ANT directory (if empty, it will be automatically downloaded.)



android.ant_path =
-
Lastly, when I remove ffmpeg from requirements in buildozer.spec, the .APK compiles successfully and i can deploy it on to my phone with the KIVY GUI. Obviously, ffmpeg functionality is not present.

















Current Environment Specs :



- 

- Running Linux Mint 17.2 as a Virtual Box VM
- Buildozer Version : 0.35dev
- Cython Version : 0.25









Any advice would be greatly appreciated.



Lastly, if there is no obvious solution via buildozer, do i need to compile ffmpeg for Android separately and somehow include this somewhere in the buildozer spec file to prevent this error message ?



Thanks in advance.


-
-
Sending periodic metadata in fragmented live MP4 stream ?
20 septembre 2022, par El SampsaAs suggested by the topic, I'm wondering if it's possible to send metadata about the stream contents periodically in a fragmented MP4 live stream.



I'm using the following command (1) to get fragmented MP4 :



ffmpeg -i rtsp://admin:12345@192.168.0.157 -c:v copy -an -movflags empty_moov+omit_tfhd_offset+frag_keyframe+default_base_moof -f mp4 ...




My main program reads the fragments from this command from either stdout or from a (unix domain) socket and gets :



ftyp
moov
moof
mdat
moof
mdat
moof
mdat 
...




So, the first fragments I get are ftyp and moov which are metadata and describe the stream contents.



Now a client program connects at a later time to the main program. The problem is, that at that point, the ftype and moov fragments are long gone.



Is there a way (=ffmpeg command option) to make this work similar to MPEGTS (aka mpeg transport stream), and resend metadata periodically with the stream ? Like this :



ftyp
moov
moof
mdat
moof
mdat
moof
mdat 
ftyp
moov
moof
mdat
moof
mdat
moof
mdat 
...




.. or is my only option to cache the ftyp and moov packets in my main program and re-send them to the client program when it requests the stream ?



A related link : What exactly is Fragmented mp4(fMP4) ? How is it different from normal mp4 ?



Caching and resending ftyp and moov each time a new client connects is not that straightforward either .. as it somehow brokes the stream (at least the browser MSE extensions don't like such a stream). There seems to be lots of sequence numbers and stuff in the moof packets that should be modified. (+)



Another option is to pass the stream through another FFmpeg process that does the remuxing (and corrects moof packets). Things are further complicated by the fact that command (1) does not give cleanly-separated ftyp, moov, moof, etc. packets.



Any thoughts / solutions appreciated.



EDIT : regarding (+), MSE seems to have problems playing fragmented MP4 with gaps : https://bugs.chromium.org/p/chromium/issues/detail?id=516114


-
New Piwik Mobile 2.3.0 is released
25 novembre 2016, par Thomas Steur — Piwik Mobile ReleasesNew Piwik Mobile 2.3.0 update is now available for Android 7+ and iOS10+ devices. Read below to learn more, including a special message to Android users.
What’s new in Piwik Mobile ?
This new version brings some bug fixes and improvements to our Android and iOS apps :
- Custom Dimension reports are now shown within the app
- Segments are now applied in sub-reports #5353
- User ID is now displayed in visitor profile #5341
- URL submitted on login are now trimmed #5338
- iOS : a 64 bit version of the app #5328
- Android : Remove possibility to disable SSL validation #5354 (read more below)
- We have updated the underlying framework bringing some performance and compatibility improvements
Attention to Android users : read more
We have removed the possibility to disable SSL validation in this update due to a Google Play restriction. We know there are some users depending on this feature and we recommend to not update if you cannot make the SSL certificate valid for your Piwik Analytics domain.
Download the Apps
Update now or install either the iOS version or the Android version. Because of the SSL validation change we have made the Android update only available to Android 7+ devices. If you are an Android 6+ user and still want to get the update, you can download Piwik 2.3.0 for Android 6+ from our website.
If you experience any issues with this version please let us know.
Sponsor
The new Piwik Mobile release has been sponsored by InnoCraft, the creators of Piwik.
Happy analytics on the go,