|
|
| pestilence |
| Posted: Dec 17 2003, 09:49 AM |
 |
|
Unregistered
|
the error message is this:
Cannot append segment "c:\path\example.avi": The video streams have different sampling rates (23.97600 vs. 23.97600)
I find that very odd 
edit
I solved my problem by saving both chunks as .ogm files, appending them, and saving as an avi, but the bug is still there for you to fix
/edit
I thought it might be because the first part is an open DML avi and the second is not, but further dividing the first half into < 2gb chunks didn't fix it.
I'm trying to append two xvid avi files i made using the exact same setup on two different encoding runs. they are two chunks of the same movie. the first part is most of the movie and the last part is a short 14000 frame section i re-did because my gigantic avisynth script was returning blocky video from a dvd source (i assume because i'm appending about 520 segments together). i trimmed up the avisynth script to just give me the last section and the video problems went away. so then i'm left with a 3.3gb chunk and a 450mb chunk i want to join together and it absolutely refuses to join them.
I've tried appending it in vdub, nandub, and two versions of vdubmod with no success.
the frame rates are the same, there's no sound, and the dimensions are identical (1120x480).
that's all i know... please help 
p.s. if you are wondering why the huge file from a movie, i've overlaid the fullscreen version on top of the wide screen version (including lining up all the different shots of the movie differently as the pan & scan region changes) in order to get GREATLY increased resolution at the center of the action in the movie. it's all a big experiment and it's working out very well - avisynth/virtualdub is a VERY powerful combination!
p.p.s. i also noticed that virtualdubmod tends to leak memory like crazy when editing the aformentioned ginormous avisynth script and then using f5 to refresh (something like 30mb per refresh!!!) |
|
| fccHandler |
| Posted: Dec 17 2003, 04:22 PM |
|
|
Administrator n00b
Group: Moderators
Posts: 3961
Member No.: 280
Joined: 13-September 02
|
AVI framerate is expressed as the division of dwRate / dwScale, but presumably VirtualDub rounds the result to some limited precision for its display (making it look like the files have the same framerate).
The dwScale and dwRate parameters are typically at offset 0x80 of the AVI file. I'll bet if you look at the two files in VirtualDub's hex editor, you'll see that the parameters are different, and this is probably why VirtualDub refuses to append them.
P.S. You could have joined them with AVISynth's "UnalignedSplice" command, but it would require recompressing them.
--------------------
May the FOURCC be with you... |
|
| pestilence |
| Posted: Dec 17 2003, 04:27 PM |
|
|
Unregistered
|
yeah - recompressing was not an option i was trying to make the best possible (compressed) copy of the movie i could achieve. fortunately it all worked out. why would the two parts have wound up with slightly different frame rates? (aside from the math/rounding, of course) |
|
| fccHandler |
| Posted: Dec 18 2003, 06:15 AM |
|
|
Administrator n00b
Group: Moderators
Posts: 3961
Member No.: 280
Joined: 13-September 02
|
| QUOTE (pestilence @ Dec 17 2003, 12:27 PM) | | why would the two parts have wound up with slightly different frame rates? |
I don't know, but editing the AVI in different programs, or explicitly setting the frame rate in VirtualDub could cause it. Any program which writes AVIs must decide how to represent the movie's frame rate as dwRate / dwScale.
For instance, let's say my video is 25 fps. Should my program write it into the AVI as 25 / 1, or 1000000 / 40000?
I only recently found out that Avisynth allows you to specify these parameters, using the syntax "AssumeFPS(dwRate, dwScale)," and VirtualDub will honor them when creating the AVI. Too bad VirtualDub doesn't offer this feature itself.
--------------------
May the FOURCC be with you... |
|
| phaeron |
| Posted: Dec 18 2003, 07:35 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
Check that you have a recent version of VirtualDub. All recent versions use special fraction code to handle frame rates and will not be fooled by an unreduced fraction in one of the segments. Also, video frame rates are always reduced to lowest terms before being written to disk. (Avisynth does something similar.)
The engine now accepts arbitrary fractions for frame rates, but the UI doesn't expose this yet. Some script commands might; I forget.
|
|
| pestilence |
| Posted: Dec 18 2003, 03:17 PM |
|
|
Unregistered
|
I did upgrade to the latest version of virtualdubmod before asking on here, but I don't have the latest version of virtualdub (if they are different). I think i know how it happened now - my original avisynth script was over 175k and had about 520 clips strung together from 2 dvd sources. the sheer size caused compression artifacts to magically appear during the last few shots of the movie. to fix that, i cut out all of the edits from the script that weren't involved with the problem and added a long blankclip() to the script to keep my frame offsets the same. the timing on the blankclip() must have used a different fraction and virtualdub must have just copied it across when encoding the piece even though i didn't actually use any of the black frames. |
|
