10-bit RGB really 8-bit?

When I capture 10-bit RGB files in Final Cut Pro they show up as 8-bit files when I bring them into Shake. Any ideas as to why this happens?

Interesting. I wasn't sure if Final Cut Pro was capturing 10-bit files properly or not. I've been reading that FCP can only render RGB in 8-bit so I wasn't sure if it was really capturing 10 bit files as 8-bit. I am able to create 10-bit RGB files in After Effects and Shake will default to working in 16-bits when I import them.
Do you have experience with Glue Tools? Does it allow one to export all the 10-bit data as DPX files?

Similar Messages

  • If you change the image mode of this image from 8-bit RGB image to Grayscale mode while in PSCS – what will the new Pixel Count be?

    If you change the image mode of this image from 8-bit RGB image to Grayscale
    mode while in PSCS – what will the new Pixel Count be?

    If you mean by Pixel count the number of pixels, this will not change. The image will have the same size thus the same number of pixels.

  • Monochrome DMK23G445 shown in MAX as 32-bit RGB

    I have Monocrome Gigait ethernet camera DMK23G445.
    When I press Grab in MAX under the image it shows it as 32-bit RGB camera(picture).
    As a result I could not process it in my program as it requires 8-but mono picture.
    Why MAX shows it like this? I have IMAQ-dx 4.0 drivers.

    In attribute it shows as options only 10-12-14-16 bit.
    The strange thing is tha in MAX it shows this camera in 2 places and currently only bottom one works(yesterday middleone worked as well but picture was very much distorted). Middle one yesterday showed picture as 8 bit, bottom one as in attached screenshot.
    If you try to open camera in Vision Builder then in the list of IEEE1394 and ET cameras only middle camera is shown. I could not use it as it does not work...
    Attachments:
    1.JPG ‏151 KB

  • How to view 16-bit RGB information?

    I'm using Photoshop CS4 v. 11.0.  I open a .tif which is 16-bit RGB.  Photoshop recognizes it as 16-bit.  The tab over the picture says RGB/16*. (I don't understand the asterisk)  Image>Mode confirms that it is 16 Bits/Channel.
    However the info panel only shows the 8-bit RGB values (0,255). The panel options do not include a bit depth selection.  How can I see the RGB values, perhaps (0,32767), in the .tif image using Photoshop?

    Simple answer this one - In your info panel, there is a tiny eyedropper beside the RGB values. If you click, this it gives you various options. Including the ability to read 16 bit values.

  • Can I save an image as a 16-bit RGB JPG file?

    Is it possible to save an image as a 16-bit RGB file? I know I can work in RGB mode in 16-bits per channel and "save as" a JPG, but when re-opening the file it appears to have been converted to 8-bit.  My research seems to show a consistent theme that JPG is by definition an 8-bit format.  Nonetheless, I have a supplier who wants their images delivered in 16-bit or 32-bit RGB in JPG format.  Is this possible. If not, what might they mean by this?

    Not possible. Jpg does not support anything higher than 8 bit. I believe png supports 16 bits per channel, other than that you could send a tiff file, but be prepared for any in compatibilities, you may need to change some settings and try again.

  • Help processing a byte[] of packed (24-bit) RGB values

    I'm having some difficulty converting a byte[] of RGB values to a JPEG using the ImageIO classes. The byte[] contains 24-bit RGB values and I'd like to somehow get this data into a format that can be saved to a JPEG File (presumably with JPEGImageEncoder?)
    Any advice on where to get started would be greatly appreciated!

    the ImageIO class wants a BufferedImage, which in my opinion is the easiest way to work with image files.
    You first construct a BufferedImage object, like this:
    BufferedImage img = new BufferedImage(width, height, BufferedImage.TYPE_INT_RGB);Width and height you should know, they are the dimensions of the image in pixels.
    You can use the setRGB() method to set a single pixel of the image, something like this:
    byte[] rgb; // get this somewhere, it is your byte array of RGB values
    // index into the rgb array
    int i = 0;
    for(int y = 0; y < height; y++){
         for(int x = 0; x < width; x++, i+= 3){
              byte a = 0;
              byte r = rgb;
              byte g = rgb[i+1];
              byte b = rgb[i+2];
              int pix = ((a << 24) + (r << 16) + ([g << 8) + b);
              img.setRGB(x,y,pix);
    This is typed from memory, I may have made a mistake somewhere. Right now I assume the byte array contains only RGB components, that's why I leave alpha 0. If you ever have a 32 bit image, you can adapt this code easily.
    After you have the BufferedImage, you can simply write it as a JPEG file using ImageIO.write().

  • Ps CS6 Problem: Lighting Effects filter quantises 16-bit height-map to 8-bit in a 16-bit document

    I've edited this message: one complaint has been removed - it was my mistake - conroy.
    Photoshop 13.0.1
    OS X 10.6.8
    16 bits per channel RGB mode.
    The Lighting Effects filter quantises the optional height-map channel to 8 bits, which can result in a very obvious terraced-slopes appearance and moiré.
    (Adobe, please do not simply reply with "you should be using 13.0.4" unless that actually fixes the problem.)

    Alpha channels are 16-bit in a 16-bit per channel document. As Christoph said, selections are limited to 8-bit, so if you make a channel from a selection then that channel will have 8-bit quantisation.
    Here is an example of Lighting Effects filter using a channel containing a 16-bit radial gradient as a height-map, and where the filter is quantising the height values to 8-bit.

  • Our Setup: XP 64-bit or Vista 64-bit?

    Let me break down the situation here:
    A year ago we built a computer from scratch. I'll list some of the basic specs here:
    A nice Tyan motherboard (can't remember the model)
    4 GB of RAM (4 x 1 GB sticks)
    an nVidia GeForce 8800 GTX video card
    TWO Dual-Core AMD Opteron 270 (2.0 GHz) - [dualcore + dualprocessor]
    10k Raptor hard drive for operating system
    3x500GB RAID as "video" hard drive
    Adobe Premiere Pro CS3
    Now, after building this computer over a year ago, Windows Vista had JUST been released, so we weren't interested in installing Vista yet, due to not knowing how great it would be. So with this awesome computer, we ended up just installing regular 32-bit ole' Windows XP on it.
    Now it's been a year, and the computer is in need of a good format. We're trying to decide which operating system to install now. Obviously, XP32 is the SAFEST choice, but probably the slowest, considering we have dual-core dual-processor here and 4GB of RAM, and want to take advantage of all of this.
    So I guess we're kind of wondering what to expect if we go to XP64 or Vista64. Which is going to give us better performance? This computer is basically ONLY for video editing, not much else. Literally installing Adobe's software, and maybe small needed things like Nero and whatnot. I haven't really heard too much about XP64, and a lot of the stuff I hear about Vista is conflicted. AND also keep in mind that next month, XP will be upgrading to SP3 and Vista will be upgrading to SP1, and VistaSP1 sounds quite promising.
    All of the hardware and software we have apparently has Vista drivers (I've checked online), so there should be no concern here.
    So it's simple. We're on XP32 at the moment. Should we go up to XP64 or Vista64, and if so, and which one and why?

    Adobe Dynamic Link "Import After Effects comp" fails in Vista Business 64 bit
    I am posting this, since in my search, I found no other reference to this problem on the web. If someone has a fix then great. Should someone have the same issue, it may confirm a glitch running CS3 Production Premium in Vista 64 bit. I run XP 64 bit and Vista 64 bit on a dual boot (same hardware) so it was easy for me to troubleshoot the " serious error" Premier gave me when I tried to import an After Effects comp through Dynamic link in Premier Pro. Below is the scenario.
    1. The following sequence for Adobe Dynamic Link>New After Effects Composition works fine in both Win XP Pro 64 bit and Vista Business 64 bit :
    I open After Effects CS3 to an untitled composition then leave AFX running in the background. Next I Open Premier Pro CS3 to create a new project in the following format:
    Standard NTSC video (4:3 interlaced). 48kHz (16 bit) audio.
    Editing mode: DV NTSC
    Timebase: 29.97 fps
    Video Settings
    Frame size: 720h 480v (0.900)
    Frame rate: 29.97 frames/second
    Pixel Aspect Ratio: D1/DV NTSC (0.9)
    Fields: Lower Field First
    In Premier Pro CS3 I choose File> Adobe Dynamic Link>New After Effects Composition. My project window now has a 11 sec dynamic link linked comp 0 movie file which is black video. I return to After Effects and find a new comp named "dynamic link Linked Comp". I import a Microsoft DV 720 X 480 48.000kHz/16 bit stereo 30 sec video into the AFX Project window then drag it to the timeline. I return to Premier Pro and find the 30 sec movie in the Premier timeline. I am able to make changes to the movie in AFX and they reflect in the Premier timeline.
    2. The next sequence for Adobe Dynamic Link>Import After Effects fails running on my Vista Business 64 bit OS. It works perfectly running on Win XP Pro 64 bit.
    I open After Effects, import an NTSC Microsoft DV 720 X 480 48.000kHz/16 bit stereo 30 sec video, drag video into the "create a new comp button" at the bottom of the project file then save the comp. I open a new Standard NTSC video (4:3 interlaced) project in Premier Pro CS3 then choose File>Adobe Dynamic Link>Import After Effects Composition. I get an Adobe Premier Alert " Sorry, a serious error has occurred that requires Adobe Premier Pro to shut down. We will attempt to save your current project." I click OK and Premier closes.
    System: Dual boot Win XP Pro 64 bit and Vista Business 64bit, 3.2 GHz Pentium D 940 Dual core, Asus P5WD2 Premium motherboard, 8 gig Crucial DDR-2 667 ram, WD 5000AAKS and WD 7500AAKS SATA hard drives, Dual Asus EAX300 Video cards.
    The above comparisons were done on a fresh load of both OS's with the latest drivers and the only programs I had installed were Microsoft Office 2003 Pro, Quicktime, Firefox and Acrobat. I have all the latest CS3 updates for Production Premium and the latest Windows updates.

  • 64-Bit Essbase on 32-bit BOX

    Hi All,
    I would like to clarify on few points.
    THere have been a lot of post sover here on the support matrix of Oracle EPM 11.1.1.3. I have gone through the Matrx and have a few queries.I would like to know whether my understanding is right.
    Which one is compatible
    32-Bit Essbase on 32-Bit Box - Compatible
    32-Bit Essbase on 64-Bit Box - No additional benefits at essbase level. Can we expect an increase in performance at OS level?
    64-Bit Essbase on 64-Bit Box - Improved performance both at essbase level and OS level.
    Now, Can we install a 64-Bit Essbase on a 32-Bit Box? I don't think this is suggested option to go for. But does it really supports?
    Need your imputs on this.

    Amarnath wrote:
    Hi All,
    I would like to clarify on few points.
    THere have been a lot of post sover here on the support matrix of Oracle EPM 11.1.1.3. I have gone through the Matrx and have a few queries.I would like to know whether my understanding is right.
    Which one is compatible
    32-Bit Essbase on 32-Bit Box - Compatible
    32-Bit Essbase on 64-Bit Box - No additional benefits at essbase level. Can we expect an increase in performance at OS level?
    64-Bit Essbase on 64-Bit Box - Improved performance both at essbase level and OS level.
    Now, Can we install a 64-Bit Essbase on a 32-Bit Box? I don't think this is suggested option to go for. But does it really supports?
    Need your imputs on this.Hi,
    32-Bit Essbase on 64-Bit Box - No additional benefits at essbase level. Can we expect an increase in performance at OS level?You shouldn't expect an increase in performance.
    Now, Can we install a 64-Bit Essbase on a 32-Bit Box? I don't think this is suggested option to go for. But does it really supports?No, I doubt the installer would even allow it.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Labview 64-bit running with 32-bit addons

    I ran into memory problem loading som data files, and I tried a workaround by installing Labview 64-bit, but found that the add-ons was not installed with it. 
    Now I needed to use sound and vibrations toolkit, so (being maybe a little too creative) I copied that toolkit over to the 64-bit Labview folder and everything seems to run.
    I can load the files and do my data analysis with no errors.
    Now the problem is that I don't really get how a 32-bit add-on can access the memory from the 64-bit core Labview. Does anyone have any ideas on why its running and why I don't get a memory access error.
    The results looks ok, but I don’t really trust them, due to the above mentioned problem in accessing memory  between 32-bit and 64-bit.
    regards
    Henrik
    Solved!
    Go to Solution.

    Hi Henrik.
    When using LabVIEW 32-bit on a 64-bit machine, all your VIs would run through the Windows-on-Windows emulation layer (WOW64) and this is also why we still have memory limitations on a 64-bit OS.
    When you are using LabVIEW 64-bit, and using a 32-bit toolkit, what's actually happening is the 64-bit LabVIEW kernel is recompiling the 32-bit VI into a 64-bit VI. Doing this changes the inherent memory characteristics and performance of the Sound and Vibration VI's (and all 32-bit VIs, for that matter). The newly converted 64-bit VI's, then, are being executed in the native 64-bit LabVIEW kernel.
    However, I would strongly advise you to install the toolkit the normal way. In the following document, you can see, that the Sound and Vibration Toolkit / Measurement Suite is in fact supported by a 64-bit version of LabVIEW.
    National Instruments Product Compatibility for Microsoft Windows 7
    After you install LabVIEW, you need to reinstall all your add-ons and drivers in order for that toolkit / driver to work with LabVIEW. When we install toolkits / driver, we only install support for the LabVIEW versions installed at that time.
    I hope this helps.
    Best Regards
    Alex E. Petersen
    Certified LabVIEW Developer (CLD)
    Application Engineer
    Image House PantoInspect

  • Microsoft Access Windows 2008 64 Bit CFMX 9 64 Bit

    We are migrating from CFMX 7 on a 32 bit Windows server to Windows 2008 64 bit with CFMX 9 standard 64 bit edition.  When attempting to add Microsoft Access datasources, I received the Unable to update the NT registry. Variable DRIVERPATH is undefined error.  I search the net and tried the recommended solutions I came across including installing Microsoft Office 2010 64 bit.  None of the solutions have worked.  I eventually came across the error "architecture mismatch between the driver and application" when trying some of the different solutions.
    Most, if not all, of the recommendations I found online were dealing with Windows 7 or Vista, not server operating systems though.
    This is a shared hosting server for our clients and some of them have older web sites implemented in Access and are reluctant to switch to SQL server because of the size and scope of their databases and it is really us who wish to migrate them in order to move to newer hardware and decommission the older server(s).
    Has anyone successfully defined Access datasources within CFMX 64 bit on a server operating system and if so, how?  Thanks in advance!

    I beleive that yes you can install 32 bit ColdFusion on a 64 bit system.  The troulbe is that you also need a 32 bit JVM and a 32 bit IIS.
    As I understand it, with IE 7 you can mix and match 32 bit and 64 bit, but in IE 6 it has to be all one or the other.
    I have read discussions on the hows and whys and the ins and outs of installing 32 bit CF on 64 bit systems.
    What I do not recall is if you can install both 32 bit and 64 bit CF on a single machine.  You may be able to with a multi-home or J2EE configuration of CF enterprise.

  • 32 bit on a 64 bit

    Hi. I have a slight problem. I am on a 64 bit laptop, but I am trying to run something that requires a 32 bit jdk and 32 bit jre. I only have a 32 bit jdk installed, and this is set up properly. Now this was set in the CLASSPATH variable
    .;C:\Program Files (x86)\Java\jre6\lib\ext\QTJava.zip
    And there is also a QTJAVA set to
    C:\Program Files (x86)\Java\jre6\lib\ext\QTJava.zip
    I dont know what set these jre's, but they are my 64 bit ones. I dont have a QTJava.zip in my 32 bit jre location. I dont appear to have any jre set in my path variable.
    Long story short, what I am trying to do is not working because apparently, the jre is being called before the jdk. Is there anyway i could stop this from happening?
    Cheers

    What is your real problem? 32 vs 64 bit doesn't really matter for most Java applications unless you are using native libraries via JNI or need lots of heap space. The QT libraries are just added by QuickTime and unless you are actually using them for something specific, you can safely ignore their existance.

  • Need conversion mechanism for converting 24 bit image to 16 bit

    In my java project I need to convert 24 bit image to 16 bit image. I don't have any clue. Please provide me the option to implement it.
    Thanks,
    jai

    That doesn't tell me much, and I know what you're talking about. I doubt that it tells the OP anything useful whatsoever.Sorry EJP, it was a mouthful I know. Maybe this will help instead, a ColorConversionOps class to work on *32 bit > 16 bit > 32 bit colors*. To help clarify where the 16 bit color input and output goes, some of the methods return or require parameters of type short. Also take notice the bitmask for variables of type short vs the bitmasks for int. AND pay particular attention to the unsigned right bit-shifting of the most-significant-digit.
    public class ColorConversionOps
      public static short convert32_16(int rgb) {
        int a = ((rgb & 0xF0000000) >>> 16);
        int r = ((rgb & 0x00F00000) >>  12);
        int g = ((rgb & 0x0000F000) >>   8);
        int b = ((rgb & 0x000000F0) >>   4);
        return (short)( a | r | g | b);
      public static int convert16_32(short rgb) {
        int a = ((rgb & 0xF000) << 16);
        int r = ((rgb & 0x0F00) << 12);
        int g = ((rgb & 0x00F0) <<  8);
        int b = ((rgb & 0x000F) <<  4);
        return (a | r | g | b);
      public static void printRGB_32(int rgb) {
        System.out.println("a="+((rgb & 0xFF000000) >>> 24));
        System.out.println("r="+((rgb & 0x00FF0000) >>  16));
        System.out.println("g="+((rgb & 0x0000FF00) >>  8));
        System.out.println("b="+ (rgb & 0x000000FF));
        System.out.println();
      public static void printRGB_16(short rgb) {
        System.out.println("a="+((rgb & 0xF000) >>> 12));
        System.out.println("r="+((rgb & 0x0F00) >>  8));
        System.out.println("g="+((rgb & 0x00F0) >>  4));
        System.out.println("b="+ (rgb & 0x000F));
        System.out.println();
    }Now to make the conversion from 32 bit color to 16 bit color and back. NOTICE there willl be a loss of precision -- just like someone else has already said.
    public class Test
      public static void main(String[] args)
        int rgb = 0xFFFFFFFF;
        ColorConversionOps.printRGB_32(rgb);
        //a=255
        //r=255
        //g=255
        //b=255
        rgb = ColorConversionOps.convert32_16(rgb);
        ColorConversionOps.printRGB_16((short)rgb);
        //a=15
        //r=15
        //g=15
        //b=15
        rgb = ColorConversionOps.convert16_32((short)rgb);
        ColorConversionOps.printRGB_32(rgb);
        //a=240
        //r=240
        //g=240
        //b=240
    }And now we see, the reason 16bit color is so unpopular to the rest of the world, but not for us here!

  • 16 bit integer vs 32 bit floating point

    What is the difference between these two settings?
    My question stems from the problem I have importing files from different networked servers. I put FCP files (NTSC DV - self contained movies) into the server with 16 bit settings, but when I pull the same file off the server and import it into my FCP, this setting is set to 32 bit floating point, forcing me to have to render the audio.
    This format difference causes stuttering during playback in the viewer, and is an inconvenience when dealing with tight deadlines (something that needs to be done in 5 minutes).
    Any thoughts would be helpful.

    It's not quite that simple.
    32 bit floating point numbers have essentially an 8 bit exponent and 24 bit mantissa.  You could imagine that the exponent isn't particularly significant in values that generally range from 0.0 to 1.0, so you have 24 bits of precision (color information) essentially.
    At 16-bit float, I'm throwing out half the color information, but I'd still have vastly more color information than 16-bit integer?
    Not really.  But it's not a trivial comparison.
    I don't know the layout of the 24 bit format you mentioned, but a 16 bit half-float value has 11 bits of precision.  Photoshop's 16 bits/color mode has 15 bits of precision.
    The way integers are manipulated vs. floating point differs during image editing, with consistent retention of precision being a plus of the floating point format when manipulating colors of any brightness.  Essentially this means very little chance of introducing posterization from extreme operations in the workflow.  If your images are substantially dark, you might actually have more precision in a half-float, and if your images are light you might have more precision in 16 bits/channel integers.
    I'd be concerned over what is meant by "lossy" compression.  Can you see the compression artifacts?
    -Noel

  • JVM 32-bit vs. 64-bit on Solaris8

    Hello developers,
    has anybody compared overall performance of 64-bit JVM on Solaris? I'd like to make some investigations, and maybe someone already has some info.
    Peter

    You will need to benchmark your application both ways to know for sure. One rule of thumb is that the 32 bit VM is a bit faster (smaller pointers in the heap, etc...), up to the point where you really need to have a 64-bit heap. At that point, choose the 64-bit VM and scale up from there.
    Start with this JavaOne presentation:
    http://servlet.java.sun.com/javaone/resources/content/sf2002/conf/sessions/pdfs/2008.pdf
    From there, take a look at:
    http://java.sun.com/performance/
    Also, refer to this document:
    http://java.sun.com/docs/hotspot/gc5.0/gc_tuning_5.html

Maybe you are looking for