Hypergammas vs Slog2

Similar Questions

• SLog2 in low light conditions

  Hello, hoping for some advice please. What about the slog2 being wonderful shooting large latitudes in broad daylight and in situations where preserving highlights important - is fair to say then that slog2 so not ideal for low light dark environments?

  That is to say, if the ideal place for shades of skin and the gray card is at 30-33 with slog2, then in the dark light scenarios / low we lose many details in shadows etc that might otherwise be exposed to.

  We therefor more easy shooting with hyper gamma or curves standard to allocate more data to the shadow and thus pull complexion and gray at 40-50 IRE and keep sLog2 of shooting for higher latitude stuff? Or are there benefits for your stay on slog2 all the time if you're happy to be ranking images in any case post?

  I think I know the answer here, but I was hoping to get some thoughts to this certain f55/5 users that pass between the curves according to the scenarios.

  I do not have a raw box with my f55 kit, so I'm looking forward to stretch and control capabilities in camera and latitude, as much as I can.

  Thank you
  Tom

  Http://www.tomdavid.com.au

  What you're missing is that with the S - Log, and using the good LUT in post, these shadow detail who look as if they were in the mud in the eyepiece arose at appropriate levels. There are more bits (steps of BRIGHTNESS) in the shade to be "brought back to the top" in post.

  The only drawback is that it does not relieve a little noise. If you want to keep the same level of noise as a Hypergamma, just expose it to IE even as a Hypergamma (500, 600, etc.). You better stay right in S-Log2/SGamut and exposing more hot (that is to say 600ISO) and lose this stop on the high end.

  Mixing and matching SLog/Sgamut with hypergammas would be a nightmare for a colorist. They don't look not anywhere close to the same thing, and they do not meet the colors even. I didn't do it.

• The "LUT" F65 SLOG2 SGAMUT to REC709 to solve

  The attached LUT were made to create a solid starting point when you are working to solve with SLOG2/SGAMUT will REC709. It's not supposed to be a LUT perfect but a starting point very solid which has more then feel a mathmatically stéril conversaion.

  This LUT is designed with images of F65 but should work as well with the F55 in SLOG2/SGAMUT.

  ENTRY:
  The following 3DLUT expects a SLOG2 Full-Range, signal SGAMUT.

  If you work with a F65/F55 Raw material to solve 9, the Sony camera raw settings should be:
  Color space: SGamut
  Gamma: SLog2

  This can be set in the project settings so that each item will be imported in this way.

  If you work with SSTP footage shot Slog2/Sgamut video levels must be set to (0-1023) levels of data in the attributes of the clip Menu.

  Screenshots of these parameters are attached.

  OUTPUT:
  The 3DLUT outputs REC709 FULL RANGE for ranking monitor.

  If you use an external monitor, waiting for the (legal) levels of the video, make sure that the video output settings monitor are set to the levels of the video.
  When rendering the Quicktime/MXF files, please use 'Auto', which will scale the LUT output correctly in the file.

  Solve the LUT THAT is attached.

  

  

  you use a mac? If so make sure that the file is in/Library/Application Support / Blackmagic Design / DaVinci Resolve / LUT

  Mine then I have in a folder called "Sony" and maybe if you tried to do a 'open with' and always 'open with' and choose Davinci, it could help it zap by being used by Davinci not VLC...

• Basis of adjustment of modes / monitoring LUT with SLog2 - F55

  Hello

  IM writing a function and possibly using the F55. Anyone help me with the following queries?

  Is it possible to shoot 4K XAVC 4:2:2 in S-Log2 monitor but still with a LUT?

  Ive been just read the manual. It seems the State-

  p. 50

  You can monitor only to READ when your shooting mode = mode MOVIE EI in your basic setting

  p. 57

  and you can only shoot in S-Log2 when your shooting mode = mode custom in your basic setting

  Rob Wilton

  DoP, based in London

  When you see how this camera images to look good, don't you think its on-board too early. the Slog2 looks great. It's a very nice picture to research which can be cooked in and for the clients/Director to examine to yet while preserving the dynamic range

  one thing I can say from experience, RED and ALEXA had a lot more problems and deficiencies out of the box than the F55

  Finally LUTS will work for XAVC too, but it having so far works fine for RAW. XAVC kicks *.

• Slog2 logfile send

  Hello together,

  I am currently facing a bug, which can be found in the production, I wanted to add the ability to send the log file of the application for me. I did the following:

  Button {
              text: qsTr("Logfile an Entwickler senden")
              onClicked: {
                  console.log("logfilepath = " + _ApplicationUI.getLogfile());
                  emailInvocation.query.uri = "mailto:[email protected][email protected]&subject=ceAuToApp%20Logdatei&attachment=file:///" + _ApplicationUI.getLogfile();
                  emailInvocation.query.updateQuery();
              }
              horizontalAlignment: HorizontalAlignment.Center
          }
  
  Invocation {
              id: emailInvocation
              query.mimeType: "message/rfc822"
              query.invokeTargetId: "sys.pim.uib.email.hybridcomposer"
              query.invokeActionId: "bb.action.SENDEMAIL"
              onArmed: {
                  emailInvocation.trigger(emailInvocation.query.invokeActionId);
              }
          }
  

  The code for c ++ is the following:

  QString ApplicationUI::getLogfile()
  {
      QString filePath = QDir::current().absoluteFilePath("logs/");
      filePath.append("slog2.txt");
  
      FILE *file = fopen(filePath.toStdString().c_str(), "w");
      slog2_dump_logs_to_file(file,SLOG2_DUMP_LOGS_ALL);
      fclose(file);
      return filePath;
  }
  

  I get the error from the linker:

  qcc -Vgcc_ntox86 -c -Wc,-include -Wc,o-g/.obj/ceAuToApp -Wno-psabi -lang-c++ -fstack-protector -fstack-protector-all -g -Wno-psabi -Wall -W -D_REENTRANT -DQT_NO_IMPORT_QT47_QML -DQ_OS_BLACKBERRY -DQT_DECLARATIVE_DEBUG -DQT_DECLARATIVE_LIB -DQT_XML_LIB -DQT_CORE_LIB -DQT_SHARED -Id:/bbndk/target_10_2_0_1155/qnx6/usr/share/qt4/mkspecs/blackberry-x86-qcc -I../../ceAuToApp -Id:/bbndk/target_10_2_0_1155/qnx6/usr/include/qt4/QtCore -Id:/bbndk/target_10_2_0_1155/qnx6/usr/include/qt4/QtXml -Id:/bbndk/target_10_2_0_1155/qnx6/usr/include/qt4/QtDeclarative -Id:/bbndk/target_10_2_0_1155/qnx6/usr/include/qt4 -ID:/bbndk/target_10_2_0_1155/qnx6/usr/include/qt4/QtSql -Io-g/.moc -Id:/bbndk/target_10_2_0_1155/qnx6/usr/include -Id:/bbndk/target_10_2_0_1155/qnx6/usr/include/freetype2 -I. -o o-g/.obj/moc_qtsoap.o o-g/.moc/moc_qtsoap.cpp
  qcc -Vgcc_ntox86 -c -Wc,-include -Wc,o-g/.obj/ceAuToApp -Wno-psabi -lang-c++ -fstack-protector -fstack-protector-all -g -Wno-psabi -Wall -W -D_REENTRANT -DQT_NO_IMPORT_QT47_QML -DQ_OS_BLACKBERRY -DQT_DECLARATIVE_DEBUG -DQT_DECLARATIVE_LIB -DQT_XML_LIB -DQT_CORE_LIB -DQT_SHARED -Id:/bbndk/target_10_2_0_1155/qnx6/usr/share/qt4/mkspecs/blackberry-x86-qcc -I../../ceAuToApp -Id:/bbndk/target_10_2_0_1155/qnx6/usr/include/qt4/QtCore -Id:/bbndk/target_10_2_0_1155/qnx6/usr/include/qt4/QtXml -Id:/bbndk/target_10_2_0_1155/qnx6/usr/include/qt4/QtDeclarative -Id:/bbndk/target_10_2_0_1155/qnx6/usr/include/qt4 -ID:/bbndk/target_10_2_0_1155/qnx6/usr/include/qt4/QtSql -Io-g/.moc -Id:/bbndk/target_10_2_0_1155/qnx6/usr/include -Id:/bbndk/target_10_2_0_1155/qnx6/usr/include/freetype2 -I. -o o-g/.obj/moc_AppSettings.o o-g/.moc/moc_AppSettings.cpp
  qcc -Vgcc_ntox86 -lang-c++ -Wl,-rpath-link,D:/bbndk/target_10_2_0_1155/qnx6/x86/lib -Wl,-rpath-link,D:/bbndk/target_10_2_0_1155/qnx6/x86/usr/lib -Wl,-rpath-link,D:/bbndk/target_10_2_0_1155/qnx6/x86/usr/lib/qt4/lib -o o-g/ceAuToApp o-g/.obj/applicationui.o o-g/.obj/Address.o o-g/.obj/Execution.o o-g/.obj/Order.o o-g/.obj/VehicleItem.o o-g/.obj/OrderManager.o o-g/.obj/qtsoap.o o-g/.obj/main.o o-g/.obj/AppSettings.o o-g/.obj/moc_applicationui.o o-g/.obj/moc_Address.o o-g/.obj/moc_Execution.o o-g/.obj/moc_Order.o o-g/.obj/moc_VehicleItem.o o-g/.obj/moc_OrderManager.o o-g/.obj/moc_qtsoap.o o-g/.obj/moc_AppSettings.o    -LD:/bbndk/target_10_2_0_1155/qnx6/x86/lib -LD:/bbndk/target_10_2_0_1155/qnx6/x86/usr/lib -LD:/bbndk/target_10_2_0_1155/qnx6/x86/usr/lib/qt4/lib -LD:/bbndk/target_10_2_0_1155/qnx6//usr/lib/qt4/lib -lbbdata -lbbsystem -lbbcascades -lQtDeclarative -lQtScript -lQtSvg -lQtSql -lsqlite3 -lz -lQtXmlPatterns -lQtGui -lQtNetwork -lsocket -lQtXml -lQtCore -lm -lbps
  D:\bbndk\host_10_2_0_15\win32\x86\usr\bin\ntox86-ld: o-g/.obj/applicationui.o: undefined reference to symbol 'slog2_dump_logs_to_file'
  D:\bbndk\host_10_2_0_15\win32\x86\usr\bin\ntox86-ld: note: 'slog2_dump_logs_to_file' is defined in DSO D:/bbndk/target_10_2_0_1155/qnx6/x86/lib/libslog2.so.1 so try adding it to the linker command line
  D:/bbndk/target_10_2_0_1155/qnx6/x86/lib/libslog2.so.1: could not read symbols: Invalid operation
  cc: D:/bbndk/host_10_2_0_15/win32/x86/usr/bin/ntox86-ld caught signal 1
  make[2]: *** [o-g/ceAuToApp] Error 1
  make[2]: Leaving directory `D:/MomenticsWorkspaces/ceAuTo/src/ceAuToApp/x86'
  make[1]: *** [debug] Error 2
  make[1]: Leaving directory `D:/MomenticsWorkspaces/ceAuTo/src/ceAuToApp/x86'
  make: *** [Simulator-Debug] Error 2
  

  What Miss me? Thanks for your help .

  Well, I already had the more things myself, but now I am facing a strange problem:

  void ApplicationUI::sendLogfile()
  {
      InvokeRequest request;
      request.setAction("bb.action.COMPOSE");
      request.setMimeType("message/rfc822");
      QVariantMap data;
      data["to"] = (QVariantList() << "[email protected]" << "[email protected]");
      data["subject"] = "ceAuToApp Logdatei";
      QString fileName = QString("log.txt.%1").arg(QDate::currentDate().toString("yyyy-MM-dd"));
      QString filePath = QString("logs/%1").arg(fileName);
      //QString logpath = "/accounts/1000/shared/downloads/listen.pls";
      QString logpath = "logs/log.txt";
      QFile::copy(logpath,"tmp/log.txt");
      QString logpathEncoded = QString(QUrl("/accounts/1000/appdata/de.carexpert.ceAuToApp.testDev_t_ceAuToApp72c58f33/tmp/log.txt").toEncoded());
      data["attachment"] = (QVariantList() << logpathEncoded);
      QVariantMap moreData;
      moreData["data"] = data;
      bool ok;
      request.setData(bb::PpsObject::encode(moreData, &ok));
      InvokeManager manager(this);
      manager.invoke(request);
  }
  

  The above method works using a path like "/ accounts/1000/shared/downloads/listen.pls" (the file exists, I downloaded it myself), but refuses to join the file when I use the path "/ log/log.txt". Any ideas, why does not work? I also tried the full path, copied what he tmp, this also does not work. I'm really confused. Thanks for your help .

• Sony A7Rii RAW Slog2 files really dark

  No matter if I use LightRoom, Capture1, DxO, Photoshop or bridge all interpret the really dark ARW files.

  My current project had me shooting video and photos at the same time. I used the Slog2 profile since it is incredible for video work, but I find that my photos are too saturated and really dark.

  However, behind closed doors, they were beautiful. Located on the exhibition was, good-looking ISO, white balance was nice.

  I import them, and they are so dark and more saturated. Even right after I import them they look up to the bridge or LightRoom or PS adds that some sort of adjustment for them which, as I said, makes really dark and more saturated.

  Help, please! What I'm missing here?

  Adam

  Slog is for video.  Raw pixel data in still images shot during the slog movie mode use * is * really dark and the camera makes image manipulation to produce the JPG even as it does for video, you're shooting mode slog.

• Slog2, 3 Luts, more missing trees 10.3 lut

  Is where all read to the 10.3 for Lumetri color trees?

  FAQ: How can I reinstall the first Pro CC 2015.2 (9.2)?

  Or place this technical file https://db.tt/DWTgZYJf in folder of the LUT root first (program flles/adobe/.../LUTs

  [post edited, now contains the correct download link]

• Out of the appearance of the box

  Recent articles of Alister and Cameramanben on the settings of the camera, the workflow and use LUT were extremely helpful. Thus, the shooting mode Sgamut feels like a much more affordable option for me. I had usually been taken slog2 space color in custom shooting mode, because I could actually it grade. While I had an impossible image desaturated of Sgamut, ranking, because I wasn't not utlizing read in the viewfinder of the time or by mail (as I should be).

  So all the foregoing is more and more clear to me and is feasible when I'm ranking/edit images. But what happens if I'm over images out to a publisher who didn't experience snorkeling or adjustment of colors? What is the best approach to get an excellent picture 'out of the box "? For example, it would be better to stay in Sgamut and cook in the oven in the LUT to the record? Or would it be better to choose "custom" mode and choose one of the standard or the HyperGamma Gamma options? I leave the principle of cooking in the LUT in Sgamut would be the way to go, and if so, what is a LUT which will do a good job maximizing dynamic range and prevent it to look too "video".

  Thanks in advance to the members of this forum who help me learn so much every day!

  
  

• Export to the same registered quality

  Hello

  IM recording in XAVCs (which is displayed as when downloaded MP4) with Slog2. What I hope to do is cut this sequence in clips can be used in a project in FCPX and then export and give it to someone who is hoping to use images from a video. What setting should I use when exporting to keep the quality high enough so they can use it and it rank as if it was raw footage - im just trying to save the hassle of having to go through all of the original sequences themselves?

  Thanks in advance,

  Chris.

  If you export the default ProRes 422 should not be a visible loss of quality.

  However the file size will be much larger.

  Also, this is assuming that the intended editor can use Pro Res, that depends on what software will be used. This is not a problem if it also uses FCP X (or 7, by the way).

• F55 artifacts of grid for the sensor

  So I shot some footage today, with flares, light heavy, and I had this strange artifacts. Looks like the table of color filter. You can see on the blooming rose. It appears in the content browser and FCPX.

  Anyone else able to reproduce this in their camera? Or is it just me?

  4 k XAVC SLOG2.

  

  
  

• Wide dynamic range equivalent Canon?

  All, morning

  I've got a shoot tomorrow and images is going to be edited, I know the guy do a very quick turn around time and also doent have LUT packages to use. I also know he usually pulls and like dynamic range color profile (clogged not) on the C100, as it seems ok on the camera, but also gives you plenty of room to play with him at the post. What would you say was the most simular color adjustment on the FS7, I tried loads but all seem to be really flat (as slog 3) or with a little look very burned in them as rec 709 standard.

  I know, it should have read so we could create the exact appearance etc., but it does not so is not an option.

  Thanks in advance!

  Greg.

  By saying this, 8 Hypergamma is much like the WDR

• F5/F55 SDI

  I have not seen information on the HD - SDI output on both devices.

  The only thing published so far is that only F55 will output 4-Channel HD to 4 k.

  I hope that both cameras will show 4:4:4 Slog2 through the SDI, recorders so 3rd party can be used

  Idid'nt he saw there. I'll watch again and come back with even more questions, because I've already ordered F55

• MLUT question

  Another question nwebie...

  During the filming for television, regardless of the camera gamma curve control... (except for STD5 709...) You can set the MLUT... for the VF and monitor for Rec 709... as that's what he'll be back to finish by... That's all the interest of the MLUT is not...

  Assuming that it's just... When and why would the other MLUTS... hypergamma, s... S journal etc. be useful...? Get the feeling Im missing something here...

  Thank you

  
  

• Deliver the feature READ us hurt F55

  All,

  Courtesy of Sony Pictures Colorworks team we are providing to the LUT F55 used on us free from Evil feature.

  It is a combination of a look of derivation of bleach with the ACES RRT v0.1.1.

  Entry: SLog2-SGamut

  This could be:

  -tap of SDI camera with NO scaling the signal full-range

  -RAW processed at S-Log2-SGamut

  Output: Rec709 / BT.1886 signal

  -Calibration for 100 nits, gamma 2.4, dim surround

  -Outputs full / extent of range, 0-1023

  This is designed specifically for this configuration by using S-Log2-SGamut. The camera does not support SLog3 at the time so if used with the new SLog3 with newer SGamut could produce unwanted results.

  Concerning

  Peter

  Peter is very exciting. Thank you!

  can't wait to try it.

• Viewfinder LUT vs exposure tools (Zebra / waveform)

  Hi guys,.

  Discussions on our new found access to MLUTs and the AE CINE was great, thanks for all the info fascinating so far. So forgive me if this has already been covered, but I have two questions:

  (A).. .for MLUTs in the viewfinder to be of any practical, why use the waveform monitor and the Zebra reacts to the MLUT when applied, as opposed to the same as if the MLUT has not been applied to all? IE - as an image in the viewfinder as slog2 sgamut my Zebra / wave give me information of the exhibition which is very useful (next to my light meter) but when I apply, say, the REC709 MLUT of the VF, news of Zebra and waveform to adapt to the new image - so REC 709 points out, blow and my zebras tell me now that the parts of the image is blown... But I'm still recording to SxS cards like sLog2 sLog2 - so, in reality, this info is not get blown at all.

  So what I mean: the REC709 MLUT is ideal to boost the brightness etc. in the viewfinder and makes the image easier on the eye than the image dark sLog2, but I always feel like my tools of exposure to expose properly for the image being recorded to the card (in this case sLog2). I hope that all makes sense... Accept others, or am I missing something here?

  and the second point is:

  (B).. .throughout all the upgrades for the camera by setting the number 2 zebras at 109% don't turn on for me in the VF, despite an image being obviously blown. No more than 108%, or 107%. However the zebras behave corectly to 106% and will show the 'Zebra lines' when the image is burned.

  Is there a reason why 109% zebras does not illuminate, or am I missing something here too?

  Thanks for all your comments guys - happy shooting.

  Tom

  www.tomdavid.com.au