IMovie using 200-300% CPU when editing video. Why?

Hello everyone,
As the title says, I am experiencing iMovie using 200-300% of my Macbook Air's CPU. This occurs when I am editing the video, taking parts out and making sure everything look and sounds good.
Does anyone know of a way to stop iMovie from using this much CPU?
Any help will be appreciated,
Thank you.

having the same problem. tried deleting the preferences and now i can't even insert cutaways - all options disappeared from the pop-up menu, only leaving the option to replace or insert

Similar Messages

When I use Photoshop CS 6 to edit video, I don't know how to change video speed after I converted the clip to smart object?

When I use Photoshop CS 6 to edit video, I don't know how to change video speed after I converted the clip to smart object? The clip color turns purple and it only allows me to add motion but not change the clip duration and speed anymore.

Thanks for the reply and as a work around method I used the Photoshop to do all the adjustments then export the video to iMovie to finish the final cut. I also have a problem to paint or clone on a blank video layer created in Photoshop. It tells me the time is beyond the target frame time, I don't understand the message. Can you explain to me what did I do wrong? Thanks a lot!
John Wang
801-3618742
[email protected]
http://johnwanggallery.shutterfly.com

How can I get the QUICK DEVELOP panel to appear when editing video in Lightroom 4

When editing video, the only panel that appears at right hand side is the the one silimar to the developing of still shots. But of course, it is greyed out, thus preventing its use when editing video.

Lee Jay for USA president.
Thanks a lot Jay. Right clicking on a panel brought up QUICK DEVELOP. I've searched through books galore and none mention this.
Regards
Mike

IMovie lags when editing video and audio

I just bought iMovie yesterday from the Mac App Store. I recorded a DJ set and wanted to edit my Video with better quality audio that i recorded seperately. I find that when editing my video and audio (Matching up audio), there is alot of lag. Especially when scrolling through the video to drag the audio to a certain point to get the audio in sync. This is very frustrating and i feel i just got cheated paying for iMovie 11 when it cant even do a simple job. Please help me resolve this. Thank you!

Hi
This is not easy in iMovie'08 or 09 or 11 -
What and how did You record the extra audio ? With what tool ?
To be able to keep audio in sync should be recorded with a device with TimeCode. Else it will be near to impossibly. Or extremely tedious even if FinalCut is used.
I would use FinalCut and keep original audio on track 1 and 2 - and the extra on track 3 and 4. Then Show Wave-form - then see if they can match up to each others.
But doing this in iMovie - is nearly impossibly.
IF AUDIO HAS - TimeCode - and there are no drop outs on video or audio then You should be able to exchange original audio with the extra recorded one in iMovie and even move it frame by frame (1/30 sec or 1/25 sec) - in FinalCut audio can be moved much more exact eg 1/100 sec or within a frame
(my miniDisc recorder - is FAR away from exact enough for this)
Yours Bengt W

IMovie lags when editing video

Hey guys
So I just updated iMovie to iMovie '11 and no I have problems with editing videos. I had many clips and I imported them into the program and the whole thing was about 45 minutes long. I started editing and everything was absolutely fine, no problems at all, although it was that long. Now the movie is only 8(!!!) minutes long and now iMovie started lagging. I can still watch the video alright, but when I try to edit, I have to wait 3 secs till the curser moves and it also sometimes turns into the buisy sign ...
I dunno what to do, I need to get the video done by today so pleeeeeease help me!
Thanks!
Yana

How much free space is there on your hard drive?

HT201177 Colours blend and pixelate when editing video

I've been editing some video using both iMovie and Adobe CS6. When I go to view on whole screen the colours tend to bleed and you can see the pixelations. I have a 27" iMac with 12 Gig Ram and I have imported the video from a full HD camera at the optimum setting. Am I doing something wrong or do I have a problem?

One possible idea...
Have you blown the dust out lately?...
Get Temperature Monitor to see if it's heat related...
http://www.macupdate.com/info.php/id/12381/temperature-monitor
iStat Menus...
http://bjango.com/mac/istatmenus/
And/or iStat Pro...
http://www.islayer.com/apps/istatpro/

Crashes, graphics glitches, and more crashes when editing video clips

Can't for the life of me figure out why PE keeps crashing on me, so I'm here for help.
My system consists of a i7-970 hexacore, 6GB ram, 1x 500GB os drive, 3x500gb raid 0 drives (this is where my video clips are stored), 2x GeForce GTX460 video cards.
OS is Windows 7 Profressional 64 bit.
The video files I work with are generally in the 50-200GB size.
A little background - the videos that I am working with are recordings from Battlefield Bad Company 2 that I have recorded with some capture software called Dxtory.
I record at 1920x1080 at 60 FPS to avi files. The avi files are using the "xtor" codec (Dxtory's own codec)
[ISFT] DxtoryCore ver2.0.0.101
[ISRC] Video:YUV420 Audio:Speakers (Realtek High Definition Audio)
Audio is PCM 192000Hz recorded in stereo.
Let me start by saying I have not had trouble with this before until I started recording the videos at 60 FPS. 30 FPS worked ok (some crashes here and there, but they were bearable), but the frequent crashes started happening when I started working with the 60 FPS videos, done mainly so I could play around with slowing the clips down, etc.
Sometimes I can open and edit clips just fine.
Recently, a project that I'm working on is crashing when I try putting two different clips from different files together on the time line. I managed to get it to work once, and saved the project after that. Then, PE crashed randomly and when trying to reopen the project, it just crashes and won't let me get any further.
I should mention the graphics glitches as well - occasionally (especially when previewing video clips before adding them to the timeline) after I close the preview window, the graphics in PE will glitch out, causing random lines to appear in certain areas, graphics to stack on top of eachother and freeze up, and sometimes I can click on the "play" button in the main project window and hear everything start playing, but the graphics are completely screwed up to the point where I can't view the video or hit the pause button.
All of my computer hardware is fine, all drivers, and PE, are up to date.
Can someone please help me figure out what is going on? I'll be happy to provide any more information that might help out.

The most likely issue is the codec that your program is using the create your video. It's apparently not compatible with Premiere Elements.
This often happens also when people try to record their on-screen video with FRAPS.
You'll see lots of discussions on this issue in the Premiere Pro forum. However, it's even more pronounced in Premiere Elements, which is designed to work almost exclusively with camcorder video.
Some video programs are a little more versatile with this type of video. Some people have found Corell's Video Studio better at handling these non-traditonal formats.
But I did a Google search on Dxtory editing and couldn't find any information on it.
Sorry I can't offer a solution. But I can pretty much assure you that Premiere Elements isn't it. sorry.

Captivate Crashing when editing video demo

I have been having a lot of issues with Captivate crashing when I'm editing video demos. When I try to save, the save progress bar will get to 'thumbnails' and then freeze up. I have to close and restart the project and lose all information that has not been saved. I try to save after every thing just to be sure, but this is still very frustrating.
Does anyone else have issues with this?
The videos I'm working with are about 6 minutes long. I've trimmed a lot of information out in an attempt to make it a shorter video. It seems that after so many 'trims', Captivate doesn't function very well. I'm assuming a work around would be to just make shorter videos, however, if anyone else has an issue such as this I was wondering what your work around was.
Thanks

You left out one important number: how much free space left on your hard drive?

After editing video, why did my changes disappear?

After editing video footage in FCP X, why do my changes, as well as, footage, words, transitions
disappear sometimes? AutoSave is on.

Auto save is always on. first what is your version of FCPX ?

After Effects CC 2014 only using 30% of CPU when rendering

I've scoured the internet for details but there's surprisingly little help when it comes to After Effects and performance.
Basically, I built a new workstation awhile ago with the hopes of really speeding up my video editing as I was starting to do a lot more. Here are the specs:
Core i7-4930k
32 GB RAM @ 1600MHz
Stock GeForce 780
Samsung 840 EVO 500GB OS drive
Crucial 240 GB SSD for Scratch Disk
3TB WD Red for Mass Storage
Windows 8.1
I must say that I've been quite disappointed so far with the setup when it comes to the CPU, especially After Effects. I would think the 6 core would greatly outperform my old 4 core, but I've found hardly any performance improvements, and in fact have seen it perform worse in a number of situations. And I think the issue is that somehow, After Effects is not fully using the CPU. Whenever rendering or previewing, all 6 physical cores as well as the 6 logical cores hover around 30% usage. Never any more. And yet, the comp it's rendering could be chugging away at maybe 2-3 frames per second, and it could clearly go faster with more CPU usage. Heat isn't throttling anything as all the cores are still at a very cool 48-50 C, and this is just pretty basic air cooling. It's definitely not being pushed that much.
I don't think it's the CPU itself as Maya gladly takes up as much CPU as possible and my render times on that have improved dramatically. After Effects however (and Premiere when not using GPU effects) can be quite slow. It's especially frustrating when other older, clearly slower computers end up rendering my comps faster.
Is there any info at all out there as to why this is? Any advice on troubleshooting? I've tried many things and can't think of anything short of maybe it being an OS issue and having to reformat (which would be quite a pain).
Any and all help would be greatly appreciated.

Martin, I don't know if there's anything Todd or I can say to change your opinions. We try to represent how After Effects works, and why the After Effects team chose to make it work that way, in a way that all users can understand so you can get back to creative work as fast as possible.
What tends to rub us the wrong way are your assertions and accusations about that. For example:
If you guys spent less time listening to the voices you want to hear, and more time on the 'yes some time difficult to hear' but nether the less valid concerns of experienced users, you would have addressed this fundermental flaw years ago.
We gave constructive feedback whilst part of that program and none of it was ever addressed. There seemed to be a weird attitude to any criticism which didn't fit the given narrative.
I'm sure you probably see it differently and it is great to hear it is being addressed.
That last statement is quite true, your perspective is your own. From our perspective, your statements do not reflect how the After Effects team interacts with After Effects users, either the users in our prerelease program or users who are not a part of that program. Fact is that we spend a lot of time talking with users: in forums, at user groups, on the phone, via email, and by visiting work sites. We take notes and discuss as a group what we learned, and use that feedback to guide the future development of After Effects. It's not all sunshine and roses, we hear plenty of negative things about After Effects. This is important as it helps us understand how to make After Effects better. At the same time, we're also cognizant that we have many different types of users with different needs and workflows, and we can't make all users happy all of the time.
What I think is not visible to you, or to most After Effects users, is how we prioritize the development of After Effects. There are many factors that go into that, starting with input from users but also including (in no particular order) fixing bugs and general improvements, industry trends, changes in hardware and software environments, maintaining a large and complex codebase (some of which is shared with other Adobe applications), maintaining interoperability with other applications (both Adobe and non-Adobe), and ultimately delivering a product that people want to use. To see how all that comes together is harder to communicate; really, you would need to sit down with us and watch us work.
The more relevant point here, Martin, is that you appear to disagree with how much priority we've given to performance improvements in After Effects. You indicate that you would prefer that we had started on this work a long time ago.
All work we do in After Effects comes at the cost of work we don't do. I'm confident that you're like me in that you have a long list of enhancements, beyond performance, that you'd like to see in After Effects. But the After Effects team is relatively small for such a complex application, and the scope of the performance-related improvements we are currently making is huge, a massive re-wiring of the application. Doing this work in a reasonable amount of time, with the number of people that we have, with as few moving parts as possible, is tricky. In that context I hope you can see that it has not been easy for us to justify putting the entire team on this effort and doing no other work, no creative features, no workflow improvements, no fixing of long-standing bugs and gotchas, etc. What is important is that this work is now in progress.
On that note, I need to temper any expectations that you may be building based on this conversation. We're laying the groundwork for the future of After Effects, and the first iteration of performance improvements that you see next year might not meet your expectations if we hype it up too much. We plan to share specific detail when we get closer to a public release, but suffice that what we are doing now is absolutely necessary for even better things to come later.
We understand your frustrations, that you'd like After Effects to be faster. We're working on it, and we appreciate your patience. We also appreciate constructive comments and questions.

Why does Lightroom 4.3 use very high cpu when waiting for user to click OK?

I saved metadata for 52 photos.
Lightroom 4.3 couldn't save metadata for 2 of the photos and opened a window to tell me so. (It had no problem saving metadata on second attempt.)
While it waited for my response and wasn't doing any work, it was using over 50% of my CPU.
Why?
Windows 7 is 32-bit Professional.
Processor: Intel Core i5 750 Processor 2.66 GHz
Here's my system info as reported by Lightroom.
Lightroom version: 4.3 [865747]
Operating system: Windows 7 Business Edition
Version: 6.1 [7601]
Application architecture: x86
System architecture: x86
Logical processor count: 4
Processor speed: 2.7 GHz
Built-in memory: 3579.4 MB
Real memory available to Lightroom: 716.8 MB
Real memory used by Lightroom: 710.9 MB (99.1%)
Virtual memory used by Lightroom: 847.9 MB
Memory cache size: 2.0 MB
Maximum thread count used by Camera Raw: 4
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1080
Application folder: C:\Program Files\Adobe\Adobe Photoshop Lightroom 4.3
Library Path: D:\Users\Calvin\Pictures\My Lightroom\lightroom\lightroom4\lightroom4.lrcat
Settings Folder: C:\Users\Calvin\AppData\Roaming\Adobe\Lightroom
Adapter #1: Vendor : 10de
    Device : 640
    Subsystem : c9593842
    Revision : a1
    Video Memory : 1007
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: Uninitialized
Direct2DEnabled: false
GL_ALPHA_BITS: 0
GL_BLUE_BITS: 8
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 2048
GL_MAX_TEXTURE_SIZE: 8192
GL_MAX_TEXTURE_UNITS: 4
GL_MAX_VIEWPORT_DIMS: 8192,8192
GL_RED_BITS: 8
GL_RENDERER: GeForce 9500 GT/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 3.30 NVIDIA via Cg compiler
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 3.3.0
OGLEnabled: true
OGLPresent: true
GL_EXTENSIONS: GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_blend_func_extended GL_ARB_clear_buffer_object GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_objects GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_debug GL_KTX_buffer_region GL_NV_blend_square GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_ES1_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_buffer_load GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_expand_normal GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control

I don't think so.
I have enough experience with LR to know what to expect for various activities.
Previews for all photos had been rendered long before I initiated the Save Metadata.
Metadata for 50 of the 52 files had already been written.
The high cpu had gone on for at least 5 minutes.   I switched to another app imediately after initiating the Save Metadata for the 52 files and only went back to LR when I heard my CPU fan running for a long time.
When I got back to LR, I saw the "Could not save metadata" window. I clicked "Show in Library" and OK. As soon as I did that, CPU usage went back to normal.
I've experienced the exact same scenario, where LR can't save metadata for all photos and I've never had LR get stuck consuming a very large amount of CPU.
As a test, I selected 118 other photos, changed metadata for all of them and then selected all and saved metadata. LR took about 20 seconds to save metadata for all 118 and LR CPU usage never went above 17%. The difference is that LR did not show the "Could not save metadata" window.

Problems when editing videos in IOS 8.02

I recorded a slowmotion video with a moving train the other day; but when I wanted to edit it, I couldn't like I used to. I wanted to cut the first seconds out because of shaking image, but when I tried doing that, it also cut the ending; I couldn't pull it all the way to the end and play it. I have an iPhone 6 Plus, and don't know if it is a problem with the phone or IOS 8.02.

contacts, photos and messages - yes (in fact I am able to send and receive messages without issue)
music & apps - no
The problem is when I try to access the iphone using iTunes on my pc, I am unable to drag and drop music or apps onto the iphone, and when I click on the iphone icon, I am greeted with the "welcome to your new iphone" screen, only giving me the option of registering it as a new iphone, or restoring from a backup!

Firefox uses too much CPU when displaying flash sites

When I have a site with flash and/or java open, firefox uses minimum 40% of my CPU power, even when I'm doing nothing, when firefox is idle and waiting for input.
P.S. This could be a recent issue, probably related to the newest version of firefox, however I haven't tried downgrading it because I don't have the old version package in my cache. (cleaned it a while ago)

Dheart wrote:
signor_rossi wrote:
schivmeister wrote:this is a flash issue
Of course it is, but there isn't much we can do about it, isn't it? Therefore I suggested firefox3, to alleviate things a little (it does it for me). Flash doesn't even work at all for me in Opera, I only get a grey window where the video should be.
Bye, signor_rossi.
The newest version of flash Plugin only works with Opera 9.5 beta. If you want to use flash with the stable Opera find an older version of the flash plug in.
Thanks for the hint, will keep that in mind in the case I will switch to Opera again (used it for a while because Firefox2 scrolling was bad, with 3 it is much better). Besides, there is a new flash version in the repos.
Bye, signor_rossi.

Audio Quality when Editing Video

Hello!
In my currenty project I have 2 video tracks and one separate audio track that I imported from garageband (via itunes). Right now, I'm trying to switch between the two video files, by spliting the video in the right chunks, and changing the opacity so only one or the other is showing (hopefully this makes sense).
When I split the video file or edit it, the audio file gets very fuzzy. In fact there's this weird sound in the background, that almost sounds like a record spinning around or something like that.
It's not in the itunes/garageband file, so iMovie is adding it or making it somehow.
Has anyone else experienced this?? And is there a solution?
Thank you!
-Nick

Hey there guys, have you found a solution to the problem? I am experiencing the same issue, not sure what is causeing this.. maybe some conflict.? what solved your issue? I have a Iphone 4S, and I would like to know if its a Firmware Issue, hardware Issue or something else?
thanks guys

Firefox 3.6.12 is using lots of CPU when shutting down, and doesn't ever die

It may have something to do with changing settings, but on the closing phase of restarting Firefox 3.6.12, one of my two CPUs get's used, CPU running at about 50% to 60%. It doesn't seem to stop until I kill it from task manager. I haven't been able to wait more than 10 minutes for it.

@cor-el
Thanks for clearing up my misunderstanding. As i understood now it is in fact only a "DOM storage data" topic.
Quote from betterprivacy:
''"Disabling DOM storage (instead of deleting the file on shutdown) causes a website script to throw an exception. This means that the execution of the script is aborted immediately, not just the DOM storage instruction is ignored. None of the following script instructions would be executed, even if those instructions have nothing to do with DOM storage. That is the reason why -with DOM storage disabled- sites like CNN.com will cease to play videos."''

IMovie using 200-300% CPU when editing video. Why?

Similar Messages

Maybe you are looking for