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
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???!!!????!!!!
Can you offer a download of a short original clip of that footage that cannot be imported?
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?
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.
have you checked if that could be related to the so4compound plugin dll?
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.
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.