![]() ![]() ![]() When the setup program is complete, go into Windows, run the Windows setup program by double-clicking its icon in the Program Manager group called MAIN.Exit Windows, and run the setup program from this disk to install the video drivers.Use Master Disk Creator to make the install disk for the Toshiba Win 3.X Video drivers.The default driver is set to 65550 800圆00x256 on a 500CDT computer. Apologies to harp on about this but it's becoming more and more critical to my work to get this right.MPLAYER causes a general protection fault when you launch Windows 3.1x Media Player after you complete the installation of the software drivers that ship with the Noteworthy NWZVMPEG1 card. exr file in case anyone can take a look at it and please tell me if there's something I'm doing obviously wrong on my end. ![]() ![]() In that config file, the scene_linear role is set to: ACES - ACEScg My system $OCIO environment variable is set correctly to point to the config file, and Houdini and Nuke are picking that config file up and are configured correctly as far as I can tell. I'm using the Aces 1.1 default OCIO config file. exr being displayed in Mplay with the Rec 709 display transform: See how all the detail in the shadow area beneath the car and also along the wall of the tyre are being almost completely crushed to black in the Mplay viewer, which displays the same in the Renderview inside Houdini. exr being displayed in Nuke with the (Aces 1.1) Rec 709 display transform, right next to the same. Here's a screenshot of a cropped render linear. Octane-mplayIPR-ACES.jpg (396.4 KB) octane-mplayIPR-affinity-ACES.jpg (415.8 KB)īumping this thread again. I realize that all the DCC and rendering apps are still working on proper ACES implementation, however given that everything is partially implemented at the moment it's difficult to tell which one is right when they all differ! Attached are two images, the blueish one is a screen shot from MPlay displaying the render through ACES 1.2 OCIO, the reddish version is the same image rendered out from Houdini with Octane as Multilayer EXR ACES and transformed in Affinity Photo. Unfortunately there is no view transform in the Octane IPR at the moment so I can not truly determine the accuracy of MPlay, fortunately I am able to get some sense of how the final render will look in ACES with MPlay, however when I open the ACES renders into Affinity Photo (and or Photoshop) and apply an OCIO transform the images show a significant red cast and the blacks are less crushed than are displayed in MPlay. I'm also curious about this though I'm using Octane. exr differently with the same view transform applied? I really love using Mplay to preview renders but I have to be able to trust that what I'm looking at exactly matches what I will see in Nuke and other software using OCIO and ACES. Is there any obvious reason why Mplay would display the linear. I am using Arch Linux with the OCIO and OCIO_ACTIVE_VIEWS env variables set. exr file (rendered by Redshift) in Mplay with the ACES Rec 709 view transform it looks different, especially in the darks a lot of the detail is being lost in the blacks and shadow areas to the point where I can't use it for colour critical work. For example I am rendering a frame in Redshift and viewing it with the Rec 709 ACES display transform and in Nuke and Redshift Renderview the images look identical, and there is lots of detail especially in the shadowed areas, however when I display the exact same. exr files with the OCIO ACES Rec 709 view transform differently than Nuke and the Redshift Renderview display them. Hey there, Mplay and Renderview in Houdini are displaying linear. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |