You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are situations where one might not want to run in single channel mode (originally this change was made to save bandwidth)
Clients might want to connect to non-Jamtrip servers that are not single-channel (-n 1). This should be supported in the manual configuration, and the patching should work as expected.
The text was updated successfully, but these errors were encountered:
in the meantime 0.1.3 has reverted to the more common 2-channel mode. Best to keep things more with the defaults, and the bandwidth impact seemed negligible in real-world testing
There are situations where one might not want to run in single channel mode (originally this change was made to save bandwidth)
Clients might want to connect to non-Jamtrip servers that are not single-channel (-n 1). This should be supported in the manual configuration, and the patching should work as expected.
The text was updated successfully, but these errors were encountered: