Thanks Fred

PD10 has only been out a week or so and a 'patch' already for 'things' that shouldn't of needed fixing

PD9 had 6 patches in 9 months, I wonder how many PD10 will have

Why can't CL get it right first time! Happing editing

Best Regards

Neil
CubbyHouseFilms
My Youtube Channel
My Vimeo Channel
PD3.5, 5, 6 & 7. Computer: Dell Dimension 5150, Intel Pen. 2.80 GHz, 2GB RAM, NVIDIA GeForce 8600GT 256MB, Windows XP Pro!!
PD8 Ultra v3022. Computer: Dell Studio 1747, Intel, i7 Q740 1.73 GHz, 8GB RAM, ATI Mob. Radeon HD 560v 1GB, Windows 7 Ult. 64
PD10 Ultra v2023. Computer: HP Pavilion dv7, Intel, i7 2630 2.00 GHz, 8GB RAM, ATI Mob. Radeon HD 6770 2GB, Windows 7 Pre. 64
PD12 Ultra v2930. Computer: HP Pavilion dv7, Intel, i7 2630 2.00 GHz, 8GB RAM, ATI Mob. Radeon HD 6770 2GB, Windows 7 Pre. 64
PD13 Ultim v3516. Computer: HP Pavilion dv7, Intel, i7 2630 2.00 GHz, 8GB RAM, ATI Mob. Radeon HD 6770 2GB, Windows 7 Pre. 64
PD16 Live v2101 Computer: HP Pavilion dv7, Intel, i7 2630 2.00 GHz, 16GB RAM, ATI Mob.Radeon HD 6770 2GB, Windows 7 Pre. 64
Director Suite 6: PowerDirector 16 Live, PhotoDirector 9, ColorDirector 6, AudioDirector 8

Cameras: Sony(s) HXR-NX5P, HXR-NX70P, NEX-VG10E, a6300 4k, HDR TG5E, GoPro 4 Black, Canon 6D DSLR

Visit PDtoots. PowerDirector Tutorials, tips, free resources & more. Subscribe!
Full linked Tutorial Catalog - PDtoots happily supports fellow PowerDirector users!

Years ago I lead a team of programmers who created the first INTRANET for the Global Company 3COM...we wrote the code and tested it at one location (Santa Clara). We compiled a list of all the equipment that MIGHT be used at all the other offices..and all the languages that might be used.

We had a fixed time/date to start the rollout and there was no "flex". The day we distrubuted/installed it onto the global offices (175)..we KNEW of 447 bugs in the code. We found and additional 375 in the first week and squashed 99% of the total in 3 weeks.

During that time, we had a 24/7 helpdesk who answered issues and supported the users with problems. After 3 weeks, the compliments began to roll in...I won't tell you the language (and I don't mean Swedish versus Spanish) of the problem reports the first day!!!

When we "FINISHED" the Intranet, there were still many active "bugs/Issues" in the code, but the impact on the business line was deemed by Risk Management to be manageable and Acceptable to the Business Unit. For example, you may have been occasionally logged out during your session without warning, but your credit card transactions were NEVER lost or corrupted.

Also, the entire Canadian branch (12 offices, 700 users) installed new Network cards in the machines the day we rolled the IntraNet out, without telling us..they blamed US for lack of connection but it was the card drivers!!! man did that take a while to figure out.

Software is BUGS!!! Bugs are never gone but if the program functions within acceptable parameters, than it is ready and good.!!!

BTW - No, it wasn't our coding's fault that 3COM and Palm(We wrote part of THAT OS, too) failed.....

Hi,
I am just glad I came across this program!
With the amount of computer systems and configurations that are possible it surprises me that cyberlink team do as well as they do with the coding to eliminate a lot of bugs. Most of the complaints ( I find) here on the forum are from people who don't read the 'specs' set out by Cyberlink, and/or supply the requested information needed for members here to remedy the problems or find a solution.
Jim Intel i7-2600@3.4Gz Geforce 560ti-1GB Graphic accelerator, windows 7 Premium 12GB memory

Visit GranPapa64's channel for your YouTube experience of the day!

Well said, FredB. I've had the same experience, from both the developer and customer ends.

The one thing that I've always resented is the reluctance of most companies to make a list of outstanding bugs public. One of my employers did precisely that: every month they sent their customers a CD containing a bug database. The database listed hundreds of bugs!

That database saved an awful lot of head-banging and wasted time, both for customers and customer support; and I never heard that it hurt our sales or our reputation. Jerry Schwartz

jerrys;
Yes..It would be nice to see a list of bugs that have been, or are in the process of being, addressed.

We had that list, but NEVER shared it with the customer. Open-source companies do it all the time, but commercial companies are less willing to do so for fear of customer over-reaction, etc. We DID share it on a case-by-case basis so a user reporting an issue knew the bug they found had been assigned a case#.

Cyberlink's version of that seems to be the little pop-up that shows on the patches in the list.

James1;
If we saw a DXDIAG for each person and they ACCEPTED the fact that their machine may be the issue...supporting the users, and solving their problem, would be SO MUCH SIMPLER!!

Hi,
I've been having an email exchange on the bug issue with CL and not knowing what is or isn't a previously reported bug. I don't have access to the list. Thank you for the contributions to the thread. I'll refer the contents for CL to read as it sort of makes my point

Dafydd

For everyone's benefit:

The little "blue" window that used to list the various bugs fixed has disappeared ! Someone at CL is reading this forum ! Win 10, i7

Huh? The popup I use occurs when you pass your mouse over the "I" on the patch page on the Cyberlink website (see attached image)...still there