how to increase speed for encrypting in mp4box by in increasing buffer ssize

[azhar5678]

Thanks for reporting your issue. Please make sure these boxes are checked before submitting your issue - thank you!

• [ ] I looked for a similar issue and couldn't find any.
• [ ] I tried with the latest version of GPAC. Installers available at http://gpac.io/downloads/gpac-nightly-builds/
• [ ] I give enough information for contributors to reproduce my issue (meaningful title, github labels, platform and compiler, command-line ...). I can share files anonymously with this dropbox: https://www.mediafire.com/filedrop/filedrop_hosted.php?drop=eec9e058a9486fe4e99c33021481d9e1826ca9dbc242a6cfaab0fe95da5e5d95

Detailed guidelines: http://gpac.io/2013/07/16/how-to-file-a-bug-properly/

[azhar5678]

i need to increase speed in mp4box crypt to send to pendrive file size 1gb current time 3 minutes

i need to reduce to 1 minute

[rbouqueau]

I can reproduce these figures. It can be drastically faster by running I/Os on a RAM drive. Also note that the version following our next GPAC release should improve these numbers.

[azhar5678]

We don't have a ram drive, is other option to increase speed. On May 19, 2019 3:35 PM, "Romain Bouqueau" notifications@github.com wrote:

I can reproduce these figures. It can be drastically faster by running I/Os on a RAM drive. Also note that the version following our next GPAC release should improve these numbers.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/gpac/gpac/issues/1248?email_source=notifications&email_token=AFSPX43VDSTUUMSILSXFSCTPWEQ7VA5CNFSM4HNWSJR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVW64KA#issuecomment-493743656, or mute the thread https://github.com/notifications/unsubscribe-auth/AFSPX46GD36NPQL4X2RVD3TPWEQ7VANCNFSM4HNWSJRQ .

[rbouqueau]

Can you wait for a few months to try the next dev version out?

[azhar5678]

OK. On May 19, 2019 3:45 PM, "Romain Bouqueau" notifications@github.com wrote:

Can you wait for a few months to try the next dev version out?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/gpac/gpac/issues/1248?email_source=notifications&email_token=AFSPX44H7TR232XNJF7DJB3PWESFPA5CNFSM4HNWSJR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVW7CDA#issuecomment-493744396, or mute the thread https://github.com/notifications/unsubscribe-auth/AFSPX42LV4YTJV77ENC3BPDPWESFPANCNFSM4HNWSJRQ .

[Murmur]

@azhar5678 Do you use -mem-frags argument so that temp files are not written to disk? Maybe you save few seconds but I guess most progress need a next dev release.

MP4Box -dash 264600 -frag 264600 -dash-scale 44100 -bound -mem-frags -rap -profile dashavc264:live \ 
  -min-buffer 6000 -bs-switching no -sample-groups-traf -single-traf -subsegs-per-sidx -1 \
  -segment-name "$RepresentationID$/$Number$$Init=i$" \
  -out manifest.mpd \
  temp-v1.mp4#trackID=1:id=v1:period=p0 \
  temp-a1.mp4#trackID=1:id=a1:period=p0

edit: hmm... ooh you mean MP4Box -crypt gpacdrm.xml ... command ok disregard my comment.

[jeanlf]

Can you try 0.9.0 Dev and do gpac -i source cecrypt:cfile=crypt.drm @ null:ext=mp4 And measure the time? This will do the whole crypto process without writing any blocks to drive. Also if you want to speed up the process, use fragmentation or flat store modes gpac -i source cecrypt:cfile=crypt.drm @ null:ext=mp4:store=frag gpac -i source cecrypt:cfile=crypt.drm @ null:ext=mp4:store=flat

[jeanlf]

no news, closing