Crushed black levels in iMovie HD

I'm having trouble with black levels being crushed (i.e.: darkening, unwanted excessive contrast, loss of detail) when importing video from a newer pro level JVC broadcast 1/2-inch chip camera into iMovie HD. I am importing via firewire into iMovie, making a few edits and sending the video back to the camera via firewire. When I use the pro camera, the black levels are crushed. However, when I use a consumer grade Canon GL-2 camera and do the same, the black levels are perfect and unaffected. Has anyone else had this problem and figured out a solution? Thank you.
Powerbook G4 Mac OS X (10.4.7)
Powerbook G4 Mac OS X (10.4.7)
Powerbook G4   Mac OS X (10.4.7)  

I am able to set the black level of what is recorded to tape; however, the camera always outputs at 7.5. iMovie wants to see black setup at 0.0 but my camera outputs at 7.5 NTSC regardless of the black level setting that goes to tape. I'll check the manual again and try some experiments. I'll post the results soon. Thank you.
that is beyond my hands-on experiences, but afaik,
broadcast camcorders allow setting the blacklevel
manually, as a keyword "superblack", which is "under"
0%...-
check camera's settings/manual
iMovie is a consumer product, ... my guess
is, your dv-stream is outside the "normal" standards
of a 200$camcorder..
Powerbook G4 Mac OS X (10.4.7)

Similar Messages

  • Crushed Black Level

    I am working with a Sony PVW-2600 Betacam deck, Final Cut 5.0, G5 and a Blackmagic video card. I have a waveform monitor that has been calibrated. When I digitize footage at the proper video levels (7.5 and 100 IRE), the blacks are crushed by 20% inside of Final Cut. I've replaced the deck with another, thinking that it was the deck's fault. It's not. Any ideas as to why this is happening? Bad cable maybe?

    You only want to add setup once, on the analog output to an analog deck.
    Try this:
    Capture bars from the Beta deck in FCP. Drop them into a Timeline. Now do an ETT back to the Beta deck. If the Decklink controls are saet properly, setup should be a 7.5.
    If blacks are crushed on the way to the deck, then there should be a setting in the Decklink card's controls to add setup.
    But you don't want to add setup twice in a roundtrip. If you do, blacks will be at 15 or so. Bleah!
    Unless I'm misunderstanding what's happening to your video.

  • OpenGL inaccuracies and black levels

    Here is an sRGB file consisting of 0,0,0 background, with five overlaid squares at one level increments, from 1 to 5.
    On my Eizo CG246, calibrated with Eizo ColorNavigator, all five squares are discernible against the black background, as long as Graphics Processor > Advanced is set to "Basic" mode. This means that the color management logic (the conversion to the display profile) is performed in the CPU.
    In "Normal" and "Advanced" modes, color management is shifted to the GPU. With these settings, black levels disappear. It's not dramatic, but it's there. The difference can be illustrated in a screenshot, as long as the display profile is assigned and the screenshot is pasted in the Basic mode. Here's how it looks straight up (should be viewed against a dark background):
    Here I put a Curves layer on top to exaggerate:
    And here I read out the numbers from this exaggerated version:
    So far it seems this can not be reproduced on another monitor I have, an NEC P232W calibrated with Spectraview II. It also seemed a bit more pronounced on a different Eizo I no longer use, an S2243W, calibrated with Eizo EasyPix.
    This suggests that the problem is in the interaction between the display profile and the Open GL engine that does the conversion. I think this is related to the ProPhoto cyan banding issue previously reported, because that also seems to behave differently between these two systems (I'll do some more testing on that).
    In all cases and all scenarios, all irregularities disappear with Open GL in the "Basic" setting.

    You neglected to include your test image with black and levels (1,1,1) through (5,5,5), but no matter, I have the one I made...
    http://Noel.ProDigitalSoftware.com/ForumPosts/DarkGrayColorLevels16Bit.png
    I've found that here I'm not seeing a visible difference between GPU and CPU color-management with the image in the sRGB color space.  In other words, no crush.  With the image in the ProPhoto RGB color space, some slight crush was apparent, along with color shifts almost exclusively toward red.
    However, that's not to say there are no differences between the two.  They're just more subtle than what you're seeing.  What I did to test was this:
    Open the image I linked to above using Advanced mode OpenGL.
    Float it in a window.
    Screen grab it.
    Pick it up and start to drag it.
    While still dragging, screen grab it again.
    Overlay the two images, and pixel align them.
    Set the top image to "Difference" blending.
    Add a couple of Curves layers over the top to greatly enhance the differences to make them more visible.
    Since my test image has a dark grayscale gradient expressed in 16 bits/channel, it's not only testing for accuracy at the visible level, but also for very subtle changes.  Lo and behold, changes are revealed.  Note:
    Enhanced differences between GPU and CPU rendering of the image in the sRGB color space:
    Assigning the ProPhoto RGB color space to my test image, then comparing GPU vs. CPU rendering...
    -Noel

  • DIsplayport crushing blacks w/ panasonic plasma tv

    I'm trying to properly calibrate a panasonic plasma for use with my mbp's displayport output. No matter how many times I run the apple calibration tool and turn up the brightness on the tv, the black levels are absolutely crushed (no detail in blacks).
    If you are familiar with it, I am using the calibration disc made by the folks over at AVSForum, and am unable to get any of moving bars visible in the black level calibration screen.
    Has anyone experienced this same issue and figured a way around it?

    My main display is an HDTV. I set all my color settings on it, not the MBP.
    If you're using a DVI > HDMI cable along with the DVI > MiniDisplay you should have no problems adjusting the colors on the TV itself.
    My Sony XBR6 has different profiles for each input. My MBP and my 360 both require different settings. Yours should do the same.
    I have had issues with newer nvidia cards (GTX295) and HDCP. They wold put out an HDCP compliant signal which would disallow me the ability to change any color/brightness settings on my TV. (Made my beyond furious)
    I would suggest making sure that the color settings on the TV are actually being changed, and that something is actually happening as you move the slider or increase the numbers, however its set up. Play with the white/black levels as well. Try turning down the backlight...
    Calibration discs can be very misleading. Your best bet is to put in a DVD and play a dark scene, adjust the brightness, then move to an outdoor scene. I still to this day need to fiddle with mine very occasionally.
    One other thing to check is your TV's features. For example, mine has some stuff called "Gamma" and another called "Advanced CE" These solved my problem with contrast the second i enabled them.

  • Compressor 2 black level/chroma issue

    I have discovered a problem about making MPEG2s with Compressor 2. I have two suites one of which has recently been upgraded to FCP Studio with Tiger; I used Compressor 2 to make a batch of MPEG2s and some QT’s for the web. The QT’s were fine but the MPEG’s were oversaturated and had crushed blacks. I have tried both the new and old setting and the problem is common to both. I have tried recompressing material that I already have MPEGs of – that were made with FCP 4.5 and Compressor 1. The new ones are different and all exhibit high chroma low black levels.
    Since my second suite is still running FCP 4.5 and compressor I ran the same tests in the old suite and the levels looked fine, suggesting that there is an issue with Compressor 2.
    I tried to alert Apple directly and was told that they had no way of putting me in touch with anyone directly. So I hope that for the sake of other users and myself this posting will ring some alarm bells.
    Robb Hart
    an ideal world
    714-953-9501
    [email protected]

    Let me be clear, I am not seeing any significant differences in the black levels and colors between Compressor 1.2.1 and Compressor 2.0.1 and yes I am using the same decoder when I compare the clips (Apple's MPEG2 Playback component). I've compared the clips side-by-side on the same display under both OS X 10.3.8 and 10.4.2. However, I haven't done an extensive set of comparison with a wide range of source material (at least not in any detailed manner).
    As for being CoreImage accelerated, under 10.4.X I do have support for CoreImage functions but they are not GPU hardware accelerated. Thus under 10.4.2 I do not get QuickTime's realtime color corrections. My PowerBook also supports Quartz Extreme.
    However, if you're talking about the so-called Quartz 2D Extreme then my system doesn't support such acceleration (and as far as I know Q2DE isn't even enabled yet -- not on any system -- you need a developer debug tool to turn it on).

  • Advice needed on white imac 24" screen - black levels

    Hi, I'm new to these forums as I'm a new mac user. So far the experience has been pretty good!
    I have a white 24" imac, and the colours and black levels look pretty ok in a normally lit room.
    However when I turn the lights off (room is in the dark) and view say a black screensaver, the whole screen appears greyish rather than a pure black. The greys appear quite even though, no splotches or anything.
    Is this something I should expect, especially for the iMac screen which is known to be an IPS lcd panel? Or should I give apply a call about it?
    Any advice and help would be greatly appreciated, thanks!

    More than likely that is caused by the backlight and is normal.

  • Data below black level 0 in h264 mp4 files.

    I'm a little confused about black and white levels in video.
    I have two questions. If you bare with me for a second I can demonstrate what I mean.
    I created gradient with values from 0,0,0 to 255,255,255 in Photoshop and saved it as sRGB jpg file.
    I imported the file to Premiere and added Fast Color Corrector to the file and changed black input level from 0,0 to 16,0
    So now everything below value 16 is cutted to black.
    I exported the edited gradient as h264 mp4 videofile.
    Now things got interesting.
    I imported the edited videofile back to Premiere, added Fast Color Corrector to videofile and changed black output level from 0,0 to 16,0
    The information that I thought was lost is there!
    I tried to to the same thing for the same video file with Photoshop and I'm not able to get the lost information back.
    Why is there information below 0? And how am I able to rescue it with Premiere, but not with Photoshop?
    Does this have something to do with YCbCr black and white levels that are 16-235?
    This whole question came up when I calibrated my Samsung lcd-tv. I used AVS HD 709 mp4-calibration videos.
    There are black level calibration videofile. Which is exactly like my gradient video file where there are black values below 0.
    If you lift your tv's brightness below certain levels you are able to see the black values that are below 0.
    I'm able to see these "blacker than black" values with tv's own videoplayer and with xbox videoplayer.
    However, if I try to see these values with my macbook pro  which is connected to tv I can't get them visible.
    It doesn't matter if I play the video with quicktime, vlc or premiere.
    So the second question is why the macbook pro does not send any "below black" information to tv?
    PS. I'm using latest premiere CC.
    Thank you in advance!
       In this image you can see from Premiere Scopes what is happening.

    Does this have something to do with YCbCr black and white levels that are 16-235?
    No and yes.
    When you manipulate levels values within 0-255 (0.0-1.0) range, you don't clip existing data, you simply compress/decompress contrast, while information is still there (to some extent). By the way, data outside 16-235 range, but inside 0-255 are not super-blacks or super-whites (underdarks or ovebrights), they are just broadcast safe values. Super-blacks or underdarks are values below 0.0, while super-whites or overbrights are values above 1.0. The nature of YCbCr does allow to store some real super-blacks and super-whites even while encoding to 8-bit codec.
    Why only some codecs are able to preserve this "illegal" values?
    MOV container is... um-m-m... quirky. For example, exactly the same data encoded to e.g. mp4 and MOV with exactly the same codec (e.g. H.264), may be decoded/interpretted differently. So as to have some fun, create a copy of an mp4 clip, which contains some super-whites, rename file extension of one copy to MOV, import both mp4 and fake MOV footages into After Effects, set your project to 32-bit, sRGB or Rec.709 and linearise working space in order to get precise result while blending layers. Then drop both clips into the same composition and set blending mode to Difference. Enjoy!
    Why I'm only able to access these values inside Premiere and not with Photoshop. Is Photoshop unable to access these illegal below 0 values?
    Try setting Photoshop to 32-bit first. If that doesn't help, then yes, Photoshop clips values outside 0-255 (0.0-1.0) range on importing. Similarly you won't be able to get super-whites or super-blacks back in PrPro with 8-bit effects.
    When i export with codecs that can preserve superblacks should I still get rid of them with videolimiter. Do they cause any problems in youtube or broadcast environments?
    No. Moreover, you should take care of broadcast legal range in case of delivering to a broadcaster only, YouTube 'broadcasts' on the web and targets regular computer monitors, which operate on sRGB 0-255 range.
    why the macbook pro does not send any "below black" information to tv?
    That has probably something to do with Apple colour management workflow. Since I'm not on a Mac, I can't comment this on

  • Black Levels too low

    I have a problem with the black level. There are too low all the time. When I do color correction and i render the blacks going up to high. Someone can help me?
    Thank you,
    Mario

    I think you are referring to this:
    http://prolost.blogspot.com/2008/01/colorista-clips-no-more.html

  • Normalising Sound Levels in iMovie

    Hello,
    I have an iMovie project which is a video/audio interview between two people. Unfortunately the interviewer's mic is far quieter than the interviewee's. Is there a way that I can normalise the sound levels within iMovie so that the volume is consistent?
    Thanks!
    Tom Ewer

    The only way to do that is, if you have iMovie 11, view the audio levels under the video clips and manually change it each time the people switch talking.

  • Black levels and exporting

    Hey there-
    When I export anything through render cue using Lossless, Lossless with alpha or Custom Quicktime the black levels of the rendered file are 5-10 units high regardless of the program that I use to open it. I'm exporting to a local hard drive and not a server.   I'm using After Effects CS6 and Final Cut Pro 7.0.3 on a Mac.  The export settings in After Effects are the same as others in my office and no one else seems to have this problem.
    Thanks for your time.

    By “units” I mean pedestal units on a wave form monitor.  Final Cut has a wave form/vector scope feature. The apps that I use do not have features to adjust gamma, video levels or pedestal.  I'm not using color management.  I've tried importing raw video (uncompressed Sony XPCAM) and Quicktime files from different sources, adding them to the timeline and exporting them without applying anything at all.  The codecs that the files are being exported to are animation and timecode.  As far as monitor calibration, everything with the exception of exported After Effects files looks normal in Final Cut Pro. (blacks have definition but are not washed out, whites and colors look normal).   Could it possibly have something to do with how the files are being imported?

  • Black levels different on import

    Hi all. I'm digitizing a DVCam Master tape of a show that I'm putting on DVD. In the studio where the show was edited, the blacks look perfect. But when I digitize on my system, the blacks look a lot lighter. I've compared the QTs I'm making with QTs my client made, and my client's are much darker. The weird thing is we both digitized using Firewire. Could my deck be causing a problem? (It's an older Sony WV-DR7, a grey-market Japanese player that takes full size DV tapes, and also plays DVCam). Could it be the way I'm digitizing? (I'm going in firewire, which I always assumed was identical to the tape). Any one else ever had these issues? Any solutions in FCP itself?
    Any ideas?
    G5 Dual 2.5 Ghz   Mac OS X (10.4.9)  
        FCP 5.0.4

    It's most likely your IRE setup with the deck. Here's where it gets tricky because I don't know how your older deck handles DV. But to sum up, digital media needs to be captured to your NLE at 0 IRE and analoge video will need 7 IRE in order to mainatain proper black levels. So check your deck and make sure it's set right for your particular capture.
    With more modern decks the default setup is usually for DV and 0 IRE but your deck may be different. It's worth it to do a test using the 2 different black setup levels on your deck. Obviously you'll choose the setup that gives you proper black levels in FCP, whatever that setup turns out to be.
    - Don

  • Black Levels Boosted Upon DVD Burn

    I realize this topic has been covered and have read the many threads on this and on other forums. I have used the FCP forum in the past and thank anyone who has ever helped, well, anyone with a question. The link to purchase a Proc Amp is wonderfully informative and does nothing to remedy the problem or answer the question (for under $700).
    Is the workaround (yes, yet another workaround to add to the incredible list of hoop jumping - try using Soundtack Pro to alter audio clips not captured in stereo!) really to figure out a final "DVD export" setting that compensates for the black level increase? That's what I've gathered after a couple days of casual research and all today really trying to tackle the problem. Sorry, just a little frustrated.
    If anyone was patient enough to read this all the way through and has a better idea than dropping the video level before exporting to Compressor/Quicktime please let me know.
    Also, why is the problem not nearly as noticable in my three year old version of iDVD?
    G4 Dual 1.25, 2GB RAM   Mac OS X (10.3.9)   FCP5.03 DVDSP4.03

    When you say "black levels boosted," do you mean you have too much black or not enough black? In other words, is your complaint that things are too dark, or that blacks are no longer "true" black?
    From your text, it sounds like you're complaining that your footage is too dark.
    Most complaints, however, are that compared to DV footage, the MPEG2 results are washed out. This is because they're comparing footage that has no "setup" (i.e. playing video directly out of the DV camera) with footage that has "setup" (i.e. playing video from a DVD player, which defaults to black equalling 7.5 IRE rather than 0 IRE). This is why you've seen the "proc amp" recommendation elsewhere.
    Can you describe your workflow in detail? It sounds like you're probably using DV footage--is that true? Are you exporting out of FCP into Compressor directly? Exporting a reference movie first? Exporting a movie and then encoding from QuickTime? Other?

  • Black levels in Compressor

    What settings are best for maintaining 7.5 IRE in a clip when creating MPEG2s in Compressor? If I go above 9, the black areas get blocky on screen. But is that going to be the case on a television screen?

    IRE isn't applied in the digital domain, it's only an artifact of analog video. If you're having problems then I suspect it's either a problem in your color workflow or the cllip was captured from an analog source that was configured incorrectly.
    If you haven't already done so, you should review the following on-line tutorials:
    http://www.signvideo.com/dv-black-levels-dvd-authoring-mpeg-2-part-1.htm
    http://www.kenstone.net/fcphomepage/video_levelsnattress.html<small><hr width="75%"><small>If this suggestion helps in any way, a confirmation or acknowledgment would be appreciated, since that would also help others who may be having the same difficulty. Do for others as you would have them help you.<center>Thanks for sharing, Waymen.</center></small>

  • Black Levels

    I am using a Canon XL1 and would like to create a DVD that plays well on an NTSC television in North America. I have color corrected using a television monitor connected to an NTSC TV via the XL1 (and I do not, unfortunately, have a proc amp).
    My understanding is that the above setup will produce incorrect black levels, due to an inconsistency in the way black is represented by Japanese cameras vs. North American TVs and DVD players.
    What I would like to know is what filter to use, with what settings, to correct black levels for video produced in this configuration.
    I understand that this is not the "right" way to approach this problem, but I would like a method that will at least provide me with something that's approximately correct.
    Thanks,
    Bob

    Hi Bob,
    You might find this flash video from JVC to be helpful - http://pro.jvc.com/pro/attributes/prodv/clips/blacksetup/demo.html I don't think the issue is Japanese cameras in general, rather it's the setup/settings of your camera and other devices. I have a Canon Optura xi and haven't had any problems with black levels, at least in my opinion/experience.
    Other than that, I think the Broadcast Safe filter is what you are looking for.

  • Black Levels in MPEG-2 files

    This is a problem I've been trying to solve for months. Whenever I encode an MPEG-2 file, regardless of what program I'm using (After Effects CS3, Sorensen Squeeze, among others), the black levels are milky grey, not black. This is a short film originally shot on 35mm; it is now a 10-bit DPX log sequence. The footage looks great in After Effects - black levels are all correct. When I export a QuickTime file from it, it looks good. But if I encode an MPEG-2 file, either directly from After Effects or using a different encoder, the blacks turn milky grey and the contrast/gamma in general just look a little off.
    Any insight anyone has into this problem would be greatly appreciated.
    Win XP/Intel Quad Core/4GB Ram

    It's a combination of the two, most likely. In general you will want to work in vanilla sRGB or 601/ Rec 709 when preparing content for DVD to be able to predict the colors as they will go on DVD. Other color profiles will use a different Gamma, which ultimately will result in a completely different effective output upon render than the one you may be seeing in your composition based on the workspace profile and log/lin conversion. This is especially critical with outputs via Adobe Media Encoder, image sequences or certain Quicktme flavors, all of which are aware of color profiles and in part allow embedding that info. A short way to bypass some of your issues may be the "preserve RGB" option on the output module color management tab, though it may cause your video to look over-saturated. Ultimately you will probably have to derive a dedicated DVD version of your project or base the actual MPEG-II transcode on a pre-rendered, color managed file. As an last item, make sure to check your monitor's Gamma and review the final output on a real TV and DVD player.
    Mylenium

Maybe you are looking for