Forced to rollback to Build 321 in middle of project

i am erikd wrote on 7/16/2018, 8:16 AM

Suddenly it seemed, none of my DJI Osmo mp4 (AVC) clips were recognized by Vegas at all! I mean no way, no how could you import the files into Vegas. I have never had this problem before. The only conclusion was to see if the problem was related build 361 or not. I rolled back and viola THE CLIPS ALL WORKED FINE AGAIN.

Jeez, hate breaking things in an update. Rather not have one at all.

Erik

 

Comments

i am erikd wrote on 7/17/2018, 12:31 AM

So I see no responses on this. I just want to add that this is EXACTLY the type of problem that leads to someone moving to a different editing software. From my experience, once something gets broken in an "update" version, good luck ever getting your particular problem bug fixed!

So now, I can't update to build 381 either since for sure it will have the same problem. Of course, it will be there in Vegas 16 and so on. This is how it goes.

I remember when Vegas 10 broke the regions embedding in mp4 files saving properly in the file itself. Yep, that was Vegas 10 and it is still spotty at best till this very day.

Why, why, why does stuff have to get broken when there are updates???!!!????!!!!

 

 

Wolfgang S. wrote on 7/17/2018, 1:17 AM

Can you offer a download of a short original clip of that footage that cannot be imported?

Desktop: PC AMD 3960X, 24x3,8 Mhz * GTX 3080 Ti * Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED (ProArt Studiobook 16 OLED (i9 12900H with i-GPU Iris XE, 32 GB Ram. Geforce RTX 3070 TI 8GB) with internal HDR preview on the laptop monitor. Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG, Atomos Sumo

OldSmoke wrote on 7/17/2018, 6:32 AM

Suddenly it seemed, none of my DJI Osmo mp4 (AVC) clips were recognized by Vegas at all! I mean no way, no how could you import the files into Vegas. I have never had this problem before. The only conclusion was to see if the problem was related build 361 or not. I rolled back and viola THE CLIPS ALL WORKED FINE AGAIN.

Jeez, hate breaking things in an update. Rather not have one at all.

Erik

Did you upgrade in the middle of the project or did it happen on the same build?

 

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

i am erikd wrote on 7/18/2018, 9:49 AM

I had done the upgrade after the last time that I used video in a project from the Osmo. I didn't notice I had a problem until I tried to bring in the Osmo footage a week later.

OldSmoke wrote on 7/18/2018, 10:21 AM

have you checked if that could be related to the so4compound plugin dll?

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

i am erikd wrote on 7/20/2018, 1:02 AM

What do you mean OldSmoke? Something different between builds regarding so4compound plugin dll? As I said, build 321 loads the files fine. Build 361 does not.

vkmast wrote on 7/20/2018, 1:09 AM

Maybe he means this https://www.vegascreativesoftware.info/us/forum/blacklist-for-so4-includes-fix-for-gopro-dji-xiaomi-yi-avc-lag--111716/#ca690583

i am erikd wrote on 7/20/2018, 5:11 AM

Thank you vkmast but in my situation, the problem isn't poor performance of playback of certain files but the fact that Vegas simply will no longer identify the files or even allowed them to be added to a project or timeline.