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

#101
1.3.2 now available for testing

https://bitbucket.org/baldand/mlrawviewer/downloads

Has everything 1.3.0 and 1.3.1 had, plus a few bug fixes:

- The major performance regression in playback should be resolved
- Compressed DNG export should now be a bit faster on dual core machines
- There was a memory leak with the compressed DNG export, now resolved
#102
Quote from: togg on October 04, 2014, 05:40:43 PM
Yes I have it. I'm still using RAW for the extra stability and performance, can I send you this? Do you also need the dngs that are created?

.RAW is fine also, as long as it's more than say 100 frames since bad pixel correction needs a few frames to identify them.
#103
Quote from: togg on October 04, 2014, 09:31:48 AM
It seems to me that yes, it's slower. But without multithread (that it's difficult to implement if I remember it right) this is the max.
For me the only thing is the hot pixel removal, it seems to not have any effect (watching the dng in resolve), if it would be possible to make it effective it would be really useful.

Do you have the stripe correction on (X in the stripes icon)?

If so, and that doesn't work, could you share with me a short sample MLV that shows the problem with hot pixels?
#104
Quote from: Kakiisch on October 04, 2014, 03:03:29 PM
Hi,

First off, thank you for developing such an awesome RAW workflow enhancer!

I've been playing around with the MlRawViewer for a few days now and everything was incredibly smooth until the last test I did which left me helpless. I was recording my RAW files as per usual and put them on my PC. I fired up MLRV, fiddled with the settings and tried to export the footage (one 20sec file with 50fps and one 25sec file with 25fps). MLRV just creates the .WAV-files to the specified directory for both MLVs (e.g. M04-1508.WAV + M04-1508_00.WAV for one file) and then stops the export at 0.00%.


What to do?

Things to check
1. Check the export directory is valid. Press W and select a folder
2. If export still stays on 0%, press Y in case you have paused the exporting process
3. Find the log file and send to me. Look in your home folder for the hidden ".mlrawviewer" folder, and find mlrawviewer.log inside that.
#105
I tracked down the cause of the playback performance regression now and should have a fix out in a couple of days. It was a side effect of changes made to support the histogram.
#106
Quote from: swinxx on October 03, 2014, 02:13:45 PM
@ baland:
Is the problem lack of time, code complexity or the fact that you dont need it?
Your tool is so great - a must for all owners with ml cams. Never heared that the code must be optimized for a special cam,
So tell us how we can make the unlikely happen? Greets

I only have a 7D, so naturally it's optimised for the problems I had on my own camera. The whole tool is designed to "scratch my own itches", and then shared in case it's useful for others.
There are no other primary contributors to the code right now, though I would a welcome anybody with the skills and time to contribute new features.
#107
Quote from: togg on October 03, 2014, 02:01:27 PM
Noob questions. Why the dng obteined with rawmagiclite are brighter? Someone has tried the new compressed dng? Are there some serious quality loss when playing with colours?

Can't comment on the brightness.

The compression is lossless. There is no quality loss.
#108
Quote from: swinxx on October 03, 2014, 10:54:43 AM
@baland:
Would it be possible to include a 5d mk3 tuned vertical stripes correction too? Thx

It's quite unlikely at this point.
#109
Couldn't really see the problem with those samples. But if MLVFS is working that's great :-)

(MlRawViewer stripe correction is more tuned for 7D stripes than 5d3)
#110
@swinxx re stripes you should try with 1.2.3 also to see if it looks the same there. re the performance, is that only on the Macbook with Intel, or is it also slow on something with a discrete GPU?
#111
Download page is at: https://bitbucket.org/baldand/mlrawviewer/downloads

The DNG specification includes a compressed mode which uses Lossless JPEG (1992) to compress the image. This can handle any number of bits up to 16bit with no data loss, and in our case of 14bit images, it typically results in files about 50% the size of uncompressed 16bit DNGs containing the same information.

The compression ratio will be worse with noisier images, and better with clean or blurry images.

Let me know if you encounter any problems.

(The lossless JPEG code is all new - it may have bugs. I do not recommend yet archiving these DNGs and deleting the source MLV files)
#112
Quote from: swinxx on October 01, 2014, 09:26:56 PM
Thank you baland! You are top notch!
Is it possible to download that fixed version anywhere? Cause I have no idea how to compile it ;(

Yes. I uploaded 1.3.1 to the usual place with the LUT import fix for Mac and Win.
#113
Quote from: swinxx on October 01, 2014, 08:50:20 AM
yes, the list stays empty - no luts available although i imported them.. :)

Thanks! I've found and fixed the bug (in git) now. Fix will be in 1.3.1
#114
Quote from: swinxx on September 30, 2014, 11:47:01 PM
second problem is that i can not load any 3d luts? they are not previewed.. 1d luts are previewed..

Are you seeing a regression here? Were you using 3D LUTs with v1.2.3 without problems?
I don't understand the "previewed" description. You import the LUT, then it is available for use - Shift UP/Shift DOWN steps through 3D LUTs. Do you mean that the list stays empty?

Anything in the log file when you do the import?

#115
Possibly a path containing Unicode/accented characters? Those are often trouble...
#117
MlRawViewer 1.3.0 available for testing


1.3.0 is now available to try in the usual place.

Since there a few larger under-the-hood changes in this one, I gave it a new minor version number. As this is the first release in that series, you should expect to encounter some new bugs. I would appreciate it if you can take the time to report any *new* problems you find with clear instructions for reproducing & log files where possible, either here or to the bitbucket issues list.

Main features:

  • S-Log, S-Log2, C-Log and Log-C curves & 1D LUTs contributed by ToS_Maverick
  • Better CDNG playback support. 12bit & compressed DNGs should be supported, including BMPCC & 7Q/FS700
  • Exported DNGs are now losslessly compressed. This makes them roughly 50% of the old uncompressed 16bit DNGs. One downside of this is broken previews in Mac because it can't view compressed DNGs correctly (Same is seen with BMPCC DNGs)
  • RGB Histogram -> Press Shift-H or click the box on right to toggle
  • Imported 3D LUTs can be deleted with Shift-3 key

Features that did NOT make it in yet:

  • JPEG/TIFF/ProRes422 export
  • The disappearing mouse cursor is still not fixed
  • Audio syncing for Resolve
  • DualISO (this will probably never happen)
  • File dialogs still appear under the main window
#118
Quote from: spnsir on September 30, 2014, 02:29:06 AM
Is there a plan to get audio sync in Resolve working?

At the moment I don't know how to do that
#119
Quote from: senzazn12 on September 27, 2014, 02:12:28 PM
When will 1.3 be up?

It's not ready yet, but as soon as it is, I will make a binary of it.  You can follow progress in more detail on bitbucket: https://bitbucket.org/baldand/mlrawviewer/commits/all
#120
Quote from: Kharak on September 27, 2014, 03:08:12 AM
Hey,

I could use some help with importing LUT's.

I press shift+L and choose a LUT, but it is not working. These luts are 3D, but I cant get them to work with MLRawViewer. I press shift+up/down and nothing happens. If I go through the 1D luts (left/right) I only find the ones included from MLrawviewer. Thinking maybe they were interpreted as 1D luts.

Do the .cube files have to be in a specific location?

Or is there something else I am doing wrong?

Thank you.


If you are on windows, you need to apply the patch file on bitbucket to make LUT importing work. Will be fixed in 1.3
#121
The red dot is removed but feature is there. Try pressing Y after starting the export to see if processing starts. Y pauses/ resumes
#122
Quote from: kyrobb on September 25, 2014, 09:05:54 PM
Do you plan to include ProRes 422 export in 1.3? ProRes4444 is great, but it's hard to justify the file size when the cameras themselves are only shooting 422 anyway.

I may include a 422 profile in 1.3. I think you are a bit misunderstanding though regarding "..cameras themselves are only shooting 422 anyway". Raw video is the bayer data straight from the sensor. It's neither (demosaiced) RGB or YUV, hence you can't really call it 422 or 444.
#123
Look for the hidden ".mlrawviewer" folder inside your user home folder. There are some persistant settings in there. Try renaming the folder. If that helps, please send the files from folder to me so I can diagnose the cause.
#124
Update on next MlRawViewer version

I've been working on a few things for the next version of MlRawViewer, due as a binary 1.3.0 release "soon". I just wanted to give a little heads about what's coming (no surprises if you've been following my tweets):

- Some new curves, SLog, SLog2, Log-C & C-Log contributed by @ToS_Maverick
- Live RGB histogram while playing
- Improved CDNG playback support: 12bit DNGs, compressed DNGs (should work with Odyssey7Q & BMPCC CDNGs)
- Compressed DNG exporting, possibly including 12bit+linearisation "near lossless" mode.

I know lots of people have probably moved onto using MLVFS for their DNG conversion needs by now, but perhaps a few of you will still find these features of some use.

After the 1.3.x release series stabilises (might take a few updates), I will probably take a break from working on any major new features for MlRawViewer, and instead look at some different things. Since there are no other primary contributors to the project right now, I expect there will only be bug fix releases for a while.
#125
@aace, @dfgh

Thanks for the reports. More info that could help:

- Mac or Windows? OS version?
- What GPU? RAM? SSD or HD?
- Log file. Look for the (hidden) ".mlrawviewer" directory in your user home directory. Within that should be an "mlrawviwer.log" file. Please send it to me.

Thanks in advance, and sorry about the troubles!

[edit] Oh, and after finding the log file and sending it to me, you can try deleting or renaming the whole ".mlrawviewer" folder. That should set the program back as if it had just been installed freshly.