bugs previously reported

Roberto-Goncalves wrote on 2/19/2025, 8:33 AM

Hi,

I know it's tiring! But today I once again told technical support that I "am aware of the bugs pointed out in relation to the project folder" (transfer of the clip from the folder list to the timeline with a 1-second limit, editing of list data related to the description, recorded on, media start, media ent...etc...) that do not comply with possible modifications, creating insecurity for the user. Now let's see why I feel unfair with what they do to the customer who paid and did not receive the due correction of the functionality. Until when will this disregard continue?

Thanks!

Comments

Roberto-Goncalves wrote on 2/26/2025, 6:38 AM

Hi,

The response from Magix technical support was exactly the same: they are aware of this previously reported issue (I reported it in November/2023 but I am absolutely sure that if you look for information here on the forum and also on YouTube, the issue involving a bug in the project folder must be more than two years old) that is, the product owner is aware and there is nothing concrete to fix it. Solving bugs is not a priority.

I asked an artificial intelligence:

I bought a product from the German company Magix, the VPX video editor. For two years now, they have not been able to fix a bug in the product. Are they not obliged to solve this issue?

Answer:

Yes, Magix has an obligation to provide a functional product, especially if the bug persists for so long. When you buy software, such as Magix Video Pro X (VPX), you are purchasing a product that must work according to the specifications promised by the company. If the product has faults or bugs, the company has an obligation to fix these problems.

However, the situation may vary depending on the company's policies and the terms of the purchase contract, which are usually described in the product's terms of use or warranty. Typically, software companies offer technical support and updates to fix bugs, but there are a few things to consider:

Product Warranty: If you purchased the product within the warranty period and the problem has not been resolved, the company is responsible for correcting the error or offering a solution, such as a refund or an exchange for a version without the bug.

Technical Support: If you have already contacted Magix support and the problem persists for two years, you have the right to demand an adequate solution. If you have not received effective assistance, you may consider taking other measures, such as escalating the problem to a higher level of support or even appealing to consumer protection agencies (such as Procon, if you are in Brazil).

Software Updates: Companies such as Magix often release updates and bug fixes. If the company has not released an update to resolve this problem within two years, this may be a failure to fulfill its obligation to provide a functional product.

If this bug is seriously impacting your experience with the software and the company is not offering an effective solution, you may even consider asking for a refund or requesting a fixed version of the product, depending on the consumer laws in your country.

If this does not solve the problem, seeking help from a lawyer or a consumer protection agency may be a good option to ensure that your rights are respected.

Thanks!

Reyfox wrote on 2/26/2025, 6:55 AM

I personally have not had any piece of complex software being 100% bug free.

Have you read the EULA that you agreed to when you installed the software that outlines Magix legal position? Are you willing to hire a lawyer or start a class action case, if it can be done?

I have several different editing software on my computer. Each brings its own issues. I've learned to work around them, but nothing has been a "deal breaker" for me so far. That is, I won't be spending my money any more with them and move on, not recommending that offending software.

Roberto-Goncalves wrote on 2/26/2025, 8:17 PM

Hi,

I agree with you! I put the artificial intelligence answer because it is a reference in the mandatory "legal" question, but it is far from my intention. I would like to understand the problem of Magix (VPX) and what is the real reason, because the bugs I referred to, believe me, are data storage in folder project and same clip in time line. And do not involve processing. For example, you enter the clip property and save information about the scene or take of the video. Moments later the content is not changed or if any change is made in these same fields the content is replicated to other clips! Wow, how confusing! See, this deals with a simple and not a complex issue.

Roberto-Goncalves wrote on 2/26/2025, 8:23 PM

Hi,

tonight I received this update 22.0.1.260 but I don't know what it is. Could you tell me where I can find the history of this update?

Roberto-Goncalves wrote on 2/26/2025, 8:38 PM

Hi,

now i saw in VPX header - feedback. It has 4 bug fixes, 1 crash fix and 4 enhancements but no fix for the bug related to project folder and clip property.

johnebaker wrote on 2/27/2025, 2:19 AM

@Roberto-Goncalves

To see what is in the patch before installing click the patch number in blue see in your image above.

John EB

Reyfox wrote on 2/27/2025, 4:58 AM

@Roberto-Goncalves, it is good to bring up the issues that plague the software. Hoping that it will get fixed one day. That sad part for me is that I just continue to edit and work around them instead of saying something.

I've gotten used to, and expecting things to appear that shouldn't, and just "tune" it out and go around. Not a good thing for sure.

Roberto-Goncalves wrote on 2/28/2025, 8:08 AM

Hi,

I am recording here the image of the bugs related to the storage of information in the properties of generated clips, whether by selecting the clip in the project folder list, or in the timeline, the contents in situations even after saving the project, may diverge in some cases, which leads to UNCERTAINTY to the user. Here I am once again calling attention to the fact that this type of bug is extremely simple to fix! But the owner of VPX is aware of it and ignored it. What is the reason?

Can anyone with VPX15, 14 or 13 confirm this?

(It is important to emphasize that it is not in a single data insertion,
that is, you must insist on changing the content via the clip property in the timeline and project folder)

Thanks!

Roberto-Goncalves wrote on 2/28/2025, 8:11 AM