20415 2012-12-17 17:21:11 +0000 Add a serializer to MIDIPort 2013-01-18 15:50:57 +0000 1 1 1 Unclassified AudioWG MIDI API unspecified PC Windows NT CLOSED NEEDSINFO P2 normal TBD 1 jussi.kalliokoski dave.null cwilso w3c public-audio oldest_to_newest 80289 0 jussi.kalliokoski 2012-12-17 17:21:11 +0000 See this thread: http://lists.w3.org/Archives/Public/public-audio/2012OctDec/0697.html 80298 1 cwilso 2012-12-17 18:51:13 +0000 Can you describe exactly what feature you're trying to get from this (i.e. user scenario)? 80308 2 w3c 2012-12-17 20:57:09 +0000 (In reply to comment #1) > Can you describe exactly what feature you're trying to get from this (i.e. > user scenario)? See "9.2 Enumerating Inputs and Outputs" example: https://dvcs.w3.org/hg/audio/raw-file/tip/midi/specification.html#enumerating-inputs-and-outputs That's pretty common... with toJSON, it becomes something like: function showPorts( midiAccess ) { function show(port, i){ console.log("Input port #" + i + " " + port.toJSON()); } midiAccess.enumerateInputs().forEach(show); midiAccess.enumerateOutputs().forEach(show); } 80309 3 cwilso 2012-12-17 21:01:25 +0000 (In reply to comment #2) > (In reply to comment #1) > > Can you describe exactly what feature you're trying to get from this (i.e. > > user scenario)? > > See "9.2 Enumerating Inputs and Outputs" example: > https://dvcs.w3.org/hg/audio/raw-file/tip/midi/specification. > html#enumerating-inputs-and-outputs > > That's pretty common... with toJSON, it becomes something like: > > function showPorts( midiAccess ) { > function show(port, i){ > console.log("Input port #" + i + " " + port.toJSON()); > } > midiAccess.enumerateInputs().forEach(show); > midiAccess.enumerateOutputs().forEach(show); > } That sample was just enumerating the parameters for debugging purposes, though - serialization implies deserialization. I don't think the "serialize everything in the input/output object" is a particularly interesting scenario, unless you're trying to imply that fromJSON() could re-create the port - and this is a "magic host object". :) 80314 4 w3c 2012-12-17 23:16:20 +0000 (In reply to comment #3) > That sample was just enumerating the parameters for debugging purposes, > though - serialization implies deserialization. I don't think the > "serialize everything in the input/output object" is a particularly > interesting scenario, unless you're trying to imply that fromJSON() could > re-create the port - and this is a "magic host object". :) Ok, fair call. I currently don't have a case for serialization (apart form using it as a stringifier in debugging). I think there might be a case for storing serialized versions of previously used ports, etc. But I need to encounter the actual use case through playing around a bit more with the API.... Can we mark this as RESOLVED/NEEDSINFO? 81572 5 olivier.thereaux 2013-01-18 15:50:57 +0000 Batch-closing RESOLVED MIDI issues. Reminder: midi issues now tracked at https://github.com/WebAudio/web-midi-api/issues