Problem creating a image sequence in Vegas Pro 17 latest build

Comments

bryan-quarrie wrote on 2/4/2020, 12:41 AM

UPDATE:

 

I’ve done the second timelapse with my other camera, and after importing the jpegs from it, worked in Vegas as it should 👍👏👏.

 

My conclusion therefore is to do with the default numbering scheme between the Yi 4k+ and the Sony RX0ii. For some reason the Yi was skipping frames, so I will try the renaming method suggested by john dennis for the Yi’s jpegs and try importing again.

 

Thanks everybody for your help!!! It’s all good now 👏👏

fr0sty wrote on 2/4/2020, 2:49 AM

If you can shoot RAW, I'd recommend it.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

bryan-quarrie wrote on 2/4/2020, 3:34 AM

Can Vegas import RAW directly?

Marco. wrote on 2/4/2020, 4:29 AM

Vegas Pro reads many RAW photo files if you have the Windows or Adobe RAW package installed (just like Adobe DNG), but Vegas does not read the RAW metadata which makes using RAW files in Vegas Pro less useful.

adis-a3097 wrote on 2/4/2020, 4:43 AM

.nef format it can. .raf, .dng, .cr2 etc needs installing their codecs. No development tabs in Vegas where you can set ISO etc, preview only.

Not so the .r3d:

 

 

Oh, Marco beat me to it. :)

EricLNZ wrote on 2/4/2020, 4:48 AM

I’ve done the second timelapse with my other camera, and after importing the jpegs from it, worked in Vegas as it should

@bryan-quarrie So there is no "major bug" after all. Glad you got it sorted. I've taken the liberty of altering the thread title to "problem" instead of "major bug". It might mislead someone in the future searching with a similar problem.

bryan-quarrie wrote on 2/4/2020, 6:36 AM

I’ve done the second timelapse with my other camera, and after importing the jpegs from it, worked in Vegas as it should

@bryan-quarrie So there is no "major bug" after all. Glad you got it sorted. I've taken the liberty of altering the thread title to "problem" instead of "major bug". It might mislead someone in the future searching with a similar problem.

Thanks EricLNZ - Sorry about how it sounded.