Rendering problems with a motion project

Hi there,
can anyone help?
I have a fairly simple motion graphic which i am trying to use in an FCP edit. The Motion project is some moving text with a simple background. The project renders fine in RAM in Motion.
The problem is that when I try and render this in FCP, the background becomes very distorted-the graphics are fine but the background isn't.
Is there anything I can do to rectify this? Any settings etc?
Any help would be very gratefully received!
thanks

You need to give the exact specifications of your Motion project and of the media in your FCP sequence and of the sequence in which the clips and the Motion project are being assembled.

Similar Messages

Rendering issues with imported Motion project in FCP

I have various titles for a DVD prepared in Motion that are imported as project files into Final Cut Pro.
When playing back the rendered timeline in FCP to a TV, the animation on these titles (scaling and moving of text and untextured, 100% opaque rectangles) looks fine. When I render the timeline to a QuickTime (DV PAL) they still look fine on a monitor, though obviously not a great test on a progressive display.
After using Compressor (and a suitable preset for PAL content) and burning to a disc from DVD Studio Pro, the animation is jumpy. Some elements in the project with a Fade In/Fade Out behaviour with Fade Out duration set to 0 suddenly disappear for a short period (looks like one frame) - these objects end on the timeline in the same frame that their Fade In/Fade Out behaviour also ends.
If I render the Motion project to a QuickTime file with transparency and overlay that in FCP then follow the same route through Compressor and DVD Studio Pro everything looks as I expected... smooth motion and no disappearing elements.
Any ideas? Should I just keep rendering Motion projects out to separate files to overlay in FCP? That seems a bit of a waste of the integration between FCP and Motion.

This gives me pause: AEManager::scanForPluginsInDirectory(PCString) + 1011
I'd check for any third party plugins...
Patrick

I have problems with creating new projects in iMovie.

I have problems with creating new projects. When i try, the mac says the following "Make sure there is enough disk space and that you have permission to write the projects to the drive." I have 8GB available, so its not that.

thanks for your support
lol

Problems Encoding FCP/Motion Project to DVD, HELP..........

Hi all, i've already posted in the Motion forum and no joy so im hoping the FCP guys can help me. Heres the problem.
I have an FCP project which which is 720 x 576 48 KHZ DV PAL. I'm trying to add titles using Motion. I've tried the Embedd and non embedd methods and when i view the titles in FCP everything looks fine.
The problem occurs when i author to DVD (iDVD or DVDSP4). My settings are the same in FCP as they are in Motion. Any pieces of video with motion effects flicker really bad. I've coastered about 10 DVD's messing with the field settings and no joy. The closest i got to a result was by applying a deinterlace filter in FCP. Whilst this helped, the footage was still noticably lacking in quality compared to the rest.
I've tried exporting the footage in compressor to Mpeg2 then authoring in DVDSP4 and the outcome was exactly the same. I find it hard to believe that im the only person with this problem??? If i create a project in motion with no DV footage it plays fine so theres a problem with motion layering over DV i guess. This pretty much renders motion useless for my needs. Incidentally the DVD's play ok on a Mac/PC, the problem is on Televisions. I've tried three Tv's and they're all the same aaarrrrrrrrggggggghhhhhhhhh!!!!!
Can anyome help?

Hi Chris, thanks for the prompt reply. I've followed your advice, i had to cheat of course. I set up my camcorder as a DV out device and then sent an S-Video to the TV. Now i can see the offending footage before i author. As you predicted the FCP footage is also affected by the motion titles, so that eliminates DVD authoring as the culprit. What a waste of DVD's. So my problem now is that Motion effects are causing the FCP footage to flicker. I have both apps set to Lower field dominance and pal 720 x 576. I cant work out where im going wrong.
Regards

Premiere CC to AME - H.264 nightmare rendering problems with CUDA on rMBP

I've been struggling for weeks trying to troubleshoot and narrow down my encoding nightmare on my own and I have finally succumbed to getting the forum's or Adobe's Help.
Problem:
Rendering a Premiere Pro CC project with via Export Media > Queue to AME in H.264 causes the encode to randomly fail on multiple projects.
I find it quite amazing that this error happens as I surely am not the only one rendering ProRes to H.264 on a new Macbook Pro!
Symptom:
Output preview starts to flicker then encoding stops randomly, preview window turns to a black screen or simply stalls while the Elapsed Time keeps rolling, PProheadless crashes in Console, encoding sometimes resumes after several minutes post the crash (but sometimes not) however the final output in such case is garbled before/after the crash. Computer is useable. All other software shutdown. Not using computer during encode. Can reproduce virtually every time.
Hardware:
Early 2013 Retina Macbook Pro
Processor 2.8 GHz Intel Core i7
Memory 16 GB 1600 MHz DDR3
Graphics NVIDIA GeForce GT 650M 1024 MB
Software:
Premiere 7.0.1 (105)
Adobe Media Encoder 7.0.1.58 (64bit)
Creative Cloud Latest Updates
Cuda 5.5.25 (latest)
GPU Driver: 8.12.47 310.40.00.05f01
OS X 10.8.4 (latest)
Project Details:
ProRes 4:2:2 or AVCHD sources
No nested sequences
Video track with image over whole sequence
Video track with text over whole sequence
Video track
Audio track
Sometimes video track with adjustment layer
Standard disolve effects between cuts
4 effects used: denoiser for audio, luma corrector and twice Fast Color Corrector
No third party plugins installed nor used
Sequence is set to Maximum Bit Depth / Max Render Quality / Linear Color
Use Previews off
Encode is set to Maximum Render Quality and always H.264 2pass VBR.
Errors in console:
8/27/13 12:38:01.144 AM PProHeadless[1389]: [CL_INVALID_OPERATION] : OpenCL Error : Failed to retrieve device information! Invalid enumerated value!
This is seen at multiple times while starting Premiere (no crash) and while starting the encodes and usually after/during the crash.
Crash report:
Process:         PProHeadless [410]
Path:            /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents/PProHeadless.app/Contents/MacOS/PProHeadless
Identifier:      PProHeadless
Version:         7.0.1 (7.0.1.105)
Code Type:       X86-64 (Native)
Parent Process: dynamiclinkmanager [397]
User ID:         501
Date/Time:       2013-08-26 21:12:21.878 +0200
OS Version:      Mac OS X 10.8.4 (12E55)
Report Version: 10
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGSEGV)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Full Crash report:
http://pastebin.com/a93cNVqk
Attempts to solve the issue:
Tried encoding without external montior
Tried encoding with source on internal HDD, output internal HDD, source exterbak RAID, output internal HDD
Tried encoding with AME while Premiere is open in the background and without it opened in the background
Uninstalled other software that could mess with the graphics: Colormunki, Parallels.
Software mode is fine on all attempts in AME however encoding takes 2-3x longer. On a $3000 laptop it's not really great.
Encoding directly via Export Media > Export without Queuing to Adobe Media Encoder seems to work fine. I have not tried this too many times because I need to render multiple outputs and doing it without AME means a lot of 'sitting and waiting' to click Export for the next format. This is not an option.
Tried deleting the Media Cache
Completely reinstalled OS X 10.8.4 from scratch with no other software running and tried to export. Same problem.
Performed Apple hardward test. No problems.
To Test:
I'm planning on installing Bootcamp so I can test the problem in the Windows version and I could pinpoint it to a hardware problem rather than a software problem.
Notes:
Problem happens with CUDA and Open CL modes although in Open CL mode, the whole computer tends to freeze intead of just 'stalling'.
Editing and playback inside Premiere is OK! Even encoding out of Premiere is OK directly but not useful for me as I need to render each project to 5 different H.264 formats.
I hope you guys or Adobe's Support can find a solution to this problem because I'm really stuck between a rock and a hard place.
I've submitted a bug report but their reply is not very comforting:
but their bug report says "Due to the volume of submissions we receive, responses to inquiries are generally not possible. However, we may contact you if we need clarification on your submission." Nice.

Yes I considered your "solution" of just upgrading to Adobe CC but on principal I don't want to have to shell out more money to "fix" the problem. I was able to get an Adobe technician to view my screen in real time. He asked me where Prem Pro was after I opened it and my response was "precisely". The only evidence that Prem Pro is open is that there is the taskbar there with what appears to be fully functional drop down tabs but as far as the panels/workspace goes non-existent! He has "escalated" the matter I'll let you know what occurs next. I have tried using the software mode and there is no change. Like you I have wondered about a hardware proplem but I have checked via Disk Utility and there doesn't appear to be any? The CUDA issue well a) I am not sure how I would revert to previous drivers and b) when I re-installed Prem Pro from disc (that's version 6.0.0.) the only render option it gave me was Software only but that was also greyed out. Prem Pro still did not open up as it should!
I'll let you know what transpires.

Shake quits with certain Motion projects ...

I have a very simple Motion project that works fine on its own and in FCP, but the moment I import it into Shake, Shake quits unexpectedly. Can anyone shed light on this? Other Motion projects seem to work fine.
Details:
Motion project - 8 seconds movie (static noise created in FCP), TV screen mask over static, text fade in across screen, with a company logo. That's all.
Shake - I want to match move the Motion onto a monitor screen for a short tracking shot, but I can't get that far as Shake quits even if there isn't any other script loaded.
Both apps are the latest Universal versions and everything else is fully up to date.
Thanks so much for any help!
Dominic

Kalimera!
Yes, I tried that straight away, but it had the same result. The workaround wasn't really a problem, the problem is that I have software that seems unstable and if it crashes like that when I'm showing off to potential buyers, I may find myself losing money.
Nonetheless, thanks for making the suggestion, which I will mark as 'helpful', as others may find it so too.
Best
Dominic

Rendering problem with AVC-HD in AECS4

Hi all ,
i have a problem with rendering AVC-HD footage with all resolutions.
when i render the result is jumpy footage .
i tested with P2 files and i dont get the jumpy footage , only with AVC-HD .
any idea why ?
my computer :
cpu - I7 920
motherboard - asus p6t .
memory - 12GB .
OS - vista 64 bit .
10x

AltiumMan wrote:
This is a bit of a pain and I don't know how it'll work if you ever have a circular reference - i.e. a Premiere Project links to AE which in turn links to Premiere. I don't know how the media encoder will cope with that.
Circular references are not supported currently, so you need to structure your workflow accordingly. This is however a popular request, so chances are good it will come in one of the next versions.
AltiumMan wrote:
2) For some reason, rendering out of an AE comp that dynamically links to a Premiere project with an MTS file in it is _much_ faster than rendering an AE comp that directly references the MTS file. On the footage I tested it with, a 30 second MTS file was suggesting 1 hour 30 minutes to render when AE reads the MTS file directly, but less than 9 minutes when using the dynamic linking. Go figure?!?
Premiere can handle suchg streams without conforming them,i.e. it does not need to decompress frames and blow them up to full RGB. And of course, being aimed at RT playback, it surely is even more optimized.
AltiumMan wrote:
3) The Media Encoder that is now used by Premiere can render out to FLV using a 2 pass encoding but rendering out of AE only offers 1 pass. I don't know why this limitation would exist? Usually the two pass encoder is much better but I don't understand why it would be available in Media Encoder but not AE.
AE does not support temporal compression natively. The various media format savers try to circumvent that, but neither of them can hold an entire composition timeline in memory or temporarily store the result of the first analysis on disk, which is what would be required for 2-pass VBR. One of these days, maybe...
Mylenium

Round Trip problems with FCP, Motion and 16:9

Hello all-
I've been having some problems with FCP5 and Motion 2. I am working with anamorphic footage (mini dv), and my problem lies in trying to use the "send to" feature in FCP to Motion 2. If I send some footage to Motion 2, edit it, and then go back to FCP to look at my edit, the anamorphic flag has been removed... the video is squished and there are black bars on the right and left sides of the film. I can easily fix this if I find the clip in the FCP browser and check the anamorphic flag, then drag and drop that clip over the original in the sequence, but I was wondering if there was an easier way. Is there a way to make it be anamorphic when it comes back into FCP from Motion 2?
Thanks!
Dual 1.8 G5/2GB & 12 PB G4/1.25GB Mac OS X (10.4.4)

Yes, it loses the anamorphic flag on round trip. Just
ctrl/right-click on the Motion project in your
timeline, select Properties/Format and click on the
anamorphic setting column.
Patrick
Patrick-
Thanks for the reply. That's exactly what I've been doing, but I was just wondering if this was an actual bug or not. I guess we will have to wait for Apple to fix it...
BTW- Whenever I check the anamorphic culumn, I always have to re-drag and drop the clip in the timeline again. Is this right? Or should it go ahead and change it in the timeline automatically?
Thanks again!
Dual 1.8 G5/2GB & 12 PB G4/1.25GB Mac OS X (10.4.4)

Burn Problem with a 4GB project: "Layer 0 Exceeds"

First off this is not the usual Dual-Layer problem. I know all about Layers how they work and how to make them. Although the error I receive deals with DL my projects or nowhere near that size.
I recently had DVDSP 4 crash on me. Ever since than its been running really funny. The biggest issue I am having is that it won't allow me to burn a DVD 5. My projects usually range from 2.5GB - 4.5GB. Let me also say that DVDSP 4's Disc meter has always been a pretty good gauge as far as I am concerned. It's always been right on telling me if something was going to fit on a DVD 5 or 9.
My problem ever since the crash is that DVDSP will not allow me to burn a DVD unless the project is under 3.5GB. I have tried everything, including a Full Re-install of DVDSP. Every time I try to burn a DVD I get the following error message:
+"Formatting was not successful. Layer 0 exceeds the maximum layer size allowed. Please choose a suitable marker location that will support this condition."+
My latest project is dealing with a 4.4Gb (according to Meter) 4.32GB actually. It is impossible for me to burn a DVD because of the error message above. I can however run the project out on a Single DLT. How does that work?
Has anyone else had a problem like this? Does anyone have an suggestions?
I have checked all the obvious settings in DVDSP and all seem to be right. I can't figure this one out.

I've never had a problem burning a 4.4 disc on a DVD 5 until now. I actually went back to some of my previous project that were a DVD-5 and I am unable to burn those now too. Everything really got screwed up on that last Crash.
Yes. I am using AC3 audio.
I have not yet tried burning my DVD project through another program...but thats a good idea.
I usually burn a DVD and DLT for the replicators...but I know they prefer a DLT. What I find odd about all of this is that I am able to run out a DLT with no errors at all. It only seems to be on the DVD side.
In regards to the uninstall...I used the exact program. I am actually in the process of doing a full reinstall of FCP2 Suite.
I'll let you know how it goes. Thanks for the suggestions.
Mike A.

RAW file rendering problems with Pentax-k5

Since a few weeks I have serious problems with the raw rendering in aperture 3.4. I have done everything to solve this problem, but until now without succes. I have upgrade with mountain lion OS X 10.8.2 and I use the latest version of aperture 3.4.3 RAW 402 build 672.6.
Does anyone have this problem to? Or do you know how to solve this problem?
Regards
Jan K.

Jan,
that may be the same problem as discussed in this thread. Do you use in-camera settings to enhance your pictures? these will not be captured in the raw processing that Aperture does, but the pentax software understands the in-camera settings:
Image Previews In Aperture 3 - Canon 5D MK2
Regards
Léonie

Raw file rendering problems with Canon EOS 5D in Aperture 3

Since upgrading to Aperture 3, I have had serious problems with the rendering of Canon EOS 5D (not Mark II/III) RAW files. With Aperture 2, both the preview and full-sized images looked basically the same as the original images as displayed on the camera's display, without any adjustments.
With Aperture 3, each preview images initially look fine after import, but when Aperture re-renders it from the RAW file (e.g. when displaying the full-size image), the colors are drastically intensified, and the hue is shifted generally towards green/blue. I've checked the RAW Fine Tuning, and it is set to the defaults. If I turn the default RAW Fine Tuning settings all the way down, the image is still not at all like the preview from the camera - it becomes much darker and stays too blue/green, with washed-out colors.
A friend with a Canon EOS 5D MkII also recently upgraded her Mac from Aperture 2 to 3, and hasn't experienced any problems. We've tried importing RAW files from my (non-MkII) camera to her Mac (with the default RAW Fine Tuning settings), and get the same results as with my own Mac (i.e. strange colors), so the problem seems to be related to the camera model.
I've also noticed that scanned greyscale tiff images (including images that were originally imported under Aperture 2) are changed when first displayed by Aperture 3 - they become darker and more contrasty, with lots of information lost in the shadow areas.
I've also tried removing Aperture preferences, Aperture itself, and re-installing from download, with no change in the problem. (Aperture is the current latest version, 3.3.2.)
Has anyone experienced similar problems?

I'm having the same problem.
iMac running Mac OS X Lion 10.7.4 and Aperture 3.3.2. Workflow is importing through Canon's DPP and then using referenced images in Aperture. The images look great in LR4, or Canon's DPP but are flat and dingy in Aperture.
There's a free preset that goes part way to fixing it at http://theapertureblog.com/2011/02/10/my-aperture-workflow-for-working-with-cano n-5d-mark-ii-files/
but as good as this fix is, it doesn't quite do the trick. [not being a hater, and not saying I can do better]
I just got back from shoooting 1,500 images with a 5DMii and a T2i using Canon 24-105L IS, 70-200 2.8L, 50 1.8 and a Sigma 120-400 and the T2i images are not just better, they're in a different league.
I've tried shooting in Faithful, Neutral and also toggling these presets in different ways and still can't get Aperture to match what I see on the camera's screen or in other Apps. I love the interface and DB of Aperture, but what's the point of using it if it doesn't produce and awesome image in the end?

Problems with a xcode project

Hi there,
I'm trying to compile an existing Xcode project which has used boost library and threadpool library. I have already added the correct header path and library path, and the boost has been successfully compiled(cause the code uses libboost_thread.a).
Here's my header search path:
/usr/local/installation/prefix/include(boost header after installed)
/usr/local/boost1_450
/Users/niexiao2008/threadpool-025-src/threadpool/boost
And the library search path is:
/usr/local/installation/prefix/lib
I'm sure the boost library has been installed correctly and passed through some test codes, but there's still some problems when buliding the project:
i686-apple-darwin10-gcc-4.2.1: error trying to exec '/Developer/usr/bin/../libexec/gcc/i686-apple-darwin10/4.2.1/cc1plus': execv: Argument list too long
Command /Developer/usr/bin/gcc-4.2 failed with exit code 1
Could someone please help?

In the Build results window select the compile line that is failing. This should reveal a 'details' icon on the line to the right. Click the icon to display the actual compile command and try to determine why the argument list is too long.

Problems with opening/creating projects

Hi all, this is my first post so Welcome
I have a problem with Photoshop CS4 Extendet. After installing it under Windows 7 when I'm trying to start a new project or open a graphic in Photoshop the only thing which happens is a gray window of project without any graphic, without possibility to work on it etc. I know that graphic is loaded but I can't work on it. When I'm trying to move/large window, it crashes. Here you can see what I see when I load any graphic: http://img231.imageshack.us/img231/6120/61404388.jpg - you can see that photograph is loaded in layers menu section but in window it doesn't appear.
I have used this Photoshop under Windows 7, even same computer some time ago, but with different hard disc. And then it worked properly without any problems. I don't know why now after installing it I have such problems. What can I do? Is it a metter of drivers for graphic cards ot something like that? I'm useing the latest drivers for graphic card and all drivers for Windows and it's components are the newest one.
Here is ma computer specification:
Processor Intel Core i7 920 2.67GHz, 6GB ram, two graphic cards NVIDIA GeForce GTX 285, motherboard Asus P6T Intel X58 Windows 7 Home edition 64 bit.
What should I do now?

As is so often suggested here, check the nVidia web site for updated video drivers for your card. Chances are very good they have already fixed this problem.
-Noel

Problems with sharing a project from Final cut x

I have just purchased a canon Legria g10 (pal) and when I share(export) the project I get horizontal lines on the image, the raw footage looks fine in quicktime but when I edit and share it back out of Final Cut x it has the lines. Do I need to de-interlace and if so why? will I have to do this everytime I use the camera? or is the problem with settings on the camera? Any help would be greatly appriciated.
thanks in advance

Hi Tom,
thanks for the swift reply. Here are the screengrabs
the exported footage
the original footage
and the propeties of the original footage
and the properties of the exported file

WLP10.2 rendering problem with FF3.5.3

Hi,
We are building a portal using the WLP10.2. We are facing problems with FF3.5.3. It doesnt render the page immediately. On refreshing the page for 5-6 times we get to see the page rendering. We have even tried debugging the issue by installing firebug. In firebugs console it shows the files being loaded. It loads till the .../framework/scripts/bea/wlp/context/Other.js and stops loading the page from there. After clearing the browser cache and refreshing 5-6 times, the site than loads up. By the way we are even using jQuery to render certain UI like tabs, accordian being used in the page.
Anyone, if you have encountered such a problem. Please let me know what was the workaround you people tried.
Regards,
Subrahmanyam.D

Are you using the DVT (dynamic visitor tools)? Is this a production mode or development mode deployment? I assume that DISC is enabled because you watched DISC modules loading.
Is there an error message in the firebug console?
I saw something that may be similar: the DVT would stop during some of its initialization code. It is client-side code that was calling some dojo module initialization code.

Rendering problems with a motion project

Similar Messages

Maybe you are looking for