Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - P337

#26
Archived porting threads / Re: First 7D alpha released!
November 04, 2012, 12:30:19 PM
True, unless it reads the entire sensor 60 times per second then scales for 720p ...or does it just skip more lines to begin with?

Also my "LiveV FPS" usually displays 60fps, but I'm not entirely sure what that means yet lol.
#28
Quote from: Shizuka on November 04, 2012, 08:56:12 AM
Hardly, you will see more blocking from jpeg compared to h264, as jpeg lacks in-loop deblocking. You will likely see more motion artifacts from jpeg as it does no sort of motion compensation. It would be better if the h264 engine could be used in place of jpeg, but it's probably impossible due to the h264 encoder's fixed input sizes.

aww :( are you sure it's that bad?  Either way this is the best JPEG could offer so I'm happy for that and if that's still not good enough there's also a full 422 option ;)
 
I may have miss-termed "motion artifacts", what I meant was prediction errors as these are all full frames like an intra codec.
 
#29
Quote from: akshayverma1 on November 04, 2012, 07:40:02 AM
I was getting higher bitrates with the previous port. But with the new port's CBR there's very few artifacts. Noise reduction works so well :) VBR with Qscale -16 is almost as good as CBR at 20x. Can CBR be pushed to more than 20x? Also, which is better, jpeg or 422?

I think the last build was All-I, which pushed bitrates higher but also needs a lot to avoid compression artifacts; if your card isn't fast enough you're likely to get compression artifacts.  What bitrates were you getting and what's your card benchmarking at?

.422 seems to be uncompressed 4:2:2 frames while the jpegs are 4:2:2 compressed.

My jpeg files were 98-623KB, which are 15:1 to 2.5:1 compression ratios of the 1.5MB .422 files.  Those compression ratios are JPEG's "Highest" and "High" Quality compression standards, so they should be clean from compression and motion artifacts ;-D  Which only leaves line skipping and an 8bit color depth to worry about right? 

They're good clean quality, except they are only 1056x704 so they need resizing to 1290x720(about 25% increase) or 1920x1080(almost 3x larger) so clear overlay HDMI out with external recorder will still have better quality but that requires having an external recorder :/
#30
Quote from: mimiloveyou on November 04, 2012, 05:31:44 AM
How do I use MJpeg 422 ?

Thank's.

Right now it's in the "Debug" Menu called "LV Dumping". 
Scroll to it and press the "set button"; there are 7 choices: "Disabled", "A:/.JPEG", "B:/.JPEG", "A:/.422", "B:/.422", "A:/.JPEG/.422" and "B:/.JPEG/.422"

The second you select one it starts saving (note the red "busy" LED) your LiveView buffer as .jpgs or .422(or both).  The choices with "A:" saves them to your card, I'm not sure where "B:" is but I heard that maybe for dual card cameras.

Once you plug the card into your computer you'll find all the jpgs or 422 files in your DCIM folder.  Then you need to make them into an mov file, like a timelapse.
#31
Been playing with Canon's bitrates and I think I understand it better now.

"VBR (Qscale) mode" in 7D seems to be used kinda like constant bitrates or rather "limited range bitrates".  For example, recording the same scene with the same exposure settings on Qscale(+16) recorded at 1-2Mbps, (+15) was 1-3Mbps, (+14) 2-3Mbps, (+13) 2-4Mbps and all the way up to 42-76Mbps for Qscale(+16).  It's like limiting the entire VBR spectrum to a smaller range, then Qscale sets that range high, low or somewhere in between. The range gets wider with higher quality settings (lower number) but the important thing is that it brings the lowest possible bitrate up.

"CBR mode" I assumed takes the bitrate "range" that is set by Qscale then multiplies it by a number of your choice (2.0x, 3.0x, etc.).  CBR mode also tries to automatically set the highest Qscale it can (which is -16) but if your card or buffer is too slow is starts to scale it back, I got Qscale(-16 to -10) in CBR mode with a FlushRate of 4 but a constant Qscale(-16) with a FlushRate of 2.  But what I still didn't understand is why are my bitrates in "VBR mode" with Qscale(-16) the same as "CBR mode" with Qscale(-16) set to 20.0x? 

I've recorded with this card at an avg 160Mbps so I know it's not a hardware limitation. 
So does "CBR mode" not multiply Qscale, does it just increase the selected Qscale's range upward?
Is most of that right so far?  Thanks for everyone's work and help here ;D
#32
Is Qscale 10 the same as QP 10?
#33
Thanks 1%

Quote from: 1% on November 04, 2012, 02:55:51 AM
As for no difference between cbr 10x and 20x or whatever... some scenes just encode to X rate even at 100% quality from the camera.
Does that mean a static scene may just ignore "CBR" settings and base it off the first frame's complexity?

Quote from: 1% on November 04, 2012, 02:55:51 AM
Tip: Go outside... indoors it doesn't get so high (not enough complexity/light), except in crop mode which 7D doesn't have.
Well I don't have a problem maxing out the bitrate indoors, by underexposing with ISO set to 128000, which get my card's full 160Mbps but it's too noisy so I'm trying to get that max bitrate with proper exposure.

Quote from: 1% on November 04, 2012, 02:55:51 AM
You shouldn't have to use CBR only, set qscale to max (do you guys have that yet?) and then camera records at fixed quality. All frames will be QP10.

We just got Qscale, its default to -8 but says "very risky" so I won't play with it until I better understand what it's doing.  All I know is -16 = highest quality and 16 = lowest quality.  Since I don't see -26 on the scale I assume it's relatively safe but I'm still not sure what to look out for.  Recording stopping? Overheating?
#34
oooh, 422 (M)JPEG  and 422 Uncompressed seems to work though ;-D

I enabled Jpeg A: and recorded 24 jpgs per second for one minute on my card (some dropped frames though).

also tried 422 A: but haven't counted the frames yet, I assume they're the same.

Jpgs are 98KB-623KB each (assumed 5:1 compression of 4:2:2) and .422s are 1.5MB each (1:1 uncompressed 422!)
#35
So, I may not be using this right yet but I unfortunately do not see a difference in bitrate with CBR vs VBR(FW default) :/

I got a scene giving me about 40-46Mbps under FW default and CBR 1.0x, I tried the same scene all the way up to CBR 10.0x but they all still read the same 40-46Mbps range (using "display bitrate", haven't analyzed the clips yet).  I'm assuming CBR should keep the bitrate at its maximum even with low detail scenes, like CBR 1.0x = 48Mbps and CBR 2.0x = 96Mbps, if that's not the case then maybe it's working as intended and I just don't understand what it's supposed to do.

Just tried the scene again with different exposure settings to give me 22-29Mbps and got the same results (every CBR setting was still only giving 22-29Mbps).

This may be unrelated and I assume just a display bug but every now and again when I first start recording the Bitrate display will start in the 700Mbps or 500Mbps range for the first frame then just drop straight down to the 20Mbps or 40Mbps range.  Once, when scaling up the CBR quickly to CBR 10.0x, it started at 528Mbps then my camera immediately rebooted itself and ML had to be reinstalled, it didn't record anything but everything still works fine and when I tried again it recorded fine and started in the 22-29Mbps range.
#36
Quote from: g3gg0 on November 04, 2012, 01:00:13 AM
here is another experimental build.

i set GOP to 4 and enabled VBR/CBR selection.

Awesome, thanks g3gg0!

So in this build everything is GOP=4 even at low bitrates?

Thanks again, checking it out now ;D
#37
Quote from: mimiloveyou on November 03, 2012, 12:25:21 PM
How can I do with these things.
I am not a technician.

I want to understand.
how to do.

Thank's.


Sorry for my bad english.

It doesn't seem to be working yet, looks like only the first few frames in a recording are accepting the CBRs.

They are however making pretty good strides in the MJPEG encoder thread, looks like the 7D can take 1056x704 4:2:2 JPEGs from the buffer and record them to the card without needing to be connected to the EOS Utility through USB ;D
http://www.youtube.com/watch?v=jQLHkXL-AWU
#38
Reverse Engineering / Re: (M)JPEG encoder
November 03, 2012, 10:22:19 PM
Ok so:
LV = 720x480p at ??fps 4:2:2 with no frame compressions
HDMI = 1620x910i at 60fps 4:2:2 with no frame compressions
MJPEG = 1056x704p at ??fps 4:2:2 with JPEG compressions?

I've noticed when checking my "LiveV FPS" I get 60fps.
Is that using the 1056x704 or 720x480 buffer?
If the former, then that means it could get 1056x704 in 4:2:2 at 60fps right?
#40
General Help Q&A / Re: 50D users: how are you getting on?
November 03, 2012, 10:54:46 AM
huh, I was wondering this too.  Thanks 50D24fps? lol
#41
Archived porting threads / Re: First 7D alpha released!
November 03, 2012, 10:45:23 AM
Unless you have a 500D ;-P
#42
Reverse Engineering / Re: (M)JPEG encoder
November 03, 2012, 10:33:32 AM
Quote from: g3gg0 on November 03, 2012, 12:56:51 AM
yes, its the LV content JPEG compressed.
1056x704

600D does when USB is connected :(

Nice! how heavy is the Jpeg compression on them?

An uncompressed 1056x704 8bit 4:2:2 image is 1,486,848 bytes (1.5MB) and "Highest Quality" JPEGs are usually a 2.5:1 compression ratio which should be around 600KB per jpeg file.  I read somewhere they were around 300KB each which would be a 5:1 (not bad!) ;D
#43
Hmm, these '4th' generation adapters certainly imply UHS-1 speeds:
http://www.memorypack.com.tw/image/Memory%20card%20reader%20adaptor/sd%20to%20cf/sdcfa_c04/sdcfa_c04%20specifications.pdf

Though I can't help to notice their terminology when describing card support ("supports" vs "accepts"):
Quote
2.1 Features
 SD interface supports SD spec 2.00 / 1.01; supports high speed(Class 10)
and normal speed(Class 2/4/6) SDXC, SDHC, and SD.
 SD interface is compatible with SD spec 3.01; accepts UHS-1 speed SDXC
and SDHC.

That said to me; "It's just like Canon, it'll read and write UHS-1 cards but at Class 10 speeds", then I noticed it also stated it "supports" UHS-1:
Quote
Supporting Cards
SDXC   All Capacities, Class 2/4/6/10/UHS-1
SDHC   All Capacities, Class 2/4/6/10/UHS-1
SD   All Capacities, Class 2/4/6/10

This is all probably just wishful thinking lol but if Generation 3 added support for UHS-1 cards at C10 speeds then I assume generation 4 has enabled UHS-1 speeds otherwise why have it?! ...WiFi?! ...wait it probably is iSDIO, damn...

Either way I've been using their 2nd generation adapter and have no issues getting 92Mbps average/96Mbps peaks at CBR 2.1x with a Class 10 card.  I get 12.8MB/s(102.4 Mbps) with Magic Lantern's Benchmark tests and 11MB/s(88Mbps) over a USB 2.0 reader so it seems to be accurate. 
#44
So I actually came here to ask...

Is there a draw back to using a UHS-1(95MB/s) SD card in an SD-CF Card Adapter over using an equal speed CF card?

The new "3rd generation" SD to CF Card Adapters claim to support UHS so I was wondering if that would actually get UHS-1(95MB/s) speeds in a UDMA 6(133MB/s) compliant DSLR.  Or are these "UHS supported" SD-CF adapters just able to read and write to UHS-1 SD Cards at standard Class 10 speeds like how Canon uses UHS-1 SD Cards? 

If anyone has this setup please report your ML card benchmark scores here.
#45
Quote from: RMAlpine on October 17, 2012, 04:28:35 AM
JUST TO UPDATE EVERYONE:

I got the memory card I mentioned in the beginning of this post with the 95 MB/s speed and when recording at bit rates above CBR 1.4x with audio enabled, it still stops recording after maybe 5 seconds or so. But I can, however, record all the way up to CBR 3.0x WITHOUT AUDIO smoothly and without the card stopping at all.

So it definitely is a MAJOR improvement over my last card which was only a 24MB/s card.

Unfortunately the Canon "SD Card" DSLRs can't record faster than 25MB/s (200 Mbps) and I think "CBR 3.0x" only goes up to about 18MB/s (150 Mbps) but you should benchmark that card using ML's benchmark tool, If you actually are getting higher speeds we'd love to know how, so we can do it too ;-D

Quote from: http://www.imaging-resource.com
The Canon Rebel T3i accepts SD/SDHC/SDXC memory cards, and does not ship with a card. Canon recommends a Class 6 card or faster for recording HD movies. UHS-I compliant cards are supported, but the camera does not take advantage of their increased bus speeds.

...Note that the Canon 60D manual says "SDHC and SDXC cards featuring UHS (Ultra High Speed) enable a maximum writing speed of SD Speed Class 10". We asked Canon for clarification on this, and they said the Canon 60D is not UHS-I compliant but should work with UHS cards at up to SD Class 10 speeds.
and
Quote from: 1% on November 02, 2012, 03:58:03 PM
...on SD cameras the max is 25mbps per the controller.

#46
Archived porting threads / Re: First 7D alpha released!
November 03, 2012, 01:27:00 AM
Quote from: nanomad on November 02, 2012, 11:35:58 PM
FPS override it's not for increasing FPS, but for decreasing it ::)

Ah, thank you for clearing that up.  So I guess it's for easy time lapsing or choppy blurry low light shots.  Timelapse mov files straight from the camera sounds like something fun to play with ;-D
#47
Archived porting threads / Re: First 7D alpha released!
November 02, 2012, 11:33:10 PM
How far has fps override gone in Magic Lantern?  I thought it couldn't do much more frames per second than "Canon FPS" with issues for 180 degree exposures and high rolling shutter.  Can any of the cameras do 48 or 1080p60?
#48
To better test these high bitrates I'm trying to decide between getting a 600x or 400x CF card.  The 600x benchmarked at an avg 640 Mbps (80MB/s) write speed, the 400x I can't find benchmarks for it but their 300x benched at 292 Mbps (36.5MB/s) write speed which is about the fastest we've seen on the 7D.


So do you think this 300Mbps limit is a camera or card speed limit? 

Has anyone achieved any peak numbers over 300 Mbps? 

Do you guys think it's worth even trying a 600x (I doubt it will be)? 
If 300Mbps really is the camera's limit then that's about CBR 6x (right?), so setting any higher values than that or using a card that benchmarks over 37.5MB/s won't make any difference.


If you have a super fast card I recommend setting CBR to 20x and Flush to 1.  Then enable spotmeter and select the 0-255 option.  Then set ISO to 128,000 and use your shutter or ND filters to underexpose to "25" on the 0-255 spotmeter.  This always shoots my bitrate up to it's max but my cards, which are "200x" 170Mbps (21MB/s)*, peak at 200 Mbps for 1 second then the buffer can't keep up** so the recording stops :/

*ML Benchmarked my card at 21.5MB/s
**my Flush rate is set to 2 (my camera throws err70 if flush=1)
#49
Archived porting threads / Re: First 7D alpha released!
November 02, 2012, 04:07:20 AM
Quote from: fotto on November 01, 2012, 08:43:15 PM
Immediately started experimenting with it. I love the cropmarks feature! This way I can make better ones with 3ths 5ths and 7th. Yet I see that not every pixel of my file is showing up. Is this because the 720x480px file is rescaled or what? Any solution? What would be the best resolution to make it in than?

Lay-out wise I don't really like the font for the aperture and shutterspeed in live view. It is much harder to read than the standard canon typography. I also don't like it being colored. Could this become a future option?

I can't wait for HDR video and a build in intervalometer.

You should post that typography under the feature request topics: http://www.magiclantern.fm/forum/index.php?board=24.0
I doubt anyone here would know about that.

You may also have better luck with cropmarks help in the general help topics: http://www.magiclantern.fm/forum/index.php?board=4.0
#50
Thanks 1%

I think I'm starting to get it; they can each be adjusted on their own but pY is still connected to pC so when you set pY to 20 (it's maximum) then is pC also pulled to it's maximum too?  Is that's why any changes to pC after pY is maxed out causes a freeze?