Is there an issue or bug with “exportSequenceFrame()”? I run the following and it even tells me that the export is true/successful. However, no matter the location I choose, or the changes I make to the arguments, I cannot get it to work.
async function exportSequence() {
try {
const project = await ppro.Project.getActiveProject();
const sequence = await project.getActiveSequence();
console.log(sequence);
const frameSize = await sequence.getFrameSize();
console.log(frameSize);
const time = await ppro.TickTime.createWithSeconds(2);
console.log(time);
const test = await ppro.Exporter.exportSequenceFrame(sequence, time, "C:/temp/export.png", "C:/temp/", frameSize.width, frameSize.height);
console.log(test === true);
console.log(test);
console.log("EXPORT should be complete");
} catch(e) {
console.log(e);
}
}
Thanks for the reply! I had tried this before, assuming it was a typo in the documentation. But unfortunately it doesn’t work and the return from “exportSequenceFrame” gives me false. Does this indicate it is bugged?
const test = await ppro.Exporter.exportSequenceFrame(sequence, time, "export.png", "C:\temp", frameSize.width, frameSize.height); instead?
I think we are having some issue for handling windows path with / as path separator. We will investigate further when possible. Please let me know if it is still not working.
Ok, so “C:\temp” didn’t work, however “C:\temp” did work thanks! One slightly annoying thing is that it is doubling the “.png” in the exported file name, and will do the same for .jpg etc.