More actions
No edit summary |
No edit summary |
||
| (17 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Infobox | {{Infobox DS Homebrews | ||
| title | |title=Pulse DS | ||
| image | |image=Pulseds2.png | ||
| type | |description=A MIDI synthesizer to produce Game-Boy-like sounds. | ||
| version | |author=tobw | ||
| | |lastupdated=2010/04/05 | ||
| | |type=Music Apps | ||
| website | |version=1.6 | ||
| | |license=Mixed | ||
|download=https://dlhb.gamebrew.org/dshomebrew2/pulseds_1.6.zip | |||
|website=http://dsmi.tobw.net/index.php?cat_id=1 | |||
|source=https://dlhb.gamebrew.org/dshomebrew2/pulseds_1.6.zip | |||
}} | }} | ||
Pulse DS turns the DS into a MIDI synthesizer that uses the DS's PSG (programmable sound generator) to produce Game-Boy-like sounds. | Pulse DS turns the DS into a MIDI synthesizer that uses the DS's PSG (programmable sound generator) to produce Game-Boy-like sounds. | ||
It is an application demonstrating the use of [ | It is an application demonstrating the use of [[DSMI Server|DSMI]] (DS Music Interface) which runs on your computer receives MIDI commands and feeds them to your MIDI applications. | ||
==User guide== | ==User guide== | ||
===FAQ=== | ===FAQ=== | ||
'''MIDI over WiFi? Sounds unreliable and slow?''' | '''Q. MIDI over WiFi? Sounds unreliable and slow?''' | ||
Of course, wireless networks are not the best method for time-critical applications like MIDI, but the latency and packet loss turned out much smaller than what we expected in the first place. In OSX, the average latency we measured was about 17 ms. We were unable to measure it on other platforms, but subjectively, the latency feels about as low in Linux and horribly high in Windows (due to the Midi Loopback that has to be used because of Windows' inflexible MIDI framework). But better try it out for yourself. | Of course, wireless networks are not the best method for time-critical applications like MIDI, but the latency and packet loss turned out much smaller than what we expected in the first place. In OSX, the average latency we measured was about 17 ms. We were unable to measure it on other platforms, but subjectively, the latency feels about as low in Linux and horribly high in Windows (due to the Midi Loopback that has to be used because of Windows' inflexible MIDI framework). But better try it out for yourself. | ||
'''Oh no! Half of my MIDI messages get lost!''' | '''Q. Oh no! Half of my MIDI messages get lost!''' | ||
Probably the connection is disturbed. Make sure that the DS is in range of the access point and that no other (bigger) traffic is going over it. Limiting your access point's bandwidth to 2MBit might also help, because the DS's WiFi has 2MBit. | Probably the connection is disturbed. Make sure that the DS is in range of the access point and that no other (bigger) traffic is going over it. Limiting your access point's bandwidth to 2MBit might also help, because the DS's WiFi has 2MBit. | ||
'''My DS can't connect to the access point?''' | '''Q. My DS can't connect to the access point?''' | ||
Make sure you set up the connection correctly using a Nintendo WiFi Connection game like Mario Kart or the Opera Browser. If it still doesn't work, try entering the WEP key in hex representation instead of ASCII in the WFC configuration. You could also try restarting your access point (this has really helped a couple of times). If everything fails, try throttling the bandwidth to 2MBit or disabling WEP (not recommended though). | Make sure you set up the connection correctly using a Nintendo WiFi Connection game like Mario Kart or the Opera Browser. If it still doesn't work, try entering the WEP key in hex representation instead of ASCII in the WFC configuration. You could also try restarting your access point (this has really helped a couple of times). If everything fails, try throttling the bandwidth to 2MBit or disabling WEP (not recommended though). | ||
'''My DS says it is connected but the server does not seem to receive any messages.''' | '''Q. My DS says it is connected but the server does not seem to receive any messages.''' | ||
Make sure the computer and the DS are in the same subnet, i.e. the first three numbers of their IPs are identical. For example, if the DS has the IP 192.168.1.x, then the computer has to have 192.168.1.y. Also make sure there is no firewall that blocks incomping packets on port 9000 or outgoing packets on port 9001. | Make sure the computer and the DS are in the same subnet, i.e. the first three numbers of their IPs are identical. For example, if the DS has the IP 192.168.1.x, then the computer has to have 192.168.1.y. Also make sure there is no firewall that blocks incomping packets on port 9000 or outgoing packets on port 9001. | ||
'''I'm connected but I cannot receive data?''' | '''Q. I'm connected but I cannot receive data?''' | ||
This happens sometimes for an unknown reason. Restart the DS and try again. | This happens sometimes for an unknown reason. Restart the DS and try again. | ||
'''How do the PC and the DS find each other? I haven't entered their IPs anywhere.''' | '''Q. How do the PC and the DS find each other? I haven't entered their IPs anywhere.''' | ||
The magic is called "broadcasting". The DS just sends the MIDI packets to all hosts in the current subnet. So, if the DS is 192.168.1.88, then the packets are sent to 192.168.1.*. | The magic is called "broadcasting". The DS just sends the MIDI packets to all hosts in the current subnet. So, if the DS is 192.168.1.88, then the packets are sent to 192.168.1.*. | ||
==Media== | ==Media== | ||
'''DSMidiWifi''' ([https://www.youtube.com/watch?v=AYDF313Ae7A 0xtob]) <br> | |||
<youtube>AYDF313Ae7A</youtube> | <youtube>AYDF313Ae7A</youtube> | ||
==External links== | |||
* Author's website - http://dsmi.tobw.net/index.php?cat_id=1 | |||
* Google Code - https://code.google.com/archive/p/dsmi | |||
Latest revision as of 04:57, 21 August 2024
| Pulse DS | |
|---|---|
 | |
| General | |
| Author | tobw |
| Type | Music Apps |
| Version | 1.6 |
| License | Mixed |
| Last Updated | 2010/04/05 |
| Links | |
| Download | |
| Website | |
| Source | |
Pulse DS turns the DS into a MIDI synthesizer that uses the DS's PSG (programmable sound generator) to produce Game-Boy-like sounds.
It is an application demonstrating the use of DSMI (DS Music Interface) which runs on your computer receives MIDI commands and feeds them to your MIDI applications.
User guide
FAQ
Q. MIDI over WiFi? Sounds unreliable and slow?
Of course, wireless networks are not the best method for time-critical applications like MIDI, but the latency and packet loss turned out much smaller than what we expected in the first place. In OSX, the average latency we measured was about 17 ms. We were unable to measure it on other platforms, but subjectively, the latency feels about as low in Linux and horribly high in Windows (due to the Midi Loopback that has to be used because of Windows' inflexible MIDI framework). But better try it out for yourself.
Q. Oh no! Half of my MIDI messages get lost!
Probably the connection is disturbed. Make sure that the DS is in range of the access point and that no other (bigger) traffic is going over it. Limiting your access point's bandwidth to 2MBit might also help, because the DS's WiFi has 2MBit.
Q. My DS can't connect to the access point?
Make sure you set up the connection correctly using a Nintendo WiFi Connection game like Mario Kart or the Opera Browser. If it still doesn't work, try entering the WEP key in hex representation instead of ASCII in the WFC configuration. You could also try restarting your access point (this has really helped a couple of times). If everything fails, try throttling the bandwidth to 2MBit or disabling WEP (not recommended though).
Q. My DS says it is connected but the server does not seem to receive any messages.
Make sure the computer and the DS are in the same subnet, i.e. the first three numbers of their IPs are identical. For example, if the DS has the IP 192.168.1.x, then the computer has to have 192.168.1.y. Also make sure there is no firewall that blocks incomping packets on port 9000 or outgoing packets on port 9001.
Q. I'm connected but I cannot receive data?
This happens sometimes for an unknown reason. Restart the DS and try again.
Q. How do the PC and the DS find each other? I haven't entered their IPs anywhere.
The magic is called "broadcasting". The DS just sends the MIDI packets to all hosts in the current subnet. So, if the DS is 192.168.1.88, then the packets are sent to 192.168.1.*.
Media
DSMidiWifi (0xtob)
External links
- Author's website - http://dsmi.tobw.net/index.php?cat_id=1
- Google Code - https://code.google.com/archive/p/dsmi