Page 1 of 1

*.MID files in preview have "decode error"

Posted: 29 Jul 2010 16:29
by cpusrvc
Happens in 2 different computers, v9.20 & 9.30. They play in Irfanview just fine.

EDIT: computers are W7, x32 & x64

Re: *.MID files in preview have "decode error"

Posted: 29 Jul 2010 17:48
by nas8e9
cpusrvc wrote:Happens in 2 different computers, v9.20 & 9.30. They play in Irfanview just fine.

EDIT: computers are W7, x32 & x64
Confirmed with 9.30.0023 on Windows 7 x64 RTM.

The odd thing is that Windows Media Player does play them correctly; I thought XYplorer uses the media facilities built into Windows/IE?

Re: *.MID files in preview have "decode error"

Posted: 29 Jul 2010 17:51
by admin
Last time I tried they played well here. Can you send me one?

Re: *.MID files in preview have "decode error"

Posted: 29 Jul 2010 18:10
by nas8e9
admin wrote:Last time I tried they played well here. Can you send me one?
Happy to if needed, but the .mid files that come with Windows 7 give the same problem:

C:\Windows\Media:
flourish.mid
onestop.mid
town.mid

Re: *.MID files in preview have "decode error"

Posted: 29 Jul 2010 18:10
by cpusrvc
admin wrote:Last time I tried they played well here. Can you send me one?
Try this one ... plays in Irfanview (change the ext to MID)

EDIT: I thought it attached, I'll send by email

Re: *.MID files in preview have "decode error"

Posted: 29 Jul 2010 19:29
by cpusrvc
Don, thanks for the email response that you can play the file. Obviously, I'm not the only one with this issue. I found the following MS article:

http://www.microsoft.com/windows/window ... mspx#EJAAC says:
Windows Media Player is only used to show the playback progress of a .mid or .midi (MIDI Sequence) file while it is playing. Playback support for MIDI Sequence in Windows is actually provided by Microsoft DirectX and your sound card, not the Player.

The article has other info in case the file doesn't play that may apply to XY's implementation.

Like others have said, they can play MIDI files just not with XY, so I don't think its a missing CODEC.

Re: *.MID files in preview have "decode error"

Posted: 29 Jul 2010 19:56
by admin
cpusrvc wrote:Don, thanks for the email response that you can play the file. Obviously, I'm not the only one with this issue. I found the following MS article:

http://www.microsoft.com/windows/window ... mspx#EJAAC says:
Windows Media Player is only used to show the playback progress of a .mid or .midi (MIDI Sequence) file while it is playing. Playback support for MIDI Sequence in Windows is actually provided by Microsoft DirectX and your sound card, not the Player.

The article has other info in case the file doesn't play that may apply to XY's implementation.

Like others have said, they can play MIDI files just not with XY, so I don't think its a missing CODEC.
Thanks, but the article does not tell me anything I could use.
The question is: Why can I play it? Must be a CODEC I have.
But I don't have time for this anyway. Sorry, but MIDI has to wait.

Re: *.MID files in preview have "decode error"

Posted: 29 Jul 2010 20:12
by admin
PS: next version will have a new AudioMCICustomExtensions tweak. Set to mid and see if that changes anything:

Code: Select all

AudioMCICustomExtensions=mid

Re: *.MID files in preview have "decode error"

Posted: 31 Jul 2010 09:54
by nas8e9
admin wrote:PS: next version will have a new AudioMCICustomExtensions tweak. Set to mid and see if that changes anything:

Code: Select all

AudioMCICustomExtensions=mid
Solves it for me with 9.30.0024 on Windows 7 x64.

Re: *.MID files in preview have "decode error"

Posted: 31 Jul 2010 10:06
by admin
nas8e9 wrote:
admin wrote:PS: next version will have a new AudioMCICustomExtensions tweak. Set to mid and see if that changes anything:

Code: Select all

AudioMCICustomExtensions=mid
Solves it for me with 9.30.0024 on Windows 7 x64.
OK, I will add this setting for MID to the hard standards, so in the next version this tweak is no longer needed MID files. (The change of MID preview was an experiment I did more than 3 years ago -- so now it turns out it fails. :) )