Chris Young
Forum Replies Created
-
Ah Rik! Not Heather ~
Good, it sounds like the dealer is playing ball with the swap. Yes please keeps us all posted for sure.
Cheers
Chris
Sydney -
Hi Heather ~
You are not alone! Know someone who has just tested the HPX250 and the AG-AC160, basically similar but the AVCHD model. BOTH cameras exhibited exactly the same focus issues so I don’t at this point feel your camera is the only one. If it is indeed an issue in these models then Pana needs to attend to this quick smart.
I had this camera high on my watch list along with the Canon XF305. Spent a fait bit of time shooting on the Canon for others and can’t fault the lens on it.
Think I will be holding off to see what our local Pana dealers find out about this as they have been informed. Being good dealers I believe they will follow it up with Panasonic pretty quickly. If Pana have a solution to the problem then the 250 will be back on my list.
Bit surprising that this hasn’t been picked up on earlier testing!
Keep posting as to the outcome on your camera as a few of us will be very interested to see what feedback you get and how it all gets resolved. Good luck.
Chris Young
Sydney
Aust -
Jack. Try the following before you render.
Once your project is finished make sure you have no anti-virus monitoring disc and file activity. Make sure that any disc-defrag software is disabled. In your preferences set Dynamic Ram to zero and rendering threads to 1. Finally save your final project as a ‘Render to FINAL’ or some such name and now go to your ‘Project Media’ bin and click on the little gold lightning bolt in the top left corner of the bin. This will REMOVE all UNUSED media in your project. Re-save to your ‘Render to FINAL’ project. Re-start your PC and go render.
Have done over 400 programs for TV and ALL based on MXF files from the EX series cams and PDW 300-350 and PDW 700-800 series and as Stephen I think mentioned have around half a dozen hangs a year and usually when I check them out it’s self induced by me the operator.
The only time we were really boxed in with issues like you outlined it turned out to be a bad stick of ram. Discovered that after running some ram torture tests. Swapped out the bad stick and that machine came good again.
Chris Young
CVY Productions
Sydney -
DSE ~
Have already reported to Sony. Plus sent them a sample .mpa audio file just in case it is a container/wrapper issue. Yes all worked fine in 9.0c, just tried it on another box that hasn’t been upgraded yet. HDV is fine in all versions. Wait untill I hear back I guess.
No big problem, just bringing them into 8.0c and redering them out as .wav or .mp3 as required.Cheers
Chris Young
CYV Productions
Sydney -
Truly EPIC! Yes you can open a v9.0 64-bit in 9 32-bit.
Chris Young
CYV Productions
Sydney -
Yes, very interesting! Thanks for the heads up. Am downloading it as I write. If this is half as good as their Raylight Ultra plugin for P2 files then it should be good. Will find out very shortly.
Chris Young
CYV Productions
Sydney -
Ed ~
Yes you are 100% correct. I should download the latest versions I guess. Doing mainly TV stuff so it’s the good old cut and some dissolves that we use most. In fact I can’t remember the last time I used Pixelan wipes. Vegas has most things I ever need.
Chris Young
CYV Productions
sydney -
Oh yes, no problem. I also have v8.0c on board as it is still one of the most stable Vegas versions to date. It is mainly some of the NewBlue and Pixelan organic type plugins that are sometimes suitable but not available in 64-bit.
Chris Young
CYV Productions
Sydney -
Oh yes the drives. Multiple drives is a must for serious editing IMHO. I run a four disc hardware raid for all the video material and as previously mentioned make sure your ‘Vegas Temp’, ‘Vegas Recorded’ and Vegas ‘Prerendered’ folders are nowhere near you ‘C’ or OS drive. That is a deal breaker for some systems with heavy rendering requirements. A lot of your working and rendering goes on in the Temp folder until such time as your project render is finished and appears in the drive/folder you nominated. Not that I think that this is your primary problem.
The following are only my observations but they have me intrigued. I may be way off but I don’t think so.
What I have discovered with the Canon AVCHD HD files is that frequently they DO NOT end on a frame boundary. If you throw a bunch of clips on the timeline straight from the Project Media bin you often find that there is a minute gap between some of the files. A half frame gap! Vegas correctly drops the next clip on the next frame boundary, as it should.
Zoom in on the timeline and you can see clips ending half way across a frame. It appears to me that the long GOP structure of the AVCHD H264 MOV files are not being closed correctly when the Canon cameras stops recording.
With H264 it’s a new concept GOP structure where a ‘B’ frame can also become a reference frame as well as the ‘I’ frame, this makes it an inherently more complex GOP to decode and re-encode dynamically. What is concerning me with these Canon files is that I believe the GOP structure has been compromised in the GOP sequence not being closed correctly. If this is the case then it’s hardly surprising that Vegas or any other software has issues decoding and re-encoding HD files working with GOPs that contain these half frames. This is why trying to render with them is a major headache hence the Vegas hangs. I know with the Cineform converted files from Canon AVCHD it’s a breeze to edit with them and render from them.
If Cineform conversions run out of sync it doesn’t surprise me as every Canon H264 clip I convert to Cineform ends correctly on a frame boundary. I am surmising here that any of these Canon half frame ended clips will be shortened to the closest closed GOP boundary where Cineform can create a complete inter-frame. I am curious, are you are trying to marry up Cineform files back to the audio from the AVCHD files? If so then I would expect to have problems, as they are now no longer the same duration. What the answer is I don’t know but if anyone has any in dealing with these Canon files when editing I for one would like to know.
Chris Young
CYV Productions
Sydney -
I do most most of my work in the 64-bit version due to the better Dynamic Ram access and faster rendering. I have numerous 32 bit video and audio plugins that won’t show up in Vegas 9 64-bit. If I need to use these I can open the project up in the 32-bit version and apply them as neccessary.
Sometimes I have finished the project in the 32-bit version but have often rendered out the segments I need from the 32-bit with the plugins I want applied then brought those clips back into the 64-bit to finish the program. If I know I will need a bunch of 32-bit plugs then I just do the whole job in v9 32. So what if it takes a bit longer to render, it’s not a big deal breaker here. Install both versions, won’t cost you any more.
Chris Young
CYV Productions
Sydney