Dxtory recording setup help.

ragepage26

Estimable
Aug 18, 2015
3
0
4,510
0
Hello people! I just started making YouTube videos and am looking for some help setting up Dxtory for optimal performance. My computer is a Intel I7 5820k OC 4.2, Asus GTX 970 strix, 16gb ddr4 2133 mhz ram (the ram says 2800Mhz, I just did not do xmp).

I am playing games like GTAV, Minecraft, League of Legends, Smite, Final Fantasy VII, Rocket League, Etc. This program has a lot of setting and I want to make sure I can make high quality recordings. I have hoping to record at 1080p 60fps.

My main drive which the program will run off from (not record to) is a 500gb evo 850 ssd. It will be recording to either a 3tb WD black drive or an external 2tb WD passport external HHD (using 3.0 usb).

My cpu has 6 cores 12 threads and is overclocked to 4.2Ghz. I see there are settings for cpu control so any insight on how many threads should be used and how high the priority should be would be nice.

I already noticed that if I record, the video will be black unless I play it in Adobe Premiere pro. Anyone know why?

I put the Lagarith Lossless Codec in Dxtory. I was wondering what settings I should use for that? like RGB, RGBA, Yuy2, Yv12. I assume I should pick multi threading.

The enviroment shows both of my monitors, I will be recording on the 144hz if that helps.


I think I covered all my bases. Any help will be much appreciated.

I did the environment information so here is that:

[Dxtory]
Version: 2.0.132
UID: 1c458b70-ee2e-495c-b6ad-88417cfcff71

[Dxtory Files]
InstallPath: C:\Program Files (x86)\ExKode\Dxtory2.0
amd_ags.dll Size: 271,872 bytes Ver: SHA1: 44ab4f74637e23ca586580c6d746974e86da98e6
AppNames.txt Size: 1,047 bytes SHA1: 40cd39ab435dbcb3d44eba72b737a05b9a14410b
AudioStreamSplitter.exe Size: 38,432 bytes Ver: 2.0.0.2 SHA1: 5195bb906a508f9e7175f3c9c7d62c6c76f8217c
AudioStreamSplitter_ja.txt Size: 134 bytes SHA1: 489a5264d73a47edcce7c92edb131cf63e5e5709
AVIFix.exe Size: 72,192 bytes Ver: 2.0.0.131 SHA1: 8743067b975002d014008cfb0db363dfb606c375
AVIFix_ja.txt Size: 288 bytes SHA1: 9cab20780686687b84f604c77c73aaae3fd8126d
AVIMux.exe Size: 166,432 bytes Ver: 2.0.0.131 SHA1: 434d85edc5d4bb77c64ca703f9790062cc87a117
AVIMuxCore.dll Size: 199,200 bytes Ver: 2.0.0.130 SHA1: 53661b27f6f6f9f3e8316dca872fd4b01da93e49
AVIMux_ja.txt Size: 1,701 bytes SHA1: fa240715d701f450bb95377aa8517a252329b619
CryptData.pup Size: 84 bytes SHA1: cf9d724807f965d372da4d168bebd78c5258d6ae
Dxtory.exe Size: 589,376 bytes Ver: 2.0.0.132 SHA1: f44d42f1bed9391c6b83bf46a0604de3ac0c55bf
Dxtory64.exe Size: 130,112 bytes Ver: 2.0.0.132 SHA1: 4cce60b896a04515767435c7fd29feefed3c1aac
DxtoryCore.dll Size: 7,136,288 bytes Ver: 2.0.0.132 SHA1: 7750f6d4888d19c4f02e7b30e1a6b19a3fa619d4
DxtoryCore64.dll Size: 6,807,104 bytes Ver: 2.0.0.132 SHA1: 302915f53071dc592ab0549d26611b7edf71c164
DxtoryHK.dll Size: 174,656 bytes Ver: 2.0.0.132 SHA1: 56a2c76428ed5f43075cc0c788534f81dc557eff
DxtoryHK64.dll Size: 186,944 bytes Ver: 2.0.0.132 SHA1: cba5e8fd83b8939212fabf45d4485cbcea5a49d1
DxtoryMM.dll Size: 1,125,952 bytes Ver: 2.0.0.132 SHA1: b0b6fcc47b6b3f326de582975b269d57c2dd0594
DxtoryMM64.dll Size: 1,139,776 bytes Ver: 2.0.0.132 SHA1: 4cc91746487d863e2eea7a572c498c7eddf83817
DxtoryVideo.dll Size: 434,720 bytes Ver: 2.0.0.130 SHA1: 8d1393e8ce7cfd4b5e2a3481308b8410c3730ab7
DxtoryVideo64.dll Size: 473,120 bytes Ver: 2.0.0.130 SHA1: f2c63192dfe94db290be10a9d8b66c7a04949ae3
DxtoryVideo64_Install.bat Size: 28 bytes SHA1: 308ae1e37b5e28ff7134beb319faad48280068b0
DxtoryVideo64_Uninstall.bat Size: 31 bytes SHA1: 3fbf8d3c3a5b375eda07e47a64534b91c8df5139
DxtoryVideoSetting.exe Size: 129,568 bytes Ver: 2.0.0.130 SHA1: ee440e846cfeec2acb4a88f81f589e00c34e825e
DxtoryVideoSetting_ja.txt Size: 1,675 bytes SHA1: e532f36bd5ac6255659d240180637484661f0c83
DxtoryVideo_Install.bat Size: 26 bytes SHA1: b00e69772cc1cae9e86fe2b70ca290c488723fd7
DxtoryVideo_Uninstall.bat Size: 29 bytes SHA1: 0b0202cbc7fba373f42e1a6916fc2ad01edaa627
Dxtory_ja.txt Size: 18,461 bytes SHA1: 093689676cf8ca51b99c97253e5187ded508838a
EULA_en.txt Size: 1,356 bytes SHA1: 340c6b3425ab78d83c6a8bd344b6cc58d152ce8f
EULA_ja.txt Size: 1,814 bytes SHA1: cded0d38ec6a1cb0e86bc264496deaa28082cb51
filelist.txt Size: 223 bytes SHA1: cc6b9d0fd453138907b8cb4a3386472b33289135
filelist64.txt Size: 231 bytes SHA1: e0e277a441381a17c12e5e6deef1d9a0383667cf
ignore_module_list.txt Size: 1,117 bytes SHA1: 9be129e61ec2d7d060fdb0d755c601af132cfa63
LicReg.dat Size: 10,305 bytes SHA1: f4340b7e28e30287486771d15b1bdb39b0a3ef0a
LicReg.exe Size: 96,816 bytes Ver: 2.0.0.4 SHA1: 0d236ac1394a97d35a67c63ec15e45a80f87db5b
LicReg_ja.txt Size: 707 bytes SHA1: 981af64897276c22867952f4972d9c29c6ee35e7
RawCapConv.exe Size: 208,928 bytes Ver: 2.0.0.131 SHA1: 32b6ec5d2f6649df4a47aedc476965433a8bdec4
RawCapConv_ja.txt Size: 1,869 bytes SHA1: 12086976f07abfc8d435abeee6c450c3cb2b07cd
RCStream.dll Size: 164,352 bytes Ver: 1.0.0.76 SHA1: 31266452f142cd7c856384945ffc410b2c9c8be9
readme.txt Size: 1,322 bytes SHA1: f8b7e31de7927309f7f3e03936374837906a94d9
Src16x10_Dest4x3.png Size: 40,081 bytes SHA1: 3b4f6332b8b3129ee351a9c96a9c4ac7f6f7a4cd
Src16x9_Dest4x3.png Size: 40,179 bytes SHA1: fcec824f4e95f7becf65bbabcc1a99c1470b99a1
unins000.dat Size: 23,028 bytes SHA1: f7fbfc2b0bbc7b93d76bc9724a4f1f9f3aa22263
unins000.exe Size: 1,199,680 bytes Ver: 51.1052.0.0 SHA1: ca5f9528690d5300428d7bd64fb070b4fcf68110
unins000.msg Size: 22,701 bytes SHA1: ab7961d64f8b22503c9c7ca4b335fa539b0278a3
UpdateChecker.exe Size: 93,696 bytes Ver: 2.0.0.0 SHA1: 221bd3663f4393b368ebf74d1a892f9379ddbe44
UpdateChecker.ini Size: 238 bytes SHA1: 796da23b4a505bf2ef370dc271d1a80585dff6e2
UpdateChecker_ja.txt Size: 190 bytes SHA1: 969913786a3497f3e448572f7810ee9814314928
DxtoryCodec.dll 64bit Size: 2,606,144 bytes Ver: 2.0.0.132 SHA1: 7ef69696fe270d8bf353ead32bd58681ee61e5fe
DxtoryCodec.dll 32bit Size: 2,499,648 bytes Ver: 2.0.0.132 SHA1: cd610194e3ddceefa04bc0f28a5f2139fee0d615

[System Information]
CPU: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
CPU Instruction Set: MMX SSE SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AVX AVX2 FMA3 AES
OS: Microsoft Windows 10 Home x64
OSVersion: 10.0.10240
OSLanguage: 1033
ServicePack:
Memory0: NODE 1 4,294,967,296 bytes
Memory1: NODE 1 4,294,967,296 bytes
Memory2: NODE 1 4,294,967,296 bytes
Memory3: NODE 1 4,294,967,296 bytes
TotalMemory: 17,179,869,184 bytes
Total Physical Memory: 17,070,211,072 bytes
Available Physical Memory: 14,490,525,696 bytes
Total Page File: 19,620,347,904 bytes
Available Page File: 16,348,450,816 bytes
Total Virtual Memory: 2,147,352,576 bytes
Available Virtual Memory: 1,714,659,328 bytes
PerformanceCounterFrequency: 3222655 (0x312C7F)
VideoCard: NVIDIA GeForce GTX 970 Memory: 4,293,918,720 Processor: GeForce GTX 970 DriverVer: 10.18.13.5560 DriverDate: 2015-08-05 20-00-00
Display0: 2560x1080 32bits 60Hz
Display1: 1920x1080 32bits 144Hz
SoundDevice: NVIDIA High Definition Audio Manufacturer: NVIDIA
SoundDevice: USB Audio Device Manufacturer: (Generic USB Audio)
SoundDevice: NVIDIA Virtual Audio Device (Wave Extensible) (WDM) Manufacturer: NVIDIA
SoundDevice: Realtek High Definition Audio Manufacturer: Realtek

[NVIDIA Info]
NVDriver: 355.60 r355_42
GPU0: GeForce GTX 970 Memory: 4096MB MemoryClock: 3505MHz BaseClock: 1114MHz BoostClock: 1253MHz

[Audio Device]
VG248-0 (NVIDIA High Definition Audio) - CoreAudioOut
Speakers (Yeti Stereo Microphone) - CoreAudioOut
LG ULTRAWIDE-4 (NVIDIA High Definition Audio) - CoreAudioOut
Realtek Digital Output (Realtek High Definition Audio) - CoreAudioOut
Microphone (Yeti Stereo Microphone) - CoreAudioIn, Volume 100

[Video Codec 64bit]
Intel IYUV codec FCC:i420
Intel IYUV codec FCC:iyuv
Lagarith Lossless Codec FCC:lags
Microsoft RLE FCC:mrle
Microsoft Video 1 FCC:msvc

[Video Codec 32bit]
Cinepak Codec by Radius FCC:cvid
Intel IYUV codec FCC:iyuv
Intel IYUV codec FCC:i420
Lagarith Lossless Codec FCC:lags
Microsoft RLE FCC:mrle
Microsoft Video 1 FCC:msvc

[Audio Codec]
Microsoft IMA ADPCM
MS-ADPCM
Microsoft CCITT G.711
Microsoft GSM 6.10
PCM
IEEE Float

[License Information]
License: Registered
Expire: Unlimited
LicVerify: c7b12b0aa542ac8ec9d137576d1095181cd51bfd

[Additional Information]
Dxtory_log.txt: Empty
ErrorLog.txt: Empty

[Global Setting]
OptionFlag=SharedJavaProfile

[Ignore List]

======================================================================

[Profile]
Name: Default
Path:

[Overlay]
Option: Right Top VidoeFPS WriteFileFPS RecordState
Color: Sleep FFFF0000, Active FF8700A6, Movie FFFFFF00, ScreenShot FF00FF00

[Folder]
x H: Speed: 90MB/sec Free: 1,968,494,829,568 Total: 2,000,228,970,496 Format: NTFS
SSFolder:

[HotKey]
MovieCapture: Alt + F9 (0x00080043)
PushToTalk: None
ScreenShotSingle: F11 (0x00000057)
ScreenShotRepeat: None
ScreenShotAuto: None
ToggleStatus: None
MovieCaptureFrame: None
ScreenShotCaptureFrame: None

[Movie]
Clipping:
ClipMargin: 0,0,0,0
ClipSize: 0,0
Scaling: Percent 100% 0x0
Codec: Lagarith Lossless Codec, Quality 10000, KeyFrameRate 15, DataRate 0, 64bit
FrameRate: 60
Output: File AVI
Option: SyncFPS

[Audio0]
Enabled: True
PushToTalk: False
Device: Microphone (Yeti Stereo Microphone)
Codec: PCM
Format: PCM 48000 Hz, 16 bit, Stereo

[ScreenShot]
Clipping:
ClipMargin: 0,0,0,0
ClipSize: 0,0
Scaling: Percent 100% 0x0
HighSpeedLimit: 0
RepeatInterval: 1000
Format: PNG
JpegQuality: 97
Option:

[Advanced]
DataProcessingOption:
HookOption:
ThreadCount: 1
ThreadMask: 0000000000000000
LimitedFPS: True
FPSLimit: 60
DelayHook: False
DelayHookTime: 5

======================================================================

[Profile]
Name: javaw.exe
Path: C:\Program Files (x86)\Minecraft\runtime\jre-x64\1.8.0_25\bin\javaw.exe

[LastUsingInformation]
DateTime: 2015/09/07 19:21:25
Version: 2.0.132
64bit Process
DeviceType: GL DX9
View0.Type=GL
View0.Version=4.5
View0.Size=1920x1080
View0.HWND=0x00170B9C
View0.WindowTitle=Minecraft 1.7.10
View0.ClassName=LWJGL

======================================================================
VerifyHash: a7412ae3d86eb7fbc63b2c6677732b667b479fb1
Modify message
 

aznricepuff

Honorable
Oct 17, 2013
38
0
10,610
12
I recommend using utvideo instead of lagarith: http://www.videohelp.com/software/Ut-Video-Codec-Suite

utvideo has less encoding overhead than lagarith, meaning you'll be able to encode at higher framerates.

Quick start guide to dxtory:
(for this I'll assume you will be using utvideo)

Movie Setting Tab

Video Codec (utvideo)

  • ■ Once you've installed the utvideo codec, you'll see a bunch of codecs in the dropdown menu named utvideo, both 64-bit and 32-bit. In general you'll want to use the 64-bit codecs unless you have compatibility issues.
    ■ I recommend using the YUV420 BT.709 VCM codec if you are not going to be doing a lot of filtering/compositing work on your recordings. If you are, then go with YUV422 BT.709 VCM.
Codec config

  • ■ Frame divide count: Set this to the number of simultaneous threads your CPU can run (12).
    ■ Optimize for compression ratio/decoding speed: self-explanatory. Neither makes a big difference in encoding speed.
    ■ Assume interlaced video: leave this unchecked.
Output

  • ■ 'File' vs 'DirectShow': should be self-explanatory
    ■ File Format: most of the time you will want to choose AVI. Use RawCap if and only if you want to dxtory to split your files across 2 or more hard drives (increases effective write speed much like a RAID0 setup would).
Option

  • ■ Synchronize Video FPS: Check this to sync your game's framerate to the recording framerate. Unless you can always render at least 2x recording framerate, I highly recommend turning this on to avoid stuttering in your recordings.
Scaling

  • ■ Use the "Size" option instead of "Percent" - it's a lot simpler. Just input the resolution you want to record at (doesn't have to match the resolution you render the game at).
Audio Setting Tab

  • ■ For lossless audio, use either PCM or IEEE Float. If you are recording mono or stereo (2 channels), use PCM since Float requires a higher bitrate but won't give you any increased quality. If you are recording 2.1/5.1/7.1, then you have to use IEEE Float, since PCM doesn't support those channel layouts.
    ■ In terms of sample rate (both PCM and float) and bit-depth (PCM only), you will want to match those to your audio sources to avoid resampling. If you don't know how/don't care enough to do this, then use 48000Hz and 24-bit. This will be the optimal setting 90% of the time.
Advanced Setting Tab

  • ■ Multi-GPU stable processing: Turn this on if and only if you have an SLI/Crossfire setup. Your environment log shows you don't, so leave this off.
    ■ Force CPU processing: Usually you will want to leave this off.
    ■ Synchronous Surface Lock/Wait for Available Buffer: Both of these options will reduce frame drops (where your video seems to skip a frame) but will decrease your maximum achievable recording framerate. I recommend you leave both on unless you are having trouble recording at your desired framerate.
    ■ Delay hook: Enable this to improve compatibility with other programs that use DXAPI hooks (steam overlay, origin overlay, etc.). You may also need to increase the delay from the default value of 5 seconds to get it to work.
    ■ Processing Threads: It's usually OK to leave these settings at their default values.
Misc.

  • ■ "Use Default Setting": This can be found at the top of almost every tab. Basically, if left checked, it will load up the settings of the default profile and force the current profile to use those settings. Moreover, if it's checked and you change settings, you are changing the settings for the default profile, even if the current profile is not the default profile. Uncheck it if you want to load, view, and change the settings for the current profile only.
 

aznricepuff

Honorable
Oct 17, 2013
38
0
10,610
12
I recommend using utvideo instead of lagarith: http://www.videohelp.com/software/Ut-Video-Codec-Suite

utvideo has less encoding overhead than lagarith, meaning you'll be able to encode at higher framerates.

Quick start guide to dxtory:
(for this I'll assume you will be using utvideo)

Movie Setting Tab

Video Codec (utvideo)

  • ■ Once you've installed the utvideo codec, you'll see a bunch of codecs in the dropdown menu named utvideo, both 64-bit and 32-bit. In general you'll want to use the 64-bit codecs unless you have compatibility issues.
    ■ I recommend using the YUV420 BT.709 VCM codec if you are not going to be doing a lot of filtering/compositing work on your recordings. If you are, then go with YUV422 BT.709 VCM.
Codec config

  • ■ Frame divide count: Set this to the number of simultaneous threads your CPU can run (12).
    ■ Optimize for compression ratio/decoding speed: self-explanatory. Neither makes a big difference in encoding speed.
    ■ Assume interlaced video: leave this unchecked.
Output

  • ■ 'File' vs 'DirectShow': should be self-explanatory
    ■ File Format: most of the time you will want to choose AVI. Use RawCap if and only if you want to dxtory to split your files across 2 or more hard drives (increases effective write speed much like a RAID0 setup would).
Option

  • ■ Synchronize Video FPS: Check this to sync your game's framerate to the recording framerate. Unless you can always render at least 2x recording framerate, I highly recommend turning this on to avoid stuttering in your recordings.
Scaling

  • ■ Use the "Size" option instead of "Percent" - it's a lot simpler. Just input the resolution you want to record at (doesn't have to match the resolution you render the game at).
Audio Setting Tab

  • ■ For lossless audio, use either PCM or IEEE Float. If you are recording mono or stereo (2 channels), use PCM since Float requires a higher bitrate but won't give you any increased quality. If you are recording 2.1/5.1/7.1, then you have to use IEEE Float, since PCM doesn't support those channel layouts.
    ■ In terms of sample rate (both PCM and float) and bit-depth (PCM only), you will want to match those to your audio sources to avoid resampling. If you don't know how/don't care enough to do this, then use 48000Hz and 24-bit. This will be the optimal setting 90% of the time.
Advanced Setting Tab

  • ■ Multi-GPU stable processing: Turn this on if and only if you have an SLI/Crossfire setup. Your environment log shows you don't, so leave this off.
    ■ Force CPU processing: Usually you will want to leave this off.
    ■ Synchronous Surface Lock/Wait for Available Buffer: Both of these options will reduce frame drops (where your video seems to skip a frame) but will decrease your maximum achievable recording framerate. I recommend you leave both on unless you are having trouble recording at your desired framerate.
    ■ Delay hook: Enable this to improve compatibility with other programs that use DXAPI hooks (steam overlay, origin overlay, etc.). You may also need to increase the delay from the default value of 5 seconds to get it to work.
    ■ Processing Threads: It's usually OK to leave these settings at their default values.
Misc.

  • ■ "Use Default Setting": This can be found at the top of almost every tab. Basically, if left checked, it will load up the settings of the default profile and force the current profile to use those settings. Moreover, if it's checked and you change settings, you are changing the settings for the default profile, even if the current profile is not the default profile. Uncheck it if you want to load, view, and change the settings for the current profile only.
 
Thread starter Similar threads Forum Replies Date
I Apps General Discussion 1
S Apps General Discussion 3
W Apps General Discussion 1
M Apps General Discussion 6
D Apps General Discussion 2
U Apps General Discussion 1
L Apps General Discussion 1
G Apps General Discussion 2
T Apps General Discussion 2
A Apps General Discussion 5
C Apps General Discussion 1
N Apps General Discussion 1
B Apps General Discussion 4
K Apps General Discussion 7
X Apps General Discussion 7
vFMXv Apps General Discussion 1
I Apps General Discussion 2
kassuba39 Apps General Discussion 1
S Apps General Discussion 3
Z Apps General Discussion 3

ASK THE COMMUNITY