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 - chadat23

#1
@domasa
That sounds good, I'm hopefull that adding that won't be too bad.
#2
IDA_ML,
I've never tried that. I have a 6d which can't handle high resolutions and "normal" frame rates so I've just never really thought about it. But that seems like it could be a good option.

Domasa,
I forgot that LRT has a custom export preset that opens an additional video rendering tool. Using my tool, I've always just exported high-quality JPGs and then imported the image sequence into my video editor de jour but I have actually been considering rendering individual sequences before trying to turn them into a final video with multiple sequences and music and stuff since video editors tend to choke a bit on image sequences.
A long term goal has been to make a tool that works for most cameras (not just Canons) and more than just LR so I'm a bit reluctant to tie it to LR even more than it already is. That said, I can imagine having a tool in BrilliantImagery where you point it at the folder where you're exporting from LR (or some other photo editer using normal user presets) so that once it sees that all of the photos have been exported, it renders them into a single video. Would that accomplish what you're looking for?
#3
Thanks! Are you referring to JPG export presets (I'm still on LR6 and haven't used LRT in forever so maybe I'm just missing something)? I haven't put too much thought into some of that stuff since setting up a User Preset is relatively easy and different people have different needs (resolutions, quality, aspect ratio, etc). That said, I'm open to suggestions if people want particular features, changes, accompanying tools, or even just recommendations.

Similarly, I have another tool that's still very rough but, with a simple little user interface moves files from an SD card to a user-selected destination and converts everything with Adobe DNG Converter in one step (including dual-iso images after it processes them with the cr2hdr converter), and does a much better job of using all CPU cores than Lightroom so it makes for a relatively painless ingestion process. That's something else that I'd be happy to share if people are interested.

Chad
#4
Here's an app that I'm writing for deflickering, ramping, and stabilizing DNG files that are part of a timelapse. It does this by editing embedded Lightroom data.

The app has a similar workflow to LRTimelapse but with a few key differences. Instead of working with Lightroom sidecar files, it directly edits the xmp data that's in the DNG files (like what Lightroom does). Also, instead of relying on an exteral app to render each image, the app does it internally with its own custom DNG read/write/render engine. This lets me do things like only render the parts of each pic that I care about when deflickering (which speeds up the process), not have to rerender between deflickering runs that continue to reference the same portion of the image, and more interestingly, it lets me stabilize shaky image sequences by adjusting crops after comparing rendered images.

Additionally, while it's not presently a main priority, I'm most of the way to being able to do things like creating DNGs with reduiced noise from comparing other DNGs, or automatically removing flying birds or bugs from timelapses.

You can find it at https://www.brilliantimagery.org/

While it's still rough in some regards, I'm pretty happy with the results. Here's something I made with an earlier version.

Edit: I should throw out that I'm expecting to expand it to work with other editing software that works with DNG files, whether they store edit info internally, or to sidecar files. When and what I work on will largely just be a function of what people are interested in and what sounds interesting.



I've gotten a lot from this community and hope to give a little back!

Chad
#5
General Chat / Timelapses with a "beat" pattern?
February 10, 2019, 09:33:17 AM
Often when I capture timelapse sequences they seem to have a "beat" to them, an almost regular shake to them. Any thoughts on what would cause this or how to prevent it? It does seem to be more prevalent when the tripod's on something softer like dirt as opposed to a big rock or pavement, but if it was just the ground squishing I wouldn't expect such regular movement.



And for those tinkering with DNG file internals, I checked and the Active Area and Default Crop Origins are constant.

Chad
#6
Accounting for nominal vs. actual shutter speeds did previously make things a bit better but it's still distinctly flickery.

I took some pictures with a constant fstop of 4 and a constant iso of 100. From playing around I knew that ettr would settle on 5s shutter, f/4, & iso 100. All of the shutter speeds were manually entered other than the "ettr 5"s which ettr calculated. Here's what I got. I'm now wishing I did more replicates for more statistical significance but regardless, there's a definite pattern and it looks like auto ettr is settling on values other than what's showing up as the nominal values. It looks like ettr is controlling the shutter or maybe some combination of knobs to the nearest 1/6 stop but again, I didn't do enough replicates with tight enough experimental control to be confident in that. Looks like unless I find some buried dng metadata or come up with something really clever, my algorithms won't play nice with auto ettr.

And sorry about the bad formatting.

Shutter    crs:Exposure2012                Theoretical EV from 5s        Actual EV from mean of                    Dev between theoretical
                from deflicker.mo                  based on Walter's link        manually entered 5s (-1.898365)      and actual EV deviations
ettr 5       -2.06436                                 0                                        -0.165995                                      -0.165995
6              -2.24175                               -0.34                                   -0.343385                                      -0.003385
5              -1.89454                                0                                          0.003825                                       0.003825
ettr 5       -2.06394                                0                                         -0.165575                                      -0.165575
4              -1.55574                                0.33                                     0.342625                                       0.012625
5              -1.90219                                0                                         -0.003825                                      -0.003825
ettr 5       -2.06266                                0                                         -0.164295                                      -0.164295

#7
General Help Q&A / Auto ETTR match camera settings?
March 19, 2017, 04:52:58 AM
Does auto ettr limit itself only to settings that you can input through the camera's UI, or will it also use in between values and then just set the camera's display and metadata to the nearest value, say, taking a 1/22 second exposure while recording it as 1/20?

I've written yet another deflicker tool. It reads the iso, fstop, and shutter speed info out of the dng files to calculate relative brightnesses in order to set the exposure in Lightroom. It generally works well when I set my camera to manual and make adjustments as needed, but I get a lot of flickering when I use auto ettr. Thanks!
#8
Ha, I updated to LR 6.9 in hopes of I don't know what, but still nothing. Fortunately the command line works.

It's still weird to me that it's not actually going through each file when it says that they're not dual-iso, it goes way too fast. It's like there's a log file somewhere with bad data but I can't find mention of anything outside of the User\{user}\AppData\Local\Temp folder, but clearing that didn't do anything.
#9
I dragged and dropped both unconverted and converted files over cr2hdr.exe from within the plugin bin folder and nothing seemed to happen other than a brief flash of the command prompt.

I never convert things that way so I don't know what to expect but no dngs ended up in either the bin folder or source file folder.

And I just took and processed a picture just to make sure there wasn't a more basic software problem. It worked fine.
#10
Also, I don't know if this is related or not, but all of the converted CR2s have grayed out thumbnails in the LR gallery and are marked with a black flag.

https://drive.google.com/drive/folders/0Bws9ohqtRnYeTzEtVkFpUTdRelE
#11
Using the Lightroom plugin 3.0-BETA3.3 (Lightroom 6.8) on Windows 10 I converted a mid-day timelapse sequence (lighting didn't change) where every shot had the same exposure. 40 ish photos from the middle of the sequence didn't convert and I still can't convert them; when I try it just immediately finishes and lists them under the "No Dual ISO" tab. I've had this happen before when processing gets interrupted for some reason and have been able to solve it by restarting my computer but it's not working this time. Thoughts? Thanks!

Chad
#12
Share Your Videos / 6D landscape timelapse
February 28, 2017, 07:35:57 PM
Here's something I made with a 6D using the ML intervalometer and, for some shots, dual-iso.



Camera: 6D
Lenses: Canon EF 24-105mm f/4L IS USM and Samyang 24mm F1.4
Software: Lightroom, something I'm writing to do lighting transitions and image stabilization natively in DNG, and HitFilm
#13
I was imagining accomplishing what a graduated neutral density filter does using the camera iso setting above a user defined line and a ML defined iso for below the line. Being able to angle the line could be nice but isn't necessarily necessary. Maybe you'd also get a marker when using Live View so you wouldn't have to guess and check as to where the line is. Thanks

Chad
#14
I've been post processing dual iso pictures with BarracudaGUI, I have exiftool selected where it's looked for in the settings. It's in the same folder as cr2hdr.exe. However, after processing, when I look at the file properties all of the camera specific information is gone and only the basic file information remains. Any idea why this would happen or how to fix it? Thanks

Chad