Mister Hatt wrote:Ah... what? Avisynth doesn't have a default colourspace for loaded clips, it defers to the source plugin.
You are correct, it does not have a default colorspace
for the loaded clips and does use the colorspace based on the information referred to it by the input plugin (which reads the colorspace information from the video file itself). That said, it does
have a default way of reading the color information of YV12 footage when converting to RGB, which is by using the Rec.601 color matrix
. This information is in the AviSynth documentation
...I'm surprised someone as well versed in this as you are happened to overlook this, but to be fair it's not easy to notice most of the time as it does not throw the overall hue way off or anything. Here is an example using HD footage (resized in Photoshop after taking the screenshots):
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.
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: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.
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.