- Jun 30, 2018
- 282
- 129
Xvid is an extremely old codec that has poor compression efficiency, especially at HD resolutions. What is your intermediate format (the codec you export from renderer)? Do you render directly to xvid or do you render to PNG first then import as frames to an editor like Vegas?You don't have permission to view the spoiler content. Log in or register now.
Thanks, these all sound like great tips. It's gonna take a bit of research and some experimenting but we're definitely giving them a try (and btw to answer your question, so far we have been creating our animations by rendering to png images, turning them into a lossless avi clip with After Effect and then convert to xvid with AVC converter)Xvid is an extremely old codec that has poor compression efficiency, especially at HD resolutions. What is your intermediate format (the codec you export from renderer)? Do you render directly to xvid or do you render to PNG first then import as frames to an editor like Vegas?
I suggest you useYou must be registered to see the linksto compress the videos. The x265 encoder set to its "medium" preset in handbrake will give you similar quality at half the size of xvid. If you can't get that to work you can try the vp9 encoder, which offers similar quality to x265 but takes longer to encode.
You don't have permission to view the spoiler content. Log in or register now.
Another tip would be to use image overlays instead of whole frames for animations like the lightning effect around the text or the "sack over the head" sequence. One of the largest videos currently, "113_sackide.mpg" could easily be 1/10th its size if you had the driving sequence be a lower resolution(480p) playing in the background and you placed a high resolution "sack" texture over the video during playback. Players would not notice the reduced video resolution because it would be blocked by the texture anyway, and the codec's motion prediction algorithm would be able to handle the video far better without the static texture messing with the motion vectors. You could even eliminate the video altogether and just reuse "105_divemov.mpg" behind the texture instead.
As far as images, Webp is the clear choice. You can useYou must be registered to see the linksto convert from PNG to lossless Webp, which would bring a decent drop in size(maybe 30%) while not noticeably effecting quality. You could shrink it further if you went with Q90 lossy mode, which would still look pretty good.
Audio should be Opus format; unless you have golden ears Opus @ 128k sounds just like CD most of the time. Even 80k can sound good.
Thank you, that is very generous. You can always buy us a coffee through Paypal, use the account info@adventuresinenf.comI would like to support the game, but unfortunately I don't have a credit card. can I do it differently with the support ???
View attachment 655006
That's good, that means you don't really have to change your workflow much, just replace AVC converter with Handbrake. Unfortunately it doesn't look like RenPy supports h.265, so you'll have to stick to VP9. Sorry if I misled you earlier.Thanks, these all sound like great tips. It's gonna take a bit of research and some experimenting but we're definitely giving them a try (and btw to answer your question, so far we have been creating our animations by rendering to png images, turning them into a lossless avi clip with After Effect and then convert to xvid with AVC converter)
python:
renpy.music.set_volume(volume=0.2, delay=0, channel='music')
stop music fadeout 1
python:
renpy.music.set_volume(volume=1, delay=2, channel='music')
True, there are probably quite a few unused image files sitting in there too. We learned a lot on the job while building the game and some of the early mistakes are still there, just hidden under the carpet Before we publish our next version we'll have to spend quite some time tiding up the place, anyway thanks for all the tips and the work you've putting into thisThat's good, that means you don't really have to change your workflow much, just replace AVC converter with Handbrake. Unfortunately it doesn't look like RenPy supports h.265, so you'll have to stick to VP9. Sorry if I misled you earlier.
I've got another tip for you though. It looks like you have a lot of duplicate files. For example: say anything.ogg, anything10db.ogg, and anything20db.ogg all seem to be the same thing, and yet they are all taking up precious space. There are others too, like the main theme shows up 2 or 3 times as well. It looks like you were trying to play the song with reduced gain but there is a better way. You can reduce the volume of a song during playback by using this command on the line before you call the file in the script:
Code:python: renpy.music.set_volume(volume=0.2, delay=0, channel='music')
That way you can have just one copy of each song, which will clean up your file structure and save on space.You don't have permission to view the spoiler content. Log in or register now.
Just remember to set the volume back to 100% when you're finished with the song like this:
Otherwise you will wonder why everything is so quiet laterCode:stop music fadeout 1 python: renpy.music.set_volume(volume=1, delay=2, channel='music')
This is the first release so no average of anything, should know an average 3-4 releases from nowwhat is the average time gap between each update ?