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 >
Bug fixes fixed from previous versions / Important!
BetoValle [Avatar]
Newbie Joined: Nov 15, 2013 11:27 Messages: 35 Offline
[Post New]
Cyberlink should have as an attitude with its client to disclose in the release of new version, which are the bugs fixed. Most important because for many users, a new version does not necessarily imply bug fixes from previous versions. If we do not join to charge for Cyberlink, we will not succeed as "good" customers that we are!

What do you consider?
Warry [Avatar]
Senior Contributor Location: The Netherlands Joined: Oct 13, 2014 11:42 Messages: 853 Offline
[Post New]
When I look at the list of fixed and improvements for e.g. PD17 2509 Beta, I think that Cyberlink is just doing that. Am I missing something or is there more/other you are looking for?
BetoValle [Avatar]
Newbie Joined: Nov 15, 2013 11:27 Messages: 35 Offline
[Post New]
Not always!
I have versions, 12,13 and 15.
For example, bugs from version 12 that were still fixed only in version or 14 or 15.
( still has version 15 bug that has not been fixed / according to this latest beta update)
If improvement occurs in version, it does not mean that the bugs have been fixed and in my case, after version 15 I am more interested in bug fixes than eventual evolution. Many improvements have been achieved, but
speed of operation in video development
in the timeline with the resources, will have to be better.
I'll cite an example: how long a user, from
create an image (in any editor) to import
for the delay pdr? Why do not they use the "w'indows clipboard" to import it? If you add up
in the year this time becomes important!
Previously Cyberlink when releasing a version it show a comparative with "previous versions", and today they do not do
plus this (logically the previous version user remains without knowing if there was correction of the bug or not)
Warry [Avatar]
Senior Contributor Location: The Netherlands Joined: Oct 13, 2014 11:42 Messages: 853 Offline
[Post New]
OK. I understand. You would be looking for Cyberlink to maintain a list of all reported bugs per version (they likely do that already) and report on those on regular basis e.g. each time a new version and/or a new release is made like: here are the bugs resolved and this is what we still have open. And maybe for older versions like: this is what we will not resolve? And bugs in older verions are still in the newer versions, unless reported as resolved?

It would however take some bravery from Cyberlink to list all their software bugs. Especially when releasing a brand new version with: here are the bugs from the previous version we have not resolved yet.... Although we see some software vendors listing the known issues when they release an update, not many will publish the full list.

I would make sense to me that they, within some reasonable time, report back to the customer who reported a bug or a technical issue, what the status of the issue is. Maybe they do, I have no experience with that. It would indeed be truly customer friendly!
Powered by JForum 2.1.8 © JForum Team