(I do realize that Vegas uses MC codecs...)
I had one clip of about 50 that was set to encode via my MainConcept standalone MPG2 encoder (the latest). Set to encode at 570000 CBR.
Clips before it and clips after encoded just fine, however, the clip in question would get errors at the same point every time. Something about not being able to ensure integrity at frame # thus and such, then proceeded to give this error for each following frame. It was about a 40 minute clip and would choke with about 8 minutes of media time remaining.
In case the file was corrupted, I rerendered it to a new AVI via Vegas. Same thing. I even did the evolution on different source and destination drives in case it was an NTFS issue, which I have seen with other file types on occasion. Same thing.
I even rendered the seemingly troubled region to a separate AVI file and it would encode to MPG2 just fine. There was nothing special about this clip. Just a regular clip.
I finally encoded it at the same MPG2 570000 CBR setting from the Vegas timeline and it encoded just fine.
Has anyone ever seen anything like this before? I have not.
(Note: I have positively seen "issues" with the new and latest MainConcept DV codec positively *NOT* handling some crossfade transitions with stills well. Vegas's DV template worked perfectly.)
Thanks.
I had one clip of about 50 that was set to encode via my MainConcept standalone MPG2 encoder (the latest). Set to encode at 570000 CBR.
Clips before it and clips after encoded just fine, however, the clip in question would get errors at the same point every time. Something about not being able to ensure integrity at frame # thus and such, then proceeded to give this error for each following frame. It was about a 40 minute clip and would choke with about 8 minutes of media time remaining.
In case the file was corrupted, I rerendered it to a new AVI via Vegas. Same thing. I even did the evolution on different source and destination drives in case it was an NTFS issue, which I have seen with other file types on occasion. Same thing.
I even rendered the seemingly troubled region to a separate AVI file and it would encode to MPG2 just fine. There was nothing special about this clip. Just a regular clip.
I finally encoded it at the same MPG2 570000 CBR setting from the Vegas timeline and it encoded just fine.
Has anyone ever seen anything like this before? I have not.
(Note: I have positively seen "issues" with the new and latest MainConcept DV codec positively *NOT* handling some crossfade transitions with stills well. Vegas's DV template worked perfectly.)
Thanks.