--Flat/Slightly Desaturated Export

Hi,
I'm using Final Cut Pro 6.
After I export a reference movie of my edit (1080/24p ProRes 422) and bring that into Compressor for an H.264 .mov (5000mb/s) export, my video is a little flat, desaturated, washed out a bit.
Even the self-contained movie looks different than what I'm seeing inside FCP 6. In the Canvas, the video looks more saturated and crisp.
Is this normal? And if so, I guess the only workaound would be to overestimate your Color Correction so it balances out when you export?
Thank you.

This should not happen. If the video is less saturated, it should show a shift in the vectorscope reading between the two clips.
I would recommend testing this by downloading the free trail version of Veescope Live. Create a color bars test video in FCP 6 and export that to a ProRes Quicktime movie. Convert the ProRes to H.264 in Compressor. In Veescope Live click on the Quicktime inputs option and drag the ProRes file and the Quicktime file into the list box. Click on the multi-scope option under scopes to display the Vector, Waveform, and RGB parade scopes. Click back on the "inputs" tab and switch back and forth between the H.264 and the ProRes version of the video. Look to see if the vectorscope changes dramatically.

Similar Messages

H264(Youtube/Vimeo Preset) export looks flat and desaturated- H264 Gamma?

All my h264 output both quickitme and mp4 looks flat and desaturated after export compared to to the program window.This happends with both cs5.5 and cs6.
I know there is some h264 bug with Quicktime but its flat on Youtube also( in Safari) I thought this gamma issue has been sorted out?
How can I output my files to youtube so it looks the same as my Program monitor on youtube? I know all screens are different and you need a color calibrated montior( I have that) but why the shift?
It just does not seem that anyone has an answer. x264 does not work... anything else? QUickitme x does not have the ability to do the "opacity fix"
How will i get that my output on my client screen will not be so flat. ( I know it wont be exactly the same (as TVs in a showroom) but the difference between the video inside premier and outside is VAST!
I dont want to "fix" it by addinga contrast and saturation layer and them on a Windows machine maybe its then overly contrasty?
I'm on 17" MAcbook PRo Using anexternal calibrated NEC Monitor.
Did I miss a major answer on the web somewhere?

So what do you guys do? Just add an extra layer of process ( I have added a fast color correction Adjustment layer and clipping the black at 10 and the highlights at 245 and putting the saturation at 120. Its a thumbsuck though...
How on earth do people who colour grade on Davinc or Lustre etc output there stuff to Vimeo.(Yes I know it goes to film or TV , but what about thier showreel?) It also uses H264? Is there ANY codec I can use to upload to Youtube that will look like my program monitor?
It is facinating how these companies provide all these wonderful tools and in the final polished output you cannot get it too look llike it looked inside the product! Baffling!
If I had a Windows machine would I have this problem?

Data convertion while exporting data into flat files using export wizard in ssis

Hi ,
while exporting data to flat file through export wizard the source table is having NVARCHAR types.
could you please help me on how to do the data convertion while using the export wizard?
Thanks.

Hi Avs sai,
By default, the columns in the destination flat file will be non-Unicode columns, e.g. the data type of the columns will be DT_STR. If you want to keep the original DT_WSTR data type of the input column when outputting to the destination file, you can check
the Unicode option on the “Choose a Destination” page of the SQL Server Import and Export Wizard. Then, on the “Configure Flat File Destination” page, you can click the Edit Mappings…“ button to check the data types. Please see the screenshot:
Regards,
Mike Yin
TechNet Community Support

Last line of table shifts to right slightly after export to PDF

Indesign CS4 (6.0.4.578), Windows XP. Last line of some tables shifts very slightly to the right, but only in exported PDFs. See screencap from PDF below. It's not very pronounced, but Xs don't quite line up, and client can see it.
When I printed to PDF through Acrobat 9 the problem goes away. But I would prefer to export.
For a one-page sample file formatted in Minion Pro (it happens in differing degrees with any typeface), download
http://www.pegtype.com/shifttorighttest.zip.
Any ideas why this is happening?
Ken Benson

It's not showing in the ID file, just in the exported PDF (and not in the printed PDF). And it shows in the PDF you made too, you just have to look at a higher magnification.
This is from the PDF you made and emailed to me. See how the bottom X is a little further to the right? Compare foot to foot, not head to foot. Minion X is narrower at the top.
Acrobat is at 9.3.1. I let the Adobe applications update themselves, so everything should be at the latest point release. No custom dictionary or kerning, though if there was, I would expect the ID file to show the same thing as the PDF.
Ken Benson

Images following a motion path shift slightly after export to .f4v (PE10)

I have been placing faces over those in a existing video. Everything is lined up properly in the editing windows but when I export to f4v or any other file type, the faces are not where they were prior to export and the effect is ruined when the faces are only 1/2 covered. Thoughts?

tjedic6
What computer operating system is your Premiere Elements 10 running on? And, does that computer use a NVIDIA GeForce video card/graphics card? If so, then please immediately go to the Announcment on Premiere Elements 10 NVIDIA GeForce at the top of this forum and rule in or out whether it applies to your Premiere Elements 10 setup.
If you fix that or rule it out, then onward....
1. What project preset are you setting for your project?
2. What are the properties of your source media which should be matching the project preset details.
3. What are the details of your "f4v" export? Apparently, Share/Computer/Adobe Flash Video and then what...
Since there are only two f4v presets, you must be using either
F4V - HD1080p (Flash 9 and Higher)
or
F4V - HD720p (Flash 9 and Higher)
Do you use the defaults for either of these presets or do you customized the Export Settings under the
Advanced Button of the preset?
The following is a screenshot under the Advanced Button/Video Tab of the F4V - HD1080p (Flash 9 and Higher) preset.
I suspect a mismatch in your settings somewhere. Your details will help us to find the answers.
Looking forward to your follow up.
Thank you.
ATR

Size of Infocube Export to a flat file (.CSV)

First off, I'm new to BW so I apologize if I use the wrong terminology. I was wondering if there was any way to estimate the size of a flat file infocube export. For example, if I look up all the associated DB tables for a cube, let's call it TESTCUBE, would the total size of those tables be about the size of the TESTCUBE export to a flat file. This assumes that the cube is not compressed in any way. So if the the total DB table size is 100 MB then is the flat file about 100 MB? If not, is there a way to estimate this.
Thanks!

Can't say for sure how all DBs that BW run on work, but with Oracle, space is consumed in blocks, not by rows/records.
Let's say you have a table where the average row width (record length) is 100 bytes. In a tablespace that has 8K blocks, in theory, you could fit 81 rows in the block.
However there is usually a certain amount of freespace left in a block when rows are added to accomodate subsequent inserts/updates. The BW tables I have looked at default this to 10%. So that means youe have over 800 bytes of the block that might not get filled. There are other things that can result in space being consumed, such as deletions that will leave dead space, and updates can cause a row to migrate to another block, etc. Also, space is allocated in chunks as a table grows, and you may add one row to a table that causes a 10MB chunk of storage to be allocated, but it is holding only 1 row.
So as you can begin to see. A flat export should require less space than the source table (unless you are using database table compression which could completely invalidate what I have said), but by how much depends on all the things I mentioned, and could change from day to day.
You could certainly use as a rough rule of thumb, that a flat file export will require the same space and you would be safe (except if you are using db compression).

Photoshop desaturating but lightroom is not (same file)

I'm sure this has been asked a million times before but..
Basically, I designed an ad for a client on my Macbook Pro (I usually design on my PC).
Using my Mac:
1. I saved the image using Save For Web in Photoshop CS4 (with Convert to sRGB), and it slightly desaturated the image.
2. I imported the PSD into lightroom and exported it (with Convert to sRGB), it did NOT desaturate the image.
I sent the desaturated Photoshop image and the proper looking Lightroom image over to my PC, and they look EXACTLY the same. Why is this happening? Why is the Mac needlesly desaturating the Save For Web image?
This is not a problem when I save using my PC.
Thank You

You've got to understand a little color management, but the answer is this:
You've got a display with a slightly smaller gamut (less colors, less saturation potential) than the standard web color space, sRGB.
On the Mac (in Safari and other Apple apps), when an untagged image (an image with no color profile) is displayed, it is assumed to be the colorspace of the display, so there is a slight desaturation (if it's really sRGB). Lightroom creates a JPG with the correct sRGB profile embedded, so there's no desaturation happening to its JPGs (this is really an assumption, but a good one, I think). On the PC, most applications assume sRGB for untagged images, so both JPGs look the same because they're both sRGB -- one just is missing its profile.
Take a look at things in the new Firefox on your Mac, and you'll find they match the PC a lot better.
You can preview this destauration in PS by using proof setup in view and proofing monitor RGB. But to be clear, you are creating images the right way already. In fact, all images prepared properly for the web are being viewed by you (right now!) with this same desaturation and you've been cool with it.
One thing you might do is go the Coke website and download a pic of one of their cans. View it in Safari and then view it in PS with sRGB assigned to it (in case your working space is Adobe RGB 1998). See, you've been looking at the web all wrong, forever! Ed: it looks like they're now tagging their images for this exact reason. In that vein, the simplest thing you can do is check embed profile in the SFW dialogue, if you can take the 4k per image hit.

Export PDF with TOC

If I didn't miss something important, it is currently impossible to add a table of contents (TOC) to the exported PDF that will show up in the sidebar of the Preview application. IMO Pages would be a great tool for publishing manuals and other documentation, but without a TOC in the sidebar, this is completely useless.
Is there perhaps any sort of hack to get around this? (the files are XML, so this doesn't seem entirely impossible). Anyone know of plans that Apple might eventually add this absolutely needed feature?
Andre

Henrik Holmegaard wrote:
This is sound, but it depends on what you are trying to decide. The trouble is that the everyday enduser expects content to be searchable, but below PDF 1.4 there is no support for content structure and even if there is support for content structure in PDF 1.4 there are plenty of preparation processes that produce non-searchable PDF 1.4.
If - or should one say when - the operating system supports creation of searchable content instead of simply supporting Spotlight as a search service, there is still no list for these problems.
Funny response.
The PDFs generated from Pages are perfectly searchable. As far as I know, when we search in a PDF displayed by Preview, it's not Spotlight which does the duty. Same thing when the document is open with Adobe Reader.
The missing feature is not the search tool, it is the TOC one. It's not a huge task (it was available in the old printToPdf pseudo printer driver under Mac OS 9).
It's just missing because it is supposed to be useless for many of us. Is it really useless, is it really useful ? I don't know the response at statistically meaningful level.
To be honest, when I saw that there are two paths to create PDFs from Pages, my first thought was:
1 - Print in a PDF file generates a flat PDF
2 - Export to PDF is able to generate one with a TOC.
I was wrong but I didn't cry for that. I may live without this feature. Missing the search tool would be more annoying.
Yvan KOENIG (from FRANCE dimanche 20 juillet 2008 19:55:27)

LR4 export creates random blank images

Hi I'm experiencing a strange situation where I export a selection of photos, perhaps 150 of them, and will see random blank images with valid photo metadata but a blank (white) image. In this case 3 of 150 photos are "real" but export as blank. I can export the exact same selection of images using a slightly different export setting and the images are present (a different watermark PNG). What is wrong with LR 4 export ?

Hi
Please check the following :
--Export to .PDF and check if you are getting a correct page format. If you are getting then check word page header and page footer settings.
--Also check the default printer and page setup.
--Use no printer option in CR page setup and try to export to word. Also check RTF format.
--Also try to check this is happening only in your system and any other system.
Thanks,
Sastry

Problems with bleed and exporting to PDF.

Hi,
I am having a slight problem exporting a file to pdf in Indesign CS3.
I have my documents set up with a 3mm bleed and I have made sure that the images and work extend passed the bleed marks as they should. The problem is that when I export to pdf, the pdf file appears to have cropped the work exactly on the bleed line leaving nothing extending passed the bleed. The 3mm bleed area is still there but nothing is extending into it which is kind of pointless. I don't know whether there is a setting I am missing or something like that but any help on this matter would be greatly appreciated.
Cheers

"It appears to crop it exactly on the bleed line."
for the record, isn't that what it's supposed to do?
Your bleed line is 3mm outside the trim. Anything you bleed will be contained in that 3mm band. If you hang any more than 3mm off the edge, only the 3mm in the bleed band will show on the PDF.
k

Defringing a Nikon raw (nef) in LR4.4

Thin black branches against a blue sky are always problematic. Problematic for Lightroom, that is. The jpegs straight out of my D5100 totally eliminate all CA and purple fringing, so I know it can be done. It's just that no matter how I play with the "Defringe" sliders I cannot eliminate the bluish case on the branches. I go back and forth between my attempts in LR4.4 to my jpeg of the same scene and the jpeg handles it perfectly.
"Remove Chromatic Aberration" box is checked. Is it maybe a fact of life that Lightroom 4.4 just doesn't handle nefs as well as maybe Canon raws?
My workflow is such that I have to work on a ton of images at one time, so I have a "prest upon import" set up. Then I export as tiffs. So I'd like to keep all the tweaking in Lightroom for efficiency's sake. Very few of my images actually have this "problem" but in a video tutorial on the use of these sliders the commentator mentioned that the submittal of images to a client (magazine, whatever) requires that all CA/defringing to be totally done or you'd look like an amateur. All his video did was get close, just like my attempts just get me closer but nowhere as good as the SOOC jpegs do. Thanks for your help.

I've used the Defringe tools very successfully with a Canon 8-15mm Fisheye and 85mm F1.8 lenses that exhibit significant axial CA. The settings that worked without removing saturation from purple objects are Purple Hue 30/55 with Amount 4 for the 8-15mm Fisheye and Purple Hue 42/68 and Amount 5 for the 85mm F1.8. These lens specific Defringe settings seem to work well regardless of the F stop used and subject type, so I can apply them almost universally on Import.
The key is finding the optimum Hue settings and lowest Amount that removes the fringing, but does not desaturate like colored objects in the picture.
Here's an example with the Canon 8-15mm Fisheye lens:
With Defringe and Remove CA With Remove CA Only
The Left image shows only a very slight desaturation in the purple objects. Higher Amount settings will desaturate them noticeably, but do NOT improve removal in the areas desired.
If still having issues please post a screenshot and perhaps we can provide some other suggestions. Better yet post the file to a download site like Dropbox or Hightail using a free account.

Yo Jao! can you help??

Jao, good work on color management topics, especially concerning output printing to Costcophotocenter. My questions is - what are the 'rendering intents' when exporting in LR 2.0? The ability to choose color space in LR while exporting was (for me) reason enough to upgrade. What a timesaver.
Thanks to everyone up front.
Antonio

>My questions is - what are the 'rendering intents' when exporting in LR 2.0?
There are several different rendering intents important in color management. The two that you should be concerned with most are relative colorimetric and perceptual. Relative simply directly translates the values in the original colorspace (linear ppRGB in Lightroom's case) to the output profile. This is the most "faithful" method, however, if a color in your original document is outside the gamut of the destination profile, the color will get clipped. You might for example, end up with a red flower with no structure in the flower anymore. Perceptual is sort of meant to fix this. It will try to map colors outside of the gamut in the destination profile to the profile. In practice this might lead to slight desaturation.
Here is an example:
http://www.oreillynet.com/digitalmedia/blog/2007/03/lightrooms_print_module_and_co_2.html
Here is some of the nitty gritty:
http://www.cambridgeincolour.com/tutorials/color-space-conversion.htm
But there is lots and lots of other info on this on the web.
P.S. note that rendering intent has no influence on outputting to sRGB and adobeRGB. They will always give you the result of the relative intent.

Rendered movie is wrong

I have created a title sequence in LT 2.1.4. I created a .m4v slideshow video from iPhoto and placed this movie in the LT timeline around 5 seconds (it's the "display" iPhoto slideshow export size -- it's very large). The entire movie is a little under 4 minutes long.
When I place start/end points at about 0 and 30 seconds and File->Render Preview, the output is fine -- all the title sequences are there and the background movie renders properly. Woo hoo!
But when I File->Render Movie and watch the resulting .mov, the output is just plain wrong. The motion just stops periodically (i.e., there are many repeated frames -- for 2-10 seconds at a time), there are many missing effects, etc.
I have LT 2.1.4 -- is that the latest? I can't seem to find anywhere to download updates. I'm running SL 10.6.2.
Is this a known issue? Are there any workaround?
Let me know if I can provide any further details. Many thanks for any advice that anyone can offer.

Hmm.
1. I checked the LT docs, and it says that MPEG-4 is supported. I don't seem to be able to attach anything to this post, so I'll just have to cite that I went to Help->LiveType User Manual, and looked at page 43 -- it says:
"LiveType can import background elements in a variety of formats:
* MPEG-2 and MPEG-4
2. I used a slightly different export option in iPhoto to export the slideshow: selecting "custom export" selected saving to a "Quicktime Movie". This produced a .mov file. So I used that as my background movie in LT. But the same behavior occurs -- the preview rendering is fine (although there is no sound -- forgot to mention that in my original post), but the actual rendering (where it produces a .mov) is just wrong.
FWIW, running the "file" command on both of the exported iPhoto files (the .m4v and the .mov) results in "ISO Media, MPEG v4 system, version 2", whereas running file on the rendered .mov from LT results in "ISO Media, Apple QuickTime movie". It makes me wonder if iPhoto really made a Quicktime movie or if it just used the same mp4 encoding and just named the file .mov instead of .m4v...
I'll keep trying.
I suspect that you are right that the Best way to do this is to slurp in the movie into FCE and import the LT titles into it in a separate track. I might end up doing that, but I'd like to give my current approach a few more tries before I give up and learn more about FCE... it should work, according to the docs, anyway...

Has anyone got Thunderbird/Ovi sync to work?

Been trawling through posts discussing error "80043c93" when trying to sync with Thunderbird.
As they seem to mainly consist of people experiencing the issue with no feedback from Nokia, I was hoping it might be possible to find an OS/thunderbird/Ovisuite version combination that might work reasonably reliably.
Failing that, are there any plans to allow Ovisuite the old fallback of flat file import/export?
Any assistance at getting some rudimentary sync capabilities (contacts, at least) would be most appreciated - am even up for bespoke/non-nokia syncing solutions that support the E72.
Thanks in advance.

I have a new E63 and I use Thunderbird on Windows Vista.
Trying to get any kind of sync seems impossible.
The 'PC Suite' installed, connected to the phone, and seemed to do a sync.
Despite saying things like '69 contacts synced successfully ...' - nothing had actually happened. So I tried Ovi Suite.
Nokia says you can install one over the other, so I did.
Ovi Suite installed and ran successfully but the error 80043c93 came up and ... no sync.
I uninstalled 'everything Nokia', turned off, unplugged, etc.
I then did a completely clean install of Ovi Suite from a newly downloaded copy (just in case).
Exactly the same result.
This is categorically a major failing (bug) with the software.
The real problems, as I see it, are these:
1) Cryptic error codes with no help or guidance in the software itself; and
2) a seeming lack of responsiveness from Nokia themselves.
I cannot find any other sync solution at present so I shall have to abandon my efforts.
I am very pleased with my Nokia phone but it is hurt by this poor software and support.
I am not overly cynical but this 'upgrade' to PC Suite seems to be wholly geared to
leveraging cash flow from the Ovi store/library rather than helping/empowering users.

RSAU_READ_FILE RFC call help.

Hi,
I trying to get Audit events from C through SAP RFC SDK. However, i could not able to read table SYSLOG_IN_TABLE.
following is sample code i am using .
strcpyU(functionname,"RSAU_READ_FILE");
    rfc_char_t * value = new rfc_char_t[500];
     rfc_char_t * value1 = new rfc_char_t[500];
     sprintfU(value,"Agtvra01-test_NSP_00             0000000000000000000000000000000020091106080000200911060800000020091109      2009110923595900                                                        00000          *");
     sprintfU(value1,"Structure: flat & not charlike");
    exporting[0].name = cU("SELECTION");;
    exporting[0].nlen = 9;
    exporting[0].addr = value;
    exporting[0].leng = strlenU(value)*sizeofR(SAP_UC);
    exporting[0].type = RFCTYPE_CHAR;
     /*exporting[1].name = cU("SELECTION_AUDIT");;
    exporting[1].nlen = 15;
    exporting[1].addr = value1;
    exporting[1].leng = strlenU(value1)*sizeofR(SAP_UC);
    exporting[1].type = RFCTYPE_CHAR;*/
   rfc_char_t   * t_name = new rfc_char_t[500];
    strcpyU(t_name,"SYSLOG_IN_TABLE");
     tables[0].name     = t_name;
    tables[0].nlen     = 15;
    tables[0].ithandle = ItCreate (t_name, 300, 0 , 0);
    tables[0].leng     = 300;
    tables[0].type     = RFCTYPE_CHAR;
     /* issue the RFC call */
   rc = RfcCallReceive (handle,
                        functionname,
                        exporting,
                        importing,
                        tables,
                        &exception_ptr);
   /* check return code */
   switch (rc)
      case RFC_OK:
        break;
      case RFC_EXCEPTION :
      case RFC_SYS_EXCEPTION :
        rfc_error( exception_ptr );
        break;
      default :
        rfc_error (cU("call/receive error"));
       break;
   display_table (tables[0].ithandle);
Please help me , how to read SYSLOG_IN_TABLE table .

Hello,
           Is your problem solved. I am facing the same situation. Could you help me out, How got the data into SYSLOG_IN_TABLE.
Thanks in advance for your reply.
Regards,
Darwin.

--Flat/Slightly Desaturated Export

Similar Messages

Maybe you are looking for