dsmi - Project Hosting on Google Code

Older Dec 04, 2009 issue 7 (The MIDI receiver thread on the iphone project doesn't have ...) reported by Martin2....@uwe.ac.uk - What steps will reproduce the problem? 1. Try using Obj-C classes in the MIDI receiver callback thread (e.g. NSString) What is the expected output? What do you see instead? There shouldn't be errors and the objects shouldn't leak What version of the product are you using? On what operating system? libdsmi_iphone 1.0, iPhone SDK 3.2.1, Xcode 3.1.4 Please provide any additional information below. Putting an AutoReleasePool in the MIDIReceiver thread fixes this. What steps will reproduce the problem? 1. Try using Obj-C classes in the MIDI receiver callback thread (e.g. NSString) What is the expected output? What do you see instead? There shouldn't be errors and the objects shouldn't leak What version of the product are you using? On what operating system? libdsmi_iphone 1.0, iPhone SDK 3.2.1, Xcode 3.1.4 Please provide any additional information below. Putting an AutoReleasePool in the MIDIReceiver thread fixes this. Dec 04, 2009 issue 6 (dsmi iphone simulator not working) commented on by Martin2....@uwe.ac.uk - Actually the fix seems simple. Two things: 1. Set the IPHONE_SENDER_PORT to 9003 so this doesn't clash with the PC_SENDER_PORT on the server. 2. Check both en0 and en1 interfaces for the broadcast address. en0 seems to work on the device but not on the simulator. en1 works on the simulator but not on the device. Hope this helps! Actually the fix seems simple. Two things: 1. Set the IPHONE_SENDER_PORT to 9003 so this doesn't clash with the PC_SENDER_PORT on the server. 2. Check both en0 and en1 interfaces for the broadcast address. en0 seems to work on the device but not on the simulator. en1 works on the simulator but not on the device. Hope this helps! Dec 04, 2009 issue 6 (dsmi iphone simulator not working) reported by Martin2....@uwe.ac.uk - What steps will reproduce the problem? 1. build a simple sending/receiving app for the iphone 2. works fine on iphone/ipod touch <-> dsmi server 3. doesn't work on simulator <-> dsmi server What is the expected output? What do you see instead? behaviour should be the same as the device What version of the product are you using? On what operating system? Mac OS 10.5.8, iPhone SDK 3.2.1, Xcode 3.1.4, dsmi_iphone 1.0 Please provide any additional information below. Building the dsmi_iphone source and stepping through in the debugger shows the socket binding fails when the dsmi server is running, presumably it is using the same ports? The binding doesn't fail when the dsmi server is not running but of course that doesn't work either since there's no where to send the data. What steps will reproduce the problem? 1. build a simple sending/receiving app for the iphone 2. works fine on iphone/ipod touch <-> dsmi server 3. doesn't work on simulator <-> dsmi server What is the expected output? What do you see instead? behaviour should be the same as the device What version of the product are you using? On what operating system? Mac OS 10.5.8, iPhone SDK 3.2.1, Xcode 3.1.4, dsmi_iphone 1.0 Please provide any additional information below. Building the dsmi_iphone source and stepping through in the debugger shows the socket binding fails when the dsmi server is running, presumably it is using the same ports? The binding doesn't fail when the dsmi server is not running but of course that doesn't work either since there's no where to send the data. Aug 16, 2009 issue 5 (Libdsmi for windows/mac/linux?) reported by SqueeDee - This is a feature request. It would be really nice to be able to use the exact same mechanism as the iPhone and DS apps use to send midi over wifi between computers on the network. It would make networked midi a breeze and present a unified mechanism. This is a feature request. It would be really nice to be able to use the exact same mechanism as the iPhone and DS apps use to send midi over wifi between computers on the network. It would make networked midi a breeze and present a unified mechanism. Apr 27, 2009 issue 4 (Having Issues Connecting PulseDS - have tried multiple scena...) reported by reconor - Scenario 1 Mac OSX - Leopard: What steps will reproduce the problem? 1. Followed Guide Directions to connect a DS directly to a Mac Airport Card 2. Confirmed Connectivity 3. Launched dsmidiwifi 4. Launched Logic 5. Launched PulseDS 1.3/1.4/1.5 (All Versions Have Same Issue) 6. Began mashing my connected MIDI Keyboard What is the expected output? What do you see instead? PulseDS displays 'running' but does not respond to MIDI input. No output or sign of receiving input. I have tried restarting the DS & have confirmed that my DS is connected to the Macbook Pro What version of the product are you using? On what operating system? PulseDS 1.3/1.4/1.5 with Mac OSX Please provide any additional information below. I have a strong feeling that my problem is within what MIDI Channel I ought to be outputting to - or how to configure Logic (or a Windows equivalent DAW) to output to the correct MIDI Channel for PulseDS to receive input. I have been knocking my head around on this problem on and off for the past few weeks - I'd love to get it figured out, the DSMI videos on your site are actually what motivated me to get my R4. I love your projects! =D Scenario 2 - Windows XP: What steps will reproduce the problem? 1. Configure DS to connect to access point - confirmed connectivity 2. Installed LoopBack MIDI Drivers for Windows 3. Launched dsmidiwifi 4. Selected my USB MIDI Controller Device which is connected to a keyboard as my input device. 5. Launched PulseDS 1.3/1.4/1.5 (All Versions Have Same Issue) What is the expected output? What do you see instead? PulseDS displays 'running' but does not respond to MIDI input. No output or sign of receiving input. I have tried restarting the DS & have confirmed that my host computer is on the same subnetwork as the DS. What version of the product are you using? On what operating system? PulseDS 1.3/1.4/1.5 with Windows XP using LoopBack driver linked from site. Scenario 1 Mac OSX - Leopard: What steps will reproduce the problem? 1. Followed Guide Directions to connect a DS directly to a Mac Airport Card 2. Confirmed Connectivity 3. Launched dsmidiwifi 4. Launched Logic 5. Launched PulseDS 1.3/1.4/1.5 (All Versions Have Same Issue) 6. Began mashing my connected MIDI Keyboard What is the expected output? What do you see instead? PulseDS displays 'running' but does not respond to MIDI input. No output or sign of receiving input. I have tried restarting the DS & have confirmed that my DS is connected to the Macbook Pro What version of the product are you using? On what operating system? PulseDS 1.3/1.4/1.5 with Mac OSX Please provide any additional information below. I have a strong feeling that my problem is within what MIDI Channel I ought to be outputting to - or how to configure Logic (or a Windows equivalent DAW) to output to the correct MIDI Channel for PulseDS to receive input. I have been knocking my head around on this problem on and off for the past few weeks - I'd love to get it figured out, the DSMI videos on your site are actually what motivated me to get my R4. I love your projects! =D Scenario 2 - Windows XP: What steps will reproduce the problem? 1. Configure DS to connect to access point - confirmed connectivity 2. Installed LoopBack MIDI Drivers for Windows 3. Launched dsmidiwifi 4. Selected my USB MIDI Controller Device which is connected to a keyboard as my input device. 5. Launched PulseDS 1.3/1.4/1.5 (All Versions Have Same Issue) What is the expected output? What do you see instead? PulseDS displays 'running' but does not respond to MIDI input. No output or sign of receiving input. I have tried restarting the DS & have confirmed that my host computer is on the same subnetwork as the DS. What version of the product are you using? On what operating system? PulseDS 1.3/1.4/1.5 with Windows XP using LoopBack driver linked from site. Apr 07, 2009 issue 3 (I am having no sucess with using this iphone app with logic....) reported by MrFitxxxx - What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? What version of the product are you using? On what operating system? Please provide any additional information below. What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? What version of the product are you using? On what operating system? Please provide any additional information below. Mar 01, 2009 libdsmi_iphone_simulator_v1.0.zip (libDSMI binary library for iPhone OS Simulator v1.0) file uploaded by collin.meyer - Labels: Featured Labels: Featured Mar 01, 2009 libdsmi_iphone_v1.0.zip (libDSMI binary library for iPhone OS) file uploaded by collin.meyer Mar 01, 2009 r18 (Fixed the message that was being sent to the server to get I...) committed by collin.meyer - Fixed the message that was being sent to the server to get IP added to the list. MIDI Receive is now working, updating this as version 1.0 Fixed the message that was being sent to the server to get IP added to the list. MIDI Receive is now working, updating this as version 1.0 Mar 01, 2009 r17 (Fixed the message that was being sent to the server to get I...) committed by collin.meyer - Fixed the message that was being sent to the server to get IP added to the list. MIDI Receive is now working, updating this as version 1.0 Fixed the message that was being sent to the server to get IP added to the list. MIDI Receive is now working, updating this as version 1.0 Mar 01, 2009 r16 (Add (void) to arguments - fixes exception Still needs furt...) committed by collin.meyer - Add (void) to arguments - fixes exception Still needs further testing to determine why MIDI receive is not happening. Add (void*) to arguments - fixes exception Still needs further testing to determine why MIDI receive is not happening. Feb 24, 2009 issue 1 (Pre-defined message types) commented on by collin.meyer - I think that this might be handled decently already. Originally I had thought maybe making a MIDI Message struct would be nice for users of the library. but now I'm leaning towards keeping the old model of calling a function like send_message(message, data1, data2); Or in the iphone port, this is split out to send_message(message_type, midi_channel, data1, data2); The thing I like about the iphone version is that the user doesn't need to understand how the or \| operator works. I think that this might be handled decently already. Originally I had thought maybe making a MIDI Message struct would be nice for users of the library. but now I'm leaning towards keeping the old model of calling a function like send_message(message, data1, data2); Or in the iphone port, this is split out to send_message(message_type, midi_channel, data1, data2); The thing I like about the iphone version is that the user doesn't need to understand how the or \| operator works. Feb 09, 2009 libdsmi_iphone_simulator-v0.8.zip (libDSMI for iPhone Simulator binary library and header file) file uploaded by collin.meyer Feb 09, 2009 libdsmi_iphone-v0.8.zip (libDSMI for iPhone binary library and header file) file uploaded by collin.meyer Feb 09, 2009 r15 ([No log message]) committed by collin.meyer - [No log message] [No log message] Feb 09, 2009 r14 ([No log message]) committed by collin.meyer - [No log message] [No log message] Feb 09, 2009 r13 ([No log message]) committed by collin.meyer - [No log message] [No log message] Feb 09, 2009 issue 2 (Add null interfaces to Windows GUI) reported by weyand - Since there are no null MIDI interfaces in the Windows DSMIDIWiFi Server, short-circuits can occur easily. Since there are no null MIDI interfaces in the Windows DSMIDIWiFi Server, short-circuits can occur easily. Feb 09, 2009 issue 1 (Pre-defined message types) reported by weyand - sending and receiving MIDI messages would be easier with pre-defined message types like NOTE_ON, CC_CHANGE, etc. sending and receiving MIDI messages would be easier with pre-defined message types like NOTE_ON, CC_CHANGE, etc. Feb 08, 2009 r12 ([No log message]) committed by collin.meyer - [No log message] [No log message] Feb 08, 2009 r11 ([No log message]) committed by collin.meyer - [No log message] [No log message] Jan 31, 2009 r10 ([No log message]) committed by collin.meyer - [No log message] [No log message] Jan 31, 2009 r9 (iPhone port of libDSMI) committed by collin.meyer - iPhone port of libDSMI iPhone port of libDSMI Jan 29, 2009 libdsmi-v3.0.zip (The library for building DSMI enabled Nintendo DS homebrew) file uploaded by weyand - Labels: Featured Labels: Featured Jan 29, 2009 pulseds-v1.5.zip (Pulse DS turns the DS into a MIDI synthesizer that uses the ...) file uploaded by weyand - Labels: Featured Labels: Featured Jan 29, 2009 kaosds-v1.4.zip (Kaos DS is an XY controller similar to the Kaoss pad. You ca...) file uploaded by weyand - Labels: Featured Labels: Featured Jan 29, 2009 dsmidikeyboard-v1.4.zip (DS MIDI Keyboard acts as a MIDI keyboard, including pitch wh...) file uploaded by weyand - Labels: Featured Labels: Featured Jan 29, 2009 r8 (Added nds header icons and descriptions Made PulseDS turn of...) committed by weyand - Added nds header icons and descriptions Made PulseDS turn off the bottom screen Added nds header icons and descriptions Made PulseDS turn off the bottom screen Jan 29, 2009 r7 (Ported KaosDS to libnds v1.3.1) committed by weyand - Ported KaosDS to libnds v1.3.1 Ported KaosDS to libnds v1.3.1 Jan 29, 2009 r6 (Ported dsmidikeyboard to libnds-1.3.1) committed by weyand - Ported dsmidikeyboard to libnds-1.3.1 Ported dsmidikeyboard to libnds-1.3.1 Jan 29, 2009 r5 (This version sends kaos coordinates separately, and normaliz...) committed by weyand - This version sends kaos coordinates separately, and normalizes all the values as floats from 0 to 1. pd patch updated This version sends kaos coordinates separately, and normalizes all the values as floats from 0 to 1. pd patch updated Jan 29, 2009 r4 (Updated libdsmi to libnds 1.3.1 and dswifi 0.3.6. dsmi_setup...) committed by weyand - Updated libdsmi to libnds 1.3.1 and dswifi 0.3.6. dsmi_setup_wifi is no longer required! Updated libdsmi to libnds 1.3.1 and dswifi 0.3.6. dsmi_setup_wifi is no longer required! Jan 29, 2009 r3 (Updated PulseDS for the new libnds 1.3.1 PulseDS now uses th...) committed by weyand - Updated PulseDS for the new libnds 1.3.1 PulseDS now uses the FIFO instead of the memory based IPC struct Updated PulseDS for the new libnds 1.3.1 PulseDS now uses the FIFO instead of the memory based IPC struct Dec 19, 2008 dsmidiwifi-v1.01.dmg (DSMI Server for OSX) file uploaded by weyand - Labels: Featured Labels: Featured Dec 19, 2008 dsmidiwifi-v1.01.tgz (DSMI server for Linux) file uploaded by weyand - Labels: Featured Labels: Featured Dec 19, 2008 dsmidiwifi-v1.01.zip (DSMI server for Windows) file uploaded by weyand - Labels: Featured Labels: Featured Dec 19, 2008 oscexample-v1.0.zip (OSC Example, is a Kaoss Pad with three sliders that demonstr...) file uploaded by weyand - Labels: Featured Labels: Featured Dec 19, 2008 pulseds-v1.4.zip (Pulse DS turns the DS into a MIDI synthesizer that uses the ...) file uploaded by weyand - Labels: Featured Labels: Featured Dec 19, 2008 kaosds-v1.2.zip (Kaos DS is an XY controller similar to the Kaoss pad. You ca...) file uploaded by weyand - Labels: Featured Labels: Featured Dec 19, 2008 dsmidikeyboard-v1.2.zip (DS MIDI Keyboard acts as a MIDI keyboard, including pitch wh...) file uploaded by weyand - Labels: Featured Labels: Featured Dec 19, 2008 libdsmi-v3.0-beta.zip (The library for building DSMI enabled Nintendo DS homebrew) file uploaded by weyand - Labels: Featured Labels: Featured Dec 19, 2008 r2 (Initial commit) committed by weyand - Initial commit Initial commit Dec 19, 2008 Project dsmi created by weyand - DS Music Interface DS Music Interface

issue 4 (Having Issues Connecting PulseDS - have tried multiple scena...) reported by reconor - Scenario 1 Mac OSX - Leopard: What steps will reproduce the problem? 1. Followed Guide Directions to connect a DS directly to a Mac Airport Card 2. Confirmed Connectivity 3. Launched dsmidiwifi 4. Launched Logic 5. Launched PulseDS 1.3/1.4/1.5 (All Versions Have Same Issue) 6. Began mashing my connected MIDI Keyboard What is the expected output? What do you see instead? PulseDS displays 'running' but does not respond to MIDI input. No output or sign of receiving input. I have tried restarting the DS & have confirmed that my DS is connected to the Macbook Pro What version of the product are you using? On what operating system? PulseDS 1.3/1.4/1.5 with Mac OSX Please provide any additional information below. I have a strong feeling that my problem is within what MIDI Channel I ought to be outputting to - or how to configure Logic (or a Windows equivalent DAW) to output to the correct MIDI Channel for PulseDS to receive input. I have been knocking my head around on this problem on and off for the past few weeks - I'd love to get it figured out, the DSMI videos on your site are actually what motivated me to get my R4. I love your projects! =D Scenario 2 - Windows XP: What steps will reproduce the problem? 1. Configure DS to connect to access point - confirmed connectivity 2. Installed LoopBack MIDI Drivers for Windows 3. Launched dsmidiwifi 4. Selected my USB MIDI Controller Device which is connected to a keyboard as my input device. 5. Launched PulseDS 1.3/1.4/1.5 (All Versions Have Same Issue) What is the expected output? What do you see instead? PulseDS displays 'running' but does not respond to MIDI input. No output or sign of receiving input. I have tried restarting the DS & have confirmed that my host computer is on the same subnetwork as the DS. What version of the product are you using? On what operating system? PulseDS 1.3/1.4/1.5 with Windows XP using LoopBack driver linked from site.

Scenario 1 Mac OSX - Leopard: What steps will reproduce the problem? 1. Followed Guide Directions to connect a DS directly to a Mac Airport Card 2. Confirmed Connectivity 3. Launched dsmidiwifi 4. Launched Logic 5. Launched PulseDS 1.3/1.4/1.5 (All Versions Have Same Issue) 6. Began mashing my connected MIDI Keyboard What is the expected output? What do you see instead? PulseDS displays 'running' but does not respond to MIDI input. No output or sign of receiving input. I have tried restarting the DS & have confirmed that my DS is connected to the Macbook Pro What version of the product are you using? On what operating system? PulseDS 1.3/1.4/1.5 with Mac OSX Please provide any additional information below. I have a strong feeling that my problem is within what MIDI Channel I ought to be outputting to - or how to configure Logic (or a Windows equivalent DAW) to output to the correct MIDI Channel for PulseDS to receive input. I have been knocking my head around on this problem on and off for the past few weeks - I'd love to get it figured out, the DSMI videos on your site are actually what motivated me to get my R4. I love your projects! =D Scenario 2 - Windows XP: What steps will reproduce the problem? 1. Configure DS to connect to access point - confirmed connectivity 2. Installed LoopBack MIDI Drivers for Windows 3. Launched dsmidiwifi 4. Selected my USB MIDI Controller Device which is connected to a keyboard as my input device. 5. Launched PulseDS 1.3/1.4/1.5 (All Versions Have Same Issue) What is the expected output? What do you see instead? PulseDS displays 'running' but does not respond to MIDI input. No output or sign of receiving input. I have tried restarting the DS & have confirmed that my host computer is on the same subnetwork as the DS. What version of the product are you using? On what operating system? PulseDS 1.3/1.4/1.5 with Windows XP using LoopBack driver linked from site.

Older