FS7: LUTCalc v2.54

Michael,

I can't seem to repeat that behaviour. I've just tried LUTCalc Testing under both Firefox and Chrome and settings saved fine. I also checked that I could generate a set of LUTs. I did however find a typo on a variable name which prevented them from being loaded back in fully. I've just corrected it and uploaded the fix so thanks for that at least! :-)

What browser and OS are you using? Does it happen when you do things in a particular order? I'm keen to figure out if I can replicate it.

Dmitri,

don't worry about the absence of the FS700. Just select 'Generic'. It makes no difference to how the calculations are made (the exception to that is if you choose an Arri camera - their approach to log involves a bit more calculation). What the camera options do is set up appropriate input gamma and gamut options, give you info about the native ISO and on the chart mark out the dynamic range of the camera and present exposure shift boxes which seem most appropriate for a particular camera's approach. Again, if you set ISO shift by stop (this is deliberately the only option given with the 'generic' camera it will make no difference to the results.

I'll look to add in the FS700 as an option.

Select 'S-Log' and 'S-Gamut' in LUTAnalyst as you mention. analyse as I mentioned in my previous post. Set 'Rec Gamma' to S-Log and 'Rec Gamut' to S-Gamut and the outputs to the LA options as I again mentioned. now change the stop shift as required. If you want to ensure that the LUT behaves exactly as your original, but with exposure shifts, make sure that the 'Input Range' and 'Output Range' in the box on the top right matches what you ended up with in LUTAnalyst on the bottom left. Away you go.

Sorry to be so long winded with these posts, but it is easier to do than to describe,

Ben
 
I can't seem to repeat that behaviour. I've just tried LUTCalc Testing under both Firefox and Chrome and settings saved fine. I also checked that I could generate a set of LUTs. I did however find a typo on a variable name which prevented them from being loaded back in fully. I've just corrected it and uploaded the fix so thanks for that at least! :-)
Oops, I meant the typo bug stopped settings getting reloaded properly, not LUT sets! Either way, it's fixed now,

Ben
 
Thanks again, Ben! Much appreciated...
I'm sure this is one of those things that are super confusing until you finally get your head around it and once you do, you can't understand how you could not get it earlier ;)

I'll give it a whirl and see what happens... thanks again!
 
Oops, I meant the typo bug stopped settings getting reloaded properly, not LUT sets! Either way, it's fixed now,

Ben

Hi Ben,
it seems Settings only work when you press them initially. If you press "Generate Set" before "Settings" you will get the "Generate Set" dialogue as well when pressing "Settings".
I'm using Chrome 53.0.2785.116 (64-bit) on OS X 10.10.5!

Hope you can replicate it ;)

BR
Michael
 
Hi Michael,

still can't get it to do that - I've tried repeatedly alternating Generate Set and Settings, doing runs of each, playing around with customisations then thumping the buttons on both Chrome and Firefox, OSX El Capitan.

I also can't think what might cause it in the code.

The only thing I can suggest is clearing your browser cache - I've made a number updates to 'Testing' over the last few days, some very small which I haven't explicitly mentioned, so maybe something is rubbing up against something else from different updates.

Very odd and frustrating that I can't repeat it. Anyone else seen this happen?

Ben
 
Hi Ben,
just tried it again on IE 11 on my Win7 machine at work, still the same thing. Also Chrome in Incognito Mode: Generate Set, Cancel, Settings => Generate Set dialogue.
Should I share that via Skype or record a screen capture?
BR
 
Hi Michael,

if you could do a screen capture to show it, that would be extremely helpful. I've tried out with various browsers on Mavericks and Windows 10 under Parallels on my MacBook and don't seem to have trouble saving individual LUTs, set of LUTs or settings. If I can see it, I should be able to fix it! ;-)

Thanks,

Ben
 
Hi Michael,

thanks for posting the screen capture. Really, really useful. Now I see it (and can repeat it), and why I hadn't before. Things get stuck if you click 'Generate Set' and then cancel it. If you click 'Go', everything is fine and the settings work as expected.

Now I know that it is just when you click 'Cancel' on 'Generate Set', I have a pretty good idea how to fix it. I'll get on it, but provided you give the 'Generate Set' a 'Go' ;-) you should be fine saving and loading your settings.

Thanks for that,

Ben
 
Hi Michael,

found the error - as I suspected it's just a typo on the 'Cancel' button for 'Generate Set'. Very silly, easy to fix (when I know what the problem is!) but will take a little while for an update to go through the App Store process (I'm in the middle of some other fairly substantial code which also needs checking!).

I've uploaded it to LUTCalc Testing,

Ben
 
Hi Ben,
I have just tried to test your Lut Cal and having problems with the web page. I can get all of the rest of the http://www.lutcalc.net webpages to load correctly but the run LutCalc page only shows everything grayed out so cannot enter data etc. I am using Windows 7 IE11 and java script is enabled. What am I doing wrong or is there some other settings I need to change to get your program to run on my PC. Perhaps some other members of the forum can also check if they can run it okay with IE11 browser.
Thanks Peter
 
Hi Peter,

sorry for the slow reply. I haven't been online much lately. I've just tried out the website using Microsoft Edge on Windows 10 and it doesn't seem to be finishing loading before having a wobbly. I think that we are seeing the same thing!

Annoyingly, the Microsoft Javascript console doesn't seem to be terribly helpful, and I know that it doesn't throw up issues under Chrome, Safari, Firefox or Opera under macOS or Windows, so it will no doubt take a fair bit of investigating (and almost certainly turn out to be some very small IE specific thing grinding it all to a halt :-) ).

Once Christmas is properly out of the way, I'll have a proper explore and sort this out.

I have just pretty much rewritten all the interpolation / extrapolation code for speed, accuracy, flexibility and maintainability so I am building towards an update. I'll work on IE/Edge before putting that out. I've also been having a play with Resolve and see that I need to add a 'Resolve 12' preset.

Merry Christmas and Happy New Year all,

Ben
 
Thanks Ben, I had asked some friends to check it out as well on their PCs with IE in case it was something to do with my internet connection security, but they found similar problems. I can always install Chrome or Firefox to get round the temporary problem.
Best wishes for 2017 and thanks for your work on LutCalc.
 
Hi Peter,

I've just uploaded an online update to LUTCalc Testing, with a fix for the Internet Explorer / Edge crashes.

IE / Edge were blocking some code from running in a particular way (inline web workers, if you're asking ;-) ) which all the other browsers seem to be OK with. I've added a test to see if inline is OK or just run conventionally if not, but for the time being to make it work I've had to delay startup by half a second on the splash screen. Let me know how it goes.

This update includes most of the stuff I have been working on for the full update: the Sony STD1-STD6 standard gammas, a 'Declip' button on the LUTAnalyst tool which attempts to extrapolate values in LUTs which have been clipped 0.0-1.0, a bugfix in the 'Gamut Limiter' tool which was blocking LUT generation and a complete rewrite of the 3D LUT interpolation / extrapolation code aimed at speed, clarity and maintainability.

Please do let me know how it goes. I'm looking to add the Odyssey and FS700 presets, then make sure nothing is obviously broken before releasing it properly. As 'complete rewrite' suggests, I'm taking particularly close looks at the interpolation / extrapolation code, as used by LUTAnalyst and the gamuts stored as LUTs (LC709A, LC709, V709 and Arri).

On a related note, if anyone has a camera with Cinegamma 3 and Cinegamma 4 and at least one log option (the FS700 perhaps) I'd be very grateful of a little help. If you can perform a full reset (this bit is important - any customisations need to be properly reset) then set the camera to display 'Test Saw' - this may require finding the maintenance menu.

Record brief clips with the gamma set to S-Log (1,2,3, one of whichever is available) and then Cinegamma 3 followed by Cinegamma 4. Get a set of log, Cinegamma 3 and Cinegamma 4 frames at 0db, 6db and 12db (also 18db if the Cinegammas still aren't clipping white). Finally please link me to the results. Single-frame tiffs generated in Resolve would be great and keep the size down, but you need to explicitly set 'clip range' to full to ensure that nothing gets lost.

From that I should be able to build pretty good representations of Cinegamma 3 and Cinegamma 4, which seem to be a bit mysterious at the moment!

Many thanks if anyone can help,

Ben
 
Hi Ben,

Many thanks for sorting the IE browser problem, it loads okay now. I am a new to generating my own Luts for use in editing my FS7 slog3 cine clips. I normally shoot at EI 800 so will do some experimenting with exposure compensated luts in my Edius and Resolve edit programs. Thanks again for your LUTCalc program and efforts, they are much appreciated. I will let you know how I get on. Happy New Year Peter
 
Hi Ben,

Just wanted to report that for some reason in Safari LutCalc does not generate LUT's correctly. Upon clicking on "Generate LUT" it goes to a page with a code (screenshot attached). When pressing the back button in the browser it goes back to the LutCalc but the calc is reset. I tried and it works properly in Chrome, it simply downloads the CUBE file.

Thanks,

Mat

generate lut code screen.jpg
safari version.jpg
 
Hi Mat,

Safari prevents Javascript from saving files as a security feature. It does let them open in a new tab. LUTCalc will first try to open a file save dialog. If a browser does not allow this, it will save the file to the browser's designated download folder (usually downloads) and failing that will fall back to opening the file in a new tab. What you have with Safari is the latter case.

If you save that code using Save As and make sure that 'page source' is selected and that you give it a filename ending in .cube, you will have your cube LUT.

Alternatively, I wrote the Mac OS app as a wrapper around the web app to avoid this issue with Safari. The Mac App takes over handling things like file saving and loading, so you can save to particular locations. Unfortunately, it has never been possible to directly save using the online version in Safari.

I've been doing a fair bit of work on LUTCalc lately, in particular completely rewriting the interpolation and extrapolation code for LUT-based colourspaces for speed, accuracy and maintainability. I've also been looking into the presets (in particular Resolve seems to handle automatic clip range setting a little differently since v12).

Hopefully I should be pretty close to uploading it soon as an update. Just trying to make sure I haven't broken anything important! ;-)

Ben
 
Ben , This is a far more basic question than all thes abstruse color space questions.
I just want to look at astill image in LutCalc as a preview and load a LUT I have already made. I thought I have did that in the past just by clicking in the LUT Title/ Filename box on the Right but maybe I imagined that as it doesn't give me the option to load a previous LUT .

Can I do it by using LUT Analyst and importing a LUT ?
 
Back
Top