BasharOfTheAges wrote:Just fucking use zarxGUI - It's as point and click as this shit gets. Easier than vdub and the damned guide spells it out for you step-by-step.
mirkosp wrote:BasharOfTheAges wrote:Just fucking use zarxGUI - It's as point and click as this shit gets. Easier than vdub and the damned guide spells it out for you step-by-step.
Eh, the issue with zarxgui is that it's using a old rev of x264, that's the point...
ALAN UPDATE ZARXGUI PLOX.![]()
![]()
BasharOfTheAges wrote:mirkosp wrote:BasharOfTheAges wrote:Just fucking use zarxGUI - It's as point and click as this shit gets. Easier than vdub and the damned guide spells it out for you step-by-step.
Eh, the issue with zarxgui is that it's using a old rev of x264, that's the point...
ALAN UPDATE ZARXGUI PLOX.![]()
![]()
The degree of how much that's a problem is minuscule compared with the problem at hand. Learn some sense of scale.
Nya-chan Production wrote:Old revision of x264 in ZarxGUI = making larger encodes = it can't be solved with ZarxGUI until newer revision is included (or maybe it could - for the price of quality, ofc)
BasharOfTheAges wrote:Nya-chan Production wrote:Old revision of x264 in ZarxGUI = making larger encodes = it can't be solved with ZarxGUI until newer revision is included (or maybe it could - for the price of quality, ofc)
I'm curious as to where the data point for that older build came from that would put it over 100MB and therefore be not big enough given the OP was using something else and converting to XviD.
Return to Site Help & Feedback
Users browsing this forum: No registered users and 1 guest