Messages

Thanks for easing my life, this connection is killing me

I am downloading, will take some time.

Tried CBR 20 Mb/s and it had the same result.

What is your bitrate settings? Try to put CBR 20Mb/s... I don't think it will generate a file with much of blocks, but, if it do, try to export directly with command line x264. If you get the same result, check your hardware.

Sorry, but what is this file you embedded in "x264" ?

I have a crap connection and don't want to waste time downloading a 7.8 mb file if its not to any use?

And yes I'll try that.

You are not using the render files on export?

Not sure what you mean about this?

I think we're getting closer to a solution here or atleast to what the problem might be.

The DNxHD file is 1920x1080 cause thats the only resolution you can render out from the AVID DNxHD Codec (free one that is), the RAW footage is 1920x872 so it is stretched when looking at the DNxHD file and I have to put in 2:20.1 aspect ratio in order to watch it properly in my player. I wrote in an earlier post 1920x1080, that was not true I meant to write that it was not upscaled or anything, but the PP project is 1920x872 and is rendered out the same and is perfect in premiere. I suppose it is actually "upscaled" because it is stretched vertically.

I am recording in 1920x872 because I started this project on my 5D MK II more than a year ago, 2 months ago I upgraded to MK III. The MK II can not record 16:9 continuously without dropping resolution quite low so I decided to stick to max resolution possible with continues recording and I do also like wider aspect ratios more than TV 16:9.

So I am suspecting that PP has a problem with this 2:20.1 aspect ratio that is stretched to 1920x1080 and then re-squeezed ?

Here Pravdomil says, "Only two features are remaining (1880 width and  crop marks for GLDraw Off)"

Correct Cropmarks with Global Draw off would be killer!

And just having cropmarks work properly even with GLdraw ON would be awesome too. It was a rarity for me to have the cropmarks appear.

You've been digging deep to find this old thread.

I suppose you are recording with raw and not MLV as you are having this problem.

What you need is a raw2dng that is specific to your camera model. What model are you using?

I have raw2dng for 5D MK II lying around

You can also with EXIF tool write in the UniqueName of you camera model and just use whatever converter you have and that will give you the right Camera Profile.

Search the forum for EXIF tool

I'd happily send you some, but my connection does not allow it. 10 kb/s will take days and I lose connection now and then

I will return home with two weeks, I don't know exactly when.

If I find a solution in the meantime, I will write here and if not I will write here also and put some files on dropbox for you

Do you mean the DNxHD files or h264 export?

I will try and upload screenshots off DNxHD source file and the h264 for comparison

Edit:

https://www.dropbox.com/s/yjfdt81xtz4pegm/DNxHD.jpg

https://www.dropbox.com/s/99yxpxug1im2wkj/h264%20Aliasing.jpg?m=

These two illustrate the problem better:

https://www.dropbox.com/s/oyhnq7xkvt4u8ts/Gallar%C3%AD%20DNxHD.jpg DNxHD

https://www.dropbox.com/s/76nbqlxgsr6vd35/Gallar%C3%AD%20h264.jpg h264


Not a frame to frame comparison, cause the h264 export has been cut, but no matter, the DNxHD has none of the aliasing.

Download the jpeg and zoom in and you see it's at a specific interval that you see these lines pass throughout the entire image.

The developer has been gone for almost a year now.

I don't think any more changes will be made to this program.

I enjoy this program the most for raw_rec though.

Thanks for your suggestion, but this did not work. It made it worse.

The rendering time was 20x times longer

Had exact same settings but the finished product has a bitrate of 820 kb/s ??

I'm really confused about all this.

Think I'll have to figure a way to get it in to AE again and render from there, just a pain with all the transitions and texts and stuff.

This can't be a hardware problem, right? I mean when AE manages to export sharp and without any aliasing.

Raw files are also 1920x1080, so there is no aliasing in original footage.

EDIT: does PP have a problem with DNxHD footage?

Running CS 6

Not sure what you mean.

In Nvidia Control Panel, for Premiere I put Power Management on High Performance and tweaked some other options for better performance.

Do you think this has anything to do with it?

Hi.

I've exported from PP before and I don't know if I missed something but now all my footage comes out with this pixelated Lines or combination of aliasing

The source files in Premiere Pro are DNxHD - 1920x1080 - 23.976 exported from AE and they are super sharp, no pixelation or aliasing, but when I export to h264 the quality dramatically drops, I have no idea why, I am very sure that I am doing exactly what I've always done when exporting h264 from Premiere.

Export settings:

h264
1920x1080
23.976
Square Pixels 1.0
Progressive
Profile: High
5.1
Target mb/s 100 and max 100 - VBR 2 pass
also tried CBR with same effect.

I am out sailing and only have a slow laptop so it's too hard for the computer to dynamic link. Usually just leads to a crash

Any ideas what might be wrong?

If need I can try and upload screenshots, but might take awhile as my connection is at 5-10 kb/s

Thank you.

Not so familiar with Resolve, but instead of rendering out of AE, can't you just open Adobe Bridge, apply VisionLog to the DNG's/CDNG's and then import in to Resolve?

Thanks for sharing

King a.d. is back!

Sorry to break the current flow of your discussion.

But I got a question about the latest development regarding higher fps and higher resolution.

Am I correct to understand that the footage is no longer stretched? and if so, is 1920x872 2:20.1 at 48 fps possible?

And is this fps hack also possible on 1.1.3?

Thank you

Is 40 fps 1080p available in 1.1.3 ?

or is this specific to 1.2.3 ?

I think your problem is AVID... Hate that program so much

AVID is oldschool, do you know how to properly import files?

I don't remember how, but think you need to "tell" AVID that you are searching for DNxHD.

Thank you for all your replies, this has given me a much greater understanding of Flash.

But this TRIM command, is this also functioning within a DSLR?

And do you think the severe fragmentation I saw when running the cards with FAT32 are the blocks/pages that are "empty" or ready for rewriting ? Never seen a HDD with 40-60% fragmentation.

And just to clarify. The best way to ensure a peak performance is to run a Quick Format, correct?

I recently upgraded from 5D MK II to MK III.

So now I'm in Exfat world.. On MK II where I was running my cards with Fat32 I regularly defragmented my cards because after filling a card with RAW footage and exporting to computer the fragmentation would be around 50% sometimes higher, sometimes lower.

But as I understand by googling a little, Exfat can not be defragmented. Is this because Exfat does not get fragmented ? or its simply not possible?

I find it hard to believe that it does not get fragmented when it is so severe in FAT32. So I am worried that I am running around with slower than need to be cards because of fragmentation.

Anyone know something more about this and how to defragment Exfat? (if need be)

Thank you.


(Maybe this is in the wrong section, but it's to do with RAW recording)

Got the last ffmpeg but everything got this weird but kinda nice teal cast, though it is absolutely not correct, it is inspirational. But the UI is terrible in my taste and it doesn't seem to read the fps of the source files, it only goes with what the presets have. Could not see in the metadata either that it reads fps.
Also, I was once able to choose AVID DNxHD but after that its just been stuck on that preset and I can't get back to selecting anything else. Thought maybe this could be an alternative to watching MLV/RAW files, but seeing as MLRV is lightyears ahead at this stage, I'll stick to that.

But thanks for sharing.

Note that while this is automatic, there would still be a approx 1 or less than 1 second gap between the 4gig clips. Heat issues is still the same as with stock firmware.

I have to say that I have recorded tons of footage over the 4 gig limit and never experienced a gap between the 4 gigs. I thought I was seeing skipped frames at a time when watching <4 gig footage in MLRawViewer, but found out that it was only MLRV that jumped to the next file at every 4 gig mark. When merged and exported, there was nothing wrong with the footage.

So what's going on at Vision Colour?

They making a new Colour grading program or new luts? Anyone got some inside knowledge?

http://vision-color.com/

So say I unsqueeze 1920x540p to 2:35.1 1920x818

In reality I am just upscaling 540 to 818? am I right ?

Or is there something I don't know?

Edit: found this post which explains it http://www.magiclantern.fm/forum/index.php?topic=5472.0

Could you answer a question for me?

I recently ordered the MK III and have been using ML Raw on the MK II ever since first released.

Now I'm speed reading the MK III threads and I read a lot about Banding, bootflag problems, but it seems like its something everyone should know about, but I don't. On the 5D MK II I have never heard or experienced any issues of that kind.

Can you give a little explanation to what banding is? I don't notice anything weird in your video. Is it lines?

The Ducati video is filmed on the MK III so it's native 1920x1080 it also seems to have proper Light setups in the the garage which is more important than just camera speccs.

Your video seems not to be even upscaled to HD

Other than that your video seems to have a lot of compression, more than normal youtube compression. But it's hard to tell.

I'm pretty sure Vegas has a template for youtube, which you should use and then tweak for extra quality.

And the grass is always greener on the other side.

The Avid DNxHD Free version that you are using only produces a 1920x1080 footage. So even if you render a project that is 1920x818 it will still come out as 1920x1080 (stretched)

A head on solution would be to do your project in 1920x1080 so you have the 2.35:1 black border.