Recherche avancée

Sur d’autres sites (11009)

• Revision 3331 : On ajoute un accès à la configuration dans les menus

  25 avril 2010, par kent1 — Log

  On ajoute un accès à la configuration dans les menus

• Scale overlay image FFMPEG

  6 juillet 2015, par VickyS

  I have 3 inputs— a background image, a text file containing list of image file location (to overlay on background image), and an audio file (to be played in background).

  I need to scale the overlay images from "images.txt".
  I am using below command.
  I dont know what am I doing wrong.

  command: ffmpeg -loop 1 -i /sdcard/emoj/angry_bg.png -r 21.0 -f concat -i /sdcard/emoj/images.txt -i /sdcard/emoj/final.wav -filter_complex [1]scale=320:240 [ovrl],[0][ovrl] overlay=(main_w-overlay_w)/2:(main_h-overlay_h)/2 -shortest -s 1080x1920 -b:v 320k -codec:v h264 -c:v mpeg4 -c:a aac -strict experimental -b:a 32k /sdcard/emoj/myPetVideo.mp4

  Please give suggestions.

  Logcat Output :

  07-06 04:13:38.525: I/ffmpeg4android(28481): Command is set
  
  07-06 04:13:38.525: I/ffmpeg4android(28481): set remoteNotificationIconId: 0
  
  07-06 04:13:38.535: D/ffmpeg4android(28481): Client Cannot unbind - service not bound
  
  07-06 04:13:38.535: D/ffmpeg4android(28481): Client stopService()
  
  07-06 04:13:38.545: W/ContextImpl(28481): Implicit intents with startService are not safe: Intent { act=com.netcompss.ffmpeg4android.FFMpegRemoteServiceBridge } android.content.ContextWrapper.stopService:520 com.netcompss.ffmpeg4android_client.BaseWizard.stopService:495 com.netcompss.ffmpeg4android_client.BaseWizard.runTranscoing:279 
  
  07-06 04:13:38.555: I/ffmpeg4android(28481): !!!!!!!!!!!!!!!!!!services.size(): 1
  
  07-06 04:13:38.555: I/ffmpeg4android(28481): putting Base categoty
  
  07-06 04:13:38.615: D/ffmpeg4android(28481): started: com.netcompss.ffmpeg4android.FFMpegRemoteServiceBridge
  
  07-06 04:13:38.615: D/ffmpeg4android(28481): Client startService()
  
  07-06 04:13:38.615: D/ffmpeg4android(28481):  bindService() called
  
  07-06 04:13:38.615: W/ContextImpl(28481): Implicit intents with startService are not safe: Intent { act=com.netcompss.ffmpeg4android.FFMpegRemoteServiceBridge } android.content.ContextWrapper.bindService:538 com.netcompss.ffmpeg4android_client.BaseWizard.bindService:506 com.netcompss.ffmpeg4android_client.BaseWizard.runTranscoing:282 
  
  07-06 04:13:38.625: D/ffmpeg4android(28481): Client bindService()
  
  07-06 04:13:38.725: I/ffmpeg4android(28620): =======service onCreate(): Stopping forground (to overcome 2.3.x bug)
  
  07-06 04:13:38.725: I/ffmpeg4android(28620): =======service onBind()=======
  
  07-06 04:13:38.735: I/ffmpeg4android(28620): ===onStartCommand called
  
  07-06 04:13:38.735: D/ffmpeg4android(28481): Client onServiceConnected()
  
  07-06 04:13:38.735: E/ffmpeg4android(28481): invokeService called
  
  07-06 04:13:38.735: E/rc......(28481): 1 
  
  07-06 04:13:38.735: I/ffmpeg4android(28481): setting remote notification info
  
  07-06 04:13:38.735: D/ffmpeg4android(28620): command items num: 33
  
  07-06 04:13:38.735: D/ffmpeg4android(28620): command: ffmpeg -loop 1 -i /sdcard/emoj/angry_bg.png -r 21.0 -f concat -i /sdcard/emoj/images.txt -i /sdcard/emoj/final.wav -filter_complex [1]scale=320:240 [ovrl],[0][ovrl] overlay=(main_w-overlay_w)/2:(main_h-overlay_h)/2 -shortest -s 1080x1920 -b:v 320k -codec:v h264 -c:v mpeg4 -c:a aac -strict experimental -b:a 32k /sdcard/emoj/myPetVideo.mp4
  
  07-06 04:13:38.745: D/ffmpeg4android(28620): workingFolder from remote: /sdcard/emoj
  
  07-06 04:13:38.745: D/ffmpeg4android(28481): deleteing: /sdcard/emoj/vk.log isdeleted: true
  
  07-06 04:13:38.745: D/ffmpeg4android(28481): deleteing: /sdcard/emoj/ffmpeg4android.log isdeleted: false
  
  07-06 04:13:38.745: D/ffmpeg4android(28481): deleteing: /sdcard/emoj/videokit.log isdeleted: true
  
  07-06 04:13:38.745: D/ffmpeg4android(28481): Client invokeService()
  
  07-06 04:13:38.755: I/ffmpeg4android(28620): ===onStartCommand cat: Base
  
  07-06 04:13:38.755: D/ffmpeg4android(28620): onStartCommand, START_STICKY, base Command
  
  07-06 04:13:38.755: D/ffmpeg4android(28481): Acquire wake lock
  
  07-06 04:13:38.765: D/ffmpeg4android(28481): TranscodeBackground doInBackground started
  
  07-06 04:13:38.765: I/ffmpeg4android(28620): =======remote service runTranscoding ======
  
  07-06 04:13:38.775: I/ffmpeg4android(28620): Start RemoteService with notification id: 5326
  
  07-06 04:13:38.785: I/ffmpeg4android(28620): Run called.
  
  07-06 04:13:38.785: I/ffmpeg4android(28620): ===============Running command from thread path: /sdcard/emoj
  
  07-06 04:13:38.785: I/ffmpeg4android(28620): videokitLibPath: /data/data/org.vinuxproject.sonic/lib/libvideokit.so
  
  07-06 04:13:38.785: I/Videokit(28620): dlopen libvideokit from path: /data/data/org.vinuxproject.sonic/lib/libvideokit.so
  
  07-06 04:13:38.785: I/ffmpeg4android(28620): =======ProgressBackgroundRemote doInBackground=========
  
  07-06 04:13:38.785: W/linker(28620): libvideokit.so has text relocations. This is wasting memory and prevents security hardening. Please fix.
  
  07-06 04:13:38.795: I/Videokit(28620): libvideokit.so loaded
  
  07-06 04:13:38.795: I/Videokit(28620): args is not NULL
  
  07-06 04:13:38.795: I/Videokit(28620): more then one arg
  
  07-06 04:13:38.795: I/Videokit(28620): function symbol found
  
  07-06 04:13:38.795: D/Videokit(28620): Calling videokit run via loader
  
  07-06 04:13:38.795: I/Videokit(28620): vk ffmpeg sdcardPath: /sdcard/emoj 
  
  07-06 04:13:38.795: I/Videokit(28620): licenseCheck in path: /sdcard/emoj 
  
  07-06 04:13:38.795: I/Videokit(28620): isLicExistsComplex...
  
  07-06 04:13:38.795: I/Videokit(28620): trying to open /sdcard/emoj/ffmpeglicense.lic 
  
  07-06 04:13:38.795: I/Videokit(28620): license file found...
  
  07-06 04:13:38.795: I/Videokit(28620): Permanent license validated.
  
  07-06 04:13:38.795: D/Videokit(28620): license check rc: 1
  
  07-06 04:13:38.795: D/Videokit(28620): run() called version 2.0
  
  07-06 04:13:39.165: A/libc(28620): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x8 in tid 28620 (ct.sonic:remote)
  
  07-06 04:13:39.655: D/ffmpeg4android(28481): onServiceDisconnected
  
  07-06 04:13:40.805: I/ffmpeg4android(28656): =======service onCreate(): Stopping forground (to overcome 2.3.x bug)
  
  07-06 04:13:40.805: I/ffmpeg4android(28656): =======service onBind()=======
  
  07-06 04:13:40.815: I/ffmpeg4android(28656): ===onStartCommand called
  
  07-06 04:13:40.815: D/ffmpeg4android(28656): Not running since the OS auto started the service after crash
  
  07-06 04:13:40.815: D/ffmpeg4android(28481): Client onServiceConnected()
  
  07-06 04:13:40.815: E/ffmpeg4android(28481): invokeService called
  
  07-06 04:13:40.815: E/rc......(28481): 1 
  
  07-06 04:13:40.815: I/ffmpeg4android(28481): setting remote notification info
  
  07-06 04:13:40.815: D/ffmpeg4android(28481): Not invoking
  
  07-06 04:13:40.825: I/ffmpeg4android(28656): Cancel notification: 5326
  
  07-06 04:13:41.135: I/ffmpeg4android(28481): Got real duration: 00:00:00.04
  
  07-06 04:13:41.145: W/ffmpeg4android(28481): /sdcard/emoj/ffmpeg4android.log: open failed: ENOENT (No such file or directory)
  
  07-06 04:13:41.145: I/ffmpeg4android(28481): ==== getting currentVkLogSize from FFmpeg4Android log
  
  07-06 04:13:41.145: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:41.155: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:41.155: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:41.155: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:41.155: I/line(28481): exit_program: 1 
  
  07-06 04:13:41.155: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:41.155: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:41.155: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:41.455: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:41.455: D/ffmpeg4android(28481): currentVkLogSize: 5316
  
  07-06 04:13:41.465: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:41.465: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:41.465: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:41.465: I/line(28481): exit_program: 1 
  
  07-06 04:13:41.465: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:41.465: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:41.465: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:41.765: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:41.765: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:41.765: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:41.765: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:41.765: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:41.765: I/line(28481): exit_program: 1 
  
  07-06 04:13:41.765: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:41.775: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:41.775: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:42.075: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:42.075: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:42.075: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:42.075: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:42.075: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:42.075: I/line(28481): exit_program: 1 
  
  07-06 04:13:42.075: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:42.075: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:42.075: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:42.375: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:42.375: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:42.375: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:42.385: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:42.385: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:42.385: I/line(28481): exit_program: 1 
  
  07-06 04:13:42.385: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:42.385: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:42.385: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:42.685: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:42.685: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:42.685: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:42.685: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:42.685: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:42.695: I/line(28481): exit_program: 1 
  
  07-06 04:13:42.695: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:42.695: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:42.695: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:42.995: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:42.995: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:42.995: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:42.995: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:42.995: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:42.995: I/line(28481): exit_program: 1 
  
  07-06 04:13:42.995: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:42.995: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:42.995: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:43.295: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:43.295: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:43.305: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:43.305: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:43.305: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:43.305: I/line(28481): exit_program: 1 
  
  07-06 04:13:43.305: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:43.305: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:43.305: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:43.605: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:43.605: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:43.615: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:43.615: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:43.615: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:43.615: I/line(28481): exit_program: 1 
  
  07-06 04:13:43.615: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:43.615: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:43.615: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:43.915: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:43.915: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:43.915: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:43.915: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:43.915: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:43.915: I/line(28481): exit_program: 1 
  
  07-06 04:13:43.915: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:43.925: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:43.925: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:44.225: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:44.225: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:44.225: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:44.225: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:44.225: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:44.225: I/line(28481): exit_program: 1 
  
  07-06 04:13:44.225: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:44.225: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:44.225: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:44.525: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:44.525: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:44.525: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:44.535: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:44.535: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:44.535: I/line(28481): exit_program: 1 
  
  07-06 04:13:44.535: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:44.535: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:44.535: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:44.835: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:44.835: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:44.835: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:44.835: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:44.835: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:44.835: I/line(28481): exit_program: 1 
  
  07-06 04:13:44.835: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:44.845: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:44.845: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:45.155: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:45.155: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:45.155: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:45.155: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:45.155: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:45.155: I/line(28481): exit_program: 1 
  
  07-06 04:13:45.155: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:45.155: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:45.155: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:45.455: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:45.455: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:45.455: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:45.455: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:45.455: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:45.455: I/line(28481): exit_program: 1 
  
  07-06 04:13:45.455: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:45.455: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:45.455: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:45.755: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:45.755: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:45.765: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:45.765: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:45.765: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:45.765: I/line(28481): exit_program: 1 
  
  07-06 04:13:45.765: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:45.765: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:45.765: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:46.065: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:46.065: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:46.065: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:46.075: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:46.075: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:46.075: I/line(28481): exit_program: 1 
  
  07-06 04:13:46.075: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:46.075: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:46.075: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:46.375: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:46.375: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:46.375: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:46.375: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:46.375: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:46.375: I/line(28481): exit_program: 1 
  
  07-06 04:13:46.385: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:46.385: I/ffmpeg4android(28481): progress is 0, not setting
  
  07-06 04:13:46.385: I/ffmpeg4android(28481): progress is 0, not publishing
  
  07-06 04:13:46.685: I/ffmpeg4android(28481): ==== getting currentVkLogSize from VK
  
  07-06 04:13:46.685: W/ffmpeg4android(28481): Looks like Vk log is not increasing in size
  
  07-06 04:13:46.685: I/ffmpeg4android(28481): No ffmpeg4android_log file, using vk log
  
  07-06 04:13:46.685: I/line(28481): a suitable output format for '[ovrl],[0][ovrl]'
  
  07-06 04:13:46.685: I/line(28481): [ovrl],[0][ovrl]: Invalid argument
  
  07-06 04:13:46.685: I/line(28481): exit_program: 1 
  
  07-06 04:13:46.685: D/ffmpeg4android(28481): currentTimeStr: 00:00:00.00
  
  07-06 04:13:46.685: E/ffmpeg4android(28481): VK log is not changing in size, and no exit token found
  
  07-06 04:13:46.695: I/ffmpeg4android(28481): onProgressUpdate: 100
  
  07-06 04:13:46.695: D/ffmpeg4android(28481): Releasing wake lock
  
  07-06 04:13:46.695: D/ffmpeg4android(28481): TranscodeBackground onPostExecute
  
  07-06 04:13:46.705: W/ffmpeg4android(28481): progressDialog failed to dismiss: null
  
  07-06 04:13:46.705: W/ffmpeg4android(28481): android.os.DeadObjectException
  
  07-06 04:13:46.705: W/ffmpeg4android(28481):    at android.os.BinderProxy.transactNative(Native Method)
  
  07-06 04:13:46.705: W/ffmpeg4android(28481):    at android.os.BinderProxy.transact(Binder.java:496)
  
  07-06 04:13:46.705: W/ffmpeg4android(28481):    at com.netcompss.ffmpeg4android.IFfmpgefRemoteServiceBridge$Stub$Proxy.setTranscodingProgress(IFfmpgefRemoteServiceBridge.java:181)
  
  07-06 04:13:46.705: W/ffmpeg4android(28481):    at com.netcompss.ffmpeg4android_client.TranscodeBackground.onPostExecute(TranscodeBackground.java:163)
  
  07-06 04:13:46.705: W/ffmpeg4android(28481):    at com.netcompss.ffmpeg4android_client.TranscodeBackground.onPostExecute(TranscodeBackground.java:1)
  
  07-06 04:13:46.705: W/ffmpeg4android(28481):    at android.os.AsyncTask.finish(AsyncTask.java:632)
  
  07-06 04:13:46.705: W/ffmpeg4android(28481):    at android.os.AsyncTask.access$600(AsyncTask.java:177)
  
  07-06 04:13:46.705: W/ffmpeg4android(28481):    at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:645)
  
  07-06 04:13:46.705: W/ffmpeg4android(28481):    at android.os.Handler.dispatchMessage(Handler.java:102)
  
  07-06 04:13:46.705: W/ffmpeg4android(28481):    at android.os.Looper.loop(Looper.java:135)
  
  07-06 04:13:46.705: W/ffmpeg4android(28481):    at android.app.ActivityThread.main(ActivityThread.java:5232)
  
  07-06 04:13:46.705: W/ffmpeg4android(28481):    at java.lang.reflect.Method.invoke(Native Method)
  
  07-06 04:13:46.705: W/ffmpeg4android(28481):    at java.lang.reflect.Method.invoke(Method.java:372)
  
  07-06 04:13:46.705: W/ffmpeg4android(28481):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
  
  07-06 04:13:46.705: W/ffmpeg4android(28481):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
  
  07-06 04:13:46.715: D/ffmpeg4android(28481): /sdcard/emoj/null length in bytes: 0
  
  07-06 04:13:46.715: D/ffmpeg4android(28481): showNotifications
  
  07-06 04:13:46.715: I/ffmpeg4android(28481): ============ Transcoding Failed, caling fexist
  
  07-06 04:13:46.715: E/ffmpeg4android(28481): fexit remote excetion
  
  07-06 04:13:46.765: I/ffmpeg4android(28481): FFMPEG finished.
  
  07-06 04:13:46.985: D/ffmpeg4android(28481): releaseService()
  
  07-06 04:13:46.985: D/ffmpeg4android(28481): Client stopService()
  
  07-06 04:13:46.985: I/ffmpeg4android(28656): =======service onDestroy()======
  
  07-06 04:13:46.985: W/ContextImpl(28481): Implicit intents with startService are not safe: Intent { act=com.netcompss.ffmpeg4android.FFMpegRemoteServiceBridge } android.content.ContextWrapper.stopService:520 com.netcompss.ffmpeg4android_client.BaseWizard.stopService:495 org.vinuxproject.sonic.WaveformActivity.handleServiceFinished:456 

• Understanding Data Processing Agreements and How They Affect GDPR Compliance

  9 octobre 2023, par Erin — GDPR

  The General Data Protection Regulation (GDPR) impacts international organisations that conduct business or handle personal data in the European Union (EU), and they must know how to stay compliant.

  One way of ensuring GDPR compliance is through implementing a data processing agreement (DPA). Most businesses overlook DPAs when considering ways of maintaining user data security. So, what exactly is a DPA’s role in ensuring GDPR compliance ?

  In this article, we’ll discuss DPAs, their advantages, which data protection laws require them and the clauses that make up a DPA. We’ll also discuss the consequences of non-compliance and how you can maintain GDPR compliance using Matomo.

  What is a data processing agreement ?

  A data processing agreement, data protection agreement or data processing addendum is a contractual agreement between a data controller (a company) and a data processor (a third-party service provider.) It defines each party’s rights and obligations regarding data protection.

  A DPA also defines the responsibilities of the controller and the processor and sets out the terms they’ll use for data processing. For instance, when MHP/Team SI sought the services of Matomo (a data processor) to get reliable and compliant web analytics, a DPA helped to outline their responsibilities and liabilities.

  A DPA is one of the basic requirements for GDPR compliance. The GDPR is an EU regulation concerning personal data protection and security. The GDPR is binding on any company that actively collects data from EU residents or citizens, regardless of their location.

  As a business, you need to know what goes into a DPA to identify possible liabilities that may arise if you don’t comply with European data protection laws. For example, having a recurrent security incident can lead to data breaches as you process customer personal data.

  The average data breach cost for 2023 is $4.45 million. This amount includes regulatory fines, containment costs and business losses. As such, a DPA can help you assess the organisational security measures of your data processing methods and define the protocol for reporting a data breach.

  Why is a DPA essential for your business ?

  If your company processes personal data from your customers, such as contact details, you need a DPA to ensure compliance with data security laws like GDPR. You’ll also need a DPA to hire a third party to process your data, e.g., through web analytics or cloud storage.

  But what are the benefits of having a DPA in place ?

  

  A key benefit of signing a DPA is it outlines business terms with a third-party data processor and guarantees compliance with the relevant data privacy laws. A DPA also helps to create an accountability framework between you and your data processor by establishing contractual obligations.

  Additionally, a DPA helps to minimise the risk of unauthorised access to sensitive data. A DPA defines organisational measures that help protect the rights of individuals and safeguard personal data against unauthorised disclosure. Overall, before choosing a data processor, having a DPA ensures that they are capable, compliant and qualified.

  More than 120 countries have already adopted some form of international data protection laws to protect their citizens and their data better. Hence, knowing which laws require a DPA and how you can better ensure compliance is important.

  Which data protection laws require a DPA ?

  Regulatory bodies enact data protection laws to grant consumers greater control over their data and how businesses use it. These laws ensure transparency in data processing and compliance for businesses.

  

  The following are some of the relevant data privacy laws that require you to have a DPA :

  • UK GDPR
  • Brazil LGPD
  • EU GDPR
  • Dubai PDPA
  • Colorado CPA
  • California CCPA/CPRA
  • Virginia VCDPA
  • Connecticut DPA
  • South African POPIA
  • Thailand PDPA

  Companies that don’t adhere to these data protection obligations usually face liabilities such as fines and penalties. With a DPA, you can set clear expectations regarding data processing between you and your customers.

  Review and update any DPAs with third-party processors to ensure compliance with GDPR and the laws we mentioned above. Additionally, confirm that all the relevant clauses are present for compliance with relevant data privacy laws. 

  So, what key data processing clauses should you have in your DPA ? Let’s take a closer look in the next section.

  Key clauses in a data processing agreement

  GDPR provides some general recommendations for what you should state in a DPA.

  

  Here are the elements you should include :

  Data processing specifications

  Your DPA should address the specific business purposes for data processing, the duration of processing and the categories of data under processing. It should also clearly state the party responsible for maintaining GDPR compliance and who the data subjects are, including their location and nationality.

  Your DPA should also address the data processor and controller’s responsibilities concerning data deletion and contract termination.

  Role of processor

  Your DPA should clearly state what your data processor is responsible for and liable for. Some key responsibilities include record keeping, reporting breaches and maintaining data security.

  Other roles of your data processor include providing you with audit opportunities and cooperating with data protection authorities during inquiries. If you decide to end your contract, the data processor is responsible for deleting or returning data, depending on your agreement.

  Role of controller

  Your DPA should inform the responsibilities of the data controller, which typically include issuing processing instructions to the data processor and directing them on how to handle data processing.

  Your DPA should let you define the lawful data processes the data processor should follow and how you’ll uphold the data protection rights of individuals’ sensitive data.

  Organisational and technical specifications

  Your DPA should define specifications such as how third-party processors encrypt, access and test personal data. It should also include specifications on how the data processor and controller will maintain ongoing data security through various factors such as :

  • State of the technology : Do ‌third-party processors have reliable technology, and can they ensure data security within their systems ?
  • Costs of implementation : Does the data controller’s budget allow them to seek third-party services from industry-leading providers who can guarantee a certain level of security ?
  • Variances in users’ personal freedom : Are there privacy policies and opt-out forms for users to express how they want companies to use their sensitive data ?

  Moreover, your DPA should define how you and your data processor will ensure the confidentiality, availability and integrity of data processing services and systems.

  What are the penalties for DPA GDPR non-compliance ?

  Regulators use GDPR’s stiff fines to encourage data controllers and third-party processors to follow‌ best data security practices. One way of maintaining compliance is through drafting up a DPA with your data processor.

  The DPA should clearly outline the necessary legal requirements and include all the relevant clauses mentioned above. Understand what goes into this agreement since data protection authorities can hold your business accountable for a breach — even if a processor’s error caused it.

  Data protection authorities can issue penalties now that the GDPR is in place. For example, according to Article 83 of the GDPR, penalties for data or privacy breaches or non-compliance can amount to up to €20 million or 4% of your annual revenue.

  There are two tiers of fines : tier one and tier two. Violations related to data processors typically attract fines on the tier-one level. Tier one fines can cost your business €10 million or 2% of your company’s global revenue.

  Tier-two fines result from infringement of the right to forget and the right to privacy of your consumer. Tier-two fines can cost your business up to €20 million or 4% of your company’s global revenue.

  GDPR fines make non-compliance an expensive mistake for businesses of all sizes. As such, signing a DPA with any party that acts as a data processor for your business can help you remain GDPR-compliant.

  How a DPA can help your business remain GDPR compliant

  A DPA can help your business define and adhere to lawful data processes.

  

  So, in what other ways can a DPA help you to remain compliant with GDPR ? Let’s take a look !

  1. Assess data processor’s compliance

  Having a DPA helps ensure that the data processor you are working with is GDPR-compliant. You should check if they have a DPA and confirm the processor’s terms of service and legal basis.

  For example, if you want an alternative to Google Analytics that’s GDPR compliant, then you can opt for Matomo. Matomo features a DPA, which you can agree to when you sign up for web analytics services or later.

  2. Establish lawful data processes

  A DPA can also help you review your data processes to ensure they’re GDPR compliant. For example, by defining lawful data processes, you better understand personally identifiable information (PII) and how it relates to data privacy.

  Further, you can allow users to opt out of sharing their data. As such, Matomo can help you to enable Do Not Track preferences on your website.

  

  With this feature, users are given the option to opt in or out of tracking via a toggle in their respective browsers.

  Indeed, establishing lawful data processes helps you define the specific business purposes for collecting and processing personal data. By doing so, you get to notify your users why you need their data and get their consent to process it by including a GDPR-compliant privacy policy on your website.

  3. Anonymise your data

  Global privacy laws like GDPR and ePrivacy mandate companies to display cookie banners or seek consent before tracking visitors’ data. You can either include a cookie consent banner on your site or stop tracking cookies to follow the applicable regulations.

  Further, you can enable cookie-less tracking or easily let users opt out. For example, you can use Matomo without a cookie consent banner, exempting it from many countries’ privacy rules.

  Additionally, through a DPA, you can define organisational measures that define how you’ll anonymise all your users’ data. Matomo can help you anonymise IP addresses, and we recommend that you at least anonymise the last two bytes.

  

  As one of the few web analytics tools you can use to collect data without tracking consent, Matomo also has the French Data Protection Authority (CNIL) approval.

  4. Assess the processor’s bandwidth

  Having a DPA can help you implement data retention policies that show clear retention periods. Such policies are useful when ending a contract with a third-party service provider and determining how they should handle your data.

  A DPA also helps you ensure the processor has the necessary technology to store personal data securely. You can conduct an audit to understand possible vulnerabilities and your data processor’s technological capacity.

  5. Obtain legal counsel

  When drafting a DPA, it’s important to get a consultation on what is needed to ensure complete compliance. Obtaining legal counsel points you in the right direction so you don’t make any mistakes that may lead to non-compliance.

  Conclusion

  Businesses that process users’ data are subject to several DPA contract requirements under GDPR. One of the most important is having DPAs with every third-party provider that helps them perform data processing.

  It’s important to stay updated on GDPR requirements for compliance. As such, Matomo can help you maintain lawful data processes. Matomo gives you complete control over your data and complies with GDPR requirements.

  To get started with Matomo, you can sign up for a 21-day free trial. No credit card required.

  Disclaimer

  We are not lawyers and don’t claim to be. The information provided here is to help give an introduction to GDPR. We encourage every business and website to take data privacy seriously and discuss these issues with your lawyer if you have any concerns.