When I  increase the mids in color corrector my videos loose quality ?

I am currently taking a LOT of night video with the JVC hd7 and I do not have a light. This is why I am opting by just increasing the mids in each video to a higher volume. I find that this is lowering the quality of my videos why is this ?

Michel's point is, is that your video is already "damaged" Video shot at low light does not have all the signal information that video requires. Light is an incredibly important factor in determing signal strength and shooting in low light weakens it, I don't care what your camera's "lux" setting is
So, you will have to do some work. Strangely enough, when you increase the mids, you may have to add some more black to fill in that graininess. No matter what you do, you are going to affect your chroma quality. Some color correction may be necessary
But, really, get yourself a light. Movies shooting on film, which has a far superior gamma rating than video, use huge soft lights even during the day. Light strengthens your video; anytime you have to go and tweak your basic video settings you are affecting that signal.

Similar Messages

  • Re: Throughput drops dramatically when I increase the number of instances in a cluster

    Thanks for the quick reply.
              Yes, we are running WLS with the performance pack.
              "Bernie Wong" <[email protected]> wrote in message
              news:[email protected]...
              > Fellow clusterers ....
              >
              > I have an EJB driver program that pumps work into a WLS cluster. For
              > scalability, I increase the number of drivers. The drivers have a big pool
              > of work to pump into the cluster.
              >
              > I noticed that with 6 (nothing special about that number) drivers, I can
              get
              > 500K worked items per hour in a single instance (clustered). That is, the
              > instance is cluster enabled and is watching for multicast, etc..
              >
              > When I add the second instance into the cluster, the cluster-wide
              throughput
              > with the six drivers drops to 370K items per hour. When I add the third
              > instance, the cluster-wide throughput drops further to 250K items per
              hour.
              > When I kill an instance, the throughput grows back to 370K items per hour.
              > When I kill another instance (to get back to one instance), the throughput
              > grows back to 500K/hr.
              >
              > Can somebody point out what we are doing wrong - do we need to tweek some
              > WLS parameters, do we have to avoid some features that limit cluster
              > scalability, etc..
              >
              > My WLS configuration is .....
              > - WLS 5.1, SP5
              > - JDK 1.2.1_04c with JIT, no Hotspot
              >
              > My hardware/software configuration consists of:
              > - an E4500 - 8 processor database server - this is only running at 15%
              > server busy
              > - three E4500 - all 8 processors/6GB RAM - application processors
              >
              > The cluster is implemented with one instance per application server.
              > Each application server is only 10-15% busy.
              >
              > My driver and application is ....
              > - stateless EJB driver and stateless EJB bean
              >
              > Your thoughts and comments would be greatly appreciated.
              >
              > Bernie
              >
              >
              

    Thanks. It works. We screwed up the settings.
              "Bernie Wong" <[email protected]> wrote in message
              news:[email protected]...
              > Thanks for the reply.
              >
              > We ran the benchmark again and got the same scaling profile. This
              afternoon,
              > we are going to run a benchmark with a really simple driver + bean (a do
              > nothing bean) and see if we get the same scaling profile. From all the
              > responses, it would appear that WLS can scale therefore we want to isolate
              > the problem to either our code or our configuration (or both).
              >
              > I will let you know.
              >
              > Bernie
              >
              > "Rob Woollen" <[email protected]> wrote in message
              > news:[email protected]...
              > > Make sure that this was set on the client not the server.
              > >
              > > -- Rob
              > >
              > > Bernie Wong wrote:
              > > >
              > > > Jim,
              > > >
              > > > Thanks for the suggestions. One of my performance engineers ran
              several
              > > > experiments last week where he set the executeThreadCount to 6 and to
              10
              > > > along with a percentSocketReaders to 50. He saw no improvement. We
              will
              > > > rerun that experiment again since that seems to be the most common
              > > > recommendation.
              > > >
              > > > Bernie
              > > >
              > > > "Jim Zhou" <[email protected]> wrote in message
              > > > news:[email protected]...
              > > > > One possible reason is not enough socket reader execute threads, try
              > to do
              > > > > this:
              > > > > "-Dweblogic.system.executeThreadCount=10"
              > > > > "-Dweblogic.system.percentSocketReaders=50" on your client JVM
              startup
              > > > > command line.
              > > > >
              > > > > http://www.weblogic.com/docs51/admindocs/tuning.html#tuning clients
              > > > >
              > > > > WebLogic RMI
              > > > > If you are using WebLogic RMI clients and there are more than 2
              > Weblogic
              > > > > servers in a cluster, you may encounter a significant performance
              > > > > degradation (very long round trip times for stateless session beans,
              > for
              > > > > instance). The solution is to make some property changes on the
              client
              > > > side
              > > > > as explained below.
              > > > >
              > > > > The solution to this problem is to ensure that there are at least as
              > many
              > > > > socket reader threads as there are connections to the server and
              also
              > > > > allowing for some extra threads for processing other tasks. This is
              > > > > accomplished by starting the client with the command line argument
              > > > > "-Dweblogic.system.percentSocketReaders" set to a sufficiently high
              > > > > percentage (say 50) and by ensuring that there sufficient number of
              > > > execute
              > > > > threads for other processing on the client. A metric of twice the
              > number
              > > > of
              > > > > execute threads as there are servers in a cluster should work fine
              if
              > the
              > > > > above percentage is at 50. The command line argument affecting the
              > number
              > > > of
              > > > > execute threads is
              > > > >
              > > > > "-Dweblogic.system.executeThreadCount".
              > > > >
              > > > > For instance, we could use:
              > > > >
              > > > > "-Dweblogic.system.executeThreadCount=10"
              > > > >
              > > > > and
              > > > >
              > > > > "-Dweblogic.system.percentSocketReaders=50"
              > > > >
              > > > > when testing with 3 or 4 servers in a cluster.
              > > > >
              > > > >
              > > > > Bernie Wong <[email protected]> wrote in message
              > > > > news:[email protected]...
              > > > > > Thanks for the quick reply.
              > > > > >
              > > > > > Yes, we are running WLS with the performance pack.
              > > > > >
              > > > > >
              > > > > > "Bernie Wong" <[email protected]> wrote in message
              > > > > > news:[email protected]...
              > > > > > > Fellow clusterers ....
              > > > > > >
              > > > > > > I have an EJB driver program that pumps work into a WLS cluster.
              > For
              > > > > > > scalability, I increase the number of drivers. The drivers have
              a
              > big
              > > > > pool
              > > > > > > of work to pump into the cluster.
              > > > > > >
              > > > > > > I noticed that with 6 (nothing special about that number)
              drivers,
              > I
              > > > can
              > > > > > get
              > > > > > > 500K worked items per hour in a single instance (clustered).
              That
              > is,
              > > > > the
              > > > > > > instance is cluster enabled and is watching for multicast, etc..
              > > > > > >
              > > > > > > When I add the second instance into the cluster, the
              cluster-wide
              > > > > > throughput
              > > > > > > with the six drivers drops to 370K items per hour. When I add
              the
              > > > third
              > > > > > > instance, the cluster-wide throughput drops further to 250K
              items
              > per
              > > > > > hour.
              > > > > > > When I kill an instance, the throughput grows back to 370K items
              > per
              > > > > hour.
              > > > > > > When I kill another instance (to get back to one instance), the
              > > > > throughput
              > > > > > > grows back to 500K/hr.
              > > > > > >
              > > > > > > Can somebody point out what we are doing wrong - do we need to
              > tweek
              > > > > some
              > > > > > > WLS parameters, do we have to avoid some features that limit
              > cluster
              > > > > > > scalability, etc..
              > > > > > >
              > > > > > > My WLS configuration is .....
              > > > > > > - WLS 5.1, SP5
              > > > > > > - JDK 1.2.1_04c with JIT, no Hotspot
              > > > > > >
              > > > > > > My hardware/software configuration consists of:
              > > > > > > - an E4500 - 8 processor database server - this is only
              > running at
              > > > > 15%
              > > > > > > server busy
              > > > > > > - three E4500 - all 8 processors/6GB RAM - application
              > processors
              > > > > > >
              > > > > > > The cluster is implemented with one instance per application
              > > > server.
              > > > > > > Each application server is only 10-15% busy.
              > > > > > >
              > > > > > > My driver and application is ....
              > > > > > > - stateless EJB driver and stateless EJB bean
              > > > > > >
              > > > > > > Your thoughts and comments would be greatly appreciated.
              > > > > > >
              > > > > > > Bernie
              > > > > > >
              > > > > > >
              > > > > >
              > > > > >
              > > > >
              > > > >
              >
              >
              

  • Throughput drops dramatically when I increase the number of instances in a cluster

    Fellow clusterers ....
    I have an EJB driver program that pumps work into a WLS cluster. For
    scalability, I increase the number of drivers. The drivers have a big pool
    of work to pump into the cluster.
    I noticed that with 6 (nothing special about that number) drivers, I can get
    500K worked items per hour in a single instance (clustered). That is, the
    instance is cluster enabled and is watching for multicast, etc..
    When I add the second instance into the cluster, the cluster-wide throughput
    with the six drivers drops to 370K items per hour. When I add the third
    instance, the cluster-wide throughput drops further to 250K items per hour.
    When I kill an instance, the throughput grows back to 370K items per hour.
    When I kill another instance (to get back to one instance), the throughput
    grows back to 500K/hr.
    Can somebody point out what we are doing wrong - do we need to tweek some
    WLS parameters, do we have to avoid some features that limit cluster
    scalability, etc..
    My WLS configuration is .....
    - WLS 5.1, SP5
    - JDK 1.2.1_04c with JIT, no Hotspot
    - we enabled performance pack
    My hardware/software configuration consists of:
    - an E4500 - 8 processor database server - this is only running at 15%
    server busy
    - three E4500 - all 8 processors/6GB RAM - application processors
    The cluster is implemented with one instance per application server.
    Each application server is only 10-15% busy.
    My driver and application is ....
    - stateless EJB driver and stateless EJB bean
    Your thoughts and comments would be greatly appreciated.
    Bernie

    The short answer is to set the following tuneables on the client side:
    java -Dweblogic.system.executeThreadCount=10
    -Dweblogic.system.percentSocketReaders=50 <your client program>
    http://www.weblogic.com/docs51/admindocs/tuning.html#tuning clients
    Srikant, [email protected], http://weblogic.bea.com/, etc.
    Bernie Wong wrote:
    Fellow clusterers ....
    I have an EJB driver program that pumps work into a WLS cluster. For
    scalability, I increase the number of drivers. The drivers have a big pool
    of work to pump into the cluster.
    I noticed that with 6 (nothing special about that number) drivers, I can get
    500K worked items per hour in a single instance (clustered). That is, the
    instance is cluster enabled and is watching for multicast, etc..
    When I add the second instance into the cluster, the cluster-wide throughput
    with the six drivers drops to 370K items per hour. When I add the third
    instance, the cluster-wide throughput drops further to 250K items per hour.
    When I kill an instance, the throughput grows back to 370K items per hour.
    When I kill another instance (to get back to one instance), the throughput
    grows back to 500K/hr.
    Can somebody point out what we are doing wrong - do we need to tweek some
    WLS parameters, do we have to avoid some features that limit cluster
    scalability, etc..
    My WLS configuration is .....
    - WLS 5.1, SP5
    - JDK 1.2.1_04c with JIT, no Hotspot
    - we enabled performance pack
    My hardware/software configuration consists of:
    - an E4500 - 8 processor database server - this is only running at 15%
    server busy
    - three E4500 - all 8 processors/6GB RAM - application processors
    The cluster is implemented with one instance per application server.
    Each application server is only 10-15% busy.
    My driver and application is ....
    - stateless EJB driver and stateless EJB bean
    Your thoughts and comments would be greatly appreciated.
    Bernie

  • Error when i increase the SGA to more that 1GB

    I have a server with 8 GB of memory running server 2003. i have 2 instances on the server, everytime i try to increase the SGA for any instance to more than 1GB the instances doesn't restart. the error message is 'Memory realm already exists' among others.

    the error message
    is 'Memory realm already exists' among others.This error is pretty self-explanatory,
    Error:     ORA-27100
    Text:     shared memory realm already exists
    Cause:     Tried to start duplicate instances, or tried to restart an instance
         that had not been properly shutdown
    Action:     Use a different instance name, or cleanup the failed instance's SGA

  • Will increasing the buffer size make flash streaming video stop stalling?

    I have surmised all this on my own so it could be just a fantasy, but:
    I am often the victim of slow internet connections. This means that when I try and watch streaming video it constantly pauses. It's my understanding that increasing the buffer size of flash would help prevent this but I can't figure out how to do that.
    Thanks

    You can pause the video just long enough for the player to load enough content. Most Flash player show a loading bar if you hover the player. For short pieces you can load the entire content before starting the play.

  • Troubleshooting of 370 A tektroniks curve tracer. Output get disabled when we increase the current to the device.how to troubleshoot?

    Output get disabled for Tektronics 370 A curve tracer when i apply current to the device from curve tracer. Please give me some iea to troubleshoot the problem.

    hello,
    i don't have tools needed but , i see one thing is that you enqueue 
    every time you are greater 3 that means about every 2-3 ms so consumer is really   sought
    is it really what you want ?
    may be you want to start on a treshold so you can use a treshold fonction 
    if i don't make mistake your square is 10 hz and the daq is configured 25000 sample 25000 hz
    so you aquire 1s of signal every 100ms , there is something to correct
    make tests and tell us
    Regards
    Tinnitus
    CLAD / Labview 2011, Win Xp
    Mission d'une semaine- à plusieurs mois laissez moi un MP...
    RP et Midi-pyrénées .Km+++ si possibilité de télétravail
    Kudos always accepted / Les petits clicks jaunes sont toujours appréciés
    Don't forget to valid a good answer / pensez à valider une réponse correcte

  • Anyone got this error message when going to the creative suite color settings from the bridge ?

    I got this error message saying :"BRIDGE'S PARENT APPLICATION IS NOT ACTIVE, Bridge requires that a qualifying product has to have been launched at least once to enable this feature.
    Plz anyone do you have any tips or help to fix this problem? thank you very much

    What do you have installed, in what form did you acquire it, and what kind of computer you're using please?
    So Bridge doesn't think you have any other Adobe programs installed properly.
    If this isn't a trial or cracked version you're using, you're entitled to free installation support from Adobe by phone.

  • Hi ! dont know But when im saving my project to an PDF file i loose quality on the project.  I dont know what to do. its very importent for me to not loose the quality

    Hi i loose my quality on my project when im saving to an PDF file.  . What to do?

    lq,
    Are you working in RGB Color Mode? If so, you will almost certainly be disappointed when the colours are squeezed into the smaller CMYK gamut.
    There may also be a question of colour management/settings.

  • FireFox with adobe flash using a retina macbook pro under win 8.1 64 bit is lagging . when you move the mouse above any flash game / video

    Hi
    I asked this question again and i reported this bug , i am a computer engineer and i tested it with few macbook pro retina laptops , when u use win 8.1 64 bit or 32 bit and install adobe flash under firefox try to play any game in facebook , view video on youtube or use any FLASH video and move the mouse above the screen of the flash game / video / etc , the screen will lag alot .
    under chrome this problem doesnt exist but the screen is blurry in chrome when using retina screen thats why firefox is better , but the problem is annoying .
    i tried to disable hardware acceleration as you suggested still the same problem

    Hi thesoulkeeper,
    Do you have the bug number? We can try needsinfo to ask for some help.

  • Why is the video loosing quality when i import?

    i just downloaded the final cut pro x trial after wanting something more than imovie, and to be honest i much prefer it to the old final cut.
    but someting is going wrong somewhere.
    i record gameplay from my xbox and edit to and so on in imovie 11.
    so i got final cut pro x trial, imprted my game clips into final cut from imovie, but it isnt as smooth for some reason. rather than running 100% smooth, it jumps a little bit, as if it were a scratched cd.
    all the settings seem to be as they should be but im getting nowhere.
    any help is much appreciated.

    What year is your iMac ... how much memory ... which graphics?  Have you gone into the Preferences under the Final Cut Pro menu and selected the Playback tab and set to Use Original or Optimized Media ... then under that set the Playback Quality to High Quality?

  • Three-Way Color Corrector Eyedropper Tool Not Working on Second Display in OSX Maverick

    Hello,
    Since updating to Mavericks at work on Monday, I have been unable to use the Three-Way Color Corrector's eyedropper tool on a dual-screen setup in Premiere Pro CC.
    I have all of my panels, apart from my Program monitor panel, on one display. When I select the Three-Way Color Corrector's white balance eyedropper and go to the second display where my Program panel is, it turns back into an arrow and doesn't allow me to select anything. When I move my Program panel to the same display as the others it lets me use it as normal. Unfortunately that is not how I work and I would like the program to function as normal.
    I was wondering if anyone else has had this problem and discovered a solution. I will submit a bug report right now.
    Thank you.

    Hi Punker,
    Thanks for posting the workaround. This is a known issue that we're investigating. Fow now the workaround is to:
    Goto> System Preferences>Mission Control.
    Un-tick "Displays Have Separate Spaces"
    Logout or Re-boot system.
    The issues should be resolved.
    Best,
    Peter Garaway
    Adobe
    Premiere Pro

  • 3 Way Color Corrector causing major slowdown

    I'm working on a project at the moment and doing some color correction.  When I apply the 3 Way color corrector to clips, it causes some MAJOR slowdown on my time line, even after the clips have rendered, When I remove the filter, the problem disappears. The footage I'm working with is 1440 x 1080, mpeg-4 video from a Canon handicam (not sure make/model, I didn't shoot the footage). I tried searching the forums, and didn't come across anyone else who has run into this problem. I'd rather not use other filters to make my adjustments, as the 3 way really does a good job of cleaning up the image.
    FCP 7.0.3.
    OSX 10.7.3
    2x2.4 Ghz Quad-Core Intel
    16GB 1066MHz DDR3 Memory
    Thanks in advance,
    Kyle

    Okay, thanks for the info Shane. However, that creates another set of issues.  The camera actually records in MTS, which I converted to mpeg-4 (given that it appears like it would work).  The rough cut is done, and I really don't want to go back and do a recut. The problem is that I can't find a good MTS conversion software that will let me convert to ProRes 422 or ProRes LT. Mpeg Streamclip doesn't even recognize the MTS files, which is obvioiusly annoying.
    I'm assuming that if I am able to reconvert the files, I will be able to "replace" them in FCP, as all FCP does is link to files... correct? And is there anything you would recommend in terms of conversion. Should I convert the mpeg4 files I have or try and convert the original MTS files.
    It's been a few years since I've done any major editing, so I'm a little out of the loop.
    Thanks again for your help.
    Kyle

  • Audio drops when using Three-Way Color Corrector in CS6

    Hello all,
    I recently encountered a very odd issue while editing a friends wedding video using Adobe Premiere Pro CS6.  I had an interview with a guest laid over a music track and had all the audio adjustments made to both audio tracks so that the levels were where I wanted them.  I then added the Three-Way Color Corrector to the video track and corrected the footage to my liking.  When I played back this section of the wedding video, half way through the person's interview, his audio cut out.  The audio from the music track was still playing, so it was not that audio drop that most people are familiar with within Premiere.  I even muted the music track and played back the mentioned section of video and at the same exact point in time his audio just cuts out completely.  I checked to see if any weird key frames had been added and nothing had been touched (that I could see).  Also, the audio waveforms were still visible.  I deleted the Three-Way Color Corrector effect off of the clip and suddenly there were no more audio problems.  Eventually, needing color correction, I added an adjustment layer and assigned the Three-Way Color Corrector to that and had no issues, but I still don't see what could have been the problem, and it seems like a glitch to me.  Has anyone ever had this happen to them?  If so, what are your thoughts?  Thanks!

    The help does not tell you where the Tonal Range output now is as it has moved from the Output Menu.

  • CS4 + CS5 Brush CURSOR outline disappear when increase the brush size

    Hi
    In Photoshop CS4 and CS5, the outline of the brush cursor starts to disappear when you increase the brush size.
    It's OK under 65px in diameter and it's start to disappear over 66px. In 438px the outline is a single dot and over 439px the cursor outline is completely gone!
    I read that it's caused by the old drivers for the video card. I'm using GeForce 8800GT and I updated the driver with the latest version form the nVidia web site. The problem is still here!
    HELP?

    I'm seeing a bit of a pattern of multiple people reporting problems with nVidia 8800 cards.  I'm thinking nVidia isn't testing new drivers against this particular model very intensively.  See my comments on video cards and drivers in this thread:
    http://forums.adobe.com/thread/682582
    -Noel

  • Midi instrument stops playing when I move the mouse button

    Hi. Weirdest thing. All of a sudden, I started noticing some strange behavior with my midi input. 1) I can play a selection for a given software instrument, but, if I move the mouse, the midi input freezes (for lack of a better term). I am using logic 9, and it happens with whatever instrument I open.
    Bottom line, its as if touching/using the mouse freezes the midi input for about 3 seconds, as if the midi got interrupted by the mouse movement. This hasnt alwatys happened, and the midi output region, when I record, the midi region has a big 'X' in the display of the region. What is that, and what does it mean?
    Thanks.

    Hi, thanls for your response, and I looked into the event list, but, I dont have a graps of what it is you are suggesting I do. I am a newbie at this, so please bear with me, and break down that answer into a little bit more simplistic terms.

Maybe you are looking for