Chuck Brown
Forum Replies Created
-
Also, it would appear that Element does need the Tangent Hub software installed. The Wave panel does not.
-
Uninstalling the Hub software left me with no communication at all. Tangent support reached back with instructions to run the Synapse app the comes with the Hub install to verify that the panel was being seen. Maybe it was the reinstall of the Hub software or something but it appears to be working in Resolve now.
Thanks for your input. Also, to clarify, I plugged the panel into the back of the iMac directly and not a USB hub. I was referring to the Hub software provided by Tangent. Sorry for the lack of clarity.
I am a solid user of Wacom and not sure how much use I’ll get from this one panel but thought it worth trying out. Honestly, the bypass button alone I may use more than any other option. Now if only a highlight toggle was on a button… ah, to dream. 😉
-
Alas… Thanks for the quick reply.
-
I’m using an Intuos3 and find that the tip is contently double clicking instead of single clicking when I’m trying to select. Doesn’t really matter what the program, but I was wondering if you made any adjustments to the default set up of the tablet? I’ve replaced the tip and tried various settings on the tablet to no avail. I love my tablet as I’ve moved from the Smoke world to Mac/FCP and would love to get my interactivity back.
-
I have a ralated question here. Much was answered in this thread, but in FCP, when shooting 720p for 1080i delivery for broadcast, is the project set up as 720p60 or 30? I’m looking for the best use of drive space here. I agree that shooting at 720p30 sucks, but does editing in that setting give the same look to something shot 60? I guess I’d be editing progressive though…maybe I answered my own question. 🙂
Also, in ralation to drive space, which takes up more room…a second of 720p59.98 or a second of 1080i29.97?
Incase anyone has words of advice, here is the low-down. Shooting all 720p, some P2, frame rates of 24, 30, and 60. Not needing any off speed effects, just looking for good interlaceing for output to 1080i29.97. I’ll be looking to edit in some form of HD that will accomidate these different framerates. Don’t care if 3:2 is added. Hopefully no upconvered SD, but I might be dealing with this in graphic builds.
P.S. I miss my Smoke 🙁
-
Way to small for my old eyes. 😉 If you find a way to move them other then one at a time, post back. Scaleing in time is greatly missed. But I’m used to Smoke animation interface, and it’s a lot more like AE in this respect.
-
Hi Todd, good reply. I haven’t read all the responces to this post, so forgive me if this has been mentioned. I’ve worked on several systems and can say that there are only 2 things I miss on most of them that the AVID has. The trim window and marking on input. That’s about it. FCP trim window is close, seems a bit clunky though in comparison. The ability to drop markers on clips as they come in is the most missed for me. You should also consideer the market you’re in. Moving material between systems (if thats what you need to do alot) can be a lot easier and might justify continued use of AVID. I don’t see them going away, the film cutters love ’em. Everything else, you’ll get used to. And I agree with Todd on the render time. It’s probibly something you deal with already anyway. Build the time in. Just my observation.
-
thank you for the reply. I was able to capture the footage using your advise. I did notice that as it tryed to pick up after a TC break, sometimes it was not successful and I had to pay close attention to make sure all footage was captured from the tape. It was inconsistent with amount of “dead tape” and it did not always fail. I have it in the back of my head that sync would help the issue. as always, the “capture all and start editing” workflow is not always as easy as it sounds. 🙂 I’m starting to like the direct to disk shooting more and more. (if it weren’t for compression)
-
There are differing versions of Smoke that restrict your options of what you can send. Uncompressed is always the safest, but with obvious size issues. Long form or short form will make this decission for you most likely. 🙂 If your Smoke house was running version 2009, what you sent would have worked. Smoke workes in unconpressed RGB native within the system, but can soft import select compressed codecs as of the latest version. I would suggest contacting your Smoke operator and ask what he wants. For long form, I like what you sent…xfer overnight to a SAN, relink an XML, and start finishing. For short form, I like to bring it all onto the Smoke drives. It’s really just a workflow question and personal preferance.