Username:
B
I
U
S
"
url
img
#
code
sup
sub
font
size
color
smiley
embarassed
thumbsup
happy
Huh?
Angry
Roll Eyes
Undecided
Lips Sealed
Kiss
Cry
Grin
Wink
Tongue
Shocked
Cheesy
Smiley
Sad
123 ->
--
--
List results:
Search options:
Use \ before commas in usernames
Edit history:
TheVampire: 2014-04-16 03:51:54 pm
TheVampire: 2014-04-16 03:51:08 pm
http://exkode.com/dxtory-features-en.html

Recording games on PC can be a hassle sometimes, but using these settings will guarantee you the best quality for recording runs to be submitted on SDA with the lowest system impact possible.

So let's get started:

1. Folder Settings:

In this tab you will need to select the folder where your recordings will go. The best thing to do is to record on a dedicated Hard-Disk Drive so there is no other program that can interfere. If you have only 2 HDDs (one for the OS and one for games, media, etc), record on the one where your media is. Sometimes, recording on the OS HDD can cause system hangs or just general unresponsiveness. If you have only one HDD then just try your luck and hope you don't have any issues.

Also you have to consider the write speed and available space on the HDD. Any modern SATA2 HDD in good condition can be used to record up to 1080p/30fps. If you want to record any higher than that, you might need either an SSD or 2 HDDs in Raid 0, depending on what resolution, frame rate or codec will be used.

Here is a picture of the tab, and my settings (using 2 Western-Digital Caviar Blue drives in Raid 0)




2. Movie Settings:

The codec that I recommend is the x264 VFW codec. It's the fastest one out there and produces basically the same quality as any other. Now to be clear, THERE ARE other codecs that can produce a better image quality, but after encoding they all look more or less identical to the naked eye, so x264 give you the best "bang for you buck" so to speak.

Here are the recommended settings and a download link for the x264 codec:


http://sourceforge.net/projects/x264vfw/files/x264vfw/38_2274bm_36885/x264vfw_38_2274bm_36885.exe/download

Now onto the tab itself.



The frame rate should be as high as you can record in general. Usually, anything at or over 25 FPS is considered acceptable, depending on the game. Remember, higher frame rates mean more frames and that means more HDD space and speed is required. For instance in one of my tests, recording at 1080p/30fps requires a bandwidth of ~25 MB/s for both audio and video.

Now here is a HDD speed test using HD Tune on my OS HDD (WD Caviar Blue):


As you can see, even with some activity, I can still reach 88 MB/s easily. So with these settings, you can achieve 1080p/60fps without too much hassle from just a HDD speed perspective.
Also the fps and resolution depend on your other hardware capabilities such as CPU frequency and core number, GPU architecture-clock frequency-memory frequency-memory size, etc. Best thing to do is to just experiment with your settings both in-game and in Dxtory till you achieve an acceptable quality.

As for the rest of the settings in this tab, just leave them as shown in the image.


3. Audio Settings:

Just select your default audio device, use the PCM codec and PCM 48000 Hz 24bit Stereo Fromat.




4. Advanced Settings:

In this tab there are only 3 setting That you should be playing with, the rest should be left untouched.



Synchronous Surface Lock and Wait for Available Buffer both have to do with way the video gets transmitted from the GPU memory buffer to the recording. In some games the video data is not transmitted fast enough to the application so not all the frames will be recorded. When recording you will see in your top left corner the actual Game FPS and the recording FPS. If, for instance, you set Dxtory to record at 30 FPS but your recording is fluctuating under that, even if the game FPS is higher than 30, then this is as situation where the memory data is not transmitted fast enough. In this case I recommend enabling "Synchronous Surface Lock" and see if that fixes the issue. If not, then disable "Synchronous Surface Lock" and enable "Wait for Available Buffer". If this also doesn't work, then enable both of them and that should do it.

WARNING: Enabling any or both of these setting will severely reduce your FPS, so only use them when you have the issue described above. In general, try to record without them and again, ONLY ENABLE WHEN YOU HAVE ISSUES!

Also, I recommend setting the Processing Threads to the number of Cores/Threads your CPU has.


5. Conclusion:

So that's about it. These are just some general settings for those who are just starting to record and need a simple guide to start recording their runs at an acceptable quality.

Here are some sample encodes using the SDA standards as well as the source file for the encodes using the settings mentioned above:
https://mega.co.nz/#F!d8BmwChD!o7jeyCO2lO1KYdTaZ4jq8Q

I can also do a more comprehensive video tutorial featuring all of the features that Dxtory has to offer and how to use them properly.

If that might interest you, drop a reply below. Also, if you have any additional questions or suggestions, please reply.

And again, thank you to the SDA Community for making this forum such and awesome place Cheesy


And here is the video that i mentioned about streaming to Twitch using Dxtory and OBS:

Thread title:  
A Serious Noob
Interesting thread you have! I've been using bandicam to record my pc gameplays. I've been hearing that dxtory is a preferred program over fraps. I might give this a try!
Edit history:
TheVampire: 2014-03-23 09:31:36 am
I recommend you download the encode samples from the link provided just to see the quality difference between bandicam and dxtory.

PS: Sorry for the music in the background. Forgot about that while recording :))
Edit history:
DeMoNFLiP84: 2014-03-23 11:22:08 am
DeMoNFLiP84: 2014-03-23 11:18:21 am
A Serious Noob
For whatever reason Yua keeps force closing when I'm trying to encode Dxtory Recorded AVI Files. I even restarted my laptop to see the same outcome! Maybe because I'm using a Dxtory trail?

Anyway I'm trying to do a comparisons video between Bandicam and Dxtory using Yua to encode videos. Here's one of them.

I can see Dxtory is a good program to record PC Gameplay as expected. I'm still playing around with the settings and it's stability. 

Edit history:
TheVampire: 2014-03-23 11:24:30 am
Yep, quality looks very good. I'm glad this tutorial helped.
Edit history:
DeMoNFLiP84: 2014-03-23 11:30:54 am
A Serious Noob
Dxtory for me seems to be stable with synchronize video FPS checked on and was capped at 30 frames per second without seeing noticable frame drops.

Quote from TheVampire:
Yep, quality looks very good. I'm glad this tutorial helped.


The attached file was recorded with Bandicam by the way.
Edit history:
TheVampire: 2014-03-23 11:48:03 am
Well, it still looks good :))

PS: Just tested the trial version or bandicam and it looks pretty good. For basic recording it's right up there, but Dxtory offers many more options and features. If I have time next week I will do that video tutorial showcasing all the features and how to use them.

But for straight up recording, bandicam is a viable option.
Edit history:
DeMoNFLiP84: 2014-03-23 12:13:58 pm
DeMoNFLiP84: 2014-03-23 12:12:09 pm
A Serious Noob
Well of course, I only use Bandicam for casual play and screen recordings. Bandicam does have it's limitations in capturing footage. I wouldn't recommend Bandicam as a reliable tool let alone as acceptable in SDA standards unless this is the only option.

Dxtory and Fraps or even any type of capture card with a good pc system is what I rather use instead if I ever submit a video to SDA.
Edit history:
TheVampire: 2014-03-23 12:52:11 pm
Hmm, actually, bandicam is pretty good. Just did a test in CS:GO again, but this time with 60fps, just to test the program capabilities. Apparently the only codec that i can record with is YV12. It's the only one that allows a uncompressed video stream while achieving 60 fps. But the bitrate is very high, around 180 MB/s . Fortunently i have the capability of recording this but most can't. Also, Using bandicam in conjuncture with x264 vfw gives some strange result. Anything under 30 fps is good. Anything over lags like crazy.
Plus there are some more instabilities with the application. On a few occasions it froze up my entire PC and i needed to log off and on to use my PC again. Very strange.

In any case here is a recording using bandicam for those who want to know:
Codec used: YV12 @ 60 FPS
Encoded using Handbrake @ SDA XQ specifications

https://mega.co.nz/#!o442UbCJ!X3zpPavjqprhE-sGcZ6QHNm58dmrN6HOW9bj7SBbyZg
A Serious Noob
Makes me want to play CS 1.6 again lol.

Video looks good even at 60fps! 30fps is also acceptable.

I run bandicam on default. I haven't really messed with the settings at all. I might want to test it on my system now.
A Serious Noob
Here is a Dxtory Video Test using the codec and settings suggested in this thread. Please disregard the watermark since I'm using a trial.

I'm going to stream a game right now.

Any particular reason for PCM 48000 Hz 24bit vs 16 bit?
Kinda.

First, 48 KHz because maybe 1% of all the people that will see and hear the video might have adequate hardware and headphones to distinguish anything over this frequency.

And second, 24 bit depth gives you a higher dynamic audio range so you can record from the most quiet sounds to the loudest bangs. Now this also depends on the source audio from the game, if it's also 24bit or not. And it also give you a better audio quality after encoding.
PS: Remember to also set your you sound card to 24 bit 48000 Hz.


This is a very subjective subject but that's just my personal opinion.
Edit history:
TheVampire: 2014-03-23 06:01:58 pm
TheVampire: 2014-03-23 06:01:31 pm
I have a new discovery to add.

While doing some more tests tonight, using the x264 codec the maximum you can record is 1080p @ 30 FPS without any issues. For some reason, recording at 60 FPS at this resolution x264 lags like crazy. If you use another more lossless codec like YV12, it works just fine but the file size increases like crazy. YV12 @ 60 FPS at this resolution records like 10GB per 1 minute of video. So if you have the space and at-least a raid 0 with 2 HDDs this seems to be the only viable option.

In conclusion if you are tight on space but still want to record at a decent quality, only use x264 with 1080p@30fps max.
Edit history:
ballofsnow: 2014-03-23 06:10:41 pm
Is that a software/codec limitation, or computer specs limitation? Are you on dual monitor? Can try monitoring cpu/gpu/hdd usage somehow while recording, see if you're getting bottlenecked.
I think it's a codec limitation. I already did all the things you mentioned and also as mentioned previously, I can record 1080p60fps with no issues using YV12 which is a much more demanding codec.
Demanding on the HDD perhaps, not so much the cpu. That's got to be some crazy Mbps for the yv12 though at 1080p60.
Here are some screenshots

1: x264 @ 60fps


2: x264 @ 30fps


3: YV12 @ 60 fps
x264 is definitely pinning the CPU close to the max in both 30fps and 60fps, but it's not 100%. The fluctuation goes somewhere around 85%-95%.
Cool. In any case you'd use whatever works for you. Some good info here.
Yeah different settings for different hardware but as a general rule for most people, don't go over 1080p @ 30 FPS while using dxtory with x264 VFW.
thethrillness.blogspot.com
I don't know what CPU you have but 1080p60 with x264vfw isn't that taxing on CPU (especially if you are defaulting to 250 for i frames). Granted I only tested this with consoles so maybe also playing a PC game is enough to cause trouble.

I have noticed that needing zero latency really messes with compression but unfortunately we do need this to keep audio/video in sync. What you can do is untick Fast Decode. I'm unsure of what it does but it will hurt compression efficiency.

Also really debatable but you might want to offer a secondary x264vfw configuration that uses a really low CRF value (like 10) or something. That will reduce the bit rate by like more than half and have an imperceptible loss.
Iha paska
1080p60 heaviness depends a lot on the material. I often end up encoding demoscene prods that have crazy 1-frame flicker and general codec poison due to having tons of tiny detail with high contrast and saturation. You could almost call it a worst case scenario sometimes.

I actually sometimes ran in to issues even when playing those back on a overclocked 2500K with 4x1tb raid0 array driving the content Cheesy
So yeah, I would still respect 1080p60. A lot of the current console stuff is on the lighter side.

Anyway, nice post. should be useful for a bunch of people.
Right now I am at work so I can't reply, but when I come home I'll do some more investigations as to why this happens.
And i'm back with some more results.

Quote from TheThrillness:
I don't know what CPU you have but 1080p60 with x264vfw isn't that taxing on CPU (especially if you are defaulting to 250 for i frames). Granted I only tested this with consoles so maybe also playing a PC game is enough to cause trouble.

I have noticed that needing zero latency really messes with compression but unfortunately we do need this to keep audio/video in sync. What you can do is untick Fast Decode. I'm unsure of what it does but it will hurt compression efficiency.

Also really debatable but you might want to offer a secondary x264vfw configuration that uses a really low CRF value (like 10) or something. That will reduce the bit rate by like more than half and have an imperceptible loss.


First off, if you are recording gameplay from a console that means that you are using a capture card. Most modern capture cards have a h264 encoder chips on the card itself to enable real-time capture and encoding. Recording the screen directly from a video card is a completely different story. To summarize it, your video card renders the images from the game and displays it on you monitor in a uncompressed RGB stream. What programs like Dxtory do is that they hijack the video data from the GPU via the PCI Bus, creates a copy of the stream and transfer it to your ram, where it gets encoded via the CPU to whatever codec you choose. Then the encoded file get's stored on your HDD.

The problems basically appear in 2 places:

1: The CPU. Depending on what type of encoding you selected, the cpu might not keep up with the encoding besides the OS and game and other applications that are running. Selecting a truly lossless format like RGB24 or a small encode like YV12 gives you the best CPU performance. x264 roughly encodes the stream about 5x to 10x from the original size even in lossless mode, that's why the CPU is the clear bottleneck. To encode a game at 1080p60fps using x264, i imagine you would need something like a Intel 4-core cpu with hyper-threading or a AMD 8-core cpu.

2: Storage space and speed: Recording a game in 1080p60fps using a direct RGB copy is not that easy either but it can be done, the only issue being the video stream size. You would need a minimum of 3 HDDs in raid0 just to keep up.

Also as a side-note, i'm currently checking a new lossless codec that seems to be promising. More info as i finish my testing.