Search the Community
Showing results for tags 'performance'.
Found 3 results
Although the just announced Mac minis don't seem to be out in the wild yet, the geekbench developers have written an interesting article estimating it's likely performance: http://www.primatelabs.com/blog/2014/10/estimating-mac-mini-performance/ Although single-core performance is slightly improved over the 2012 model, as many predicted multi-core performance takes a massive hit owing to the lack of a quad-core configuration in the new lineup. There's no discussion of what difference Intel Iris (in the mid and top level 2014 model) will have over the 2012 model's Intel HD 4000 though. So which matters more to video editors, multi-core, or better graphics performance? (or, something else, like super fast storage, a thunderbolt RAID 0 or something?) Anyone have any thoughts on how say, the mid-tier 2014 Mac mini with Intel Iris would compare to a second-hand or refurbed quad-core model from 2012 (which would only have Intel HD 4000), for running FCPX? I'm talking about short, single-cam personal projects in FCPX (ie no deadlines, I can make a cup of tea while it renders), 1080p AVCHD and Prores 422, occasional processor-intensive effects like Neat Video NR or Optical Flow, I'm not needing or expecting anything screaming fast.
Hello, Everyone. I am debating whether to jump into the Canon 5D Mark III Raw video capture world, but as I have been researching the topic and equipment further I am now wondering what kind of real world computer performance in necessary in order to edit Raw video? I have a Mac Pro (2009) with 16gb RAM and four internal HDs (500GB for OS and three 2TB for storage). Until now I've only edited ProRes in Final Cut 7 on my machine, and I've never had a performance problem. Moving into Raw shooting, however, I wondering if this will change my computer performance needs dramatically. I'm planning on editing either in ProRes or Cineform in Final Cut 7, but I wasn't sure if the higher quality files and larger sizes of shooting Raw would force me to change my setup dramatically? I will most likely need an external backup system to handle the larger storage needs, but I was wondering if investing in a RAID system is necessary? I was also wondering is there were any dramatic performance need difference between editing with ProRes vs. Cineform? Does one require more power to run smoothly? I was also wondering where my money would be better invested in updates? If I want better performance would it be smarter to add more RAM? Or would I be better served by buying a RAID system? Any input on how others shooting with Raw feel is greatly appreciated. Please don't hesitate to add comments and insights beyond the scope of my initial questions here. Thanks so much. I look forward to your responses.
For some time there has been widespread problems with Youtube buffering performance. This affects anyone wanting to distribute or view video content via Youtube. I did some testing, and here are my results. Symptom: A consistent 24x7 lack of complete buffering on certain videos, independent of network speed or browser. I've tested Chrome 27.0.1453.110, FF 21.0, and IE 10.0.9200.16576 on 64-bit Windows 7 Home Premium SP1, Flash 11.7.700.202. I have Comcast Extreme 105, which on speedtest.net consistently produces 115 megabit/sec down, 21 megabit/sec up. My ping is 19 mS with 1mS jitter. The behavior is incomplete or halting buffering of some videos in the Youtube client. It happens with some videos at some resolutions, but not others. In general 480p and below FLV videos buffer slowly and incompletely. Some 720p and above MP4 videos buffer quickly and completely; others do not. The difference in network data rate is about 150-200k bits/sec for the slow case vs. 70 megabits/sec for the fast case. It is obviously a Youtube client code issue, not a pure network or server-side issue. If you use the FireFox extension DownloadHelper (http://www.downloadhelper.net/) it bypasses the buffering problem on 720p and 1080p MP4 videos, despite using the same PC, OS version, network, browser, flash, and time of day. Interestingly it does not help on 480 and below FLV videos -- they download or buffer slowly. You can monitor network speed with Windows Perfmon -- Control Panel>Administrative Tools>Performance Monitor. Select "network interface", bytes received/sec and bytes sent/sec. Perfmon clearly shows that the Youtube client is throttling the download under some conditions. For each performance "counter" at the bottom, you may need to right-click and pick properties>data>scale, and select a scale factor so the graphs fits vertically on the screen. Note if you right-click on the graph background and select properties>Appearance>color>graph background, select light grey, you can then highlight the specific graph line by pressing CTRL-H. However different videos exhibit different behavior. This video currently (6-7-13, 10:30 AM CDT) shows the throttling behavior in all browsers at all resolutions, 24x7: https://www.youtube.com/watch?feature=player_embedded&v=dQ51rE_ZUgo However THIS video shows throttling only at 480 and below -- at 720 and above there's no throttling and it buffers completely and quickly -- IF played on Youtube. If played embedded on this forum, buffering remains slow: https://www.youtube.com/watch?v=Alm6D_6sd8k&list=PLC10321FC136BF7C1 480 and below are typically FLV files, 720 and above are usually MP4 files. Whether using the Youtube interface or DownloadHelper, I cannot buffer or download FLV videos quickly. 720 MP4 and above can be downloaded quickly with DownloadHelper, and (sometimes) the Youtube client will buffer them quickly but usually not. While there may be issues with time of day, ISP traffic shaping and local net capacity, this behavior seems independent of that. Chrome HTML5 also makes no difference. I speculate Youtube has implemented client-side code which limits buffering in order to reduce overall load on their servers. In Perfmon you can see bursts of activity if you scrub forward, but buffering quickly stops. Unfortunately it's not working consistently. The difference between the slow case and fast case is gigantic. When the throttling code mis-predicts the needed buffer prefetch, it interferes with viewing videos, especially at 720 and above. I posted the above symptoms on a Google help forum, but I doubt they'll respond.