IMovie '09 dv video capture clip length too short

I have a Sony DV video camera connected to my Mac with a firewire cable. When I do a video capture on most of my videos, everything is fine. On others, it captures about 1000 unique video clips for a minute or two of video. I get 1000 clips ranging from 0.1 seconds to maybe 1.5 seconds in length. Has anyone seen this? Any ideas whats causing it?

You can always download the free trial version of Veescope Live and try capturing with that. Just connect your camera to your computer, start Veescope Live, click the camera input, press play on your camera and then press the record button on Veescope Live.

Similar Messages

Editing VHS Video Imported to iMovie Using Elgato Video Capture

I have imported video using Elgato Video Capture and want to edit it in iMovie. Specifically I want to permanently delete some of the Event video which is of poor quality. I can mark it as "Reject" but I cannot move the "Reject" to Trash. How can I do this?

I see the drop down menus. One is "Move Rejected to Trash" and beside it "Hide Rejected". If I click "Hide Rejected", the rejected clips are hidden. If I click "Move Rejected to Trash", nothing appears to happen.

Log & capture clip length

log and capture seems to arbitrarily determine the clip lengths for a longer piece of footage. each clip within a longer clips seems to vary between 2 seconds to 30 seconds. is there a way to make the clip length more uniform?
thanks

I do not understand. Please describe your workflow in more detail. What format material are you working with, etc.

Channel length too short for calculation

I've just switched from 9.1 to 2010 and I was told that our VBS scripts wouldn't need updating - not so it seems.
I have the following piece of code:
Call ChnAlloc("Input PSD")
L1=Cno("RealPart")
L2=Cno("ImaginaryPart")
Call FormulaCalc("Ch('Input PSD'):=Ch(L1)^2+Ch(L2)^2")
but this doesn't work anymore. I get an error message saying that channel 7 (Input PSD) is too short for calculation. Previously I would have checked the data matrix but I can't find this anymore so I assume DIAdem works in a different way know. The help files suggest that the channel length option for ChnAlloc is optional so I don't understand why it thinks the channel is too short.
Any help appreciated.
Thanks, Si.

Hi SI,
You only need a minor addition, and you get the benefit that all new channels can have their length(s) dynamically changed. Please add this line of code after creating the channel and before the FormulaCalc() command:
ChnLength("Input PSD") = NeededNumberOfRows
Back in the dark days of the DIAdem memory matrix, DIAdem would by default launch with 60 static channels of exactly 8196 rows each. As you apparently know, you could customize the memory matrix to have fewer or more channels, and you could change their static lengths assigned when DIAdem launched. The fully dynamic channel lengths are a vast improvement, but it does mean that for FormulaCalc() commands you need to tell the channel to be big enough first. Interestingly, none of the ANALYSIS commands require you to do explicitly set the channel length before writing to them-- just the channel calculator.
Ask if you have any further trouble,
Brad Turpin
DIAdem Product Support Engineer
National Instruments

Multiple 30" Cinema Displays, cable length too short

I have two 23" Cinema Displays, and they work great! Power adapters have long clean leads and can put them away from my G5 and place the displays where I want. Then I bought a 30" Cinema Display to try in prep for a "Nehalem" machine. I discovered that the power adapter has to be 6 inches away from the back of the computer and the monitor cable is SHORT. I want to use two 30" displays, but the cables are too SHORT and I don't want those two white bricks (power adapters) behind a new Nehalem. Apple says you can run up to eight 30" displays, with the necessary video cards, but no mention how to reach the second display let alone the 8th display!! Does Apple have cables in a male-female configuration? I have looked at Gefen.com and their extensions are Male-Male for the Apple Combo Extension Cables for dual link (30"). I could say demeaning things right now, but I won't.

Thank you for the quick reply, I can place the power adapter where I want with your solution. You would have posted if you knew about an extension with an "elegant breakout for connection to DVI, USB and FireWire ports" but I will still ask if you know of that kind also so that all monitors have USB and FireWire.

Video clip length playing shorter on my mac

Hi all,
Fairly new to mac, so apologies if this is fairly basic.
I have some video files stored on an external hard drive. If I open a file using my PC the video file plays the full length of the clip, yet if I open the file using my mac it opens no problem, yet only plays part of the clip. Can anyone explain why this might be happening ??
Many thanks in advance

Timecode "breaks" in your AVI files.
Use MPEG Streamclip (free) to "repair" them.

Matching Video/Audio Clip Lengths

I import a series of video clips (from 35 mm slides) into the video track time line, each 7 seconds in length with transitions. If desired, I may reorder the sequence of these clips. Then I add voice-over for each clip on an audio track. The voice over time for a particular video clip may run 10-15 seconds. To extend the video clip time to match the length of the audio clip, I set an "in" and "out" marker to match the length of the audio clip, drag the video clip from the Browser to "fit to fill" in the canvas thus extending the time of the video clip. Is there a more efficient way of extending the length of the video clip to match the length of the voice-over clip? Many thanks. Jack A2

Are these still images or video clips? You said they came from slides is why I ask. One way is to use the ripple tool to lengthen the clips in the timeline.

Captured clip length or duration inaccurate

I can't figure out what's happening but I've captured a projected as uncompressed 8-bit (but I've tried others as well) and for some reason the initial clip duration is 80 minutes and works fine in QT but in FCP it shows up as 59 seconds. I can not get it to play anything past the initial 59 seconds. QT sees everything but FCP can't. I've recaptured 6 times changing variables trying to overcome this issue. I've captured another project and it works without a hitch, it's only capturing this project that reproduces this error. The log and capture works as advertised, everything appears normal. Once the capture is finished I double click or drag to the timeline and I get 59 seconds... Open it in QT, all 80 minutes.
Any ideas? This is really frustrating... Thanks.
Greg

Thanks a bunch. Saved suspect file as QT reference file per your instructions, reimported to FCP, I can see all 80 minutes. Such an easy fix for something that caused me so much grief! Thanks again.
- Greg

ORA-28234 - Key length too short

What would cause ORA-28234 to be raised by the show engine? I occasionally get this error during development, quite random and not reproducible.
Thanks

Something like that. Like I said, it is very inconsistent, not reproducible at all. The app doesn't have a login page, it uses the mod_ntlm and associated page sentry function, the same function my app (24317) on the hosted site uses.
What is your diagnosis, Dr. Scott? :-)

Blue screen of death, surprise restarts, and some captured clips distorted, with blocky artifacts!

Hello,
I've been using my set-up (Premiere Pro 2.0* with Cineform AspectHD) successfully for years, to capture and edit footage. But just recently, my computer has given me the blue screen of death after capturing for about 5-10 minutes or caused my computer to restart in the middle of capturing. I've also noticed that the resulting captured clips are, in some places, distorted and contain blocky artifacts. It isn't a problem with the tape because the footage plays just fine on the camera's preview monitor. I tried re-installing Premiere Pro 2.0 and Cineform AspectHD, but the problem persisted after a successful, but brief capture session (the resulting clips were still distorted and contained blocky artifacts). I have no idea what the problem is! One solution I attempted was to capture on another computer in my house, using the same software. Although I didn't get the blue screen of death or a surprise restart, the captured clips were still distorted and contained blocky artifacts in some spots. Another option I tried, with the second computer, was deselecting the Scene Detect option in the capture dialogue box. As a result, the captured clips are free of distortion and blocky artifacts, but the problem is that the captured clips are too big and very difficult to manage (I shoot a lot because I'm a filmmaker and I'm in the middle of a big project). Why is this happening?!
Any help with this problem would be greatly appreciated!
*I'd use a later version of Premiere, but I spent a lot of money on Cineform AspectHD and the version of Cineform I have only works with Premiere Pro 2.0.

I agree with John T. BSOD's are most often caused hardware issues, such as overheating of a component, or a failing, or undersized PSU.
Also, general system drivers can cause failure. Often, those are outlined (though maybe not in really adequate detail) in the Event Viewer's log. In that article, that John T. linked to, there is another link to "Finding Clues." It goes into more detail on using Event Viewer to explore warning, or error messages. If your testing of your system's components and heat, do not yield a weak link, see that one (no pun intended). It is in Reply # 3.
Good luck,
Hunt

Compressor is exporting clips that are too short in duration

Hi,
I am sending clips via FCP 7 into Compressor 3.5.
The problem is that the outputted clips are too short in duration.
Has anyone else had this problem?
I need to fix it quick!
Thanks,
Phil.

Hi, welcome to the forums.
It might be possible that you have set an IN and/or OUT point somewhere.
Double check and make sure that in FCP or Compressor Preview window you
do not have IN/OUT set on a selection of clips.
Luca

Key Lenght too short error with dbms_crypto.encrypt

Hi Friends,
I am getting above mentioned error with dbms_crypto.encrypt.
I had created a thread in technology --> security forum but i am not getting any help from there.
ORA-28234 Key Length too short with dbms_crypto.encrypt
Appreciate if anyone help me resolve this issue.
Thanks
AT

Hi Warren,
Yes function is compiled without any compilation error.
Thanks
AT

Why can't I get any audio sound on my Hi8 video capture in iMovie?

Hi
I have just captured some video clips from my Hi8 Camcorder and exported it to iMovie on my Apple Mac. Unfortunately there is no audio sound on the captured video. Can any one help? I am using Roxio Video Capture USB to capture the video from my camcorder.
Nazimoja

>I am using Roxio Video Capture USB
That's the problem. The Roxio device captures in a highly compressed, multiplexed (muxed) format that isn't intended for editing. Muxed files won't playback audio without the proper software installed on your system. You could try using MPEG Streamclip to convert the captured files to an editable format, but that means you'll be taking a double hit on quality.
The proper way to capture analog footage for editing is to use a qualified "DV Device" (DV camcorder, converter or VTR) to convert the analog signal into a Firewire signal and use iMovie, FCE or FCP to capture and edit. Or, in your case, you could use a Digital8 camcorder for playback directly via Firewire.
FWIW, this is the Final Cut Studio forum. The iMovie forum is located here: https://discussions.apple.com/community/ilife/imovie?view=discussions
-DH

Captured video-material appears far too dark

hi there!
I have a great problem (being under time-pressure with a project): video-material, taken with a canon HV30, that looks all right on the camera-screen, appears FAR TOO DARK (not usable), after beeing captured. the problem does not seem to be a premiere-problem (I have CS3), since windows movie maker produces the same fault. it is neither a pc-screen-calibration or -regulation-problem, since the same material played onto the same screen by another pc, that displays everthing else perfectly, is also too dark. the answer must be between the cam-corder and the capturing software? does someone have a clue? (the problem seems to be not only mine if you check via google... and the solution seems not to be at hand...)
I'm working with DV-widescreen(16:9)-PAL-material converting it with 16-bit sound and 48 kHz.
following my relevant systems-data... (everything is updated with the most recent drivers...)
thanks very much indeed in advance!
hilmar
System Information
Time of this report: 11/21/2008, 23:54:29
Machine name: PC02
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.080814-1233)
Language: German (Regional Setting: German)
System Manufacturer: MAXDATA
System Model: *
BIOS: Default System BIOS
Processor: Intel(R) Core(TM)2 CPU 4400 @ 2.00GHz (2 CPUs)
Memory: 2048MB RAM
Page File: 766MB used, 3172MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode
DxDiag Notes
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.
DirectX Debug Levels
Direct3D: 0/4 (n/a)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
Display Devices
Card name: NVIDIA GeForce 8600 GTS
Manufacturer: NVIDIA
Chip type: GeForce 8600 GTS
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0400&SUBSYS_040110B0&REV_A1
Display Memory: 256.0 MB
Current Mode: 1280 x 1024 (32 bit) (60Hz)
Monitor: (Standardmonitor)
Monitor Max Res:
Driver Name: nv4_disp.dll
Driver Version: 6.14.0011.7824 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 10/7/2008 13:33:00, 6058112 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: Nicht zutreffend
Mini VDD: nv4_mini.sys
Mini VDD Date: 10/7/2008 13:33:00, 6133856 bytes
Device Identifier: {D7B71E3E-4740-11CF-906D-0A2400C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0400
SubSys ID: 0x040110B0
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_C ModeMPEG2_D ModeWMV9_B ModeWMV9_A
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: F

thanks,
dear craig,
for your thoughts and tips!
I will do that just for curiosity. but then I would have to know how the waveform-scopes should ideally look like? where can I find model-scopes? (and, what's more, the camera "gave up its spirit", as we say in german: can't be switched on any more - brand new... so I'll have to get it fixed...)
but: it seems to me, that your path-finding leads in the wrong direction... see: the camera records pictures digitally on a tape. from the tape it is able to read the data again out onto a screen - and fine! now: you should be able to reproduce that outside the camera - and not blame it somehow...
others seem to have the same problem with different cameras and different systems-cominations (operating system, graphic cards...). so it can't be just my camera. the problem is not so easy...
the guy here - http://forum.videohelp.com/topic281706.html - seems to aim in the right direction (imho): he touches the point of the colour-spaces used! he says inside the camcorder IRE 0.0 / 16-235 color space is used. right? well: outside the cam on a computer-screen RGB or sRGB is used, right? so some transformation has to happen - or may be, it is not done - with the bad result, we have...
now the chap there speaks about the possibly wrong codecs. a codec however has to do with compression/decompression. but - they say - the capturing via firewire is just the unaltered transmission of data, and .avi (the resulting format) is compression-free! so the problem is not a codec-problem. but how's the software called that changes the color-spaces or should change them???
what astonished me very much is to see that, when I change the screen-settings for color/luminance with my nvidia-graphics-card, then everything on the screen changes exept! the to video-images in the two screens (source, program) in premiere... so premiere seems to use its own screen-controle here!
and why actually can't I choose somewhere which the output-conditions for and after the capturing shall be, e.g. the clip-format (.avi, .mov etc.) and - may be! - the color-space! I can just say "DV 25i PAL max. bit-depth" and, under device(=cam)-controle, brand and type of device (and again PAL). now I can choose "canon" but not "HV30" (not contained in the list) - just "standard" instead. but that raises the question: what colour-space are the various cameras using and sending??
now if I check the supported camera-brands and -types online on the adobe-website (http://www.adobe.com/products/premiere/dvhdwrdb.html) I can't find canon's HV30 (just the semi-pro-models, for which "conditional support" is promised... but problems seem to lay elsewhere).
on the website, where you can check the compatibility of your cam with premiere, adobe boasts its "Preconfigured solutions
Certified Adobe OpenHD configurations (that) help ensure compatibility between hardware and software components." if you click on the linked text some general boasting and buy exhortations about the "creative suite" come up - no precise information...
should this well known and ill suffered compatibility problem not be handled more clearly and competently?
please help me finding the solution, which is: to interprete the recorded data on the tape, that get transferred via capturing, like the camera does!
thanks a lot indeed!
hilmar
ps: it is interesting to check http://en.wikipedia.org/wiki/Color_space, where it says: "YIQ was formerly used in NTSC (North America, Japan and elsewhere) television broadcasts for historical reasons. This system stores a luminance value with two chrominance values, corresponding approximately to the amounts of blue and red in the color. It is similar to the YUV scheme used in most video capture systems[2] and in PAL (Australia, Europe, except France, which uses SECAM) television, except that the YIQ color space is rotated 33° with respect to the YUV color space. ...
" you see: two different color spaces in TV and CAPTURE SYSTEMS! is premiere not a capture system?? and what do the graphics-devices underway between the camera and premiere??

Hi, i get the error -49 when trying to Export a Movie edited in iMovie and recorded with Elgato Video Capture anyone know why i get this Error and can help me?

Hi, i get the error -49 when trying to Export a Movie edited in iMovie and recorded with Elgato Video Capture anyone know why i get this Error and can help me?

Read this
http://support.apple.com/kb/ts1583

IMovie '09 dv video capture clip length too short

Similar Messages

Maybe you are looking for