Exporting Issue with Nikon D7100

Hi.
Just shot some footage with Nikon D7100, 1080p 23.4fps.
I have recently exported on these settings using the H.264 with no issue.
Today I sped the footage up to 2500% (20 min down to 35 seconds) and when I export it is turning my video into a squashed box that has been dramatically degraded.
I doubt this is to do with speeding up though?
These are my settiings. Any ideas? It will be something stupidly simple.

Weird things can happen with extreme speed up. Can't say what exactly the issue is without seeing the footage. However - I would UNcheck the boxes for Frame Blending and Max Render. Frame Blending is used when changing frame rates, which you are not, 24p source and 24p export. The blending could definitely mess up the output. Max Render is used when downscaling, which again you are not going - adds time to the render.
Lastly, how will the exported video be viewed? For web/computer viewing, you want to use square pixels (1.0 pixel aspect ratio). Exporting as anamorphic (1440x1080 1.33 PAR), it may play back as 4:3 rather than 16:9. So export either as 1920x1080 (1.0 PAR) or 720p (1280x720, 1.0 PAR) for best results.
Thanks
Jeff Pulera
Safe Harbor Computers

Similar Messages

I have been using Aperture 3.3.2 with Mac OS-X 10.7.5. This version doesn't support RAW with Nikon D7100, I decided to upgrade to 3.4. On downloading, it tells me that to upgrade, I need Aperture Vers.3! which I have. What to do??

I have been using Aperture 3.3.2 with Mac OS-X 10.7.5. This version doesn't support RAW with Nikon D7100, so I decided to upgrade to 3.4. On downloading, it tells me that in order to upgrade, I need Aperture Version 3, which is what I have. What is one supposed to do??

Have you moved or renamed your Aperture 3 version? If it is not installed in the "Applications" folder or not named simply "Aperture", then Software Update will not recognize it.
Put Aperture back and "Software Update" should find your version.
Regards
Léonie

RC 8.6 Issues with Nikon D810 NEF RAW files

RC 8.6 does not correctly process Nikon D810 NEF RAW files. See the following blog article for some details:
Nikon D810 vs D800E ISO Comparison

This is very helpful. My current workflow, until ACR 8.6 and LR fully support the Nikon D810, are to use the DNG converter and import the resulting D810 DNG files into my LR catalog.
I have not yet tried this (traveling right now), but I assume I can still make a custom profile using the X-Rite ColorChecker Passport and it's associated software for my D810 using the RC 8.6 DNG files. This is my normal workflow for all of my other cameras in LR, but the process is direct from native RAW and not DNG (to produce the custom profile).
Sent from my iPad
On Jul 28, 2014, at 6:51 PM, "max.wendt" <[email protected]> wrote:
RC 8.6 Issues with Nikon D810 NEF RAW files
created by max.wendt in Adobe Camera Raw - View the full discussion
Until Lightroom gets D810 support, you will need to use the ACR plugin in order to see the profiles. The DNG Converter always uses Adobe Standard, and embeds it into the DNG. Lightroom 5.5 doesn't have the D810 profiles.
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image athttps://forums.adobe.com/message/6592335#6592335
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: [https://forums.adobe.com/message/6592335#6592335]
To unsubscribe from this thread, please visit the message page at [https://forums.adobe.com/message/6592335#6592335]. In the Actions box on the right, click theStop Email Notifications link.
Start a new discussion in Adobe Camera Raw by email or at Adobe Community
For more information about maintaining your forum email notifications please go tohttp://forums.adobe.com/thread/416458?tstart=0.

RAW file problem with Nikon D7100

Ijust purchased a Nikon D7100, and I'm unable to upload and edit RAW files(NEF) in Lightroom 3.6. Nikon provided no help. Can anyone offer a solution?

Have you downloaded the Codec from Nikon. I use both Windows Vista and Windows 7. I downloaded the Codec of the Nikon D7100 yesterday and installed it and I don't have the latest Capture NX, I have the original I brought shortly after buying my D200. I can now use the D7100 files directly into my Capture NX software. ViewNX gives you the basics of Raw editing but Capture NX gives you the advantage of using the U point system. I found this out purely by accident. If you can download the Codec free of charge and pick up a cheap old Capture NX you can get all your EXIF data as well as lense data without any issues.. The Camera companies pay Adobe a license fee for using the Adobe Gamma in their cameras so why should they pay more for file format. Adobe is very protective over its intellectual property so why not with Canon or Nikon. They comply with the consumer trade agreements on EXIF and image authentication. Nikon have cameras in Space which is more than Adobe ever dreamt of. So file format has little or nothing to do with compatibility.

Adobe Camera Raw 8.6 issue with Nikon D810 files

Just installed ACR 8.6 with D810 support.
A huge amount of moire is introduced when selecting the following profiles: camera standard, camera landscape, camera vivid, and camera monochrome.
All other profiles (adobe standard, camera neutral, camera flat, and camera portrait) seem ok.
The problem exists in Photoshop (via ACR) and in Lightroom 5.6. Please note that Nikon Capture NX-D doesn't have this issue.
Example: Check the upper portion of the following image:

I have experienced the same, although having never owned a camera without the olpf, I did not realize that what I was seeing was moire -- I was calling it "color banding" as if shooting with a low bit rate or very small color gamut.
I think the same issue is referred to in the following post: http://www.dslrbodies.com/accessories/software-for-nikon-dslrs/software-news/acr-86-and-li ghtroom-56.html but he is vague as to just what the "issue" is.
I noticed this issue not only with acr, but on the back of the lcd of the 810 itself. Wondering if I was doing something wrong in terms of settings or if it was a bad copy of the d810, I contacted nikon support. They were not helpful and told me to return the unit for repair. I saw this to a great degree on the lcd, to a small degree even in the raw images processed via Capture NX-D and to some extent via acr 8.6 as you say, when using he following profiles: camera standard, camera landscape, camera vivid, and camera monochrome. Since I was not able to convince myself tat it was not an issue with the camera itself, I returned the d810, so I was not stuck with a problematic unit or having to wait for a repair. Now of course I just have to wait for a replacement unit!!
Again, I am curious as to the extent others are seeing this problem. I am seeing nothing but superlatives posted by others. I am hoping that this is some raw processing issue and a bad lcd screen on my original d810, but it seems too big of a coincidence. If it is a matter of Adobe racing to keep up with the new profiles ok, but if this is the extent that I am going to see moire on a camera of this price then it is not worth the upgrade.
What are others experiencing?

Lightroom 4.4 Tethering does not work with Nikon D7100

A week ago i bought my new Nikon D7100. Yesterday i wanted to try the thetering of Lightroom 4.4.
It worked with my Nikon D5100 but it does not work with the new camera.
Is it a problem with my camera or with Lightroom?
Another question does tethering work with Lightroom 5?

...And Google says:
Tethered camera support in Lightroom

Lightroom 5 auto import issues with nikon d90

Hoping someone can help answer my question - I am wondering if Lightroom 5 has any issues with the auto import or tethering feature using a Nikon d90? I was using Lightroom 2 and the auto import feature has no issues with my d90. After I installed Lightroom 5 (Cloud App) and ran it for the first time, the first thing I used was the tethering feature and it worked great for 4 shots. I turned my camera off and then back on again and LR would not recognize my camera any longer for tethering. What's strange is that it will detect it for "Importing from Device" option. So, I went to plan two which was to auto import and that wasn't working at all. I am at a loss. I have a shoot coming up this weekend and need for one of these options to work. Any help is appreciated!!!

I use a D90, but I have never tried tethered shooting with it. Other users might have some suggestions for you, but looking at the list of supported cameras for tethered shooting the D90 is not "officially" supported in Lightroom. So you're probably on your own to find solutions. I know this isn't a lot of help.

Video export issues with 5D mk II video

Using a trial version I keep running into issues with video slideshow export.
I have some 1080p '24fps' video clips from the 5D II, added them to a new Slideshow, did a Custom Export to h264 with height 720 (which from memory took the width to 1152) and 24fps - I want this to play on AppleTV, but the resulting video starts ok, but has multiple sections of blank video - in QT the frame rate has also been upped to 36fps!
It also takes a ridiculous amount of time to export a short clip, but that's seems par for the course for many of Apple's apps. This is on a 2008 8x3GHz Mac Pro with plenty of RAM, though running Leopard.
Anyone done any A/Bs of performance in Leopard vs Snow Leopard - does it make better usage of multiple cores? (They all have a little activity but it's 10% or so, perhaps 1 core at 70-80%, I can't understand even if it's not using all fully why one isn't getting maxed out with the conversion process).
The slideshow export function seems incredibly buggy - it used to output using AppleTv preset with incompatible frame rates, though they may have fixed that.
Message was edited by: Alley_Cat

DLScreative wrote:
Just a thought, but 24p was just added to the markII through a firmware update.
Yes, which is why I thought it would be great for AppleTV which can only officially support 720p at 24fps (though 25fps will often work).
If I use an AppleTv preset it will now rescale to 960x540, but I want to use 1280x720.
Previously in 3.0 the AppleTV preset output 720p but at 30fps which is too high for AppleTV.
Are you sure it's not the footage? Have you tried it in FCP? Also, it maybe that 24p isn't supported in A3, but this all just conjecture on my part.
Good thought, but I would imagine QT is the engine supporting the Aperture exports, and if parameters are set correctly it should give the appropriate output.
I'll try using QT Pro and see what that does with a clip.

LR5.3 Export issue with Sequence Renumbering

I just discovered an issue with the LR5.3 Export module on my Windows 7 system when exporting JPEG image files with 'Sequence' File renaming and 'Original' File Settings to a subfolder. When exporting approximately 100 JPEG image files LR shows a file count in the subfolder of ~1/2 the actual file count and the ability to 'Synchronize Folder' disappears. The correct number of files appear in the subfolder using Windows Explorer, so they all were successfully exported and renamed properly. LR must be closed and reopened to restore the ability to 'Synchronize Folders' and/or 'Import' images using the Import module. I've never encountered this problem before since I normally process raw image files, which do not exhibit this issue.
Here are screenshots:

Posted to the Photoshop Family site as a problem:
http://feedback.photoshop.com/photoshop_family/topics/lr5_3_export_sequence_numbering_issu e

Export Issues with Compressed Partition Tables?

We recently partitioned and compressed some large tables. It appears, but I'm not sure yet, that this is causing the export to run extremely slow. The database is at 10.2.0.2 and we are using the exp utility, not datapump. Does anyone know of any known issues with using exp to export compressed, partitioned tables?

can you give more details of the table structure with dbms_metadata if possible, and how you are taking the export please?
did you try to take an sql*trace of the export process to see what is going on behind, this is an introduction if you may need;
http://tonguc.wordpress.com/2006/12/30/introduction-to-oracle-trace-utulity-and-understanding-the-fundamental-performance-equation/

Speeding up Final Cut Pro X workflow with nikon d7100

Hi everybody,
I recently bought a Nikon d7100. I've shot some footage and now I want to edit it in Final Cut Pro X. I know FCPX doesn't support the H264 codec natively so I converted it to ProRes 422(LT) with mpeg Streamclip and Compressor. Works perfectly, but my problem/question is as follows:
Doing it this way takes way too long. Is there a faster way to do this? I used other camera's in the past and usually there was a plug-in to do this within FCPX itself.
Does anyone have tips to speed up my workflow?
All help is appreciated! Thanks

Hi Tom,
Yes I've tried, but it didn't work.
It works when I copy all the files from the SD-card to my hard drive, but then I see blocks/pixels in the video as shown on the picture below.
Thanks for your help thusfar. Hopefully you have an other suggestion for me

Lightroom 3.2 Tethered shooting with Nikon D7100

I have a laptop Windows Vista which will not allow me to upgrade Lightroom 3.2 to 5.3. I have bought a Nikon D7100. Is it possible to
enable the older version of LIghtroom 3.2 to recognise the Nikon D7100 for tethered shooting?
Cheers.

No, Lightroom 3.2 does not recognize D7100 RAW files, and cannot tether to it.

Yet another export issue with Aperture 3

Judging by a search of topics, there seem to be a myriad of problems associated with getting files out of Aperture, some of which represent occult setting issues, others which seem to be actual bugs. I've run into an issue which seems to defy categorization, and I'm not sure if it's me doing something wrong, or if it is actually yet another bug with this software. I've been an Aperture user since 1.0 and I have to say the current version I'm running (3.4.3) is by far the worst yet. Anyway, enough whining. Here are the issues:
I'm running Aperture on a 6 core Mac Pro with Lion 10.7.5. There are two thing happening.
1. Exporting JPEGs is INCREDIBLY slow - perhaps as long as 4 or 5 minutes for a 3MB file.
2. This is the one driving me batty right now. Tried exporting a batch of images as JPEGs at the 50% original size setting. The master files are large 16 bit TIFF images from Nikon D800 RAW files, post-processed in Nik HDR Efex Pro 2. They are 80-100MB in size. When I export the images to a file on my Desktop, it consistently exports 6- 10 KB thumbnails. I've checked and rechecked my export settings and can find nothing amiss there. Has anyone else had a similar experience? Could the view I'm working in have anything to do with this? I work 95% of the time in split view.
Thanks,
Russ

I agree that there re a lot of posts about exporting, but a very large number of them refer to the same thing, and it's not a bug, but rather a misunderstanding.
For instance:
Tried exporting a batch of images as JPEGs at the 50% original size setting.
Okay.
The master files are large 16 bit TIFF images from Nikon D800 RAW files, post-processed in Nik HDR Efex Pro 2
Not relevant.
They are 80-100MB in size.
Not relevant either.
Why?
Because size refers to the dimensions of the image. So a 1,000 x 1,000 pixel image exported at 50% will turn out as 500 x 500 pixels.
Were you expecting a jpeg between 40 and 50 MB? That's Jpeg quality or the amount of compression applied to the image. And as you're compressing a lossless format (tiff) to a lossy one, and one with an aggressive compression algorithm, he resulting Jpeg, even at high quality, will be much, much smaller, more likely in the 6 - 8 MB range.
That's the nature - and indeed the point - of Jpegs.
So, if you're getting 6 - 10 kb images, you're exporting at a very low Jepg Quality.
This may also explain why it's taking so long to export. Getting rid on 99.99% of the data and compressing into 10kb is always going to take time.

Crystal XI R2 exporting issues with double-byte character sets

NOTE: I have also posted this in the Business Objects General section with no resolution, so I figured I would try this forum as well.
We are using Crystal Reports XI Release 2 (version 11.5.0.313).
We have an application that can be run using multiple cultures/languages, chosen at login time. We have discovered an issue when exporting a Crystal report from our application while using a double-byte character set (Korean, Japanese).
The original text when viewed through our application in the Crystal preview window looks correct:
性能著概要
When exported to Microsoft Word, it also looks correct. However, when we export to PDF or even RPT, the characters are not being converted. The double-byte characters are rendered as boxes instead. It seems that the PDF and RPT exports are somehow not making use of the linked fonts Windows provides for double-byte character sets. This same behavior is exhibited when exporting a PDF from the Crystal report designer environment. We are using Tahoma, a TrueType font, in our report.
I did discover some new behavior that may or may not have any bearing on this issue. When a text field containing double-byte characters is just sitting on the report in the report designer, the box characters are displayed where the Korean characters should be. However, when I double click on the text field to edit the text, the Korean characters suddenly appear, replacing the boxes. And when I exit edit mode of the text field, the boxes are back. And they remain this way when exported, whether from inside the design environment or outside it.
Has anyone seen this behavior? Is SAP/Business Objects/Crystal aware of this? Is there a fix available? Any insights would be welcomed.
Thanks,
Jeff

Hi Jef
I searched on the forums and got the following information:
1) If font linking is enabled on your device, you can examine the registry by enumerating the subkeys of the registry key at HKEY_LOCAL_MACHINEu2013\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink to determine the mappings of linked fonts to base fonts. You can add links by using Regedit to create additional subkeys. Once you have located the registry key that has just been mentioned, from the Edit menu, Highlight the font face name of the font you want to link to and then from the Edit menu, click Modify. On a new line in the dialog field "Value data" of the Edit Multi-String dialog box, enter "path and file to link to," "face name of the font to link".u201D
2) "Fonts in general, especially TrueType and OpenType, are u201CUnicodeu201D.
Since you are using a 'true type' font, it may be an Unicode type already.However,if Bud's suggestion works then nothing better than that.
Also, could you please check the output from crystal designer with different version of pdf than the current one?
Meanwhile, I will look out for any additional/suitable information on this issue.

Action batch export issue with image trace

So, currently I'm working on batch processing jpeg sequences using illustrator's image trace and distortion effects. I have batch exported the image traces of the sequences via Adobe bridge. Now I'm trying to create an action which opens the .ai files containing those image traces, apply a graphic style to the trace, and export a png from that. I'm banging my head against the wall trying to get this to work right now. If I do the steps (step by step... not using a recorded action) I want on a single file, it works great, but the moment I batch export using the action I've created, it puts the original .png image that the image trace was linked to, on top of the image. The result is a bunch of .png exports that look exactly like my original image sequence. If I add a "save" function to the action and open the resulting .ai files, I can see that the image trace vectors are in the file. The "linked png" however visible on the layer above those vectors. Anyone have any idea what I'm doing wrong? How do I get rid of that pesky linked image.
Also, for anyone who might be thinking that it has something to do with expanding the image trace before applying effects, this issue I'm running into, I've determined, is happening higher up in the hierarchy of the actions... If I simply make an action to open the image trace illustrator file and save it back out, the same issue occurs... placing the .png "linked file" on top of the vector image.
While I'm at it, I might as well ask if anyone knows how to change the illustrator default image trace preset.... Without being able to change it, or much less specify in the action sequence that I'd like to use a user created image trace preset rather than the default setting, it's greatly overcomplicating my workflow. Makes what could easily be one-step batch processing into two. Seems pretty silly if you ask me.
Please, if you guys have any insights on this, let me know. It's super frustrating... By the way, if you're wondering what type of effect I'm going for, the idea (as well as some explanation into their own process) starts at 12:44 of this video (http://vimeo.com/77427470).
THANKS!

Just wanted to let you guys know, for anyone who might be having my same issue... My home computer, even after a fresh install of Illustrator, was still placing the linked jpeg over the traced vector shapes when batch exporting... I did however find a workaround. Rather than using Bridge CS6 for the batch image tracing, I used Bridge CS5 to trace in Illustrator CS5. Then, I used Illustrator CS6 to batch export an action that imported and applied an effect to those image traced sequences. When you do this, it forces you to expand the tracing on import (because of the difference in Illustrator versions I'm assuming). This way, when you batch run the action, it's already working with expanded vector shapes. Not sure why this works, but it does.
Also, I was having some issues getting Illustrator to apply the graphic style when batch exporting. I got it to work by copying an object with that particular graphic style to the clipboard, then adding in the action I was running a "paste" command, followed by a "clear" command. I can only assume that Illustrator was having issues loading custom graphics styles while batch exporting. The paste/delete technique is annoying, but gets it done.
Anyways. Just wanted to check in on this one. I'm happy I was able to muscle my way through it all.

Exporting Issue with Nikon D7100

Similar Messages

Maybe you are looking for