Vista thinks bluetooth 'radio is "USB Human Interface Device"

Hi all,
I've been having this problem for a couple of weeks now; it came straight out of the blue - perhaps triggered by an update? I'm running Windows Vista Ultimate (still in trial period, actually, as I haven't bothered to buy it yet) on a 17'' MBP, and everything has been working fine as far as Mac hardware... or was... until my bluetooth radio suddenly stopped showing up.
My Bluetooth devices still connect fine (well, only my wireless keyboard which doesn't need to be paired, my Mighty Mouse isn't working now), but do not show up in the Bluetooth Devices control panel applet. My radio shows up as a 'USB Human Interface Device' in the Device Manager, and no amount of uninstalling/reinstalling my BC drivcers is helping.
This is becoming a problem for me; I do a lot of gaming and need my Mighty Mouse.
All help is REALLY appreciated!
Thanks,
Bookworm

It IS, but so are all USB Mice, Keyboards, etc,etc,etc. My issue is that because Windows Vista cannot specify it as being an Apple Bluetooth Radio, I cannot control it - and thus cannot use it to setup my mouse. The issue seems to be that the drivers for the Apple Bluetooth Radio are not being used when my adapter is detected - instead, Windows is defaulting to a generic USB driver which would work for most USB devices - but doesn't allow things that require specific device types to work, such as pairing with bluetooth.
Happily, I have managed to obtain a fairly good USB mouse... the problem is that this ***** up a much-needed accessible USB port. I have to get a port extender or something...
Message was edited by: Bookworm9405

Similar Messages

  • T61 USB Human Interface Device drivers not loading after undocking

    I have a T61 and after I undock (correct method, by pressing the eject button on the docking station and waiting for it to turn green) the laptop from my advanced docking station, the external mouse does not work.  More specifically, this is the error message that I can see in the USB Human Interface Device with the yellow ! in Device Manager.
    "Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38) "
    Is there a fix for this? If I reboot the laptop then I can get my external mouse to work because the drivers  can load, but I don't want to have to reboot after undocking.

    Regarding your keyboard problem, it seems to be a very low-level problem. The driver cannot access the Control Registers on the Keyboard. By going down from your error message to the lowest level, one can see that it's probably a simple "outb" operation (write data on a specified address, shouldn't fail if the address is correct...) that doesn't succeed.
    So I think you defintely need to look in your BIOS if you didn't deactivate something when upgrading, or messed with some address space, or many things I cannot think of right now.
    Good luck

  • USB Human Interface Device

    Hi, I have an annoying yellow ! in my Device Manager for the USB Human Interface Device. Can anyone point me to the correct driver to remove it please?
    Pete

    Hi Laurent, I got your email with files and replied with my findings. However my email to you was bounced back to me as undeliverable, so I will reply on here.
    I tried the files you sent; but unfortunately they had no effect using 64 bit Windows. I have since gone back to 32 bit; but not because of the problem with the human interface; I have decided to go back because my printer and my scanner manufacturers do not and will not be providing 64 bit drivers, and not only that; there are still other things that 64 bit are just not ready for.
    So having said that; reverting back to 32 bit has enabled your previous version to work perfectly as expected. I do still have my 64 bit setup on a spare hard drive, so I can go back to that anytime if you wish me to try something else; being that it will be inevitable to use 64 bit Windows in the not too distant future.
    Regards
    Pete

  • USB Human Interface Device (HID) in LabVIEW

    How do you write/read to/from an HID USB device in LabVIEW? Note that this
    is not a mouse or keyboard but does use the standard Windows XP HID driver.

    Matt,
    Neither of the bellow worked. I believe this answer's why:
    http://digital.ni.com/public.nsf/websearch/273BB58D3B52CE6886256F3B00714D03
    The device registers as an HID and the above link says that I would have to
    change firmware to fix the problem. That's not going to happen because the
    hardware is made by another Mfg.
    Any other ideas for communication to my USB/HID device? All I need to do is
    write and read data from it. The device driver shows an hid.dll. I wonder
    if I could call the DLL to accomplish what I need to do. The problem is
    that I don't know where to find documentation to setup the DLL call.
    - Neal
    "Matt_S." <[email protected]> wrote in message
    news:[email protected]..
    > That depends. If this device is part of the USB TMC standard, you can do
    > the steps in the following KB.
    >
    > http://digital.ni.com/public.nsf/websearch/044FA220F32774ED86256DB3005850CA
    >
    > If not, use VISA to create a USB Raw device driver for it.
    >
    > http://digital.ni.com/public.nsf/allkb/E3A2C4FE42D7ED0D86256DB7005C65C9
    >
    > Best of Luck!
    > -Matt S.

  • Human Interface device for 6280

    Any add-on software to activate human interface device for Nokia 6280? Blue tooth section is greyed, but some other cheaper brands than Nokia have this active! Any help!

    Cheers, there is also a more simple one here which works out of box but it's functionality is very limited.
    http://today.java.net/pub/a/today/2006/07/06/java-and-usb.html?page=2
    > And, as a last resort, that Java daemon (I believe
    the APC UPS installation program installs and starts
    one, anyway) can always be decompiled and inspected
    (although I would have qualms about the legality of
    it).
    I'm curious to know more about this.
    I've just looked in the powerChute instilation directory,
    I can't see anything java'y of java'ish. Can you elaborate on this a little more please.
    Thanks again for all the help. Still holding out for HID although your links are good and appreciated.

  • Human Interface Device (HID) API

    Hi All
    I searched but, I can't find a Java Human Interface Device (HID) API for windows.
    Does such a thing exist?
    Thanks Very Much

    Cheers, there is also a more simple one here which works out of box but it's functionality is very limited.
    http://today.java.net/pub/a/today/2006/07/06/java-and-usb.html?page=2
    > And, as a last resort, that Java daemon (I believe
    the APC UPS installation program installs and starts
    one, anyway) can always be decompiled and inspected
    (although I would have qualms about the legality of
    it).
    I'm curious to know more about this.
    I've just looked in the powerChute instilation directory,
    I can't see anything java'y of java'ish. Can you elaborate on this a little more please.
    Thanks again for all the help. Still holding out for HID although your links are good and appreciated.

  • Human Interface Devices/To​shiba Hot Key Driver/Win​dows 8

    HELP! My computer is only 6 months old and my external mouse all of sudden stopped working, after many call and many research I have found that under my device manager, under Human Interface Devices, Hotkeys Driver has an exclamation point on it, the driver may be corrupt. I have requested the update the driver option but it is not updating. How can I fix the hotkey driver please? I need help. Toshiba tech support won't help unless I have them $170.00 I don't have that, I am a full time student? I am still in shock that Toshiba won't help me fix a problem on their software, I am so disappointed!!! Any help will be appreciated.
    Thank you!
    SZ

    Hi This is a program I use to find driver up dates. It's freeware. Not sure if the forum approves this program, so I better add use this at your own risk. Hasn't caused me any problems.http://download.cnet.com/SlimDrivers-Free/3000-185​13_4-75279940.html?tag=dre
    I Love my Satellite L775D-S7222 Laptop. Some days you're the windshield, Some days you're the bug. The Computer world is crazy. If you have answers to computer problems, pass them forward.

  • ThinkPad T60 USB Ports and Human Interface Devices

    Hi. I have a Lenovo ThinkPad T60 and an HID gadget.  When I try plugging it into the left vertical USB port, it installs and works just fine; however, when I try plugging it into either USB port on the right side, it always malfunctions and doesn't install or work correctly.  Is there any solution to this error, and what's exactly causing it? I've tried the following:
    -Updating laptop BIOS
    -Reinstalling all USB drivers
    -Reinstalling the driver of the device
    Thanks in advance for some advice.

    I believe you'll find the right side usb ports are part of a separate usb card that connects to the motherboard with a cable, the ports on the left go directly into the motherboard. If the ones on the right aren't working, then you may have a bad usb card. This part can be easily damaged too, bumping a device while plugged in can damage it. 
    The easiest way to test it would probably be to get a known good usb card and plug it into your motherboard. I believe this can be done temporarily as a test with only partial disassembly of the laptop. Replacing the part would require removing the systemboard/frame assembly from the lower case. I believe you could test if a new card solves the problem by removing only the keyboard and plugging it into the motherboard. It's hard to be sure without knowing exactly which T60 you have, and without having one in front of me to refresh my memory.
    ThinkPad W-510 i7-820QM(1.73-3.06GHz) Quad Core... ThinkPad T500, T9900, 8gb SSD...FrankNpad T-60p/61p (X9000 2.8ghz) 8gb SSD ips FlexView...ThinkPad T-61p (T9300 2.5ghz) 8gb ram...Thinkpad X-61 Tablet 4gb ram...ThinkPad A-31 (1.9ghz P4 1.5gb ram)

  • Bluetooth HID (human interface device) on Droid Charge

    You can use a bluetooth mouse and keyboard with the Charge.
    But does anyone know if this is just a Samsung thing?
    A froyo/gingerbread thing?

    Please tell me that you have successfully used a bluetooth keyboard with the Samsung Charge, OR at this point it is still only a rumor.  I've been trying to pair a specifically designed android keyboard and it is not working.  The internet is FULL of frustration from people trying to do the same.  I have not found ONE person who has been successful.
    The charge does recognize the existence of the keyboard, but when asked to pair, it gives a pop up that lasts all of one second, that instructs entering code, but that not only can't be entered in one second, it can't even be read in one second.  FAIL.
    It is quite possible that the "exclusively Samsung" bluetooth profile does not ACTUALLY allow bluetooth keyboards>..
    Anyone????

  • Bluetooth radio missing, not found in device manager - Probook 4530s

    I have a Probook 4530s with Windows 7 Ultimate, 64-bit installed on it. A little while ago I wanted to use bluetooth for networking, but thee was no bluetooth adapter in the Network Connections window. I looked in Device Manager next, thinking maybe there was something wrong with the driver, but no bluetooth adapter showed. I've tried rebooting, turning it off and on in BIOS, and even just pressing the wireless button, but nothing has worked.
    Along with Windows, I have Mac and Ubuntu installed. Bluetooth dooesn't work on any of the operating systems, but it used to.
    Any help with getting my adapter working again would be appreciated.

    Hi,
    Its more than likely Ubuntu that has caused the problem. I can't say for sure though as I've never used the model of laptop you have. With the WiFi/Bluetooth portion of the hardware its not just a driver that keeps the hardware running correctly, there is a firmware as well. I managed to kill my WiFi card for a while when I was messing with Linux OS's.  Find out the precise model of the bluetooth adapter on your laptop (it may be a WiFi/Bluetooth combo card?) then start searching the Linux communities for information about the firmware for the cards. 
    Sorry I can't be more helpful. 
    DCampbell

  • My Bluetooth radio isn't in Device Manager in Windows 7 64 anymore.

    My Bluetooth radio isn't even in Device Manager in Windows 7 64 bit after being there and working before.  I also have updated to the most recent Boot Camp drivers, but to avail to get Bluetooth working in Windows 7 anymore.

    does it show up in control panel ?

  • My old Intel-Based iMac is no longer recognizing USB wired input devices; it only recognizes Bluetooth.  What happened?

    My friend's old Intel-Based iMac is no longer recognizing USB-wired input devices (Kensington TrackBall, Logitech Mouse) plugged into any USB slot at the back of the computer.
    They were working before and for many years.
    All of a sudden, A pop up window came up. IT said no Bluetooth mice could be found.  We don't know what set off that window to pop up and look for a WL mouse. It never has before in the 5 or more years my friend has been using this computer.
    I supplied a wireless Apple mouse and his is back running again.
    But want to know why his USB-input devices (Except his keyboard) are not being recognized. He would prefer to use his  Trackpad (Wired), but can't find anything in SYstem PReferences to allow that.  The computer only seems to want a Bluetooth input device.
    Anyone have an idea what happened and if this can be reversed?
    I think he is still running Mac OS X 10.5.8.

    Hi Carol, lets try this...
    reset FW bus, same goes for USB reset...
    Reset the Firewire bus
    If your Firewire or USB isn't recognizing any device.  A solution which has worked for some whose hard drive became invisible in 10.4 was simply to follow these four steps to reset the Firewire/USB bus:
    1. Shut the machine down.
    2. UNPLUG the power lead to the computer and any firewire/USB drive/devices.
    3. leave it for 10 minutes.
    4. Connect back up and reboot.
    http://www.macmaps.com/firewirebug2.html

  • Package for DVC80 USB Video Interface

    Gents;
    Some info sources say that a linux app can be provided which will permit the DVC80 to  respond to NTSC video camera input.
    The DVC80 operates well in windows, permitting capture in Irfanview and a program called Dazzle.
    The following data describes a possible application which may be compatible with arch.  The interface in video apps, especially from USB, can be daunting.  Audio is also provided on NTSC basis for camera input via the DVC80 input connectors(stereo).
    The data below describes how it might be built in linux:
    ===============================================================
    Readme for kernel 2.6.x Linux device driver for the Zoran/Nogatech USBVision Video Grabber
    Author: Joerg Heckenbach <[email protected]>
    Homepage: http://www.emuit.com/webcam.html (Dwaine Garden)
    INTRODUCTION:
    This is a driver for the USB video bridge USBVision from Zoran/Nogatech, a USB-only cable used in many "webcam" devices.
    It supports streaming and capture of color or monochrome video via the Video4Linux
    API. Most V4L apps are compatible with it, but a few video-conferencing programs
    do not work yet.
    If you need more information, please visit the Zoran/Nogatech homepage at the above URL.
    usbvision-0.9.6 is the first prerelease of the 1.0 driver. I did many changes in the code and I hope I
    didn't break working features on different devices. The decompression is completed. Just from time to
    time there are some black or white error pixels in the image on slower machines. Maybe it is a timing problem
    in the isoc interrupt routine. We stay a third of the time in interrupt and so it is likely, that the parser
    is called twice. Let me cleanup the routine for performance, move the parser to user-context and add a lock.
    For 2.6x kernels we can use the saa7111 from the kernel tree, so the make will not compile the saa7111-new
    for these kernels.  The bt819-new.c is not coded to 2.6. kernel yet.
    I have tested the driver with kernel 2.6.1, 2.6.2 to 2.6.7 with devices "Hauppauge WinTV USB FM 1" and
    "Pixelview PlayTV USB Pro FM" on a 600MHz PII system.
    WHAT YOU NEED:
    - If you want to help with the development, get the chip's specification docs at
      http://www.emuit.com/webcam.html
    - A Video4Linux compatible frame grabber program (I recommend xawtv or Kwintv)
      xawtv is available at:  http://www.in-berlin.de/User/kraxel/xawtv.html
    - Radio Application to take advantage of the radio tuner. (some of the devices)
      GQradio is available at:  http://gqmpeg.sourceforge.net/radio.html
    HOW TO INSTALL THE DEVICE DRIVER:
    First way (The easy one)
    It works with most modern standard installations.
    a) In the usbvision directory do
       make; make install; modprobe usbvision
    b) Start your video application.
    c) Enjoy.
    If c) doesn't work, something went wrong ;-)
    Second way (Not as easy as the first one)
    You need this, if either usb-, i2c-, tuner- or v4l-support is missing in your kernel.
    a) cp the following files into the directory /usr/src/linux/drivers/usb/media
        usbvision.c
        usbvision.h
        saa7113.c
        i2c-algo-usb.c
        i2c-algo-usb.h
        usbvision_ioctl.h
    c) In the makefile of the dir /usr/src/linux/drivers/usb, look for the line "obj-$(CONFIG_USB_IBMCAM)    +=media/",
    insert an additional line then added the line for the usbvision driver
       obj-$(CONFIG_USB_USBVISION)    += media/
    e) Add the line to the makefile in /usr/src/linux/driver/usb/media/
      obj-$(CONFIG_USB_USBVISION)     += usbvision.o saa7113.o i2c-algo-usb.o
    f) Edit file /usr/src/linux/drivers/usb/media/Kconfig   
       Paste the following lines below after the entry for the IBMCAM.
    ---------------------------- Begin Paste ------------------------------
    config USB_USBVISION
        tristate "USB Zoran/Nogatech USBVision Video Grabber Support"
        depends on USB && VIDEO_DEV && I2C && VIDEO_BT848 && VIDEO_DPC
        ---help---
            Say Y here if you want to connect a Nogatech NT100x, or a Zoran
            ZR36504/ZR36505 chipset based video/tv/radio grabber, to your
            computer's USB port.
            For more information, read <file:Documentation/usb/usbvision.txt>.
            This driver needs the following support: Please enable (Y or M in config)
              Video For Linux API
            I2C API. 
            BT484 Device Support
            DPC7146 demonstration board Device Support
            This code is also available as a module ( = code which can be
            inserted in and removed from the running kernel whenever you want).
            The module will be called usbvision.o.  If you want to compile it as a
            module, say M here and read <file:Documentation/modules.txt>. This
            video grabber has several configuration options which can be specified
            when you load the module.  Read <file:Documentation/usb/usbvision.txt> to
            learn more.
    ---------------------------- End of Paste -----------------------------
    h) If it is not already there (it usually is), create the video device:
        mknod /dev/video c 81 0
    i) Sometimes /dev/video is a symlink to /dev/video0
    You will have to set permissions on this device to allow you to read/write
    from it:
        chmod 666 /dev/video
        chmod 666 /dev/video0 (if necessary)
    When configuring the kernel choose Zoran/Nogatech USBVISION video support as
    module. You are going to need also to select i2c and v4l, and if your
    device have tuner you need to compile also BT848 support or other modules
    that compile the tuner.o module.
        a) Do a make modules, make modules_install.
        b) If the USB Support and the Video4Linux was compiled as modules.
           modprobe usbcore.o
               modprobe usb-uhci.o  <OR>  modprobe ohci-hcd.o
           modprobe videodev.o
        b) Install the modules:
              modprobe usbvision- For a great radio application, try GQradio.
           The usbvision module will also load the i2c-algo-usb, i2c-core, saa7111, saa7113.
    VIDEO PLAYERS FOR PLAYING VIDEO OUPUT
    Here is the setting to get the TV tuner working with mplayer.  It does software video scaling, so you can have full screen mode with the USBVision driver.
        mplayer tv:// -tv channel=43:driver=v4l:input=0:outfmt=rgb24:norm=ntsc:height=240:width=320 -flip
    Here is the setting to get the TV tuner working with xawtv.
        xawtv -c /dev/video0
    USBVISION MODULE PARAMETERS:
      NAME: isocMode
      TYPE: integer (0x03, 0x14, 0x60)
      DEFAULT: 0x60
      DESC:  The isocMode is the format mode of the data that is transmitted on the isocronous
      pipe via USB. It is not depending on the connected video-hardware. Default is 0x14.
            YUV422          0x03
            YUV420          0x14
            COMPRESSION     0x60    Enable compression for full framerate.
      NAME: debug
      TYPE: bitmask
      DEFAULT: 0
      DESC: You don't need this option unless you are a developer. If you are a developer then
      you will see in the code what values do what. This is a bit mask, and you can combine any
      number of bits to produce what you want:
           bit 2    debug procfs
           bit 3    debug video ioctl
           bit 4    debug video io
           bit 5    debug radio io
           bit 7    debug usb frame header
           bit 8    debug probe and disconnect
           bit 9    debug irq
           bit 10   debug handling of isochronus transfer
           bit 11   debug parsing of usb data
           bit 12   debug handling of scratch
           bit 13   debug utility functions
           bit 14   debug i2c stuff
      NAME: flags
      TYPE: bitmask
      DEFAULT: 0
      DESC: This is a bit mask, and you can combine any number of bits to produce what you want.
      Usually you don't want any of extra features this option provides:
           bit 0    FLAGS_RETRY_VIDIOCSYNC     This bit allows to retry failed
                                               VIDIOCSYNC ioctls without failing.
                                               Will work with xawtv, will not
                                               with xrealproducer. Default is
                                               not set.
           bit 1    FLAGS_MONOCHROME           Activates monochrome (b/w) mode.
           bit 2    FLAGS_DISPLAY_HINTS        Shows colored pixels which have
                                               magic meaning to developers.
           bit 3    FLAGS_OVERLAY_STATS        Shows tiny numbers on screen,
                                               useful only for debugging.
           bit 4    FLAGS_FORCE_TESTPATTERN    Shows blue screen with numbers.
           bit 5    FLAGS_SEPARATE_FRAMES      Shows each frame separately, as
                                               it was received from the camera.
                                               Default (not set) is to mix the
                                               preceding frame in to compensate
                                               for occasional loss of Isoc data
                                               on high frame rates.
           bit 6    FLAGS_CLEAN_FRAMES         Forces "cleanup" of each frame
                                               prior to use; relevant only if
                                               FLAGS_SEPARATE_FRAMES is set.
                                               Default is not to clean frames,
                                               this is a little faster but may
                                               produce flicker if frame rate is
                                               too high and Isoc data gets lost.
      NAME: dga
      TYPE: integer (0-1) boolean
      DEFAULT: 1
      DESC: This will set the option for DGA video to either Yes or No.  Default is 1.
      NAME: PowerOnAtOpen
      TYPE: integer (0-1) boolean
      DEFAULT: 1
      DESC: This will set the device to power on automatically when opened.  Default is 1.
      NAME: SwitchSVideoInput
      TYPE: integer (0-1) boolean
      DEFAULT: 0
      DESC: To help people with Black and White output with using s-video input.  Some cables and input devices are wired differently. 
            If you are getting a black and white image when using the S-Video input.  Set this parameter to 1.  Default is 0, since most
        devices do not have this problem.
      NAME: CustomDevice
      TYPE: string
      DEFAULT: NULL
      DESC: This will set a new Custom device
      EXAMPLE: "0x0573 0x4D31 0 7113 3 PAL 1 1 1 5 -1 -1 -1 -1 -1"
      FORMAT: "idVendor idProduct Interface Codec    VideoChannels VideoNorm AudioChannels Radio
                 Tuner TunerType Vin_Reg1 Vin_Reg2 X_Offset Y_Offset Dvi_yuv"
            Codec:
                7111
                7113
                819
            VideoNorm:
                P or PAL
                S or SECAM
                N or NTSC
            TunerType: (!!!use the NUMBER not the name)  see latest in "/usr/src/linux/drivers/media/video/tuner.h"
                TUNER_TEMIC_PAL                 0   /* 4002 FH5 (3X 7756, 9483) */
                TUNER_PHILIPS_PAL_I             1
                TUNER_PHILIPS_NTSC              2
                TUNER_PHILIPS_SECAM             3   /* you must actively select B/G, L, L` */
                TUNER_ABSENT                    4
                TUNER_PHILIPS_PAL               5
                TUNER_TEMIC_NTSC                6   /* 4032 FY5 (3X 7004, 9498, 9789)  */
                TUNER_TEMIC_PAL_I               7   /* 4062 FY5 (3X 8501, 9957)        */
                TUNER_TEMIC_4036FY5_NTSC         8   /* 4036 FY5 (3X 1223, 1981, 7686)  */
                TUNER_ALPS_TSBH1_NTSC              9
                TUNER_ALPS_TSBE1_PAL             10
                TUNER_ALPS_TSBB5_PAL_I             11
                TUNER_ALPS_TSBE5_PAL             12
                TUNER_ALPS_TSBC5_PAL             13
                TUNER_TEMIC_4006FH5_PAL            14  /* 4006 FH5 (3X 9500, 9501, 7291)     */
                TUNER_ALPS_TSHC6_NTSC             15
                TUNER_TEMIC_PAL_DK            16  /* 4016 FY5 (3X 1392, 1393)     */
                TUNER_PHILIPS_NTSC_M            17
                TUNER_TEMIC_4066FY5_PAL_I           18  /* 4066 FY5 (3X 7032, 7035) */
                TUNER_TEMIC_4006FN5_MULTI_PAL       19  /* B/G, I and D/K autodetected (3X 7595, 7606, 7657)*/
                TUNER_TEMIC_4009FR5_PAL             20  /* incl. FM radio (3X 7607, 7488, 7711)*/
                TUNER_TEMIC_4039FR5_NTSC            21  /* incl. FM radio (3X 7246, 7578, 7732)*/
                TUNER_TEMIC_4046FM5                 22  /* you must actively select B/G, D/K, I, L, L` !  (3X 7804, 7806, 8103, 8104)*/
                TUNER_PHILIPS_PAL_DK            23
                TUNER_PHILIPS_FQ1216ME            24  /* you must actively select B/G/D/K, I, L, L` */
                TUNER_LG_PAL_I_FM            25
                TUNER_LG_PAL_I                26
                TUNER_LG_NTSC_FM            27
                TUNER_LG_PAL_FM                28
                TUNER_LG_PAL                29
                TUNER_TEMIC_4009FN5_MULTI_PAL_FM    30  /* B/G, I and D/K autodetected (3X 8155, 8160, 8163)*/
                TUNER_SHARP_2U5JF5540_NTSC          31
                TUNER_Samsung_PAL_TCPM9091PD27         32
                TUNER_MT2032                 33
                TUNER_TEMIC_4106FH5             34  /* 4106 FH5 (3X 7808, 7865)*/
                TUNER_TEMIC_4012FY5            35  /* 4012 FY5 (3X 0971, 1099)*/
                TUNER_TEMIC_4136FY5            36  /* 4136 FY5 (3X 7708, 7746)*/
                TUNER_LG_PAL_NEW_TAPC           37
                TUNER_PHILIPS_FM1216ME_MK3          38
                TUNER_LG_NTSC_NEW_TAPC           39
                TUNER_HITACHI_NTSC               40
                TUNER_PHILIPS_PAL_MK             41
                TUNER_PHILIPS_ATSC               42
                TUNER_PHILIPS_FM1236_MK3         43
                TUNER_PHILIPS_4IN1               44  /* ATI TV Wonder Pro - Conexant */
                TUNER_MICROTUNE_4049FM5          45
                TUNER_LG_NTSC_TAPE               47
                TUNER_TNF_8831BGFF               48
    ================================================================================================
    FINAL NOTE:
    If your device isn't known, add it to usbvision_device_data and usbvision_table in usbvision.h.
    You can speed up tuner detection, when adding "options tuner addr=your_addr" to /etc/modules.conf.
    If your device isn't known, edit line (modprobe usbvision CustomDevice="0x0573 0x4D31 0 7113 3 PAL 1 1 1 5 -1 -1 -1 -1 -1")
    in 'usbvision.rc' file then 'usbvision.rc start'
    also edit "etc/rc.d/init.d/usbvision" if you use it
    Please tell me your experience ([email protected]), or contact ([email protected]).
    =============================================================
    As described it is a PAL device.  There are options for TV included.
    I am interested in single frame capture and video stream capture via the camera input connectors(NTSC-stereo audio).  My camera is a PIXERA and has video NTSC output.
    The following is reference to the USBVISION tar.gz which seems to require ZORAN in the kernel.  It used to be called ZORAN/NOGATECH. 
    It would seem necessary to enable ZORAN in the latest kernel in order to implement the device.  Other requirements are likely as well.
    Perhaps a pkg could be built but certainly seems a big challenge!
    My DVC80 is recognized in USB.
    Hopefully, it can be done in arch!
    EDIT:The tar.gz reference below:
    file:///root/Desktop/usbvision-0.9.8.2.tar.gz

    I use this one with Windows 7:http://www.chronos.com.tw/Product/E/2/USB%20Movie%20Editor/USB%20Movie%20Editor.htm
    It worked bad with out of box Windows 7.
    But after all updates it works very well and stable.
    A nice thing is that it has little USB extender cable included. So it is less harmful for laptop usb port.

  • Best USB-MIDI interface to connect Yamaha MFC10 foot controller to MacBook Air

    Hi guys,
    I would like to buy a Yamaha MFC10 MIDI foot controller. It has a number of advantages over other foot controllers. For instance: you can connect up to four additional expression pedals to the foot controller, which is something I might need in the future, so it's better to invest in this product so I am prepared for the future.
    The thing is, I want to connect this MIDI controller to a USB port on my MacBook Air. What is the best USB-MIDI interface to get in this situation?
    I love to hear your thoughts on this.
    Cheers!
    Best regards,
    Theo

    Did you set midi communications to USB? I think by default it may be set to the MIDI port on the back. You need USB.
    Press Utilities, then MIDI (F6).

  • M-Audio Mobile Pre USB audio interface compatibility w/ FCP

    I am trying to do voiceovers in FCP with my mic connected to the XLR input on a M-Audio Mobile Pre USB audio interface.
    The first time I did this, even though I got a signal in System Preferences audio input, I would get no signal in the Voiceover Tool window in FCP. I know I chose the correct source, input and rate for the device. I rebooted and it worked. Then on another day a reboot would not make it work. Now I can’t make it work again. Upon opening FCP with the USB interface connected OSX crashed. This almost never happens ether with the system in general or since I installed FCP 5.1. This has happened twice. I also started this whole process by updating to the newest driver for the M-Audio device. I liked the sound I got when it worked so any help with this problem would be appreciated.

    Thanks for that link...that's what I saw months ago, and I realize I got a few of the specifics mixed up. UNFORTUNATELY, I tried those tips and I still have the exact same problem. I also went to M-Audio and downloaded the most recent driver. I did a variety of starts and re-starts where the unit was connected or not upon start up...whether phantom power was on or off at start up, etc etc. And by start up I mean both starting GB only, and/or starting up my Mac. I tested using the interface through both of the USB ports. All yield the same result. The only thing I didn't test yet is changing the USB cable itself.
    Any more thoughts? You think the interface is bad?

Maybe you are looking for