Shot with ML?
If not, please don't post videos not associated with Magic Lantern.
If not, please don't post videos not associated with Magic Lantern.
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
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 MenuQuoteI have confirmed this works! Thank you so much N/A!Very welcome
I have provided a Google Drive Link to a folder with screenshots, pictures, and videos showing the beauty of this:
https://drive.google.com/drive/folders/0Bz5n0qYxIkVOMnJMeWhkU3pMVjQ?usp=sharing
The videos are of my cat in my room, handheld at 50mm. Sorry for the shakiness, I just wanted to test this out with the time I had. I was able to record for 15 seconds.
If anyone has any questions, or can't get to the link please let me know. Thank you to all the Magic Lantern Developers, this is truly awesome!
- Paul Harwood
Quote from: dmilligan on August 10, 2015, 03:00:49 AMSure, I have a couple good examples. It may take a while though, my internet connection is pretty spotty right now.
Do you mind posting some 100% crop comparisons between the two methods for the pixel-peepers?
Quote from: rtf on June 05, 2015, 09:34:49 AMHere's a good thread to refer to for high fps times and combinations-
Thinking of upgrading from the 550D to the 7D. How long can you record in RAW at 1280x544 at 50fps and at 1280x720 in 50fps?
Quote from: DigitalVeil on January 08, 2015, 02:23:43 AMBesides advanced methods used in the adtg-gui module, ML really can't control the line-skipping in non-crop mode, which causes the squashed look in high fps. I found a glitch on 7d that allows for 48 fps raw video that doesn't need stretching in post, haven't been able to push it up to 60 fps though.
Whoa, I thought this whole time the squashed video height in Canon 720p mode was intentional to allow cameras with slower storage to get wider resolutions. This isn't intentional?
It's really strange that Canon's default 720p h264 mode can record 60fps with no squashing, but ML raw in 720/60 mode is squashed even with custom resolutions set well below 720p and FPS set well below 30. Assuming the 7D Mark II eventually gets an ML port, I wonder if that will be the first camera to record 1080p60 raw without squashing (given its 1080p60 h264 mode) or if it will have the same problem when set to 1080p60 mode.
Quote1728x692 48 fps slow mo. But wait a minute... When I play it back, the footage is normal aspect, no stretching required! I'm kinda running on no sleep in 2 days, I need someone to confirm this ASAP. I noticed when I set the cam to 1280x720 60p, and set the fps override to 23.976 exact fps, the liveview display was stretched vertically, so when recording it and playing it back records it in normal aspect! Timer A under 23.976 exact is 422 (FT -76). So I set the fps to 48, and Timer A back to 422. Mlv settings-Here are two frames from these settings. The first frame is with the modified fps settings, opened in MLVFS and rendered out into jpg through LR with no editing done. The second is normal 48 fps override, distorted frame rendered the same way. And also a screenshot of MLVFS to verify that it's 48 fps. Camera was mostly in the same position, with same exposure settings. Looks like the dng's get stretched downward, the top of each frame is in the same place. Interesting...
1728x692
3:2
GD Off
Canon preview
256 MB warmup
SRM On
Hacks on
4 buffers
Reserve on
Global Draw off
Expo override on
Rokinon 35mm manual cine lens
After messing with it a little bit more, the black and white levels get all wacky sometimes and the exposure is super glitchy. At first, I noticed this while testing out different settings in 640x480 mode, going to do some more tests soon as I charge my battery.
:edit: Yeah definitely a bug in the fps override control. I just downloaded the latest nightly, same thing. How exactly does fps override cause LV to stretch? Or is this a new feature I completely missed?!
:edit2: Ok, just figured out that this bug has been in the nightly since 7d fps override was implemented.
:edit3: To fix this issue, Timer A needs to be set to 498 (FT +76) for 23.976 exact and 440 (FT +10) for 60 exact.
Page created in 0.112 seconds with 14 queries.