Recherche avancée

Sur d’autres sites (6463)

• opening .js file in CMD runs windows script host [migrated]

  6 août 2017, par Alex

  I am installing ffmpeg for node.js.
  When i run ffmpeg by the following command in CMD ; ffmpeg -codecs
  It opens a .js file with windows script host instead of CMD.

  This is because i accidentally pressed windows script host as standard program for .js files.

  I am running this on windows 10 and i cannot find a way to reverse my actions..
  i have tried select CMD as standard program for opening javascript files but this didnt work. It gave me an error that this file type could not be associated with the program chosen.

  I dont know what to do.

• How do I install stream-m on my vps server using putty for windows

  19 décembre 2014, par They Went Viral

  when i logged into my vps server using the plesk control panel i see httpdocs in the root when using putty i entered an ls command and i only see

  @vps : # ls
  ffmpeg parallels parallels_installer plesk-installer.sh univac.webm

  wonder why this is why dont i see the same files as in te control panel ??!

  the problem is i am trying to run this https://github.com/vbence/stream-m on the server
  the read me says

  RUNNING THE SERVER

  java -jar stream-m.jar

  Before running the server you should edit the sample config file (change password and choose a stream name). So you will end up with something like :

  java -jar stream-m.jar server.properties

  but im getting an error that says

  @vps : # java -jar stream-m.jar server.properties
  Error : Unable to access jarfile stream-m.jar

  Now i do have ffmpeg installed as per putty but when logged into the control panel i don’t see that either what am i doing wrong ?

• lavf : Use wchar functions for filenames on windows for mkdir/rmdir/rename/unlink

  17 novembre 2014, par Martin Storsjö

  lavf : Use wchar functions for filenames on windows for mkdir/rmdir/rename/unlink
  This makes sure that the internal utf8 path names are handled
  
  properly - the normal file handling functions assume path names
  
  are in the native codepage, which isn’t utf8.
  This assumes that the tools outside of lavf don’t use the mkdir
  
  definition. (The tools don’t do the same reading of command line
  
  parameters as wchar either - they probably won’t handle all possible
  
  unicode file parameters properly, but at least work more predictably
  
  if no utf8/wchar conversion is involved.)
  This is moved further down in os_support.h, since windows.h shouldn’t
  
  be included before winsock2.h, while io.h needs to be included before
  
  the manual defines for lseek functions.
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DBH] libavformat/internal.h
  • [DBH] libavformat/os_support.h