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.

Messages - bpv5P

Pages: [1] 2 3 ... 7
HDRmerge is not useful for movie seqences.

And where exactly I have said it is?

For still image hdr work it's ok most of the time.
About your 18 photos suggestion I think you missed the point with this post.

I don't. You haven't understood my comment. The 18 images are not meant to be used for one single SR, it's meant to be 6 images for each of the 3 different exposures, then the 3 results from SR be merged again with the Ceronoice technique, to generate a nearly ideal image (excluding optical errors).
If you're biased towards only one application for SR, fine, but it doesn't mean it's not useful for other applications.

ps. I'm out, sorry.

I'll suggest it again, just to be sure someone reads it (I know you guys are just experimenting for now, and I know SR is not a new thing): it would be great to put SR in HDRMerge.
Most images need 3 different expositions (-2/0/+2) for near full dynamic range. The SR you presented uses 6 images, so we would need 18 photos to start working. Not practical for many applications, but it would be very useful for landscape or low-light static scenes, for example. Imagine you get a low-end camera and produce images with the quality of a hasselblad. No noise, +16 f-stop DR, no color artifacts, no aliasing. No need for denoising or deconvolution. It would also be good for scientific community, to generate more close to the real images.
HDRMerge already has a align algorithm built in. The SR implementation you are working needs a debayered image to work? Because HDRMerge does everything on DNG, that's the ideal.

Sorry for asking here and not googling  :P

But is there an easy command line option, with convert, for converting all tif's in one direcory to ppm files ?

See command "convert" inside the imagemagick package. If you're on debian-based gnu/linux system, use "sudo apt-get install imagemagick" and then "convert foo.tif bar.ppm".

A integration of it on HDRMerge would be cool...

General Chat / Re: Apertus Axiom Beta
« on: November 17, 2017, 02:51:22 PM »

I looked at auto ETTR, but not being able to set the shutter speed means I basically can't use it, unless there's something missing here? I don't want shutter speeds of 1/500 for a 25fps timeline.

In this case you should use a ND filter (if you don't want to close your lens aperture). You can also do ETTR manually, for best results. Get the raw histogram from global draw menu. Set your shutter speed (for 25fps you should have minimum of 1/50), the aperture and then using the ISO get the exposure as high as you can (in most high-end cameras you can push as high as +2 f-stops). The image should have much less noise that way.
ISO higher than 600 will probably have bad noise anyway, doesn't matter your technique. In this case, a post-production denoise filter would help (or get artifial lights on the scene).

Raw Video / Re: Problem with playing back whole raw card
« on: November 09, 2017, 12:18:12 AM »
The raw2dng can't read it. The header is probably fucked.
Can you reproduce this error? Other files recorded with this camera gets the same error?
You could send the file as @dford suggested, if it's not something that require strict privacy. Compression with LZMA2 can be done with 7zip (again), so it will take less time to upload.

Nice, thanks :^)

Raw Video Postprocessing / Re: MLVProducer: [v3171]
« on: November 08, 2017, 11:12:09 PM »
Got it.
Indexing bug. But not in Code! Compiler option for optimization has ruined the code. OMG Really o_O?

haha, funny. That's why we need more formal methods.

Raw Video / Re: Problem with playing back whole raw card
« on: November 08, 2017, 11:04:19 PM »
You can't now, since the original file is gone (hash algorithms create a unique number for a file, so you can make sure it's not alterated)...

tl;dr unless someone appear with a magical solution or you have the skills to fix the file yourself (it would take too much time and effort to even consider), the files can't be converted. Better reschedule a reshoot. Make sure to use MLV module instead now. Magic Lantern is experimental, sometimes things can go bad.

Raw Video / Re: Problem with playing back whole raw card
« on: November 08, 2017, 10:50:48 PM »
I don't think that's corruption, else it wouldn't decode inside the camera... have you tried to check if your copy is exactly what's on the card (using a hashing algorithm, for example)? Maybe while you were doing the copy it just corrupted. The 7zip has a simple checksum tool, try it, please.

Is it true, though? I couldn't find any confirmation about this.
Also, all software using dcraw automatically apply this curve, Andry600?

Raw Video / Re: Problem with playing back whole raw card
« on: November 08, 2017, 10:18:08 PM »
So, you can play the file inside the camera, but cannot extract the dng from the .raw file?
If that's the case, then the data corruption hypothesis is not the problem. If you make sure you really can't process it with the latest raw2dng, then the problem is also not on the processing software. You also said you copied the files to the computer, so it's read-write.
Considering your hardware is performing well and the software (operating system) is also OK (could try in another computer?), I can't see the solution, sorry. Maybe some developer have the answer...

Raw Video / Re: Problem with playing back whole raw card
« on: November 08, 2017, 09:19:38 PM »
The data is probably there, since the file is not empty.
Try another software, so you can confirm that it's not a MLrawViewer issue. If none of them can open it, try to put the card back in camera, turn on the file_man module and try to playback the .RAW file inside the camera. If the preview works, then you're data is actually there, but for some reason you can't read it. In that case, it would be needed more information about your system (maybe the filesystem is read-only?)...

What bitrate are you using, 10, 12 or 14 ?

bitrate != bitdepth

Check the default gamma and black level, as @Danne said. If nothing works, do some testing:
1- Save your configuration profile from Resolve.
2- Uninstall it and remove all folders/configuration files.
3- Flash latest compilation of ML nightly builds.
4- Record a small footage on all bit depth possible
5- Reinstall Resolve (do not load your configuration profile)
6- Open each of the test footages

All of them are dark? If all are dark, then it's probably not a issue with Resolve. If no one can reproduce it on Resolve, then the issue is on primary conversion (in your case, Swift). In the last case, you should talk with the developer...

Raw Video / Re: Shooting raw monochrome?
« on: November 07, 2017, 08:02:16 PM »
You can't recording RAW in b&w on normal canon cameras. Learn how bayer filter works, so you will understand that.
Some Leica digital cameras are especially designed for b&w photography, but that's not the case here.
About configuration, there would be no difference from color recording.

Camera-specific Development / Re: Canon 600D / T3i
« on: November 07, 2017, 07:51:44 AM »
So what is the highest continuous resolution you get from 600D with 10bits?

Sorry for the late reply...
On a SDXC Toshiba Exceria card, the speed is about 19.5 MB/s (according to the quick benchmark - global draw off).
So, the maximum resolution for continuos recording, in 16:9, is 960x540 10bpp.
On 2.50:1 aspect ratio, it's possible to record 1280x512 10bpp continuous.
I don't advice you to record above 640 ISO. Try to stay bellow 400.
I did a comercial project using MLV on 600D, it went not so well, although the I could finish the work and the cliend liked it.
If you want to know how MLV perform, compared to x264, on 600D I would say: try it yourself. Sometimes you'll get better results from a upscaled MLV, other times (especially at night) you will get very bad results.

If you want seriously experiment with MLV, try some camera with CompactFlash support (50D, for example).

Raw Video / Re: Shooting raw monochrome?
« on: November 06, 2017, 02:48:04 AM »
Unless we only record Green channel (stop recording of Red-Blue) and interpolate later... but, even if that's possible, it would have a very bad quality (aliasing/moire).
@70MM13 there's a option in RawTherapee in the demosaicing panel called "monochrome".

Camera-specific Development / Re: Canon 600D / T3i
« on: November 04, 2017, 11:36:04 PM »
Hi guys,

I can not get my 600d with san disk ultra 64GB 80MB/s exfat and latest experimental build to run continuously in 10 bit raw, 1280 @ 2:35 / 24fps mode with sound. Recording stops after 10-12 seconds.

Is there something special I should be aware of?


The maximum speed of 600D is about 25MB/s. That's the bus interface limitation. You can test your card using the benchmark tool inside ML.
You can probably stretch some more seconds disabling Global Draw (using HacKeD preview on MLV menu) and disabling sound rec (use external recorder).

Share Your Videos / Re: Second Crack at the Whip
« on: November 04, 2017, 11:17:20 PM »
I’d love to see your footage if you have a link?

Oh, I'm not that good to link you some of my works... I use a old 600D and Takumar lenses, nothing compared to the quality of your video, really.

Mlvraw viewer > Dng with a log c profile
Dng into resolve > export to Pro res LT
Edit in premiere and chuck a LUT on.

It's a good workflow, but if you want even better results you should convert the MLV to CinemaDNG and do the color grading on Resolve, and export to ProRes. So, Premiere should not touch the color grading, it's the Resolve part of the process.
The ACES color processing would possibly be better than Log C, but I don't know about the color precision, since Canon cameras are not calibrated to it (as discussed on the thread linked above). Give it a test and post the results! :^)

As for the light, my maximum aperture is f2.8 and I do have an old 50mm Pentax f1.7 however my trouble is a cropped sensor, first being the low light performance and second a 50mm is effectively a 85mm.

Oh, yeah, that's a problem. The APS-C crop (1.6x) is very big...

My plan is to save for a second hand 5d mkiii, higher res, faster cards, just seems a better route to me?

I think 5D MKIII is your best option today if you want video quality and not waste too much money on high-end cameras like RED or Alexa.

Share Your Videos / Re: Second Crack at the Whip
« on: November 04, 2017, 01:18:13 AM »
Fuck yeah, beautiful! Much better than my own footages.
Have you tried color grading with ACES? Also, if you got some money, give it try to these cheap old lenses, like Helios 44. You would get much more light from those and get less noise...
It's great to see you using my tips!

edit: see this, but you already got the idea better than myself.

Post-processing Workflow / Re: Premiere Pro & 2:35 aspect ratio
« on: November 03, 2017, 08:54:28 AM »
You have to turn on the "Synthesize Edges" option. If your footage don't match the sequence aspect ratio, then you need to apply "nest" first (right-click on the clip > "Nest")...

Share Your Videos / Re: 60D 60fps RAW Test Video
« on: October 29, 2017, 02:06:27 AM »
It depends on what software you're using, but most of them will interpolate using bad algorithms (nearest-neighbor interpolation). If you want good quality you should use something like Lanczos. There's some software that does this good interpolation, just search for it (I even think that there's plugins for premiere pro and after effects, I used to use AVIsynth's Spline64, though).

Camera-specific Development / Re: Canon 600D / T3i
« on: October 29, 2017, 01:59:45 AM »
@bpv5P - Yes, it is strange that we're directed to Pelican's website for old firmware versions but he's got the most complete collection.

That's the point, why not mirror the files?

@bpv5P: I have to say that I'm not happy with your view on user pelican who is around us for more than 5 years.

I don't have a bad view of "pelican" specifically, that's just my default mode.

You're aware this kind of argument does apply to the devs, contributors, anyone offering a link, too?

Yes, but the code is open source, the website don't runs too many nasty things as the pelican website and it's not distributing a compressed file with unknow binary. All ML builds has the code, changelog and (now) tests (on QEMU). We can compile and check for ourselves. There's a big difference between the two cases.

I'm fine with all ideas trying to get rid of single points of failure.

Decentralization without security/safety is for dummies.
You're trying to apply a good concept with the very wrong implementation.

BTW: There are some prominent examples where big web based services failed, their user databases got public or - like recent - got unusable by changing terms of use.

This is a admin issue. Database should always be encrypted. (edit: and a backup of this database)

Pages: [1] 2 3 ... 7