Render Issues, FCP7 - strange colours

Hi there,
sorry if this issue exists somewhere else on the forum. I couldn't find it.
I'm trying to render in FCP 7 and I'm getting strange issues where colours that shouldn't be there appear.
I'm using footage that was originally shot in HDV on an HV20 but was converted to Prores. It's also been through colour, rendered through that and then reimported.
The shot in question has a colour filter on it, crushing the blacks. It appears in anything I export. In other situations where I've come across this issue, I just rerender and it's fine. But this shot seems to not be able to shake it.
I'm uploading a video to youtube for reference. I'll post when it's up. But in the meantime if you have any suggestions or thoughts it would be much appreciated.
Thanks in advance for the help.

Thanks,
That didn't help. But it seems I've now worked around it. I removed the colour corrector filter and replaced it with a brightness and contrast filter.
If anyone else has suggestions on how to solve this issue for future issues - or an explanation as to why this happens - your insight would be much appreciated. I've come across this problem before. But I usually work around it by switching to my other computer (that seems to favour rendering better for some reason). Unfortunately, this time I'm on the 'better' computer that tends to solve my problems.
Thanks,
Tess

Similar Messages

Apple Pro Res 422 / FCP7 render issues

Hello,
I do a lot of timelapses and have pretty good workflow for all this. However, I am experiencing one issue that makes everything a bit difficult. I appreciate if anybody could help me.
My workflow is:
1. Shoot some stills RAW
2. Develop in Adobe Camera RAW
3. Import stills sequence and render in AfterEffects CS4 to AppleProRes 422
4. Import to FCP7 and edit
5. Grading / color correction
6. Publishing
All works fine, however I am having very often an unpredictable issues with the Apple Pro Res 422 codec under FCP7.
I always render a bunch of sequences from AE using the same settings for all files. The only difference is resolution.
My render settings for exporting from AE are:
- Apple Pro Res 422 wrapped in MOV
- render in 10-bit YUV from RAW 16 bit sequence files
- AE project in 16 bit
- Resolutions of rendered all files around 3500x2500 px, this vary from file to file.
The sequences render fine in AE.
The sequences play properly in QT, I can import them to FCP properly, play in FCP properly. I can drag to timeline, scale, rotate, scrub etc.
However: Some sequences fail to render in FCP7.
When I drag them to my working sequence in timeline (Usually a Full HD 1080p, Pro Res 422, YUV), scale down (usually) and try to render timeline footage (don't mean exporting here yet) I get the following error:
"Codec not found. You may be using a compression type without the corresponding hardware card."
This happens on many computers including iMac, MacbookPro and a Mac Pro.
I discovered that setting the footage size to even width and height figures when exporting from AE eliminates the problem sometimes, but it does not help in all cases.
Also it sometimes help if i take such sequence, crop and export using QT under the same settings, just a few pixels less in size. But again - it helps sometimes.
Can anybody help me with these?
Anybody experiencing similar issues?
Thanks a lot.

I had the same problem when we started to edit on Pro Res timelines. The solution I found was to go the Sequence Settings > Video Processing > and change the Render setting to "Render in 8-bit YUV" that allowed me to actually render the timeline and view my work. Hope that helps.

My macbook pro's screen display has suddenly gone into a strange colour setting where everything appears in a kind of infrared colour palette an I can;t seem to change it back. It's the same for all icon and websites, does anyone know how to restore?

My macbook pro's screen display has suddenly gone into a strange colour setting where everything appears in a kind of infrared colour palette an I can;t seem to change it back. It's the same for all icon and websites, does anyone know how to restore?

Wow! I think I had this same issue just last night.
I was cleaning my macbook pro retina on the outside. Then I opened it up and was wiping dust off the monitor and I can't pinpoint exactly when, but the colors changed suddenly. It looked super strange, it was like green halo's and it looked worse when looking at it at an angle. Of course I took no pictures!!! I was freaking out that my 2 grand laptop was busted and I somehow removed a protective film or something.
But I digress... The image looked very green and spacey, it was almost a neat effect. After about 5 minutes it started to look a little more digital though. There were straight lines of this halo effect on the edges and top. After about 10 minutes it turned into a predominate issue with the blacks on screen. I could open a web browser and it was unnoticable on a white background. After about 15 minutes, you could only barely see the green cloud effect if you looked at the monitor from an extreme angle. After about 20 minutes, it was completely back to normal, I almost feel paranoid like I see a halo or something strange. But I believe that might be all in my head now.
So yerp, lemme know what you guys figure out.

Strange colour spots (red & green) appear after RAW files converted to JPEG, anyone know how to fix it?

Strange colour spots (red&green) appear after RAW files converted to JPEG, anyone know how to fix it? Thanks.

I use "Export" function to convert the picture from RAW format to JPEG format, resolution 240 pixels per inch. Strange red dots appeared in the area supposed to be dark grey, as per the picture below. The red colour does not appeared in the original RAW picture when viewing from Lightroom, only exist in the JPEG it created. Any ideas how to fix this? Thanks!

Render issues with text

I have made a short 1 min movie, and have rendered it. I want to download to youtube, but when I try to export using quicktime conversion, it shows render issues wherever I have text. Once I get cancel out, it shows no render problems.
When I remove the text, the render problem still remains. I can export with quicktime, but not sure youtube will allow this to be downloaded.

Please define: "render issues" and also the phrase "Once I get cancel out"
-DH

560GTX render issue help please

I've got the MSI 560GTX-Ti twin frozr video card in my Sandy Bridge system. It is NOT overclocked, I am running it at all factory resets. This is the second card I have received and they have both had some rendering issues. I'm using the latest drivers from Nvidia 266.66
Everything looks good in general usage, but when I play the game Rift (using High settings) I am getting some rendering artifacts. The card does not appear to be overheating as far as I know. I have run Furmark and it looks ok. Temps do go up to close to 70c but no graphic anomalies show up. In Afterburner the settings are all stock factory settings. At no time in the game does the fan seem to crank up to be audible.
I would include an image of the screen but don't know how. Basically the landscape will display square beams of texture protruding from random areas of the screen. Any ideas on what is going on and how it can be fixed?
Willax
edit: I ran Furmark right after getting the render issues in RIFT and the fur donut had some holes in it, the temperature was running close to 70c
Then I changed the fan speed from AUTO to 70 percent and the temp in Furmark dropped to a steady 65 but there were still render issues with holes and extended triangles in the donut.
It seems that this card is getting too hot and not rendering correctly, but it shouldn't be happening. I even turned the fan up to 100% and although it got loud the temp did not change
very much from 65c

Well, I clicked those items and told it would be active after I started afterburner. I restarted and the voltage slider was not active. Nothing I clicked would let me do anything. I hadn't really planned on doing any o/c stuff with this card, but purchased it because of the GREAT reviews on it. I prefer to run at stock settings, and it's not giving me very good performance with those
I'm glad I got the extra year warranty on it and will probably call New Egg tomorrow to replace it.

Render Issues

I'm trying to export part of my project(feature length) and Speedgrade keeps crashing. Not wanting to come back to these forums asking for help that would lead to such an easy answer as last time, I tinkered. I originally messed with some of my export options to see if that would effect anything, but eventually I found that for some reason it only crashed when the timeline did a full fade to black and there was empty space in the timeline. Seeing as how I'm not yet exporting the final media, this is alright, and I managed to export this section of the project into 9 files for my producer to view. I am wanting to see if I can solve the problem before I move to exporting it in higher quality, however.
Additionally, when I started exporting the timeline in separate clips, the second and on exported strangely. It exported the movie, but it took up 1/4 of the video size of the movie clip, inhabiting the upper left corner, the rest being filled by black. Again, the clips are only for review, so not a big deal, but definantely don't want that on the final product. Any help is appreciated.
https://dl.dropboxusercontent.com/u/44489041/H.264/Act%202%20p9.MOV -Link to the final part of the pieces I exported from this for an example the strange export video.
Picture included of my export options (Strange note: I had to change the fps to 60 even though the timeline originated in premiere as 30. Whenever I exported as 30 the video would move too slow though, changing it to 60 fixed the problem, dunno why this occured int he first place).
Really enjoy the workflow of speedgrade and I think its an awesome program, but the amount of errors, crashes, and bugs I've run into is severe. Even if they are mostly user generated, getting out of them isn't terribly user friendly. I enjoy the rest of the adobe suite and never seem to have such dramatic issues, and I look forward to the day when speedgrade is more like the rest of the suite.

Hey, I think your problem might be with h.264
It is very processor intensive to render to h.264 and if your applying color while coming from a 16 bit source its going to get crazy especially around high compression points like fades and really dark frames or just black...
I would recomend rendering to prores or dnx hd first and then to h.264 hopefully it wont crash anymore and you will get better color rounding results... and if you really want to get crazy you could render to animation or dpx sequence for the best quailty but I find prores to be just fine and you cant tell the difference for finish purpouses...

Render issues with footage from Color

I'll start off by noting that this issue only happens running Snow Leopard.
I am having terrible problems when trying to apply and render some effects on footage which has come from Color…specifically, the Bad Film filter. Either at the render completion or during the render, I'll get all sorts of "screen draw" problems, like green and pink pixels everywhere. Sometimes they will only appear in the Canvas window, but if I launch any other app, the new app's is nothing but the screen error and the app is useless, thought I think it still functions, though useless to the point that I'm only left with having to restart. Occasionally, it'll throw that error telling me I must restart (in several different languages). I have occasionally had success with very short clips, but anything much more than 30 seconds is useless. I would think this is a hardware issue; however, it only happens under Snow Leopard and is not an issue with Leopard.
I have performed a clean install from a zeroed disk with both 10.5 and 10.6 and upgraded to the latest point release. I'm not really sure where to go from here. Has anyone experienced anything like this? I have the early 2008 8-core 2.8GHz Mac Pro with 16Gigs of RAM and two monitors connected to the ATI HD 2600 XT. I've also tried rebooting to just one monitor, but no dice. I've run hardware tests from TechTools that came with my ACD's AppleCare and all appears rosy. Real Time effects seem to work just fine and I don't have issues with all effects that require rendering. Most befuddling, I'm having no issue on clips that have not first gone through Color. Strange, huh?

Sorry about that.... The footage is ProRes422 1440x1080 going into Color and ProRes422 1920x1080 coming out. I've tried exporting at 8-bit Uncompressed out of Color with the same results.
Originally, this is 24p footage from an HV20 taken to ProRes via this: http://support.apple.com/kb/HT2410 method.
I'm still just not sure why this only happens in Snow Leopard, while everything works peachy in Leopard, though I think you may be on the right track with this being an FxPlug filter. I know I would occasionally get messages stating, basiclly, "Your GFX card is a wimp, these filters won't work" when trying 10-bit sequences under Leopard, thus I tried the 8-bit setting with this issue and all without any luck. I'll will try "Light Rays" and "Bloom" this evening to see if I get the same result.
To make this stranger still, Bad TV seems to render just fine, as far as I can recall, only Bad Film give me problems. I suppose this particular filter may not be compatible with my configuration. Perhaps, I shoud be getting that message instead of a crash.
Message was edited by: Carl Spackler

Fuzzy screen, strange colours, and startup freeze

Hello there.
This issue might have been covered, but I have not found a thread with it specifically.
The thing is, I have an first generation Imac G5, with 17 inches screen and 1.8 Ghz. It has Leopard with the latest patches. The serial number was in the range of the repair extention program (http://support.apple.com/kb/HT2390?viewlocale=en_US) so I got it repared for that issue over a year ago. There was no video gliches, but it just refused to power up. They really had a hard time making in work at the shop I went to in Montréal. I think they said the first power supply they instelled grilled, and they also had to change the mother board. But at last it was ok and worked for a year.
But small video glitches (with strange random colour lines)and kernel panics started to became more frequent until finally, the thing froze on mid startup.
After a night's sleep it started all right with a bit of screen oddities but froze two minutes after when a program was started. It starts all right in safe mode, but more screen oddities become apparent over time and after a while it dies painfully in an abstract graphic figures drug addict vision style nightmare. I have tried all the basic reset stuff without sucess.
At apple they say repair it at your own expanse and bugger off... lol. But I'm really being poor student budget here! So basically, I want to identify the problem's origins, know if I can sort it out myself and how... If not, how much would it cost to repair the damned beauty. It would be a shame to end the love-hate relationship we share, and I might be old-school but I like keeping my comps more than 3 years.
Thanks in advance for all your answers ladies, gents and geeks.
Antoine

Welcome to Discussions Antoine - you may be having a problem with your video RAM, or with your power supply or logic board. Try starting from your install disk and run Disk Utility:
Disk Utility
1. Insert the Mac OS X Install disc that came with your computer, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume.
6. Click Repair. Disk Utility checks and repairs the disk.
Let us know what you find,

Strange colours on screen after upgrading memory.

Hi all.
I bought a 2nd hand eMac from eBay and have just received a 512MB SDRAM module to upgrade the memory from it's current 384MB to 768MB.
On the first install I removed my 128MB module and installed the 512 module - No Boot. (beeping on startup)
I thought I'd try the 512MB module on its own - No Boot (again beeps).
I then tried just my 256MB module - Booted fine.
I then tried the 512MB module on its own and it did boot but this time the display colours were very off (the apple logo in Tiger was pink for instance)
Last of all I took out all ram and reseated it all - Success finally.
Now my questions are:
Were the beeps a memory error warning (I assumed they were)?
Is the display issue possibly related to poorly seated memory?
I do have big hands and found it difficult getting the ram in the eMac, especially with the sharp(ish) mesh on the underside of the eMac.
I feel this may be related to me seating the memory poorly but that time it booted with the colours all screwed has me worried in case something more is wrong.
I'm currently testing the memory with Remember and all is fine so far (I'm up to the 256 block sequential test so far)
Thanks for reading and apologies for the long post!

Thanks for the suggestion srojtas.
The eMac has been running fine since posting this and completely passed the Remember memory test. I also tested it by filling the memory up by opening many apps and it didn't crash at all there either.
The eMac didn't come with a hardware CD sadly, so I can't test it that way!
I feel now it must have all been due to me not seating the memory correctly.

Low Memory Environment Render Issues...

Howdy folks,
     I've been working on a 13 minute promotional video for a non-profit summer camp. It is made up of mostly still images with some ken burns effects, a narration track, a music track, some titles, and some logo overlays.
     I am doing this on a 3.2 Ghz P4 with only 1.5G ram under XP sp3. I realize this is not an ideal PPro box.
     Windows XP is configured to use 2 drives for VM paging (3Gigs each). All drives have over 100gigs of free space on them.
     Now until recently I've only had a couple of small issues which I suspected were related to trying to do this in a low memory environment. In one case a flash render would die at the same point every time (error was something along the lines of "did not return a valid frame"), and simply scaling down the still image clip at that point in the sequence so that it was closer to the project size took care of it. That method also helped in a few cases where some images would not render at all, and just appeared as black screens in the final video (the render process did not fail, but the end result was missing clips).
     Then there was one case it seemed to fail at random points. A simple reboot took care of that, and it exported just fine.
     But now, however..... Now it's back to failing at random points (sometimes it gets 3500 frames in... sometimes as far as 13400... or anywhere in between) and additionally, by viewing the incomplete flash video file with VLC (which I need to do in order to find out where it failed because PPro never tells me) I find that some of the images are black screens, as before.
     The problem now, is that it's never the same point of failure, and it's never the same images blacked out. And rebooting and or killing off extra processes does not help.
     Now this was rendering fine last week. Here's the kicker - I haven't changed much of anything since then. The project is still the same length, with just about the same number of cuts, tracks, and assets used. The only things I've done since then are:
     1) I duplicated the sequence so that I can make some changes unique to the web-version of the video, and still save the old sequence to go back to. The old sequence has remained untouched and I haven't even looked at it since then.
     2) Created 2 new titles and inserted them in place of some old ones in the new sequence which weren't appropriate for the web version of the video (only the text is different in these new titles... they are the same style, size, etc. as the old ones they replaced)
     3) I shortened some empty time/space/pauses between sections of the sequence.
     So those are all minor changes... but I can't shake the rendering issue no matter how many times I restart or scale down an image that was blacked out or appears at one of the random points of outright failure (again, with the "did not return a valid frame" issue).
     I did notice that after I duplicated the original sequence, the project takes much longer to open. Does having another sequence present in the asset bin use that much more resources? Even if the clips in that 2nd sequence use the same assets as another? I'm tempted to remove the original sequence and see what happens, but I don't want to lose it and have to un-edit the web version whenever I want to go back and re-render the DVD version.
     So basically I'm looking for anything that might cause the small changes I made to be giving me so much grief now.
     Any input is appreciated. Thanks.

You may have a corrupt project. Try creating a new project and importing the old one into it.
If you still experience problems then carefully do each of these troubleshooting tips. One or more of them is likely to help.
Cheers
Eddie

Dreamweaver 8 Design View render issue

I was wondering if anyone else has noticed a highly
irritating issue with DW8 that is apparently not an issue in the
Design View of DW MX 2004.
In DW 8 for some reason I'm getting an extra 150 pixels of
white space to the right of my #content container. It only appears
to happen when the content within the #content container does NOT
exceed the length of the content in my menu container (#priNav2).
In other words, if the content is longer then the menu, it renders
fine.
See here:
Dreamweaver
8
But, in DW mx2004 the exact same file shows up how it should.
Dreamweaver
MX 2004
Does anyone have any suggestions on how to resolve this issue
or have a clue as to why this is happening? It's really one of the
only bugs left preventing me from upgrading to DW 8 anymore.
Thanks,
- Paul

After some tinkering around and a call to Tech. Support I
eventually resolved this issue by pointing out a bug to Adobe.
Apparently the problem is the View / Visual Aids / Invisible
Elements option. If this is turned on, and you have a website set
up similiarly to
this one, you will
experience this sporatic, extranenous white space that shifts your
content around. It is not an issue in DW MX 2004, only DW 8.
The solution is to just simply turn OFF the "Invisible
Elements" option. Then the page will render the way it should.
A bug report has been submitted.

"Adobe After Effects CS5 Render Issues"!

Hey guys
I currently just downloaded the free trial of "Adobe After Effects CS5" and I am wanting to render some video which I added some colour correction to.
When I put this in the render queue and press render is says "You mus have at lease on render item queued in order to render". Also it says on status "Needs output"
How come this is happening, do I need to buy the full vision.
Cheers
ash

You haven't specified the output location or name. After Effects is telling you to do that.
Follow the instructions here.
I strongly recommend beginning here if you're new to After Effects:
http://blogs.adobe.com/toddkopriva/2010/01/getting-started-with-after-eff.html

How to solve issue with strange iphoto events shown in itunes for sync IOS devices ? This issue is very old and not been fixed by apple... terrible

all softwares latest version january 2013.
I see in itunes many strange crazy iphoto events that in iphoto do not exist.
These vents are named as data and contains just few photos.
each event can be sync with IOS devices, but that event is not in iphoto !
It looks like miniatures... no way to solve this issue making all possible maintenance in iphoto library.
THis issue is very old, very terrible, people start to have doubts about iphoto as a reliable software.
Need a fix asap.
Apple please help!
I were with 2 hours at genius bar but nothing.
Genius told me apple have been informed and they are working on a solution..... this 4 months ago !!!
Need solution asap
THanks
Fabio

Apple aren't here. As you're the only person with this problem that I've seen on here, I would suspect that its more a local problem on your machine than something Apple need to fix.
Go to your Pictures Folder and find the iPhoto Library there. Right (or Control-) Click on the icon and select 'Show Package Contents'. A finder window will open with the Library exposed.
Look there for the iPod Photo Cache.
Trash it. Start iPhoto and try sync again.
Regards
TD

Live text template render issue when using Media Encoder?

I'm running into flash frames with Media Encoder exports of Premiere sequences using the live text templates.
Unfortunately, AME doesn't flag it as an error, so the render completes without any issues in the render log and the only way to find it is to watch the rendered file.
I have tried different combinations of having After Effects open or closed, with the live text template comp open or closed; I can't consistently reproduce the problem with any certainty and so am having trouble pinpointing the source.
My only hypotheses so far are that:
The glitches seem to be happening in the dynamic link between AME and PP, not AE and PP. The live text will pop back to the duplicated comp's text for one frame. Video playing simultaneously doesn't pop.
In other words, the AE text template said: "name here". In PP it was edited to say "John Doe", then that comp was duplicated and edited to say "Bob Smith". Everything looks fine in PP. There are no keys on the source text in AE (I have noticed that if there are keys on the source text in AE, the text will pop back to the original AE text at that key in PP).
When rendered out of AME, halfway through Bob Smith's title, it will read "John Doe" for a single frame, then pop back to being Bob.
I've only had this happen so far with AME renders. The renders out of PP haven't given me any issues so far.
It might happen more frequently on longer segments? If a title is up for 45 sec instead of 10 sec, it may be more likely to pop.
The issue seems to occur more often in batch renders out of AME (happened to 3 of 5 files rendered in a batch, AME 2014.1) and/or with unrelated AE comps open (on a single render from AME 2014.2)
Again, it doesn't happen every time or to the same title, or in the same spot. Files are being rendered to ProRes 422 HQ. Unchecked "Use Previews" in AME.
Would be nice to get to the bottom of what's happening so I can recommend something to the editors when I hand off these live text templates to them.
I realize that the live text is a new feature as of 2014.1, but haven't found anyone else talking about this. Would love if this was a very simple fix that I'm missing.
I was able to reproduce the error on 2 different machines, with similar specs:
Premiere CC 2014.1 and 2014.2
Media Encoder CC 2014.1 and 2014.2
Mac tower 2010
2x 6-core Intel Xeon
RAM: 64 GB
Graphics: ATI Radeon HD 5770 and NVidia Quadro K5000 (or K4000)
OS: 10.8.5 Mountain Lion

I'm running into flash frames with Media Encoder exports of Premiere sequences using the live text templates.
Unfortunately, AME doesn't flag it as an error, so the render completes without any issues in the render log and the only way to find it is to watch the rendered file.
I have tried different combinations of having After Effects open or closed, with the live text template comp open or closed; I can't consistently reproduce the problem with any certainty and so am having trouble pinpointing the source.
My only hypotheses so far are that:
The glitches seem to be happening in the dynamic link between AME and PP, not AE and PP. The live text will pop back to the duplicated comp's text for one frame. Video playing simultaneously doesn't pop.
In other words, the AE text template said: "name here". In PP it was edited to say "John Doe", then that comp was duplicated and edited to say "Bob Smith". Everything looks fine in PP. There are no keys on the source text in AE (I have noticed that if there are keys on the source text in AE, the text will pop back to the original AE text at that key in PP).
When rendered out of AME, halfway through Bob Smith's title, it will read "John Doe" for a single frame, then pop back to being Bob.
I've only had this happen so far with AME renders. The renders out of PP haven't given me any issues so far.
It might happen more frequently on longer segments? If a title is up for 45 sec instead of 10 sec, it may be more likely to pop.
The issue seems to occur more often in batch renders out of AME (happened to 3 of 5 files rendered in a batch, AME 2014.1) and/or with unrelated AE comps open (on a single render from AME 2014.2)
Again, it doesn't happen every time or to the same title, or in the same spot. Files are being rendered to ProRes 422 HQ. Unchecked "Use Previews" in AME.
Would be nice to get to the bottom of what's happening so I can recommend something to the editors when I hand off these live text templates to them.
I realize that the live text is a new feature as of 2014.1, but haven't found anyone else talking about this. Would love if this was a very simple fix that I'm missing.
I was able to reproduce the error on 2 different machines, with similar specs:
Premiere CC 2014.1 and 2014.2
Media Encoder CC 2014.1 and 2014.2
Mac tower 2010
2x 6-core Intel Xeon
RAM: 64 GB
Graphics: ATI Radeon HD 5770 and NVidia Quadro K5000 (or K4000)
OS: 10.8.5 Mountain Lion

Render Issues, FCP7 - strange colours

Similar Messages

Maybe you are looking for