I'm a new user to PD, had used Pinnacle for about the last 10 years since switching a month ago. I had my ups and downs with it, but overall produced some pretty good stuff over the years. Here's an example of a video I produced from Penn State Homecoming just weeks before the Sandusky/Paterno news blew sky high:
http://www.youtube.com/watch?v=y2J5lXoJYg8
I hope it plays back smoothly for you, because many edits are meant to hit at exact points (on exact frames).
I was ready to upgrade from PS 12 to 17 but I started reading a lot of negative feedback on it. At the same time, I came across PD and saw rather good feedback and PCMag.com's award. So I figured, why not, let's try something new. So far it appears it has a lot of potential, but then again I feel like I've traded in one set of problems for another. For one, as I stated in a previous post, I thought my rig would produce faster and better results while editing and previewing. But I won't harp on that again. I did learn that using Render Preview improves the playback immensely. I make lots of very precise edits when I work, and choppy previews are a pointless waste of time.
But to address this specific thread, I *did* install 2706 before Cyberlink removed it. Again, being a new user, I'm not sure how many of my bugs are specific to this patch, but I will list a couple. I didn't try and switch back to 2420 since Playsound (above) said it blocked him from the work he did in 2706, which is my situation too.
I don't know how many people use 5.1 wav files in their projects, I'm hooked on them and enjoy creating them in Audacity. But after setting my control points in said audio track, which lies beneath a video track, on most occasions, when I make a change in that video track, and Render Preview it again, the audio track starts blasting (like it returned to 0db, I have it knocked way down). Several things fix it, but none consistently. Sometimes restarting the app fixes it. Sometimes sliding it from one audio track to another fixes it. Sometimes wiggling a control (volume) point in the track fixes it. Classic bug it appears. 2706?
Another annoyance, I'll be working on one part of my project, only to notice an audio clip in another part of my project (on its own track) has either moved or jumped to another open track. I'm careful when I'm trimming other clips not to cause other dominoes to fall. 2706?
Finally, when an audio clip on one track ends, it will create an audible hiccup in another audio track underlying it, and dropping a control point all the way down to silence the offending audio clip didn't help. At first I figure it was just poor quality in the preview playback and didn't worry. But when I rendered out the movie, oops, it was there. 2706?
Just seems to me these are pretty basic bugs that should have been ironed out years and years ago. I'm hoping I just happened to come along just at the time Cyberlink released a bad patch. I will pack my patience, and await the next patch, hoping things smooth out!
This message was edited 1 time. Last update was at Mar 24. 2014 22:32
Windows 10 64 Bit
ASUS Z87 Pro MB BIOS 2103
i7-4770K Haswell OC'd to 4.3Ghz
16GB Corsair Vengeance DDR 1600Mhz
EVGA Geforce GTX 960 2GB GDDR5 v368.22
Samsung SSD 840 Pro 256 GB (Rapid Mode)
Power Director 14 Ultimate 64 Bit