QuoteConfiguring M/MI/MIZZY/FFmpeg-Command-0.19.tar.gz with Makefile.PL
Checking if your kit is complete...
Looks good
Generating a dmake-style Makefile
Writing Makefile for FFmpeg::Command
Writing MYMETA.yml and MYMETA.json
MIZZY/FFmpeg-Command-0.19.tar.gz
C:\Strawberry\perl\bin\perl.exe Makefile.PL -- OK
Running make for M/MI/MIZZY/FFmpeg-Command-0.19.tar.gz
cp lib/FFmpeg/Command.pm blib\lib\FFmpeg\Command.pm
MIZZY/FFmpeg-Command-0.19.tar.gz
C:\STRAWB~1\c\bin\dmake.exe -- OK
Running make test
"C:\Strawberry\perl\bin\perl.exe" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib\lib', 'blib\arch')" t/*.t
t/00-load.t ............ 1/? # Testing FFmpeg::Command 0.19, Perl 5.020002, C:\Strawberry\perl\bin\perl.exe
Das System kann den angegebenen Pfad nicht finden.
t/00-load.t ............ ok
t/01-coderef.t ......... 1/2 Das System kann den angegebenen Pfad nicht finden.
t/01-coderef.t ......... ok
t/02-option_a.t ........ Das System kann den angegebenen Pfad nicht finden.
t/02-option_a.t ........ ok
t/03-option_b.t ........ Das System kann den angegebenen Pfad nicht finden.
t/03-option_b.t ........ ok
t/04-option_c.t ........ Das System kann den angegebenen Pfad nicht finden.
t/04-option_c.t ........ ok
t/05-option_d.t ........ Das System kann den angegebenen Pfad nicht finden.
t/05-option_d.t ........ ok
t/06-output_options.t .. Das System kann den angegebenen Pfad nicht finden.
t/06-output_options.t .. 1/? # Failed test at t/06-output_options.t line 25.
# got: 'ffmpeg -y -i in.mp4 -f mp4 -ab 64 -vcodec mpeg4 -acodec libaac -s 320x240 -ar 48000 -b 600 out.mp4'
# expected: 'ffmpeg -y -i in.mp4 -acodec libaac -b 600 -f mp4 -vcodec mpeg4 -ar 48000 -s 320x240 -ab 64 out.mp4'
Das System kann den angegebenen Pfad nicht finden.
# Failed test at t/06-output_options.t line 38.
# got: 'ffmpeg -y -i in.mp4 -f mp4 -vcodec mpeg4 -acodec libfaac -ab 64 -s 320x240 -ar 48000 -b 600 out.mp4'
# expected: 'ffmpeg -y -i in.mp4 -b 600 -acodec libfaac -f mp4 -vcodec mpeg4 -ar 48000 -s 320x240 -ab 64 out.mp4'
# Looks like you failed 2 tests of 2.
t/06-output_options.t .. Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/2 subtests
t/boilerplate.t ........ ok
t/pod-coverage.t ....... ok
t/pod.t ................ ok
Test Summary Report
-------------------
t/06-output_options.t (Wstat: 512 Tests: 2 Failed: 2)
Failed tests: 1-2
Non-zero exit status: 2
Files=10, Tests=15, 13 wallclock secs ( 0.44 usr + 0.23 sys = 0.67 CPU)
Result: FAIL
Failed 1/10 test programs. 2/15 subtests failed.
dmake.exe: Error code 255, while making 'test_dynamic'
MIZZY/FFmpeg-Command-0.19.tar.gz
C:\STRAWB~1\c\bin\dmake.exe test -- NOT OK
//hint// to see the cpan-testers results for installing this module, try:
reports MIZZY/FFmpeg-Command-0.19.tar.gz
Stopping: 'install' failed for 'FFmpeg::Command'.
Failed during this command:
MIZZY/FFmpeg-Command-0.19.tar.gz : make_test NO
2017-08-29T17:26:37 GwenDragonIch vermute, in der Umgebungsvariable PATH hast du keine Angabe auf ffmpeg.exe drin.
2017-08-29T19:57:22 GUIfreundWenn ich mich recht erinnere, musst du / statt \ als Pfadtrenner verwenden.
2017-08-30T08:28:14 reneeDie Fehler in dem 06_*-Test kannst Du ignorieren. Da hat einer nicht mit der zufälligen Reihenfolge von Hashkeys gerechnet...
1 2
require FFmpeg::Command; my $ffmpeg = FFmpeg::Command->new('C:/ffmpeg/bin/ffmpeg.exe');
QuoteC:\>C:/ffmpeg/bin/ffmpeg.exe -version
ffmpeg version N-86994-g92da230 Copyright (c) 2000-2017 the FFmpeg developers
built with gcc 7.1.0 (GCC)
configuration: --enable-gpl --enable-version3 --enable-cuda --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-zlib
libavutil 55. 74.100 / 55. 74.100
libavcodec 57.102.100 / 57.102.100
libavformat 57. 76.100 / 57. 76.100
libavdevice 57. 7.100 / 57. 7.100
libavfilter 6. 99.100 / 6. 99.100
libswscale 4. 7.102 / 4. 7.102
libswresample 2. 8.100 / 2. 8.100
libpostproc 54. 6.100 / 54. 6.100
2017-08-31T12:38:50 GwenDragonOder verpasst du dabei Ausgaben?
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
#!/usr/bin/perl use strict; use warnings; use 5.010; use Win32; use Win32::Process; if ( Win32::Process::Create( my $ProcessObj, 'd:\FFmpeg\bin\ffmpeg.exe', 'ffmpeg -i "d:\ein musikvideo.mp4" -filter_complex "[0:v]fade=t=out:st=229:d=4[v]; [0:a]afade=t=out:st=229:d=4[a]" -map "[v]" -map "[a]" -f mp4 "d:\ein neues video.mp4" 2>out.txt', 0, Win32::Process::NORMAL_PRIORITY_CLASS(),#|Win32::Process::DETACHED_PROCESS(), '.', ) ) { my $pid; if ($pid = $ProcessObj->GetProcessID()) { say "PID erhalten: $pid"; } else { die 'Kann PID zum Kindprozess nicht ermitteln (Zeile '.__LINE__.')'; } } else { die "Kann Verarbeitungsprozess nicht starten: '" .Win32::FormatMessage(Win32::GetLastError()) ."' (Zeile ".__LINE__.')' ; }
Quote[NULL @ 0000000002b169c0] Unable to find a suitable output format for '2>out.txt'
2>out.txt: Invalid argument
""-report
Dump full command line and console output to a file named program-YYYYMMDD-HHMMSS.log in the current directory. This file can be useful for bug reports. It also implies -loglevel verbose.
Setting the environment variable FFREPORT to any value has the same effect. If the value is a ’:’-separated key=value sequence, these options will affect the report; option values must be escaped if they contain special characters or the options delimiter ’:’ (see the “Quoting and escaping” section in the ffmpeg-utils manual).
The following options are recognized:
file
set the file name to use for the report; %p is expanded to the name of the program, %t is expanded to a timestamp, %% is expanded to a plain %
level
set the log verbosity level using a numerical value (see -loglevel).
For example, to output a report to a file named ffreport.log using a log level of 32 (alias for log level info):
FFREPORT=file=ffreport.log:level=32 ffmpeg -i input output
Errors in parsing the environment variable are not fatal, and will not appear in the report.
2017-09-08T16:56:00 LinuxerIch würde es mal mit der ffmpeg-Option -report versuchen?
Damit bräuchte es dann keinen Redirect des STDERR-Kanals mehr.
2017-09-08T16:56:00 Linuxer
1 2 3 4
# set ENV Variable $ENV{FFREPORT} "file=ffreport.log:level=32"; # call program system( "ffmpeg -i input output");