Reference: http://groups.yahoo.com/group/vjamm/messages (posts 421 & 423)..
I use VJamm to mark regions within a long piece of video and then export each region to a separate AVI file. Often I will shut off the Quantize-to-Frames feature because I am trying to mark regions more precisely than frame quantization will allow - in order to cull one measure of music within a clip, for instance, so that it will loop perfectly in time.
This is the case within the Vegas interface, but it is being claim that the legal spec of the AVI format is such that the resultant exported AVIs will always round to the nearest frame, and therefore be slightly longer than the actual region that was selected?
If so, would SF consider an option to allow export these "illegal" non-integer frame length) AVI's?
I use VJamm to mark regions within a long piece of video and then export each region to a separate AVI file. Often I will shut off the Quantize-to-Frames feature because I am trying to mark regions more precisely than frame quantization will allow - in order to cull one measure of music within a clip, for instance, so that it will loop perfectly in time.
This is the case within the Vegas interface, but it is being claim that the legal spec of the AVI format is such that the resultant exported AVIs will always round to the nearest frame, and therefore be slightly longer than the actual region that was selected?
If so, would SF consider an option to allow export these "illegal" non-integer frame length) AVI's?