TV prog encoding - credits » Games » FORUM lowesmall.shop
FORUM lowesmall.shop

FORUM lowesmall.shop



ПоискПоиск   Users   Registration   Entrance
Today: 03.04.2025 - 05:44:40
Pages:  1  

TV prog encoding - credits

Advertising


AuthorMessage

Deep2007

main user




Statistics:
Messages: 303
Registration: 11.01.2010

I've done many film encodes with gknot and even edited the .avs file on occassion but I can't quite figure out how to deal with R2 Season 2 X-Files. For ivtc/deinterlace I installed decomb3.91 and add the lines LoadPlugin("C:\PROGRA~1\GORDIA~1\decomb.dll") ..crop line 700x576..pity about top black matt Telecide(guide=2) to the avs file is the best I can come up with after trying various deinterlace methods - this still leaves an occassional problem when camera is panning across an area with strong contasting regular shapes e.g. b&w photos with white borders on a dark table. More importantly I could do with some guidance on how to efficently deal with the opening credits sequence which is gobbling up bytes - I'm currently seeing how going a split within dvd2avi so entire episode is split in two with the break at the end of the opening credits [is that the right name] just after "The truth is out there". At least I can then treat the opening credits as credits within gknot2.31. Current attempt ignores audio which I'll prepare via the command prompt and merge with ? vdub or nandub at the very end. Target is 350MB/episode 512x384 ~125kBps video 96kbps audio, so saving 12MB or so withing the opening credits seems worth the effort. Software gknot2.31 divx4.12 decomb3.91 xp-pro Hardware P2-350 [ouch!] 512MB 50GB

---------------------
Message # 1 25.10.20 - 13:33:29
RE: TV prog encoding - credits

lolo21

main user




Statistics:
Messages: 11
Registration: 19.08.2011

Just make another avs file for the start-credits and use the trim(startframe,endframe) command (in analogy to what Gknot does if you save two avs files, one for the movie, one for the credits). Use bilinear resizing for the credits and encode them at a high quantizer (27-31) to squeeze them as much as possible. For ivtc, I just collected a few settings - some are from Gknot 0.26, some are from dedicated anime encoders of the doom forum :D. Those seem to be quite good for different, complicated sources: #Telecide() #Decimate(cycle=5) # or use #InverseTelecine(32,11,110) # or use #InverseTelecine(60,11,110) # or use #InverseTelecine(44,11,95) # or use #GreedyHMA(1,0,4,0,0,0,0,0) or use manual ivtc (be aware that the pattern might change throughout one episode, so it's quite hard to do...) DoubleWeave() # # plus ONE of the following (depends) # #Pulldown(0,2) #Pulldown(1,3) #Pulldown(2,4) #Pulldown(0,3) #Pulldown(1,4)

---------------------
Message # 2 25.10.20 - 13:39:38
RE: TV prog encoding - credits

6

main user




Statistics:
Messages: 10.04.2012
Registration:

thanks theReal, I'm unsure by what you mean by "Just make another avs file for the start-credits and use the trim(startframe,endframe) command" - do you mean from within gknot0.23b open the vobs in dvd2avi and select the 'open-credits'. I don't see how this on it's own will help make a single avi per episode. Using gknot to make 3 avis per episode [prologue, opening credits, main with end credits treated as credits] leads me into audio problems when I try to merge the pieces and it is tiresome to compute the various filesizes. In the interim I've tested using gknot to make the follow from vobs start.avi with opening credits treated as credits end.avi with closing credits treated as credits and then join the two using vdub and merge all.mp3 generated from the command line using azid and lame [versions in the gknot directory]. Unfortunately while the video is nice & clean the audio is seriously desync'ed, audio and video lengths seem to differ as well - young eyes/ears might be able to fix this in a few minutes but I've to squint and tilt for too long a time ;-

---------------------
Wizoku
Message # 3 25.10.20 - 13:50:57
RE: TV prog encoding - credits

kew

main user




Statistics:
Messages: 16
Registration: 29.10.2009

If select to encode the end credits seperately with Gknot, Gknot saves two .avs files which are encoded seperately. In the one for the movie, you'll find a line like: trim(0,24567) which means this file goes from frame 0 to frame 24567. Then, in the credits avs file, you'll find the line: trim(24567,31456) which means the credits are from frame 24567 to the last frame, 31456 in this case. I suggested you just make a copy of the first file and change the trim values to (0,3000) - of course you have to know how long the start credits are to enter the correct frame. Then, change the main avs to trim(3000,24567). Now, you have three avs files which you can all encode seperately (now you can't encode them with the Gknot encoder-tab because you have two credits avs files and Gknot only has the option for one, but you have to set up the encoding jobs manually in VDub, or use "Jonny's Divx5enc" to do it). When the encoding is done, you join the files in Nandub. To mux with the audio, you shouldn't run into problems when you have an mp3 file called "audio.mp3" and mux it using Nandub. I don't know why you get a .wav extension for the mp3 file created by Gknot - it should be an .mp3 extension, then you just add it as "(VBR) mp3" audio in Nandub. So, I'd say make yourself acquainted with Avisynth and VirtualDub (the tools that Gknot uses for encoding). Open the avs files created by Gknot and see what it does, then you can change everything as you like.

---------------------
Message # 4 25.10.20 - 14:01:57
RE: TV prog encoding - credits
Надійна стійка алмазного буріння: де купити в Києві? : Previous topicNext topic: How to check if mpeg encoded with 5.1 audio
Pages:  1  

The administrator has prohibited guests from replying to messages! To register, follow the link: register


Participants