|DTXMania 099 series, and DTXCreator: (099g(191022))||2019-10-23 00:21|
|DTXMania 100 series, and DTXCreator: (118(200510) and 035(191001))||2020-05-10 00:00|
By default, DTXMania's configuration is for "running (only) DTXMania fast",
So, in the broadcasting situation... "DTXMania and Screen-capturing work at the same time"...the PC doesn't use enough performance to screen-capture, and the DTXMania itself's performance may also become bad.
Here is some settings to reduce DTXMania performance (to improve screen-capture performance). (I believe it will make good performance for broadcasting usage.)
It is the wait time (milliseconds) of each screen-refresh, when DTXMania window is NOT focused. It may be useful for auto-playing screen-capture/broadcasting.
The value must be 0 or bigger. By default, it is 0. 0 means "Every screen-refresh, DTXMania will release CPU-time to other apps". After releasing CPU time, it needs unknown time for DTXMania to use CPU-time again. If you set it to 2, "Every screen-refresh, DTXMania will release CPU-time to other apps, at least 2ms".
For broadcasting, 1-10ms is preferred.
It is the wait time (milliseconds) of each screen-refresh, when DTXMania window IS FOCUSED. It may be useful for self-playing screen-capture/broadcasting.
The value must be -1 or bigger. (Although, -1 can't use to BackSleep, but SleepTimePerFrame can use.) By default, it is -1.
The behavior for 0,1,2,... are the same as BackSleep. If you set -1, DTXMania doesn't release CPU-time at every screen-refresh.
For broadcasting, 1-10ms is preferred. (Same as BackSleep)
It means "how many playback multiple sounds in the lane" (maximum number of multiple sounds). 1-8 can be set. By default, it is 2.
The value is effective for Drums Lanes. For Guitar/Bass, it is 2 or 1 (when PolyphonicSounds=1, it is 1. Otherwise, it is 2) For BGM/SE, it is always 1.
The value become bigger, the sound become richer (but CPU load also become bigger).
For broadcasting, it is better to set 2 or 1.
If WASAPI(Exclusive) or ASIO is used, DTXMania exclusively uses the sound device and other app can't use sound. So, generally, WASAPI (Exclusive) or ASIO can't be used for broadcasting. (But there is some special way to use it. If you know plz let me know...I'll introduce it here)
Bigger sound buffer size will make lower CPU load. However, too-big buufer size become bad result...it must be up to 100ms.
In case you use DSound, you don't have to take special care for broadcasting. The bad thing is big sound output lag, but it may be able to reduce by using REAL.