Open Bozzeh opened 3 years ago
You need to have the width and height be even. Most codecs including H264 need to have an even resolution.
I'm supposed to have an error message show up when that's not the case but I used an AND in my logic instead of an OR. Dummy me.
Issue remain on v1.50.6 with a 128x1080 resolution
Issue remain on v1.50.6 with a 128x1080 resolution
The pipe has been ended is just a generic message that something has went wrong with ffmpeg. Usually by modifying the arguments
200x1080 is OK for example
128x1080 working fine here.
The original issue was because the width or height was not even which we do not allow anymore https://github.com/lay295/TwitchDownloader/blob/611ae6a7e448709df627af0ef0dad9dfadb11586/TwitchDownloaderWPF/PageChatRender.xaml.cs#L261-L265
You can encounter this error by modifying the arguments on this page incorrectly. This is how most people encounter the pipe ended error atleast.
Right it work on libx264 and libx265 but not on h264_nvenc strangely.
-framerate {fps} -f rawvideo -analyzeduration {max_int} -probesize {max_int} -pix_fmt bgra -video_size {width}x{height} -i -
-c:v libx264 -preset veryfast -crf 18 -pix_fmt yuv420p "{save_path}"
-framerate {fps} -f rawvideo -analyzeduration {max_int} -probesize {max_int} -pix_fmt bgra -video_size {width}x{height} -i -
-c:v h264_nvenc -preset fast -cq 20 -pix_fmt yuv420p "{save_path}"
-framerate {fps} -f rawvideo -analyzeduration {max_int} -probesize {max_int} -pix_fmt bgra -video_size {width}x{height} -i -
-c:v libx265 -preset veryfast -crf 18 -pix_fmt yuv420p "{save_path}"
I can't see any configuration difference, whatever I will just render on CPU until AV1 is released. Thanks for your replies.
Not sure, I know NVENC in consumer GPUs are limited to 2 sessions at once. Are you running multiple instances of the program trying to render multiple chats at once and hitting the 2 session limit? (I think showplay also counts as one) but I'm not really sure.
I had already disabled ShadowPlay by precaution. And no I was not rendering anything else.
Ah, looks like it's a limit of the NVENC encoder.
https://forums.developer.nvidia.com/t/minimum-width-in-turing-gpus/155566
uh, trying to render chat 450x1080 and it progresses to like 60% to 80% before error pipelining me, is it a problem with the dimensions??, cleared cache and reinstalled still have the same problem idky. I have a 4 gigs mov of chat that i cant open. gonna try rendering with webm instead but that would take like thrice the amount of time and some change instead of just doing it with mov rle
uh, trying to render chat 450x1080 and it progresses to like 60% to 80% before error pipelining me, is it a problem with the dimensions??, cleared cache and reinstalled still have the same problem idky. I have a 4 gigs mov of chat that i cant open. gonna try rendering with webm instead but that would take like thrice the amount of time and some change instead of just doing it with mov rle
If you enable "Verbose Error Output" in the GUI there should be a popup that will help us diagnose why the pipe ended.
@ScrubN I couldn't render the video with the nvidia decoder,H264.H265 Always report errors,The pipe has been ended。I can't seem to find a solution
I couldn't render the video with the nvidia decoder,H264.H265 Always report errors,The pipe has been ended。I can't seem to find a solution
If you enable "Verbose Error Output" in the GUI there should be a popup that will help us diagnose why the pipe ended.
@ScrubN Here you are
@ScrubN Also, can you tell me if there is any way to quickly add rendered chat videos to videos, such as ffmpeg, and how I can do it
@ScrubN May I ask, are you still here? How do I fix this? The pipe has been ended,
The program changes the contents of the verbose error message box depending on the error message, but unfortunately it's only aware of the English version of the message. Due to other poor design decisions, that one message content check is the only way for it to display the other errors that I would need to see in order to fix the issue unless you are able to reproduce the issue with the CLI with all log levels enabled.
Hi, I am getting this error while rendering the chat, you can see in the logs that some have actually worked, and specifically i hope this helps in reproducing it too, but when i have the Width set to 225 it hits this error, doing 250 or above works fine. But would be cool to stay with 450x225 :)