如何使用.NET compact framework 2.0播放midi文件?

时间:2022-12-06 13:24:16

I have tried this but it does not work (even if I specify .wav file as an input). Also tried this but still no sound. Trying to avoid .wav because they are BIG if you compare with midi.

我试过这个但它不起作用(即使我指定.wav文件作为输入)。也试过这个,但仍然没有声音。试图避免使用.wav,因为如果你与midi比较它们会很大。

I'm trying this with VS 2008 emulator. Is that the problem? Should I test on the real hardware?

我正在尝试使用VS 2008模拟器。那是问题吗?我应该在真正的硬件上进行测试吗?

What is the best way to play midi on the .NET compact framework 2.0 ??

在.NET紧凑框架2.0上播放midi的最佳方法是什么?

1 个解决方案

#1


Hi I am just adding some information. It seems you have a misunderstanding about Midi format. Not like the Wave files the Midi file does not keep the actual "Sound". It just keeps a value mapped with the actual sound. We just use a synthesizer to regenerate the sound. As and example we may hear the same midi song differently with different synthesizers.

嗨,我只是添加一些信息。看来你对Midi格式有误解。与Wave文件不同,Midi文件不保留实际的“声音”。它只是保持与实际声音映射的值。我们只需使用合成器来重新生成声音。作为例子,我们可以用不同的合成器以不同的方式听到相同的midi歌曲。

According to this synthesis of sound I guess it consumes the CPU more than a normal Wave file. Please have a look on this matter as well because you are trying to use the mobile devices with less resources.

根据声音的这种合成,我猜它消耗的CPU比普通的Wave文件更多。请关注此问题,因为您尝试使用资源较少的移动设备。

#1


Hi I am just adding some information. It seems you have a misunderstanding about Midi format. Not like the Wave files the Midi file does not keep the actual "Sound". It just keeps a value mapped with the actual sound. We just use a synthesizer to regenerate the sound. As and example we may hear the same midi song differently with different synthesizers.

嗨,我只是添加一些信息。看来你对Midi格式有误解。与Wave文件不同,Midi文件不保留实际的“声音”。它只是保持与实际声音映射的值。我们只需使用合成器来重新生成声音。作为例子,我们可以用不同的合成器以不同的方式听到相同的midi歌曲。

According to this synthesis of sound I guess it consumes the CPU more than a normal Wave file. Please have a look on this matter as well because you are trying to use the mobile devices with less resources.

根据声音的这种合成,我猜它消耗的CPU比普通的Wave文件更多。请关注此问题,因为您尝试使用资源较少的移动设备。