Suddenly Movie S is not decoding Lagarith or Huffy encoding correctly

Comments

clement5 wrote on 8/9/2022, 10:19 PM

Apparently, the problem is in the section of the MS code which decodes Lagarith. I deleted the Lagarith codec from my pc, but MS still could read the Lagarith files, but could not write them. They have their own embedded decoder which may also be used for Huffy decoding. Both of them have difficulties. As usual I have not heard back from Magix about the problem or its resolution.

I did a complete analysis of the various available exports for MS and found some inconsistencies. One of them would setup to export in PAL format even for a standard NTSC SD video. When NTSC is selected the interlacing defaults to bottom first, but NTSC uses top first. All of the export menus clear the 3D selection if an "Advanced" option is selected, except for the AVI menu. The AVI menu changes the aspect ratio and makes the frame rate of 23.976 to be 23.980 if a CODEC is selected. Putting the frame rate back to 23.976 doesn't work properly. The metadata for frame count is shortened and the duration is also wrong. The frame count is OK for a short clip, but for a 1h4 48min video the count is short by 26 compared to the actual number of frames. The count/duration is then 23.98. The 23.976 frame rate is encoded as 23976/1000 instead of the correct NTSC 24000/1001. However the default settings for AVI output are OK. When selecting an AVI CODEC the aspect ratio is set to the frame width/height which is not correct. The display aspect ratio is independent of the pixel aspect ratio for both PAL and NTSC SD videos. HD videos often have them both the same. MS notices that the reset frame rate does not match the movie rate and gives an error, but there is no way to set it back to the correct value.

I am really tired of having to find their errors and diagnosing them. I am switching to IYUV codec by converting the Lagarith files using VirtualDub. It seems to work OK, but the compression is not as good. I am also buying a bigger external drive so I have room to spare for my big projects!

BTW MS 2022 messes up the 3D display to passive monitors, and I have put in a complaint about that also. They are probably tired of my complaints. They messed it up once before with an update, and now they have done it again!

 

johnebaker wrote on 8/10/2022, 10:34 AM

@clement5

Hi

. . . . I deleted the Lagarith codec from my pc, but MS still could read the Lagarith files, but could not write them. They have their own embedded decoder which may also be used for Huffy decoding. . . .

I get this message when trying to load a Lagarith encoded video file: - same program and version as MMS, only has the old name.

I get the same message with Video Pro X14 which is the Magix pro video editing software.

Check the Lagarith X86 and x64 codec files and registry items have been uninstalled.

John EB

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

clement5 wrote on 8/10/2022, 8:11 PM

I located both of the Lagarith codec files and deleted them before this test and noted that I could not export in Lagarith. The name of the codec in the MS file info implied that it was decoding Huffy. So something was screwy?

AAProds wrote on 8/10/2022, 9:16 PM

@clement5

I deleted the Lagarith codec from my pc, but MS still could read the Lagarith files, but could not write them. They have their own embedded decoder

You're not uninstalling LAGS correctly. I have LAGS installed and MEP can read and export LAGS files. I then uninstalled it using Windows Control Panel > Programs and Features and then MEP/MS would not import a LAGS file: "cannot be read".

I reinstalled LAGS via the installer and then MEP would open a LAGS file.

Last changed by AAProds on 8/10/2022, 9:17 PM, changed a total of 1 times.

All my forum comments are based on or refer to my System 1.

My struggle is over! I built my (now) system 2 in 2011 when DV was king and MPEG 2 was just coming onto the scene and I needed a more powerful system to cope. Since then we've advanced to MP4 and to bigger and bigger resolutions. I was really suffering, not so much in editing (with proxies) but in encoding, which just took ages. A video, with Neat Video noise reduction applied, would encode at 12% of film speed. My new system 1 does the same job at 160% of film speed. Marvellous. I'm keeping my old system as a capture station for analogue video tapes and DV.

System 1

Windows 11 v23H2 severely modified by Openshell and ExplorerPatcher

Power supply: 850W Cooler Master (should have got modular)

CPU: Intel i7 13700K running at 3400mhz, cooled by a Kraken 2x140mm All In One liquid cooler.

RAM: 64gb (2x32gb sticks) G.Skill "Ripjaws" DDR4 3200Mhz

GPU 1: iGPU UHD 770

GPU 2: NVidia RTX 3060Ti Windforce 8gb

C drive: NVME 500gb

Bluray Burner: Pioneer BDR-212D

Various other SSD and HDDs.

Monitor: 27"/68cm Samsung, 2560 x 1440, 43 pixels/cm.

MEP 2021 version 20.0.1.80

Movie Studio 2025

Magix Video Easy version 7.0.1.145

System 2

(Still in use for TV and videotape capture)

Windows 10 v22H2

CPU: i5-750 at 2670mhz with 12gb RAM

Onboard IEEE1394 (Firewire) port

GPU: ATI Radeon HD 4770 (512mb) which is ignored by MEP

Hard drives: C Drive 256gb SSD, various other HDDs.

Monitor: Dell 22"/56cm, 1680x1050, 35 pixels/cm

MEP 2021 version 20.0.1.80

Movie Studio 2023 version 22.0.3.172

VPX 12