search

arduano / Zenith-MIDI

world's fastest and most customisable MIDI rendering program
https://arduano.github.io/Zenith-MIDI/
Other
162 stars 21 forks source link

Video outputs only to the red channel, FFmpeg reports bad packet #57

Closed minelolpride closed 2 years ago

minelolpride commented 2 years ago

While the preview of the render displays with correct colors, the final rendered video appears very red, with no other colors present. image This is present on a fresh install, and occurs in every module, so I turned to FFmpeg to find this in the output. image This appears to happen no matter what my input. (settings, letting the render complete)

Is there maybe a version of FFmpeg that plays nice with Zenith here? The link in the README is dead too, so I cannot check it out.

Zenith version is 2.1.5 FFmpeg version is 5.0-full_build-www.gyan.dev

arduano commented 2 years ago

That's honestly strange. Are you using default settings? I've never seen this before.

Personally I have version 4.3.1 installed, if you want to try that.

minelolpride commented 2 years ago

Default settings will create this effect. I will try that version of ffmpeg later here though and see what it does.

minelolpride commented 2 years ago

image Downgraded to 4.3.1, the error persists. I am unsure if this is specific to my hardware too (Ryzen 7 3700x, EVGA GTX1060 6GB SSC), as when I asked around, I havent seen anyone else run across this as of yet

arduano commented 2 years ago

Yeah sorry I'm honestly not sure. I don't know anyone else who can reproduce this issue.

When I open FFMPEG, I set the input stream as raw colour bytes passed through stdin. I set the input colour format too, pretty sure it was either rgb or argb, but point is that it's set to the right one and should correctly work.

In your screenshot, I see that the error message comes from the rawvideo codec, I'm not sure if that one is built into ffmpeg, but if it isn't then maybe you have a codec issue? I'd suggest having a look into that.

minelolpride commented 2 years ago

I was tipped off to disable Unicode UTF-8 in the Windows Region Settings, which I had enabled. Turns out, doing just that fixed the issue. Not sure how it relates to this on a lower level, but it's a fix! image

arduano commented 2 years ago

that's so weird