zdoom/fluidsynth
0
0
Fork 0
mirror of https://github.com/ZDoom/fluidsynth.git synced 2024-12-11 05:11:33 +00:00
Code Issues Projects Releases Packages Wiki Activity

fix wording

Browse source
This commit is contained in:
Tom M 2017-09-01 17:35:11 +02:00 committed by GitHub
parent 597667b9c0
commit da14a19785
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
fluidsynth/doc/fluidsynth-v11-devdoc.txt
View file

@ -528,7 +528,7 @@ fluid_synth_nwrite_float or fluid_synth_process in parallel with the
rest of the calls, and it won't be blocked by time intensive calls to rest of the calls, and it won't be blocked by time intensive calls to
the synth. Turn it off if throughput is more important than latency, e g the synth. Turn it off if throughput is more important than latency, e g
in rendering-to-file scenarios where underruns is not an issue. in rendering-to-file scenarios where underruns is not an issue.
<br /><br /><strong>Deprecated:</strong><br />As of 1.1.7 this option is deprecated. The current implementation relies on the fact that this option is set to TRUE to correctly render audio. Also in fact it enforces thread safety for rvoice_mixer instead of enabling parallel-render, which is mainly controlled by "synth.cpu-cores". <br /><br /><strong>Deprecated:</strong><br />As of 1.1.7 this option is deprecated. This option enforces thread safety for rvoice_mixer, which causes rvoice_events to be queued internally. The current implementation relies on the fact that this option is set to TRUE to correctly render any amount of requested audio. Also calling fluid_synth_write_* in parallel is not considered to be a use-case. It would cause undefined audio output, as it would be unpredictable for the user which rvoice_events specifically would be dispatched to which fluid_synth_write_* call.
</td> </td>
</tr> </tr>