Forum Replies Created

Page 6 of 10
  • Thank you. After your reply, I found a webpage that had some info which bears repeating, lest anyone else reads this thread. A modified extract is below. (Source: http://www.infocellar.com/Video/dv.htm)

    ——————
    Uncompressed full-screen Video – 31 MBps
    Uncompressed Audio and Control data – 0.5 MBps

    Calculations:
    NTSC DV Video is 720×480 using 3 bytes for color info (3 bytes per pixel)
    720x480x3 = 1,036,800 bytes/frame
    29.97 frames/sec x 1,036,800 bytes/frame = 31,072,896 bytes/sec (31 MBps)

    Compressed DV (using DV25 codec)
    – Camera Compression of video – 10:1, stored on tape at 3.1 MBps
    – Camera compression of audio and control info – None – stored on tape at 0.5 MBps
    – Camera Compression overall 8.6:1.

    Total Data Rate = 3.1 + 0.5 = 3.6 MBps

    During filming compression occurs in the camera (not the capture)!! The data stored on the miniDV tape is compressed.

    During capture, no compression occurs – the data is just piped into the computer, as is, and stored on the hard drive at 3.6 MBps.

  • John,
    We use Vegas Pro 8.0c. I have not lost any functionality. We had the same experience with 8.0b.

    Harold,
    It’s interesting to know I’m not the only one. No, I’m not talking about the Fade-out/in or Event Edge [mover-things].

  • I will add a screen-shot of my friend’s screen Wednesday night. Here is a screen-shot of my screen:

    ——————————

    – 4 GB RAM
    – Intel duo core processor, 2.16 gHz EACH, 4.3 gHz total
    – Vista 64-bit (32-bit able), with SP1
    – Video Card: NVIDIA GeForce 8400M GS
    – Sound Card: RealTek High Definition Audio, 6.0.1.5384
    – Camera: Sony DSR-PD170. Also: Kodak m1033 digital.
    ——–
    Jilligan

  • Thank you. I think there must have been a lot of [bleed] between mic’s/mikes – with both mic’s picking up what both interviewees were saying. I had seen that the audio track had two parts to it, but they were so similar I thought they could not be separate channels. Upon closer inspection I find that yes the loud talker is louder on the left channel than the right.
    If DV only carries 2 channels, is there a way to dedicate separate channels for 3 talkers/sources? I guess that would require another recording device (either another camera or an audio-only recorder. I think I just answered my question.
    How do you spell mic’s?
    ————————–

    – 4 GB RAM
    – Intel duo core processor, 2.16 gHz EACH, 4.3 gHz total
    – Vista 64-bit (32-bit able), with SP1
    – Video Card: NVIDIA GeForce 8400M GS
    – Sound Card: RealTek High Definition Audio, 6.0.1.5384
    – Camera: Sony DSR-PD170. Also: Kodak m1033 digital.
    ——–
    Jilligan

  • Thank you Steve and Thank you John,

    If Levelator works well in my case, I’ll use that.

    I may use it in combination with volume envelopes for fine tuning.

  • Glory Glory Hallelujah!
    Thank you Gilles.
    I am switching my working method – so I may not be using subclips – but your script makes them much more valuable – at least in my case. I spent hours trying to copy subclips between projects, with their names intact.
    Gilles, you can call me “Jilles“.

  • Thank you Ron – and now Douglass too.

    Yes, I’d rather start riding a new horse out of the gate than keep whipping a dead horse just because I’m 1/4 way around the track.

    I will consider this further, but I don’t think starting fresh is necessary, because I think it’s fair to say everything is logged, albeit by an unusual route:
    1. Each tape has clips in well-named regions.
    (Each tape has its own project file. Originally all tapes were in one project file, but when we found we could only fit a few tapes’ worth of subclips into our all-encompassing project file, we gave each tape its own project.)
    2. Since I will now be operating in DV, surely I can batch render these regions and then splice and trim them at will, without needing to keep track of where the clips come from (the timecodes in the source tapes.)

    If I’m wrong about part 2 of that, then I think I have an easy way to batch capture:
    1. Run the “Regions to Subtitles” script
    2. From ‘Edit Details’ => Commands, copy the spreadsheet of titles and timecodes to a spreadsheet program, and from there to a batch capture program. [I need to investigate that further. If it’s difficult in Vegas I might be able to do it using my friend’s Premiere.]

    Thanks again Ron and Douglas – I will think about this more.

    (P.S. I recalled another reason I accepted my project partner’s suggestion to just capture all the footage: I thought I needed to work with intermediate files and I learned that it was well-nigh impossible to capture in low res, then edit, then generate a log from the edit, then batch capture in full res the required clips – AND: In learning that, I came across someone’s opinion that batch capturing was old school, and that with modern computers capable of storing and processing more data, I’d be better off to just capture it all.
    Yup, I’ve taken every wrong turn.)

    – 4 GB RAM
    – Intel duo core processor, 2.16 gHz EACH, 4.3 gHz total
    – Vista 64-bit (32-bit able), with SP1
    – Video Card: NVIDIA GeForce 8400M GS
    – Sound Card: RealTek High Definition Audio, 6.0.1.5384
    – Camera: Sony DSR-PD170. Also: Kodak m1033 digital.
    ——–
    Jilligan

  • It also crashed when I tried copying a bin of subclips from one project to a ‘full’ project.
    (Repeat: I only call it full because it won’t let me add more media files or subclips.)

  • Thanks David,

    If it gives you problems with having too many clips, and there’s no cost efficient way to improve the computer, […]

    As I’ve written in other recent threads ([url=https://forums.creativecow.net/readpost/24/888851]Vegas’ poor use of memory? Unused RAM. Project ‘full’? Vegas crashing.[/url]), it seems that improving the computer would not solve the problems.
    Happily, I think rejecting the intermediate-file method will solve everything, since when we’re not using subclips we won’t need all 60 hours of video in the project (plus the 20 hours of subclips).

    —————–

    could you try just making a second Vegas program and putting the remained of the clips in there, and then just alt+tab between them?

    I considered that previously, but wrote in the thread
    [url=https://forums.creativecow.net/readpost/24/888680]Re: Project ‘full’? Maximum # of hours in a project file? Can’t add to Project Media.[/url]

    I could divide the doc into 2 or 3 or 10 sections/themes/categories, with a project file for each section, but almost all 60 tapes contain moments that fit all the story’s sections – I would want to pull from almost all 60 tapes into each section, so I would still need perhaps 50 tapes in each sections’ project file.

    That would be okay except for:

    A RELATED PROBLEM:
    Vegas project files are ALSO limited by total duration of Subclips.
    Even when I reduced the # of hours of footage, I could only add subclips up to a limit. So I can’t add all the subclips for the project or even for just a section of the project.

    A-ha!
    But now that I won’t be using subclips, if I have the “too many clips” problem, your suggestion may indeed be the solution.
    Thank you!

    – 4 GB RAM
    – Intel duo core processor, 2.16 gHz EACH, 4.3 gHz total
    – Vista 64-bit (32-bit able), with SP1
    – Video Card: NVIDIA GeForce 8400M GS
    – Sound Card: RealTek High Definition Audio, 6.0.1.5384
    – Camera: Sony DSR-PD170. Also: Kodak m1033 digital.
    ——–
    Jilligan

  • Thank you Ron,

    I valued reading your workflow/process/method, and I bookmarked this page, tagging it so I will develop a better gameplan before the next project.

    Pros would first log the shots and would only import areas of the tapes that would actually have a chance of being used in the production.

    In the beginning,
    that’s how we began.
    I could tell you a story, but it’s not a great one.

    Well, maybe it is of interest.

    Before the beginning, before time began, 2.5 years ago, we had hired a great editor. Then he got sick, and the editing work he had done (of which we had seen some) was nowhere to be found. We proposed getting a new editor but he was well enough to say he was totally committed to this project (before his sickness, he began as the producer and principal camera operator).
    At first he had said it’s best to have only one person viewing the footage and editing, but since he was sick he agreed it would be good if our other partner (with a good eye for editing) viewed all the footage, took notes, and developed possible outlines. She watched it all, twice, including noting brief flashes of a visual or sound that could be useful. I had asked her to log it in computer, but she prefers pen and paper, and at that point it still seemed our editor would be creating again soon, and that he would be doing the real work, after having been fed by her thoughts.
    Eventually, with him still sick, I asked her to provide me with a log so I could do a batch capture of logged sections. She concluded, and I accepted, that there were so many clips that it would be more efficient to capture it all and let her then cull it where she could do more precise culling than from the notes she had originally taken for a purpose other than logging. Previously I wrote that we have 250 subclips, but I’ve learned that it’s closer to 900, totaling 18 hours, so I expect that means she was right that it was better to capture it all than for her to try to write a log from her notes.
    Is it clear to you whether it would be better for her to have viewed it all again, this time logging it, instead of capturing it all then culling?

    (I also replied, more briefly, to Douglas.)

    – 4 GB RAM
    – Intel duo core processor, 2.16 gHz EACH, 4.3 gHz total
    – Vista 64-bit (32-bit able), with SP1
    – Video Card: NVIDIA GeForce 8400M GS
    – Sound Card: RealTek High Definition Audio, 6.0.1.5384
    – Camera: Sony DSR-PD170. Also: Kodak m1033 digital.
    ——–
    Jilligan

Page 6 of 10

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy