Forum Replies Created

Page 9 of 22
  • Andrew Smith

    March 16, 2013 at 6:46 pm in reply to: AAF workflow update

    Ok great thank you for the info guys!

    Jef I see the problem with baking out speed effects when its R3d and 5D like that last aaf job – otherwise maybe that is best if speed effects are included in a sequence.

  • Andrew Smith

    March 15, 2013 at 1:56 pm in reply to: AAF speed changes?

    Hey William thanks for the reply!

    It did not ignore the in & out – totally lined up with the offline quicktimes i was given but the renders themselves did not have the speed changes in there so the AE artist among other things had to also re-time very single shot to be the exact duration it was in the Avid timeline – so that each shot had an exact duration of 15 seconds.

    Anyone from BMD reading this and can respond?

    I guess overall it leaves a question about what comes thru on an aaf comp[aired to say an xml from fcp7…would love to know what to tell an avid editor to remove or prep before sending me an aaf and files.

    thanks

  • Andrew Smith

    January 29, 2013 at 8:10 pm in reply to: color chart for log-c footage?

    Very insightful thank you Joseph!

  • Andrew Smith

    January 27, 2013 at 12:28 am in reply to: Resolve 9.1 10 to 8bit monitoring issue.

    Nerd alert.

    Get a super-size shake for the haters!

    We also have the GT120/5803GB card combo and know of a few other people running this setup for Resolve, CS6, Nuke, etc. But its not the overclocked 580’s just the standard stock pc model 3GB running OSX10.8.2, if you run that with a quadro4000 i believe it would be too much of a power drain but with gt120 ok. Regardless I would say why not get the external power booster just to be safe ya know, especially if you have 4HD’s RAID, SSD, Decklink, redrocket or whatever? That is a beefy card my friends, i think i found a slightly used one if you need and cant afford a new one:

    https://www.amazon.com/gp/offer-listing/B004YJVUBG/ref=sr_1_2_olp?ie=UTF8&qid=1359245986&sr=8-2&keywords=gtx580+3GB&condition=used

    https://www.amazon.com/Apple-MC002ZM-GeForce-Graphics-Upgrade/dp/B001V3DZD4/ref=sr_1_1?ie=UTF8&qid=1359246265&sr=8-1&keywords=apple+gt120

    My interactions via ebay with macvid guy have been really poor gotta say people, terrible customer service. If i were building a new macpro for Resolve with no cubix i think the 120/570 combo is actually a great idea if you don’t want the external power source, BUT that Booster is not expensive and its super easy to set up.

    My two cents.

  • Andrew Smith

    January 20, 2013 at 4:24 pm in reply to: Davinci workflow with CS6

    This week I have also been wondering more about best practices going from PremiereCS6 to resolve and back – as more editors are moving away from fcp7.

    There are still MANY issues with Premiere XML last time i checked, and the normal practice I have seen and actually done myself, is ‘washing’ them thru fcp7 in order to get things functioning properly. Another part of this problem is the fact that there are ALOT of dslr h264 projects in CS6 being done, and people want to avoid having to transcode to better codec for playback and performance like proresHQ with added timecode (FCP EOS plugin, 5D2RGB, etc). Kinda makes me wonder if learning Speedgrade just to check it out might not be a bad idea for this type of job?

    I am wondering how best to handle a workflow where they have cut in PremiereCS6 using the camera original h.264 files and want to grade in Resolve and send back to Premiere for finishing. Should I be advising assistant to send me xml and transcoded w/timecode ProResHQ files or just stick with the h264? As far as I am aware Premiere CS6 XML’s are still not coming into Resolve as they do from FCP7 and I imagine not having metadata will show many issues when trying to match the the offline reference file. I would love to get some opinions on how best to handle this workflow as of today on the latest ‘stable’ version of Resolve 9.0.4 (I have read there are some issues with Tangent control surface so will have to wait for 9.1.bug fix 🙂

  • Andrew Smith

    January 9, 2013 at 11:43 pm in reply to: Premiere CS6 EDL workflow for Scene Detect?

    Thanks for the responses gents,

    So Margus, are you saying you in fact have had success with edl from premiere?

    Ultimately it sees they will have to just give me a baked out file and i am suggesting that they make it pro res hq even though in pp they used the h.264 files – because its a mix of stuff it seems best to do the baked out option but i would love to easily chop it up with an edl like i would from fcp7.

    any help would be great!
    thanks

  • Andrew Smith

    January 9, 2013 at 3:27 am in reply to: Premiere CS6 EDL workflow for Scene Detect?

    any suggestions on how to handle this workflow?

  • Andrew Smith

    September 28, 2012 at 12:19 pm in reply to: DaVinci Resolve 9.0.1 update

    Sorry I can’t agree with that logic sascha…no offense.

    Software update seems pretty standard with other apps for post-production, no reason Resolve should not follow suite even if it’s an email notification – might I suggest an online form where you select your BMD products and get automated emails whenever any of them have updates (i.e. Davinci, cinema camera, decklink, hdlink, etc).

    Just my opinion on this, seems like not such a biggie to avoid checking FB for updates 🙂

  • Andrew Smith

    September 27, 2012 at 9:49 pm in reply to: 9.0.1 window tracking issue

    I hate to agree here because well honestly i think great work is being done by the BMD guys, BUT wowzers!! Yeah shots that easily tracked for me in V8 were having lots of issues in V9. Every version of Resolve 9 I have tried has some bugs in it that directly effect my work a lot. Just kinda blown away compared to V8 the number of glaring bugs that really do negatively effect real world paying jobs for users. This latest release has fixed a lot which is great, but obviously still kinks need to be worked out.

    Kinda surprised it could be released with this many bugs and a kind of “send us your project file, xml, footage, crash report, etc. nope we don’t see that issue on our end” response without actually telling users that YES many others are also experiencing all these bugs and you are not alone.

    To be constructive here because I do actually think they are doing great work, I think it would help greatly for BMD support to share what bugs people are finding as soon as its a consensus among enough users or have a section on the forum for bug reports or something so users can get an idea of what is going on. Being left in the dark on this stuff i think is the most troublesome thing for me as a DaVinci user..I dont have this issue with Adobe, Maxon, Imagineer, Autodesk, etc. whom I have also invested in greatly.

    Also, I think auto update notification or something for versions and decklink drivers etc would be great – redcine-x (as do many other apps) now has this feature where it notifies you of available updates – or even an email notification for the BMD products you have which have updates? Having to search forums and dig thru the support page is just extra steps no?

  • Andrew Smith

    September 27, 2012 at 12:46 pm in reply to: Standard Candle 9.0

    Does anyone have the test – the yousendit link has expired?

Page 9 of 22

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy