1/10/2023 0 Comments Ffmpegx iphone![]() Video from the iPhone (presumably via ffmpeg?) to the jsmpeg JavaScriptĪfter some git archeology, I figured out that jsmpeg was rewritten in commit HTML5 Live Video Streaming via WebSockets (2013-Sep)Īs hinted at in the blog posts, the way the app works is by streaming MPEG1.MPEG1 Video Decoder in JavaScript (2013-May).There are three interesting related blog posts by app author Dominic Szablewski: I’m using the PhobosLab Instant Webcam (install I’m not looking into updating the instructions, but if you figure it out, feel The protocol changed between the two apps, so the steps below only work for the This entry was posted in Code on 2020-January-22 by jashale.On, PhobosLab released a new “Magic Webcam” I am betting that we can save 1100GB by re-encoding the videos. We have 1400GB of videos on that Network drive. Recently I was at XYZ Company, I did a check for videos on the network. This allowed us to start working again on our Corporate Network drive. The 300GB’s of iPhone movies that I found on the ABC Company network, I re-encoded saving around 270GB. The bitrate is variable, you could have a segment of a video that is a bitrate of 10,000KB/s but still have an average 2000KB/s. The bitrate during the video isn’t constant though. After using -crf of 28, the bitrate will drop to an average of 2000KB/s or so. Often, you don’t need that high of bitrate and it is overkill. The problem is that the bitrate of an iPhone video is an average of 20,000KB/s or more. For instance, a video that was 100MB will be 10MB after re-encoding it with -crf 28 and you can’t tell that I re-encoded the video. This is aggressive but the loss of quality is minimal. I usually use a -crf of 28 for my x264 videos which is basically what all iPhone, GoPro, and Android videos are. ![]() The above code snippet will maintain the format, codec, framerate, resolution, and then adjust the bitrate based on some factors documented better here: CRF Guide (Constant Rate Factor in x264, x265 and libvpx). ![]() All you have to do reduce the video size by 80-90% is the use the following code snippet ffmpeg -i inputMovie.mov -crf 28 outputVideo.mov This is where FFmpeg and the -crf option comes in handy. Therefore I looked for a solution that could re-encode the videos, maintain the format, codec, resolution, framerate, and compatibility but reduce the file size. People had dumped 300GB of iPhone videos onto our network over several years. The #1 space-consuming filetype was iPhone videos. I scanned the network to see what was stored on our network drive. I couldn’t believe that this had happened at a large company and no one was doing anything about it. IT could not expand the Network drive because of a limitation. We had several hundred engineers that could no longer work because we ran out space. The first time I encountered this problem, I was working for ABC Company (to not name names or blame or whatever) and we ran out space on a network drive. The problem I have run into is corporate network drives have lots of iPhone videos that have been stored for future reference. Side note, if you don’t know what a video format, container, and codecs are and how they relate, pause and read this link: Every Video Format, Codec, and Container Explained. The above code will convert an mp4 to an avi using inferred settings and won’t change the video’s codec. To use FFmpeg, use something like the following. The point here is you can save 80-90% of the space used by iPhone, GoPro, or Android Video by re-encoding the video with FFmpeg and the -crf option. It is a command-line tool that goes from very simple to very complicated. I use FFmpeg on a regular basis for video, audio, and image-related editing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |