AVCHD sucks!

matt s. said:
Are you transcoding ¥our footage? Are you trying to edit the raw avchd files? We need more info. I have yet to see any macroblocking from anything I have shot with an HMC.
Click to expand...

no offense, but if you hav'nt seen it, it's because you don't have a eye for it.
ANY camera even at 100MBPS will have macroblocking that is easily picked out PERIOD. the hmc at 24mbps i can pic out from across the room.
 
I have to say I've never seen anything remotely like that screengrab out of my HMC40, which has the same bitrate AVCHD. (I transcode to Cineform, since Premiere doesnt handle native AVCHD decodes correctly)
 
Sideside,

There must be something in your water that makes you more able to see the problems with AVCHD that the rest of us don't see.

I am sure it must be the camera!

Grant
 
sideside said:
no offense, but if you hav'nt seen it, it's because you don't have a eye for it.
ANY camera even at 100MBPS will have macroblocking that is easily picked out PERIOD. the hmc at 24mbps i can pic out from across the room.
Click to expand...

Yup! I can agree with this. I can find macro blocking on all the digital video footage I've ever looked at and you don't have to look very far to see it at 100%. The question is how best to minimise it.
 
Hi,

I have never seen any thing like that screen grab you are posting out of any of the AVCCAM product line, from the HMC40 through the HMC150. Nothing. There is either something wrong with your camera or something wrong with your workflow. Try this. Import into your NLE, if FCP, go to ProRes 4:2:2 HQ. Do a frame Grab from your timeline. Post the entire frame here. Don't turn it to RAW, keep as BMP or JPG.

Thanks,

Jan
 
I dont think you are importing your screen grab correctly and my guess is you are only grabbing a window preview of your NLE. If it were a "raw" grab it would be 1920X1080 but your png is only

818X588
 
Must be something in your setup too. I've had really a very positive experience this past two years. I had an HVX and sold it cause the HMC did most of what I wanted at a cheaper price. The only area that the HVX was better at was the greenscreening cause it was a lot more forgiving if things on the key weren't perfect.... Overall though, I intercut the HVX and the 150 seemlessly with some really great results....
 
So how about this and this? Take a look at her arms. Such a flickering squares I would show you at much more clips recorded in sunny and cloudy days, in sun and in shade. Beautiful blocks on arms, around face, on neck, forehead, etc.
Reset and black balance only reduce that problem but dose not resolve it in 100%. Problem is back every time.
Good results are only at 720 25p (PH mode)
Maybe Vitaliy would rise bitrate to 30 or more ;) because it looks like 24 is not enough for 1080i/p nor 720 50p and my private opinion is not to buy AF 100 untill there is the same AVC 24mbps :(

*footage removed
 
Last edited:
that image was cropped as to fit in a browser window and to target the problem area, the rest of the shot was just green bg. but again that's 1:1 from the camera.

and yes it's PH, and Lighted well and in focus, and pretty standard settings, and NO your computer would not have any effect on it, and not it's not encoded , thats raw.

starting to think theres somethign wrong iwth my hmc, it's extremly grainy ontop of the macroblocking (im thinking one is causing the other) :(
 
ggrantly said:
Sideside,

There must be something in your water that makes you more able to see the problems with AVCHD that the rest of us don't see.

I am sure it must be the camera!

Grant
Click to expand...


what arrogance, if your ignorant on a topic just remain quite, you dont have to speak up
 
can you get your hands on a second 150 to make a side by side comparison? Your results don't match my results or anyone else here it seems....then make sure your NLE is set right. Can you see this macroblocking when you use the Panasonic viewer software? (I know, it sucks but as an alternative to be able to baseline that it isn't settings in your NLE).

I've had my camera six months, have shot close to 75 hours of video, and never seen what you describe. So my guess is to look at camera problems, or NLE settings (since you are new to AVCHD, it could be that you haven't set your settings right.)
 
Side,

I am neither arrogant nor ignorant. My comment spoke the truth; you may have an issue with the screen shot you posted, but most of us get along just fine with AVCHD. I shoot in both AVCHD and DVCProHD and I can tell you that AVCHD holds up quite well to ProHD. Many users here produce quality output with AVCHD on a daily basis and are quite happy with the results. Is it the best codec available, no. Is it better than HDV, yes. Your experience seems to run contrary to most folks here and you seem more interested in shouting than solving, which in this case, won't get you far.

Grant
 
sideside said:
that image was cropped as to fit in a browser window and to target the problem area, the rest of the shot was just green bg. but again that's 1:1 from the camera.

and yes it's PH, and Lighted well and in focus, and pretty standard settings, and NO your computer would not have any effect on it, and not it's not encoded , thats raw.

starting to think theres somethign wrong iwth my hmc, it's extremly grainy ontop of the macroblocking (im thinking one is causing the other) :(
Click to expand...

There was (probably still is afaik) a problem with avchd on Premier, is that how you are opening up the raw AVCHD file? Barry ended up reporting the issue to Adobe, but I don't know if they fixed it in the end or not.

Basically the image quality was very poor and blocky. If you are using premier it might be worth transcoding into an editing format before importing into premier (maybe use the panasonic software that converts it to DVCPro HD.

It isn't a problem with AVCHD itself as Jan has already made clear.
 
studio1972 said:
There was (probably still is afaik) a problem with avchd on Premier, is that how you are opening up the raw AVCHD file? Barry ended up reporting the issue to Adobe, but I don't know if they fixed it in the end or not.
Click to expand...
They finally fixed it on the latest update (5.0.2).
 
You must log in or register to reply here.
Back
Top