|
|
|
#1
|
|||
|
|||
|
Thank you Felice, but your calculation above address very different purpose. To clarify, your calculation above is about getting best possible quality for certain length of video while still fitting specific medium format. In other words, targeted size is a known constant and bitrate is calculated to get most of that size.
On the contrary when repacking game videos, targeted size is a variable and objective is to get it as low as possible. Therefore its about quality vs size, not about bitrate for certain known size. And for that, you absolutely have to consider resolution which in turn must be selected based on targeted display resolutions. Specifically, my 640x360 is exact 1/3 of 1920x1080(for which it was chosen) in terms of W and H and its exact division. It will still look ok as it is closer to 1/2 res., whereas 1/4 res for example was already too low in my tests(regardless of bitrate/quality). So pixels do matter here. You want to get as low resolution and bitrate as possible to save as much space as possible, while compromising on quality as little as possible. I agree there is not mathematically standard bitrate and it also depend on the codec, I referred to 2880 as "enough" in scale ratio because for all modern codecs if you check various original FullHD game videos they almost never have significantly more than that. 2880 was referred only as an example for being "enough" for majority of FullHD content out there(in games). Last edited by elit; 18-11-2017 at 11:31. |
| Sponsored Links |
|
#2
|
||||
|
||||
|
Yes, ok theoretically your calculation could also work, but you'll have the same visual quality by playing the video natively at 360p recoded, from the original 1080p, but if you try to reproduce it at 1080p the 360p recoded, you'll have the degrade of the image , you will never get the same (definition/pixel), especially when it comes to
games, the majority and the most ordinary today at 1080p.
__________________
≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈ ≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈ « I Mediocri Imitano, I Geni Copiano, Dio Crea & Distrugge » (Io Ridefinisco & Perfeziono le Loro Opere Rendendole Uniche) ![]() ≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈ ≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈ « Mediocrities Imitate, Genius Copy, God Creates & Destroys » (I Reconsider & Improve Their Works, Rending Them One And Only)
|
|
#3
|
|||
|
|||
|
But that is the whole point of this topic!
![]() Its about recoding game videos from original(FullHD mostly) into a low res vids to save space, and is directed for game repackers! Of course we are not going to get same fidelity, the idea is to get reasonable enough(read watchable) quality for 1/4- of saved space. |
|
#4
|
|||
|
|||
|
Here is how you recode bink videos while preserving their original multi-audio tracks:
Example of original file with multiple audio tracks(note track ID start at 100): orig.png Recoding this video make it lose them all: recmp.png What to do now: proc.png ^Select newly recoded video and click "Mix in sound", select original video that contained all tracks(remember their ID's), select new(or same) video for output, select compression(recommended 4), select what ID number will new audio track be, select ID track number from original video you want to inject, ten click "Mix". New video will be created with sound injected into appropriate track ID(video quality unaffected). Audio ID track number of original and into new file must be selected same for games to work properly! You need to process each track injection separately, remember to select last created bink file as new "Mix in sound" source. Remember however you can batch process this with small batch list modification, either directly in RAD Tools batch list or through .bat file shell script. Here is example where I already inserted 2 audio tracks from original: cont.png Nothing stop us now from recoding bink videos without fear of losing audio. EDIT: Here is how to automate it: Code:
set binkmix="C:\Program Files (x86)\RADVideo\binkmix.exe"
for %%i in ("a\*.bik") do (
%binkmix% "%%i" "%%~nxi" "%%i" /o /l4 /t0 /i0 /#
%binkmix% "%%i" "%%~nxi" "%%i" /o /l4 /t1 /i1 /#
...
)
Last edited by elit; 06-04-2018 at 08:08. |
| The Following 4 Users Say Thank You to elit For This Useful Post: | ||
|
#5
|
|||
|
|||
|
Recently I encountered games whose videos consist of short period length(10s - ~1min), but with incredibly big size for such length(80-200mb). These and few other cases, like videos with quick movements/transitions may need higher bitrate as 320k can be on the edge(even for 360p resolution). 640k-768k can be considered. I found that for these special cases even higher bitrate doesn't create files bigger than ~10% of original. For example, recently I recoded 4.2gb vids to ~320mb with 768k. This was for mp4(h264) not bink, maybe thats why, but 320k work on them in majority of cases as well.
What I am saying is that sometimes, certain input content behave "specially" to encoders in terms of output and ratio. In those cases, 320k would create files way too small(say under 1mb of like ~60mb+ original). Based on that too high ratio you would know something is not right, where you normally get ~4-8x less size using 320k now you see ~50x+ less, which is suspicious. In those cases, dont worry increasing(up to 640-768k should be enough) bitrate as you are still going to get *extremely good* ratio. This also mean that ratio comparison between original and recoded size with visual quick preview is an important practice to find and treat those "special cases". |
|
#6
|
|||
|
|||
|
Here is another example, as I am repacking FFXII I recoded webm vids in it. I used 768k bitrate for this, its vp8 format.
Default: default.jpg Recoded: recode.jpg Now the thing is, how much space did I saved? Original videos dir was: 10gb. Recoded: 625mb. Dont forget that it is blurrier also because of lowered resolution to 640x360. EDIT: Here is same recoded again but with original resolution recoded2.png Less blurry but some pixelation already visible. 360p is better. Note that while on these pics blur may look too big, in motion this is much less of problem and video appear very solid in perception. Last edited by elit; 24-02-2018 at 09:14. |
| The Following User Says Thank You to elit For This Useful Post: | ||
ffmla (03-07-2019) | ||
|
#7
|
|||
|
|||
|
any idea how to sync audio and video wav and avi after changing frame rate from 30fps to 24fps ?
|
|
#8
|
|||
|
|||
|
Not really, haven't needs for doing so yet, I would probably use rad tools or some ffmpeg frontend gui.
|
|
#9
|
|||
|
|||
|
Useful topic, I think I should take a look on GTA V, there are almost 2.5G of biks, recoding them should make them smaller, and then I can use bpk
__________________
NOT AVAILABLE |
| The Following User Says Thank You to 78372 For This Useful Post: | ||
elit (06-04-2018) | ||
|
#10
|
|||
|
|||
|
Quote:
That said, I think its time to refresh the main post with new info. |
| The Following 2 Users Say Thank You to elit For This Useful Post: | ||
78372 (06-04-2018), EzzEldin16 (09-04-2018) | ||
|
#11
|
|||
|
|||
|
260mb should be amazing, my main game is 50G(1.0.350.1) because I resized textures and so after encoding biks it will be about 47.5G, and probably pzlib+srep+dlz should make it like 25G(There are lots of dds textures)
__________________
NOT AVAILABLE |
![]() |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Tips for Diner Dash | AnyavanS1261994 | General Gaming | 1 | 01-07-2007 13:27 |
| Newbie needs tips on correct media | deerayrose | CD/DVD Recordable Media | 8 | 29-02-2004 14:36 |
| Installation Tips | TylerDurden | PS2 Games | 0 | 03-01-2004 13:52 |
| Soldering tips | seaneyb2003 | PSX Games | 16 | 30-11-2003 00:39 |
| messhia tips needed | squatcher | PS2 Games | 7 | 25-03-2002 14:28 |