0001165: Odd symbols when using \t and \r make it impossible to use Timidity++

Notes
(0005309) unknownna (updater) 2012-11-04 08:01 edited on: 2012-11-04 08:04	You can also use "\c", "\n" and "\x".

(0018694) Edward-san (developer) 2017-11-01 01:14	Hold on. Does it happen with GZDoom 1.8.6? If yes, how about latest GZDoom (3.2.1)?

(0018728) Leonard (developer) 2017-11-02 14:47	It doesn't, I checked. I already know what's going on here, this is due to a really dumb difference between Zandronum and GZDoom.

(0018922) Wololo (reporter) 2017-11-27 12:04 edited on: 2017-11-27 12:07	You shouldn't use the "old" method that relies on ancient special compilation of timidity.exe, it's borderline broken, creates cracking sounds on midi track start/stop, random instrument distortions and other unpleasant effects. What you should do is get Timidity++ CVS version from here 'https://ja.osdn.net/projects/twsynth/releases/36408 [^]' This will install Timidity++ with standalone windows player AND a timidity driver, configuration is simple, you put your timidity.cfg into C:\WINDOWS, do a single reboot after installing and you should have Timidity Driver listed in your Zandro sound options, just like I've got it - 'https://i.imgur.com/mCNGnDL.jpg [^]' Now you can enjoy the Timidity++ sound free from all the sound glitches. Other games can use it as well. As a bonus note, there is a newer CVS version 2.14.0 but it's served without installer, after you install the one from previous link you can use just slap in those files as upgrade if you want to 'https://sourceforge.net/projects/timidity/files/TiMidity%2B%2B/TiMidity%2B%2B-CVS/ [^]' I suppose that will require replacing timiditydrv.dll in Windows\System32 [in case of 32bit Windows] or Windows\SysWOW64 folder [64bit Windows], which may require more advanced steps to update it [unregistering and re-registering .dll via CMD -> cd c:\windows\syswow64 -> regsvr32.exe -u timiditydrv.dll -> delete the old .dll and put in the new .dll in the syswow64 folder -> regsvr32.exe timiditydrv.dll] so consider the manual update as a poweruser option.

(0018923) Edward-san (developer) 2017-11-27 13:41 edited on: 2017-11-27 13:41	Quote You shouldn't use the "old" method that relies on ancient special compilation of timidity.exe, it's borderline broken You can bring this info in the ZDoom forum, since this is something for the developers over there about it. This ticket has nothing to do with Timidity itself. In any case, there's a workaround: just edit the config file and write the path in the timidity_exe option entry.

(0018924) Wololo (reporter) 2017-11-27 14:04	Quote You can bring this info in the ZDoom forum, since this is something for the developers over there about it. Graf doesn't really care, especially when their "special timidity.exe version" is considered legacy code leftover before audio revamp that happened at some point during 2.X series. I think there was even discussion in this regard at old skulltag forum with general consensus being "just don't use zdoom timidity.exe". Other places like doomworld or odamex wiki tell you straight how to set up timidity driver, so in this case someone should rather update zdoom wiki instead with timidity driver method. Anyway I'm gonna link them in as those two are most comprehensive guides how to set up Timidity++. 'https://www.doomworld.com/vb/doom-general/51868-how-to-install-and-set-up-timidity-driver/ [^]' 'https://odamex.net/wiki/Timidity#Install_the_Timidity_driver [^]'

(0018964) Leonard (developer) 2017-12-15 01:28	PR.

(0018966) Leonard (developer) 2017-12-17 22:09	This was merged.

(0020039) Ivan (reporter) 2018-10-08 21:28 edited on: 2018-10-08 21:28	Can confirm the console portion of using "\r" or "\t" is fixed in Zandronum 3.1-alpha-180901-1533.

(0021258) Ru5tK1ng (updater) 2020-04-11 00:22	Marking as resolved based on Ivan's testing report.

This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why.
Supporters:	No one explicitly supports this issue yet.
Opponents:	No one explicitly opposes this issue yet.

Issue History
Date Modified	Username	Field	Change
2012-11-04 03:59	Tosen	New Issue
2012-11-04 08:01	unknownna	Note Added: 0005309
2012-11-04 08:02	unknownna	Status	new => confirmed
2012-11-04 08:04	unknownna	Note Edited: 0005309	View Revisions
2012-11-04 09:29	unknownna	Severity	minor => major
2017-11-01 00:17	Leonard	Assigned To	=> Leonard
2017-11-01 00:17	Leonard	Status	confirmed => assigned
2017-11-01 01:14	Edward-san	Note Added: 0018694
2017-11-01 01:14	Edward-san	Status	assigned => feedback
2017-11-02 14:47	Leonard	Note Added: 0018728
2017-11-02 14:47	Leonard	Status	feedback => assigned
2017-11-12 22:18	Dusk	Relationship added	related to 0001564
2017-11-26 18:08	Leonard	Target Version	=> 3.1
2017-11-27 12:04	Wololo	Note Added: 0018922
2017-11-27 12:07	Wololo	Note Edited: 0018922	View Revisions
2017-11-27 13:41	Edward-san	Note Added: 0018923
2017-11-27 13:41	Edward-san	Note Edited: 0018923	View Revisions
2017-11-27 14:04	Wololo	Note Added: 0018924
2017-12-15 01:28	Leonard	Note Added: 0018964
2017-12-15 01:28	Leonard	Status	assigned => needs review
2017-12-17 22:09	Leonard	Note Added: 0018966
2017-12-17 22:09	Leonard	Status	needs review => needs testing
2018-10-08 21:28	Ivan	Note Added: 0020039
2018-10-08 21:28	Ivan	Note Edited: 0020039	View Revisions
2020-04-11 00:22	Ru5tK1ng	Note Added: 0021258
2020-04-11 00:22	Ru5tK1ng	Status	needs testing => resolved
2020-04-11 00:22	Ru5tK1ng	Resolution	open => fixed
2020-04-11 00:22	Ru5tK1ng	Fixed in Version	=> 3.1