58 Seconds for ProRes 422 - Clip Size 784MB.50 Seconds for ProRes 422 LT - Clip Size: 432MB. Here are my results as I encoded the clip into 3 different flavors of ProRes in both EditReady and Media Encoder: The original clip was full HD, and the original file size was 274MB. I used a single 57 second h.264 clip shot on my Canon 60D to conduct my test. However, once I started using EditReady (and comparing it to Adobe Media Encoder, which is what I normally use for all of my encoding), what I found was pretty impressive. Unfortunately, EditReady is a Mac-only app, so in order to test its speed and overall performance, I had to use the Macbook.Ĭoming into the conversion process, I had been expecting all of my tests to be painfully slow because, frankly, the Macbook is on its last leg. Suffice it to say, I would NEVER choose to do transcoding work on the Macbook unless it was absolutely necessary. Back in the day, the Macbook was no slouch in terms of performance, but time has not been kind to it, and the performance these days is pretty underwhelming. I own two computers, a mid 2010 Macbook Pro with a dual core 2.66GHz i7 processor and 8GB of RAM, and a custom-built editing PC that is insanely beefy in terms of specs and raw power. But, before we do, a primer on the computer that I used to test the software. That is how I have been limping mine along.Now let's talk about performance. Try to find it in device manager right after it starts up and disable it. I think what windows update is doing is trying to update your intel graphics card. Mine was crashing after a few min as well. I would have never bought this hardware if I wasn't continuously reassured Windows would function normally. It has NEVER worked right with ANY version of Windows. I have a 8 page blog I am writing on how these machines cannot be used for Windows functions. It is still real half *** and a huge disappointment. It seems my graphics is running in 16 bit mode (shading is off). After getting bootcamp to fully installed on my computer, I ran the apple software update application and it actually updated my Windows bootcamp to 6 anyways. I feel like Windows update should find all the drivers though (or run compatibility mode). They want you to create a bootable USB from Yosemite/Bootcamp6. I had to start my install with 5.1 something because I don't have working version of OSX on my machine at all. I have spent about 10 hours so far trying to make this computer work with Windows 10 now. If anybody on here has a work around to make this work, please let me know. It has always been a struggle trying to run Windows on this Mac, I will never do it again. I had to jump through similar hoops of fire for Windows 8.1 as well regarding video driver installation. I can't believe how bad the driver support is for Windows on this machine. I figured I could at least use the computer without audio, but then I found out whenever the screen blanks/sleep mode, upon waking the computer I get the zig zag too and the computer has to be force restarted! I even downloaded the driver update software directly from Intel and tried. The computer just starts bootlooping after this though no matter what I do. It seems whenever I try to update that driver (which is disabled?) it looks like it is trying to install something audio related. I believe the audio is related to the intel graphics somehow. Upon running apple software update, it was then finally updated to bootcamp 6! That really didn't fix anything though.Īfter all of that, I still have no audio. This allowed me to fully install the bootcamp assistant software. I removed the intel graphics card files, the Nvidia files, mainly. I had to remove any program the computer was hanging up on/rebooting/locking up. To install the rest of the software (mainly the bootcamp assistant software, since it won't let you install as "stand alone".), I had to manipulate the bootcamp installaton source folder. I hooked up the computer via hardwire to the internet, and windows update seemed to update my Nvidia graphics card properly so my started working for the most part. I created restore points before making any major driver change and that has been working to go back after I crash something. I ended up having to re-install windows several times. Booting into safe mode (SHIFT+F8 worked for me) yielded no results in repairing. I was running into the screen blacking out issue you had mentioned. The bootcamp driver support would crash the video upon installing the Nvida drivers as this was the first or second thing it does. I was hoping the most drivers would work, at least for network cards so I could update them to the latest versions via windows update. On mine, I wasn't able to download bootcamp 6 as I don't even have OSX on my machine at all, so I had to use an older version of bootcamp driver support initially. I have a macbook pro mid-2012 with Nvida graphics option.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |