dv avi from unchanged sources ?
To Sony: When will restored timestamp preserving on rendering
Back to post
Comments
RexA
wrote on 7/14/2004, 2:26 PM
>>
The thread and my finding came about in a thread about DV_DateCode. So right now I am running the promo through it - this is a Vegas rendered file, rendered form several other files. Here is some of the readings - and the format is DD.MM.YYYY HH:MM:SS Frame
[snip various dates and times apparently from the original clips]
And so on - so you can see that Vegas *does* retain the date, time/timecode of the source tapes during a render.
<<
Filmy,
I just read this thread today. The results sounded interesting so I thought I would try an experiment. I did this with Vegas 4.0d which is all I have installed on this machine right now. (I do have 5 on a different PC.)
I downloaded dv_datecode freeware program from the internet. I picked 4 clips from my drive and checked the Date codes; all were from 17.01.2004 with different times through the day. I opened a new edit session and put the 4 clips on the timeline with no transitions. I checked that the project settings were the same as the clip properties.
I rendered this as a windows avi. Checked the Time Code in the resulting clip and it was today's date with the time of creation. Tried it again by rendering to a new track, also today's date in the resulting file.
So I don't see the Time Codes being preserved through a render, which I think is what you saw. If you can give me particulars of how you rendered to get your results, I'll try again.
The thread and my finding came about in a thread about DV_DateCode. So right now I am running the promo through it - this is a Vegas rendered file, rendered form several other files. Here is some of the readings - and the format is DD.MM.YYYY HH:MM:SS Frame
[snip various dates and times apparently from the original clips]
And so on - so you can see that Vegas *does* retain the date, time/timecode of the source tapes during a render.
<<
Filmy,
I just read this thread today. The results sounded interesting so I thought I would try an experiment. I did this with Vegas 4.0d which is all I have installed on this machine right now. (I do have 5 on a different PC.)
I downloaded dv_datecode freeware program from the internet. I picked 4 clips from my drive and checked the Date codes; all were from 17.01.2004 with different times through the day. I opened a new edit session and put the 4 clips on the timeline with no transitions. I checked that the project settings were the same as the clip properties.
I rendered this as a windows avi. Checked the Time Code in the resulting clip and it was today's date with the time of creation. Tried it again by rendering to a new track, also today's date in the resulting file.
So I don't see the Time Codes being preserved through a render, which I think is what you saw. If you can give me particulars of how you rendered to get your results, I'll try again.
farss
wrote on 7/14/2004, 2:38 PM
Rex,
the timecode cannot be preserved through a render becuase you've created a new entity and the TC in the rendered file has to match the TC on the timeline.
What the original post was about is preserving / manipulating the date/time stamp. That's when the recording was made.
Bob.
PS don't understand why that's an issue but you never know.
the timecode cannot be preserved through a render becuase you've created a new entity and the TC in the rendered file has to match the TC on the timeline.
What the original post was about is preserving / manipulating the date/time stamp. That's when the recording was made.
Bob.
PS don't understand why that's an issue but you never know.
RexA
wrote on 7/14/2004, 6:33 PM
Sorry, I said Time Code in my message but meant the date/time stamp (datecode?), same as filmy was describing in his post. I tried to duplicate what he was describing in the post that I replied to. From filmy's description he had the original timestamps from clips preserved in the file he rendered (or that was my understanding.)
I was saying that when I tried it, a new datecode was created for the newly rendered file with today's date and times relative to when I generated it. If it worked for filmy, I was curious what he might have done differently from me.
I was saying that when I tried it, a new datecode was created for the newly rendered file with today's date and times relative to when I generated it. If it worked for filmy, I was curious what he might have done differently from me.
farss
wrote on 7/14/2004, 7:55 PM
I'd just love to know why DaLiv thinks it's important?
As I tried to explain to him it didn't even exist from what I know on analogue broadcast cameras.
As I tried to explain to him it didn't even exist from what I know on analogue broadcast cameras.
taliesin
wrote on 7/15/2004, 10:23 AM
Timestamp/Datacode is needed for automatic scene detection! Once stuff was inside Vegas it will be impossible afterwards to use automatic scene detection. This is my complain about the lack of having an option to preserve the datacode.
Marco
Marco
DaLiV
wrote on 7/19/2004, 1:30 AM
don't need burned in - better when you have full picture and when wanted show or hide timestamp on viewing ....
farss
wrote on 7/19/2004, 3:07 AM
Ah yes,
now I can see an issue I think. If you wanted to use scene detection on a rendered file, am I right?
Perhaps one way around that would be to place markers at each scene change and then load them in from the rendered file?
I'm just guessing here, still no clues from you guys as to why you need it!
now I can see an issue I think. If you wanted to use scene detection on a rendered file, am I right?
Perhaps one way around that would be to place markers at each scene change and then load them in from the rendered file?
I'm just guessing here, still no clues from you guys as to why you need it!
taliesin
wrote on 7/19/2004, 8:47 AM
>> If you wanted to use scene detection on a rendered file, am I right?
Rendered or just printed back to tape and recaptured. In Vegas even printing to tape without any rendering makes the dv files loose their datacode.
Your idea with saved markers isn't bad indeed. But then - even when using some scripts to automate placing markers and splitting the file - I wouldn't get separated files in the bins. O.k. I could use subclips then, but then it gets rather time consuming again.
Best way to manage such kinds of huge projects in my opinion is to use the scene detection tool AVCutty which isn't based on datacode. So I would do first organzing there and switch to Vegas afterwards. Mmh, media organisation still could have some improvement in Vegas I think.
Marco
Rendered or just printed back to tape and recaptured. In Vegas even printing to tape without any rendering makes the dv files loose their datacode.
Your idea with saved markers isn't bad indeed. But then - even when using some scripts to automate placing markers and splitting the file - I wouldn't get separated files in the bins. O.k. I could use subclips then, but then it gets rather time consuming again.
Best way to manage such kinds of huge projects in my opinion is to use the scene detection tool AVCutty which isn't based on datacode. So I would do first organzing there and switch to Vegas afterwards. Mmh, media organisation still could have some improvement in Vegas I think.
Marco