Andrew Kimery
Forum Replies Created
-
Under the keys though and it’s going to be covered by one or both of your hands most of the time. Having it at the top makes the most sense, IMO.
-
On a related noted,
DNA Evidence Can Be Fabricated, Scientists Show
“You can just engineer a crime scene,” said Dan Frumkin, lead author of the paper, which has been published online by the journal Forensic Science International: Genetics. “Any biology undergraduate could perform this.”
The company offers a test that can tell the difference between real and engineered DNA, but how affordable and widespread the test is is another issue.
-
I’m sure for some it’s spec thing and for others it’s not. Just like some workflows are pretty hardware intensive and some are not. For me, the more RAM I have, just like the more storage I have, the more I seem to find ways to use it. Effortlessly hop between PPro, PS, and an AE RAM preview at full quality while exporting/transcoding via AME? Yes please.
I’m not up on the latest SSD but the ones I use for boot drives will hit about 420MB/s write and 480MB/s read according to the BM speed test utility. Certainly faster than the spinning HDDs they replaced but I don’t know how they compare to the SSD in the new MBP. Computer speeds are certainly getting faster, but the files we are working with are getting more intensive as well. Maybe 16gig is still a comfortable number for most today but will it be in a few years? I don’t really see a downside to allowing more than 16gig of RAM (other a battery life hit since Apple put a 25% smaller battery in the new MBPs).
Is 16gig the new 640k? 😉
-
There is a thread on this on a FCP X FB page and most of the responses seemed to be split between 16 is good enough and 16 is too low of a ceiling. From the article though, “I am sure there are some genuinely heavy users who will undoubtedly chew down more than 16GB of RAM, and this is by no means an attempt to minimize their concerns. Working with video and audio production is one area I can see this becoming a reality, but I don’t own Final Cut Pro or Logic Pro to demonstrate.”
Since we are throwing out fodder, the recommended amount of RAM for OS X (2gig), FCP X (8gig) and Photoshop (8gig). The least amount of RAM you can get on a 6-core nMP is 16gig and I don’t remember anyone saying “Man, why would I upgrade to 32 or 64 when it already ships with 16”? I already max out the 16gig in my MBP on a routine basis (and come close to the 24gig on my tower) so when the new mobile chips from Intel are available next year hopefully we’ll see a MBP refresh that has a higher RAM ceiling. Considering the RAM is no longer user replaceable I’m sure Apple wouldn’t mind the extra margins on the up-sell. 😉
-
[Charlie Austin] “SpeedScriber is, even in beta, amazingly good, and really inexpensive compared to the established services. Combined with Lumberyard it is an enormous timesaver. Ran a few interviews through it recently… blown away.”
Agreed. I think martin is heading up a ‘must have’ product when it comes out of beta.
-
[Brett Sherman] “Which doesn’t exist anymore. But that is an extremely limited application of what I’m talking about. It seems like those who work primarily on scripted pieces have trouble imagining anything outside of that.”
Avid recently signed an exclusive license with Nexidia’s for their speech tech so presumably ScriptSync and PhraseFind . ScriptSync is amazing for unscripted/documentary work as well (honestly I think it’s probably more of a boon for that than for scripted, but that’s just my opinion).
https://www.avid.com/press-room/2016/10/avid-acquires-exclusive-licensing-rights
SpeedScriber is a new (still in beta I think) cloud-based transcription service that is looking to eventually have ScriptSync-like features inside of PPro (among many other features).
And Microsoft’s R&D wing has a speech recognition system that can be as accurate as human transcribers.
Many companies seem to be making inroads down the path you are describing, though I wonder how much metadata current video codecs can handle? I.e. can scripts/transcripts be saved and used reliably as metadata inside of video clips like you are describing. For a ScriptSync-type situation (where the text and video are ‘married’ inside of the NLE) I think a lot of what you mentioned sounds feasible by just adjusting existing tech. And maybe instead of highlighting a Word doc you just highlight the text document from inside your NLE.
-
[Jeremy Garchow] “I have no idea what workflow you could not do on a 2016 MBP that you can do on a 2011 MBP.”
I could totally do it with a 2016 MBP. I could also do it with a mid-2015 MBP, save a bunch of money and then buy a 2017 (or 2018) MBP that will hopefully have more RAM, the next gen CPUs from Intel, and avoid the USB-C crossover mess as more USB-C devices will exist. The 2016 MBP feels like a ‘tweener’ machine to me and if I’m going to drop $3300-4100 on a laptop I need to feel more confident about that purchase than I currently do about the MBP.
[Jeremy Garchow] “I don’t think I have ever used my iPhone headphones on my laptop.”
Point is less about the headphones used and more about the adapter dance that is needed just to do something as basic wanting to charge your phone via your laptop and have the headphones (any headphones) plugged in at the same time.
-
[Bill Davis] “I’m not sure a problem that can be solved cheaply is really that big a problem.
“I dunno. Add that to the other pile of dongles for the MBP and I think the tally is up to around $250. ?
Speaking of dongles… “Apple’s New USB-C AV Multiport Adapter/Dongle Doesn’t Work”
https://fstoppers.com/gear/apples-new-usb-c-av-multiport-adapterdongle-doesnt-work-152877
-
[Bill Davis] “Fingers on the homerow – all it takes is a gentle drop of my right thumb to mouse around on the trackpad. Add the index finger for pinch moves. “
Might be the difference in hand size. On my 2011 MBP if my fingers are on home row it’s an uncomfortable reach to drop my right thumb onto the trackpad and ‘mouse around’ (even with sensitivity turned al the way up). I have to move my whole hand down.
-
I have no hands on time with it, but it seems like the difference between kinda useful and really useful is going to be in how open/flexible the API is. I know Apple has already issued some guidelines, but having third parties embrace it and have a lot of flexibility for user customization seem like the keys to victory.