AKH

Something to consider: With All-I intraframe compression (IPB has interframe compression), increasing motion may actually make the compression require less bitrate than a static image. A blurry photo requires less data to maintain quality compared to a sharp photo.

For Premiere 5.5 I would right click on the footage in the project window and select Modify -> Interpret Footage. Make sure framerate is set to 25fps and Field Order is set to No Fields (Progressive Scan). Hopefully that will be enough clear the problem.

I'm going to hazard a guess that the MTS file is being treated as interlaced content by premiere and is deinterlacing it to put it on the timeline. Should be able to turn it off if that is the case.

The Sigma doesn't have completely constant transmission across it's focal length range. http://www.dxomark.com/Lenses/Sigma/Sigma-18-35mm-F18-DC-HSM-A-Canon-mounted-on-Canon-EOS-700D---Measurements__870 Would the speedbooster make it more noticeable? Not sure.

This all reminds me of a useful tutorial from a few years ago. You don't have to use AE to apply these techniques. http://greyscalegorilla.com/blog/tutorials/how-to-remove-banding-artifacts-in-after-effects/

Read the next post after yours on that forum...........willfully missing the point. Some forums are just too frustrating to bother with.

I was under the impression from reading the instructions off the Panasonic website that the GH4 can output 4K in an MP4 or a MOV container, so you shouldn't have to work with MOV at all if you don't want to. Vegas should be able to decode MP4 natively.

I'm guessing it is a setting relating to monitor display over HDMI to avoid playback jitter on screens that support 24Hz. Edit: It also seems that according to current standards 4K can only be transmitted over HDMI at 24Hz, whereas UHD can/will go higher in the HDMI 2.0 spec. Edit2: Having looked at the GH4 instructions, 24Hz (Cinema), 50Hz (PAL) and 59.94Hz (NTSC) are just system frequency settings to keep recording framerates divided into their specific regions. 4K records at exactly 24fps (only available in 24Hz mode) whereas UHD can record at 23.98fps, 24fps, 25fps or 29.97fps depending on what the system frequency is set to.

That sounds like a hardware fault on your camera.

I would give a +1 for the Nvidia 750 suggestion. The 750 has a much reduced power footprint over the previous generation. Its max power draw is about 60W (the 650 is approx 135W). You can get away with a 400W power supply with even a fairly power hungry cpu and it is powered by the pcie slot alone.

The whole concept of privacy in a public place is a rather odd one. A right to privacy implies that other people don't have the right to know what you are doing unless you permit it. If you are in a public place everybody can see what you are doing, therefore you have no privacy. This has implications beyond just photography and videography if taken to it's logical conclusion. The mere knowledge of a person being in a particular place at a particular time could be taken as an invasion of privacy. Perhaps Germans should look see this public information film for advice:

  How do you think digital cameras in general handle ISO?   The sensor itself has a fixed sensitivity to light (native ISO) and doesn't vary.

One thing to note.  ACR applies sharpening by default on dng files.  So if you haven't zeroed it the noise does get lifted a bit.

I don't think this issue is particular to one OS. Premiere doesn't always make the right decisions when it comes to decoding .mov files. Best performance is usually achieved when Premiere uses its internal codecs to decode, but with some .mov files Premiere decides (wrongly) it cannot decode the file internally and falls back to using Quicktime for decoding duties. Changing the extension of the file forces Premiere to try it's internal codecs. I experienced bad stuttering with Nikon .mov files. Simply changing the extension to .mpg resulted in no more stuttering. The work-around solution came from Creative Cow.

Try changing the extension of the footage from .mov to .mpg then re-import into CS6. If this solves the performance problem then I may know what the issue is. I'll elaborate further then.