ProRes Render Issues

I am having an issue with ProRes movies rendered in After Effects and imported into Premiere Pro. They don't seem to work very well since the last update.
Specifically, the movies barely play in the timeline and they lock up the program when I try to render them. I have also had problems playing them back on the desk top.
The work around for me has been to render to ProResLT. These have been working fine.
I have not had any problems with raw footage files (Sony AVCHD converted using ClipWrap to Premiere Pro PreRes).
Thanks,
Benny Christensen
Producers Playhosue
Oklahoma City

Hi Benny,
We need more info: FAQ: What information should I provide when asking a question on this forum?
Thanks,
Kevin

Similar Messages

  • 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.

  • ProRes Render time issue

    I hear a lot about the benefits of ProRes so I decided to change my workflow from HDV to ProRes.
    I am trying to Render 1 hour footage and its saying its going to take 6 days!!! whats going on? I am running a MacBook Pro 2GB Ram and connected to a Firewire 800 external drive.
    FCP 6.0.5
    am I doing something wrong?

    Hello,
    reading and writing from the same disk will slow down the export. Try exporting to the local disk instead or a second external disk.
    Apart from that I recommend trying to restating the export process several times. With me it sometimes tells me 6h for a 10min clip and the 5th time round 6 minutes. Sometimes I even restart if the machine has been running and rendering for a few days.
    Hope that helps...

  • 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

  • Round Trip and Render issues - Color back to FCP

    Graded, rendered, send to FCP. Looks good on the timeline, minor issues with some variable speed clips and sound (for some unknown reason) but i had duplicated timelines and was able to gather everything onto one timeline and each clip plays back fine, but i can't really get a good read thru, the timeline after about 5-7 secs will start to hold up. I think maybe its having a problem playing back the rendered files off the internal harddrive and the firewire 800 drives I use for capture scratchs. So I export a self-contained movie file and it won't play without stopping in either quicktime or FCP. I can't figure out what the problem may be or how to fix it. My next call is apple support but i figured maybe one of you esteemed gentleman may be able to see the tree in my forest. Thanks, Steve

    Michael Trauffer wrote:
    but i figured maybe one of you esteemed gentleman may be able to see the tree in my forest.
    I see a lot of trees here, so I'll grab my chainsaw and start swinging away
    I appreciate that, as here in south louisiana we keep our chainsaws oiled and ready to roll
    Graded, rendered, send to FCP.
    I follow you up to this point. I'm assuming you're using XDCAM EX footage?
    Yes
    Looks good on the timeline, minor issues with some variable speed clips and sound (for some unknown reason)
    I should point out here that it's been documented on numerous occasions in this forum that Color doesn't necessarily play well with variable speed clips. The Color User Manual has a section on page 75 that shares some steps that should be performed before sending a sequence to Color. One of those steps is baking a variable speed clip into a quicktime movie.
    Gotcha, I actually did that to solve that issue.
    but i had duplicated timelines and was able to gather everything onto one timeline and each clip plays back fine,
    Sorry, I can see how this can be confusing. What I meant to say that is when i had the weird audio issue (it sounded as if the stereo pair were out of sync with eachother, giving it a wierd audio reverb even though i could not visually identify from any information available on the timeline) I then overwrote those audio files and that fixed it. But all this was on the initial sequence timeline that i had loaded from color after the grading.
    but i can't really get a good read thru, the timeline after about 5-7 secs will start to hold up.
    Define "read thru". If the sequence is dropping frames, it sounds like a bandwidth issue with your scratch disks, or a hardware setup problem.
    Yes dropping frames is exactly what it was doing...I am running a quad-core xeon with 2.8ghz, with 4 daisy-chained firewire 800 drives.
    I think maybe its having a problem playing back the rendered files off the internal harddrive and the firewire 800 drives I use for capture scratchs.
    How many drives do you have designated as capture scratches?
    I have one folder on one of the 800 drives designated for this project. In color I chose a different 'render Directory' on the internal hardrive (i believe it was a default)
    What specific drives are you using?
    Lacie 500gb drives
    If by "internal harddrive" you mean your system drive, this is a big no-no. I can only assume here, but I think you're working with ProRes material at this point. Depending on your specific Mac, the internal drive may not be up to the task. If you consider that that drive is running your entire OS, plus any open application, plus Final Cut Pro, plus accessing the render files, plus any other source material that you may have stored on that drive, you're asking that one drive to do a whole lot of work.
    I get that. But should i change Color's render directory to somewhere in the project folder on the Lacie Drive?
    So I export a self-contained movie file and it won't play without stopping in either quicktime or FCP.
    A self-contained movie file of what?
    The sequence.
    How are you exporting?
    FCP export > quicktime Movie > What are your sequence settings?
    Xdcam 720p30 project settings based on xdcam clips, 1280 x 720
    Open the file in Quicktime Player, and press Command I to open the Info Window. Make a note of the format information and post that information here.
    I wish i could and I will when i get back to the office after dinner.
    Chainsaws can get pretty heavy after a while. I'll take a break here and see if I hit anything of value.
    I think you did...but confirm for me. Color's render directory, whats a better place for it? And thanks for the quick response it is duly appreciated.

  • Audio Render issue - Media Encoder

    Hello All,
    I just ran into a odd audio issue after a render.  Anyone have any idea as to why this is happening?  (audio file below)
    Sequence is :  ProRes 1080p 2997.   Rendering to ProRes.  Audio source is a .WAV
    http://www.rtbstudio.com/Clients/AudioError.aif
    Additional testing has shown that the issue only occurs when I render out of Adobe Media Encoder.
    Rendering straight out of Premiere does not produce this issue.
    Thanks!
    - Ryan
    Premiere 7

    You are correct Jim,  I was in a bit of a hurry and didn't check my language.
    It is on exports.  Odd thing about this, it only gave me an audio issue when 'exporting' to ProRes.  I did a multitude of client review Quicktime H264's and never had the issue.  Even with the 'Native Premiere Support' checkbox enabled. 
    It appears de-selecting the 'Native Premiere Support' option works for the prores.
    Will Adobe ever address this issue?  This issue makes me really nervous when exporting batches via AME.
    Cheers!
    -Ryan

  • 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

  • Render Issues - Vertical lines

    Speed Grade sure knows to handle CinemaDNG, realtime playback, very smooth, ...
    But when I render, the result has a vertical striping pattern all over the image. And it happens with every output format possible (DPX, ProRes mov, H264 mov, CineForm, ...).
    I've attached an example. The Vimeo compression seems to make the issue a little bit less noticeable, but the source files show big stripes.
    I do not have this issue with any other CS6 application.
    Any idea what may be causing this. A setting I'm overlooking?

    Can you give me some infos about your system?
    Also attaching your projectfile would be very helpful.
    Thank you in advance
    Duy-Anh

  • 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

  • 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.

  • Any fix for CC render issue with the new MacPro Firepro D700.  Getting lines and flicker as documented in threads

    Hi,
    We're facing some critical problems with our new MacPros, CC, and the Firepro D700's.   It appears that after we upgraded to 10.9.3 the D700's no longer work with Creative Cloud.  Our Premiere renders are full of artifacts, lines, and drop out.   Same issue as documented in RENDER PROBLEM - AME and Premiere Pro CC causing random horizontal lines on H.264 Renders     Can you advise as to when the fix will be pushed?  We have turned to "software only" render, which is killing us for time.  We have a huge amount of work that goes through 4 edit bays and its putting us days behind.
    Please let us know,
    Sincerely, Jim Janicek
    Janicek Media, Inc.
    720-891-6276
    [email protected]

    You need to ask in Community: Premiere Pro | Adobe Community but do not expect Adobe to discuss future plans
    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform for bug reports or feature requests
    This forum is about the Cloud as a delivery process, not about using individual programs
    If you start at the Forums Index https://forums.adobe.com/welcome
    You will be able to select a forum for the specific Adobe product(s) you use
    Click the "down arrow" symbol on the right (where it says All communities) to open the drop down list and scroll
    Also, this is an OPEN forum, not Adobe support... please do not post personal information

  • UI Problem: Tab render Issues on page navigation

    Hi All,
    I am with a ADF application using jDev11g where i have some JSF pages and have navigations between those pages.
    In the first page i have two tabs.
    In the second tab of that page I have put the ViewObject (ViewObject is based not base on Query, ie. not on any Entity Object) attributes as input text fields.
    After that i have a Search page next where i search on some conditions and from the result table I select a specific row and catch its column values. Using the row record I populate the viewObject of that first page while clicking on a button on the second page (this button calls a AppModuleImpl class method to populate the ViewObject).
    Till this it works fine. But there are some UI related issues associated with it.
    Query--1:
    Approach 1: As i have dropped a View Object as inputText and it is not populated on on the first go it will have label field but the value field will not be rendered at all. But this doesnot meet the UI requirement. I need to have a value field (white box with no data). How to resolve this? Are there any property for that to render.
    Please suggest.
    Work Around: For this problem i applied a work around by dropping some extra input texts beside the VO attributes (as text field without label) in my 2nd tab of first JSF page. And while navigating to second page i made these extra i/p fields as hidden (through Disabled/Rendered property) in the backing bean.
    Then i populate the ViewObject from second page and returned to the first page(default goes to first tab) and opened the 2nd tab i found all the extra nput text fields visible which i had disabled. Can you tell why it's happening?
    Please suggest for these 2 approaches.
    Query--2:
    Is there any way that when i navigate back to the first page by default the second tab will open instead of the first?
    Please suggest.
    Thanks in advance.

    Hi,
    Query--1:
    Approach 1: As i have dropped a View Object as inputText and it is not populated on on the first go it will have label field but the value field will not be rendered at all. But this does not meet the UI requirement. I need to have a value field (white box with no data). How to resolve this? Are there any property for that to render.
    Please suggest.
    an input field need an object to write to to display the input area (otherwise its read-only). So you can create your input form pointing to a managed bean initially any then, when users enter and submit data, save it manually in ADF and after this hide the bean bound fields and show the ADF fields. Or - before getting onto the page - you create a new row if the current collection is empty.
    Short answer: there is no declarative way to do this
    Is there any way that when i navigate back to the first page by default the second tab will open instead of the first?
    Please suggest.
    The ShowDetailItem component that is used to render tabs has a Diclosed property that you can point to a managed bean method. When you navigate back, you have the managed bean returning false for all but the second tab.
    Frank

Maybe you are looking for