Lines During Capture? (Time Sensitive)

Hi - I'm capturing HD video off miniDV into PProCS4 and I see these "lines" in the picture every time there's motion (panning, quick zoom) in the shot.  However, the picture looks perfect on the little camera screen.
Does anyone have any ideas how to fix this?
Thanks in advance for your thoughts!  (This is for a Christmas video, so this is time sensitive!)

Thank you!
I'm going to send the finished piece as a video Christmas Card over the internet - just in case that matters.
So if I keep it interlaced, will it look right after export?

Similar Messages

  • Vertical lines during capture

    Hey Yall:
    Just got Miglia director's cut take 2 for analog to digital capture into FCP 5, and am getting vertical lines in both FCP (5.0.4), and iMovie 6. Probably a miglia issue, but just trying to rule out any possible Mac issues. Any takers??
    Jason
    PowerMac G4   Mac OS X (10.4.4)   Dual 1GHz
    PowerMac G4   Mac OS X (10.4.4)   Dual 1GHz

    I've heard of similar complaints in the past. I don't believe that product play well with FCP.
    Best to return it and get a Canopus 110, or better yet the 300 with built in TBC correction.
    Shane

  • Retaining AVI date/time stamp during capture to pre 9.

    I have pre 9. When capturing DV from my camcorder, how do I get pre 9 to add the clips  time and date to the avi file properties like it does for jpg's. What I get is the date I captured it to the computer. If I add "date taken" to the properties shown, it remains blank.
    I realize the time/frame stamp changes throughout the clip but it should be able to show the initial date/time stamp, for example. I sort these travel clips by oldest date first and need to be able to match them to their itinerary locations. I have a small freeware app that will strip the date/time stamp from the meta data and then I can adjust the time/date in "Organizer" but I have 100's of clips so I'd rather not go that way. I know there app's that will encode the date/time stamp visibly on the image during capture but I don't want that as I make DVD's from the clips. Do you have any advice or suggestions? I have Win 7, 64 bit, 3.2 ghz, 2 core. Thanks, Rob.

    Premiere Elements won't do this.
    You'll need a third-party program called DV Date, downloadable from the web.

  • Flilcker interlaced during capture, Monitor is perfect. CS4

    When capturing DV from a normal panasonic dv cam (GS250) into adobe premiere CS4 (4.2.1) i get flicker / interlaced image in the capture window during preview. But when I look at the captured video in the source monitor afterwards, the video image is perfect.Just upgraded from windows xp premire CS2 to windows 7 (64 bit) premiere CS4. Same camera. The problem with flicker during capture is not present when I use VirtualDub for capture in windows 7. Playback of the captured avi file is perfect, both from VirtualDub and Premiere.

    To be more precise (this is difficult to explain in english for me):
    1) Connect the camera
    2) press F5 to get the Capture window
    3) I press play button to start viewing whats on the tape in the camera. The video image is now "flickering" of "interlaced".
    4) press G to start reccoring. The video images is still flickering/interlaced
    5) press Escape
    6) save the clip
    7) drag the clip to the time line
    8) replay the very same clip from the timeline, video images is now perfect with no trace of flickering/interlaced.
    So it is actually saved allright into the computer. There is nothing wrong with the avi-file. It is just how it looks during capture.
    I also tryed to view whats on the tape on the campera in another program called PowerDirector (a program that was pre installed in the coomputer). The video image is perfect in PowerDirector. I also checked the camera in my old computer, also perfect there.Then I tested Adobe OnLocation to see if I could get something similar there. But no, video image also perfect in OnLocation. I alse verifyed that I had set my project to PAL 25 fps 4:3, the same as the camera.
    This problem is _only_ in Adobe Premere CS4 (windows 7 64bit) and _only_ in the capture window.
    (I also tryed to change the driver for the firevire card. There are 3 built in drivers It didn't help.)

  • Video Stuttering during capture

    I know this has been discussed in the past, but I cannot seem to find it; hope someone will help.
    I am capturing old VHS tapes using Premiere 10 media capture via a Canopus ADVC55.  The clips I'm transferring suffer from stuttering during capture (approx every 1 sec).  I seem to remember that this indicated a timing issue from stretched tape or something.  I hate to think that's the case.  Could it be anythng else, and is there a workaround? 
    Thanks,
    Julian

    Steve,
    I had an informative (but ulimately depressing) talk today with an engineer at Grass Valley.  He said that the ADVC55 adherence to the NSTC spec is quite tight, and suggested I try another source as an input to the device.  I plugged in a Sony camcorder and it converted seamlessly.  He suggested the VHS player (or tape) doesn't meet the NSTC spec, and that I try another VHS player that may be tighter to the spec.  If is also possible that my old VHS camcorder originally used to create the tapes didn't meet the spec.  The ADVC-300 contains time-base correction that could alleviate this, but is substantially more costly.  The cheap Diamond A/V converter probably isn't as sensitive to the spec, and is therefor more forgiving.
    All interesting, but in the end, I have a fairly expensive device that won't help me.  I guess I can look for another VHS player to try, but it sounds like a lot of effort for a long shot.  Any ideas on a work-around?  I'm stuck.
    By the way, MediaInfo shows the following for the  Diamond device:
    Format:  YUU
    Codec:  UYUY          http://www.iis.fraunhofer.de/en/bf/amm/http://
    Frame Rate:  59.940 fps
    Resolution:  480x720
    The link must be to the developer.
    Julian

  • Lighting issue during capture

    During the capture process, when I monitor the picture on the camera's LCD viewer it appears bright & normal. But in the viewing window on FCP during the capture it appears much darker. Likewise, after the capture is complete and I run the clip in the viewer it also appears just as dark as it did in the viewer during capture. Likewise, it's just as dark when placed in the time-line and viewed in the canvas. Hence, is it a setting during capture or something else that causes the picture to become much darker in FCP? THX!

    Nothing is being adjusted during the capture process. The images being brought into the computer are what the camera really recorded.
    If so, why do they look so different? It could be someone turned up the "brightness" on your camera viewfinder to see images on a sunny day. It could be your computer monitors are set way too dark.
    The truth will not be found until you view the image on an adjusted external monitor designed to play that video format. Until then, you have no real idea of the lightness/darkness of the image.
    x

  • Speed Issues during Prime Time

    Over the last two months my speed during primetime hours 4 pm to around midnight have degraded drastically.  During these hours I typically get 1mbs, during the rest of the hours from midnight to around 4 again, I get the full 7mbs that I pay for.  I thought DSL wasn't supposed to have these problems and it was typical for cable companies.  I would really like this to be resolved as it wasn't always like this and now its to the point where its unacceptable.  I've tried removing my router and connecting both my pc and my mac directly to the dsl during these times incase it was some sort of virus issue, and that didn't solve my problem.  Not really sure what to do.
    So to summerize
    -Slow internet speeds in primetime hours 4  pm to 12 am PST
    -Problem has only been happening in the past three months but has been getting noticeably worse recently.
    -4pm internet speed drops to 1mbs at midnight goes back to the 7 mbs I pay for and stays that way until around the same time the next day.
    Tried hooking up modem to both a pc and a mac and removing the router during these slow periods as well as restarting the modem with no positive result.
    The modem I have is a Westell G90610015-20 Rev E.
    Router is a netgear but again this happens with or without the router.
    Speedtest numbers during these times agree with it, and when I check the modem connection setting it still says I'm at 7000+ down so I'm not exactly sure whats wrong.

    Please post your Modem Transceiver Statistics. You can obtain them by visiting http://192.168.1.1/ , clicking System Monitoring, Advanced Monitors and then Transceiver Statistics. If you are presented with a Username and Password prompt, try one of the following combinations.
    admin/password
    admin/password1
    admin/admin
    admin/admin1
    Your Verizon username and password
    Additionally, how is your voice service, if you have a phone with with Verizon? Do you have Static, buzzing, or any other noise on the line that should not be there? 
    If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

  • No sound captured during Capture Now

    First time in many moons using FCP. I'm capturing from a mini DV (Canon Eulura 70) using the Capture Now function. The problem is that it appears that no sound is being captured. I've read other posts about not hearing sound during capture... at the moment I'm using headphones connected to the camera and the sound is fine. I'd prefer to use the computer to monitor the sound but I cannot locate a checkbox anywhere to turn this feature on.
    When I drop the captured clips onto the canvas no corresponding audio file appears in the timeline, and no audio plays during playback. I've checked the clip setting in log/capture and it's set to capture both video and audio. I've checked System Settings, and under Scratch disks it's set to capture video and audio separately. Audio playback in FCP is set to built-in audio. Sound is working fine in all other applications.
    I've tried trashing the preference files but no effect. Also I tried to just capture audio, and as soon as I hit esc, FCP crashes... this is totally repeatable. I also noticed that on the clip setting tab there is a section with a bunch of sliders (7 in all)... don't know what they do, but they are all greyed out.
    Camera works fine in iMovie...
    Message was edited by: Ronald Dans1

    There are no check boxes on that tab, only a pull down list entitled "Capture". The choices are Video and Audio, Video only, Audio only. I have it set to Video and Audio. Perhaps there are checkboxes in another version?

  • When i sign out of imessage, and then sign back in, all the messages i received during my time away, are not there instantly. help?

    when i sign out of imessage, and then sign back in, all the messages i received during my time away, are not there instantly after i sign back in. help?

    hi,
    Mac, iPhone, iPad, iPod Touch ?
    Do they appear eventually ?
    The iMessages are "pushed" to the devices which means there can be small delays between the server recognising the device went Off Line and coming back.
    10:19 pm      Thursday; July 10, 2014
    ​  iMac 2.5Ghz i5 2011 (Mavericks 10.9)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
     Couple of iPhones and an iPad

  • Why can't I Apple+H hide Final Cut during capture anymore?

    I used to love hiding the big screen while it was capturing footage and I could get on with other stuff and see my desktop!
    For some reason it doesn't hide anymore?
    Anyone know about this?
    Alex

    Alex Wilding wrote:
    I have a Powermac G5 and I hide Final Cut during capture and get on with other things on the machine all the time, no problem.
    Now, there is a problem though, now Apple-H doesn't hide it! I just don't understand why this would happen all of a sudden? I can live with it but I preferred hiding Final Cut so I can see my desktop.
    Alex
    Hi Alex, very interesting. What version is your OS? Did this happen after an update to the OS? I can certainly understand your frustration when a function all of a sudden doesn't work as it use to, especially when it's a function that is suppose to work.
    Personally I don't do too many other tasks while capturing, but I will often switch over to check my email or something not very demanding upon my system. Yet, I have at times run some pretty heavy applications without any problems with my capture. So, I suppose it has a lot to do with installed memory and your processing power + fast drives. In any case, I understand what your asking here and will be anxious to see what other solutions you are offered.

  • Variable Creation During Run Time

    Is there anyway to create new instances of variables during run time based off of user input from a command line prompt. Thnx~!

    Depends what you mean .. if you mean the user can type "a = 8", and it creates a variable "a" with the value 8, then no.
    But you can implement something very similar using a HashMap. Use put("a", new Integer(8)), or whatever, and then get it out later with get("a").

  • Edit Capture Time XMP vs. EXIF

    Scope:
    - LR 1.4.1 and 2 Beta
    - Any file that is edited using Metadata:Edit Capture Time
    (Note: detail info below may be helpful to those seeking to understand date/time problems/issues with LR and other tools)
    Background:
    LR allows editing/offsetting of image capture time via the Metadata:Edit Capture Time menu option.
    Changing the time in LR alters the following EXIF date/time metadata fields as displayed in LR:
    - Date Time Original
    - Date Time Digitized
    - Date Time
    Writing the LR metadata to the image file via the Metadata:Save Metadata to File command writes the values into the images relevant EXIF and XMP date/time metadata fields.
    Challenge:
    LR writes the correctly edited times into the XMP date/time metadata fields but writes incorrect times into the EXIF date/time metadata fields.
    LR uses XMP date/time metadata fields for its displayed time data, not EXIF date/time metadata fields. As a consequence, the user does not know the EXIF time fields have been incorrectly changed unless they check them in a tool that displays or uses the EXIF date/time metadata fields.
    Solution:
    Use a batch file based on exiftools to copy the LR edited XMP date/times into the EXIF date/time metadata fields.
    Resources:
    - Batch file LR XMP/EXIF date/time bug fixer here - LR-xmpdatetime2exif.bat: http://www.hackneys.com/photos/lr/LR-datetimexmp2exif.bat
    - Batch file arguments file (required) here LR-xmpdatetime2exif.args: http://www.hackneys.com/photos/lr/LR-datetimexmp2exif.args
    A few useful tools to better understand this challenge:
    - Batch file to display relevant date/time metadata fields here - list-exif-tags-sample-datetime.bat: http://www.hackneys.com/photos/lr/list-exif-tags-sample-datetime.bat
    - Batch file to display set of EXIF metadata here - list-exif-tags-sample.bat: http://www.hackneys.com/photos/lr/list-exif-tags-sample.bat
    - Batch file to display set of XMP metadata here - list-xmp-tags-sample.bat: http://www.hackneys.com/photos/lr/list-xmp-tags-sample.bat
    - Batch file to display complete set of metadata here- list-metadata-tags-sample.bat: http://www.hackneys.com/photos/lr/list-metadata-tags-sample.bat
    - Sample photo file here sample.jpg: http://www.hackneys.com/photos/lr/sample.jpg
    Preparation:
    All batch files require an installed copy of exiftools by Phil Harvey (free) available here: http://www.sno.phy.queensu.ca/~phil/exiftool/
    1. Download exiftools windows command line version and rename the file exiftools.exe.
    2. Place the exiftools.exe file in your windows directory or on your system path.
    Utilization
    1. In Lightroom, select the folder containing the photos you need to fix.
    2. In Lightroom, select all the photos you need to fix.
    3. In Lightroom, select Metadata:Save Metadata to File (this step ensures you dont lose any Lightroom specific metadata that has not been embedded in the file).
    4. Using Windows Explorer or another utility, backup your jpg files
    5. Using Windows Explorer copy the LR-xmpdatetime2exif.bat and LR-xmpdatetime2exif.args files to the folder with the jpg files you need to fix.
    6. Using Windows Explorer double click on LR-xmpdatetime2exif.bat
    7. Wait for the batch file to process.
    8. In Lightroom, ensure the photos you just fixed are still selected, if not, re-select them.
    9. In Lightroom, select Metadata:Read Metadata from File (this step ensures that Lightroom has all the revised EXIF date/time metadata loaded).
    Detail:
    This challenge is a subset and another manifestation that LR 1.4 uses the XMP date/time metadata fields, not the EXIF date/time metadata fields that other programs use and rely on. There have been numerous posts regarding other manifestations of this problem.
    Most of the confusion relates to several primary factors:
    1. Cameras embed EXIF metadata into photo files. Adobe products, and some others, support XMP metadata, which is not part of the EXIF standard. If a tool was developed p

    Detail:
    This challenge is a subset and another manifestation that LR 1.4 uses the XMP time data fields, not the EXIF fields that other programs use and rely on. There have been numerous posts regarding other manifestations of this problem.
    Most of the confusion relates to several primary factors:
    1. Cameras embed EXIF metadata into photo files. Adobe products, and some others, support XMP metadata, which is not part of the EXIF standard. If a tool was developed prior to XMP, such as Exifer or PSP 9, then that tool has no way to view or edit XMP metadata. If a tool only displays, edits and maintains XMP, such as LR, then the two data sets can become de-coupled for common data points, such as date/time. If a tool relies on the EXIF version of a common data point, such as RoboGEO, but the date/time was edited by a tool that only maintains XMP data, such as LR, then the EXIF dependent tool will be working with out of synch data.
    2. LR, PSE, Bridge, etc. use, either exclusively or primarily, XMP metadata, even though they may label/display it as EXIF. LR, for instance, only displays the XMP date/time values, even though they are labeled EXIF.
    3. The EXIF specification assigns time field names different than those commonly used in various tools when labeling/displaying EXIF time data fields. You will find the very same EXIF date/time field labeled a wide variety of ways in even a handful of tools.
    4. The XMP specification has a namespace area labeled EXIF. Adding to the confusion even more, the XMP-EXIF namespace has date/time field names that duplicate those of EXIF date/time fields.
    As you can see, if you add these four factors together, it is no surprise there is widespread confusion related to photo file date/time in general and LRs handling of it in particular.

  • Lr no longer sorting images by capture time

    Good afternoon,
    I've been using Adobe Lightroom 2 with Photoshop CS4 without any problems.
    However, recently I've been having problems with the order in which LR is storing my images.
    I work in Raw and always start from LR. From there I open my image in Photoshop before making any adjustments and then saving as a 16bit PSd or Tiff.
    On the first save the psd/tiff file is stored as normal in LR - i.e next to the original raw and virtual copy. But now, when I return to make any alterations in Photoshop the re-saved psd file is moved to the very beginning of the Lightroom library. The box around the image is blacked out and against it it has a message '2 of 0' and the phrase 'photo is part of a stack'.
    I don't understand why it's doing this and I don't use stacks purposely. I just want my images all on display, next to each other for ease of use.
    All my photos are sorted by capture time and even though the files in question are of the correct time it still doesn't stop Lightroom from placing it at the top, well away from where it ought to be.
    It's not a massive issue but it is quite annoying when you have thousands of images in your catalogue, and it's never done it before. I've restored LR to the default settings but it hasn't made any difference.
    Please can anyone help.

    Thank you very much.
    I tried as suggested
    > Stacking> Auto Stack By Capture Time
    and that moved the psd file back into line.
    I've tried opening up a few of the psd files into Photoshop and re-saving and so far so good! They're still alongside the original raw files.
    The strange thing is that the sort order is/was set to capture date so I don't know why it moved it in the first place.
    Thank you again. Much appreciated.

  • File manager crash during capture

    Using the latest version, I am getting consistent crash during capture of the file manager. Using an IBM T61P that has a 7200rpm drive. If I do frequent saves during capture I don't loose the work before the next crash. I hope I don't have to use an external drive to make this problem go away.
    Any ideas out there?

    Dennis already said it, but a single disk is not enough. Minimum requirements are a DEDICATED 7200 RPM (e)SATA disk for capturing. Add to that the fact that your system is dead slow (at least 50 times slower than a fast system) and that one should not do anything else during capturing, and that the system may not be tuned at all for editing and disaster is waiting to strike.
    Have a look here: Adobe Forums: Guide for installing and tuning a Vista... which also applies to Win7, for a band-aid. It will not solve the issue of an extremely slow CPU, possibly integrated Intel graphics, which should be avoided at all times, shared memory, which is another no-go and the lacking disk setup.

  • LR3: sorting by capture time

    Sorting by "Capture time" does not seem to work right in LR3.4.1. In Grid view, with compact cells, top label: capture date/time, and using Sort: Capture time, I see pictures from 2009, then 1900, 1910, 2010. The files are .jpg and .psd - no movies. Metadata -> Edit capture time... also shows the correct date/time. It's just the sorting that does not get things in the right order. Most of the files are imported from PSE6, which sorted correctly. For some JPGs, LR3 seems to show the windows file creation date (as can be seen in the Windows file properties), not anything in the metadata. For the PSD files, the correct date I want to sort by (the one PSE6 showed) is shown as Exif metadata "date time original" and "date time digitized".
    This makes me wonder what date is actually used by LR3 for sorting by capture date?
    Any suggestions for getting LR3 to sort the way I want?
    Tia,
    Alex

    Interesting -- I was able to confirm the same thing.  It appears that if an image is missing metadata date/time fields, then LR uses the file date-modified for filtering and sorting, and it uses file date-created to display in the grid view.  Seems like a blantant bug to me -- you could report it at the new feedback site, http://feedback.photoshop.com/photoshop_family/products/photoshop_family_photoshop_lightro om, where Adobe employees reguarly participate.  Adobe may not make this a priority to fix, since their priority is LR's focus on images taken with digital cameras (which always attach a date to the metadata), and those of us using LR to manage non-digital-camera images get lower priority.
    So there are two problems:
    1. You have images with metadata fields XMP:DateTimeOriginal that omit seconds, and when these were imported by a LR version earlier than 3.4, they produced corrupted catalog capture-date entries. You could try doing Metadata > Save Metadata To File followed by Read Metadata To File for these images -- that may clear the corrupted catalog dates and be a little bit easier than removing the images and reimporting them (which would lose your stacking and collections).
    2.  As described above, LR uses file date-created and date-modified inconsistently for images without metadata date/times.  A workaround is to make sure all your images have the field EXIF:DateTimeOriginal in their metadata.  You could do that one photo at a time using the Medata > Edit Capture command.  Alternatively, you could use Exiftool to copy the file date-modified or file date-created into the EXIF:DateTimeOriginal field for just those images that don't already have that field.  That will take some study of Exiftool documentation to come up with the precise command line -- it's a powerful tool but not easy to use at first.
    You'll have to figure out whether the file date-modified or the date-created is the best date to use for your images.  Beware that on Windows, date-modified is generally preserved when a file is copied, whereas date-created is not, and some backup programs won't properly preserve date-created.

Maybe you are looking for