20:09
I'm working on a C# project where I need to run FFmpeg commands to process videos. The FFmpeg command works perfectly fine when executed directly in the shell, but it hangs when run from my C# application. I suspect the issue is related to the output pipes getting full.
Here is the FFmpeg command I'm using:
shell
C:\\path\\to\\ffmpeg.exe -f concat -safe 0 -i "C:\\path\\to\\list.txt" -vf "scale=1080x1920,setsar=1" -c:v libx264 -pix_fmt yuv420p -c:a aac -ar 44100 -ac 2 "C:\\path\\to\\output.mp4"
And here is my C# code:
private static async Task (...)
15:51
I'm working on a captcha solver and I need to use ffmpeg, though nothing works. Windows 10 user.
Warning when running the code for the first time:
C:\\Users\\user\\AppData\\Roaming\\Python\\Python310\\site-packages\\pydub\\utils.py:170: RuntimeWarning: Couldn't find ffmpeg or avconv - defaulting to ffmpeg, but may not work
warn("Couldn't find ffmpeg or avconv - defaulting to ffmpeg, but may not work", RuntimeWarning)
Then, when I tried running the script anyway and it required ffprobe, I got the following (...)
15:05
This is a head scratcher.
I need to move these three oddly-named files from an external 2.5" SSD to my desktop. The file names were intended to have variables replaced by date info, however, clearly it didn't work. So I'm left with these filenames that MacOS seems to want to interpret rather than treat as a string. I wish it was as easy as tossing in single quotes or escaping chars, but so far, that hasn't worked.
Files: Test01-$(internal:date_y)-$(internal:date_m)-$(internal:date_d)-.mp4 Test01-$(internal:date_y)-$(internal:date_m)-$(internal:date_d)-0001.mp4 (...)