I hate to be the bearer of bad news, but this production workflow is very,
very bad. Nobody should use this and I will explain why not.
AVC (x264 and h264) are lossy video codecs, meaning that encoding video to
these formats always results in a loss of image quality, *every single time
you do it.* This bizarre workflow has *three* separate AVC encoding
processes.
All video production workflows, of any complexity, should ideally use
lossless media until the very last step of rendering the final video for
distribution. This means that if you are going to use x264vfw in Dxtory,
there should be no other reencoding of the video at all. This is an
acceptable method if you don't want to edit the video, and it still allows
you to edit the audio and then multiplex the two streams into one mp4 file.
In situations where someone wants to edit the captured video, but disk
space is limited, it's legitimate to do at least the first two steps of
MrMarcalus's workflow. This is two reencodes of lossy footage, but it's
viable as long as you use a very high bitrate with x264vfw in Dxtory. *Under
no circumstances should anyone do the third step with Handbrake.*
Handbrake is not a magical piece of software that makes videos smaller. It
does literally the same thing both x264vfw and Adobe Premiere Pro can do:
it's just another AVC encoder!
In this example, MrMarcalus exports from Premiere with AVC at 9 Mbps for
both maximum and average bitrate, 1-pass. Notice how his Handbrake encoder
also has maximum and average bitrate settings, and an option for 1- or
2-pass encoding.
*Handbrake literally does the same exact thing Premiere does!* The only
difference are his settings. Instead of 9 Mbps average bitrate, he's using
the much lower bitrate of 1.8 Mbps. This is the only reason the Handbrake
video has a smaller file size.
If you really want a 1.8 Mbps 2-pass encode, then just set Premiere to 1.8
Mbps average bitrate and skip the unnecessary step of reencoding lossy
video a third time. The Handbrake step results in lower quality than
exporting directly to 1.8 Mbps from Premiere and it's just a waste of time.
I want to make a correction to my original post. After making it, I looked up what the mysterious "-keyint 1" encoder setting actually does, and it governs how often key frames are generated. A key interval of 1 means that every frame is a key frame.Key frames are intermittent lossless frames that lossy frames reference. Lossy frames based off of a single key frame is called a "Group of Pictures" (GOP), and any advanced AVC encoder will let you adjust the GOP size.At 10:13 in the video, you can see that Premiere's H.264 encoder has a "Key Frame Distance" setting. This is the same setting. It's set to 30 by default, which means there's one key frame every second for a 30 FPS video.If you're using a key interval of 1, then all frames of the encoded video are key frames. In other words, the video is lossless. So, the capturing of footage is lossless with this workflow. I was wrong to say that it was lossy.The Handbrake step is still incredibly bad. Never do it.
+Rollersteaam Yes, Handbrake is completely useless in this workflow. I'll just add that 1.8 Mbps is too low a bitrate for 1080p video unless it's a slideshow. This guy's original bitrate of 9 Mbps is better for action games like BSI.
+Eincrou This is very true. There is no point putting the clip through Handbrake unless the format/codec isn't working with Premiere, all you are doing is lowering the quality.Lower the bitrate on premiere pro itself, and then as if like magic the video is at a decent fucking filesize.
Could you list what codecs you have installed? I honestly don't remember
what I had before, but it worked fine and now they just black screen on
me. I recently had to re-install a lot of codecs, and old videos that were
in AVI format that worked in Premiere now show up as black. They worked
fine before, so I don't want to start having to convert them to mp4s now
(and ffmpeg yells at me a lot with vague error messages).
+Law p.s. A friend of mine says they open fine in Lightworks, but the free version of that is limited to 720p. If you're up for learning Avisynth, they work fine except that you can't preview the script in a media player, but the AvsP preview works.
+AudioSerf It probably has something to either do with the decoder (a few places pointed towards FFDShow Tryouts, but it didn't work for me, maybe some different settings), or the core 264 library that's installed. When I did a system restore it started working again, but as soon as installed a new version of x264vfw it stopped working.
+Law Sorry to hear that. I've got over 15GB of Titanfall clips I'm trying to trim with Premiere, but I can't get them to show either. I've been working for the last hour on a fix. I'll let you know once I've found it.
+AudioSerf It is possible for the files to work in Premier without converting, I had it working for months. Then I reinstalled some codecs and it stopped working. There is definitely a way to fix it, but any actual fix is buried under dumb workarounds like "convert the file first" (which for me often caused desync). Anyway it doesn't matter, I just went back to using Avisynth.
As far as I know, the reason for that is that DxTory encodes recordings in as Mp4 in an AVI container. You can use HandBrake to convert it to a usable file though.
HOW TO USE DXTORY WITH CALL OF DUTY: GHOSTS!
Subscribe! ➜ //full.sc/11Ugeb3 If you guys enjoyed the video don't forget to leave a "Like" and leave a comment on your favorite part :) As always, Thank you ...
How To Record PC Gameplay Without Lag Using The Lagarith Lossless Codec In DxTORY |Anyone Can Do It|
I joined Maker Studios & so can you! Click here to see if your channel qualifies for RPM Network/Maker Studios //awe.sm/t3kM0 Download: ...
+jokamutta Me either but you dont have a choice. Some games just dont use the same way of going fullscreen. Fraps is the only one that gets some of them. Unless you're using a external device such as an Elgato HD60.
These files are gigantic, so your PC has problems playing this video in normal speed because of the big mass of data (high bitrate) he has to work withFor example: I took a YouTube-video, downloaded it and looked for the bitrate: ~1mbit/s (1080p, 30fps)Then i looked at one of my recorded videos: ~1.770mbit/s (720p, 60pfs) / ~800mbit/s (720p, 30fps)As you can see, the difference beween normal video (YouTube) and Captured Video is very big and even my PC (AMD r9 280x / i5 3,4 ghz / 8gb ram) has problems playing these videos at the beginning (it "catches up" after like 10 seconds and then runs normal)
Simple Virtual Audio Cable and Dxtory Setup Tutorial
Can we hit 50 likes? ▻A quick tutorial on how to easily setup your VAC and Dxtory to split your game, mic and communication audio track. I hope you enjoy.
+itsDRIPPER “JacekTomek” It has an impact on your cpu so if that is not that good then you might find you have delayed audio. To fix this I usually found restarting my PC worked fine as it happened over a long period of time however if it is happening straight away then you might need to look up some other form of splitting your audio.
When setting the virtual audio cables to default if I unplug my headset
will it let me listen through the speakers or do I have to change speakers
back to default