Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
28th June 2013, 07:49 | #61 | Link | |
Registered User
Join Date: May 2009
Location: Belgium
Posts: 1,743
|
Quote:
Do you believe that TV channels encode in PAFF ? I believed it was rare. |
|
28th June 2013, 07:55 | #62 | Link | |
Registered User
Join Date: May 2009
Location: Belgium
Posts: 1,743
|
Quote:
When I used to record in analog, video was always in tff, for years, and on all channels. I guess they also chose tff in digital. |
|
28th June 2013, 08:58 | #63 | Link | |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
Quote:
If there is enough time to encode the material "offline", broadcasters may use more elaborate encoders; results created by x264 have been spotted in TV broadcasts already. __ Field inversions ... do you mean wrong flagging (motion analysis reveals TFF order but bitstream flags report BFF), or do you mean a correct TFF/BFF conversion by omitting one field? Last edited by LigH; 28th June 2013 at 09:01. |
|
28th June 2013, 10:00 | #64 | Link | ||
Registered User
Join Date: May 2009
Location: Belgium
Posts: 1,743
|
Quote:
So I meant that TV often do that kind of conversion and we can't know if it was filmed in tff or bff. And as my analog recordings were in tff and as MediaInfo also detects tff for my digital recordings, I was astonished to note that these digital recordings were in bff for Libavcodec. But VFR maniac has given a good explanation about this phenomenon. Quote:
Do you mean some typical x264 defects seen on TV, which means they also use x264 (which is free) ? Last edited by Music Fan; 28th June 2013 at 11:13. |
||
16th July 2013, 07:40 | #67 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
There is a report that Apple ProRes videos (e.g. clipcanvas_14348_PRORES_HQ.mov) are incorrectly decoded and deskewed by LWLibavVideoSource (LSMASHSource r632), in contrast to FFVideoSource (FFMS2 v2.18 RC1).
|
16th July 2013, 14:15 | #68 | Link |
Spinner of yarns
Join Date: May 2009
Posts: 164
|
Apple ProRes?
Haha, I guess the strange output from LWLibavVideoSource is high bit-depth interleaved format. You may feel FFMS2 outputs correctly but, the fact, the output loses accuracy around 2-bit for each Y'CbCr component. Try format="YUV422P8" or stacked=true. Edit and Note: currently libavcodec ProRes decoder supports only Y'CbCr 4:2:2 10-bit and 4:4:4 10-bit format with or without alpha channel. Therefore, LWLibavVideoSource(source="ProRes") always output in interleaved format unless user specifies output format. And even if ProRes4444 (12-bit) is input, the default output format will be Y'CbCr 4:4:4 10-bit with alpha.
__________________
僕と契約して、L-SMASH developerになってよ! L-SMASH | L-SMASH Works | Opus-in-ISOBMFF specification and reference software Last edited by VFR maniac; 16th July 2013 at 17:07. |
24th July 2013, 20:23 | #69 | Link |
Registered User
Join Date: Oct 2001
Location: Germany
Posts: 7,259
|
btw. is there some way to roughly predict the size of the LWLibavVideoSource index.
Since I can't specify where the index should be created, I normally use to let LWLibavVideoSource create the index inside the RAM, problem is on large files the index gets to large for Avisynth to handle, so I would like to predict the size before indexing a file so I can decide whether to use LWLibavVideoSource or not. |
25th July 2013, 11:10 | #70 | Link |
Spinner of yarns
Join Date: May 2009
Posts: 164
|
There is no way to predict the size of the index file.
The index file consists of properties per packet returned by libavformat in the overall stream. (+plus CODEC specific decoder configurations and libavformat own index entries) The size doesn't depend on the source file size.
__________________
僕と契約して、L-SMASH developerになってよ! L-SMASH | L-SMASH Works | Opus-in-ISOBMFF specification and reference software Last edited by VFR maniac; 25th July 2013 at 11:13. |
4th August 2013, 11:15 | #71 | Link |
Spinner of yarns
Join Date: May 2009
Posts: 164
|
This message means the subsequent filter requests frame number exceeding the number of output frames from vslsmashsource.
For instance, the number of output frames from vslsmashsource is 239, and the filter requests 240-th frame, then vslsmashsource will return this error message. I guess mvtools or VapourSynth's AviSynth compatible module causes the problem.
__________________
僕と契約して、L-SMASH developerになってよ! L-SMASH | L-SMASH Works | Opus-in-ISOBMFF specification and reference software |
4th August 2013, 11:48 | #72 | Link | |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,548
|
Quote:
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
|
4th August 2013, 14:20 | #74 | Link |
Spinner of yarns
Join Date: May 2009
Posts: 164
|
@ Myrsloik
Should return with error or warning message? @ Music Fan I can't get what you mean.
__________________
僕と契約して、L-SMASH developerになってよ! L-SMASH | L-SMASH Works | Opus-in-ISOBMFF specification and reference software |
4th August 2013, 14:31 | #75 | Link |
Registered User
Join Date: May 2009
Location: Belgium
Posts: 1,743
|
I want to open a vfr video with LWLibavVideoSource, is there anything to add at the end of the 1st line of the script ?
For comparison, when it's done with DirectShowSource, one has to add convertfps=true. Is there anything like this for LWLibavVideoSource ? |
4th August 2013, 14:47 | #76 | Link |
Professional Code Monkey
Join Date: Jun 2003
Location: Kinnarps Chair
Posts: 2,548
|
As I said, filters are allowed to request frames beyond the end. No errors or warnings.
__________________
VapourSynth - proving that scripting languages and video processing isn't dead yet |
5th August 2013, 09:38 | #77 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
Current versions of L-SMASH Works appears to be r662.
Changelog is probably best read in the Github. __ A user in the german doom9/Gleitz forum is reporting intermittent issues with batch-converted DVB-S2 720p50 movies being encoded twice as long, sometimes repeated, sometimes with green blanks. But before your alarm goes off, we are trying to discover the reason (RAM, resident AV, timing issue of indexing different files with always the same temporary name...). Usually a second run returns a correct conversion. Last edited by LigH; 5th August 2013 at 09:45. |
6th August 2013, 16:14 | #78 | Link | |
Oz of the zOo
Join Date: May 2005
Posts: 208
|
Quote:
Stacked=true: 950 fps (LWLibavVideoSource only) -> 400 fps drop. Code:
msb = crop(0,0,0,height/2) lsb = crop(0,height/2,0,0) stackvertical(mt_lutxy(msb,lsb,"x 8 << y + 2 >>",u=3,v=3), \ mt_lutxy(msb,lsb,"x 8 << y + 3 &u 6 <<",u=3,v=3)) Code:
assumebff.turnleft.separatefields.turnright.assumeframebased stackvertical( mt_lutxy(selectodd, selecteven, "x 8 << y + 2 >>", u=3,v=3), \ mt_lutxy(selectodd, selecteven, "x 8 << y + 3 &u 6 <<", u=3,v=3)) It'd be nice if the LW output for 10-bit files in avisynth would match that, since it's not as useful otherwise. Last edited by wOxxOm; 6th August 2013 at 16:20. |
|
16th August 2013, 22:43 | #79 | Link | ||
Spinner of yarns
Join Date: May 2009
Posts: 164
|
Quote:
It just returns frame by frame. VFR->CFR conversion is "patches welcome". Quote:
'format' and 'stacked' are not exclusive option each other. I have not tested speed comparison though.
__________________
僕と契約して、L-SMASH developerになってよ! L-SMASH | L-SMASH Works | Opus-in-ISOBMFF specification and reference software Last edited by VFR maniac; 16th August 2013 at 22:45. |
||
16th August 2013, 22:58 | #80 | Link | |
Oz of the zOo
Join Date: May 2005
Posts: 208
|
Quote:
Code:
YUV420P10 265 - default mode YUV420P10stacked 248 YUV420P16 270 YUV420P16stacked 190 - same fps as the old ffms2-mod Code:
YUV420P10 285 - 7% faster YUV420P10stacked 285 - 15% faster YUV420P16 285 - 5% faster YUV420P16stacked 223 - 17% faster than the previous build Last edited by wOxxOm; 18th August 2013 at 23:02. Reason: 18 Aug build speed test added |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|