That is a very good suggestion, but unfortunately it would be a monumental task. Systems vary greatly. I find very few bugs in the latest releases while some users report that PD9 is completely unusable. I believe there is a sticky at the top of the forum in which Dafydd has posted several links to issues. That may help some. __________________________________
CORNBLOSSOM

..."unfortunately it would be a monumental task"

I'll take your word for it, not knowing how many actual bugs are in level 2930. What I had in mind was something like this. Let's say there are a dozen known bugs that have been vetted by CL as needing to be fixed. By "bug" I mean it can be reproduced on any system (not internittent and not system dependent). An example would be the one where if you insert a text block in the text track, text to the right stays put. But if you delete a block from the text track, text to the right shifts left (should stay put). The list would not necessarilly include problems/issues reported on this forum, which as you say can be "monumental". People could then search the list of known problems being worked on by CL, use any circumventions in the list and/or wait for the next update release. If they don't find their problem on the list, they could make a post here and/or submit a trouble ticket.

Just a thought...

By "bug" I mean it can be reproduced on any system (not internittent and not system dependent).

That would be a much smaller list, but probably would cover very little of what we see every day here in the forums. So much of how PD performs is system dependent. __________________________________
CORNBLOSSOM

What seems to be a bug for you may not even be a issue for me and work as expected....... That's the life of PD9.....

There are a lot of computers old and NEW that cannot perform well with PD9. When something crashes for you and runs as expected for someone else is not a "bug" within PD9 for the most part. Now if the same things crashes for everyone, that could be a bug of sorts.

There are so many people having issues with PD9 that a running report would be impossible. I am like Jaime, I have no real problems with my projects. There even seems to be different issues between running 32 bit and 64 bit, that the 32 bit users like myself have less problems. I tried 64 bit when 7 first came out. I still do not think 64 bit is ready for prime time yet. But that is just my opinion. And now that you do not have an option for 32 bit on a new machine it is too bad, as I think some of the machines in here with problems running PD9 in 64 bit mode may not have any problems if they had 32 bit Windows.

And as far as those SSD drives are concerned. Unless you can get a 300 gig one.... DON'T! And Don't even try PD9 with a 80-100 gig SSD drive (or any other drive with less that 100 gig free space.) __________________________________________
Windows 8 Pro 64 bit

CyberLink PowerDirector 10 Tutorials
PDtoots PowerDirector Tutorials

**NOTICE**
When you are asked to provide a DXDIAG you go the following link and do part "B". Your posted specs are NOT what we are looking for as they tell us nothing. The specs on the box of your computer mean nothing. The DXDIAG shows us how your computer is configured as it runs.

DXDIAG Link

10-4. I'll consider this a dead issue and not flog it any more.

The hidden agenda behind such a list would be the "wishfull thinking" hope that it might influence CL to not release a product 6 months prematurely again. Five major updates to a product within months of releasing does not speak well for CL's quality control. But then I joust at windmills too.

Regarding the philosopy of having to have the right hardware to run an "open use" software product -- sorry, but I can't buy into that. A product like PowerDirector should be able do every function on any computer that meets the published hardware requirement. So often over the many years of dealing with technical support on products, the message communicated to the user is "get the right hardware and our product runs fine". This is a cop out. I've even had vendors tell me I need to have a dual boot system with their product on a specially configured OS, untill I reverse engineered the machine code, developed my own patch, and showed them it now runs on any machine. No, what vendors need to do is develop their code so that it works on the "lowest common denominator". The big negative that, of course, being to not exploit the special features of some systems to optimize performance. I give CL credit for trying to push the edges of the envelope of PC hardware, including "rendering" video cards. Their attempt to milk the optimum performance out of our machines is admirable. In CL's case, I don't think their programming staff was prepared for the nuances of coding for multi-threading CPU's, and the timing issues they present. They should have held off releasing products during their learning curve (resulting in happier customers). I suspect most of the "hardware dependent" bugs have more to do with this than 32 bit vs 64 bit. Just a guess mind you.

Hasta la vista...

To shed a bit of light on this from being a user on another forum for a competing video editing application the issues there are identical to PD9's. There's simply too many configurations possible to list all issues. The crashes, hangs, video artifacts, transition issues all exist but on different configurations - HD editing is NOT a cut and dry application on a PC. Unless you're running the latest hardware and software there are bound to be problems. And even then the "latest" does not always produces the best. Win 10, i7

Yes indeed. Of the 3 other "consumer" video editors I own, all have usage issues. Albeit not to the degree of PD9 (production limiting), and they are more or less "documented" (acknowledged). Knowing this is not the place to have a philosophical discussion about marketing a software product, will exit with the following rhetorical questions...

Should a person who buys a software product expect all the advertised features to work on their computer (assuming meets manufacturer's minimums)? If not, how will user know what won't work? Must each user go through this discovery process?

Out...

This thread holds an interesting conversation.
I hope it will not be doomed as not editing-related or besides whatever point.

I would have liked to quote a line from a Norwegian song. Translated, it misses "the snap" it
has in my language. "It's not easy these days to be a bird".
I wonder if it's possible to compare computers+software to other stuff we might purchase,
lets say bicyckles, skies....cars? What we look for would most likely be in light of
answers to the questions: How will I use it? What are my skills? How often will I need/use it?
What am I prepared to pay?
If you were to buy skies here today, you will have to study long and hard to be able to
choose between all the models- or, rely on the seller to find you the "right" pair to suit
your use/need. But that's only the start. When the skies are home, you will have to spend
time finding your way of using all kinds of different skiwax - only to experience a
reasonable sucsessful day out on your skies.
We have been taught and learned to accept (?) that there is a coherence between price
and quality. Every now and then we see proof of that's not always the case, but still we
assume it's so. Not to mention that products of today are not meant to last very long. Wheels
must turn, and they turn as fast as money can shift hands.

Nevertheless; you expect more from a software costing 800$ as opposed to 100$. But then,
when the software actually costs 100$ you sort of expect it to really be "consumer" , just as
advertised and marketed as. What I really don't know is; what is "a consumer" computer
these days? What do people, the "avarage consumer" buy?
Surely, I'm thinking, there must be some sort of coherence between "consumer computer" and "consumer software".

Just something.
https://www.petitpoisvideo.com