Page 1 of 3

Bug found with OpenMSX perhaps. Input required.

Posted: 18 Apr 2010 15:31
by Tinytimrob
Hello,

I was wondering if anyone could help me. I have recently compiled OpenTTD r19669 on Windows 7 and downloaded the latest nightlies for OpenGFX/SFX/MSX.

Specifically since this bug concerns OpenMSX I have nightly r49.

If I play the regular game using original_windows music selection for the entire time then the sound is fine (other than a long pause at the end of track 9, "Can't get there from here" which I presume everyone already knows about because it's been there for several years now at least). HOWEVER if I play the game using OpenMSX, after a few tracks the music starts to sound odd. If I switch back to original_windows after using OpenMSX I get the same problem (odd sounding music). It's quite hard to describe so I did an in-game mic recording of a few tracks and uploaded it to my site. Apologies for the poor quality and the sound effects present in the recording.

http://media.thegineverblock.com/opentt ... td-bug.mp3

As you can hear if you listen to the MP3, the music sounds a little odd (a few instruments not sounding right, and pitch bends screwed up). If you don't really want to listen to the whole thing then the problem is most noticeable in the track which I believe is called 'Goss Groove' about 4:25 into the recording.

Since this recording includes a portion of the original windows soundtrack which is copyrighted I will remove it from my server once the problem is resolved :) I would avoid uploading it but it's a little difficult to hear what's going on without a recording...

I would like to know if anyone can reproduce this bug and perhaps suggest a potential solution.

Thanks in advance.

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 18 Apr 2010 15:39
by Kogut
Tinytimrob wrote:Specifically since this bug concerns OpenMSX I have nightly r49.
49? It is rather ancient. //Sorry, I thought about openttd nightly.

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 18 Apr 2010 15:42
by Tinytimrob
As far as I can see OpenMSX r49 is the latest revision dated 08-04-2010 21:14
http://dev.openttdcoop.org:81/projects/ ... repository

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 18 Apr 2010 16:25
by planetmaker
Tinytimrob wrote: Specifically since this bug concerns OpenMSX I have nightly r49.

http://media.thegineverblock.com/opentt ... td-bug.mp3
don't really want to listen to the whole thing then the problem is most noticeable in the track which I believe is called 'Goss Groove' about 4:25 into the recording.
Thanks for the report. Could you maybe look up again which song(s) is / are causing the problem? I don't have a song called "Goss Groove"... and I haven't yet identified the song by listening :-)

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 18 Apr 2010 16:34
by Tinytimrob
Goss Groove is an original TTD song, not from OpenMSX :)

It is just one of many tracks that glitch up after listening to OpenMSX for a while. Tracks from both the original_windows and OpenMSX music sets become glitched up. The problem is most noticeable on Goss Groove but it is not the only track which mucks up (most of them do)

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 18 Apr 2010 18:44
by Doorslammer
Wow, odd remix. :P

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 18 Apr 2010 20:12
by Tinytimrob
Indeed, it is most peculiar. I have had to resort to using Windows Media Player in order to listen to the tracks from OpenMSX so hopefully there will be a fix soon.

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 26 Jun 2010 17:38
by Samu
ahhhh..... I seee. Same problem, but the track is named Smooth Groove.

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 26 Jun 2010 19:24
by Tinytimrob
Indeed this problem is still not fixed!

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 28 Jun 2010 21:46
by Samu
Please check this topic to make sure it's the same problem.
(sorry for cross-posting)
http://www.tt-forums.net/viewtopic.php?f=32&t=48896

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 29 Jun 2010 17:20
by Tinytimrob
Confirmed. This is the same bug. The track "Smooth Groove" from OpenMSX does not appear to be what is causing the issue however. I removed the entry for Smooth Groove from the openmsx.obm file and the 'darkness' as you put it is still present.

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 29 Jun 2010 17:28
by planetmaker
Hm, so I replaced that song for no good reason? :-(

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 29 Jun 2010 17:55
by Samu
Tinytimrob wrote:Confirmed. This is the same bug. The track "Smooth Groove" from OpenMSX does not appear to be what is causing the issue however. I removed the entry for Smooth Groove from the openmsx.obm file and the 'darkness' as you put it is still present.
What's your sound card? Can you find out which track is doing it?

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 29 Jun 2010 17:58
by Samu
planetmaker wrote:Hm, so I replaced that song for no good reason? :-(
I appologize... :( But this seems to be a sound card driver problem after all.


-----
EDIT: hold on. I downloaded the mp3 file, I hear the OpenMSX tycoon theme, then the original tycoon theme and then Goss Groove which is part of the original_windows pack.

You say that after listening for a bit of OpenMSX the songs become distorted afterwards, no matter which pack you listen to, and the mp3 is already what you listen after that, right?

Well, same issue for me. I was able to find out the song that was causing the problem was Smooth Groove from OpenMSX, but you say it's not Smooth Groove. So, the Goss Groove is just merely an example? I got it now!

The problem still relies on OpenMSX pack then, can you try to find out which song is causing it?

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 29 Jun 2010 18:08
by Tinytimrob
I have a Realtek ALC888 onboard audio and the issue occurs with the default Microsoft GS Wavetable SW Synth MIDI driver that ships with every version of Windows.

I'll try and work out which track is causing the problem for me, since all tracks play fine on their own if they're the only item in the playlist.

In response to your "long gap in one of the tracks" problem, it's "Can't get me out of here" aka gm_tt10.gm - the fixed MIDI file is attached, but you'll have to update your .obm file with the new MD5 to prevent the game from flagging it as corrupt afterwards.

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 29 Jun 2010 18:20
by Tinytimrob
Listening to all tracks one by one now, I'll try to work out the buggy track for you :)

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 29 Jun 2010 18:36
by Samu
Tinytimrob wrote:I have a Realtek ALC888 onboard audio and the issue occurs with the default Microsoft GS Wavetable SW Synth MIDI driver that ships with every version of Windows.

I'll try and work out which track is causing the problem for me, since all tracks play fine on their own if they're the only item in the playlist.

In response to your "long gap in one of the tracks" problem, it's "Can't get me out of here" aka gm_tt10.gm - the fixed MIDI file is attached, but you'll have to update your .obm file with the new MD5 to prevent the game from flagging it as corrupt afterwards.
Yes, this was the track with a long silence I was referring to. Thanks.

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 29 Jun 2010 18:49
by Tinytimrob
I have now narrowed the bug-causing track down to one of the following:

Modern Motion
Busy Schedule
The Fast Route

Edit: I think it's Modern Motion, just double checking now

Edit: Confirmed. The buggy track is Modern Motion for me.

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 29 Jun 2010 19:08
by Samu
Busy Schedule and The Fast Route were created by the same autor, just saying.

I don't know how to put your file working. I receive an ini error when I start the game

ini: '$Id: orig_win.obm 19446 2010-03-17 22:21:03Z rubidium $' outside of group

I obtained this md5 for that file
18ad592de57e370f0503315a780a3445

EDIT... FIXED!!! The obm was 1 byte difference, I tried doing it again, now it has the same size, it works!

Re: Bug found with OpenMSX perhaps. Input required.

Posted: 29 Jun 2010 20:35
by Tinytimrob
I edited ini.cpp to get rid of that problem, so I'm glad you managed to fix it without doing that.