Skip navigation

Problems with XDCAM EX Footage

May 21, 2012 2:00 PM

Tags: #cs6 #xdcam #ex-1 #ex-3
  Latest reply: alextheshoe, Oct 3, 2012 9:27 AM
Replies 1 2 3 4 5 Previous Next
  • Currently Being Moderated
    Jul 19, 2012 3:57 PM   in reply to nickdbomb

    Yeah! I received a callback after 3 days, My memory's a bit foggy but I thought Adobe tech support said it would be in the afternoon or next morning.  Unfortunately I was on a shoot and missed the call.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 26, 2012 3:22 AM   in reply to nickdbomb

    EDIT Must have missed a page, after reading back I see that someone already tried and still has the problem.

     

    "I talked to technical whizz who works for a tvstation. He said to try and import the files using the the mediabrowser. And you must have copied the entire directory structure of the card, so basiscally the BPAV folder and import that.The mediabrowser apperently imports it different then import folder from the menu. I havent installed CS6 to test it yet, I have some projects to finish. Has / can someone test this?

     

    greetings"

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 26, 2012 3:24 AM   in reply to Tkoopmans

    As far as I remember it did not do any difference for me. Someone said in this thread that if you, like me, have Canon XF media, you should export the media from the card using the Canon XF utility and then import them into Premiere. Someone tried it, and apparently it worked. I am not sure if the Sony utility has the same option, but my guess is that it would have an option like that, that also join spanned clips.

     

    I have not had an awfull lot of time to test, so I have trancoded to UT / AVI files until now, but I might get some more time to test more soon.

     

    /Ulf

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 26, 2012 3:42 AM   in reply to UlfLaursen

    Not any help I know, but I have just produced a 80min classical music video shot on an EX1r and a PMW 320 using about 700 clips recorded as EX footage 1920x1080 25i and have not had any picture trouble. I always copy the video from the SXS cards to the local Hdd using Sony Clip Browser and I then import into Premiere CS6 using the Media Browser.

     

    Richard

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 26, 2012 4:02 AM   in reply to Richard M Knight

    Yeah - I think that is the same someone else suggested to do with the Canon util, so apparently it also works with Sony.

     

     

    /Ulf

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 20, 2012 8:02 AM   in reply to Richard M Knight

    More XDCAM EX coming my way, so had to dive in this problem again. (Had the problem earlier with only a few EX clips in a HD422 project, so I just transcoded those few clips)

     

    Googling around I got:

     

    - A workflow recommendation from Sony for Premiere CS3

    - The XDCAM Browser program. (Mac, v2.1)

     

    The recommendation from Sony for XDCAM EX in Premiere is to go through the XDCAM Browser.

     

    I used the function "XDCAM for NLEs" (rightclick on a clip, choose "Export" then there are a few options)

     

    As far as I understand this just rewraps the .MP4 to .MXF files without transcoding.

    The MXF files created can be imported in Premiere. Since using these MXF files, the tearing problem seems to be gone.

     

    One seems to loose some (all?) metadata though, compared to importing from the BPAV structure directly. Not sure if this is a setting within XDCAM Browser.

     

    For me this workflow solves the problem for now. Also the direct imported files always got the yellow renderbar in premiere, the new MXF files don't.

     

    Does anybody have any idea why the metadata doesn't come across?

     

    Best regards,

     

    Carl.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 20, 2012 9:38 AM   in reply to Carl Schuurbiers

    Simply dragging clips to a folder also works, it creates a new BPAV structure in the specified folder. When this folder is imported, all metadata is preserved, and so far I have seen no tearing.

     

    So the answer seems to be to first copy XDCAM EX footage through the XDCAM Browser to a newly generated BPAV structure and to import that into Premiere.

     

    For some reason the EX footage in MP4 container always gets the yellow render bar? The same EX footage rewrapped in MXF doesnt get the yellow bar...

    Can someone confirm that using the export->"MXF for NLEs" option does NOT transcode, only rewrap?

     

    Best regards,

     

    Carl.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 20, 2012 10:20 AM   in reply to Carl Schuurbiers

    I arrived at this thread late - I have never worked with XDCAM footage before and have an edit starting tomorrow with footage from a Sony EX-3.  Are people having issues with simply ingesting the footage through Prelude - not sure what the re-wrapping, XDCAM browser, etc is all about.

     

    Is this yet another case where Premiere doesn't do what it is supposed to - simply bring footage in and edit it? 

     

    I'm on a Mac - are the problems cross-platform?

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 20, 2012 11:16 AM   in reply to needles27

    It is an Adobe aknowledged bug that is inconsistent, intermitent and cross platformed.

     

    The bug appears on my desktop PC but not my HP laptop.

     

    Keep your fingers crossed and hopefully you won't have a problem.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 12:04 AM   in reply to Carl Schuurbiers

    CARL SCHUURBIES WROTE:

    Simply dragging clips to a folder also works, it creates a new BPAV structure in the specified folder. When this folder is imported, all metadata is preserved, and so far I have seen no tearing.

     

    So the answer seems to be to first copy XDCAM EX footage through the XDCAM Browser to a newly generated BPAV structure and to import that into Premiere.

     

    For some reason the EX footage in MP4 container always gets the yellow render bar? The same EX footage rewrapped in MXF doesnt get the yellow bar...

    Can someone confirm that using the export->"MXF for NLEs" option does NOT transcode, only rewrap?

     

    Best regards,

     

    Carl.

     

     

    Can someone confirm that this is the solution for every system?

     

    Hope to hear from you, so that I can start using Prem Pro CS6 I bought months ago...

    (Am still working with 5.5 for this bug)

     

    Regards,

    Christiaan

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 12:27 AM   in reply to Arts Emotion - C. Vink

    XDCAM EX Browser can be found in the Version 2.6. But I did not find it on a Sony site.

     

     

    On Sony I found this:
    http://pro.sony.com/bbsc/ssr/micro-xdcam/resource.downloads.bbsccms-as sets-micro-xdcam-downloads-XDCAMSoftwareDownload.shtml#apps

    EXCAM (No ex) browser 2.1

     

    Can this be used for my ex3 to hopefully solve the tearing?

     

    Regrads,

    Christiaan

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 4:42 AM   in reply to Arts Emotion - C. Vink

    Did some more tests:

     

    Test material: A folder containing a BPAV folder that was copied directly from an SD memorycard recorded by a Sony EX3.

     

    Imported this folder directly in Premiere -> tearing.

     

    Opened this folder in XDCAM Browser, copied the clips to a new folder with XDCAM Browser, imported the resulting copy in Premiere -> NO tearing

     

    For me this seems to solve the problem. The copy looks the same as the file structure that was copied from the camera, but the result in Premiere is different. Importing was done selecting the folder in Media Browser in Premiere, and dragging the clips to a bin, resulting in an import.

     

    Also the metadata comes across. The only thing I don't understand is why we get the yellow render bar, and with HD422 footage not. It's the same MPEG2 Long-GOP codec, but at different rates/levels, is the difference that big? Anyway I'm happy that I can now use the footage and don't need to transcode.

     

    It would be nice if some more people could confirm if this workflow works for them too, because of the intermittent nature of this bug.

     

    Carl.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 7:27 AM   in reply to Carl Schuurbiers

    Hi Carl,

     

    I will test this in a couple of days with my EX3 and premiere pro CS6. I'll let you know.

    Thanks for your post.

     

    Regards,

    Christiaan

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 7:36 AM   in reply to Carl Schuurbiers

    Thanks for testing but the real rub is the hundreds of clips already in the RAID archive not on the SxS cards.

     

    For new projects, Ill test your workflow and post results.

     

    It would be a long painful proceedure to rebuild each clip in a CS5.5 projects from scratch for CS6 using the Sony XDCAM browser.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 7:44 AM   in reply to nickdbomb

    You're right Nick.
    ADOBE... Please help all of us who bought your CS6 software and can not use it!

    Looking forward to that moment!

    Kind regards,

    Christiaan

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 8:51 AM   in reply to nickdbomb

    nickdbomb wrote:

     

    Thanks for testing but the real rub is the hundreds of clips already in the RAID archive not on the SxS cards.

     

    For new projects, Ill test your workflow and post results.

     

    It would be a long painful proceedure to rebuild each clip in a CS5.5 projects from scratch for CS6 using the Sony XDCAM browser.

     

    Assuming you have the clips in their BPAV folder: Make the clips offline in Premiere. On the RAID: Move the clips to a different folder. Open this folder with XDCAM Browser, then copy the clips back to their original location WITH XDCAM Browser. (So you replace the "original" files with a copy made by XDCAM Browser. Then in Premiere relink the media. You can probably also just make the copy and start Premiere. It will probably complain and ask for the files. Not sure exactly how I did this, what it comes down to is:

     

    You don't need the original cards, just make a copy of what you already have on your RAID through XDCAM Browser.

     

    Be sure that your footage is in the correct folder structure:

    /whatever/BPAV/CLIPR etc. If it is right, XDCAM Browser will recognise the folder when you select it and display the clips, which you can then drag to a new folder. XDCAM Browser will create a new BPAV structure in the directory you copy to. So you (seemingly) end up with the same you had before. They have just been "touched" by XDCAM browser.

     

    Carl.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 8:58 AM   in reply to Carl Schuurbiers

    Does anyone have any solutions other than transcoding for when the files have been stored outside of their card folder structure?  We have thousands of clips sitting in archive folders, just as mp4 files,  we always pulled them off the cards as files when dumping them to laptops in the middle of shoots - and now we're having nightmares trying to transcode loads of clips when we need to use older footage.  We can't even go back to cs5.5 now as two of our workstations only have cs6!  Aaarrrgh.  I've already screwed up two client deadlines because of this.

    Ben

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 11:25 AM   in reply to BenForder

    FYI,  Over a month ago Adobe tech support told me the bug has a number it is MAKePCS6. 

     

    Is Adobe still working on a fix?

     

    Are we a ball of wet laundry left in  the corner to dry forcing us to iron out the wrinkles Adobe has perminately created?

     

    Should I switch my career to screen writing?

     

    Must we deal with FUBAR situation on our own?

     

    I haven't missed a deadline yet but worked through a few weekends and many long nights that would not be necessary if this bug was fixed. 

     

    It's not so easy to find and fix the files using the XDCAM browser. I've evolved my EX1 workflow starting in CS4 when I would copy the contents to portable hard drives in the field then in the studio to a mirrored array for long term storage then to a striped array for editing.  I recently added a RAID 10 array that new video is being transferred to for long term storage and burned to Blu-ray discs.  Some of the files on the drives have been saved only as MP4 outside of the wrapper.

     

    I've been hoping for a fix so I won't need to angonizingly rebuild all my thousnads of archived clips on all those drives.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 11:33 AM   in reply to nickdbomb

    Since Adobe is licensing some codeks from MainConcept, this might not be entirely in Adobes hands. And rest assured that if there was an easy fix, we'd already have it. It's is very hard to get to the root of this problem. Not all users have the problem. Some do, but not always on the same material. And the amount of tearing varies with the import method.

     

    Too many variables for easy problem solving. :-(

     

    /jarle

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 2:41 PM   in reply to Jarle Leirpoll

    Im sorry Leirpoll, it wasnt broke in cs5.5 so that means Adobe broke it in CS6. If it aint broke dont fix it. Put simply all the extra coding has broken it somewhere and for Adobe to take nearly two months with out any solid info or updates just excuses that they are working on says alot, the programmers must be either bloody slow OR Adobe hasnt prioritised this meaning they dont care....simples ... squeek!

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 3:13 PM   in reply to Jarle Leirpoll

    It would be nice if some people could at least confirm that the workaround that I mentioned works consistently at all. We need to know if we have a functioning workflow or not. At least for new projects and people transitioning to CS6.

     

    Otherwise I'll be transcoding anything XDCAM EX to ProRes.

     

    The whole thing sucks of course, I'm also not happy having to spend so much time troubleshooting, but somehow we need to move on...

     

    So if some people that do have the tearing problem and BPAV folders, could they please see if this fixes the problem for them? For the moment it seems to work for me.

     

    Why do I have a feeling I am repeating myself? Oh well.

     

    Thanks,

     

    Carl.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 4:04 PM   in reply to Roddy Mc

    Roddy Mc: What makes you think that MainConcept never updates their decoders? MPEG decoders have become much more efficient over the last few years. The one in CS6 may be different from the one in CS5.5. We don't know. MainConcept knows. Not trying to put the blame on them, mind you. The world isn't black and white. There are many shadows of gray. What we do know is that their current decoder (if at all involved) doesn't work with CS6. I know several Adobe employees, and I can assure you they're as frustrated as we are. And I'm sure theat MainConcept employees are too.

     

    Like many others, I've contributed to the solving of this problem by sending in problematic files and projects, filing detailed bug reports. I have gotten a lot of questions back from the Premiere Pro team, so I know that several knowledgeable people are working on this. So to state that they're not doing anything, or working slowly, is just wrong.

     

    I repeat: If this was an easy fix, it'd already been in our hands.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 4:34 PM   in reply to Jarle Leirpoll

    And as I stated earlier it wasnt broke? As you will well know the software has been released with a major flaw for many users who are having to use work a rounds or back up footage waiting for a solution.

     

    I dont see any press release from Adobe stating their software is flawed for users of XDCAM or HD MXF files so if your using that format of footage beware you will have to use a work around in cs6!

     

    Its leaves on the track syndrome, your train is late but all your told is there are leaves on the track. But your not aware that the leaves break a connection in the motor room stating you dont have full connectivity to the tracks therefore safety dictates a speed of 30mph no more hence late train!

     

    If adobe were more professional AND cared about those needing to update to use lets say more than 4 cameras in a shoot, anti stabilisation or what ever the latest addon in cs6 they should have thoroughly tested the software before making claims like " its made by professionals for professionals" It isnt professional by a long way, full of bugs crashing stabilisation, bugs in multicam and of course the main issue here tearing appearing in footage from certain formats.

     

    I lost a week due to this issue and had to re-edit a massive production in a previous version. I asked if i coud have an extention on a trial version and didnt even get a reply!

     

    I have submitted examples, from the very start of this issue arising.

     

    Its broke, shouldnt have been released broke and now that it has been released should have been fixed within 2 months! along with updated statement as to progress, hell even the community has to provide footage for them to recreate the tearing issue that says alot to me!

     

    Not being able to fault find the issue from working previous software also says a lot to me.

     

    Yes I am a programmer and im not very impressed at all!

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 4:36 PM   in reply to Jarle Leirpoll

    Leirpoll,

     

    Thanks for the update.  Is it Possible Adobe for marketing reasons, is not keeping it's user informed on the progress of this bug?

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 4:48 PM   in reply to nickdbomb

    We know this has been a big issue for many users and are working on addressing it as soon as we can. We are sorry that this can take a while but every change has some risk and we need to ensure these things do not introduce unintended consequences.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 5:00 PM   in reply to nickdbomb

    nickdbomb,

     

    Your guess is as good as mine. But I can't see how this can help their marketing...

     

    Roddy Mc,
    There are a LOT of beta testers that did not find this bug before release. I am one of them, and I use almost exclusively XDCAM-EX material. Blame me, not the programmers! I've edited shundreds of hours without encountering this bug. If this bug had been easy to reproduce CONSISTENTLY (as a programmer you must know how important that is) and track down it wouldn't have been there in the first place.

     

    As a programmer you also know that you can't just put in some old code when the rest of the app has been changed and updated. So I interpret your "attack" on Adobe's programmers as frustration.

     

    That's understandable. We all agree it shouldn't be broke. But "dissing" the people who work on this is not overhelmingly constructive. If you're better than Adobe's programmers, I salute you. They've made a piece of software that has helped me earn a huge part of my money. I'm hoping they'll fix this issue very soon.

     

     

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 6:24 PM   in reply to Jarle Leirpoll

    Hey Nick, I think your right, frustration is getting the better of me. Regarding old code comment, a good programmer will structure his code so he can more easily identify a problem if one arises and I think from the many comments alone in the forum the problem is being identified not that we are being told.. I think first yes you have to identify the problem then your armed to fix it! Im ex games industry and run two businesses now and if I had released some software that was causing many people a problem I would keep them informed on a regular basis as to any progress. I personally hate vague statements, they sound insincere however from a marketting/sales point of view I can also appreciate keeping information under your hat. I havent upgraded for the simple reason I can't use this software on XF100 or Xf300 MXF files due to tears in the video. I posted at the beginning of this thread with examples only to suddendly see many were in the same boat. I have been an Adobe Premiere advocate since it first came out and just roll my eyes to see others taking the lead with multicam, stabilisation etc. I can assure you there is no malice in my statements just it been a long time since launch and still no closer to a solution at least from what we have been informed. As you will see from the last statement its not been addressed properly yet?

     

    I have many friends in thel filming business  who are also reluctant to upgrade because of the same problem from pcs to macs and common sense says fix it and more sales will follow. It doesnt cost anything to be forth coming about any progress however no official statement make you think there isnt any progress.

     

    I dont proclaim to know everything but I do know if enough people kick up a stink about a problem it gets noticed.

     

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 8:26 PM   in reply to Roddy Mc

    I would keep them informed on a regular basis

     

    You have to consider that Adobe is a publicly traded company.  The law in the U.S. is a rather twisted, asinine monstrosity that actually considers investor profits a higher priority than customer service, and so forbids certain types of communications.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 8:42 PM   in reply to SteveHoeg

    SteveHoeg wrote:

     

    We know this has been a big issue for many users and are working on addressing it as soon as we can. We are sorry that this can take a while but every change has some risk and we need to ensure these things do not introduce unintended consequences.

     

    Thanks Steve - keep our fingers crossed for a soon solution

     

    /Ulf

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 10:59 PM   in reply to SteveHoeg

    SteveHoeg wrote:

     

    We know this has been a big issue for many users and are working on addressing it as soon as we can. We are sorry that this can take a while but every change has some risk and we need to ensure these things do not introduce unintended consequences.

    Big issue? Yup, a show stopper for many. Do the product managers know what a BFD this is? Do they need to get phone calls asking for statements on the bug from video production publications? If this were a priority, something would be done in the last 3 months.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 27, 2012 1:02 PM   in reply to Stephen_Spider

    Big issue? Yup, a show stopper for many. Do the product managers know what a BFD this is?

    Yes.

     

    Do they need to get phone calls asking for statements on the bug from video production publications?

     

    No. That won't expedite a fix.

     

    If this were a priority, something would be done in the last 3 months.

     

    Something is being done. Please stay tuned.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 27, 2012 10:54 PM   in reply to jstrawn

    Well thanks for replying at least. I'll try to refrain from venting for a while. Good luck with this.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 29, 2012 3:30 AM   in reply to Stephen_Spider

    Hoping for a soon update! would be very welcome!

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 29, 2012 6:42 AM   in reply to Arts Emotion - C. Vink

    Oh my, the original EX issue was first discovered/reported on this forum in May. It's the end of August! Wait just a few more months, and we'll all probably get the wonderful opportunity to upgrade to the all new CS 6.5!  Will EX footage work in that version? Well, testing that functionality is just part of the excitement you get when purchasing the upgrade! Oh, and then, well, when things don't work "optimally", you'll be told it's because of your 'outdated hardware', which, of course, used to work just fine with previous versions. (For now, I'll crawl back under my rock, live in my happy little CS 5.0 world, editing EX with my outdated machine, thank you very much...)  Now, if only the ADBE shareholders read this forum!

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 29, 2012 2:21 PM   in reply to Ed Edited It Productions

    Unfortunately CS5 world is the only world for many of us and if what you say is true ie the update comes in a newer version of Premiere ie cs6.5 or 7 or what ever the next launch is I will change NLE on principle, I already know many of my collegues and friends share the same sentiment based on v.6 being unusable and to have to pay an extra premium to be able to use MXF and XDCAM FILES would quite franKly be an insult to the user/adobe client. A provission should be put in place for all those unable to use cs6 concerning this serious issue if its not rectified prior to a new launch.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 31, 2012 9:38 AM   in reply to Roddy Mc

    Having all your eggs in one basket isn't a good business plan especially when the basket has a flimsy handle. I am a Adobe Certified Expert PPCS5 video editor and feel that having skills with whatever tool that is required for the project will bring me more work. 

     

    Premiere Pro is building a user base but many professionals in entertainment are still standardized on Avid and some FC. This might be a good time for me to add Avid to resume.  By the time I learn it, Adobe might have a fix for XDCAM users and I'll be more professionally flexible. My budget will allow me to buy a new computer and this time I will choose hardware required for AVID.  Not because I have lost faith in Adobe Premiere Pro but it makes sense for me to have additional skills. 

     

    I must thank Adobe for giving me a reason to build my expertise using another video editing system. CS5.5.2 is on one of my computers because CS6 is incompatible with it for who knows why? For unknown reasons, my Laptop is running CS6 Production Premium just fine  and I use it for projects that I import Illustrator files into After Effects then export the video so I can use it in Premiere Pro CS5.5.2 or soon, AVID

     

    Any recommendations for a modest AVID configuration would be greatly appreciated.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 31, 2012 9:58 AM   in reply to nickdbomb

    Any recommendations for a modest AVID configuration would be greatly appreciated.

    If you're serious, please start a new topic in the Hardware Forum.

     

    Jeff

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 6, 2012 1:41 AM   in reply to digitalkiln

    The Premiere Pro CS6 (6.0.2) update is available. There are a lot of bug fixes in this update, as well as HiDPI functionality for Retina Display, some new supported GPUs, and Windows 8 certification.

     

    One of the fixes in this update is for tearing in XDCAM EX footage. Try the update and let us know how it works for you.

     

    See this page for details about this update:

    http://bit.ly/PremierePro602

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 6, 2012 2:30 AM   in reply to Todd_Kopriva

    Is there also a fix for MXF files video tearing ergo Canon XF series?

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 6, 2012 2:33 AM   in reply to Roddy Mc

    I'm not certain whether the update addresses tearing in Canon XF footage. I'll have to check. In the meantime, I recommend installing the update and seeing for yourself. There are a lot of major fixes in this update, so it's highly recommended for everyone using Premiere Pro CS6.

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (2)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points