Day 14: No zero days November – 2023 – Voylin's Gamedev Journey

Been a calm day today, decided to work a bit more on the extension’s interface to be able to troubleshoot a bit better whilst working on the importer.

Interface?

So we have 4 classes, the pipe renderer (which can serve as a backup, probably going to remove this at some point though), the renderer, and importer. The 4th class is the interface. With this you’ll be able to use more FFmpeg functions which return data about video files, or about system data, to check by example which codecs can be used on your system and which can’t be used.

Plans for tomorrow?

For tomorrow, I want to work a bit more on the Godot side of things as I will really need to invest a bit more time in editing videos for my other channels, can’t let them stay in the fridge. ^^”

However, starting from the day after tomorrow I’ll be working fully on the importer again. In the beginning of No zero days November I felt that I should work as much as possible each and every day, kind of started figuring out that over exhausting myself each day will make me not last for the entire month hahah.

So I’m setting limits of 3 hours each day on the work I do on GoZen. This gives me enough time to spend time with family, cleaning, cooking, and working on my other channels. No time for hobbies, but I enjoy everything I do, even though the programming makes me want to pull out my hair every now and then hahah.

Conclusion

Progress has been coming allong each and evey day, sometimes a lot, sometimes not so much, but having finished the renderer with the ffmpeg library crosses a big checkmark on “Is GoZen actually possible?” list. 2 other items on that list are the importer and the timeline. Once we have a basic version of that, I’ll be a lot more confident in saying that GoZen will become a real video editor which can beat the competition. 🙂

Extra announcement

I know that I already posted my daily journal, but I really wanted to share this hahah. A story about me being dumb. ^^”

Almost double performance in rendering speed

I actually forgot to delete a line of code which was causing memory issues:
PackedByteArray frame_data = frame_image->save_webp_to_buffer(false, 1.0); Basically this was using cpu power to process each frame into an image, which we did not even end up using. So it would allocate memory, generate the image, and write the data before the actual data was send to the FFmpeg process. Woops hahah. completely forgot about removing that line.