Greg Huson
Forum Replies Created
-
Creating the handles isn’t the problem – it’s tracking power windows through the handles, since they’re ‘hidden’ during the grade. I’ll try following your steps, but I don’t think it solves my problem.
That said, your note makes me think that I could probably track power windows in shots (that are suspect of having speed changes) using the master sequence (or is that called a master session?) That should give me windows that don’t jump during the handles later during render.
Love the way resolve handles speed changes – that is, it doesn’t try to recreate them, but simply simulates them in playback… that way you can still adjust them you return to the editing application.
[EDIT!] Thanks for reading the manual for me – I just re-read your email, and I that might be exactly what I need! I’ve got another show tomorrow that I know will have tons of speed-changes – can’t wait to try this trick! Also source-order is an interesting idea, too.
Greg Huson
Secret Headquarters, Inc
Greg (at) SecretHQ.com
http://www.secretHQ.com -
Not sure anyone answered your question directly – If you’re using the FCP or Avid preset, you can render any indvidual clip. I think you could use like… mark for render cache… or something to mark clips you NEED to render if your director doesn’t want to wait for each render… it does seem like there should be a way at least automatically flag clips that have been changed since render…
Greg Huson
Secret Headquarters, Inc
Greg (at) SecretHQ.com
http://www.secretHQ.com -
Discovered that my 7.1 was booting in 32 bit mode- reset it per apple instructions to boot to 64 bit and that solved my Nvidia driver problem- at least so far. Hmmm. Or maybe it was the 8.1 upgrade… Either way, working correctly now.
Greg Huson
Secret Headquarters, Inc
Greg (at) SecretHQ.com
http://www.secretHQ.com -
“Does Lion have anything you actually need?”
Yes, unfortunately. We’re beta testing another piece of software that requires lion – and I’d like to run them off the same boot drive. For now, I’m sticking with 10.6.8 until we find a solution to the graphics card problem – Systems working great in 10.6.8
Greg Huson
Secret Headquarters, Inc
Greg (at) SecretHQ.com
http://www.secretHQ.com -
deleted that .kext – made no difference. grrrr.
Greg Huson
Secret Headquarters, Inc
Greg (at) SecretHQ.com
http://www.secretHQ.com -
That did it. Thanks! Not sure why I didn’t find that info elsewhere – lifesaver! (I obviously misunderstood what the ‘current’ driver was.) Now getting 24fps off the GUI card (4000) alone in HD. Just reconnected the Cubix – that seems to work, too – still not qetting quite the performance I was expecting, but I’ll tweak a little…
Also, both monitors now working!! Thanks for the help.
Greg Huson
Secret Headquarters, Inc
Greg (at) SecretHQ.com
http://www.secretHQ.com -
Actually running 10.6.7 – That might be the problem, but I doubt it. Upon review of the install guide, the combo should be 10.6.7 with 3.2.17 – and I have the newer driver and the older OS. I’ll update the OS and see if that solves the problem… If not, I’ll try a different graphics card for the GUI
Greg Huson
Secret Headquarters, Inc
Greg (at) SecretHQ.com
http://www.secretHQ.com -
I pulled the Cubix loose, and Resolve now says there’s no CUDA cards available.
The drivers loaded using the ‘preferences’ pane are
The CUDA driver for mac is 4.0.21, Mac driver 256.01.00.35f05When I download the drivers from the website, the mac driver is a higher number, but the installer won’t run – simply stating ‘not driver update is needed’
I’m going to try a different graphics card for the GUI.
Greg Huson
Secret Headquarters, Inc
Greg (at) SecretHQ.com
http://www.secretHQ.com -
Huh. I see that now. Well… wish I had an answer for that! Switching from Nvidia to ATI solved what I guess was a ‘similar problem’ for me. If you figure it out, please post!
gh
Greg Huson
Secret Headquarters, Inc
Greg (at) SecretHQ.com
http://www.secretHQ.com -
I don’t think Avid’s codecs are 100% compatible with the BMD hardware- and QT references can be, as stated, funky at best. That said, we use them constantly with compressor- though rarely directly into final cut.
Avid is very open to being… open these days. If you’re not on 4.x, I’m amazed what you’re doing works at all. We also mix Avid and FCP all the time- and each version it becomes more manageable. I suggest you get near the front of the line for future upgrades.
As far as field order – it’s not avid vs fcp. It’s NTSC vs Pal vs HD. Interlaced HD formats are upper field first, NTSC is lower field first (pal, too, I think) What you’re describing kinda sounds like a field order problem, in fact. You may not see it on the quicktime, because you’re looking at a progressive monitor (omputer monitors are progressive.) But if you’re putting on NTSC tape, it’s interlaced – all NTSC is interlaced, even when it’s produced progressive originally. Add to that, on the screens in the avid editing application, you’re only seeing half the picture – a holdover from solving the problem of interlace when EVERYTHING was SD (I think this is true for FCP, too, but there may be a way to display both fields, not sure.) So, the ‘jittery’ part may be there, it’s just not being displayed. Once you look at it ‘on tape’ you’re seeing the field order problems you didn’t notice before. I suspect you’re mixing interlaced HD sources into finished SD projects – that has nothing to do with codec compatibility.
Sorry if I’m stating the obvious. I realized I haven’t offered any help, either… One suggestion might be to have a glass NTSC monitor hooked up to your system- this will help you detect these problems sooner rather than later. (LCD and Plasma mostly convert back to progressive. God, I wish interlace would go away completely…) If you need a couple 13″ ntsc monitors, I’ve got a few in the back closet!
Greg Huson
Secret Headquarters, Inc
Greg (at) SecretHQ.com
http://www.secretHQ.com