LabView and USB MIDI cable

Can LabView interact with a MIDI-capable piece of HW through a cheap 5 dollar USB MIDI cable? 

LabVIEW is able to communicate though midi, although  it's a very very hacky process!   I'm assuming your cable has drivers and  creates a midi interface
There's two ways to do it, this works if you are on windows and it's probably the cleanest way.
http://zone.ni.com/devzone/cda/epd/p/id/718
which may be enough for some people...  The second, more full featured way of getting MIDI out of labview is through OSC...  get this
https://decibel.ni.com/content/groups/osc
And use it to generate OSC messages, then  grab a complementary piece of software to do the OSC- MIDI translation, unfortunately the OSC to midi conversion department is pretty sad right now,  there's a lot of  hacky programs, like OSCulator, touchOSC bridge, this thing (http://konkreetlabs.com/2011/05/24/free-win-mac-osc-to-midi-converter/) that all can be persuaded into working, but it's not very pretty. perhaps the best alternative to  get MIDI to OSC is though a  synthesis software suite such as pureData, MAX/MSP, Max for Live... but I assume you don't want to learn a new programming  language (and don't want to spend hundreds of dollars in music software)
As a matter of fact, because labVIEW's native MIDI support is less than stellar,(or inexistent! )   I'm working on third way, basically  creating a whole API to communicate to the OS provided midi interfaces, but you need to do some DLL/framework  (winMM, CoreMidi, ALSA) in addition to the labVIEW API  to get it working... It's actually not that sophisticated,  but  there's way to much work to be done before it's usable ( so far  you can  get a listing of MIDI devices and  information about them but no messaging just yet..)

Similar Messages

  • Voyetra USB MIDI Cable...Can I use it with the Mac

    I bought a USB Midi cable with a software package for my PC.
    http://www.voyetra.com/site/products/skits/usbmsk.asp
    I've recently switched to the Mac. Are these cables pretty standard, or do I need to get a new cable? I haven't hooked it up yet. The Voyetra site doesn't seem to have any Mac drivers.
    Thanks

    Answered my own question with a little more digging. Hope this helps anyone else.
    http://support.turtlebeach.com/site/kb_ftp/582218411.asp

  • Real Time ADC/DAC for SMPS using Labview and USB

    Hello all,
    I have asked the sales department this same question, so here's a two-pronged approach:
    I am reserching a control algorithm for a switch-mode power supply, and so far, the simulations for its performance look good.  Now, the goal is to implement the circuit for experimental data.
    I've seen several NI USB DAQ boxes that appear to have the performance I'm looking for (for example, the USB-6211 would have the resolution and sampling rate that I need).
    The control algorithm uses the following math functions:  add/sub/mult/div/exponent, and derivative/integral.
    My question is this: is Labview "strong" enough to take in four channels of 250Ksps data, crunch the numbers in an equation, and spit out the answer to an analog out channel, all in REAL time?  I'm looking for an analog output rate of ~100kHz.
    Thank you for any suggestions that you have!
    -Rick
    Solved!
    Go to Solution.

    Hey,
    So if you were just trying to perform an input or output then the USB-6211 would certainly be able to handle it because the hardware clock would be handling the input/output, not software. However, what you're wanting to do, basically a feedback system, will require software timing (at least for a USB device) because you'll have to be able to actively specify what the output is. So, for that reason alone, and the fact that you want 100kHz output, this device and USB devices in general won't be an option no matter what software you use, LabVIEW or otherwise. On another note, what you're looking to do sounds more like live updating, not Real-Time, which is more about jitter. Bottom line, for these kinds of requirements, you're going to need to move to an FPGA board, something like the NI PCIe-7841R would work. It's more expensive, but for your requirements, FPGA is going to be the only option and it comes down to bus latency as well as software response time. With FPGA, as is shown in the first diagram of the following document, you're basically closing your software loop through hardware.
    FPGA Fundamentals
    http://www.ni.com/white-paper/6983/en
    --Ryan S.

  • Controling heating/cooling element with labview and usb 6008 DAQ card

    Greetings All
    I'm looking for a heating/cooling type of element that I can control with labview and my usb-6008 card. Heating/Cooling will just be for clean water and the temperture range will be from 0 C to 100 degree C.
    Thanks
    The heating and cooling elements can be seperate products. Any recommendations

    A simple kettle element will of course be sufficient for upto 100°C
    To get the temperature down you need a cooling system, what springs readily to mind of course is a refrigerator.
    Just a note of warning, water and electricity are dangerous bed fellows.
    On that note perhaps one of those vortex air units would be safer - they blow hot in one direction and cold in the other, nominally to 100°C
    see: -
    http://www.airtxinternational.com/how_vortex_tubes_work.php

  • LabVIEW and "USB to 1-wire" (DS2490)

    I have made an "USB to 1-wire adapter" using DS2490. I can communicate with the DS2490 using USB standard requests, but I'm having a hard time getting data from the device attached to the DS2490 (i.e. DS1820). I'm using LabVIEW 7express.

    Hi,
    I did a little searching around on the Dallas Semiconductor website, and from App Note 177, it looks like the driver has a TMEX and OWCOM API. You can probably implement code to communicate to your hardware and then access that code via Call Library Function nodes or .NET calls in LabVIEW.
    Also, I'm not sure how different the 2-wire communication protocol is to the 1-wire, but DS has App Node 215 with example VIs to show how communication to a 2-wire device can be done. If you have the control commands for the device, you can also just write your own VISA commands (as that App Note 215 demonstrates) to communicate to your device. There are also a couple VISA examples that ship with LabVIEW for you to take a look at.
    Hopefully some of this will be helpful. Good luck.
    Kileen

  • Window's XP, Labview, and USB device conflicts

    Hello,
        I have labview 2011 running on windows XP SP3 with all of the updates and the USB hotfix.
        I have several usb devices connected to my computer: 3 cameras, a picoammeter, a piezo drive controller, and an external hard drive.
        I wrote labview code to use one of the cameras to take time lapse imagery, and it works great, so long as none of the other devices are on/connected.  The second I plug in another USB device invariably I get an error message:
    "Error 178 occurred at GetSingleImage.vi
    This error code is undefined. Undefined errors might occur for a number of reasons. For example, no one has provided a description for the code, or you might have wired a number that is not an error code to the error code input. 
    Additionally, undefined error codes might occur because the error relates to a third-party object, such as the operating system or ActiveX. For these third-party errors, you might be able to obtain a description of the error by searching the Web for the error code (178) or for its hexadecimal representation (0x000000B2)."
    which according to the documentation is a USB transfer error.
    I was told to update Windows XP with the newest updates, I did and it didn't help.  Someone also suggested using Windows 7, but several of my devices arent supported by windows 7 currently, so I don't want to upgrade and lose those devices.
    The other thing is that when I use multiple devices with their respective software(not labview) they behave and play well together.  It's only when labview is accessing them that they don't behave and give me errors.
    Does anyone know how to fix this?  I've been trying to fix it for a while with no success

    We have a "monitoring" application that involves taking a short video (5 to 10 seconds) when a particular event occurs.  We used IMAQdx to acquire the images from an ethernet camera.  We are actually monitoring 24 sites simultaneously (and asynchronously), and as each of the cameras has its own IP address, it wasn't difficult to keep them "apart" from each other.
    We recently tried doing the same thing using a USB camera.  When we used a single camera (one station), things worked pretty well, but when we tried using multiple stations (2 or 3, let alone 24!), we got "interference".  We attributed it to overloading the bandwidth of the USB channel -- as we already had a viable and working solution with (more expensive!) Ethernet cameras, we shrugged and (for now) gave up on using multiple USB cameras.

  • MIDI Cables and Audio Interface

    Hi, are any of you guys running GB with a USB MIDI cable and the Audio box hooked up at the same time?
    I am experimenting with GB with an iMic USB and the M-Audio UNO USB MIDI and everything is very noisy.
    If you have a setup like this, is it working for you?
    Thanks Steve

    here are some of the most popular interfaces around here:
    http://www.bulletsandbones.com/GB/Interfaces.html

  • USB MIDI not working in Windows 7 Pro 64-bit

    The problem is that even though my devices are recognized in Control Panel/ Sound and in Device Manager, no MIDI data actually flows and I cannot sync my keyboard to the Yamaha software that edits it.  The error message in the Yamaha software reads
    “The following MIDI ports can not be opened at this time”.   At first, MIDI was working and I could sync up, but after about a week, right around the time I uninstalled and re-installed a MS Lifecam, it failed and has not worked since.
    I have been working directly with Yamaha tech support on the issue for some time. I have a Yamaha SX70 XS keyboard, which is recognized by Windows as a connected USB device. It is self-powered, not powered by USB. I am using the Yamaha USB-MIDI driver version
    3.1.2 for Windows 7 64-bit (the latest driver). And the latest versions of all their editing software for Win7 64-bit. They assure me that those work for other users of Win7 64-bit. In my case though, everything shows up in Windows, but MIDI doesn’t actually
    work. And I cannot sync to the keyboard due to the above error message.
    Yamaha tells me that their USB-MIDI driver is installing fine on my machine, except that it’s missing a windows driver at the bottom of the driver stack. (You can see this in Device Manager, Properties/Driver tab, then Driver Details. The missing driver
    is ksthunk.sys, which I think handles kernel streaming. Sounds like that would relate to MIDI data. They have never heard of this driver not showing up there, and they cannot reproduce the problem. ksthunk.sys is on my machine in c:\windows\system32\drivers\
    and in the registry the image path is \SystemRoot\system32\drivers\ksthunk.sys
    All devices are “working properly” in Windows Device Manager, despite that missing driver. Yamaha MIDI Driver is shown in Control Panel/Sound, and it can be worked with there (opened, closed, configured, etc.).  I have also tried three different USB
    cables (but those shouldn't be an issue since the keyboard is showing up in Windows).
    I was also advised by Yamaha to edit registry key  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32  and remove all midi, midi1, midi2, etc entries, then uninstall and reinstall all drivers. Which I did, but it didn't help.
    So far, no amount of re-installation, event viewing, uninstalling devices, numerous reboots,etc has fixed it. On this machine, that driver just doesn’t hook up to the Yamaha MIDI driver and show up in the stack.
    So it looks like it may be a Windows 7 config problem on my machine, and I'm hoping someone here can give me some advice on how to fix it. The Microsoft forums contain a fair number of users reporting similar problems, some are audio and some are webcam
    related. I've followed those threads, and done several of the suggestions, but haven't found a solution to this one.
    This is a Dell XPS 8300 Windows 7 64-bit PC with all the latest updates, only about six weeks old. I've been struggling with the MIDI problem for most of that time.  I'm an IT professional (network and systems admin), so you can be fairly technical
    in your response.
    Any suggestions will be welcome. Thanks in advance.

    I am so glad I found keyman7's description, since I have exactly the same problem.
    The problem is not related to MIDI output! I have it with a pure USB-MIDI-input device (keyboard), whichs produces "unknown externeal error" every time I try to select it as input. The same thing occurs with a USB-MIDI-Cable.
    I compared the driver details from my system (Dell T1500 windows 7 pro 64 bit) with those of another windows 7 pro 64 bit. On that other system the device works like a charm (so it is not the hardware, either).
    On the other system I find ksthunk.sys in addition to the modules that are listed on my system as well (beeing \windows\system32\drivers\drmk.sys, ..\prtcls.sys, ..\USBAUDIO.sys and \windows\system32\SysFx.dll, ..\WMALFXGFXDSP.dll).
    Can it be some other USB driver is interfering with this driver stack? I have no idea how to figure out which one it could be. Or, it has been suggested in other threads with somewhat similar looking symptoms, ksthunk.sys has been removed as  UpperFilters
    entry?
    Help - please!

  • Generic "usb midi device" in 10.9 / Mavericks

    What does Mavericks need to use the product string from the USB descriptor as the name of the MIDI port?  I have an assortment of USB Audio Class 2.0 compliant audio + MIDI interfaces.  Some behave as they do in Mountain Lion and earlier:  If manufacturer Foo makes a product Bar with audio and MIDI interfaces, then the Audio Midi Setup windows will show an audio interface named Bar, and a MIDI port named Bar.  If you double-click on the MIDI port, it shows the Model, "Bar," and additional information, including the manufacturer Foo, as retrieved from the USB descriptor.  This is expected and desired, especially with devices that unlock features in non-free software.
    However, with Mavericks, some devices (staying with the Foo/Bar example), though the audio interface gets named Bar, show up in the MIDI Studio window of AMS as "USB MIDI Device," and double-clicking reveals the manufacturer and model to be "Generic" and "USB MIDI Device," respectively.  If you use the drop down menu at the top of this window to switch to a different configuration, or define a new one, while the device is connected, it appears in the second configuration as Bar, with the correct manufacturer.
    Now, according to https://developer.apple.com/library/mac/technotes/tn2274/_index.html, the Interface Association Descriptor needs to group all the audio descriptors together, they need to be contiguous, and they need to be ordered by Audio Control, then Audio Streaming, then MIDI streaming.  The device that isn't coming up correctly meets those criteria, so I wonder what else is missing.
    Here's a dump:
    Information for device Bar (VID=0x0f00 PID=0x0baa):
    Connection Information:
    Connection status: Device connected
    Device actual bus speed: High
    Device is hub: No
    Device address: 0x0001
    Current configuration value: 0x01
    Number of open pipes: 5
    Device Descriptor:
    0x12    bLength
    0x01    bDescriptorType
    0x0200    bcdUSB
    0xEF    bDeviceClass   (Miscellaneous device)
    0x02    bDeviceSubClass  
    0x01    bDeviceProtocol  
    0x40    bMaxPacketSize0   (64 Bytes)
    0x0f00    idVendor
    0x0baa    idProduct
    0x0010    bcdDevice
    0x01    iManufacturer   "Foo"
    0x03    iProduct   "Bar"
    0x00    iSerialNumber
    0x02    bNumConfigurations
    Device Qualifier Descriptor:
    0x0A    bLength
    0x06    bDescriptorType
    0x0200    bcdUSB
    0x00    bDeviceClass  
    0x00    bDeviceSubClass  
    0x00    bDeviceProtocol  
    0x40    bMaxPacketSize0   (64 Bytes)
    0x01    bNumConfigurations
    0x00    bReserved
    Configuration Descriptor:
    0x09    bLength
    0x02    bDescriptorType
    0x0169    wTotalLength
    0x05    bNumInterfaces
    0x01    bConfigurationValue
    0x00    iConfiguration
    0x80    bmAttributes   (Bus-powered Device)
    0xFA    bMaxPower   (500 mA)
    Interface Association Descriptor:
    0x08    bLength
    0x0B    bDescriptorType
    0x00    bFirstInterface
    0x04    bInterfaceCount
    0x01    bFunctionClass   (Audio Device Class)
    0x00    bFunctionSubClass  
    0x20    bFunctionProtocol  
    0x00    iFunction
    Interface Descriptor:
    0x09    bLength
    0x04    bDescriptorType
    0x00    bInterfaceNumber
    0x00    bAlternateSetting
    0x00    bNumEndPoints
    0x01    bInterfaceClass   (Audio Device Class)
    0x01    bInterfaceSubClass   (Audio Control Interface)
    0x20    bInterfaceProtocol  
    0x00    iInterface
    AC Interface Header Descriptor:
    0x09    bLength
    0x24    bDescriptorType
    0x01    bDescriptorSubtype
    0x0200    bcdADC
    0x08    bCategory
    0x0087    wTotalLength
    0x00    bmControls
    AC Clock Source Descriptor:
    0x08    bLength
    0x24    bDescriptorType
    0x0A    bDescriptorSubtype
    0x29    bClockID
    0x03    bmAttributes
    0x07    bmControls
    0x00    bAssocTerminal
    0x0E    iClockSource   "Foo Internal Clock"
    AC Clock Selector Descriptor:
    0x08    bLength
    0x24    bDescriptorType
    0x0B    bDescriptorSubtype
    0x28    bClockID
    0x01    bNrInPins
    0x29    baCSourceID(1)
    0x03    bmControls
    0x0D    iClockSelector   "Foo Clock Selector"
    AC Input Terminal Descriptor:
    0x11    bLength
    0x24    bDescriptorType
    0x02    bDescriptorSubtype
    0x02    bTerminalID
    0x0101    wTerminalType   (USB Streaming)
    0x00    bAssocTerminal
    0x28    bCSourceID
    0x04    bNrChannels
    0x00000000    bmChannelConfig
    0x12    iChannelNames
    0x00    bmControls
    0x06    iTerminal   "Bar "
    AC Feature Unit Descriptor:
    0x1A    bLength
    0x24    bDescriptorType
    0x06    bDescriptorSubtype
    0x0A    bUnitID
    0x02    bSourceID
    0x0000000F    bmaControls(0)
    0x0000000F    bmaControls(1)
    0x0000000F    bmaControls(2)
    0x0000000F    bmaControls(3)
    0x0000000F    bmaControls(4)
    0x00    iFeature
    AC Output Terminal Descriptor:
    0x0C    bLength
    0x24    bDescriptorType
    0x03    bDescriptorSubtype
    0x14    bTerminalID
    0x0301    wTerminalType   (Speaker)
    0x00    bAssocTerminal
    0x0A    bSourceID
    0x28    bCSourceID
    0x0000    bmControls
    0x00    iTerminal
    AC Input Terminal Descriptor:
    0x11    bLength
    0x24    bDescriptorType
    0x02    bDescriptorSubtype
    0x01    bTerminalID
    0x0201    wTerminalType   (Microphone)
    0x00    bAssocTerminal
    0x28    bCSourceID
    0x04    bNrChannels
    0x00000000    bmChannelConfig
    0x16    iChannelNames
    0x00    bmControls
    0x00    iTerminal
    AC Feature Unit Descriptor:
    0x1A    bLength
    0x24    bDescriptorType
    0x06    bDescriptorSubtype
    0x0B    bUnitID
    0x01    bSourceID
    0x0000000F    bmaControls(0)
    0x0000000F    bmaControls(1)
    0x0000000F    bmaControls(2)
    0x0000000F    bmaControls(3)
    0x0000000F    bmaControls(4)
    0x00    iFeature
    AC Output Terminal Descriptor:
    0x0C    bLength
    0x24    bDescriptorType
    0x03    bDescriptorSubtype
    0x16    bTerminalID
    0x0101    wTerminalType   (USB Streaming)
    0x00    bAssocTerminal
    0x0B    bSourceID
    0x28    bCSourceID
    0x0000    bmControls
    0x07    iTerminal   "Bar "
    Interface Descriptor:
    0x09    bLength
    0x04    bDescriptorType
    0x01    bInterfaceNumber
    0x00    bAlternateSetting
    0x00    bNumEndPoints
    0x01    bInterfaceClass   (Audio Device Class)
    0x02    bInterfaceSubClass   (Audio Streaming Interface)
    0x20    bInterfaceProtocol  
    0x00    iInterface
    Interface Descriptor:
    0x09    bLength
    0x04    bDescriptorType
    0x01    bInterfaceNumber
    0x01    bAlternateSetting
    0x02    bNumEndPoints
    0x01    bInterfaceClass   (Audio Device Class)
    0x02    bInterfaceSubClass   (Audio Streaming Interface)
    0x20    bInterfaceProtocol  
    0x00    iInterface
    AS Interface Descriptor:
    0x10    bLength
    0x24    bDescriptorType
    0x01    bDescriptorSubtype
    0x02    bTerminalLink
    0x00    bmControls
    0x01    bFormatType
    0x00000001    bmFormats
    0x04    bNrChannels
    0x00000000    bmChannelConfig
    0x12    iChannelNames
    AS Format Type 1 Descriptor:
    0x06    bLength
    0x24    bDescriptorType
    0x02    bDescriptorSubtype
    0x01    bFormatType
    0x04    bSubslotSize
    0x18    bBitResolution   (24 Bits/sample)
    Endpoint Descriptor:
    0x07    bLength
    0x05    bDescriptorType
    0x01    bEndpointAddress   (OUT Endpoint)
    0x05    bmAttributes    (Transfer: Isochronous / Synch: Asynchronous / Usage: Data)
    0x00D0    wMaxPacketSize   (208 Bytes)
    0x01    bInterval
    AS Isochronous Data Endpoint Descriptor:
    0x08    bLength
    0x25    bDescriptorType
    0x01    bDescriptorSubtype
    0x00    bmAttributes
    0x00    bmControls
    0x02    bLockDelayUnits   (Decoded PCM samples)
    0x0008    wLockDelay
    Endpoint Descriptor:
    0x07    bLength
    0x05    bDescriptorType
    0x81    bEndpointAddress   (IN Endpoint)
    0x11    bmAttributes    (Transfer: Isochronous / Synch: None / Usage: Feedback)
    0x0004    wMaxPacketSize   (4 Bytes)
    0x04    bInterval
    Interface Descriptor:
    0x09    bLength
    0x04    bDescriptorType
    0x02    bInterfaceNumber
    0x00    bAlternateSetting
    0x00    bNumEndPoints
    0x01    bInterfaceClass   (Audio Device Class)
    0x02    bInterfaceSubClass   (Audio Streaming Interface)
    0x20    bInterfaceProtocol  
    0x00    iInterface
    Interface Descriptor:
    0x09    bLength
    0x04    bDescriptorType
    0x02    bInterfaceNumber
    0x01    bAlternateSetting
    0x01    bNumEndPoints
    0x01    bInterfaceClass   (Audio Device Class)
    0x02    bInterfaceSubClass   (Audio Streaming Interface)
    0x20    bInterfaceProtocol  
    0x00    iInterface
    AS Interface Descriptor:
    0x10    bLength
    0x24    bDescriptorType
    0x01    bDescriptorSubtype
    0x16    bTerminalLink
    0x00    bmControls
    0x01    bFormatType
    0x00000001    bmFormats
    0x04    bNrChannels
    0x00000000    bmChannelConfig
    0x16    iChannelNames
    AS Format Type 1 Descriptor:
    0x06    bLength
    0x24    bDescriptorType
    0x02    bDescriptorSubtype
    0x01    bFormatType
    0x04    bSubslotSize
    0x18    bBitResolution   (24 Bits/sample)
    Endpoint Descriptor:
    0x07    bLength
    0x05    bDescriptorType
    0x82    bEndpointAddress   (IN Endpoint)
    0x05    bmAttributes    (Transfer: Isochronous / Synch: Asynchronous / Usage: Data)
    0x00D0    wMaxPacketSize   (208 Bytes)
    0x01    bInterval
    AS Isochronous Data Endpoint Descriptor:
    0x08    bLength
    0x25    bDescriptorType
    0x01    bDescriptorSubtype
    0x00    bmAttributes
    0x00    bmControls
    0x02    bLockDelayUnits   (Decoded PCM samples)
    0x0008    wLockDelay
    Interface Descriptor:
    0x09    bLength
    0x04    bDescriptorType
    0x03    bInterfaceNumber
    0x00    bAlternateSetting
    0x02    bNumEndPoints
    0x01    bInterfaceClass   (Audio Device Class)
    0x03    bInterfaceSubClass   (MIDI Streaming Interface)
    0x00    bInterfaceProtocol  
    0x00    iInterface
    MS Interface Header Descriptor:
    0x07    bLength
    0x24    bDescriptorType
    0x01    bDescriptorSubtype
    0x0100    bcdMSC
    0x0041    wTotalLength
    MS MIDI IN Jack Descriptor:
    0x06    bLength
    0x24    bDescriptorType
    0x02    bDescriptorSubtype
    0x01    bJackType
    0x01    bJackID
    0x00    iJack
    MS MIDI IN Jack Descriptor:
    0x06    bLength
    0x24    bDescriptorType
    0x02    bDescriptorSubtype
    0x02    bJackType
    0x02    bJackID
    0x00    iJack
    MS MIDI OUT Jack Descriptor:
    0x09    bLength
    0x24    bDescriptorType
    0x03    bDescriptorSubtype
    0x01    bJackType
    0x03    bJackID
    0x01    bNrInputPins
    0x02    baSourceID(1)
    0x01    baSourcePin(1)
    0x00    iJack
    MS MIDI OUT Jack Descriptor:
    0x09    bLength
    0x24    bDescriptorType
    0x03    bDescriptorSubtype
    0x02    bJackType
    0x04    bJackID
    0x01    bNrInputPins
    0x01    baSourceID(1)
    0x01    baSourcePin(1)
    0x00    iJack
    Endpoint Descriptor (Audio/MIDI):
    0x09    bLength
    0x05    bDescriptorType
    0x02    bEndpointAddress   (OUT Endpoint)
    0x02    bmAttributes    (Transfer: Bulk / Synch: None / Usage: Data)
    0x0200    wMaxPacketSize   (512 Bytes)
    0x00    bInterval
    0x00    bRefresh
    0x00    bSynchAddress
    MS Bulk Data Endpoint Descriptor:
    0x05    bLength
    0x25    bDescriptorType
    0x01    bDescriptorSubtype
    0x01    bNumEmbMIDIJack
    0x01    baAssocJackID(1)
    Endpoint Descriptor (Audio/MIDI):
    0x09    bLength
    0x05    bDescriptorType
    0x83    bEndpointAddress   (IN Endpoint)
    0x02    bmAttributes    (Transfer: Bulk / Synch: None / Usage: Data)
    0x0200    wMaxPacketSize   (512 Bytes)
    0x00    bInterval
    0x00    bRefresh
    0x00    bSynchAddress
    MS Bulk Data Endpoint Descriptor:
    0x05    bLength
    0x25    bDescriptorType
    0x01    bDescriptorSubtype
    0x01    bNumEmbMIDIJack
    0x03    baAssocJackID(1)
    Interface Descriptor:
    0x09    bLength
    0x04    bDescriptorType
    0x04    bInterfaceNumber
    0x00    bAlternateSetting
    0x00    bNumEndPoints
    0xFE    bInterfaceClass   (Application Specific)
    0x01    bInterfaceSubClass  
    0x01    bInterfaceProtocol  
    0x0F    iInterface   "Foo DFU"
    Configuration Descriptor:
    0x09    bLength
    0x02    bDescriptorType
    0x0169    wTotalLength
    0x05    bNumInterfaces
    0x01    bConfigurationValue
    0x00    iConfiguration
    0x80    bmAttributes   (Bus-powered Device)
    0xFA    bMaxPower   (500 mA)
    Interface Association Descriptor:
    0x08    bLength
    0x0B    bDescriptorType
    0x00    bFirstInterface
    0x04    bInterfaceCount
    0x01    bFunctionClass   (Audio Device Class)
    0x00    bFunctionSubClass  
    0x20    bFunctionProtocol  
    0x00    iFunction
    Interface Descriptor:
    0x09    bLength
    0x04    bDescriptorType
    0x00    bInterfaceNumber
    0x00    bAlternateSetting
    0x00    bNumEndPoints
    0x01    bInterfaceClass   (Audio Device Class)
    0x01    bInterfaceSubClass   (Audio Control Interface)
    0x20    bInterfaceProtocol  
    0x00    iInterface
    AC Interface Header Descriptor:
    0x09    bLength
    0x24    bDescriptorType
    0x01    bDescriptorSubtype
    0x0200    bcdADC
    0x08    bCategory
    0x0087    wTotalLength
    0x00    bmControls
    AC Clock Source Descriptor:
    0x08    bLength
    0x24    bDescriptorType
    0x0A    bDescriptorSubtype
    0x29    bClockID
    0x03    bmAttributes
    0x07    bmControls
    0x00    bAssocTerminal
    0x0E    iClockSource   "Foo Internal Clock"
    AC Clock Selector Descriptor:
    0x08    bLength
    0x24    bDescriptorType
    0x0B    bDescriptorSubtype
    0x28    bClockID
    0x01    bNrInPins
    0x29    baCSourceID(1)
    0x03    bmControls
    0x0D    iClockSelector   "Foo Clock Selector"
    AC Input Terminal Descriptor:
    0x11    bLength
    0x24    bDescriptorType
    0x02    bDescriptorSubtype
    0x02    bTerminalID
    0x0101    wTerminalType   (USB Streaming)
    0x00    bAssocTerminal
    0x28    bCSourceID
    0x04    bNrChannels
    0x00000000    bmChannelConfig
    0x12    iChannelNames
    0x00    bmControls
    0x06    iTerminal   "Bar "
    AC Feature Unit Descriptor:
    0x1A    bLength
    0x24    bDescriptorType
    0x06    bDescriptorSubtype
    0x0A    bUnitID
    0x02    bSourceID
    0x0000000F    bmaControls(0)
    0x0000000F    bmaControls(1)
    0x0000000F    bmaControls(2)
    0x0000000F    bmaControls(3)
    0x0000000F    bmaControls(4)
    0x00    iFeature
    AC Output Terminal Descriptor:
    0x0C    bLength
    0x24    bDescriptorType
    0x03    bDescriptorSubtype
    0x14    bTerminalID
    0x0301    wTerminalType   (Speaker)
    0x00    bAssocTerminal
    0x0A    bSourceID
    0x28    bCSourceID
    0x0000    bmControls
    0x00    iTerminal
    AC Input Terminal Descriptor:
    0x11    bLength
    0x24    bDescriptorType
    0x02    bDescriptorSubtype
    0x01    bTerminalID
    0x0201    wTerminalType   (Microphone)
    0x00    bAssocTerminal
    0x28    bCSourceID
    0x04    bNrChannels
    0x00000000    bmChannelConfig
    0x16    iChannelNames
    0x00    bmControls
    0x00    iTerminal
    AC Feature Unit Descriptor:
    0x1A    bLength
    0x24    bDescriptorType
    0x06    bDescriptorSubtype
    0x0B    bUnitID
    0x01    bSourceID
    0x0000000F    bmaControls(0)
    0x0000000F    bmaControls(1)
    0x0000000F    bmaControls(2)
    0x0000000F    bmaControls(3)
    0x0000000F    bmaControls(4)
    0x00    iFeature
    AC Output Terminal Descriptor:
    0x0C    bLength
    0x24    bDescriptorType
    0x03    bDescriptorSubtype
    0x16    bTerminalID
    0x0101    wTerminalType   (USB Streaming)
    0x00    bAssocTerminal
    0x0B    bSourceID
    0x28    bCSourceID
    0x0000    bmControls
    0x07    iTerminal   "Bar "
    Interface Descriptor:
    0x09    bLength
    0x04    bDescriptorType
    0x01    bInterfaceNumber
    0x00    bAlternateSetting
    0x00    bNumEndPoints
    0x01    bInterfaceClass   (Audio Device Class)
    0x02    bInterfaceSubClass   (Audio Streaming Interface)
    0x20    bInterfaceProtocol  
    0x00    iInterface
    Interface Descriptor:
    0x09    bLength
    0x04    bDescriptorType
    0x01    bInterfaceNumber
    0x01    bAlternateSetting
    0x02    bNumEndPoints
    0x01    bInterfaceClass   (Audio Device Class)
    0x02    bInterfaceSubClass   (Audio Streaming Interface)
    0x20    bInterfaceProtocol  
    0x00    iInterface
    AS Interface Descriptor:
    0x10    bLength
    0x24    bDescriptorType
    0x01    bDescriptorSubtype
    0x02    bTerminalLink
    0x00    bmControls
    0x01    bFormatType
    0x00000001    bmFormats
    0x04    bNrChannels
    0x00000000    bmChannelConfig
    0x12    iChannelNames
    AS Format Type 1 Descriptor:
    0x06    bLength
    0x24    bDescriptorType
    0x02    bDescriptorSubtype
    0x01    bFormatType
    0x04    bSubslotSize
    0x18    bBitResolution   (24 Bits/sample)
    Endpoint Descriptor:
    0x07    bLength
    0x05    bDescriptorType
    0x01    bEndpointAddress   (OUT Endpoint)
    0x05    bmAttributes    (Transfer: Isochronous / Synch: Asynchronous / Usage: Data)
    0x00D0    wMaxPacketSize   (208 Bytes)
    0x01    bInterval
    AS Isochronous Data Endpoint Descriptor:
    0x08    bLength
    0x25    bDescriptorType
    0x01    bDescriptorSubtype
    0x00    bmAttributes
    0x00    bmControls
    0x02    bLockDelayUnits   (Decoded PCM samples)
    0x0008    wLockDelay
    Endpoint Descriptor:
    0x07    bLength
    0x05    bDescriptorType
    0x81    bEndpointAddress   (IN Endpoint)
    0x11    bmAttributes    (Transfer: Isochronous / Synch: None / Usage: Feedback)
    0x0004    wMaxPacketSize   (4 Bytes)
    0x04    bInterval
    Interface Descriptor:
    0x09    bLength
    0x04    bDescriptorType
    0x02    bInterfaceNumber
    0x00    bAlternateSetting
    0x00    bNumEndPoints
    0x01    bInterfaceClass   (Audio Device Class)
    0x02    bInterfaceSubClass   (Audio Streaming Interface)
    0x20    bInterfaceProtocol  
    0x00    iInterface
    Interface Descriptor:
    0x09    bLength
    0x04    bDescriptorType
    0x02    bInterfaceNumber
    0x01    bAlternateSetting
    0x01    bNumEndPoints
    0x01    bInterfaceClass   (Audio Device Class)
    0x02    bInterfaceSubClass   (Audio Streaming Interface)
    0x20    bInterfaceProtocol  
    0x00    iInterface
    AS Interface Descriptor:
    0x10    bLength
    0x24    bDescriptorType
    0x01    bDescriptorSubtype
    0x16    bTerminalLink
    0x00    bmControls
    0x01    bFormatType
    0x00000001    bmFormats
    0x04    bNrChannels
    0x00000000    bmChannelConfig
    0x16    iChannelNames
    AS Format Type 1 Descriptor:
    0x06    bLength
    0x24    bDescriptorType
    0x02    bDescriptorSubtype
    0x01    bFormatType
    0x04    bSubslotSize
    0x18    bBitResolution   (24 Bits/sample)
    Endpoint Descriptor:
    0x07    bLength
    0x05    bDescriptorType
    0x82    bEndpoin

    Hi,
    I have same issue with my device, but what's strange  is that it's correctly detected under Yosemite but not under 10.9.4,
    It's always detected as Generic Midi device under 10.9.4
    Do you find the reason ?
    Thx

  • IPod dock connected to both firewire and usb at same time

    I have 3 ipods, 3G 4G 60gb photo 5G 80gb vid. I have a 5G doc and a dual usb / firewire cable. I prefer to manage my 3G and 4G using firewire as it is oh so quicker. However 5G requires usb2 only. I have a Apple 'dual' usb/firewire port cable that at the moment to use I alternate which socket is plugged into the front port of my PowerMac G5 as they are the only spare ports I have.
    I just bought an Iomega Ultra Max which comes with a built in firewire and usb hub that means i now have enough ports to dedicate one of each to the ipods but want to use only one dock and so I would like to plug both the firewire and usb iPod cable into the hub and leave them there connected to the iPod dock. I know it won't cause problems when the 5G is connected as there is no hardware for firewire connection. But the 4G has both.. will I encountering a usb and firewire conenction cause problems and possible damage to the ipod or my PowerMac G5, will the 4G ipod use firewire in prefeance to USB if it will work???

    Hi iPodista;
    I would recommend very strongly that you don't even attempt do this. Generally cross connecting in this fashion is a very good way to get yourself into serious troble.
    Allan

  • Looking for a way to get my Product ID and Vendor ID so I can enable my Radium 49 USB MIDI keyboard to work with Labview 7

    Looking for the Product ID and Vendor ID for my Radium 49 USB MIDI keyboard to work with Labview 7
    Is there a tool to find out the Vendor ID and Product ID for a USB device?
    Example: of what I'm looking for
    The Product ID for National Instruments DAQPad-6020E is 0x12C0. The
    USB vendor ID is 0x3923. This is a 16-bit hexadecimal number(1093)
    (that is decimal 4243).
    Thanks for all the fast responses this newsgroup RULES!!!!!!!!!!!!

    http://digital.ni.com/public.nsf/allkb/335A90747734097886257070006415B9
    How To Find The Vendor and Product ID for USB Devices?
    Primary Software: Driver Software>>NI-VISA
    Primary Software Version: 3.3.1
    Primary Software Fixed Version: N/A
    Secondary Software: N/A
    Problem:
    I want to make an NI-VISA driver that requires the vendor and product ID?
    Solution:
    There is a utility called USBView,
    free from Windows, attached below, which you can use to view what is
    connected to your computer's USB ports. It is necessary to load this
    program and connect the USB device in development. Upon selecting the
    device in USBView, one can then look on the right side of the
    application window to obtain the Product ID and Vendor ID. This will
    allow you to enter in the correct IDs when creating a driver .inf file
    when using the VISA Driver Development Wizard. For more information
    about how to use the VISA Driver Development Wizard see the related
    links below.
    Note: It is necessary to keep the hexadecimal
    (0x####) format. Do not remove the "0x" hexadecimal format preceding
    the ID number. 

  • TS1702 Using an iPad camera connection kit and a MIDI to USB cable to interface a MIDI keyboard with GarageBand. It works flawlessly... almost...

    I'm using an iPad camera connection kit and a MIDI to USB cable to interface a MIDI keyboard with GarageBand. It works flawlessly... until I use the sustain pedal. Once the pedal is depressed while playing a given note, from then on, the pedal itself plays the note every time it is depressed. It's not the keyboard or the pedal. I've tried others. That leaves the app or the connection between the iPad and the keyboard. I find it hard to believe I'm the only person who is experiencing this problem. Anyone have a fix?

    Yes.  There are a ton of write-ups on how to do the connections.   I connect my m-audio Keystation 61 es through the CCK to my iPad and use GarageBand to control it.  Some keyboards require a powered USB hub to make things work.  I use a belkin 4 port hub in my own setup.   Here is a link to tested / verified keyboards that work via the CCK:  http://iosmidi.com/devices/
    Hth

  • Connecting kurzweil sp88 to GB I want to connect my Kurzweil sp88 to GB. The Kurzweil has a baffling array of buttons and possible MIDI channels. It also has the old style MIDI plug ins. I've got the MIDI out connected to my MacBook Pro via USB adapter.

    I have my Kurzweil connected to my MacBook Pro via an adapter (old style MIDI from Kurzweil to USB adapter connecting to Mac). The Kurzweil has a baffling array of buttons and possible MIDI channels. Can anyone please tell me which of the channels I should use? Also, should I leave the MIDI In cable out of the Kurzweil? Thanks for as detailed an answer as possible. If you like you can respond directly to me at [email protected]

    First of all I do not own this keyboard. But a quick look at the manual (found on the internet) says that when first powered up the SP88 is in Internal Sounds mode. Meaning you hear the sounds selected when playing the keyboard. It also stated that the default Midi Transmit Channel is Midi Channel #1.
    Looks like you would need to go to the SP88 Keyboard's MIDI SETUP and simply select LOCAL OFF. Now the keyboard should be ready to transmit Midi Out only and no internal sounds should be heard.
    Next you may or may not need to do this but you might need to go into the Utilities Folder found in your Applications Folder on your Mac and double click AUDIO MIDI SETUP the keyboard Icon. Figure #1 below.
    Next you need to make a physical connection from the Midi Out of the SP88 to the Midi In on your Midi Interface. Figure #3 below. You may need to Click on Add Device first. Figure #2 below.
    In the examples shown below I have a Yamaha Electronic Drum Kit that is Midi Out only... not USB out. I had to plug a Midi cable from the Midi Out Port on the back of my Drum Module to the Midi In Port on the back of my Motu 828 Audio Inferface which is connected to my Mac. Next I created the Audio Interface and Drum Module "Devices" as mentioned above.
    I then double clicked on the Drum Module and made my Midi Out Selections. Figure #4 Below. And once it was setup and the icons closed I used my mouse to draw a virtual cable connection from the Drum Module Out to the Audio Interface In. Figure #3 below. This is how I got my Midi Devices to talk to one another.
    Once you have made your setup as I have outlined create a MIDI Instrument Track in Garageband, select an instrument for example a Piano then Record Enable that track in Garageband and see if you now hear what you are playing. In this example the SP88 is a Midi Controller only and you will only hear sounds selected in Garageband which is what you want.
    Keep in midi your setup may be different than mine. You can keep your SP88 Keyboard on the default Midi Channel #1. That would be a good place to start. Garageband receives Midi on all channels.

  • WIth LabVIEW how do I control an instrument with a RS232 output, using a RS232 to USB converter cable.

    WIth LabVIEW how do I control an instrument with a RS232 output, using a RS232 to USB converter cable since I dont have rs232 ports. I have two instruments that I want to control in this manner. One is an Imada ZPS force gage with RS232 output. The other is a Panasonic HL-G103-S-J laser micrometer sensor which is RS422. I've done considerable LabVIEW programming using GPIB but I have no experience with devices like these. Any tutorial or examples would be greatly appreciated.
    Thanks.
    Solved!
    Go to Solution.

    I understand that you want to control a device which having RS 232 port as output. If so, you can use an USB-RS232 cable from PC to device and you can control or monitor the device.
    See this link http://zone.ni.com/devzone/cda/epd/p/id/2669
    Also, first check the device in hyperterminal and then continue to program in labVIEW. You can find the serial VI's in Instrument I/O.

  • Core MIDI from iPad Mini to Mac via lightning USB charging cable

    I want to use some of my Core MIDI compatible iPad Apps to control Logic Pro and other DAWs on my MacBook Pro via USB (Core MIDI over WiFi has unmanageable latency issues).
    I read on various forums that it is possible to use Core MIDI via USB using the Apple Camera Connection Kit or Lightning to Mini USB adapter, but doesn't this simply work with the included Lightning to USB charging cable?

    Image Capture is a built-in program and should be in your Applications folder, Aperture I bought from the Mac App Store.
    For Simple Transfer it's an iPad app, so you would download it on your iPad from the app store.

Maybe you are looking for