Joined: 4/17/2010
Posts: 11475
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
Nope. Changing the length of the encode didn't help either.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
That just means the section where it's getting the auto timecode is not where you cut it.
Edit:
Mind posting the timecode file somewhere and the x264 line used?
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Okay, I took a look at it. I only found a workaround. Add this to the AVS:
Language: avisynth
AssumeFPS(60, 1)
The fact you changed the framerate slightly for x264.exe doesn't matter because the timecodes file will be used for the real times when you use mkvmerge.exe
Is there an easy way to encode SNES at 4:3 and at least 720p without the pixels being different heights like this?
http://puu.sh/qdPQ2.jpg (This is resized to 960x720)
Joined: 4/17/2010
Posts: 11475
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
You meant different widths?
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Resizing to 1792 x 1344 would do it, right?
Basically replacing one original pixel by 7 pixels horizontally, and 6 pixels vertically, going from 8:7 (256:224) to 4:3 (1792:1344), because (8/7) * (7/6) = (4/3)
Warning: Might glitch to creditsI will finish this ACE soon as possible
(or will I?)
Joined: 4/17/2010
Posts: 11475
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
Which one?
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
If it's for YouTube, it would be better to resize to 3584x2688 since color resolution is 1/4 brightness resolution on YouTube (colorspace YUV4:2:0) in which resizing in multiple of non even numbers is not recommended.
Hi everyone, i recorded 104K frames of SM64DS, and it gave me 3 separated videos. Though, those 3 videos have different frame rates, and virtualdub doesn't let me append them.
What can I do please ?
I improved the AppendSegment function to optionally resize, if you specify width > 0
Language: avisynth
# Multisegment AVI import
function AppendSegment(
\ string base,
\ int first_val,
\ int last_val,
\ string format,
\ int wide,
\ int high
\){
AviSegment = base + string(first_val, format) + ".avi"
result = wide > 0 \
? AviSource(AviSegment).LanczosResize(wide,high) \
: AviSource(AviSegment)
return (first_val < last_val) \
? result + AppendSegment(base,first_val+1,last_val,format,wide,high) \
: result
}
Joined: 4/17/2010
Posts: 11475
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
Thanks for ideas once again, I'll see if I will use them.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
For recent Sega Master System movies, and only in case the TAS syncs on BizHawk 1.11.7 (likely), you need to display the overscan for proper aspect correction. To do so, simply check "Display Overscan" on the SMS menu.
However, since you're going to have an uneven height (243 lines), you need to add a 244th scanline, with this line (provided by creaothceann):
Language: Avisynth
StackVertical(last, Crop(0, Height-1, 0, 0))
This repeats the last line. Another option would be dropping a few lines to get it to an even 240. :)
(Official NTSC standard was 241.5 lines per field afaik, and they didn't expect every TV set to actually show all of them.)
Hey, I'm following the Encoding guide for my Mario Kart 64 movie at http://tasvideos.org/EncodingGuide.html and I noticed that the AVISynth script in the Pre-Encoding section did not work (I had to add a ConvertToRGB24() command to the movie avi as well as the png). Is this guide still up-to-date? It's from 2011 - 2012, which is before YouTube supported 60fps movies (for example).
Also, is there an updated version of the TAS Encoding Package linked here? http://tasvideos.org/EncodingGuide/HybridEncodeScript.html
Joined: 4/17/2010
Posts: 11475
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
Weatherton wrote:
Is this guide still up-to-date?
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
So, when I'm calculating the playing time to show in my Mario Kart 64 encode, should I assume 60.0 fps (as the TASVideos submission form does) or 59.94005994005994 fps (2 * (30000/1001)) consistent with NTSC?
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
