Compressor | Java写的压缩解压小工具，可压缩解压zip rar tar gz | Script Programming library

I did resolve, to some degree, my original post's questions and frustrations by using the ffmpeg_kit_flutter_full_gpl package on the client side, and then ffmpeg again in GCF on the server side. In summary:

• Within 60 seconds, I can now compress a 2 minute video by 90% before uploading to firebase storage.
• Using onFinalize via GCF on the server side I run ffmpeg again on the uploaded video and gain another 77% reduction in file size on the server side without any loss in video quality.
• My solution does not yet upload while the app is closed.
• On the client side, this solution requires setting the camera ResolutionPreset to high (720p), rather than max, which can be a minimum of 1080p, and setting the ffmpeg -preset veryfast rather than the medium default.

Camera & ffmpeg solution settings:

• Flutter camera package ResolutionPreset to high
• ffmpeg -preset veryfast

Transcoding results stats for 2 minute video:

• Before transcode: 255MB
• After client side transcode: 25MB (90% decrease in size before upload)
• Time to transcode: 60 seconds
• onFinalized GCF ffmpeg transcode: 19MB (77% reduction in size)
• In total a 93% reduction in size while keep high quality 720p video.

flutter_ffmpeg is archived, the new ffmpeg flutter package is ffmpeg_kit_flutter.

That being said, I used ffmpeg_kit_flutter to build my solution on the client side, rather than the server side, and transcode the video before uploading.

Cons:

1. Doubled my app size to use ffmpeg, because I needed access to both lame and x264 so I had to install the full-gpl package to gain access to these libraries.
2. A two minute video can take up to 60 seconds to transcode.

The pros:

1. Low bandwidth connections will operate much better after a video is reduced in size by 90%.
2. Large videos will transcode and ffmpegkit does not crash like other flutter packages I've tried.
3. The second pass with ffmpeg on GCF gains another 77% reduction in size taking a video of 100's of MB's down to just 10-20 MB max for eventually delivery.
4. Costs lower on the front and back end.

So, you'll have to decide if the pros outweighs the cons and if 720p is high enough quality for playback. For me 720p looks perfect for video playback on a mobile phone and 1080p or higher was big time overkill.

I've provided sample code (not full classes) to give anyone looking to implement my solution a try. It became very important, due to the amount of time to transcode, to display a progress meter so the user does not give up on the process. You'll see my simple solution to displaying transcoding progress.

pubspec.yaml

• camera package for video recording
• riverpod required for statenotifier and transcode/upload progress notifications
• ffmpeg_kit_flutter_full_gpl (the full_gpl gets the ffmpeg package with most libraries) required to get h264 and libmp3lame encoders to produce most widely playable transcoded videos.
• wakelock required because transcoding takes so long you don't want the phone to sleep while transcoding.

From rails tailwind readme

Tailwind uses modern CSS features that are not recognized by the sassc-rails extension that was included by default in the Gemfile for Rails 6. In order to avoid any errors like SassC::SyntaxError, you must remove that gem from your Gemfile.

https://github.com/rails/tailwindcss-rails

Replace src by files in line:

try

I figured it out. I had to add an Array and make the file excisable for all functions.

The 31 parameter in the Python code is requesting a gzip stream, not a zlib stream. In Kotlin, you are generating a zlib stream. (zlib is described in RFC 1950, gzip in RFC 1952.)

It does not appear that Java's Deflater (spelled wrong) class has that option. It does have a nowrap option that gives raw deflate compressed data, around which you can construct your own gzip wrapper, using the RFC to see how.

By the way, the results are not "totally different". You have gzip and zlib wrappers around exactly the same raw deflate compressed data: 4b4c...0020.

In my case, firebase UI (com.firebaseui:firebase-ui-auth:8.0.0) was using com.google.android.gms:play-services-auth:19.0.0 which I found with the command './gradlew -q app:dependencyInsight --dependency play-services-auth --configuration debugCompileClasspath'

This version of the play services auth was causing the issue for me.

I added a separate

implementation 'com.google.android.gms:play-services-auth:20.0.1'

to my gradle and this issue disappeared.

getting Webpack up and running from scratch is not an easy task. I suggest you start with a ready to use an approach like cra or expo. then work your way up to customization.

1. firstly, install the dependencies:

I have fixed the problem by deleting /tmp/mongodb-27017.sock.I have found the answer here