VPX 17 - project folder - transferring clip from list to timeline

Can-Dive wrote on 6/10/2025, 6:23 PM

Just to confirm your workflow:

You drag a clip from the Media pool or Source monitor to the Project folder.
You then click on the "send to the timeline" button on the object in the Project folder and the error is generated.
But if you drag the clip from the Project folder to the timeline, it works?

Roberto-Goncalves wrote on 6/10/2025, 9:40 PM

Hi, see

Roberto-Goncalves wrote on 6/10/2025, 10:11 PM

In the routines involving the Project Folder, the bugs in the properties of clips involving different content were also not resolved, as follows:

Roberto-Goncalves wrote on 6/10/2025, 10:56 PM

These fields are clip-specific metadata, meaning they should reflect the individual content of that piece of media. If you cut a video into two parts and add both to the project folder as separate clips, you would expect each to have its own description, scene, and take, since they are now distinct entities in the context of the edit. This might be intentional in some simplified workflows (e.g., when the focus is on cataloging media by file rather than by instance of use), but it is inappropriate for more refined editing workflows, such as those used in film or television, where:

A single video may have multiple scenes;

Each clip may have separate takes;

Descriptions are important for narrative and logistical organization.

Can-Dive wrote on 6/11/2025, 12:50 AM

Hi @Roberto-Goncalves

Thanks for the video's. As for the first video, my workflow is a little different to yours. You cut and trim on the timeline before moving the objects to the Project Folder. I trim the video in the Source Monitor and then move the trimmed clip to the Project Monitor before sending the clip to the timeline. This works in VPX16 and I'm wondering if it still works in VPX17?

o

In my video I created the objects with exactly the same length to demonstrate that this particular workflow does work and the objects are the length they were trimmed in the Source monitor. The "one second bug" in VPX16 is created when you use the timeline to cut/trim the clip before moving it to the Project Folder. You have demonstrated that this is fixed in VPX17 but unfortunately a new bug has been introduced. I'm wondering if my workflow as outlined in my video still works in VPX17?

As for your second video regarding scenes and takes, I guess it's still on the bug "to-do list."

Can-Dive wrote on 6/11/2025, 3:57 AM

@Roberto-Goncalves

With regards to the Scene/Take bug, as a suggested workaround, you can use the Description field. While it is true related objects will obtain the same description as you have demonstrated in your video, subsequent changes to the Description field will not populate the other objects (In VPX16). This can be a timesaver if all you need to do is change a single digit. Does VPX17 act the same way?

Roberto-Goncalves wrote on 6/11/2025, 6:37 AM

@Can-Dive I repeated the operation with your workflow and the error (bug) is repeated, that is, you move the 2 clips with exactly the same sizes from the source monitor, and when you transfer them to the timeline with the arrow, the reported bug occurs! I opened a ticket yesterday, now let's see if technical support will be willing to fix these bugs!

Can-Dive wrote on 6/11/2025, 9:00 PM

@Roberto-Goncalves

Thanks for confirming the "Arrow button bug" using my workflow. I'm sure they will fix this error in an update. As for the Scene/take bug, you indicated that you had reported it before, did you receive any feedback from Support acknowledging it as a bug?

I tested this issue on VPX11 and it even existed back then! I wonder when they scoped these two input fields, they took into consideration that scenes and takes would be extracted from the same video clip? Or did they just scope the work for separate clips (camera shots)? I wonder if there was any version of VPX where it worked as expected.

I agree with you, that one should be able to update these fields for the separate scenes/takes. With my underwater footage, I tend to take long shots. In fact, on many occasions I keep my camera turned on throughout the entire dive so I don't miss anything. There are times when a shark will appear and then suddenly disappear and by the time I press record, I missed the shot. So, a major part of my workflow is cutting up all these scenes/takes in the Source monitor and labelling them in the Project folder before arranging them on the timeline.

browj2 wrote on 6/11/2025, 10:09 PM

@Can-Dive

Hi,

As for the Scene/take bug, you indicated that you had reported it before, did you receive any feedback from Support acknowledging it as a bug?

I also raised this in a follow up message to a ticket started on January 11, 2022, along with the problem of dragging a trimmed clip from the Source Monitor to the PTF resetting the range to 0 instead of the selected range. I also mentioned that the Rating field could not be entered and did not correspond to the rating of the file metadata and asked what it was for. There was also a problem with the red light the shows which clips were on the timeline, showing on clips that were not actually on the timeline.

The reply was "Thank you for the video and the further information. This is very helpful to document the problem.
I will take a closer look at it later today and then document it for our developers."

This was followed up by Magix with the customer survey. That's it.

Earlier this year, in a ticket mainly about Neat Video, I raised the problem of the PTF and they replied, "The Problem with the projekt temp folder is know. Unfortunately this is not in the development focus. You can avoid the problem, when you put objects in the folder with drag and drop instead with the dropdown menu."

Obviously, not a solution. I didn't reply.

John CB

Can-Dive wrote on 6/12/2025, 8:41 AM

@browj2

Thanks for your feedback. It looks like the "PTF one second bug" has been fixed. They just need to fix the "Send to Timeline" arrow button and it should be good to go.😀

I noticed the Ratings field, but like you, I'm not sure how it gets populated. I thought it may have something to do with Photo Manger Deluxe where you have the ability to rate your photos and videos from 1-5 and these would populate that field in VPX. You have Photo Manager. Can you confirm if Photo Manager's ratings do get transferred to the Ratings field?

Thanks for mentioning the issue with the red dot. I havn't noticed this issue but will check it out.

As for the scenes/takes bug, do you know if it ever worked? I checked VPX11 which is 6 generations behind this one and it didn't work then. So how far back do you need to go?

The thing is; people upgrade to VPX because they want to use the PTF and the features it offers. We are not talking about "AI" or rocket science, essentially this is basic database management stuff. And when these simple features don't work, you are left wondering; why did I upgrade?

And I'll ask again, In VPX, what features or enhancements were added specifically and exclusively to VPX17. As far as I can see, they just cut and pasted the same code from VDL2026 to VPX17 and then charge you over three time more to upgrade from VPX16.

Roberto-Goncalves wrote on 6/12/2025, 10:41 AM

Hi @Can-Dive @browj2

There is actually no data entry for this rating field! (VPX16 or 17). Since Magix did not comment at the time, I asked the GPT chat:

"Clip rating field in the video editor"

Explained in parts:
Rating field = rating field, that is, a place where you can assign a rating, evaluation or number of stars.

of clip = of the clip (usually a video or audio clip within the editor).

in video editor = within a video editor (such as Adobe Premiere, Final Cut, DaVinci Resolve, etc.).

What does this mean in practice?
It is an area or field within the video editor where you can rate or rate a clip. This rating can be used to:

Better organize the clips (for example, mark the best ones with 5 stars).

Filter or search for clips based on the rating given.

Help in editing by highlighting the most relevant clips.

---------------------------

As in the ticket I opened I mentioned this topic on the mailing list, I hope you will review the content of the clip columns and also inform in the manual what it means and above all with some examples because I saw that the manual has a new look in this version 17, although it is necessary to substantially improve the content of the topics, incorporating better images in examples (why not use gifts added in the manual page or link to existing page on the magix website that contains the videos?)