Recherche avancée

Sur d’autres sites (4560)

• Attempting to Process.Start("ffmpeg.exe") ; unhandled exception [duplicate]

  7 janvier 2016, par hallwayRaptor

  This question already has an answer here :

  • Can Process.Start() take the system PATH into account ?
    
    7 answers
    

  I’m attempting to create a Windows Forms Application that will

  Process.Start("ffmpeg.exe");

  I’ve added the path (C :\Program Files (x86)\ffmpeg\bin) in the environment variables in Windows, and I can launch ffmpeg from anywhere in the CMD prompt with just ffmpeg or ffmpeg.exe.

  When I change the line to open something else that I’ve added to the environment variables manually such as Livestreamer the application launches no problem.

  It’s driving me crazy trying to figure out why this particular executable won’t launch when others that have been added the exact same way launch without problem.

  An unhandled exception of type ’System.ComponentModel.Win32Exception’
  occurred in System.dll

• libavformat/tcp.c : add send_buffer_size and recv_buffer_size options

  19 janvier 2016, par Perette Barella

  libavformat/tcp.c : add send_buffer_size and recv_buffer_size options
  adds two new options that may be set via the dictionary :
   send_buffer_size
  
   recv_buffer_size
  When present, setsockopt() is used with SO_SNDBUF and SO_RCVBUF to set
  
  socket buffer sizes.  I chose to make send and receive independent
  
  because buffering requirements are often asymmetric.
  Errors in setting the buffer size mean the socket will use its
  
  default, so they are ignored.
  There is no sanity checking on values, as the kernel/socket layers
  
  already impose reasonable limits if asked for something crazy.
  Rationale for enlarging receive buffers is to reduce susceptibility
  
  to intermittent network delays/congestion.  I added setting the send
  
  buffer for symmetry.
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] doc/protocols.texi
  • [DH] libavformat/tcp.c

• ffmpeg Command Fails in C

  16 février 2016, par cclloyd

  I have a program that stitches together files in ffmpeg using the system() function. It works when I run the command normally, but fails when I run it through the C program (it gets like 80% of the way through then fails saying

  [concat @ 0x7fe299801000] Impossible to open '/Us' parts.txt: No such file or directory
  
  No more output streams to write to, finishing.

  But that only happens in the C program. Not when I run the exact same command manually.

  The command it’s running is

  char command[1024];
  
  sprintf(command, "ffmpeg -f concat -i parts.txt -c copy s%de%02d.ts", season, episode);
  
  system(command);

  And the parts.txt file is as follows : http://pastebin.com/pUAu9mbt

  (Before you ask, yes those are absolute pathnames, not relative)