@Videditor01

I don't think this is a recent change as I don't have new versions of either programs.

Will have await a reply from @johnbaker. He knows more about the workings than I do.

Ray.

@Videditor01

If you collect too many LUTS you spend more time looking through them than it would take to adjust manually and copy to the next video objects of your choice or save as another preset. I have yet to actually use a camera LUT. I have used some of the old film looks but not the LUTS so far.

I'm inclined to agree with you. I'm not overly concerned about using them I just wanted to experiment with the D-Log-M mode of the Pocket 3 and as I understand colour grading after using it is a requirement.

I suppose using pre-made presents (LUTs) would be a way to do this.

However, I'm more than happy to continue using the Pocket 3 auto mode if not. Just wanted that choice to see how their auto mode compares to a more tweaked set-up.

Thanks as always for your time and replies.

@Videditor01

Hi I think it is the msi_keyfile_ that is the problem. I removed mine from my version of the program and got this message.

Look familiar?

I do understand that it would be nice to see what the D-log-M can do but one LUT file is not really going to show you the entire range of what is possible shooting in 10 bit is capable of for a given scene or how best to use it.

It's very similar to shooting and processing raw files from a digital camera (DNG files in the case of the Osmo Pocket) where the contrast ratio and colour saturation can be set flatter so that the highlights and shadows can capture a wider amount of detail without over-saturating the brighter information but also capture the shadow areas better at the same time. Such an image file can look flat and lifeless. The contrast ratios and colour saturation needs to be tweaked until the detail is more visible. You can still do pretty much the same thing with a normal video file up to a point but it is more difficult and doesn't have the same amount of graduation detail.

That is VPX above when trying to make the band more visible. Note the additional tools and saving option.

The same can be done more limited with Movie Studio but the result can't be saved as a LUT file.

I don't have any 10 bit files I can use so the results you see above are from using normal 8bit video files.

It does seem odd that the ability to import 10 bit files can be now be done in Magix Movie Studios but the ability to import LUTS is still restricted, as is the ability save any when you create your own variation. The tools needed to create the alterations necessary are also somewhat more limited in Movie Studio compared to VPX as well.

That missing msi file also has a string of letters and numbers with it so may be keyed to my machine. I hope @johnebaker gets back to us to confirm or has a solution for you.

Ray.

@Videditor01

Hi.

It just got worse. I put the file back into the folder but I'm still getting the same message. I even copied the file I had used from VPX originally and replaced the MS one completely. Didn't work. Luckily the VPX one still does.

Will look into this further.

[Edit] Checked if the asi file had been altered. It hadn't. Now stumped. Must be something to do with that msi_keyfile_ . Maybe putting it on the desktop altered it in some way Have tried rebooting and restarting my system to no avail as well a replacing the folder with a copy from VPX. Not a big problem for me but if I can get it going again (or @johnebaker has a further suggestion) then maybe we can get yours to work.

Ray.

@Videditor01, @CubeAce

Hi

First my apologies for forgetting about creating the ias_keyfile when you manually create the LUT folders. I kept a master copy of my LUT presets folder from VPX and copied this to correct folder for MMS, fortunately you found the old solution.

. . . . shed some further light on the msi file and ias_keyfile . . . .

The msi file appears to not be necessary, it is created by the installer when the program (VPX) installer installs the LUTs, you will find many folders contain a key file.

The ias_keyfile is the one I had forgotten about and has the fileextension=cube and
include_subdirectories=true entries for the program to know what format should be used, there are 5 different LUT formats/file extensions, that I know of, and they are not x-compatible or not supported.

Additionally there are 2 types of LUT 1D and 3D.

A 1D LUT, can only adjust brightness, contrast and black/white levels, by taking the RGB colours and calculating the relative black/white levels of each pixel then remaps them to according to the LUTs parameters.

A 3D LUT can change the 3 colour (RGB) channels remapping all 3 colours independantly - it contains 3 mapping tables one for each colour channel.

. . . . It's frustrating they seem to have changed working features as the program has changed . . . .

True, however fortunately the folder locations/names do not change too often, upgrading automatically remaps/moves the appropriate content to the newer folders during the upgrade. We just have to go find them again 🙃

HTH

John EB

@johnebaker

Hi John.

Any idea why when I took out the ias_keyfile to see confirm that was the problem but subsequent replacement now gives me the same error as @Videditor01 ?

Does that also mean the Videditor01 cannot use LUT files in hos copy of MMS?

Ray.

@CubeAce

Hi Ray

. . . . Any idea why when I took out the ias_keyfile to see confirm that was the problem but subsequent replacement now gives me the same error as @Videditor01 ? . . . .

If you mean the ias_config.ini then it would - see the third paragraph in my post above yours.

I did test removing the _msi_keyfile_random characters, before posting and the LUTs worked fine after restarting MMS once the msi files were removed from both folders - they are put there by the installer.

John EB

@johnebaker

Hi John.

It seems an additional file went missing when I took the ias_keyfile out of the MEP folder.

I looked for the file mentioned in the warning pop-up.

And found it was missing in that location so I went to the VPX location for the same file and copied and pasted it into the MEP folder.

It is now back up and running.

So does that mean @Videditor01 will not be able to use LUTS? as he will not have these files and I'm not sure those files are not locked onto the PC's individual identity.

Ray.

Seems like an odd feature to omit from more recent versions.

I have an extremely old copy of this family of products "Movie Studio 13 Platinum". I wonder if that has the required files 🤔.

@Videditor01

Hi

. . . . Seems like an odd feature to omit from more recent versions. . . . .

Assuming you mean MMS not having LUTs, this is what differentiates the Prosumer products from the Professional product VPX.

. . . . "Movie Studio 13 Platinum". I wonder if that has the required files . . . .

IIRC this never had the Vegas LUT plugin feature, a third party plugin was available and worked with the program. again product differentiation with Vegas Pro.

Do note - Vegas plugins are not compatible with MMS 2024, however if you do find you have some .cube files for VMS 13 they should be usable in MMS 2024.

@CubeAce

Hi Ray

. . . . So does that mean @Videditor01 will not be able to use LUTS?  . . .

They are working, unless I missed something later on - see the comment here

John EB

@johnebaker

Hi John.

That folder is not working for @Videditor01 the folder shows but won't load LUTS as per the accompanying warning message. It needs the additional VPX file to work as I explained.

However my workaround above does work by importing additional files to the already existing Movie Looks folder.

Ray.

@CubeAce

I just did an experiment and loaded a camera LUT into the LUTEffect folder where it worked as that folder also uses CUBE files.

Folder is found in C: Users / Public / Public Documents / MAGIX / Common / Videocontent / (Your program version) VideoEffects / LUTPresets / LUTEffect.

Maybe not ideal but workable.

"By jove you've done it!"

That works well. Thank you very much CubeAce, your persistence paid off. Much appreciated!

I'm baffled as to why it works in one folder and not the other.

@CubeAce, @Videditor01

Hi Ray

I have eventually been able to reproduce that error message, MxVfxLUTCamera.vsx does not exist in MMS 2024 and appears to be not necessary.

The file MxVfxLUT_x64.dll, on removal triggers the error message regarding the above file, it is in the folder C:\Program Files\MAGIX\Movie Studio 2024 Platinum\ImageProcessingPlugins

I also made sure that MMS 2024 was not picking up the VPX files, and also checked a clean installation of MMS 2020 on a VM, the dll file is present there as well.

Your work around would have been my next test.

At least it is working now.

John