QE API trackItem.moveToTrack() and trackItem.move()

[dmytrok98627988]

Hello. What arguments does this functions accept? And if there any way to check arguments for QE functions?

[Bruce Bullis]

While it is currently the only way to do a few different things, QE DOM is unsupported, and not at all recommended.

What's the entire workflow you'd like to support?

[dmytrok98627988]

I dropped clip from panel and need to move other clips down/up if they exist in destination track

[Bruce Bullis · Accepted solution]

When dragging from a panel, you can only provide N file paths to PPro; there's no way to indicate in/out ranges.

This is unlikely to change in the immediate future.

[dmytrok98627988]

I know. I already made drag and drop that emulates sequence d&d. That was not a trivial task but i managed. In any case i alredy solved track's clips inserting / moving but still curious to know moveToTrack() and move() args cuz I'll need this in future

[Bruce Bullis]

All new work on inserting and manipulating clips in tracks, will be done in the non-QE-DOM API.

[dmytrok98627988]

Yeah i've read about this as well. But for now i need some working solutions to make a proof of concept. This code will be updated as soon as new api will be available

[BrianDavison]

Almost a year later I encountered this thread looking for the same answer. Did you ever have any luck figuring it out?

[Bruce Bullis]

> Did you ever have any luck figuring it out?

There's no move() function in the normal API, and no improvements have been made to drag n drop. Perhaps the work we're doing around enabling the creation of sub-sequences from a specified in/out range in an existing sequence, would help pare down some of the work an extension would currently have to do, to produce behavior like 'move'.

[itsenouphoto]

Surely someone Googles this and opens this link with the same hope as I did
    qeClip.moveToTrack( 1 /*trackIdShift, int*/, 0 /*unknown, int?*/, "00:00:01:00" /*timeShift timecode ss:msms, string*/, 1 /*1 = duplicate, int bull*/)
trackIdShift- If you want to move a clip from track 2 to track 5 then here is 5-2 = 3. -3 for vice versa work too
unknown,  - ... (I did a bunch of tests and couldn’t find out what was changing, I’d be glad if someone figured it out)

timeShift - move clip forvard to 1 sec in "00:00:01:00" case

duplicate - if 1 move the clip to a new track while maintaining the source one, else 0

[itsenouphoto]

I googled the parameters of this function and found that I had figured this out last year, but there was one mystery left. Now I have solved it, at least sort of

I don't know what to call it more precisely, but while trying to create copies of not only video but also audio, I found that the second parameter (0 /*unknown, int?*/) disables the ability to move clips on audioTracks

This parameter in the value 1 does not make the function copy the audio linked with the video or selected with it or something like, but the value 0 simply disables the ability for the function to move/duplicate the audio clip subject. 

In this case, I needed to move/duplicate the audio along with video to the top tracks. To do this, I found audio clip (var qeAudio) corresponding to the video clip (in my case, it was enough to find a clip with the same parentTrackIndex and start.seconds, but this option will not suit everyone ofc) and applied
qeAudio.moveToTrack((seq.audioTracks.length - findSelAudio.parentTrackIndex - 1), 1, "00:00:00:00", 1)

[itsenouphoto]

UPD: Sorry, I'm an idiot confused by myself. The second variable is not a boolean int. It's like the first one, but for audio - the number of tracks to move an audio to