Fly through 79 Photos

caverx2014 wrote:

From what I have been reading the image sequence should be naming them image:[####].jpg:13:17 at least in the browser view

the 13 is the image number and the 17 is the position in the sequence

My understanding is that the sequence representation in Motion for image:[####].jpg:13:17 would be that the first image in the sequence has the label 0013 and that it is followed by 0014, 0015, 0016 and 0017. Which is why I don't understand the breaks in the sequence after applying the folder to the Make Image Sequence droplet because it ignores the previous numbering scheme and applies a new sequential numbering based on the sorting attributes that are picked from the dialog. Importing an image sequence with the trailing numbers like13:17 makes no difference -- that's just 5 ordered images that will be placed in the project as if it were a 5 frame "movie".

I really don't know what more I can do to be of help to you. Try a different image sequence than the one your trying to deal with now (perhaps there are corrupted files in the group?) Open each image in Preview and export them as .png and create a new image sequence (making sure all of the images are the same format [you cannot mix jpg, png, tiff, etc...). If you have Quicktime 7, you can open an image sequence and export it as a mov file (with your choice of frame rate.) Of all the problems people have with Motion, this is the first time I've heard of this one.

Very good!

caverx2014 wrote:

Looking at the images in the browser they are not all getting renamed with the same [####].jpg:22:23 stamps some

are just name.0043.jpg ...I can assume these are the ones getting dropped in the Motion which is breaking the sequence import..

You don't see these file names in Finder...

I am going to convert some others and test....

hmmm same results?

My guess is that Motion is creating different image sequences due to the use of jpg vs JPG file extensions.

Set the dolly distance to be slightly more than the distance between the first and last images. I recommend setting the Start point to negative Z space (somewhere like -20000 or more); the End point at 0 (or increase it to get it closer to the camera to start) and then set the dolly to 20000 give or take. If the transversal is too quick, lengthen the project. If it's not quick enough, you can shorten the Dolly behavior to speed up the camera movement.

For transparency, you have to export as ProRes 4444 (whether you use Luma keyer or not). If the images already had transparency when you imported them into FCPX, they should have it when exported (with 4444).

PS - you can save over the original export version -- it should automatically update in Motion.