
Recherche avancée
Autres articles (41)
-
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
XMP PHP
13 mai 2011, parDixit Wikipedia, XMP signifie :
Extensible Metadata Platform ou XMP est un format de métadonnées basé sur XML utilisé dans les applications PDF, de photographie et de graphisme. Il a été lancé par Adobe Systems en avril 2001 en étant intégré à la version 5.0 d’Adobe Acrobat.
Étant basé sur XML, il gère un ensemble de tags dynamiques pour l’utilisation dans le cadre du Web sémantique.
XMP permet d’enregistrer sous forme d’un document XML des informations relatives à un fichier : titre, auteur, historique (...) -
Soumettre améliorations et plugins supplémentaires
10 avril 2011Si vous avez développé une nouvelle extension permettant d’ajouter une ou plusieurs fonctionnalités utiles à MediaSPIP, faites le nous savoir et son intégration dans la distribution officielle sera envisagée.
Vous pouvez utiliser la liste de discussion de développement afin de le faire savoir ou demander de l’aide quant à la réalisation de ce plugin. MediaSPIP étant basé sur SPIP, il est également possible d’utiliser le liste de discussion SPIP-zone de SPIP pour (...)
Sur d’autres sites (3185)
-
ffmpeg file read permission denied in application but not in debug
25 novembre 2019, par PurgitoriaMy application has a function of taking captured images and using an ffmpeg background worker to stitch these into a time lapse video. The GUI has some simple options for video quality and for the source folder and output file. I had an older version of my application written in VB.NET and that worked without issue but i am rewriting in C# as it supports additional capture and filter capability in the image processing but am having real trouble figuring out what is wrong with this function.
I have tried relocating ffmpeg to different locations just in case it was a permissions issue but that had no effect and i also tried to put the function in a "try" with a message box to output any exceptions but i got different errors that prevented me from compiling the code. When i run the application from within VS 2015 in the debugging tool the function works just fine and it will create a video from a collection of still images and create a log but when i build and install the application it does not work at all and i cannot see what is causing it to fail. In the options for ffmpeg i used the -report to output a log of what happens in the background worker and in debug it creates this log but from the application it does not so i presumed it was not even running ffmpeg and going straight to the completed stage of the function.
Function startConversion()
CheckForIllegalCrossThreadCalls = False
Dim quality As Integer = trbQuality.Value
Dim input As String = tbFolderOpen.Text
Dim output As String = tbFolderSave.Text
Dim exepath As String = Application.StartupPath + "\\bin\ffmpeg.exe"
input = input & "\SCAImg_%1d.bmp"
input = Chr(34) & input & Chr(34)
output = Chr(34) & output & Chr(34)
Dim sr As StreamReader
Dim ffmpegOutput As String
' all parameters required to run the process
proc.StartInfo.UseShellExecute = False
proc.StartInfo.CreateNoWindow = True
proc.StartInfo.RedirectStandardError = True
proc.StartInfo.FileName = exepath
proc.StartInfo.Arguments = "-framerate 25 -start_number 0 -pattern_type sequence -framerate 10 -i " & input & " -r 10 -c:v libx264 -preset slow -crf " & quality & " " & output
proc.Start()
lblInfo.Text = "Conversion in progress... Please wait..."
sr = proc.StandardError 'standard error is used by ffmpeg
btnMakeVideo.Enabled = False
Do
ffmpegOutput = sr.ReadLine
tbProgress.Text = ffmpegOutput
Loop Until proc.HasExited And ffmpegOutput = Nothing Or ffmpegOutput = ""
tbProgress.Text = "Finished !"
lblInfo.Text = "Completed!"
MsgBox("Completed!", MsgBoxStyle.Exclamation)
btnMakeVideo.Enabled = True
Return 0
End FunctionI checked the application folder and it does contain a sub folder \bin with the ffmpeg.exe located within the folder so i then used cmd to run an instance of the installed ffmpeg from the application folder and it seemed to be throwing out permissions errors :
Failed to open report "ffmpeg-20191101-191452.log" : Permission denied Failed to set value ’1’ for option ’report’ : Permission denied Error parsing global options : Permission denied
This seems then like it is certainly a permissions problem but where i am not sure. I did not run in to this error when using VB.NET so i am wondering where i am going wrong now. I thought perhaps it would just be a write permission in the application folder so i the removed the -report and ran ffmpeg again using cmd from my application folder and it then gave the error
C :\Users\CEAstro\Pictures\AnytimeCap : Permission denied
Am i missing something really obvious in my code or is there something more fundamental i have wrong in my setup ?
I should also add that i tried running ffmpeg via cmd from a copy that was manually placed elsewhere (i used the same file) and that actually created the report but again i got a permission denied when trying to read the input files, considering it was from the user "my pictures" folder which should not have restrictions on read/write access i am at a rael loss.
-
How to get Updated Shared Object Files of OpenCV and FFMPEG libraries to overcome Libpng vulnerability ? [duplicate]
3 mars 2017, par LiyaThis question already has an answer here :
-
Libpng vulnerability
2 answers
We seek a technical help on a current issue which we are facing with one of our android application.
Our application is for live video streaming and recording (both audio and video) using wifi camera . We have completed the development process and every functionality of the application is working as expected in current version. but once we tried to upload the application to Google has rejected the application stating that vulnerability issue with Libpng library version.
Our application uses OpenCV, FFMPEG, JavaCV and JavaCPP libraries for Image processing for Video generation. But when we tried to upload to play store google have rejected application with following message :
“ Hello Google Play Developer,
We rejected Application name, for violating our Malicious Behavior or
User Data policy. If you submitted an update, the previous version of
your app is still available on Google Play.This app uses software that contains security vulnerabilities for
users or allows the collection of user data without proper disclosure.Below is the list of issues and the corresponding APK versions that
were detected in your recent submission. Please upgrade your app(s) as
soon as possible and increment the version number of the upgraded APK.Vulnerability APK Version(s) Libpng library
The vulnerabilities were fixed in libpng v1.0.66, v.1.2.56, v.1.4.19,
v1.5.26 or higher. You can find more information about how resolve the
issue in this Google Help Center article.”Since we have not used libpng library directly in our application we assume the problem is with opencv lib version which may be using libpng , so we replaced the opencv jar file with its gradle dependency and .so files of different libraries are combined in an armeabi.jar file and once we deleted the .so files from libs/armeabi.jar folder and uploaded to play store, then Google didn’t rejected with vulnerability issue and it got uploaded to the play store but the recording isn’t working in that version because we have removed the .SO files from the Project.
So as per our assumptions the libpng vulnerability is not only due to opencv but also due to the other libraries or the .so files .So please kindly suggest us which all .SO files we can remove from the library , so our application functionality for video recording works properly .
We tried to update the OpenCV, FFMPEG libraries and since the SO files are not getting regenerated so could not resolve this issue yet
We already refer following links to find a solution :
For more information please read our stackover flow post regarding this issue :Libpng vulnerability
We need help to solve this issue. Please let us know if you can help us to solve this issue since we are running out of time.
PS : These are the assumptions we made on this issue, May be we are wrong , so please guide us to the right path so we can achieve our goal.
-
Libpng vulnerability
-
ffmpeg background worker runs in debug but not in application
2 novembre 2019, par PurgitoriaMy application has a function of taking captured images and using an FFmpeg background worker to stitch these into a time-lapse video. The GUI has some simple options for video quality and for the source folder and output file. I had an older version of my application written in VB.NET and that worked without issue but I am rewriting in C# as it supports additional capture and filter capability in the image processing but am having real trouble figuring out what is wrong with this function.
I have tried relocating FFmpeg to different locations just in case it was a permissions issue but that had no effect and I also tried to put the function in a "try" with a message box to output any exceptions but I got different errors that prevented me from compiling the code. When I run the application from within VS 2015 in the debugging tool the function works just fine and it will create a video from a collection of still images but when I build and install the application it does not work at all and I cannot see what is causing it to fail. In the options for ffmpeg I used the -report to output a log of what happens in the background worker and in debug, it creates this log but from the application, it does not so I presume it is not even running ffmpeg and going straight to the completed stage of the function.
Function startConversion()
CheckForIllegalCrossThreadCalls = False
Dim quality As Integer = trbQuality.Value
Dim input As String = tbFolderOpen.Text
Dim output As String = tbFolderSave.Text
Dim exepath As String = Application.StartupPath + "\\bin\ffmpeg.exe"
input = input & "\SCAImg_%1d.bmp"
input = Chr(34) & input & Chr(34)
output = Chr(34) & output & Chr(34)
Dim sr As StreamReader
Dim ffmpegOutput As String
' all parameters required to run the process
proc.StartInfo.UseShellExecute = False
proc.StartInfo.CreateNoWindow = True
proc.StartInfo.RedirectStandardError = True
proc.StartInfo.FileName = exepath
proc.StartInfo.Arguments = "-framerate 25 -start_number 0 -pattern_type sequence -framerate 10 -i " & input & " -r 10 -c:v libx264 -preset slow -crf " & quality & " " & output
proc.Start()
lblInfo.Text = "Conversion in progress... Please wait..."
sr = proc.StandardError 'standard error is used by ffmpeg
btnMakeVideo.Enabled = False
Do
ffmpegOutput = sr.ReadLine
tbProgress.Text = ffmpegOutput
Loop Until proc.HasExited And ffmpegOutput = Nothing Or ffmpegOutput = ""
tbProgress.Text = "Finished !"
lblInfo.Text = "Completed!"
MsgBox("Completed!", MsgBoxStyle.Exclamation)
btnMakeVideo.Enabled = True
Return 0
End FunctionI checked the application folder and it does contain a subfolder \bin withe the ffmpeg.exe located within the folder so I then used cmd to run an instance of the installed ffmpeg from the application folder and it seemed to be throwing out permissions errors :
Failed to open report "ffmpeg-20191101-191452.log" : Permission denied
Failed to set value ’1’ for option ’report’ : Permission denied
Error parsing global options : Permission deniedThis seems then like it is certainly a permissions problem but where I am not sure. I did not run into this error when using VB.NET so I am wondering where I am going wrong now. I thought perhaps it would just be a write permission in the application folder so I the removed the -report and ran ffmpeg again using cmd from my application folder and it then gave the error
C :\Users\CEAstro\Pictures\AnytimeCap : Permission denied
Am I missing something really obvious in my code or is there something more fundamental I have wrong in my setup ?
I should also add that I tried running ffmpeg via cmd from a copy that was manually placed elsewhere (i used the same file) and that actually worked. For some reason, it seems like it just will not work from wherever my application installs it.