FCP 7 seems to drop frames in Mountain Lion?

I understand there are compatibility problems with Mountain Lion and FCP 7. I edit independent feature films and really tried to work with FCPX but gave up in frustration -- it doesn't think like an editor......... or at least someone who has been editing for over twenty years. Is there a way to fool FCP 7 or change a setting so it doesn't drop frames? I'm also using a Lacie thunderbolt drive (and tried the USB 3 port as well) and it's still dropping frames. So I don't think it's the Lacie external drive. Anyone have a solution?
Bryan

well I think you're out of luck. As I said, there were a bunch of posts complaining about this a while ago. Don't think I ever saw a solution. The only thing you can do is get some sort of external monitoring device like an aja or blackmagic and connect a video monitor.
I wonder whether connecting another computer display via thunderbolt would help? Unfortunately, don't expect any help from Apple. As you well know, they ain't supporting fcp7 anymore.
I've just installed the avid media composer demo (that's why I've done a mountain lion install) cause I know I'm going to have to make that move sooner or later.
Good luck.

Similar Messages

Slow video rendering etc. in FCP/Premiere/etc. Radeon problem with Mountain Lion?

My mid 2010 Mac Pro was working fine until I installed Mountain Lion. My colleague has the exact same setup as I do, but has SnowLeopard and no issues. Mountain Lion may or may not be the problem.
Now, all video takes a really long time to render or encode or export, especially .mov. Testing on FCP, Premiere, Compressor, and Media Encoder, Quicktime 7, results in really long times for anything involving video processing.
All other video works fine; playback capture, etc. Just processing of video takes a really long time.
I thought it might be an issue with the video card?
Mid 2010 Mac Pro
2x2.66 GHz 6-Core Intel Xeon
12 GB 1333 MHz DDR3 ECC
ATI Radeon HD 5770 1024 MB
OSX 10.8.2
I may have to resort to a clean install of Snow Leopard and just go back to when things worked...

Take a look at this article, originally written for MacBook owners. There are some things in 10.7 and 10.8 that do not seem to upgrade happily -- they leave some tasks eating up CPU cycles when they should not be.
Runaway applications can shorten battery runtime, affect performance, and increase heat and fan activity

IPhoto '09 seems to be incompatible with Mountain Lion

Hi
I am a long-standing major fan of Apple computers. This is because they allow me to work easily with images. I am an art historian and museum curator. My professional life is entirely about images ... or rather about images attached to data.
For years I have been accumulating and categorising images using iPhoto. It has been the most wonderful tool. A clear, simple interface. The capacity to attach searchable free-text metadata. Wow, that simple feature makes this the most powerful application of any I have ever used.
The problems started for me when iPhoto '11 first came out. This removed the capacity to compare photos side by side in full screen mode, a brilliant, simple and obviously powerful feature. As a consequence I did not upgrade, but stuck with iPhoto '09 (8.1.2).
Now I discover that there seems to be a bug which means iPhoto '09 is not compatible with Mountain Lion. Whenever you go into Preferences the computer seizes up and has to be hard-booted. An Apple genius was unable to fix this for me. I've reinstalled the entire operating system to try and fix the problem, but it remains. I gathered from a discussion thread that it was simply an incompatibility with Mountain Lion.
As a consequence I have purchased iPhoto '11 (9.4.1) and Aperture, which I was advised by the Apple Genius would be much better than iPhoto. I have converted my several iPhoto libraries. But I just cannot get anything resembling the clean functionality of iPhoto '09. Everywhere I am cluttered up with gadgetry which I cannot remove. It just is no longer possible to view photos with their basic metadata in a clear and simple way.
The only way I can see forward is to downgrade to Lion, reinstall iPhoto '09, and live the rest of my life without ever upgrading to Mountain Lion.
Forgive the long rant. I am sure people will be irritated and say I should not be using an application designed for holiday snaps for professional purposes. But that is not how I see it. iPhoto is part of the fundamental suite of utilities which makes an Apple computer what it is. That means it ought not to be designed with a single purpose in mind. We are creative people. We use our machines as it suits us to use them. Apple became what it is because it understood that.
If anyone can point me in the direction of a image organiser which allows me to store photos with associated searchable free-text metadata, add dates of my own choosing to the images and to do this in a way which integrates with other applications as well as iPhoto, I'd be so very grateful.
Otherwise I think it's going to have to be the downgrade.
Or could this even be the moment come to abandon Apple? I'm due for a new machine. For the first time in 25 years and six Apple computers I'm going to be considering the competition. Any helpful suggestions would be very gratefully received.
Thanks.

Yes, that's it! You're brilliant. Thank you so, so much.
Just in case anyone else reads this having had the same problem, the answer is (as Terence says) to delete anything which might cause the computer to try to link to a MobileMe account. My iPhoto libraries had old MobileMe photo galleries which I hadn't bothered about in years. It seems these caused the iPhoto Preference pane to attempt to access MobileMe whenever I opened it. This of course it could not do because the service is defunct and so the computer simply beachballed. In order to remove the MobileMe galleries I found I could only do it if I first disconnected my wireless network. All MobileMe references are gone now (I hope) and everything seems to be working well.
Hugely grateful.
(Sorry clicked the wrong message for 'Answered my question')

WIFI DROPS OUT AFTER MOUNTAIN LION UPDATE

Since upgrade to mountain lion my wifi keeps dropping out after sleep i have ipad and that is ok.

Had the same problem and this worked for me:
Try deleting following two items:
~/Library/Preferences/com.apple.dock.plist
~/Library/Preferences/com.apple.dock.db
Make sure you take a screenshot of your current dock since deleting these files will reset your dock to default.
Now open terminal and do a sudo reboot w/ your password.
This solved the problem for me.

Replacement battery still dropping considerably on Mountain Lion.

Just replaced my battery on a late 2008 MacBook Pro with Mountain Lion and within 25 minutes went from 32% (when the Apple Genius Bar replaced it) to 8%. I have had the same issue like this already, with an Apple representative contacting me to try and figure it out. Why does it keep doing this? Has this happened to anybody else?
Thanks.

UPDATE: Charged the battery full last night and within 2 hours by battery life is at 40%.

Dropping frames in QT export from CS3

I just got CS3 for my PC and I was all excited about the new
feature that lets you export dynamic/actionscripted/MovieClip
content. I do animation targetted at TV, so everything needs to be
rendered to AVI or Quicktime, so I figured that this new feature
would let me use a dynamic camera symbol as I've always wanted to.
I've run into a problem, though: the export process seems to
drop frames! As far as I can tell, Flash is rendering and recording
the frames of the animation in real time (or perhaps just close to
real time). If the computer has any hiccups because of another
process demanding some processor time then the resulting quicktime
will have frozen bits where the renderer couldn't keep up.
You can see what I'm talking about by looking at the
quicktime and an AVI of the same scene here:
http://www.pinkandaint.com/flasherror/bad.mov
http://www.pinkandaint.com/flasherror/good.avi
To test this theory, I tried witching applications a bunch
during a render. Sure enough, there were long sections in the
resulting quicktime where the renderer missed frames. The quicktime
is the right length and number of frames -- it just repeated the
same frame over and over where it couldn't keep up.
That's not the only problem, though. When I look at the
exported quicktime file in either Quicktime Player or Premiere pro
(version 1.5) it reports a framerate significantly lower than in
the original FLA. In the file I'm looking at right now, the FLA's
framerate is listed as 29.97 but the MOV file reports a rate of
19.29 (which is, incidentally, different than the framerate I got
any other time I exported the same scene). In premiere, when I tell
it to interpret the footage as having 29.97 fps the clip gets
significantly shorter than it should be -- in this case 161 frames
rather than the 208 frames that it is in the FLA.
I'm pretty sure this is the same way that the various
SWF-to-video programs do things. I thought it was an interesting
kludge to use those external programs but I was sure Adobe would be
able to do something more elegant and sure-footed with this new
export feature. Couldn't they have somehow guaranteed that each
frame would get captured? It seems like they could have just
modified the Flash player to play with artificial time, where the
time to render each frame was always reported as 1/framerate.
Oh, and there's one more problem. The Quicktime renderer
seems to do something different about the order of execution of
actionscript or something. In the rendered quicktime movie the
first frame displays my camera symbol even though I explicitly made
it invisible with actionscript on the first frame of its timeline.
When displaying in the Flash player the first frame does _not_
display the camera symbol....
Has anyone else encountered these problems? If so, have you
figured out a workaround? I tried setting the framerate really low
(I was at 29.97, so I set it down to 10) but it still seemed to
miss frames.
-David

I can understand your frustration with this feature as it
tries to capture in real time what's being
compiled in the player - but your last line is a bit unfair:
"...it
> exemplifies the Flash team's disregard for animators in
favor of web developers."
Copy Motion and Copy Motion as AS3 are useful new additions
for animators. I will add however that I
myself have a list of animation oriented features I would
love to see added in flash but for now
have you checked out www.flashants.com and their SWF2Video
tool? It exports an SWF to AVI with
flawless results. Worth looking into if you have the need to
output any kind of flash content to video.
Chris Georgenes
Animator
http://www.mudbubble.com
http://www.keyframer.com
Adobe Community Expert
*\^^/*
(OO)
<---->
animator_geek wrote:
>
quote:
Originally posted by:
Newsgroup User
> [...]
> Turn off other applications. When recording, Flash uses
all of your system's
> available resources as much as possible, so any
interference of the system
> performance affects the result of the recording. We
recommend you exit other
> applications while exporting to a video.
>
>
> So you're telling me that Flash makes my computer
completely unusable while
> it's rendering? Sorry, I thought we left that kind of
limitation behind with
> DOS. Particularly for something like this, where the
rendering process should
> be
completely independent of real-time. The renderer should go
exactly
> as fast as it needs to in order to capture every frame.
Whether I set the
> frame rate to 1 or 1000 should make no difference in how
many frames are
> dropped in the rendering process.
No frames should ever be dropped I
> mean, what's going on here? You guys have access to the
actual source code of
> the renderer. Can't you adapt it so that it when it's
rendering non-real-time
> the SWF thinks that it's executing at exactly the frame
rate it desires? You
> could just set the renderer's "clock" to whenever the
render was started, then
> increment it 1/fps seconds every frame. The program
would never be the wiser.
> You could even let the timer run (or simulate it
somehow) for 1/fps seconds
> between rendering each frame, thereby handling any timer
events that need to be
> sent while the SWF is running.
>
> Clearly I'm not privy to the inner workings of the Flash
player but as a user
> there's a certain standard I expect, particularly when a
company touts this
> great new feature. It's supposed to work as advertised.
This feature clearly
> does not.
>
> Now I've been a software engineer in the past and I know
that sometimes
> workarounds have to be made but this is just too much.
To me as a user, it
> exemplifies the Flash team's disregard for animators in
favor of web developers.
>
> -David
>
>
quote:
Turn off audio. The audio in a Flash movie may also slow the
performance
> possibly causing dropped frames. Turn off the audio, if
you have many
> dropped frames in the first attempt. Other video editing
tools can be used
> to add the audio to the video after export.
>
> Reduce frame rate. If the movie dimension is a full size
NTSC video, 740 x
> 480, and frame rate is 30 fps, you are more likely to
have dropped frames.
> Reduce the fps of Flash movie increase the chance of
grabbing all the
> frames. Other video editing tools can be used to adjust
the frame rate of
> the video after export.
>
> Optimize your animation. Try to avoid a lot of screen
motion. The greater
> the area of change on the screen, the more likely
slowdown will occur. Also,
> if possible, restrict your use of transparency and alpha
channels as they
> too can cause poor performance.
>
> Use ActionScript 3. Animation created by ActionScript 2
and ActionScript 3
> are different in play back performance. Convert the
ActionScript in your
> animation to ActionScript 3 for optimized performance.
>
> Dimension settings in 2 places. The dimension settings
in Export Settings
> dialog sets the dimension of the SWF movie to be
captured. The Size settings
> in QuickTime Settings dialog sets the dimension of the
exported MOV files.
> If the SWF size is smaller than the exported MOV size,
the picture quality
> will be degraded; if it is larger than the exported MOV
file, you may have
> better picture quality. For best quality (and often
performance) these
> settings should match.
>
>
>
> "animator_geek" <[email protected]>
wrote in message
> news:[email protected]...
> >I just got CS3 for my PC and I was all excited about
the new feature that
> >lets
> > you export dynamic/actionscripted/MovieClip
content. I do animation
> > targetted
> > at TV, so everything needs to be rendered to AVI or
Quicktime, so I
> > figured
> > that this new feature would let me use a dynamic
camera symbol as I've
> > always
> > wanted to.
> >
> > I've run into a problem, though: the export process
seems to drop frames!
> > As
> > far as I can tell, Flash is rendering and recording
the frames of the
> > animation
> > in real time (or perhaps just close to real time).
If the computer has
> > any
> > hiccups because of another process demanding some
processor time then the
> > resulting quicktime will have frozen bits where the
renderer couldn't keep
> > up.
> >
> > You can see what I'm talking about by looking at
the quicktime and an AVI
> > of
> > the same scene here:
> >
http://www.pinkandaint.com/flasherror/bad.mov
> >
http://www.pinkandaint.com/flasherror/good.avi
> >
> > To test this theory, I tried witching applications
a bunch during a
> > render.
> > Sure enough, there were long sections in the
resulting quicktime where the
> > renderer missed frames. The quicktime is the right
length and number of
> > frames
> > -- it just repeated the same frame over and over
where it couldn't keep
> > up.
> >
> > That's not the only problem, though. When I look at
the exported
> > quicktime
> > file in either Quicktime Player or Premiere pro
(version 1.5) it reports a
> > framerate significantly lower than in the original
FLA. In the file I'm
> > looking at right now, the FLA's framerate is listed
as 29.97 but the MOV
> > file
> > reports a rate of 19.29 (which is, incidentally,
different than the
> > framerate I
> > got any other time I exported the same scene). In
premiere, when I tell
> > it to
> > interpret the footage as having 29.97 fps the clip
gets significantly
> > shorter
> > than it should be -- in this case 161 frames rather
than the 208 frames
> > that it
> > is in the FLA.
> >
> > I'm pretty sure this is the same way that the
various SWF-to-video
> > programs do
> > things. I thought it was an interesting kludge to
use those external
> > programs
> > but I was sure Adobe would be able to do something
more elegant and
> > sure-footed
> > with this new export feature. Couldn't they have
somehow guaranteed that
> > each
> > frame would get captured? It seems like they could
have just modified the
> > Flash player to play with artificial time, where
the time to render each
> > frame
> > was always reported as 1/framerate.
> >
> > Oh, and there's one more problem. The Quicktime
renderer seems to do
> > something different about the order of execution of
actionscript or
> > something.
> > In the rendered quicktime movie the first frame
displays my camera symbol
> > even
> > though I explicitly made it invisible with
actionscript on the first frame
> > of
> > its timeline. When displaying in the Flash player
the first frame does
> > _not_
> > display the camera symbol....
> >
> > Has anyone else encountered these problems? If so,
have you figured out a
> > workaround? I tried setting the framerate really
low (I was at 29.97, so
> > I set
> > it down to 10) but it still seemed to miss frames.
> >
> > -David
> >
>
>
>
>
>
>

Drop Frame media warning

Im capturing footage from a DVCAM deck using the normal DV-NTSC Easy Setup, however, after logging the clips and preparing a batch capture, I'm getting a Warning prompt:
WARNING: You are about to capture Drop Frame media from a device currently detecting or configured for Non-Drop Frame media. If you proceed, you may experience changes in logged in and out points, problems relinking media, or removal of master clip relationships.
I've capture DV footage forever, and I've never had problem like this. This production house works in Drop Frame and my FCP is set for Drop Frame. I've tried setting the deck and FCP capture preset to Non Drop Frame yet I still get the prompt and the capture error (the capture is actually stopped as dropped frames were detected). Any help?

Thanks for your help. I tried right clicking on the In point (which isn't set) on the Browser and It had a check mark for non-drop frame. So I tried right clickin on Media Start and I had the option of Drop Frame or Non Drop Frame. I chose Drop Frame, but I still didn't see any change in the capture process. I just went to the User Preferences and turned off Abort Capture with Dropped Frames and it's capturing alright now. I'm still very mystified by this because I shut down the computer and tried the Batch Capture and it captured just fine (without the non drop frame prompt), but when I put in a new tape the prompt came up again when trying to capture. A restart of the computer didn't help this time.

Dropped Frames & Firewire Busses - A Discussion

A side discussion broke out on this recent thread:
http://discussions.apple.com/thread.jspa?threadID=231733&tstart=0
and because this discussion is OT to the thread, I thought it might be helpful to start a new on-topic thread.
A number of FCP users have experienced dropped frames when capturing or outputting to tape while using a DV VCR/camcorder and a firewire drive for media on the same FW bus. There are many causes for dropped frames, but this discussion centers on the relationship between FW drives, DV devices, and using a single firewire bus.
Some say that having the DV device and the firewire media drive on the same bus can be a cause of dropped frames with some systems. Others disagree. I'm in the first camp, so I'll leave it to others to explain the other side.
I'm starting this thread to pick up where the side discussion on the thread linked above left off.
In response to Hughes Video:
If I'm reading your post correctly, my opinion is that your testing doesn't adequately address the real world situation. In practice, the FW port on the DV device is receiving data at 3.6MB/sec and buffering. Then it sends a data stream to the FW bus at about 12MB/sec, where is again buffered before being sent to the destination drive.
The benchmark test results you noted don't predict what happens in the real world when capturing a DV stream from a VCR/camcorder to a FW drive. To do that, you need to be able to report in a time graph what the throughput is for every 1/30 of a second while capturing.
I'm not sure that's what Adam Wilt has done, but he's told me that he's done thorough testing that proves the points he's made. I don't know what testing that entails.
I do know, as I posted in the other thread, that when those who are having dropped frames separate the DV device from the FW drive on separate busses, their problems resolve. I don't know the technical reason for that, but I theorize that it has to do with the data moving and buffering in both directions on the same bus simulteneously. If the bus speed is decreased when both devices are on the same bus (whether daisy-chained or on separate ports), I don't know. But I know the problem resolves when you separate them.

this begs the question though: how do users of an
imac or a mini get around the limitations of one
internal harddrive and one firewire bus?
zeb
They can't. iMac's are a consumer (and terribly sexy) computer. Make no mistake, if you are doing this for a living you need a PowerMac. Want less headaches with dropped frames and FW? Then take a closer look at better drives. G-Raid, Weibetech, and Granite Digital make the best out there, and invest in another FW 800 card for 'em. End of story.
Want to avoid dropped frames forever and ever with any video format? Forsake FW drives for fibre. SCSI is dying a slow but steady death IMHO.
Yeah, it all costs more, but you GET more (speed). Faster drives don't drop frames. Nothin' new there...
There is a tendancy with new users of NLE's to cut corners. Don't do that, because it results in unhappy NLEing.
Do I use FW drives? Of course I do, and use exclusively the above brands, I've clients who want to keep all media ever captured. (also a good idea) but I include in my invoices the cost of buying more FW drives to do the job. It works, I don't drop frames, have happy clients, and drop frame free system. I'm using the G-Raids for uncompressed storage and FW 800 Weibetech and Granite digital rigs for DV res storage. It works beautifully.
Jerry

Dropped frames and Spinning ball no matter what...

Hello,
After many months of flawless performance since the FCP 7 upgrade, FCP has decided to drop frames and give me the beach ball of death when editing anything: SD, HD and audio.
I am working off of an external G-Raid HD. I've connected via both FW800 and eSATA w/ the same above results.
Here's what I've done:
-Trashed Preferences
-Repaired permissions on external drive
-Run Disk Warrior on external drive
-Run Disk Warrior on boot drive
-Uninstalled FCP w/ FCS Remover and Re-installed FCP (not the whole suite just FCP)
-Moved project to internal drive
After all of the above I am still having the same problems.
Any insight?
thanks,
-B

Thanks for the response, I should have been more clear:
"Did you move both the project and the associated media files to a discrete, dedicated internal SATA drive, and also trashed all the render files?"
Yes, but I didn't trash the render files I'll do that. Unfortunately I don't think it will help because I forgot to mention that this happens w/ different projects on different external HDs.
"What are the sequence settings for that project?"
I've experienced this w/ a project editing XDCAM footage & a project editing DV footage. Both projects live on different external drives.
"And what does it consist of, ie video, stills, etc?"
Video, stills, music and text. No special treatments (drop shadow, movement, etc) a pretty basic timeline.
thanks,
-B

Final Cut Drops frames intermittently

Hi all-
okay, heres my situation- In different fcp projects, I get dropped frames on the playback of my DVPAL, 16:9 sequence. I have captured this video directly from my camera in that format, onto my fw800 drive that is my scratch disk for capture, render etc. The dropped frames are occuring on things like text, a little bit of rendered material, between rendered material and just a simple fade in of another clip, cross dissolves, particularly (but not always) between video and free frames. The most worrying incident was a dropped frame within just a slide show of freeze frames taken straight from my dv video.
Have tried updating to 5.1.4 from 5.1. (Also 5.1.2 a few weeks ago)
Reformatting the FW800 drive and starting again
actually replaceing the drive inside the fw800 chassis which has an oxford 922 chip
reformatting the internal hdd of the laptop and reinstalling mac osx and fcp from scratch
it is osx 10.4.8 with qt 7.1.3
Ran a benchmarking tool with xbench and found my fw800 drive to have much faster access than my fw400 on my desktop system. To prove speed of fw800 drive i have had it play 8 videos at once in a single fcp sequence without render and it did not stutter.
have ran Activity monitor and hardware test
sooooo.....why should I be getting these random dropped frames, and how can I stop them?

You don't have Norton or any FileSaver/AntiVirus program running? Could your drives be spinning down? Fighting with Spotlight for drive access?
Patrick

XSAN and FCP5 - Drops frames during capture

We are trying to capture video directly to an XSAN volume from FCP, and we get dropped frames usually within 5 minutes. Capturing to local HD works fine.
We've been dealing with these problems on and off ever since we got the XSAN. We've 'tuned' our fiber switch, reinstalled 10.4 and FCP and the XSAN software from scratch, ran all the updates to the latest stuff, and still no loving from the SAN environment.
I'm coming to the conclusion that this just doesn't work - does anyone else capture from a DV deck directly to a SAN volume successfully? If so, any hints or tips about what / where I might turn to get this working??
Thanks!

Derrick,
I have successfully captured from SDI with 8 Channels of Embedded Audio through the AJA I/O into the DV Codec (which ends up being 4.5 Mb/S) for more than an hour without a problem (directly to Xsan Volume).
If you are hitting a wall about 5 minutes everytime, it sounds like the cache in the controllers on the Xraid are filling up (1 Gig = 5 minutes of DV) and not writing to the drives properly.
I might sound far fetched, but just a though.
Kalagan

XF Utility drops frames in playback on my Mac Book Air

Hello,
I recently purchased a C300 and I am using a 2013 Mac Book Air to transfer media from the camera to external hard drives.
All works well except XF Utility drops frames when playing back footage from media that has been transferred to the laptops hard drive and also my external hard drives. I am using the latest version of XF Utility (1.3.0) and here are the tech specs for my Mac Book Air:
Processor 1.7 GHz Intel Core i7
Memory 8 GB 1600 MHz DDR3
Graphics Intel HD Graphics 5000 1024 MB
My iMac desktop from 2007 plays the footage back with no dropped frames, no hiccupps. I have a hard time beleiving that the latest the processor and graphics components on a 2013 MacBook Air cannot play back the footage without dropping frames. Anyone have any ideas what might be my problem?
Thank you.

Hello jdbrunet,
We are not aware that this is a common issue with the footage shot with the EOS C300. Since XF Utility seems to drop frames, the next thing to try would be another program to see if the footage drops frames there as well. This would give us an idea if the issue is solely within XF Utility or the computer as a whole.
Desktops are generally more stable with regards to video processing because most Mac systems that are built for editing have more RAM and would handle the flow of video better. You do not list the spec's for the iMac, so we cannot say this for certain.
If this is an urgent matter and you need assistance right away please Contact Us directly.
Did this answer your question? Please click the Accept as Solution button so that others may find the answer as well.

Dropping Frames 60Hz - 24Hz

Hello,
Since the ATV2 was released, I’ve really been struggling to work out why playback of films seems to drop frames. I don’t seem to notice frames been dropped on my ATV2 in my Bedroom Setup or when playing via iPad or Macbook. Only on my Main Room setup.
Here are all the things I’ve tried so far to resolve this issue.
1, Bi-Passed the Onkyo amp and connected the HDMI direct to TV.
2, Swapped the HDMI cable
3, Swapped my ATV2 unit with the bedroom one.
4, Disabled video upscaling on the Onkyo Amp
5, Messed around with the audio and video setting in ATV2 including the HDMI settings.
6, Connected to both 5Ghz and normal ‘N’ wifi on my network (Apple Airport Extreme)
All my films are ripped using Handbrake and are mainly HD, the dropped frames are in different locations each time I playback a scene so the dropped frames are not caused by the file conversion/ripping.
I’m 95% sure the frame drops are due to the HD films been in 23.97 Frames. My Amp shows that input from my ATV2 is 1280x720p at 60hz And the output to the TV is also 1280x720p at 60hz. The TV display info also confirms this.
I do find it strange that I’ve not noticed dropped frames on my Bedroom setup, maybe its because the screen is smaller. But that also is outputting at 60hz.
My Setup is as Followed.
Main Room:-
ATV2
Onkyo TX-NR807
Samsung 46” LE46C750
BedRoom:-
ATV2
Samsung 32” LCD
iTunes running from MacMini and Netgear NAS Storage over WiFi
iTunes and ATV2 running latest firmware.
Any feedback, help or advice is appreciated.
Thanks

Have a similar setup with an Onkyo receiver, and experienced the same issue with my ATV2.
More details can be found in this thread: https://discussions.apple.com/thread/2616205?start=0&tstart=0
Found a post on AVForums (http://www.avforums.com/forums/apple-tv/1436454-apple-tv-dropping-frames-60hz-no t-24hz.html)
Based on this, I chaned the setting for the HDMI input on my Receiver from "Custom" to "Direct" and the dropped frames disappeared.

HT1619 How do I disconnect an Apple remote from my MacBook Pro w/ Mountain Lion update?

My friend set up Apple TV while I was using my laptop in the same room and the remote is now connected to my laptop. I've looked at a bunch of different sites and forums trying to figure out how to disconnect it and it seems that with the new Mountain Lion operating system, there is no way to do this. PLEASE HELP it's driving me crazy because everytime he presses a buttom on the remote, it interferes with what I'm doing.

Sorry, but my late 2009 MacBook Pro running Mountain Lion continues to be be controlled by the ATV2 remote after disabling remotes in system preferences. Anyone else having the issue or has a solution?
Cheers!

Apple remote no longer works with mountain lion

The apple remote that was quite happily working with Lion no longer seems to be working with mountain lion.
I've checked with at least 3 other apple remotes I have and none of them seem to want to pair.
I've been able to pair them with another mac running Lion, but when going to the pair option under;
Preferences--> Security& Privacy --> General --> Advanced -> Pair
Pressing the menu and next for more than a minute gives me nothing on any of the remotes.
Anyone else having issues pairing with mountain lion?
*Note, each of the remotes quite happily will

I thought I had a problem pairing my aluminium Apple remote with EyeTV, but all turned out fine.
When I clicked Preferences --> Security & Privacy --> General --> Advanced --> Pair a message told to press the "Menu and Next" buttons until the remote paired with the computer. At first, I assumed this meant that I should press the two black buttons underneath the main, circular control, but nothing happened.
Then it struck me that the "Next" button might mean the right arrow on the main, circular control, so I held down this while holding the Menu button (the smaller button, below and to the left of the main, circular control), and the remote paired within a few seconds!
I don't have one of the older, white Apple remote controls to test this idea with, but something similar may also work with that remote.

FCP 7 seems to drop frames in Mountain Lion?

Similar Messages

Maybe you are looking for