Resolution View = Export Quality?

I was under the impression that Render Quality (Draft, Normal, Best) determined the export quality, and that Resolution View (Full, Half, Quarter) was for Canvas viewing purposes only. Am I wrong?
Thanks,
Zak

I'm not sure if I've seen it do that before or not. There were a couple of times where the export size was inexplicably lower than the project, but I don't remember if resolution view was the cause.
You can just uncheck the "same as project settings" checkbox and settle it manually. I always export in that fashion because I'm forever turning off Motion Blur, lights, etc. and it's a good way to make sure it exports correctly.
Andy

Similar Messages

  • So what's the export quality like???

    Hi, after the 'pain' of i-movie 8, what's the view on the export quality in 9?
    Does it export high enough quality to look good when burnt to dvd and played back on tv?

    Welcome to Apple Discussions!
    It looks the same as iMovie 08.
    I did a compare one day using the same clip burned to DVD from iMovie 06 and from iMovie '08.
    The iMovie 06 clip looked like it came from the DV camera directly and the iMovie 08 clip looked much worse. The difference is the single field processing used by iMovie 08/09 and the fact that it throws out every other horizontal line.
    Because the two softwares handle the imported video differently - single field processing is how iMovie 08 / 09 handles the video, meaning that one of every two lines of the image is ignored. iMovie 06 uses ALL of the image to form the video.
    If your primary workflow is editing DV clips and making DVDs, iMovie '06 is better suited. Your movie will arrive at iDVD in DV format, which is an ideal match for making a DVD: same resolution, same pixels aspect ratio, and original quality. If you share your movie from iMovie '08 / 09, it gets re-rendered at 640x480 or less, and then iDVD upscales it back to 720x480. The end result is obviously not as good.

  • Youtube Export Quality

    Is the youtube export quality improved in iMovie 09? Is 640x360 still the maximum size for direct upload to youtube?
    Thanks,
    Shawn

    Is the youtube export quality improved in iMovie 09?
    iMovie has little to do with the end quality of files other than determining the size/duration/quality of the files sent to YouTube. All files sent to YouTube are converted to FLV by Youtube. This conversion by Youtube itself determines the final resolution/quality of your files. If quality is what you seek, then it is probably best to create your own website and post your video at the resolution and level of quality which you can manage yourself. YouTube and similar sites aim for compatibility of viewing -- not quality.
    Is 640x360 still the maximum size for direct upload to youtube?
    I don't believe there are restrictions on resolution -- just duration (10 minutes) and file size (1 GB). Whatever you upload will be re-compressed to fit in the 1 GB file size limit. Higher quality means shorter times. Larger files usually mean more compression to fit it within the YouTube file size restriction. Your best bet is to review the Help resources area at Youtube.

  • Export quality grainy for TEXT / TITLE

    Hello there,
    Am kind of a newb, but am getting used to the basics and am happy with the video export quality. For some reason, the TITLE objects are coming out grainy, even when viewed at 100% size. I tried different output types, bitrates, changed fonts, font size, position, etc. Put black background behind, removed background, no matter what am still getting the fonts looking crappy once exported.
    Some screenshots of what I see in the Premiere Pro output preview / workspace, and then a second shot showing the resulting output (same result in diff bitrates, just chose one as example)
    In Pro:
    http://fms.whoajack.com/textIssue01.png
    Exported:
    http://fms.whoajack.com/textIssue02.png
    Any ideas?
    Thanks for any suggestions,
    Greg

    DV is far from the best codec for text. But the real problem is that you're using FCP's built-in text generators. Instead, use the Boris Title 3D and Boris Title Crawl generators. They produce much cleaner vector-based text and have a ton of more options for creativity.
    -DH

  • Losing resolution when exporting...

    I have made a few movies using photos and video clips set to music. When I export them, either using Quicktime or sharing them with iDVD, they lose a lot of resolution. Is there a way to burn these movies to DVD without losing quality?

    I used the Ken Burns feature on every photo (70 total). Some of the photos are 3264x2448(8MP), most are 2592x1944(5MP), and a few are scanned photos size app. 2711x2033.
    Okay. Would assume the still are being stored in your project as 1920x1440 frames. (You can check this out for yourself and I don't know if working in PAL mode would be different that NTSC.) In any case, the stored image resolution will be the limiting factor for export resolution.
    When finished, I exported the video in Large size 720x576. At this resolution the quality was very deteriorated.
    Just finished making a dozen runs duplicating your work flow in Compressor Native PAL, Compressor Native NTSC, 768x576, 640x480, etc. and cannot duplicate you problem without doing something like using a filter to overdrive the contrast like this:
    Preview in iMovie '08
    Output in QT Player
    Output w/Overdriven Contrast in QT Player
    Apple Care recommended that I share with iDVD, but I got the same results. Then I started experimenting with Quicktime, which is where I am now. I have tried several different sizes, including my own concoctions with the custom function (1382x1036 is what I'm exporting at now, I want to keep a 4:3 aspect ratio).
    As indicated above, you can open your project folder and check the "Still Images" QT file which contains your stored photos to see their resolution. Max resolution depends on your project import settings (e.g., 1920x1080, 960x540, etc.) and their orientation. In any case, this is the max height resolution to which you can export your project at optimum quality for its aspect ratio. Remember, however, that whatever resolution you export your project to will later be re-scaled in iDVD down to 720x576 (PAL) or 720x480 (NTSC) for burning to DVD. If you think the increased processing time is worth whatever increase in quality you may achieve, then go for it.
    The resolution looks acceptable (once I shrink the movie down to fit on the screen), but as I mentioned the color saturation is too high. In the quicktime filters, I adjusted the saturation down to 80 percent, and reduced the red by 5. Still waiting on the results...
    Still haven't a clue here.

  • IMovie vs FCPX export quality

    Afternoon/morning all.
    Question I have is regarding the export quality of FCPX vs iMovie!!
    I've been using iMovie for over a year now but only recently started to publish my work.
    I get on with iMovie great but the one issue that let's it down is the export quality, it's been driving me crazy but after finally looking into it seems that iMovie is the problem and reduces the footage quality.  
    I'm just thinking about upgrading to FCPX the extra editing features and functions will be great too.
    I just want to know that the exporting footage in FCPX won't reduce the quality of the footage!
    Can anybody help!!
    Thanks

    'quality' is a very complex issue.
    Most consumer IMPORTS do look nice, when the cam is connected straight to a telly.
    … but those recordings contain tons of 'flaws'. (low bitrates, artefacts due to wrong exposure etc)
    the difference, how iMovie and FCPX handle that:
    • iM uses as intermediate AppleIntermediateCodec - which does marvel with all the diff. flavors of video, a consumer wants to edit ... but it is far from perfect.
    • … and iMovie deinterlaces interlaced material = reducing vertical resolution by half
    • FCPX transcodes to proRes or even handles codecs 'natively' - which reduces transcoding errors (dramatically)
    on export, both apps use the same Quicktime-engine, I dare to say no difference.
    using the wrong export settings, multiplies bad imports …
    the 'hurt' is done on import, …
    and most damage, in terms of quality, is done on recording   ....

  • Can not view/export a report which has 2 group by field when no data found

    Recently I developed a report, which contains 2 group by fields. it runs successfully when the report displays some data.
    but when there is no data, i cann't view/export this report.
    It shows nothing by html format and shows "this file cannot be opened because it has no pages" message by pdf format.
    even there is no records for this report, i still want to see the template file and show some basic information.
    please help me.
    Daniel

    I've found that, just like I used to do in Oracle Reports, if you put in a COUNT column to count your returning rows, you can put 'No Data Found' when there's no data. That way, your report will return and not error out.
    For .pdfs, this is the code I use; COUNT with code of <?if:count(field_name)=0?>.
    In the .rtf..
    COUNT
         No Data Found     
    END COUNT
    Put this in the .rtf before your data should appear or else it won't work.
    Hope this helps!
    Kris

  • In Lightroom 4, is it possible to change the resolution when exporting to Facebook?

    Is it possible to change the resolution when exporting a photo to Facebook using either the regular plugin or Jeffrey Friedl's plugin?  I can't seem to do it; I only have control over the image dimensions, not the resolution and the dimensions, as you can see in the screen shots below:
    I have control over both when I export to my hard drive (or a flash drive, etc.), as you can see below:
    I can't find the option to control the resolution when I try to export to Facebook.  Before I got Lightroom 4, I would create whole new low-resolution files of images I wanted to post online using Photoshop.  The image size settings I would use are a longest edge of 10 inches at 72ppi, and I would like to continue doing this.  If I can only set the longest side to 720 pixels (I can't even seem to set the longest edge to an inches value - I can only choose a pixels value) and not change the resolution from 300ppi to 72ppi, then my photos' longest edge will only be less than 3 inches long (right?).  Thus, I really want to be able to upload low-resolution photos to Facebook via Lightroom with the ability to change both the resolution and the image dimensions.  Any idea how to do it without having to export to my hard drive first?  Thanks!

    Rob Cole wrote:
    I'd be inclined to set it to zero so it obviously doesn't mean anything
    You can set it to whatever you like, and it makes no difference. Most of the time (depending on how you saved it), it will still open as "72".
    When you save an image for web, the resolution is usually stripped from the file. It's simply not there anymore. That's probably what happens in the Lr facebook module, and that's why there's no entry for it.
    But when you open that image somewhere else, that default of 72 ppi is assigned. Most apps need to know what to do with a file if asked to print it out. So there is a default, and that's usually 72, mostly by convention. With that default ppi, it prints out at a comparable size to what you see on screen at 1:1 display.
    And when people see that, they think "hey, web images are 72 ppi". But they're not - that figure is just inserted there by the opening application.

  • Poor export quality Aperture 3

    I've been searching all over the internet and can't seem to find any answers in regards to export quality in Aperture 3. When I finish editing an image and I export it in either TIFF, JPEG or PNG all of them look the same regardless of if I change DPI, File size etc and none of them look even close to as detailed as the original. I'm exporting "version" and changing the options in presets with no luck.
    Can someone help me? I can't accept the poor quality of the exported images as they make my portraits look fuzzy and not sharp (when they're very sharp and vivid in Aperture!). Is it possible to get the same quality in an exported image as I see in Aperture. It seems like it should be a no brainer!
    Thank you!

    I had the same problem. While in a One-to One the Creative told me to do this. What ever you are planning to export the file/files to have pluged in (flash drive, hard drive) or loaded (DVD/CD) before you start the process.
    Chose the file or files by highlighting them then choose File - Export - Version. In the center of the window that will pop up there is a "Export Preset"" tab. He told me to choose TIFF- Original Size (8-bit). He did say that any higher than 8 bit is pointless. I did this and it worked great. I had a large beautiful file that I was blowing up to 30 by 20 and it looked so bad printed before I learned this trick. I printed it again after exporting the new way and it really looked great!
    I hope this solves your problem, it was VERY frustrating for me also.

  • Anybody know what resolution and KBPS quality apple use in their SD movies?

    I want to digitize some of my movies into the MP4 format so I can watch it on my apple tv.
    this is mostly children tv (thomas tank engine and so on). problem with dvd's is that we need to change often and they get worn. children do change their mind very often.
    so, a digitized version in my Apple tv would be nice.
    I Use DVD FAB 5.
    but when it comes to the kbps setting what should I choose?
    I think that I can use the same setting as Apple them self. I bought walle movie and that was 1.1 GB and had very nice look.
    anybody know what resolution and KBPS quality apple use in their SD movies?

    anybody know what resolution and KBPS quality apple use in their SD movies?
    They are generally encoded at 1500 Kbps for video and 128 Kbps for audio and a resolution of 640 x 480 depending on the aspect ratio.
    The ToU of this forum forbid discussion about circumventing copy protection, so I'm not willing to comment on the rest of your question.
    http://discussions.apple.com/help.jspa#terms

  • ADF view, export excel does not export more than 65536 rows

    as this is limitation of ms excel 2000, but not sure whether it is still limitation in using ADF view export excel feature.
    in our table , there are more than 80k rows, when we click on export excel, it only get's 65536 rows
    remaining rows are not exported.
    please let us know if this is still open issue or fixed, also let us know which version if it is fixed.

    Hi,
    Yo have to use custom library Ex: Apachi POI
    See
    Re: ADF table data export to Excel

  • Is Your Footage Suffering from the Massive Difference in Export Quality Between FCPX

    I read this article today and considering I do all my rendering through Premiere or AME it made me a little concerned. What does Adobe think of this? and has any else experienced this problem?
    Cheers,
    Moja.
    I took this article from: Is Your Footage Suffering from the Massive Difference in Export Quality Between FCPX & Premiere?
    A rational person might assume that the program from which you export your media wouldn't have a noticeable impact on the quality of the final image, especially if the export settings are identical in both programs. A recent test by filmmaker Noam Kroll might just teach us to think twice before making assumptions.
    First, a little bit of background on Kroll's test. Having noticed that exporting from Adobe Media Encoder yielded quicker results than using the same settings and exporting from FCPX, he tended to use Media Encoder for the bulk of his exporting. When a recently exported project came out with some nasty compression artifacts, blocky rendering of certain areas, and a noticeable change in color quality, Kroll put on his detective's hat and tried exporting again from FCPX. To his, and soon to be your, surprise, the exported result from FCPX yielded significantly higher image quality with the EXACT same export and compression settings.
    Don't believe it? Have a look for yourself. According to Kroll, "both FCP X and Premiere Pro were set to output a high quality H.264 file at 10,000 kbps." The image on top was exported from FCPX and the bottom was exported from Premiere Pro.
    Exported from FCPX
    Exported from Premiere Pro
    In the shots above, you'll notice more blocky compression artifacts in the version exported from Premiere, especially on the lower part of the woman's face, and there's a fairly significant reddish hue that's been introduced into the midtones and shadows of the Premiere export. Here's a version of the same shot that is cropped in on the woman's face by 400%. This is where the difference between the two starts to become painfully obvious. Again, FCPX is on top, and Premiere on the bottom.
    Exported from FCPX
    Exported from Premiere Pro
    Here's the conclusion that Kroll came to in his post.
    After seeing this I can confidently say that I will not be compressing to H.264 using Premiere Pro or Adobe Media Encoder any more. [sic] The image from Premiere is so much blockier, less detailed, and muddy looking, not to mention that the colors aren’t at all accurate. In fact I even did another output test later on with Premiere Pro set to 20,000 kbps and FCP X only set to 10,000 kbps and still the FCP X image was noticeably higher quality, so clearly something is up.
    It's really difficult to speculate as to what's going on behind the scenes that's causing such a drastic difference in results between the two programs. However, what is clear is that you should take caution when exporting to h.264 from Premiere and Media Encoder. Regardless of the program that you're using, perform your own tests and make sure that the export process is leaving your media with a visual quality appropriate for the delivery medium.
    The good news here is that Adobe is extremely receptive to feedback from their user base, and their Creative Cloud subscription model allows them to roll out updates with a much higher frequency than they could with the boxed version of the Creative Suite. If more people are experiencing these problems and reporting it to Adobe, chances are that we'll see an update with fixes sometime in the near future. With that said, I have no idea how Adobe handles the technical process of exporting, so it could very well take a complete overhaul of how the program encodes h.264 to fix the problem.

    Well, I did my own little comparison with a shot from my A7s (XAVCS 50mbps) and seeing as I don't have FCP X I used FCP 7. The AME H264 looks nicer than the FCP one in this instance.
    Dropbox - WALKING 444.jpg
    Pro Res 444 from Premiere
    Dropbox - WALKING AME.jpg
    H264 from AME at these settings:
    Dropbox - WALKING FCP.jpg
    H264 from FCP 7 at these settings:

  • Setting default export quality for PDFs in Pages 5.0

    Hi,
    Anyone know if it is possible to set a default export quality for PDFs in Pages 5.0.  Even if it remembered the last used setting that would be helpful.
    Thanks,
    Nick

    OK,  I have managed to get higher quality images from the PDF renderer. Here is what I have found:
    1) The PDF renderer in Reporting Services 2005 will size all images that it is given at 96 DPI no matter what DPI the image is when you pass it to the renderer. That means that a 300 DPI image or even a 600 DPI image will be sized in the PDF as if it is only 96 DPI. That means your high DPI image will render much larger than you expect.
    So you might expect a 300 DPI image that is 6.5 inches wide to render properly at 1950 pixels. Yet, the PDF renderer will size it as it were 96 DPI which would make the image 20.3 inches long!
    2) There is good news though. Despite sizing the images as if they were 96 DPI, the PDF renderer appears to render higher DPI images at a higher quality than 96 DPI. So despite the sizing being wrong, the image actually is rendering at a higher quality.
    This means that you should size the image to the proper number of inches based on 96 DPI calculations. Then you can use Bitmap.SetResolution to set your images to at least 300 DPI.  That should give you a higher quality image that is the proper number of pixels to fit properly in your report.
    I am able to do all of this sizing dynamically because I am using objects as my data sources, but I am sure there are VB functions you could use in the report itself to accomplish the same task.
    It is late, and I've been at this project all day long, so forgive me if I have explained anything poorly or gotten any concepts long. Yet, at this late hour, I believe this is what the renderer is doing.
    I hope this helps someone else in the future, or at least points them in the right direction.

  • Export quality in After Effects

    I'm using After Effects CS4 and have exported as an MPEG-4.  The quality of the final movie is very poor.  It looks like a low quality JPEG.  In After Effects preview, it looks fine.
    I'm familiar with exporting quality videos out of Premiere.  Is the usual workflow to open AE projects in Premiere and use the options there to export?  Or am I missing something in AE?

    That may be, but I'm just not a fan.  I did some tests a few years ago and decided that Animation
    wasn't worth it and that it was in fact creating artifacts in my renders.
    Just to show my work, I am pulling some info from wikipedia as a reference:
    "For complex 3D rendered scenes or digitized film of real-world footage, it barely compresses at all and also can add visible noise."
    Now I know, wikipedia isn't highly reliable, anyone can edit it, blah blah blah, but this statement runs congruent to my own findings.  Add to that the weighty file size, and then the fact that this codec is officially my ENEMY because my students, who are instructed to use Sorenson 3, often forget to change the codec for their .mov renders, and so sometimes I get these bloated files that I have to trash and they have to re-render, and I just don't really care for this codec at all.
    I just don't render video any more.  Haven't for a long time now.  So many advantages to using img sequences, I haven't looked back to big bloated video files.

  • Export quality of CS6 compared to CS3

    Having had Premiere Pro CS3 for about 5 years I recently upgraded to CS6 but immediately found problems achieving the same kind of export quality I had before. Initially I was testing with a project created in CS3 but then simplified the matter by creating a new project in CS3 and entering a single piece of text and exporting as a single tiff frame and doing exactly the same in CS6 and attached is the comparison. I can't of the life of me figure out what the problem is, hopefully someone can help.
    Thanks,
    Keith.

    Okay, thanks for the further input, I've made progress with it, I've discovered it's to do with the field order setting. Basically my knowledge of video editing and video standards is rather limited and the kind of work I've done in the past has mostly been to produce animations from 3ds Max which are simply shown as demonstrations to people on a PC or laptop, and so when setting up a new project in Premiere I always selected "Desktop" editing mode, changed some settings and left others as default such as Fields: Lower Field First, mainly because I didn't know what it meant.
    When exporting the finished video the default would be Progressive Scan and everything fine, so never touched it. With CS6 if I do everything the same way I get the problem described above, but if for new projects I select Progressive Scan in the setup then everything is fine. (Similarly with lower field in setup and export).
    However I still have a problem with imported CS3 projects. In CS6 if I simply open the project and select Lower Field on export, or start a new project with Progressive Scan in setup and import the project, the fuzziness I had before is gone but now I get the effect in the following attached image (a print screen from a paused video, left one exactly as I expect):
    I have found a work around though, which is to start a new CS6 project with progressive scan in setup, import the project, then create a new sequence and copy the contents of the imported sequence into it and that exports fine, although I suppose it could get complicated when there are sequences inside sequences. I'm sure there is still something simple I'm missing to do this in a more seamless manner, if anyone has any ideas please let me know.  

Maybe you are looking for

  • Data Extraction failure from DSO to Cube

    Hello Experts, The Data load to Cube( zfiar_c03) from DSO (zfiar_03) using a full update is failing throwing the error message"Incomplete update due to errors in single records ".We had deleted the failed request from infocube and loaded the the same

  • Printing from windows xp to printer on aeb

    I have a network set up using an airport extreme basestation which provides internet access to a powerbook and a pc laptop running xp. this works flawlessly. I also have a canon ip3000 printer connected to the basestation which i want to use from bot

  • Creation of offline cubes from pivot table[Automation]

      I have a pivot table on which i can slice data based on 3 different users so i create the offline cube for each of them independently using Analyse->OLAP Tools->Offline OLAP. So i need to repeat this process 3 times since each time i only select on

  • HT1918 hi

    my son has downloaded games on my iphone4s which cost money and my card details are on the phone but it says they were unable to process the payment but for me to be able to use the account it says it needs to be paid but i will not pay it as i did n

  • AFP Error when trying to use OD logon.

    Attempting to log onto Lion using a OD user and recieving the followinf error in the secure.log: PremountHomeDirectoryWithAuthentication( url=afp://server.local/Users, homedir=/Network/Servers/media.local/Volumes/Media/Users/userxxx, name=userxxx ) r