Re: [FFmpeg-user] ffplay RTSP listen mode with UDP

2018-03-14 Thread Roee Kashi
any lead on this issue?

2018-03-08 12:10 GMT+02:00 Roee Kashi <gala...@gmail.com>:

> Hi,
>
> i'm trying to use RTSP to push video from client to server.
> it works on TCP, but fails on UDP.
>
> server side:
> > ffplay.exe -rtsp_flags listen rtsp://0.0.0.0:14000/test
>
> client side (TCP mode):
> > ffmpeg.exe -re -i  -rtsp_flags prefer_tcp -f rtsp
> rtsp://SERVER_IP:14000/test
>
> cliend side (UDP mode):
> > ffmpeg.exe -re -i  -f rtsp rtsp://SERVER_IP:14000/test
>
>
> when I open the ffmpeg in the client side in TCP mode, everything works,
> and i see the video stream in the server.
> But when i open the ffmpeg in the client side in UDP mode, the server
> writes an error:
> "bind failed error number -10048" (already in use)
>
> to try and investigate this problem a little bit, i set RTSP min port in
> the server to 6001.
> the result was the same, yet i could see (using netstat) ffplay listening
> on 6001 in UDP (and still writes the same binding error).
>
> seems like something in the RTSP reverse mode is not fully compatible with
> UDP mode, and it tries to bind the same port twice.
>
> is there a workaround to this matter?
>
> tested with Zeranoe build 20180307-5ab0ecf
>
> Roee.
>
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-user] ffplay RTSP listen mode with UDP

2018-03-08 Thread Roee Kashi
Hi,

i'm trying to use RTSP to push video from client to server.
it works on TCP, but fails on UDP.

server side:
> ffplay.exe -rtsp_flags listen rtsp://0.0.0.0:14000/test

client side (TCP mode):
> ffmpeg.exe -re -i  -rtsp_flags prefer_tcp -f rtsp
rtsp://SERVER_IP:14000/test

cliend side (UDP mode):
> ffmpeg.exe -re -i  -f rtsp rtsp://SERVER_IP:14000/test


when I open the ffmpeg in the client side in TCP mode, everything works,
and i see the video stream in the server.
But when i open the ffmpeg in the client side in UDP mode, the server
writes an error:
"bind failed error number -10048" (already in use)

to try and investigate this problem a little bit, i set RTSP min port in
the server to 6001.
the result was the same, yet i could see (using netstat) ffplay listening
on 6001 in UDP (and still writes the same binding error).

seems like something in the RTSP reverse mode is not fully compatible with
UDP mode, and it tries to bind the same port twice.

is there a workaround to this matter?

tested with Zeranoe build 20180307-5ab0ecf

Roee.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] using -vtag on input files

2015-04-05 Thread Roee Kashi
just mentioning, adding  | OUT_INPUT to vtag option indeed sort it out.
i hope it will get into git-master one day :)

thanks

2015-04-02 19:32 GMT+03:00 tim nicholson nichot20-at-yahoo@ffmpeg.org:

 On 02/04/15 16:45, Carl Eugen Hoyos wrote:
  tim nicholson nichot20-at-yahoo.com at ffmpeg.org writes:
 
  ffmpeg.exe -f rawvideo -vcodec rawvideo -s 704x576
  -r 25 -pix_fmt yuv420p -vtag YV12 -i raw.yuv -f avi
  -qscale 0 out.avi
 
  Ahh, so you are using the pix_fmt to specify the input...
 
  What happened on the older version if you left the
  -vtag off? I think its always only been an output
  only option
 
  It was definitely an input- and output-option.
  It is currently not possible to (easily) read
  such streams.
 

 So it was, I see you fixed it ages ago, sorry for causing confusion by
 misremebering.

 In oreder to make amends I think I have tracked the issue down

 It looks like the merge 5743095c line 3043 from avconv made it at output
 only option...

 needs an  OPT_INPUT | OPT_OUTPUT instead of OPT_OUTPUT


  One possible work-around is of course to remux
  to nut with (output) option vtag.
 
  Carl Eugen
 
  [...]


 --
 Tim.
 Key Fingerprint 38CF DB09 3ED0 F607 8B67 6CED 0C0B FC44 8B0B FC83
 ___
 ffmpeg-user mailing list
 ffmpeg-user@ffmpeg.org
 http://ffmpeg.org/mailman/listinfo/ffmpeg-user

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user


Re: [FFmpeg-user] using -vtag on input files

2015-04-02 Thread Roee Kashi
first, since my rawvideo input is YV12 and there's no such pix_fmt, yuv420p
without vtag results with a blue-pink video output.
second, before vtag supported input files, i had to convert the file first
to avi with -vcodec copy, and then convert it to mpeg4 or something, which
takes forever.

i think this thread could shed some light on this matter (last message is
the most important i think):
http://ffmpeg-users.933282.n4.nabble.com/convert-YV12-stream-to-ProRes-td4665890.html

Roee.

2015-04-02 17:53 GMT+03:00 tim nicholson nichot20-at-yahoo@ffmpeg.org:

 On 02/04/15 15:22, Roee Kashi wrote:
  Hi,
 
  with the older ffmpeg version (described earlier), my command line looks
  like this:
  ffmpeg.exe -f rawvideo -vcodec rawvideo -s 704x576 -r 25 -pix_fmt
 yuv420p
  -vtag YV12 -i raw.yuv -f avi -qscale 0 out.avi

 Ahh, so you are using the pix_fmt to specify the input...

 What happened on the older version if you left the -vtag off? I think
 its always only been an output only option, and istr a patch to fail
 options put in the wrong place.

 What happens if you move the option to the output side on a current build?

 
  with newer version, the output of the same command is:
  [...]


 --
 Tim.
 Key Fingerprint 38CF DB09 3ED0 F607 8B67 6CED 0C0B FC44 8B0B FC83
 ___
 ffmpeg-user mailing list
 ffmpeg-user@ffmpeg.org
 http://ffmpeg.org/mailman/listinfo/ffmpeg-user

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user


Re: [FFmpeg-user] using -vtag on input files

2015-04-02 Thread Roee Kashi
Hi,

with the older ffmpeg version (described earlier), my command line looks
like this:
ffmpeg.exe -f rawvideo -vcodec rawvideo -s 704x576 -r 25 -pix_fmt yuv420p
-vtag YV12 -i raw.yuv -f avi -qscale 0 out.avi

with newer version, the output of the same command is:
ffmpeg version N-71209-gd759844 Copyright (c) 2000-2015 the FFmpeg
developers
  built with gcc 4.9.2 (GCC)
 ...
Option vtag (force video tag/fourcc) cannot be applied to input file
raw.yuv -- you are trying to apply an input option to an output file or vice
 versa. Move this option before the file it belongs to.
Error parsing options for input file raw.yuv.
Error opening input files: Invalid argument


this error can be with any input file, not necessarily a yuv file, but to
fully test it with the YV12 tag, i uploaded raw.yuv file:
http://www.filedropper.com/output1


2015-04-02 16:11 GMT+03:00 Carl Eugen Hoyos ceho...@ag.or.at:

 tim nicholson nichot20-at-yahoo.com at ffmpeg.org writes:

  On 02/04/15 13:56, Roee Kashi wrote:
  
   back in 2012 I could use -vtag on an input rawvideo file,
   thus tell ffmpeg the pixel format is YV12.
  
   at a certain point there was a regression in that feature
   so vtag is again allowed only for outputs.

  use -pix_fmt, valid for input/output

 There is no such pix_fmt...

 Carl Eugen

 ___
 ffmpeg-user mailing list
 ffmpeg-user@ffmpeg.org
 http://ffmpeg.org/mailman/listinfo/ffmpeg-user

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user