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 >
Only problem I am having is with PD 12. Support suggested that I created a dump file from Task Manager for PD 12 ( r/click create dump file). That crashed my machine completely and even reset my BIOS to its basic state. That was fun getting all the drives reset and finding I could not burn discs as Win 8 was now seeing my Bluray burners as "CD Discs". That was fairly easily sorted in the BIOS - but baffled me until I looked at the system manager.

However, PD12 now works! It does have the odd hiccup but at least I can complete my DVD creations and edit files/videos.

It would appear to be a software clash - not figured out what with yet, but if PD12 runs alone, it operates fine. Been trying software like IE 10, Mailwasher, Outlook - so far not found - but still looking.

Will let you know if I get anywhere.
That sounds like a very useful bit of software/tool for this type of error.

I have 100GB of free memory on my SSD + 128GB virtual on SSD as well.

It's probably software clash more than hardware I would have thought - but presume the crash logs will assist those in support. No error messages the programme simply closes - very quickly!
I have tried support and carried out their suggestions with no improvement. Have the latest drivers for Video(GTX 680), sound (no sound card installed) using the latest version of PD12, Quick time is also up to date. Have an i7 unlocked, 64GB memory, 500GB Samsung 8 SSD drive with 2 other Red 3tb drives so the PC is pretty up to date on Windows 8 operating system.

Only started having the problem after the latest round of Windows updates - that might not be connected as I have only had 12 for s short period of time.

Quite simply every time I place an object (sound or video) on to the timeline the programme simply closes.

Anyone else having this problem or can think of something that might be causing it. Support is working on it but just putting it out there if anyone has experienced this problem and found a solution.

Thanks. :
Hi,

I thought the content was very relevant to the problem being experienced by the poster. The problem seems to lie in the number of "sound" files being used in the edit.

One sound file and it appears to be OK, more than that and it does produce this juddering, out of sync problem.

Try cutting the number of sounds channels and see how he gets on?

In fact when I get a chance to run some tests I will try that theory - surely that is relevant to the problem?


Hi,

Sorry there is no problems in the viewable video once you render it. There is a very slight knock on effect due to the codec Youtube uses in its compression but that is hardly noticeable.

The problem is only in editing. When you start off there is not a problem so in my case the audio and lip sync blend together it is only when you start to add fades and inserts does the problem kick in. You play the video and the sound goes well but the video will lag/judder well out of sync.

I now think the problem is with sound - not video. If it was video many would have the problem and not just a few.

I have completely changed my machine (PC). Switched operating systems to Window 8, spent £1000's on hardware and still have the same problem?

Conclusion - the problem is in PD 11. Probably how it handles sound. My new system has a new 24bit sound card and system installed so not the output. I think PD 11 cannot handle multiple sound tracks? Will need to experiment a bit but I think that is where the problem lies.

My .mov files used to take nearly 2 hours to render off about 12 mins of footage. My new system does it (7 mins of footage) in 8 minutes!!! Fab stuff.

Will keep you posted.
Hi,

Steve sorry about the multiple replies but I have to say that the problem is in PD, or at least appears to be.

I record sound from one source (the camera) and then have the event recorded professionally. This master recording is laid down on the track and I try to sync the normal sound to the video. I them mute the normal sound and leave the master source in place - in sync to lip movement. This is fairly standard practise in video editing.

As you add in tracks/effects the vies start to stutter - making it impossible to lip sync. made this public to give you an idea:

http://www.youtube.com/watch?v=WzJB0_wIUCc not a lot of transitions/effects?

Nearly impossible to lip sync as it get longer.

Thanks for any help. New hardware has made a big difference - but this is till a problem so probably not a "spec" problem but a software clash somewhere.
I have the latest drivers and a cpu/video card spec that will choke a horse. 6 core cpu that does not even get to 33% when I am having the problem.


The machine was custom built for me to edit video. Others are having the problem and it is not the lack of spec on my system. The cache is a 128gb ssd drive etc.

It looks like a software/driver problem.
Initially was told I need to upgrade my PC:

Notes some posters had juddering and sync with long rendering times.

Had the same problem and basically was told my system was not good enough to cope with the files, including .mov files.
Have upgraded to an Intel i7, 3.2 6 core unlocked processor. 64GB ram, ssd 128gb cache on a 300gb Velociraptor and using a Zotan NVidia 680 4gb graphics card. Have 32gb ram as windows cache - and I still have the same problem!!!!!


Its not hardware - its the software, it just has to be!

The rendering of 2 layer videos and editing of same takes minutes now - it took hours on my last machine.

As soon as you layer tracks and music (not .mov files) is gets jerky! Impossible to sync and its frustrating.

Anyone out there with an answer?
had the same problem and basically was told my system was not good enough to cope with the files, including .mov files.
Have upgraded to an Intel i7, 3.2 6 core unlocked processor. 64GB ram, ssd 128gb cache on a 300gb Velociraptor and using a Zotan NVidia 680 4gb graphics card. Have 32gb ram as windows cache - and I still have the same problem!!!!!


Its not hardware - its the software, it just has to be!

The rendering of 2 layer videos and editing of same takes minutes now - it took hours on my last machine.

As soon as you layer tracks and music (not .mov files) is gets jerky! Impossible to sync and its frustrating.

Anyone out there with an answer?
Had the same problem and basically was told my system was not good enough to cope with the files, including .mov files.
Have upgraded to an Intel i7, 3.2 6 core unlocked processor. 64GB ram, ssd 128gb cache on a 300gb Velociraptor and using a Zotan NVidia 680 4gb graphics card. Have 32gb ram as windows cache - and I still have the same problem!!!!!


Its not hardware - its the software, it just has to be!

The rendering of 2 layer videos and editing of same takes minutes now - it took hours on my last machine.

As soon as you layer tracks and music (not .mov files) is gets jerky! Impossible to sync and its frustrating.

Anyone out there with an answer?
It was today's I downloaded. See no reason why it should need much compression in PD at that size.
Basically you have a 4mp sensor with what looks like not a great lens. The image is not sharp and suffers from colour shifts along the image edges. You see green edges running along white objects within the image etc.

You can correct all this within photoshop (to a certain extent) and enlarge the image with other softtware (eg OnOne). Not sure if all that is worth the effort as buying a new camera would probably solve your problem.

I have it as a 16mb file now and the flaws are fairly obvious - as listed above. No (little) dynamic range within the image either so the shadows will block up or the highlights will be blown - as in your image.

Saving it as another format will help, but it will not correct the problems.

You appreciate this is only my opinion - someone may have more information to assist you.
I think the problem is sensor size in the camera. Have not looked at your files but as a photographer who upload a ton of videos to Youtube I cannot see a loss of quality in .jpeg files.

Suspect the images have been captured on a small snsor camera - that would explain the loss in quality?
It's certainly a problem I came up against when I upgraded from Ver 10. Switching back to Ver 10 did not solve my problem but that might be because I did not uninstall Ver 11 but left it on my system.

I have dual core processor, 8GB ram, SSD drive and a WD Raptor and it will not handle the load - see my other threads in interested.

It's OK until you start to use multiple effects or timelines and .mov files (QuickTime - from Canon 35mm cameras) simly overwhelm the system and makes editing impossible.

The files from my Sony (Pro) video camera are easier to work with - until you start adding effects/lines etc.

Version 10 worked well on my PC with the specs listed. Ver 11 is a non starter really.

My new PC should arrive in about 10 days - Intel i7 3930, 64GB 1600 ddr3 ram, 2TB WD, Nvidia GTX 680 4GB. If it does not run on that - then it will need a super computer to work.

Hope that helps.
Thanks Robert. No point in two graphic cards then unless you are a hard core gamer or similar.

Regards,
George
Thanks for that.

Regards,
George
Think you might need to look at my problem posts. I am having to upgrade my PC to get the best out of PD11

You have a new(ish) machine?

http://forum.cyberlink.com/forum/posts/list/25037.page
Thanks Jim.

You edit multiple tracks ok?
Hi,

Looks like my machine will not keep up with multiple tracks and large file sizes so need to upgrade or build a new pc.

Those with the knowledge care to part with some wisdom on a good spec to get the best out of PD11?

2 graphic cards or one etc?

Any advice greatly appreciated.
Hi,

Sorry, you said in your previous post that you could use the SSD drive for PD to access. Just looking for a way to direct PD to look at that drive as a swap file/work area. Rather than use the "C" drive.

Hopefully that makes sense?
Go to:   
Powered by JForum 2.1.8 © JForum Team