Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Profiles like RFCOMM does not belong to BTLE but to the bluetooth classic.</p> <p>In music applications you should care about latency. The time from first byte is send from a midi keyboard and until it arrives at the destination really matters. There is no exact BAUD rate in SPP / RFCOMM but throughput which depends on the 2 sides. <a href="http://snapshot.bluecove.org/bluecove-examples/bluecove-tester/speed.html" rel="nofollow noreferrer">http://snapshot.bluecove.org/bluecove-examples/bluecove-tester/speed.html</a></p> <p>If you input MIDI (31250 BAUD), send it through a "channel", send it out through MIDI (31250 BAUD) then you need to look at 2 things: 1) Throughput, must be big enough to 'sink' and 'source' Midi In and Midi Out 2) Latency, must be fast enough to make it 'musically' accurate.</p> <p>A Midi ON event takes aproximately 30 signal bits so you can send some 104 Midi events per sec. Latency is aprox 10ms.</p> <p>On iOS the fastest Connection Interval (1 block of some 20 bytes) is around 19ms if you break the recommendations or 39ms if you follow them. The total latency would then be: Midi In (10ms) + BTLE GATT (up to 39ms) + Midi Out (10ms) = 60ms. 6 times slower than normal MIDI cable. Minimum BTLE connection interval is 7.5ms but you will lose packets at the lowest level so let's just say 10ms: Midi In (10ms) + BTLE (10ms) + Midi Out (10ms) = 30ms. Not too bad but not really impressive either. In each Connection Interval you can pack around 20 Bytes so there should be plenty of bandwidth or throughput.</p> <p>Take a look at this BTLE RFCOMM project: <a href="http://support.connectblue.com/display/PRODBTSPA/Bluetooth+Low+Energy+Serial+Port+Adapter+-+Getting+Started" rel="nofollow noreferrer">http://support.connectblue.com/display/PRODBTSPA/Bluetooth+Low+Energy+Serial+Port+Adapter+-+Getting+Started</a></p>
    singulars
    1. This table or related slice is empty.
    1. POMIDI Over Bluetooth
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USuser3052786
    1. UShenrik
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMIDI latency on its own is more typically around 4-5ms. Most messages (note on/off) are 2 bytes. Controller messages are usually delayed by the sending device if there are notes to be sent.
      singulars
      1. PO
      1. USBrad
    2. CO@Brad: most messages (Note On/Off, Control Change, Pitch Bend, ...) are **3 bytes**.
      singulars
      1. PO
      1. USFlorian
    3. COhenrik and Brad: Sending one 3-byte messages over a standard MIDI cable takes 960us (matching @Hal's 1041 full Note messages per second), not 4-5ms. Of course, the receiver may add delay for processing.
      singulars
      1. PO
      1. USFlorian
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload