Announcement: Our new CyberLink Feedback Forum has arrived! Please transfer to our new forum to provide your feedback or to start a new discussion. The content on this CyberLink Community forum is now read only, but will continue to be available as a user resource. Thanks!
CyberLink Community Forum where the experts meet|Advanced Search >
HalConSenior ContributorLocation: Charlottetown, PEIJoined: Mar 01, 2008 10:36Messages: 719Offline
Oct 05, 2010 10:28
Dafydd,
I also have received this message. I recently purchased a Panasonic HD TM-20 camera. The media from the camera is .mts
I can import and edit the files fine but when I try to produce to AVCHD with the same option as above (AVCHD 1920x1080) I get that error. I can reduce to the next lowest (I am not at home right now so I can't give the option I used, 1440x810? I think) I get a successful render.
I use PD8 Ultra v-3022, basic system specs below.
Hal
OS - Win11 Pro, Alienware R13, CPU - Intel Core I7-12700KF 12 CPUs), 16g DDR5 4400 RAM, Video - Geeforce RTX 3080ti 12g, PD11 & PD365
My YouTube
HalConSenior ContributorLocation: Charlottetown, PEIJoined: Mar 01, 2008 10:36Messages: 719Offline
Oct 05, 2010 17:56
Dafydd,
When David installed his patch it must have fixed my problem also. I cannot replicate this evening.
I successfully rendered to three profiles in the AVCHD drop down list. The only difference between now and last evening is a fresh start of the computer.
I am attaching the Media information from the original video and the information for three produced files in different AVCHD profiles. I have some short clips ready if you think they are required.
I have had that similar "error message" all they way back to PD6 when I try to produce 1080 video with editing that causes a lot of memory to be used as in stabilisation, video enhancements etc.
I have the latest patch and latest build running Vista 32bit with an i7 920 cpu.
Long story short and I mean Loooong Story. If you are running an i7cpu the only solution I have found that works is to cripple your i7cpu chip down from 8 cores to 2 cores.
For HalCon and david_lexicon, be aware that you may have thought you have solved your problem, I have a sense that it is still there and keep this post handy if the problem comes up again when you push your system with a more complicated 1080 video.
1. Go to start...run...type 'msconfig'....boot....advanced options...put a tick in 'number of processors'....select '2'....reboot.
I can have the most complicated and intensively edited 720 video with no problems but as soon as I try to render to 1080 I get the above mentioned "error messaage" It is something to do with Windows 32 bit systems being hardwired to only allow 2 gig of ram to be allocated to any one program no matter how much ram is on the system and PD wants to use more than 2 gig of memory when things get complicated producing 1080 video.
HalConSenior ContributorLocation: Charlottetown, PEIJoined: Mar 01, 2008 10:36Messages: 719Offline
Oct 05, 2010 20:24
Thanks Robert2 S,
I made no changes since I first tried to produce the files. Last evening on three different files I got the error. Tonight when I tried to replicate the problem I was able to render every try. I had never seen that message before last night.
My system used all 4 cores, never checked the memory usage though. I will be doing more work with these files over the next day or two.
I am testing the camera to see if it suits my needs. I have about two hours of clips to work with and test. Clips are between 25 seconds to about four minutes long.
Will keep you posted.
Hal
OS - Win11 Pro, Alienware R13, CPU - Intel Core I7-12700KF 12 CPUs), 16g DDR5 4400 RAM, Video - Geeforce RTX 3080ti 12g, PD11 & PD365
My YouTube
In my long long hours, days, weeks of testing it appears that the error message comes up when PD crosses from one clip to the next when producing to 1080 not 720. Like say a 2-3minute clip to the next clip, it rarely crashed in the middle of a clip.
If you want to test it drop your 4 minute clip onto the timeline.
1. Use Video enhance at default then use colour adjustment with just a touch of contrast and sharpness.
2. Drop the same clip onto the timeline at the end of the first clip.
3. Then produce the video to 1080 H.264 AVC at say 17Mbps.
This is what I was doing with a recent hang gliding video and was consistently getting the above mentioned error message. I had a separate voice track but was only using 1280X720 8Mbps video but rendering to H.264 AVC 1920X1080 at 12Mbps. If I produced it to 1280X720 no problem it was the 1080 producing that has always caused my crashes.
This is the video, I think I still have a touch too much contrast but hey its all fun.
It was consistently crashing at the 2 min 29sec transition to the next clip.
The reason I say it is a memory thing is that sometimes on a fresh re-boot it won't crash then other times it will. It seems as though the type of editing I do when producing to 1080 has PD on the edge and the only consistent way out as I said was to cut down my i7cpu down to 2 cores.
HalConSenior ContributorLocation: Charlottetown, PEIJoined: Mar 01, 2008 10:36Messages: 719Offline
Oct 05, 2010 21:45
Robert,
I did two tests tonight, 7 clips. I made some cuts in each clip. Two clips have lighting balance corrected and white calibration done. Total finished length 50 seconds.
Fade transition between each clip. Rendered to 1920x1080 24bit(22.95 in the properties) and 1920x1080 17bit(16.02 in properties) no problems.
I figure I will see the error again sometime.
I am not overly impressed with the quality of the clips from the camera though. I am getting near the same quality with a JVC SD camera. The Panasonic will not pan the action of a hockey game well either. Got quite a few 'panning too fast' error messages with the HD camera. I am seriosly considering returning the Panasonic for something else in its' price range.
I have watched that video a couple of times in the past, really enjoyed watching it. Great shots. But you would never get me up on one of those things.
Hal
OS - Win11 Pro, Alienware R13, CPU - Intel Core I7-12700KF 12 CPUs), 16g DDR5 4400 RAM, Video - Geeforce RTX 3080ti 12g, PD11 & PD365
My YouTube
The problem with crashing at transitions seems to be when the transition is from one clip that is at least 3 minutes long to the next clip. Not from short clips. The short clips don't seem to use as much memory as a longer clip. Maybe this is one reason why I seem to have more problems than most as my clips can be minutes long, especially when I have the camera mounted out of my reach. Where most people shoot in short clips.
The trick with getting the best quality with videos is producing to the same format with the same resolution or higher with at least the same bitrate or higher than the raw video. There are so many options when producing a video that it is very easy to pick an option that is a different format, lower in resolution or lower in bit rate, choosing a lower bit rate is definitely a way to drop the quality of a produced video.
My youtube channel====>http://www.youtube.com/user/relate2?feature=mhsn
Dafydd BSenior ContributorJoined: Aug 26, 2006 08:20Messages: 11973Offline
Oct 06, 2010 05:47
Hi Hal,
I could still do with a few sample clips from that Panasonic camera - to add to the camera sample collection, if you've a few minutes spare and can upload them.
HalConSenior ContributorLocation: Charlottetown, PEIJoined: Mar 01, 2008 10:36Messages: 719Offline
Oct 06, 2010 12:09
Dafydd,
I will be deciding today or tomorrow. Am considering another JVC or a Cannon. JVC might be the preference because I have one now and some of the assessories might fit.
Which ever I will upload some samples as soon as I get them.
Hal
OS - Win11 Pro, Alienware R13, CPU - Intel Core I7-12700KF 12 CPUs), 16g DDR5 4400 RAM, Video - Geeforce RTX 3080ti 12g, PD11 & PD365
My YouTube
Cyberlink.com uses analytical cookies and other tracking technologies to offer you the best possible user experience. By using our website, you acknowledge and agree to our cookie policy. For more information on cookies or changing your cookies settings, read CyberLink’s Cookie Policy.