Forum Replies Created
-
Thanks Fellas… I was hoping to hear from people like you. I just wanted to get a feel for what real people are actually doing. A tax person will give great advice, but you guys give experience.
I appreciate it.
Jason
-
Hey Shane,
Just wondering about stock answer #8. If you hook it up as you say, FW-deck-TV… Is the audio and video ALWAYS in sync? I ask because sometimes I see a delay, and then play with the delay playback settings until it gets to what I think is close, but I trust my canvas for sync and my monitor for color.
Jason
-
I moved some of the text layers around and viola! Success. Thanks for the heads up. I guess I should dive into this app a little deeper before I try to “do something simple” in motion again!!!
peace!
-
Up to a point I am. I just opened it up and moved the playhead and it immediately crashed out. I will try to remove the text around the area where it seems to be crashing and report back. That is, if I can without it crashing.
-
So I tested just the Satin template, and exported it with the default export preset (DV NTSC) and it exported fine, although it looked like DV, all soft and unacceptable. I trashed my motion pref and it still crashed when trying to export. I have adjusted ins and outs… still crashes. I’m now convinced it’s something I’m doing (as it usually is)…. I have had motion for awhile, but haven’t used it much, as I am more comfortable in AE. My client needed something HOT with no time or budget, so I went to motion… naturally.
Now I’m screwed…. Any suggestions? Is there a certain thing that motion hates as far as sequence layout? I copied a second template in the same “Satin” and pasted it into my sequence… previews fine… RAM preview makes it about 20 seconds into a 30 seconds piece. I’m getting very frustrated!!
-
I had the problem too. After building about 40 titles, suddenly, it wouldn’t close. I found that hitting the red “x button would close the window, and a prompt would ask me if I wanted to save my changes (something to that effect)… Click yes and it worked, but troubling that it suddenly became buggy.
I haven’t been back into that project this week (tomorrow I will), so I don’t know if my upgrade to 5.1.4 fixed it or made it worse. I’ll find out in the morning!!
-
Mitch,
I followed the instructions on here: https://www.borisfx.com/hosts/fcp/bcc4.php
Now I’m realizing that it’s for BCC4, but I has BCC3 on both systems. I doubt it’s a full version, now that I think about it. None of the plugs say trial version on them.
Man, I wish I had the time to dissect all these issues, but I don’t. What I do need is to make sure my client don’t become affected.
Jason
-
I just looked at all posts concerning 5.1.4 and Boris Continuum… I have an Intel MBP that I use for travel and offline with FCP and AE, and my main system is a G5 PowerPC. The posts and Boris’ site claim the 5.1.4 update renders BCC unusable. This was true with my MBP, but not my G5. I checked them and they work. Should they? Am I gonna be lulled into a false sense of security and then one day, with a client breathing down my neck, my BCC effects won’t be there?
Update on boris site seemed to work on the MBP, but we’ll see.
Any thoughts?
-
Bummer…
I appreciate you dropping some knowledge. I have adjusted the playback offset, so I’ll try that on my next output and report back.
Jason
-
Thanks for the post… I’ll give that a shot. 6 frames seems such a strange number. I am not sure I understand WHY this is happening.
I know this isn’t the most ideal way to do this, but I’m not buying a beta machine. This client is moving to DB (wishing I could just upload to their server)… Is DV just not reliable for frame accuracy? Seems to me it should be.
Jason