Feature Request:
Frame by Frame Advancement
Please forgive me if this has already been requested but I did NOT see it in he current list of user requested features.
I, like others here, would really like to see a few of the features that I've grown accustomed to in VLC for desktops and that I find extremely useful; as well as necessary on a routine basis.
Among such features are the ability to step ahead and backwards when utilizing playback in frame by frame viewing mode. This allows for far more precise capture of individual frames when breaking down complex sequences or action segments for granular study and/or production of instructional videos, creation of icons for specific videos and how-to-type step-by-step manuals, etc.
I have hoped for this feature for a very long time and I'm grateful for all of the continued development and new features that are brought to MX Player Pro! This is my daily driver on Android and has been since at least 2010 or 2011.
With the addition of a frame by frame advancement feature, the next logical request is the addition of a frame capture feature that would swiftly save a PNG or JPEG to a user-selectable folder on internal or external memory source using a user-definable file naming convention that could include several readily available elements--time & date, video title, video frame timestamp, incrementing alphanumeric value(s), etc.
These are my immediate requests, though I have a few others, which are less pressing but still remain very much on my list of future "wishes" for MX Player Pro. Thanks in advance for your consideration and for so many years of awesome video playback on Android devices big and small.
Really useful idea. Frame by frame is always useful, even if to check out a scene in every little detail
Related
There are some extremely detailed threads on video playback on the Rafael/Touch Pro/Fuze, and while we all appreciate the hard work and statistics and information in those threads, even those with years of technical knowledge can find themselves hardpressed to get ANY definitive answers underneath the mountain of information.
So, let's hand it out to the community. No long posts, no technical details. I want everyone to answer one question:
What do you encode your video with, at what resolution, at what bit rate, with which codec, watching on which player, and give some reasons?
Answer like this (these are my answers):
Software: Any Video Converter
--------------------free, easy to queue files and set up, and sounded good on Lifehacker
Resolution: 640x480
--------------------best to stick to native device resolution, bitrate makes more of a difference anyway
Video Bit rate: 190 kbps
--------------------File size is decent, 70-90 MB for 42 minute show, looks more than good enough for this screen
Codec: XviD
Media Player: Windows Media Player
Notes: Minimal stuttering, briefly some lag for video to catch up to audio, can watch maybe 3-5 hours of video on full charge
Please keep things to the point. People are interested in video quality, video performance (how smooth it runs), and battery life, not detailed explanations. Just please say, straight up, what you do, with a few notes as to why. Everyone's notes combined can be a wonderful resource, if we all stick to a simple format. Thank you all.
the new Iphone 4 is out, and I think that the HD2 can handle move editing quite well, Is there any movie editing software out there? (like the Omnia's video editor?)
thanks,
Sapir.
I found this from Omnia. Dunno - working or not. Try.
I use the VGA version of TrakAx with the WVGAFIX cab.
Its a bit crude because you lose some of the screen but its a pretty powerful app.
Results are VGA 640x480 only though.
this app doesn't work.... it doesn't show on my start menu...
Video editors come with a wide range of features and capabilities. However, many editors lack the ability to efficiently create templates. This can be a limiting factor when creating videos, as templates can help speed up the video creation process.
Adding templates to a video editor gives you the ability to quickly create videos with pre-defined settings and formats. This can save you time and effort when creating new videos, as well as make it easier to repeat common tasks.
This was a buzz a few versions ago, but not a popular topic anymore it seems. I am looking to create an app that can take pictures and save them as fast as the hardware will allow. AFAIK the preview was made a mandatory part of using the camera back around 2.3.3. We are currently working on rebuilding a version of CM without this requirements, but want to make sure we are not duplicating work. I have found a few little nuggets around that have given us hints, but doesn't seem like anyone has cracked the nut on this one yet. The overall goal being an app that captures high resolution imagery at a slow frame rate (compared to video). I would be happy with 5-10 fps. With the preview requirement, we see anywhere from 1-3 fps, usually in the lower range depending on the device. The target device for us will be the Samsung Galaxy Camera, but it should work across multiple devices as it is just a tweak to the camera API and underlying services.
Perhaps I am part of a very small minority in this regard but has anybody else noticed how poorly implemented scrolling is in the Google Play Music and Play Store applications? Here is a short video highlighting the problem.
What's happening here in both applications is that images are being loaded into RAM as they move into view, unloaded when they move out of view and then reloaded when they move back into view. This might seem insignificant but it impacts the user experience in two very negative ways.
The first is that while you are scrolling through the list of album artwork in Play Music or applications in the Play Store, you will encounter numerous little stutters as new images come into view and are loaded. Given that almost every other facet of Android 5.0 is running at a consistent 60 FPS, this is very jarring and unpleasant.
The second impact which this produces is that (especially in Play Music), you are forced to stop and wait for the album artwork to catch up with you while scrolling. This is highly inconvenient as one of the main purposes which album artwork serves is to allow you to quickly identify an album at a glance. It should not be necessary to crawl through the grid listing in order to easily distinguish one album from another.
Now with all of that said, I do understand why Google chose this particular scrolling implementation. The idea was to improve performance on lower end devices with less RAM and slower SoCs. On a low-end device with very little RAM and a slow SoC, caching a large number of images simultaneously would be quite taxing. This would have been a reasonable compromise to make three years ago but at this point you would be hard pressed to find a low-end device with less than 1GB of RAM and almost every flagship Android device currently ships with 3GB. In this case, Google's attempt to improve performance has actually had the opposite effect.
The HTC Music application on my HTC One M7 last year (which had 2GB of RAM) cached all of the album art immediately upon launching, which resulted in a perfectly smooth experience. There is nothing preventing Google from doing this. If necessary, they could even design these applications to check the amount of RAM available and change their behaviour accordingly.
For comparison, here is another short video demonstrating what a good scrolling implementation looks like.
In this recording, I scroll through about 250 cached images, occupying only about 6MB of RAM.
The points where it appears to get stuck are simply due to the poor touchscreen driver in this build of Lollipop and can be ignored.
Another issue with Play Music which has been bothering me is the size of the album list grid. Only being able to fit four albums onscreen at once is incredibly silly and there is no way to change it. What was Google thinking when they completely removed the standard list view?
Anywhoozles, I congratulate you on your perseverance for making it through this mini-essay. :highfive:
I don't know if the title is appropriate for this request.
I mean MX Player would be better with a button to capture a shot from a video.
Why need an internal capture when Android OS already has a capture feature?
Because capture in Android OS simply interprets what is shown on the screen and saves it and I think the interpretation process is unnecessary because the data is already included in the video file. (I don't know much about video encoding/decoding, so if im wrong sorry for my ignorance on the subject) The resulting image is poor in quality and most importantly takes up TOO much space. If I capture the same scene on the same video by video playing programs (KMP, etc), I get better capture image small in size also(as much as 20 times smaller).
Another problem with Android capture is that ads (I don't know the free version still shows ads when tje video is paused) or soft-keys (although it can be hidden by the app) can be captured together.
And finally, capture is done not considering the size of the video. Android merely captures the screen as shown, the captured image's resolution is the same to the device's screen's resolution, which is a problem when playing videos with higher or lower resolutions or when the video's height-width ratio is different to that of the device's screen(4:3, 16:10, CinemaScope, etc).
So, I think it would be wonderful if you would consider including an internal capture feature in the app.
I think you're working on Frame-by-Frame feature, so I guess it can be related to that.(again, sorry if Im wrong)
Im always happily using MX Player for years and I appereciate your efforts. :laugh:
11si17bun said:
I don't know if the title is appropriate for this request.
I mean MX Player would be better with a button to capture a shot from a video.
Why need an internal capture when Android OS already has a capture feature?
Because capture in Android OS simply interprets what is shown on the screen and saves it and I think the interpretation process is unnecessary because the data is already included in the video file. (I don't know much about video encoding/decoding, so if im wrong sorry for my ignorance on the subject) The resulting image is poor in quality and most importantly takes up TOO much space. If I capture the same scene on the same video by video playing programs (KMP, etc), I get better capture image small in size also(as much as 20 times smaller).
Another problem with Android capture is that ads (I don't know the free version still shows ads when tje video is paused) or soft-keys (although it can be hidden by the app) can be captured together.
And finally, capture is done not considering the size of the video. Android merely captures the screen as shown, the captured image's resolution is the same to the device's screen's resolution, which is a problem when playing videos with higher or lower resolutions or when the video's height-width ratio is different to that of the device's screen(4:3, 16:10, CinemaScope, etc).
So, I think it would be wonderful if you would consider including an internal capture feature in the app.
I think you're working on Frame-by-Frame feature, so I guess it can be related to that.(again, sorry if Im wrong)
Im always happily using MX Player for years and I appereciate your efforts. [emoji23]
Click to expand...
Click to collapse
From your description it looks like you looking for trimming feature. There are many apps are available in Google Play which can trim the video without recoding. It will do the job as you are expecting.
Sent from my SM-G900H using Tapatalk
ktsamy said:
From your description it looks like you looking for trimming feature. There are many apps are available in Google Play which can trim the video without recoding. It will do the job as you are expecting.
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
Yes, I'm aware that there are lots of video trimming/frame break and capturing/editing apps available. But I was just thinking that it would be nicer to have a capturing (I believe it is different from trimming, since capturing is about extracting just one frame out of the video while trimming is extracting multiple continued frames and merging it) feature included in the MX Player so that I can easily watch a video and capture "a" frame without opening another app while watching a video. It is not a big and urgently needed feature, but it would make things more easier.
11si17bun said:
Yes, I'm aware that there are lots of video trimming/frame break and capturing/editing apps available. But I was just thinking that it would be nicer to have a capturing (I believe it is different from trimming, since capturing is about extracting just one frame out of the video while trimming is extracting multiple continued frames and merging it) feature included in the MX Player so that I can easily watch a video and capture "a" frame without opening another app while watching a video. It is not a big and urgently needed feature, but it would make things more easier.
Click to expand...
Click to collapse
[emoji2] [emoji2] [emoji2]
It's my mistake. Apologizes for that. I have misunderstood the word Capture.
Anyway I will convey your request about frame extraction/capture feature to the developer.
Sent from my SM-G900H using Tapatalk