Jump to content

Andrew Reid

Administrators
  • Posts

    15,439
  • Joined

  • Last visited

Everything posted by Andrew Reid

  1. Go to preferences and select 4 cores. It will now do 4 clips at once instead of waiting for 1 clip to finish and starting on the next. 2009 iMac is 6 years old now so don't expect miracles though. H.265 is many many many more times CPU intensive than exporting ProRes in FCPX. FCPX does not support H.265 yet.
  2. It's still there. Please can you guys upload profile pic to help brighten the place up a bit?
  3. EditReady blog on why it's so fast. http://www.divergentmedia.com/blog/editreadyperformance/ So how is FCPX even faster for ProRes... hardware ProRes encoding on the GPU?
  4. Very interesting info, thanks joema. I was transcoding 4K MJPEG -> ProRes though, not H.264. But still felt there should have been a big difference to the MBP. No longer in any rush to upgrade to a Mac Pro! As for I/O, wasn't a bottleneck... did the test on the internal SSD.
  5. Last February I made the first EOSHD video quality charts 2014. This was an at-a-glance chart of image quality delivered by every camera I can possibly think. This year I've decided only to include the cameras I've direct experience of shooting with in my own filmmaking projects, with only a few exceptions such as the Sony F35 and Canon C300. I've also removed cameras that have been superseded by very similar ones (such as the GH2 by the G6, sharing the same sensor). Here are the results... Read the full article
  6. A story of the $1999 SLR Magic cinema lens versus a $7999 Cooke S4i Mini. Read the full article
  7. Just tried a 2014 Mac Pro (4 core) with Edit Ready and FCPX. Virtually zero improvement in transcoding speed compared to a 2.3ghz i7 Macbook Pro Retina (Nvidia 750M 2GB). Really surprised at that. Edit Ready took 2.03 to transcode 1 min of 4K 1D C footage on the Mac Pro compared to 2.08 on the Macbook! FCPX transcoding to 4K ProRes (optimised media) wasn't really much either. Same story with the 5K iMac, not much improvement. How can that be?
  8. Ah I see, press X to select entire clip range before dragging. That does it. Getting used to it... it's not bad actually.
  9. When I drag a clip onto the timeline, is there a way to stop accidentally dragging the in / out points over the clip instead? It's infuriating.
  10. ​And another result... EditReady was slower on my Hackintosh, 670 GTX 4GB, arguably more powerful hardware than what's in my 'proper' Macs. The GTX 750 and 775 2GB in my Macbook and iMac seem to do a good job.
  11. FCPX vs Premiere is the new PC vs Mac debate isn't it!?
  12. Results for 4GB 1 min 1D C 4K... EditReady - 2m18 (ProRes LT) FCPX - 1m05 (ProRes 422) However the EditReady file is 2.77GB vs 3.6GB for the FCPX one and it looks slightly nicer, even with the lower bitrate (350Mbit/s vs 450Mbit/s) I bought it. I like it.
  13. EditReady is interesting. Faster than all but FCPX it seems. But with the advantage of being able to select the transcoding codec, naturally
  14. With the clip placing tool the magnetic timeline acts like a normal one. Much more sensible now. I'll give it a go. I need to place clips perfectly in sync to an audio track and the magnetic timeline would knock everything out.
  15. Yes, it works for 4K. Tried it. Sorry Nick I missed your suggestion. It ended up being suggested on Twitter and I tried it from then on. Shame to lose LT but 422 will do me... better than silly old MJPEG anyway!! And 3x faster than Premiere... can't sniff at that. Going to save me HOURS.
  16. I don't use FCPX as my editor, and why should I use it to transcode media when we have Compressor for that? The answer may surprise you... Read the full article
  17. The plan is to use the speedy FCPX transcoding and then import the ProRes into Premiere which is my favoured editing software. PS - It's not just the timeline in FCPX I don't like
  18. By the way your RX10 clip seems much more compressed in the YouTube video than the D5300 clip, what did you do to it? Flush it down the toilet?
  19. Hacked D5200... Is it just the bitrate change or have they progressed much further since I last looked at it?
  20. Yes exFAT is needed for files larger than 4GB. Weird that the NX1 doesn't format it that way in-camera or that it doesn't span to multiple files! Still, 7 and a half mins of 4K per 4GB isn't bad. On the KineMINI in Cinema DNG that is about 4 seconds
  21. So I tried FCPX in the end and glad I did because it transcodes MJPEG 4K at real-time speed (24fps) to ProRes (various flavours) on my iMac and the quality is perfect. Some quite amazing magic sauce going on with this. Resolve is giving me 7fps and FCPX can even edit / playback MJPEG 4K from the 1D C flawlessly on my Macbook Pro Retina 15" whereas Premiere can't (and has the banding). I won't yet be switching NLE but going to explore Compressor as my transcoding app for the 1D C. The FCPX interface has NO batch export for clips, you can only do them one at a time or bunch them all into one clip on a timeline export... pretty stupid!!
  22. ​Good choice. I'll leave the art part up to you rather than lecture on that like certain other members like to do...
  23. Could do with going for 30" for 4K. Any good ones?
  24. ​Good to see support trickling out yet further. What spec PC do you use?
×
×
  • Create New...