Remy Thirot
Forum Replies Created
-
I’ll be able to work it then, as long as I don’t drag it into the trimmer… but seriously I don t understand either why it did that but I’m pretty sure it was Vegas because I tried the same thing with a meaningless .MOV file and it ruined it as well, with the trimmer
-
Can’t be more simple than what i explained but imma take a screenshot:
https://s3.noelshack.com/upload/10882940317128_vegas1.png
( Put a random video in there, what they call “Trimmer”, then select None instead of the path… when i do that with that random avi it’s ok, but when I did with a .MOV video it just made it unreadable )
.. but yea i should ve made copies, i just had no idea vegas was going to do a mess with my original file. -
Well it s weird because it definitely did.
I can drag it but it now says that Vegas can’t read the file. It could before damaging it tho. -
the .MOV file became totally unreadable now, by Vegas or by quicktime or by everything. I can’t drag it to Vegas anymore
-
Hi, thanks for you answers.
I was able to read my .MOV files perfectly with Quicktime or even WMP before trying to drag then to Vegas. And yes I was able to move them to the timeline before it happened…
By the way I kept on working a little and I don t have the same problem with .AVI files, something really bugs me about that .MOV files thing, I tried with a meaningless .MOV file again to see if the same thing was going to happen and it did : moving it to the main window, not the preview one, something they call trimmer window or sth like that, and then selecting “None” instead of the file path above that window instantly creates a .SFK and a .SFL file wearing the .MOV file name, plus a .JPG file, and the .MOV still exists and becomes unreadable.
I’m using Vegas pro 10.0 by the way …Hoping that I was more clear this time 🙂
Remy