PE9 freeze on VOB capture

I just installed PE9 onto my machine and can't capture video. I am running a PC with Windows 7. I have an i7 930 2.8 GHz with 6 GB RAM. I have been trying to capture video from a DVD and PE9 just freezes and locks down my entire system. The files are in IFO, BUP, and VOB.... VOB being the video. I don't get an error message, I only see "not responding" in the bar and everthing locks up. I am a first time user of PE and haven't been able to do anything with it yet, please help!

I mentioned that the Copying of the VOB to the HDD is preferred. There are two main reasons for doing that:
DVD multi-drives are very slow, and trying to use material directly from the DVD can be too slow for a program. Windows Explorer is very patient, and will calmly wait, while the data is being written to the much faster HDD.
If one has Imported directly from the DVD, then that disc must be in the multi-drive, whenever that Project is Opened, or all media will be Offline. When one Imports an Asset into a PrE Project, the media file is NOT copied over, and does not exist within the Project's file, the PREL. Only a link to the location is included, and if that Link is broken, such as the DVD being removed, or not available, then the program has nothing to Link to, and will have to Offline that media. By having the file on your HDD, and not Moving, Deleting or Renaming it, will mean that the Link is constant, plus things will be MUCH quicker.
Hope that explains things, and will help.
Good luck,
Hunt

Similar Messages

FCP freezes temporarily during Capture

Hi
I've been using FCP for almost 5 years now and I never encountered this problem. I usually use log and capture to bring my footage in. Lately, I noticed that on some clips, the footage will freeze during the capture resulting in a skip/jump cut when I play the imported clip later.
I am using FCP HD on a 1.8Ghz Mac G5.
Could anyone advise please?
T.

I always set the "on timecode break" setting to "warn after". FCP will capture over timecode(TC) breaks if they are logical and not big. How about your disk configuration, or RAM. Are the disks running full, more than 80% filled? Do you have the proper configuration for the video you are trying to capture? External FW disks will work, but they are not created equal. I would say if you are using external FW800, that you would be all set. Some FW400 have a lower sustained data rate. How about RAM? Running enough, is it after market (some not supported by apple)?
G4 dual 450Mg AGP, G3 1G RAM Mac OS X (10.4.5)

Freeze frame while capturing

Hello
Whislst capturing I experience a freeze frame in the capture display window for a few minutes, then it starts playing again. When I look at the captured clip the still image is still there but the audio is running as normal. Is this a problem with the cable? or something more serious.
Many Thanks
Adrian

As you may have guessed, I have not experienced your problem and have been giving general trouble-shooting strategies.
There is one more. Reinstall FCE !
It may sound drastic but it will only take ten minutes or so.
The reasoning behind it is that FCE may be corrupted in some way.
However, you must uninstall it fully first, or you will be rebuilding on dodgy foundations.
This is how to do it :-
FCE 1 and 2..... http://docs.info.apple.com/article.html?artnum=93688
FCE HD............ http://docs.info.apple.com/article.html?artnum=301182
You don't need to trash the LT or Soundtrack items.
Ian.

FCP6.05 keeps freezing in log & capture

FCP6.05 keeps freezing after log and capturing for short time of 5 or 7 minutes.
I had to shut down as it woudn't respond to quit. Then it would only part open and freeze.
previously the problem was that it wouldn't allow firewire audio option when copying to tape, just the default playing sound thro' laptop, hence no audio on copy tape.
I tried trashing preferences but it didn't help.
Has a solution to these problems been discovered? Thanks.

I had a probelm with dropped frames when capturing. Im also using a mac book pro. for me it was having my e mail open whilst capturing. now when capturing I only have fcp running.

MBP freezes after Screen Capture (Cmd+Shift+4)

When I try to do a screen capture, my MBP is freezing (rotating wheel) after the 2nd or 3rd screen capture. This is new after I upgraded to 10.6.6
Any hints?
thnx
viTus

I don't think there is a bug for Apple to fix, as far as I can tell. I've taken plenty of screenshots using cmd-shift-4 since the update (I actually did a number just a few days ago), and my system is working just fine, as always. I also haven't heard any other reports of this kind of problem. So, the question is, what's going wrong with your systems?
Since it's happening on two different machines, my inclination would be to blame third-party software you've got installed. Try [starting up in Safe Mode|http://support.apple.com/kb/HT1455]... does the problem still happen then? Safe mode disables third-party software that may be loading at startup/login, so if the problem goes away in safe mode, then it's just a matter of figuring out what software is causing the problem.
Also, are you using any other third-party hardware, especially input devices, with both MacBooks when you're taking the screen shots? If so, try disconnecting all of it and use just the built-in keyboard and trackpad. If the problem goes away then, it's probably a hardware incompatibility.

Event Structure Freezes Vi After Capturing The First Event

My Event structure catches the first instance of my button press but then it freezes my Vi. The reason is because of the while loop but I need the while loop to constantly read from a serial port and send data to a serial port. The vi included is stripped down to be just a while loop that does nothing. I have also tryed putting the event structure in the while loop, but the same thing is happening.
Any ideas?
Thanks,
Cason Clagg
SwRI
LabView 7.1, Windows XP

Also, put the button inside the event structure where it is acted upon, from LV help (suggest you read the entire events section of help):
When you trigger an event on a Boolean control configured with a latching mechanical action, the Boolean control does not reset to its default value until the block diagram reads the terminal on the Boolean control. You must read the terminal inside the event case for the mechanical action to work correctly. As a reminder, a note appears in the Edit Events dialog box when you configure a Value Change event on a latched Boolean control.
Refer to the Handling a Latched Stop Boolean Control in an Event Structure caveat for information about how to handle a latched Boolean control.
When you trigger an event on a Boolean control configured with a latching mechanical action, the Boolean control does not reset to its default value until the block diagram reads the terminal on the Boolean control. You must read the terminal inside the event case for the mechanical action to work correctly. As a reminder, a note appears in the Edit Events dialog box when you configure a Value Change event on a latched Boolean control.
Refer to the Handling a Latched Stop Boolean Control in an Event Structure caveat for information about how to handle a latched Boolean control.
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

Video freezes during clip capture

Help! I'm capturing my footage a clip at time for this project to save space on the hard drive. Sometimes the captured footage has a one or two second section where the video is frozen. It doesn't happen on each capture but enough to be very annoying. Is there something I can do to fix this?
Thanks
Michael Calamar

I think thats when FCE is locating time code. It usually stops the video for about 1 min. and it looks for places where you have a timecode break. That's when you stop the camera and review what you shot. Because you won't get back to your original place, you may have gone too forward and there is two seconds of nothing. FCE sees this as a 'timecode break' and breaks the clip everytime it sees one. You should avoid this, and the way to is to not review your footage. (I mean, reviewing it isn't gonna change it, is it?)
- Craig

Image capture keeps freezing

I just scanned several images using image capture a week ago no issues and now image capture keeps freezing in scan mode. updated drivers. wireless is detecting (using a canon MP640) in "scan gear" screen preview works fine but when scan is choosen everything freezes and image capture (not responding)
anyone?

I just had the same problem. Printer is connected by USB and the print function works perfectly. Mashing the scan button launches image capture but the pinwheel starts spinning and nothing happens. Same printer. Did you ever solve the problem?

Premiere Freezes During Capture

I have a problem with Premiere freezing during capture, consistently at 17 minutes, around 25 seconds.
I am capturing from a Blackmagic Decklink SDI card, 720p 59.94, ProRes 422 HQ. I've also tried LT.
I am running Premiere 6.0.2 on OS 10.6.8 on a Mac Pro. My 1TB disk is empty and still has 900GB available after 17min of capturing.
Any ideas?

I have the exact same problem. The diference is im capturing from another device (Sharp Video 8 camera connected to BlackMagic Intensity Shuttle for Thunderbolt). Premiere doesnt freeze, only the capture window shows freezed image, at some random point, first it was almost like afer 1hr of recording but now is at any time, sometimes after secconds. Sometimes i can still hit stop and the filename window appears so i can save the file, but other times it doesnt. I hit stop and nothing, so i try to hit record again and it starts recording again, i can tell because another file is created, but the previous file is corrupt (i suppose because it isnt closed by premiere).
I have a MacBook Pro Retina 16gb RAM 512 GB SSD, i dont think the computer has no capacity for handling this...

Capture Now Freezes

I frequently capture video in to FCEHD using capture now. I've double checked all of my settings but my computer always freezes when I capture a clip greater than 4 minutes in length. I also have a MacBook Pro where I can capture 15-20 minutes at a time with no problem. I also have a lacie external hard drive hooked up to my G4 where I capture too, but I've also hooked it up to the MacBook and have had no problem at all. Then when the computer freezes it completely locks up my internal hard drive and I have to end up powering off the computer manually. When I restart, I open my external hard drive icon and the clip ends up having a (-av) behind the title and the clip almost takes up the entire hard drive space (about 300 GB). I can then delete the clip, which does free up space and start all over.
Thanks for your help!!

Well, I checked the specs on FCEHD 3.0 and your version of OSX is ok. The minimum requirements are:
• Mac OS X 10.3.7 or later
• QuickTime 6.5.2 or later
If you upgraded to QuickTime 7 on the Panther machine, however, that could be the source of your capture problem. Admittedly I'm guessing there, but I encountered enough other problems with QT7 on Panther machines that I long ago stopped installing it unless the system already had Tiger (10.4) installed.

AVI File Captured in Premiere Elements 8 Only Plays First Few Minutes

Hello folks,
I'm totally new to this. My problem: I've recently installed Premiere Elements 8 and used it to capture some mini DV video tapes (via firewire), without any significant problems (other than a few freezes). Now I've tried to capture some VHSC tapes via my TV card (Avermedia H727). The capture process went well (except that the preview screen was just a fuzzy mess!) but I had to plug the audio inputs into my sound card (onboard) rather than the TV card.
The caputred files are about 6 + Gb for a 30 minute tape but when playing the captured video back in PrE8 only the first few minutes is available (the length of playback seems to vary unpredictably (1 tape allowed 3 minutes of playback, another a bit less).   The full avi files can be played back in Roxio or Windows Media Player etc but not PrE8.
Interestingly, videos captured from VHSC via the same TV card in Roxio 2010 Pro will play back correctly and fully in PrE8.   I had to switch audio inputs to the TV card (rather than the soundcard) for the audio to be captured with Roxio.
My son has tried to help me with this (having some experience on PrE2) but he's also drawn a blank with this.
I'd be very grateful for any help that you might be able to give as I've not found anything in FAQ although it's not easy to succintly define my search for this problem.
Many thanks
Computer spec:
OS     Windows 7 Pro 64 bit
CPU     Intel i7 2.8GHz
RAM     4Gb DDR3
MB     Asus P7P55D Deluxe
HDD     2x Sata II Western Digital 1.5Tb (each)
Graphics     ATI Radeon HD 4300/4500 series
All updates for Windows 7 and PrE8 installed

Thanks John:
My PC has 2 HDDs and both are of the “green” variety. Both are partitioned (2 partitions on each HDD) with operating systems on the first partition (Windows 7 Pro 64 bit on one and Windows XP Pro -32 bit on the other, the operating systems are on different physical drives).
The tips relating to PrPro are hard to follow as they are quite technical and I’m not even sure which ones also relate to PrE8.   It would take me an age to try to wade through this lot.
My point is that my current setup (for all its imperfections) will capture video (via the TV card) using PrE8 as the capture software. The setup must be adequate for this task as the complete avi file is played back correctly on Roxio and Windows Media Player but PrE8 fails to recognise any video after the first 3 minutes (approx).
If I capture to PrE8 using a firewire connection from my mini DV video camera then the capture proceeds normally (apart from odd freezes) and the captured video is all playable in PrE8.
When capturing using the mini DV camera, I select "DV camcorder" in the “Get Media” menu. However, this only supports Firewire or USB sources.   When capturing from the VHSC tapes via the TV card I have to select “Webcam or WDM Device” as the media source (I’m not convinced that this is the most suitable capture mode but it’s the only one I can find that doesn’t look for either a firewire or USB device.
It seems as though PrE8 must be putting some code onto the captured video that prevents more of it from playing back because avi files recorded on Roxio will playback fully.   I've tried to copy the PrE8 avi files into a different folder (devoid of any PrE8 project files) and then renaming the file before importing into PrE8 but still only the first few minutes will play.   My thinking here was that perhaps one of the other associated project files that PrE8 creates might be the source of the corrupt info.
Many thanks for your interest and taking the trouble to respond.

Sync problem during capture

Hello, if anyone can solve this for me I owe them a large beer.
I have FCE 3.0 which has been working fine for the past year, but recently every tape i capture has serious audio sync problems. initally i thought it was the camera, but i have 2 and the problem occurred from both, then i thought it was the tape so i tried various tapes including ones that had previously worked, but the problem persisted. Then i thought it might be the cable, but the tapes import fine into i-movie, so it can't be that. I checked the capture settings - has always been and still is 48 pal - i've always use the same cameras (canon xm2s).
The problem is that the video freezes every 31 seconds for about 28 frames, but the audio doesn't, so that you get a sync problem that increases as the clip progresses. you can see the video actually freezing in the capture window, although it plays back fine in the camera (and in i-movie).
This is killing me as it is simply impossible to edit as the sync problem is not constant so its not just a matter of doing the math & moving the audio.
I've spent about 5 hours today trouble shooting this & trawling through user forums to find some help and after reading an article on this site (http://docs.info.apple.com/article.html?artnum=305284) have ordered an upgrade to FCE 3.5, but am not convinced.
Has anyone any similar experiences / advice / good contacts for tech support?
Any help greatly appreciated.
i mean it about the beer!
Cheers,
Murray
g5 os 10.4.9 Mac OS X (10.4.9)

Hello fellow Tyke and welcome to the discussions. Try Ian's suggestion here. (He's from the wrong side of the Pennines, but we'll let him off)
http://discussions.apple.com/thread.jspa?messageID=4523275&#4523275

How to stop Freeze frame jitter/fuzz in PE3

I used freeze frame to capture a video frame to add titles. During play the freeze frames have jitter or fuzzy look. Is this interlace problem? How do I get a freeze frame (duration 5sec) to look as clean during play as when paused?

Wes,
Usually, the best practice is to critically study the exact Frame, that you Export as a still. Due to the "effective shutter angle" of the camera, one frame might look a lot better, than the one just a frame earlier, or later.
I like to view the Program Monitor (the Preview), at 100% and use the Rendered Timeline, as ATR mentioned. If one is set to Fit (and not to 100%), it's a bit tough to get a good look at the frame.
It also might help to tell us the full details of the AV file that you are using, plus the Project's Preset. There could be an element there, that would improve your output.
Good luck,
Hunt

Solution for "Error while trying to synchronize Audio and MIDI" and "System Overload" messages

Article for those who hate Logic error windows
Seen in Logic Pro 9.1.7 on Mac OS X Lion 10.7.4
and Logic Pro 9.0.0 on Mac OS X Snow Leopard 10.6.5
Logic Pro:
System Overload.
The audio engine was not able to process all required data in time.
(-10011)
Error while trying to synchronize Audio and MIDI.
Sample Rate xxxxx recognized.
Check conflict between Logic Pro and external device.
The search in the help given as follows: overload occurs when you use a lot of tracks and a lot of effects on them, and the synchronization is lost when the selected MIDI track for recording or playback. Yes, this is all that is written in the resources. And here are useful tips that have been found:
The Bounce function allows the entire instrument track to be recorded as an audio file. This bounced audio file can then be used (as an audio region) on a standard audio track, allowing you to reassign the available processing power for further software instrument tracks. For more details, see "Bouncing Your Project."
You can also make use of the Freeze function to capture the output of a software instrument track, again saving processing power. For details, see "Freezing Tracks in the Arrange Area."
These tips - about the timing. About overload - there are no tips, except as "reducing the number of plug-ins" and "increasing latency". Zero useful tips - I got two errors in the test project with a blank audio track with no effects, MIDI drums and standard synthesizer, it was no aux buses, and the entire project was only a single plugin in the master track.
Here is the configuration of my computer:
iMac12, 2
CPU: Intel Core i5 3,1 GHz
Memory: 4 GB
And here's a project that almost immediately stops Logic, all instruments and plug-ins with the init-patch, ie not the most demanding settings:
It's sad.
When this happened the first time, I could start the project only if the empty audio track has been selected, a track specially designed so that you can at least start the project. Then, this problem has evaporated along with the changing conditions of work and I forgot about it until the last case.
I was looking for the cause of the problem in the console and the system monitor for two days, and finally I found that Logic ping to the network frequently. I remembered the exact time of occurrence of the problem, and system logs revealed that the problems began immediately, as soon as I deactivate the service of the Internet.
Solution: enable the Internet, or add a new network service on a computer with no Internet. I just created the Ethernet connection to the ip address 1.0.0.0
Logic immediately began to sing.

Hi gabaghoul
Yes, it worked for me on four different OS and Logic versions (10.6 - 10.8 and 9.0 - 9.1.6)
It does not work in some cases, hard enough to tell in which one, but you can try, it very easy: go to the net settings and create new Ethernet connection to the ip address 1.0.0.0 and connect LAN cable to the port.
Also you can try to figure out what happens in your system while Logic error occured - fot that you just start Console and search "logicpro"
Pay attention to repetitive events in a console and events with suitable timing, not so far from error
The problem may be related to the GUI or system memory, sometimes turning off Safari (or Chrome, others browsers) might help.
Message was edited by: spred

Logitech quickcam Sphere/Orbit compatibility problem

I'm having troubles to make JMF works with Logitech's Quikcam Orbit (known as 'Sphere' in Europe).
Oh, ok, this device is quite different from other ones as it is motion-capable.
- JMFInit, it 'freezes' on the capture device detection.
- I wonder if some logitech's driver such as motion control palete or something is not actually locking the device connection by JMF...
Anyone experienced using this cam with JMF??
Any consideration or idea (other TWAIN driver) ? (replacing the cam is NOT an allowed suggestion ;-) )
Thanks in advance, have a nice day...

I have succesfully used this camera with JMF under linux.
First, I've used this site to get the drivers to get it working on video4linux:
http://www.saillard.org/linux/pwc/
Then I started the jmstudio and did a scan for devices. After that, it worked, both in jmstudio and in a simple demo application I wrote. The only thing that does not work is the control of the pan and tilt motors.
If anyone's interested in getting those to work, let me know! :)

PE9 freeze on VOB capture

Similar Messages

Maybe you are looking for