[x264-devel] some questions about "x264_is_regular_file" & "x264_is_regular_file_path" in file "common\osdep.h"

[Edward Richards]

Using Windows Named Pipes (\\.\pipe\_THE_NAME_ ) is more complicated than
that.
You can't seek a pipe... which is one of the reasons that
"x264_is_regular_file" & "x264_is_regular_file_path" exist to test for such
things.

It turns out that you have to modify libav or ffmpeg's lavf to get it to
work with raw inputs like i420, i444 etc.

I have that code working but have not made a patch for submission.

It's not a x264 problem and it has nothing to do with the return codes from
the mentioned functions.

Edward

-----Original Message-----
From: x264-devel-bounces at videolan.org
[mailto:x264-devel-bounces at videolan.org] On Behalf Of Jason Garrett-Glaser
Sent: Friday, April 13, 2012 9:17 AM
To: Mailing list for x264 developers
Subject: Re: [x264-devel] some questions about "x264_is_regular_file" &
"x264_is_regular_file_path" in file "common\osdep.h"

On Fri, Mar 30, 2012 at 9:57 AM, zxfishhack <zxfishhack at 126.com> wrote:
> There is some problem that using a pipe for input stream of x264.exe 
> on Window Platform, I think the problem is the two functions I mention.
> I think it's check the return value in wrong way.
>
> In the function mention in the topic, I found the code below:
>
>     if( fstat( fileno( filehandle ), &file_stat ) )
>         return -1;
>
>     if( stat( filename, &file_stat ) )
>         return -1;
>
> but when I check for fstat & stat in MSDN and Linux man page 
> @linux.die.net , I found the return value is defined below:
> fstat - Linux man page(link: http://linux.die.net/man/2/fstat)

I'm not sure exactly what the problem is?  The descriptions you posted say
"-1 is error, 0 is no error", which the current code works correctly with.

Jason
_______________________________________________
x264-devel mailing list
x264-devel at videolan.org
http://mailman.videolan.org/listinfo/x264-devel