cademtz / sparkly-fx

A recording utility for Team Fortress 2
17 stars 2 forks source link

Failed to create FFmpeg pipe `writer->WriteFrame` failed. The FramePool will close. #6

Closed esogcs closed 3 months ago

esogcs commented 4 months ago

Failed to create FFmpeg pipe writer->WriteFrame failed. The FramePool will close.

issue

FFmpeg doesnt seem to record the frames and it gives me an "audio" file of only one frame with no output image

cademtz commented 4 months ago

Please attach your config file and I will look into this

esogcs commented 4 months ago

cfg.zip

cademtz commented 4 months ago

I'm sorry, I meant for you to attach Sparkly FX's config file.

You can find this next to xsd-base64.dll file, insparklyfx/config.json

cademtz commented 4 months ago

In the meantime, try a different directory. It is possible that your game does not have permission to write frames to E:\Sparkly

EDIT: Nevermind. This does not apply to you because FFmpeg would have printed the following:

Failed to create folder (Access is denied.): 'C:\'
cademtz commented 4 months ago

A new update was released. It will reveal more detailed information in the error log.

You can test the update and see what the new errors look like.

esogcs commented 4 months ago

It still seems to give me the same error when I press play on sparklyfx, I updated to the latest build but it doesnt seem to give me more info on the error log. Config: config.json failed ffmpeg

I have hlae launcher with the newest patch image image

esogcs commented 4 months ago

xsdk-crashlog.txt

crash log

Uryyb4 commented 4 months ago

I'm having the same issue, heres my config

If anybody else runs into this issue, just specify qoi as sparklyfx's video encoder, then use -framerate yourfps -pattern_type sequence -i frame_%d.qoi in the output folder of sparklyfx with ffmpeg, along with any other encoding settings

cademtz commented 3 months ago

@Uryyb4 @esogcs I have found the likely issue. SparklyFX only uses the default FFmpeg path, and not the one you manually specified. For esogcs and another users, no default FFmpeg path existed.

This behavior is obviously incorrect and will be fixed shortly.

cademtz commented 3 months ago

Should be fixed in commit f1965c9da47ea2e171d897ff075917f4c7f1a409. Please download the latest release and confirm this for me, when you have time.

esogcs commented 3 months ago

works now, thank you