Sequence audio format stuck on 32-bit Floating Point

Hi,
The audio format for all my sequences is set to 32-bit Floating Point when I check them in the browser's Aud Format field. When I manually change the format in the sequence settings nothing changes in the browser and choosing a new sequence set up doesn't seem to help. What I don't understand is that there isn't even an option for 32-bit Floating Point in Audio Settings. Anyone else experience this?
I am using v6.0.6 on osx 10.5.8
Thanks,
Tom

16 bits per channel equals 32 bits stereo. Floating point means that you can, but don't have to, have a non-integer value for your audio.

Similar Messages

  • Using iMovie footage in FCP: 32-bit floating point audio?

    I'd like to use iMovie 7 to capture my DV footage because I like its cataloging and skimming features, and the way it splits up clips based on DV stops. I want to do my editing in Final Cut Pro 5. Unfortunately, I've found that the audio depth in the clips I've captured with iMovie is 32-bit floating point, rather than 16-bit integer, and FCP has to render the audio before it can play back. Strange, since the FCP browser says that the sequence I dropped the iMovie footage into IS 32-bit. Any ideas on how to get FCP to playback this bit depth without rendering, and without having to convert my footage?

    Do a search here and you will find all kinds of post on this very subject.
    The main problems with using iMove to capture for FCP are
    1. iMovie and FCP capture in very different ways. iMovie captures footage as a DV stream, problematic for editing in FCP
    2. iMovie captures will not give you the timecode from your tape... may or may not be important to you unless you ever need to recapture and reconnect the footage.
    In short, if you are editing in FCP... capture with FCP. If you want to split the footage based on tape start/stop, use the Start Stop detect function after you have captured.
    rh

  • 32 bit Floating Point

    Hello,
    Running FCP 5.1
    Having audio sync issues and was double checking my settings.
    Although the sequence presets are at 16 bit, they are showing up in the browser as 32bit Floating Point.
    Any thoughts?
    I generally capture now at 30 minute increments and actually have always had this issue. FCP 4.5 and 5.1
    all settings are where they should be.
    although I do notice, obviously when the device is off, the audio output defaults to 'default' not to firewire dv.
    thanks
    iMac intel Mac OS X (10.4.8)

    Some more details please. What hardware device are you sourcing the audio clips from? The likely culprit is your capture settings. What preset are you using? Check Audio/Video Settings-Capture Presets and see if the preset you've selected records audio as 32 bit. It will say in the right column after you've selected your preset.
    If it says 32 bit there, click Edit to get the Capture Preset Editor. Under Quicktime Audio Settings, the Format field should give you a selection of sample rates and possibly alternate bit depths. If your only choice is 32 bit, (as it is for me when I capture audio via my RME, 32 bit Integer in my case) then you'd be well served by bringing those files into Peak or Quicktime and saving them as 16 bit Integer files to match your sequence settings.
    If you've imported these files into FCP from an audio editor that can create 32 bit floating point audio files, eg Kyma, Sequoia, Nuendo, etc. then the same advice applies. The 32 bit files are much larger than they need to be and may upset the apple cart (he he, pun) when pulled into a sequence with different settings. More cpu overhead for sure.
    Let us know what you find.

  • Help me changing 32-bit floating point into 16bit

    When I open a new project, the browser gives the following information:
    Audio format: 32-bit floating point.
    Even when I changed the sequence settings (under sequence > settings, or under final cut pro > audio/video settings > sequence presets > edit) to 16 bit, the 32-bit floating point in the browser stays the same.
    I would love to change this into 16 bit. Can anybody help me?
    Thnx

    You can't change it. FCP is 32-bit float internally. What are you trying to do by changing it?

  • 32 bit floating point ... SLOW...

    Hi,
    I ran a little test because i found Motion took too much time exporting with 32 bit floating point.
    I made a single layer, animated text in Motion with my Quad ( 2.5 G RAM)
    When i exported 32 bit floating point QT Animation in Motion, it was very very slow and the CPU were running at 10 to 15%.
    When i export 8 bit floating point, it is much faster but CPU run at about 20%.
    BUT
    In FCP, when i render 8 bit Motion project and .mov (from 8 bit), or 32 bit Motion projet and .mov (from 32 bit), they all render pretty fast...
    8 bit Motion prj 45% CPU
    .mov from Motion 8 bit 30% CPU
    32 bit Motion prj 45% CPU
    .mov from Motion 32 bit 60% CPU
    Why that much difference ?
    I dont understand why the CPU are running higher with a .mov (QT Animation) that has been created in 32 bit floating point ?
    I thought that once it has been created (self contained) it did not matter...
    thanks

    32 bit floating point refers to how it will be rendered. Has nothing to do with the format itself. You're OK ... just edit.
    32-bit floating point allows audio calculations, such as fader levels and effects processing, to be
    performed at very high resolution with a minimum of error, which preserves the quality of your digital audio.
    Jerry

  • 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

  • SignalExpress 2010 - Chart time axis format will not change to floating point or anything else

    I just downloaded and installed the new and shiny SignalExpress 2010 to replace the old version. And immediately run into major problems:
    The x-axis time format refuses to change to floating point or scientific even if I choose them from chart properties. The format is always absolute, e.g. 12:23:54.743. This makes the usage of the chart and the whole application impossible! Is this a known issue and is it going to be fixed soon? And where can I get the old version of the SignalExpress (2009) so I can install it again?

    Here is a screenshot of the problem:

  • Photoshop CS3 vs CS2 32 bit floating point tiff loading

    Hi,
    The application I'm developing exports 3 channel 32 bit floating point tiff's.
    The exported files could have been loaded into PS CS2, but PS CS3 can't load them anymore, all I get is a message box with this message:
    "Could not complete your request because of a problem parsing the TIFF file."
    I've uploaded the file here, so you guys can have a look at: www.thepixelmachine.com/dispmap.tiff

    Where should I've posted this thread instead? I suppose people here write plugins by programming them (right?), so they suppose to be programmers, not regular PS users. I thought a programmer would be much more familiar with programming related issues, such as tiff file saving c++ routines. Correct me if I'm wrong.
    The people who tested the file have Photoshop CS3 and didn't manage to open it, they even sent me screenshots with the error message box. In CS2 however, the file loads perfectly. Also, the single strip version opened just fine in CS3.
    You may close this thread, the problem was solved and more than that it looks like I haven't posted it in the right forum.
    Thanks.

  • 128-bit floating point calculations

    I'm looking to buy a used SPARC. Which model is the oldest that provides
    C or fortran 128-bit floating point calculations? Does every 64-bit CPU
    have 128-bit quad real numbers?
    Ron

    The AMD 64-bit processor does not support 128-bit
    floating numbers. I need a Sparc processor that
    does.And yet your question has just what to do with Java -- why did you create a userid and post this question in the Java forums?
    A response "Does every person have ten fingers?"
    shows me that you don't know much about writting
    computer programs that have more than 16 significant
    decimal digits.I wouldn't infer that - but now that you've proven to be a whiny little snot, I'm sure everyone is just going to want to help you here.

  • 32-bit floating point HDR support for LR4.1 RC2

    Folks,
    In the event you haven't discovered it, LR4.1 RC2 has added support for importing and adjusting a 32-bit floating point TIFF file. Which means LR4 can tonemap an HDR image. To use this, you'll need to use Photoshop's HDR Pro to put together the multiple exposed images, then set the options to make a 32-bit HDR image in HDR Pro and save that as a TIFF file. Then import the TIFF into LR4.1 RC2 for toning...note: nothing you do to the HRD in HDR Pro will impact the 32-bit FP TIFF. If you do some initial adjustments of the original raw files in LR 4.1, I'm pretty sure most of the toning in LR4.1 on the raw files is ignored. But white balance works (haven't tested spot healing and lens corrections yet).
    Note, to do the HDR process, the raw images will end up being demosaiced and the saved HDR TIFF will be a linear ProPhoto RGB image.
    Try it...the ability to use LR (and eventually ACR–it's not hooked up in the ACR 7 beta yet) to toning HDR images is actually pretty impressive. Also note, that you don't really need to feed HDR Pro a ton of multiple exposures...2 (normal and under to preserve highlight detail) or 3-5 depending on the scene contrast range is all you need. More isn't really better (unless you really need to shoot a very high dynamic range scene...

    I will try that in the morning, but when checking the properties today it did say 16-bit for each clip. I have gotten around this by taking each clip offline, opening it in STP, applying the effects, doing a save as and then reconnecting each clip with the new file. It seems to work with no sync issues. Just doesn't work as easily as it should. Ideally I should be able to send each section to an STP script and allow it to do its work and have it work.
    I sure hope to find out exactly what is going on.
    K

  • 128-bit floating point numbers on new AMD quad-core Barcelona?

    There's quite a lot of buzz over at Slashdot about the new AMD quad core chips, announced yesterday:
    http://hardware.slashdot.org/article.pl?sid=07/02/10/0554208
    Much of the excitement is over the "new vector math unit referred to as SSE128", which is integrated into each [?!?] core; Tom Yager, of Infoworld, talks about it here:
    Quad-core Opteron? Nope. Barcelona is the completely redesigned x86, and it’s brilliant
    Now here's my question - does anyone know what the inputs and the outputs of this coprocessor look like? Can it perform arithmetic [or, God forbid, trigonometric] operations [in hardware] on 128-bit quad precision floats? And, if so, will LabVIEW be adding support for it? [Compare here versus here.]
    I found a little bit of marketing-speak blather at AMD about "SSE 128" in this old PDF Powerpoint-ish presentation, from June of 2006:
    http://www.amd.com/us-en/assets/content_type/DownloadableAssets/PhilHesterAMDAnalystDayV2.pdf
    WARNING: PDF DOCUMENT
    Page 13: "Dual 128-bit SSE dataflow, Dual 128-bit loads per cycle"
    Page 14: "128-bit SSE and 128-bit Loads, 128b FADD, 128 bit FMUL, 128b SSE, 128b SSE"
    etc etc etc
    While it's largely just gibberish to me, "FADD" looks like what might be a "floating point adder", and "FMUL" could be a "floating point multiplier", and God forbid that the two "SSE" units might be capable of computing some 128-bit cosines. But I don't know whether that old paper is even applicable to the chip that was released yesterday, and I'm just guessing as to what these things might mean anyway.
    Other than that, though, AMD's main website is strangely quiet about the Barcelona announcement. [Memo to AMD marketing - if you've just released the greatest thing since sliced bread, then you need to publicize the fact that you've just released the greatest thing since sliced bread...]

    I posted a query over at the AMD forums, and here's what I was told.
    I had hoped that e.g. "128b FADD" would be able to do something like the following:
    /* "quad" is a hypothetical 128-bit quad precision  */
    /* floating point number, similar to "long double"  */
    /* in recent versions of C++:                       */
    quad x, y, z;
    x = 1.000000000000000000000000000001;
    y = 1.000000000000000000000000000001;
    /* the hope was that "128b FADD" could perform the  */
    /* following 128-bit addition in hardware:          */
    z = x + y;
    However, the answer I'm getting is that "128b FADD" is just a set of two 64-bit adders running in parallel, which are capable of adding two vectors of 64-bit doubles more or less simultaneously:
    double x[2], y[2], z[2];
    x[0] = 1.000000000000000000000000000001;
    y[0] = 1.000000000000000000000000000001;
    x[1] = 2.000000000000000000000000000222;
    y[1] = 2.000000000000000000000000000222;
    /* Apparently the coordinates of the two "vectors" x & y       */
    /* can be sent to "128b FADD" in parallel, and the following   */
    /* two summations can be computed more or less simultaneously: */
    z[0] = x[0] + y[0];
    z[1] = x[1] + y[1];
    Thus e.g. "128b FADD", working in concert with "128b FMUL", will be able to [more or less] halve the amount of time it takes to compute a dot product of vectors whose coordinates are 64-bit doubles.
    So this "128-bit" circuitry is great if you're doing lots of linear algebra with 64-bit doubles, but it doesn't appear to offer anything in the way of greater precision for people who are interested in precision-sensitive calculations.
    By the way, if you're at all interested in questions of precision sensitivity & round-off error, I'd highly recommend Prof Kahan's page at Cal-Berzerkeley:
    http://www.cs.berkeley.edu/~wkahan/
    PDF DOCUMENT: How JAVA's Floating-Point Hurts Everyone Everywhere
    http://www.cs.berkeley.edu/~wkahan/JAVAhurt.pdf
    PDF DOCUMENT: Matlab's Loss is Nobody's Gain
    http://www.cs.berkeley.edu/~wkahan/MxMulEps.pdf

  • Color picker stuck in 32 bit float mode

    I cannot get my color picker to go back to 8 bit mode. Places I have gone to make sure its set to 8 bit mode
    info
    comp window > color options > set project working space
    file > project settings.
    Despite all of them being 8 bpc, it is staying in 32 bit mode. I feel like I am missing something stupid. Any Ideas

    Taking a close look at your screenshot your color picker is in 8 bit, you've just selected to look at the red channel and you've typed in a very odd number for green. I can get the same thing:
    The gradient editor will let you type in anything. If you use the picker you'll get normal values. If the display was in 32Bit the values would look like this:

  • Add mode and 32 bit Floating point

    Hi.
    I have an AE comp containing 10 layers rendered off to EXR from 3DS Max using VRay.  I have a "cold" scene and have composited several hot VRay ObjectSelect render elements and VRayAtmosphere render elements.  Every layer uses "Add" blend mode.  All are OK except one layer (an Atmosphere element containing smoke).  The smoke is very dark (virtually black) when rendered in Max.  It is layered in AE over a glowing hot area.  When I use "Add" blend mode the smoke looks very thin/transparent and very pale.
    Q.  What effects should I use to get the black smoke to appear black (as it would look in the Max render)?  I would like a degree of control over the transparency so that I can let part of the glow behind it still show through.
    Many thanks,
    T  

    USING Thanks Mylenium.
    As "Add" seems to be the only blend mode that "works" in this instance i.e. by placing the information on top of the other layers, can I get the required control over the smoke by using other effects?  I have played around with levels/exposures/gamma etc. but not found anything that worked.  Is there something that will do this?
    Many thanks,
    T

  • How to change sequence audio preset?

    in my browser, my FOOTAGE audio rate is 48khz/audio format 16-bit integer. but my SEQUENCE audio rate is 48khz/audio format 32-bit floating point.
    when i go to adjust the sequence settings to make my sequence 16-bit as well, it says it is 48khz/16, but that doesn't correspond to how the sequences are in my browser. when i try to add new sequences, it adds them as 32-bit instead of 16 still.
    any ideas?

    Your sequence will show 32bit floating point as it's functionality. Why, I don't know...others here may.
    If you open a sequence, then go to MainMenu/Sequence/Settings, you'll see that the settings there should be 16bit depth.
    That should be correct.
    Are you having issues with anything, or simply determining what's up?
    K

  • How do you set sequence audio sample rate?

    I tried posting this to another, but it was already answered, and noone will see it.
    I am getting the capture error "audio sample rate doesn't match" and yes, I can see in my browser that the clip is 48khz/16bit, but the sequence is 48khz/32 bit. Howver, wherever I look to change the sequence setting, it is 48/16 already. I've gone to FCP on the menu dropdown to audio/video settings - it's correct all through there. I've gone to the menu dropdown Sequence settings, and it's correct there. I've closed down, opened a new sequence, restarted, everything I can think of. Is there a secret to getting them to match? And, can I fix a project already edited with this discrepancy? Its export to QT is WAY out of synch.

    Annoying - I can't see your post when I am in reply mode.
    Yes, I get this error when i am capturing. From reading a previous post about the error, I thought the solution was to check the audio rate of the captured clip in the browser, and then make sure it matched the audio rate of the sequence. Like I said, everywhere you get to change the sequence setting, it SAYS it is 48/16, but yet, whe I scroll over in the browser, it says the audio rate is 48 KHz and the audio format is 32-bit floating point. Am I looking at the right places?
    I can't check the settings in the camera until this evening...don't ask.
    I'm not so sure this is not a QT issue instead of anything to do with capturing, etc. It plays back fine in the timeline.

Maybe you are looking for

  • Biller Direct Documentation

    Does someone who has installed Biller Direct using EP 6.0 know where to find detailed information about customizing the web application - ie. texts, graphics, etc. The Modification Guide does not specify document names. Thank you for your assistance,

  • Using a paramter to fetch data from database

    Hello SAP, Is there a way to use a parameter that takes in the employee ID and have it fetch from the database the employee name.  Just to note, the tables that I am using in this report do not link to the employee table that contains the employee na

  • How do I "Open In New Tab" by wheel click (like in Windows)?

    I have a Microsoft Trackball Explorer (though I imagine this pertains to ANY mouse). In Windows if I click on a link with the wheel it open it in a tab. Not sure if this was a driver feature or what, bit it sure was handy. In OS X clicking the wheel

  • HT1208 Information about turning menu bars on might be worth adding to this article?

    Re http://support.apple.com/kb/HT1208 Doesn't mention turning on menu bars.  Might be worth adding.

  • Capturing iPhoto Book Temporary PDF File

    In earlier versions of iPhoto, it was possible to capture a copy of the PDF file that is generated and sent to the photo printing service by finding the temporary folder where iPhoto saves the file during the "assembling book..." phase. (For a detail