JMF support for mvBluefox USB2.0 camera

I trying to access a MatrixVision Bluefox USB 2.0 camera with JMF. However, it doesn't seem to detect it. Does the camera driver have to conform to any particular protocol or interfacing standard for it to work with JMF? How can I get the camera and JMF to work together?
http://www.matrix-vision.com/products/hardware/mvbluefox.php
Thank you.

Okay, here's what I think I think I know.
From what I understand, there are two video camera formats currently in use. VFW (Video for Windows) format is what most web cams / TV tuner cards use. They are analog input, so a constant stream of data that's coming in.
The other, Windows DirectShow, is a digital API that uses DirectX to give programs direct access to video memory that the camera writes to. IE, there is a buffer that you read from and display.
I know that VFW is supported through JMF, but from the nature of what DirectShow is, I imagine it is not. With that in mind, I would imagine that you need some sort of WDS-to-VFWs converter to be able to use your WDS-compliant camera. Or maybe it has a VFW mode you can put it in.
Regardless, if you can get to the VFW stream of the camera, JMF should play it.

Similar Messages

  • Support for HD (1280x720px) web-cams

    Does JMF 2.1.1e support HD format (e.g. 1280x720 px, 30 FPS) web-cams?
    After a recent purchase of a Netbook with web-cam, I finally got around to playing about with using JMF to access the inbuilt cam and grab sequences of frames (for time-lapse animations). Unfortunately the inbuilt camera is 640x480 and of otherwise low quality (as you might expect of a camera supplied as standard in a Netbook). Am considering buying a HD web-cam, but need to assure myself I am not spending $70+ for a camera that is not compatible with JMF.
    Did a quick search of the forum for '720' and got 5 hits that were not relevant.
    Side note: Checked the Netbook could take 4 hours worth of frames every 2 seconds and store them (into a Zip archive) at 640x480 using the internal camera on battery. It still had 31% charge left. It will be interesting to see how storing the images performs in terms of charge, using an USB based HD camera. ;)

    AndrewThompson64 wrote:
    captfoss wrote:
    Andrew, if you don't mind learning something new, I think your best bet would be Adobe Flex. It's free and it's got excellent support for web cams... I'd take a look at some ActionScript code and see if it's something you think you could pick up fairly easily.Might be the way to go. ..That is probably a cleaner approach, but in the end I settled for a hack.
    - A simple Java app. that will click a point on screen repeatedly using Robot.
    - VLC media player connecting to the web cam and offering a snapshot button to click.
    Connected to the new 'Fission'(1) webcam, I get 1600x1200 snapshots in .png format that I can further utilize to create either 1600x1200 4:3 ratio animations, or by cropping a little of the top & bottom and down-sizing, a 720p 16:9 ratio animation. I'd probably do the latter using JAI from an Ant task.
    A test last night suggested it could only grab an image around once every 4 seconds. I set it for every 2 seconds over two hours, and while I expected 3600 images, I ended up with just 1836. Given the still camera could only manage one shot every 9 seconds or so, this still allows me to keep the same basic rate of progress of the animation at double the FPS (15->30) that I was seeking. The only other concern is the total length of animation obtainable via. a single battery pack. The 2 hour run took battery from 100% to 41%, but I am hoping I can stretch it to (at least) a 4 hour shoot using a 4 second delay.
    1) I had never heard of the Fission brand before I saw it. I got it from Aldi(2) for $25 Aus. It supports a phenomenal range of formats, some astonishingly high.
    2) Not sure if Aldi operates in your neck of the woods. They are a German based group that supplies groceries real cheap, and offer whatever other little nick-knacks that are also cheap.

  • How does jmf support for avi format

    I have written code to play audio and video filesusing JMF..My code is able to run only in mp3 and other 2 formats, but it is failed to run other formats like avi, mov etc..Now i need to play my video file which is their in avi format. Please tell me how does my code supports in other formats too...I had searched in google and it has given me some sites, but i didnt get any solution from them.

    Ok, I rant about this same thing again
    AVI is a file format. Think of it like a can. Either you have a can openor or not, but just because you have the ability to open the can doesn't mean you can necessarily eat what's inside.
    AVI is simply a file format that you can embed audio and video data into. The video itself is going to be encoded using some video encoding, like, RGB or DivX or something like that.
    JMF supports the AVI filetype, but it only supports a few video encodings for the AVI.
    [http://java.sun.com/javase/technologies/desktop/media/jmf/2.1.1/formats.html]
    Same with MOV files. Again, a filetype. You need to make sure the encoding inside the file is supported by JMF, otherwise it won't be able to play it.

  • Raw Support for Leica X Vario Camera?

    Is There Raw (DNG) support a Leica X Vario camera?  I've currently dowloaded LR 5.7 and tried tio import two DNG files from the camera and the software won't read them.  any idea about what is going on.
    Need help
    Regards

    Not yet: https://helpx.adobe.com/creative-suite/kb/camera-raw-plug-supported-cameras.html
    5.7 has added some Leicas. You may have to wait for the next release.
    Nobody here knows when the next release is due.

  • How do I get RAW Support for Panasonic Lumix L10 camera?

    Aperture 2.1 still does not support Panasonic Lumix L10 RAW nor jpegs (Adobe 4.3 RAW plug-in already does). Is there a workaround? Any help?

    cyntlee
    from
    http://www.apple.com/aperture/features/100.html
    Baseline DNG support
    Shooting RAW on a camera or camera back not natively supported by Mac OS X? Aperture lets you work with DNGs created from the RAW files generated by most cameras, increasing its breadth of support.
    Regards
    TD

  • Sigma raw (x3f) support for Merrill series of cameras . . .

    Just wondering when and if Adobe is going to support it in camera raw. I've been a Photoshop user since version 2 or 3 - would really like to continue with it.
    Thanks and look forward to your response!

    Actually They do they use  a Converter that changes all Camera formats to DNG Format. That Photoshop actually can read. It works with all versions of Adobe Photoshop. The people from adobe claim  (When I wrote and asked why they simply couldn't use the Camera Raw system That Apple updates every month or two to add new Cameras) That NEF and the other format that Nikon, Cannon Sony are just something they just made up and are not legitimate file formats. (despite their being used by their respective companies for years.)
    Each new version of Photoshop comes with a new version of this converter built in. And in the the past Until they came out with their way over priced subscription service you had to upgrade to a new version of PS in order to use your new camera. I have to note that Lightroom4 apparently doesn't need the converter.(on Mac they evidently uses built in Apple's Raw Converter).
    Go to Adobe's website > support and put in search box DNG Converter. 

  • 1411 Support for Sony XC-ST50 Camera

    I am trying to use a Sonly XC-ST50 camera with a 1411. Are there camera files to support this? If not, can I use the camera with the 1411?

    I am trying to Sony XC-ST50 Camera with PCI-1411  IMAQ card.
    I use RS-170 format, but I have a trouble.
    The error code is: 0XBFF6001F      "  Cannot detect recognizeable video source "
     Can you help me ?
    Thanks!!
    C.B Kuo

  • Camera RAW image support for Pentax K100D

    Hi,
    Firstly, let me just say I have a MacBook Pro which came preloaded with Tiger. A month or so ago I upgraded to Leopard and I have applied all the available Apple software update.
    I recently got a Pentax K100D digital SLR camera capable of taking images in RAW format (the pentax saves these with a .PEF file extension) and I have been trying to view these images in Leopard. I read the article below, which says that Leopard provides system-level support for the Pentax K100D camera RAW format.
    *Digital camera RAW formats supported by Mac OS X 10.5*
    http://docs.info.apple.com/article.html?artnum=306835
    Now, my problem is that I cannot seem to be able to open the .PEF files with neither Quick Look, Preview, iPhoto or Aperture. Basically, none of these programs seem to be able to display my .PEF files. Aperture says 'unsupported image format'.
    I have installed the software that came with my Pentax (i.e. Pentax Photo Browser and Pentax Photo Laboratory) and these applications can display the .PEF images just fine. For what it's worth, I installed this software before I upgraded to Leopard.
    If I right-click on a .PEF file in Finder, the only programs listed in the Open context menu are the above two Pentax applications.
    So, what am I missing? Clearly something seems to be screwy in my Leopard set up. Is there some way to 'repair' the RAW image support in Leopard??
    I would appreciate any help in fixing this as I would really like to start working with RAW images in Aperture and iPhoto.
    Finally, just be aware that I am not an experienced Mac user. I have always used Windows until now and so... if you have a fix for this I would really appreciate a slightly more elaborate response.
    Thanks in advance,
    Eddie

    I have done a little more research on this...
    As it turns out, my camera is a Pentax K100D Super - not a K100D. The K100D Super is not listed as one of the supported camera RAW formats in the aforementioned article. So I guess this means that my camera is as yet unsupported. Sigh...

  • What is going on with tethered support for the canon 70D?

    I just saw the release of Lightroom CC, and it appears that the Canon 70D is still not supported for tethering. This camera has been on the market for almost 2 years, and there have been several releases of Lightroom, including this major one. What is going on here? This is a major feature that is missing and a huge inconvenience to workaround. When will this be fixed? What is holding it up?

    This information is a couple of years old, so I can not vouch for how current it is.  But it may be worth a try.
    ColdFusion's Dedicated Account Managers
    October 9, 2007
    http://www.forta.com/blog/index.cfm/2007/10/9/ColdFusions-Dedicated-Account-Managers
    Just a reminder (especially for those of you whose experiences when calling Adobe sales regarding ColdFusion were anything less than stellar) ...
    Adobe has dedicated ColdFusion Account Managers (in the U.S. and Canada), all they do is ColdFusion, and they can help with purchasing, EULA and pricing questions, and more. Here are the contact details:
    For users in AK, AR, AZ, CA, CO, HI, IA, ID, IL, KS, LA, MN, MO, MT, ND, NE, NM, NV, OK, OR, SD, TX, UT, WA, WI, WY (West of the Mississippi), ping Jason Graves at [email protected] or call (858) 847-7541.
    For users in AL, CT, DC, DE, FL, GA, IN, KY, MD, MA, ME, MI, MS, NC, NH, NJ, NY, OH, PA, RI, SC, TN, VA, VT, WV (East of the Mississippi) as well as Eastern Canada & Ontario, ping Dominick Conte at [email protected] or call (858) 847-7451.
    [revised]

  • Now Here! Support for the Canon PowerShot G1

    After much trial and error, I have figured out how to support the Canon PowerShot G1.
    I started with the settings for the hacked un-supported G2 (thanks to user jpugsley for this message: http://discussions.apple.com/thread.jspa?threadID=262930). Then I read the source code to the open source dcraw.c command line raw convertor. There I found Adobe's translation values for the G1 which has a CYGM filter array. I'd say this opens up opportunities for many other CYGM cameras to be supported.
    The premul values seem to affect the color balance of the images. Adjusting the values very slightly may be helpful. I don't know what most of the other values are. The m2 array values came from dcraw.c You probably shouldn't touch those.
    The images seem to open fine in Preview and Aperture. I hope Apple officially supports this camera soon (Aperture 1.1?).
    How To:
    All you have to do is paste the following XML into this file (make sure you save a backup of the file first). Rebooting is NOT needed:
    /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ImageIO.fram ework/Versions/Current/Resources/Raw.plist
    <key>Canon-PowerShot G1</key>
    <dict>
    <key>blackReplace</key> <true/>
    <key>black</key> <integer>32</integer>
    <key>max</key> <integer>1023</integer>
    <key>white</key> <integer>1023</integer>
    <key>premul0</key> <real>1.00</real> <key>premul1</key> <real>1.2</real> <key>premul2</key> <real>1.1</real> <key>premul3</key> <real>1.11</real>
    <key>m1</key>
    <array>
    <real>1.0507</real> <real>-0.4281</real> <real>-0.0161</real>
    <real>-0.5540</real> <real>1.2938</real> <real>0.2909</real>
    <real>-0.1205</real> <real>0.1844</real> <real>0.8335</real>
    <real>-0.1566</real> <real>1.1051</real> <real>0.0577</real>
    </array>
    <key>m2</key>
    <array>
    <real>-0.4778</real> <real>0.9467</real> <real>0.2172</real>
    <real>0.4743</real> <real>-0.1141</real> <real>0.4344</real>
    <real>-0.5146</real> <real>0.9908</real> <real>0.6077</real>
    <real>-0.1566</real> <real>1.1051</real> <real>0.0577</real>
    </array>
    <key>mc</key> <real>0.83355</real>
    <key>otrc</key>
    <array>
    <real>0.00</real> <real>0.090</real> <real>1.467</real> <real>0.260</real> <real>1.842</real> <real>0.652</real> <real>1.040</real> <real>0.538</real>
    </array>
    </dict>

    This is stellar.
    Thanks. It wasn't as hard as I thought it would be... I didn't think it was possible at first.
    is this in fact all
    there is to supporting a new camera RAW format --
    providing a translation array in a plist file?
    What follows is pure speculation... I really don't have a solid understanding of this at all.
    Seems like all you have to do is get these Camera->XYZ trans values (trans may stand for transform or translate). The image is essentially monochrome with color filters over it. Some cameras use RGB filters, looks like Apple has supported a lot of those. Some are CYGM, so far Apple hasn't supported any of those. Apple has supported the Sony DSC F828 which is RGBE where E stands for Emerald. Total guess, but each set of three values in the m2 array is associated with a color. (9 total for RGB and 12 for CYGM and RGBE). Guessing, each of these sets of three values probably is used to calculate a response curve for each color.
    Basically, when dcraw.c provided twelve values, I began to poke around Raw.plist and discovered the Sony F828 camera also had 12 values in its m2 array. It also had 4 premul (pre-multiplier) values, one for each set of 3 m2 values. So I took a leap of faith that CYGM could be supported because after all, a color is just a color. Does the computer really care if the value represents emerald or magenta? This produced a promising image but color was way off. I had to then tweak each premul value to bring the color in. Those values don't seem to be linear. A minor adjustment can either dramatically change everything or have no noticeable effect.
    Are all RAW formats essentially supported via simply a
    declarative filter array, or did it just happen to
    work for G1 RAW, and other formats are different?
    My amateur guess is many cameras are similar and a few stand out as different. For example, I'm guessing the Foveon cameras are an example of a different sort of RAW file. Thats just a guess based on looking at dcraw.c.
    if this is all there is to
    supporting a new RAW format, I wonder
    - why more of the RAW formats weren't supported in the first place.
    To get you to buy a fancy new camera on the Apple Store? Lazyness? Not enough time? Lack of cooperation from the manufacturer? All of the above?
    - why RAW formats haven't been progressively added
    since the Aperture release.
    Seems like they could have had support for dozens of additional cameras. This took me only a matter of hours to figure out. Someone with a deep understanding could have done this in minutes.
    The real time sink is when you almost have the colors correct and you are endlessly tweaking trying to get them perfect... as you will see, the colors will be fine in certain exposures and way off in others. Look at daylight vs. tungsten photos. It may take many hours to get the values of the camera correct to customers exacting standards. We, the photographers, are very picky.
    Why don't we just contact Canon, Nikon, etc. and get
    their translation values?
    There are values for 83 additional cameras that aren't supported by Apple in the dcraw.c file. That's a place to start.

  • Lightroom support for Fuji X-Trans???

    From DP review:
    Just came back from D-Clic photo show in Montreal and had the chance to talk with Billy from Fuji Guys. He asked me if I was happy with my X-Pro1 and I said yes, very happy BUT would like Adobe and others to better support it (or at all in the case of Aperture...). I expected him to play it safe but he actually acknowledged the problem right away and told me that they recently signed a non-disclosure agreement with both Adobe and Apple and provided them with specs for supporting the X-Trans sensor !
    He said he is also pushing strong with Fuji to add support for TIFF in the camera so that could be another good thing for some.
    Lets hope this leads to progress...
    http://forums.dpreview.com/forums/thread/3286994
    Hope this is the real deal…

    I had contact with Adobe support on Friday. They are aware of the problem, but could not confirm me that it will be fixed in LR 4.4. We need more pressure!!!

  • Lost camera raw support for canon 1ds markI in mountain lion

    I seem to have lost system support for camera raw files for the original Canon 1ds (what you might call the markI). There's been two recent raw support updates, and I'm not sure if it occured with the first for those two updates or with update to Mountain Lion itself (which I recently clean-installed). I noticed it after the first raw support update (Digital Camera RAW Compatibility Update 4.01) but it could have happend with Mountain Lion install and I just didn't notice. In any case, I definitely don't have support for the camera raw files, finder shows only the generic TIFF icon thumnail (the raw files from the markI 1ds were of the extension .TIF, before canon moved on to .cr2 format..). Preview and Aperture can preview the file but without any custom white balance or other info stored with the raw file from camera.
    Anybody else experience this or know fix?
    Thanks!
    For anyone wanting and willing to test on their machine, I'll post a link to a test raw file.... hmm, apparently this support forum does not allow for the linclusion of a link to an image file, but I'll see if it allows for a link to a zipped folder with image inside... I suppose I wouldn't download a .zip file myself but for anyone braver than I:
    http://laglj.com/2012hirez/1dsTestFile.zip
    Thanks,
    Lane
    laglj.com

    Lane,
    That latest raw update also shows supported devices. The EOS-1Ds is still shown as supported by Mountain Lion in the knowledge base article that accompanies it. Bump!
    I wonder if using Disk Utility and verify/fix permissions may restore your RAW capability.
    Don't have Aperture or Lightroom.
    I installed the recent raw updates into 10.8.2. The DB5W2360.TIF file has a generic Preview icon. Graphic Converter 8.3.1 opens .cr2 files, and it opened this TIF file nicely as well. GC is willing to modify white balance with a condition that it cannot be done in place, and must be exported to a different format.
    Not much help, I know.

  • Is there Camera RAW support for Lightroom 4.4 and Canon 7D Mark ii?

    I need Camera RAW support for Lightroom 4.4 and Canon 7D Mark ii.  Is there a Camera RAW version for me? 

    Thanks for your help.  I checked out DNG on YouTube and understand more
    about it.  I downloaded the DNG converter and transferred in files from my
    camera.  Then I imported into Lightroom.  It works!   Thanks again.
    On Wed, Nov 19, 2014 at 5:56 PM, Jeff Schewe <[email protected]>

  • Camera Raw Support for Canon 7D MkII

    Just trying to get some idea if I should spend the $99.00 to buy Aperture from the Apple Store.  This might sound a little over the top, but the work flow I miss by not having RAW support in Lightroom is worth the expense of buying Aperture.
    I do find it very disappointing that Adobe have not as yet provided support for the new Canon 7D MkII.  This will be a VERY popular camera.
    More importantly I find this tardiness on Adobe's part very disappointing because they market CC buy saying "You will always have up to date software".  When you consider Apple and Google Picasa have both already supported the Canon 7D MkII.  I might add they both had support for the camera within days of it's release on 31 of Oct.
    So after my little rant.
    Can anybody from Adobe advise when we will see Camera Raw support the new Canon 7DMkII?
    Even if it is in Beta form I would be very happy to be a Beta tester.  I have very extensive experience in testing software and would be prepared to do structured Beta testing.  I would be very happy if someone from Adobe Labs would contact me for the purpose of Beta testing Camera Raw support for the 7D MkII.
    Kind Regards
    Tom Croll

    Thanks ssprengel, you have clearly put into words what is currently reality at Adobe, and confirmed my suspicion of Aperture being a dead product.  Although Google's Picasa is not dead.
    I do realize Adobe Products are very well developed and software does take time to perfect before it gets released.  I have been in the software development game for 35 years
    But Camera RAW is an adjunct to Lightroom, Photoshop, Premier Pro etc.  As such the support for new camera models should be a relatively simple exercise and should not be held up by other R&D on the products that Camera Raw plugs into.  I believe they have in the past released updates to Camera Raw that essentially was just for new camera models.  I do realize I could be wrong on this point, but I fail to see why they can't achieve this outcome.
    Also, as I said Adobe Market Creative Cloud membership saying you will always be up to date. Or words to that effect.
    To have an Adobe support person get upset because he has a large number of people pestering Adobe, and not him personally, trying to get ans answer as to the timing of the release of support for a new camera model, quite frankly is totally unacceptable.  Not acceptable to the customers and not acceptable to the poor support person who has to handle disgruntled customers due to poor planning on Adobe's part.
    In my original post I made a very serious offer to do Beta Testing on support for the Canon 7DMkII Raw files.  But when i last checked with Adobe Labs the current Beta does not include support for this camera.
    There maybe extenuating circumstances around the timely supply of this support.  Like when did Canon provide the Specs for the 7D MkII and are those specs so different from other currently supported models.   Even some feedback as to what the problem is, would help us understand.
    I hope I have expressed my thoughts objectively and hope this discussion stream will get to management at Adobe.  In fact I am very inclined to ensure it does get to senior management.  I don't want to start writing a personal letter to the Chairman of Adobe's Board, but sometimes things do need a shake up.
    Kind Regards
    Tom Croll

  • Does JMF Support multilingual absolute paths for video playback?

    Hi everyone,
    I hope I can find some answer here.
    Does JMF supports multilingual paths for videos? E.g. I have a video located by the following URL:
    G:\video\Stürmische\video.mp4
    When I try to open this video by JMF, I get the following Exception: Problem playing video+
    javax.media.NoPlayerException: Cannot find a Player for :file:/G:/video/Stürmische/video.mp4_
    When I use the same video.mp4 file with path containing only simple latin letters, it's played normally.
    Is there any problem with JMF regarding to multilingual paths?
    Many thanks,
    Armine

    868310 wrote:
    I assume that it's a JMF cons. and IMHO, multilingual support for video paths/names should be added in it.Several things...
    1) JMF is designed to play both local files and RTP/RTSP file sources. As such, it uses URLs as resource locators. It makes perfect sense to make that design decision.
    2) URL encoding only allows alphanumeric characters and a handful of special characters. Considering the internet was invented by the United States army and our keyboards don't have those symbols, it makes perfect sense to make that design decision.
    3) Most importantly, JMF hasn't been updated since 2002 and development has been completely discontinued... so "multilingual support" won't ever be added to it.
    And it isn't multilingual support you're asking for, it's support for non-ASCII characters.
    It is my understanding that you can take a path like:
    G:\video\Stürmische\video.mp4
    Run it through some encoding procedure, and come out with a usable URL like:
    G:%5Cvideo%5CSt%FCrmische%5Cvideo.mp4
    Which I got by using the encoder on the following website:
    http://www.blooberry.com/indexdot/html/topics/urlencoding.htm
    Coincidentally, had you done the research that I suggested you do, you might have learned that Java already has something built in to handle encoding non-compliant URLs for you.
    http://download.oracle.com/javase/1.5.0/docs/api/java/net/URLEncoder.html
    So, I'd expect you could use the URLEncoder class to implement suggestion #3 from my previous post.

Maybe you are looking for