Adv1sor wrote:I know it's not AMV related but, can anyone suggest a program to edit iphone video on a PC?
Mister Hatt wrote:Not necessary, if it reads mp4 it can read mov. Still makes more sense to do it in avisynth though.
mirkosp wrote:Editing with non intra-only h.264 files directly is pretty much as bad as editing with xvid/divx directly. With the difference that non-linear seeking and backward speed will be even more agonizingly slow.
mirkosp wrote:I really don't understand why people shouldn't prefer an intra-only stream whenever possible, makes editing much more relaxing and to the point.
mirkosp wrote:It's not even about quality... if keyframes are too far from each other and you need to reverse speed/do heavy time alterations/massive overlays/whatever, the seek time will hit on you even with a good cpu, because you're limited by the hard drive speed too, and not just by the processing power.
Depending on what file they are using for editing, there may be literally hundreds of frames between keyframes, and that won't be fun to reverse or seek through.
Once upon a time I used to load .avs directly in premiere to edit to save space. With time I realized why people suggested lossless clipping on my own.
Then again with iphone footage it likely has plenty of keyframes (prolly 24 frame GOPs or something like that), so it shouldn't be too bad...
But anyway, when I say intra only I don't even necessarily mean lossless. Even h.264 or whatever else. Just... only keyframes, or possibly 1 or 2 P frames per GOP tops.
mirkosp wrote:Yeah, that's fine. In general I'm concerned about this because... I didn't enjoy what I had to go through back then, so now I really stress on it just so I can spare other people from making my same mistake from back then.
Mister Hatt wrote:Ah... what? Avisynth doesn't have a default colourspace for loaded clips, it defers to the source plugin.
What should be the case is not always how things actually are. It depends on how the software is handling the containers, sometimes plugins don't always support what you think they should. Just because MP4 was developed based on MOV does not mean software that supports MP4 will by default support the use of or handling of a MOV container. Additionally, the way in which a particular software handles containers can control how the footage performs in the editing software. This can cause one type of container to have a significant amount of lag and/or other issues compared to another even with the same exact video information inside of them.Mister Hatt wrote:Also, MOV is a subset of MP4 so it has to work unless the demuxer has incomplete MP4 support to begin with.
Exactly, it depends on a lot of factors, and having used iPhone footage to do simple edit before it is not going to be a nightmare. Again, not trying to start a war here, but it's rather deceptive to not give possible options because those options aren't good for COMPLEX editing, yet are perfectly fine for simple tasks.Mister Hatt wrote:As far as seek times etc, the biggest limiting factors are HDD spin speed and CPU cache size, not the CPU speed in itself. Large files or poorly spaced keyframes hit on HDD limits due to buffers not being large enough and seeks not being fast enough, so lossy but intra-only AVC is a good choice if it compresses better than lossless. Too many reference frames and other complicated bits and bobs have inefficient decoding thanks to limited CPU cache so going intra-only and not relying on references improve speed in that regard, even on something like an i3. Of course that depends on the decoder at hand as well.
Users browsing this forum: No registered users and 1 guest