Lagarith Lossless Codec

jak.willis wrote on 10/2/2021, 5:42 AM

Hello,

I decided to do some experimenting with the Lagarith lossless codec. In MEP, I used an MPEG-2 720x576 video, and exported to AVI using the Lagarith codec. The resulting file plays fine in Windows Media Player, but, for some reason, when I put the file on a USB stick and attempt to play it on my TV/Blu-ray Player, it comes up with “Video resolution not supported”. It plays the audio but not video. Does anyone know what the issue could be here?

Comments

CubeAce wrote on 10/2/2021, 7:37 AM

@jak.willis

Hi Jak.

Well 720x576 video has a 4:3 screen ratio whereas HD DVD has a screen ratio of 16:9.

Then you are trying to spread 720 x 576 pixels across 1920 x 1080 pixels.

I'm sure Al (AAprods) may have a solution for you. @AAProds

Ray.

 

Windows 10 Enterprise. Version 22H2 OS build 19045.5737

Direct X 12.1 latest hardware updates for Western Digital hard drives.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1 Bios version 1401

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version Graphics Driver 31.0.101.2135 for 7th-10th Gen Intel® with 64GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB Evo 970 NVMe: drive for C: drive backup 1 x 1TB Sabrent NVMe drive for Operating System / Programs only. 1X WD BLACK 1TB internal SATA 7,200rpm hard drives.1 for internal projects, 1 for Library clips/sounds/music/stills./backup of working projects. 1x500GB SSD current project only drive, 2x WD RED 2TB drives for latest footage storage. Total 31TB of 10 external WD drives for backup.

ASUS NVIDIA GeForce RTX 3060 12GB. nVidia Studio driver version 572.60 - 3584xCUDA cores Direct X 12.1. Memory interface 192bit Memory bandwidth 360.05GB/s 12GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x8 Gen3. Two Samsung 27" LED SA350 monitors with 5000000:1 contrast ratios at 60Hz.

Running MMS 2024 Suite v 23.0.1.182 (UDP3) and VPX 14 - v20.0.3.180 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

VXP 14, MMS 2024 Suite, Vegas Studio 16, Vegas Pro 18, Vegas Pro 21,Cubase 4. CS6, NX Studio, Mixcraft 9 Recording Studio. Mixcraft Pro 10 Studio. CS6 and DXO Photolab 8, OBS Studio.

Audio System 5 x matched bi-wired 150 watt Tannoy Reveal speakers plus one Tannoy 15" 250 watt sub with 5.1 class A amplifier. Tuned to room with Tannoy audio application.

Ram Acoustic Studio speakers amplified by NAD amplifier.

Rogers LS7 speakers run from Cambridge Audio P50 amplifier

Schrodinger's Backup. "The condition of any backup is unknown until a restore is attempted."

me_again wrote on 10/2/2021, 9:12 AM

@jak.willis

Ray is correct, Al @AAProds may have a solution for you, he does know everything there is to know about the Lagarith codec - it was he that put me onto it. This is what I think I know about the codec and I stand to be corrected by Al.

The Lagarith encoded AVI will play in Windows Media Player on your system because the Lagarith codec is installed on your system.

The Lagarith encoded AVI will not play properly through your TV/Blu-ray Player because the Lagarith codec is not installed on your TV/Blu-ray Player. The audio plays because you've probably used MP3 for the audio which your TV/Blu-ray Player will have installed.

The Lagarith codec is excellant for use on a computer for the reasons Al has extolled in several posts but, as far as I know (and indeed found out when I first started using it), it is useless for a file to be played on a TV.

The Intel AVI codec works on my TV.

If you're using 720x576 for your AVI why not encode to DV-AVI, it's slow but not as painfully slow as with the Intel codec..It works on my TV. Just don't use DV-AVI for any files you want to edit, only use it for a finished video.

@CubeAce

Ray, 720x576 encodes very nicely to 16:9. I use it a lot when editing VHS stuff and I find it surprising how good the picture can be on a modern TV.

The files look soft and indeed sometime blurry when plaued on my computer monitor but the TV obviously upscales much better than my monitor because 720x576 videos look OK on the TV - not 4k quality but definately watchable.

AndyW

Last changed by me_again on 10/2/2021, 9:28 AM, changed a total of 2 times.

"Just when I think I've learned the workrounds of MEP/MS the bounders go and update it"

Aorus Z690 Elite DDR4 Motherboard

12th Gen Intel(R) Core(TM) i7-12700K, 3600 Mhz, 12 Core(s) 20 Logical Processor(s)

64gb (4x16gb sticks) DDR4 3200Mhz

Intel(R) UHD Graphics 770

Gigabyte GeForce RTX 4060 Eagle OC 8Gb DDR6 DLSS3 Windforce

Corsair RM750 PSU, be quiet! Pure Rock 2 cooling

System drive 500Gb 4.0NVMe M,2 SSD, dedicated video/audio drive 2Tb Gen 4 NVMe SSD, 2x 500Gb Local Fixed Disks (Music etc), USB3 expansion drive 5Tb and 2Tb

Audio Onboard ALC1220 Amp-Up, Windows 11 Home updated as and when

Movie Studio 2025 Suite, Photo Manager Deluxe 13

Norton 360

All Drivers updated as they become available.

AAProds wrote on 10/2/2021, 9:26 AM

@jak.willis @CubeAce @me_again

It will be because the TV and Bluray can't decode the LAGS codec. I haven't been able to play any type of AVIs on my LG Smart TV or WDTV media player, but there could be a media player out there that does.

Windows programs will play LAGS files because the codec is installed on your system, and VLC Player has it's own codec library.

An option which I didn't know (but do now!, found after some sleuthing): if you have a Chromecast, you can play the AVI on your 'puter and cast it to your TV.

Play the file, go to Playback>Renderer, and choose the Chromecast.

If install Splashtop you can remote-control your computer from your phone!

Just saw Andy's post; my TV won't play DV-AVIs (USB or network) but my Apple TV will, via the network. I haven't tried via USB. but I assume it will.

I concur with Andy's comment about 720x576 on big TVs; they play correctly (unless deliberately stretched in the TV settings) and the upscaling is great. I tend to think 1440x1080 looks a tiny bit better but there's not a lot in it.

Last changed by AAProds on 10/2/2021, 9:36 AM, changed a total of 3 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

jak.willis wrote on 10/2/2021, 10:14 AM

@jak.willis @CubeAce @me_again

It will be because the TV and Bluray can't decode the LAGS codec. I haven't been able to play any type of AVIs on my LG Smart TV or WDTV media player, but there could be a media player out there that does.

Windows programs will play LAGS files because the codec is installed on your system, and VLC Player has it's own codec library.

An option which I didn't know (but do now!, found after some sleuthing): if you have a Chromecast, you can play the AVI on your 'puter and cast it to your TV.

Play the file, go to Playback>Renderer, and choose the Chromecast.

If install Splashtop you can remote-control your computer from your phone!

Just saw Andy's post; my TV won't play DV-AVIs (USB or network) but my Apple TV will, via the network. I haven't tried via USB. but I assume it will.

I concur with Andy's comment about 720x576 on big TVs; they play correctly (unless deliberately stretched in the TV settings) and the upscaling is great. I tend to think 1440x1080 looks a tiny bit better but there's not a lot in it.

Thanks for clearing that up for me, that does make some sense now. Although, if it’s unable to play the video because of the codec, then why doesn’t the player just say “codec not supported” instead of “video resolution not supported”? Seems a bit strange.

As you are the expert here on Lagarith, the other thing I’m confused about is why it produces files with a much larger file size and bitrate than the original source files. If you export as AVI uncompressed then obviously the file size & bitrate is much larger, but if Lagarith is lossless, then how come it ends up producing files with a size & bitrate that almost mimics a fully uncompressed file?

johnebaker wrote on 10/2/2021, 1:45 PM

@jak.willis

Hi

The most universal formats for Smart TV and player support are MP4 (.mp4), or AVCHD (.m2ts) container files with, h.264/AVC encoded video and AAC (AC3?) audio.

. . . .  if Lagarith is lossless, then how come it ends up producing files with a size & bitrate that almost mimics a fully uncompressed file . . .

 The same applies to Lagarith as for the uncompressed AVI in your previous topic.

The only difference is that once the frames have been created with no loss, they are then compressed, using a similar technique of compression for Zip files, to reduce the file size slightly.

John EB

Last changed by johnebaker on 10/2/2021, 1:50 PM, changed a total of 1 times.

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 24H2 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.

jak.willis wrote on 10/2/2021, 2:23 PM

@jak.willis

Hi

The most universal formats for Smart TV and player support are MP4 (.mp4), or AVCHD (.m2ts) container files with, h.264/AVC encoded video and AAC (AC3?) audio.

. . . .  if Lagarith is lossless, then how come it ends up producing files with a size & bitrate that almost mimics a fully uncompressed file . . .

 The same applies to Lagarith as for the uncompressed AVI in your previous topic.

The only difference is that once the frames have been created with no loss, they are then compressed, using a similar technique of compression for Zip files, to reduce the file size slightly.

John EB

Hi, so Lagarith is more or less the same as uncompressed then?

CubeAce wrote on 10/2/2021, 4:36 PM

@jak.willis

My guess would be, and it is a guess, that Lagarith is still recording each pixel separately but how the pixel data is represented may be written differently using slightly less code. It is a 'lossless' codec. There is at present no way around that.

Lossless formats are not always a good thing. For instance, in a video camera you would set your sharpness and colour balance or allow the automatics to do it for you. In a stills camera that would normally be recorded in with the pixel information and be applied when viewed in an editor. A true lossless image such as Tiff for stills does not record that information. That means the resulting image looks softer, the image can suffer colour noise even at low ISO settings and everything has to be done from scratch. Any advantage gained from taking decisions when the image is recorded is lost.

I have stills cameras that shoot in Tiff 14 bit RAW and jpeg, and although I prefer the colour that Tiff gives, getting the final image to look correct is much more difficult and hard work and the file size is three times larger than the 14 bit RAW file and generally still has to be exported as a jpeg for general use.

I can see the usefulness that AAprods and others find for it when transferring older analog video or film footage to be digitized ready for further editing, but for use as a general playback medium, no.

Ray.

Last changed by CubeAce on 10/2/2021, 4:37 PM, changed a total of 1 times.

 

Windows 10 Enterprise. Version 22H2 OS build 19045.5737

Direct X 12.1 latest hardware updates for Western Digital hard drives.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1 Bios version 1401

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version Graphics Driver 31.0.101.2135 for 7th-10th Gen Intel® with 64GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB Evo 970 NVMe: drive for C: drive backup 1 x 1TB Sabrent NVMe drive for Operating System / Programs only. 1X WD BLACK 1TB internal SATA 7,200rpm hard drives.1 for internal projects, 1 for Library clips/sounds/music/stills./backup of working projects. 1x500GB SSD current project only drive, 2x WD RED 2TB drives for latest footage storage. Total 31TB of 10 external WD drives for backup.

ASUS NVIDIA GeForce RTX 3060 12GB. nVidia Studio driver version 572.60 - 3584xCUDA cores Direct X 12.1. Memory interface 192bit Memory bandwidth 360.05GB/s 12GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x8 Gen3. Two Samsung 27" LED SA350 monitors with 5000000:1 contrast ratios at 60Hz.

Running MMS 2024 Suite v 23.0.1.182 (UDP3) and VPX 14 - v20.0.3.180 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

VXP 14, MMS 2024 Suite, Vegas Studio 16, Vegas Pro 18, Vegas Pro 21,Cubase 4. CS6, NX Studio, Mixcraft 9 Recording Studio. Mixcraft Pro 10 Studio. CS6 and DXO Photolab 8, OBS Studio.

Audio System 5 x matched bi-wired 150 watt Tannoy Reveal speakers plus one Tannoy 15" 250 watt sub with 5.1 class A amplifier. Tuned to room with Tannoy audio application.

Ram Acoustic Studio speakers amplified by NAD amplifier.

Rogers LS7 speakers run from Cambridge Audio P50 amplifier

Schrodinger's Backup. "The condition of any backup is unknown until a restore is attempted."

AAProds wrote on 10/2/2021, 10:36 PM

@jak.willis

Video compression is a compromise with size. The more compressed a video is, the more data has been "thrown away" as well as more complex encoding with various types of frames, as Cubeace has described).

LAGS is one of the so-called "lossless" codecs that, while compressed, retains all the video data. An "uncompressed" video has the same data but with no compression. A "lossy" codec such as MPEG 4 is great for smaller file sizes but compromises by reduced quality. That reduction is not a lot, as long as you keep the bitrate up.

So, what to use? It depends on the source. If you are capturing analogue video (eg VHS), capture in a lossless codec such as LAGS; the file sizes are pretty big, but you get a lossless copy of the tape which you can then edit and re-encode into MP4 for playing on your various devices, or MPEG for a DVD.

If you already have an MP4 or an MPEG 2 file, after there would be much point in encoding it to LAGS just to view. Just export to MP4 again or MPEG 2, keeping the bitrate up.

There is case for exporting into lAGS: if you wanted to re-edit the edit. I think i mentioned in the other topic that I had a piece of problem video that I re-encoded multiple times. I stayed in LAGS the whole time to minimise quality loss, then at the end, brought that back into MEP for the final export to MP4.

As it turns out, it appears none of the MEP AVI export options are not truly "uncompressed". I had to use Virtual Dub to get a true uncompressed file. The AVIs (and the MXV at 100% quality) are allegedly "lossless", although the Microsoft Video 1 is so much smaller that it may be a bit "lossy".

I would surmise that the lower the file size, the higher the compression, but that the quality of that MP4 is pretty close to all the the others at a fraction of the size (you would not want to re-edit that MP4 though). These are 720x576 files.

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

AAProds wrote on 10/3/2021, 5:17 AM

Found this on Wiki re that Microsoft Video 1. As I alluded to, it seems to be an old lossy codec:

https://en.wikipedia.org/wiki/Microsoft_Video_1

Last changed by AAProds on 10/3/2021, 5:20 AM, 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

johnebaker wrote on 10/3/2021, 6:55 AM

@AAProds, @jak.willis, @CubeAce, @me_again

Hi all

. . . . LAGS is one of the so-called "lossless" codecs that, while compressed, retains all the video data. An "uncompressed" video has the same data but with no compression. . . . .

The use of the word 'compression' is somewhat ambiguous - using a couple of examples already mentioned:

h.264/h.265* involve video compression, as Al has said throwing away some data, this is done before the encoded video is put into the container file. Whether file compression occurs I can find no reference to this - if it is applied as well then the video audio data is compressed further, think of Zip files and how they are compressed, without throwing anything away.

Lagarath, on the other hand, has the option to not compress the video, however the resulting video audio data can be compressed to make the file size smaller with no loss.

* This involve some complex maths calculations, the algorithm for h.265 is more complex than h.264 and can throw away more video data while maintaining the same perceived quality as h.264 for a significantly smaller file sizes, however you need more CPU/GPU power to decode them.

. . . . Microsoft Video 1 . . . .

Definitely not recommended for high quality video, the colour space appears to be restricted at 15 bit - 5 bits/colour - 32,768 colours.

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 24H2 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.

jak.willis wrote on 10/3/2021, 8:59 AM

@AAProds, @jak.willis, @CubeAce, @me_again

Hi all

. . . . LAGS is one of the so-called "lossless" codecs that, while compressed, retains all the video data. An "uncompressed" video has the same data but with no compression. . . . .

The use of the word 'compression' is somewhat ambiguous - using a couple of examples already mentioned:

h.264/h.265* involve video compression, as Al has said throwing away some data, this is done before the encoded video is put into the container file. Whether file compression occurs I can find no reference to this - if it is applied as well then the video audio data is compressed further, think of Zip files and how they are compressed, without throwing anything away.

Lagarath, on the other hand, has the option to not compress the video, however the resulting video audio data can be compressed to make the file size smaller with no loss.

* This involve some complex maths calculations, the algorithm for h.265 is more complex than h.264 and can throw away more video data while maintaining the same perceived quality as h.264 for a significantly smaller file sizes, however you need more CPU/GPU power to decode them.

. . . . Microsoft Video 1 . . . .

Definitely not recommended for high quality video, the colour space appears to be restricted at 15 bit - 5 bits/colour - 32,768 colours.

John EB

I see. So, in Lagarith, what do you need to do to ensure it does compress? And, the other weird thing I’ve noticed is that whenever I export a 4:3 video using Lagarith, the output file ends up as 5:4. Is there any particular reason for this?

AAProds wrote on 10/3/2021, 9:16 AM

@jak.willis

So, in Lagarith, what do you need to do to ensure it does compress?

Nothing; it does it automatically.

And, the other weird thing I’ve noticed is that whenever I export a 4:3 video using Lagarith, the output file ends up as 5:4. Is there any particular reason for this?

Well spotted. We've noticed the same. I don't know why. All the AVI exports from MEP seem to have 5:4 in the box (but not when I have a 16:9 project...). I used to think it was the 5:4 analogue video from my capture stick, as it registers as 5:4 in Mediainfo, but since you mention it for your MPEG (which is not, I assume, 5:4), it is a conundrum! At least MEP throws up a message warning you of it.

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

me_again wrote on 10/3/2021, 9:44 AM

@jak.willis @AAProds

Greetings, assuming you are saving to 720x576 then that is 5:4 aspect.

I read somewhere, and it's been proven in practice, that 720x576 accepts 16:9 but not actually 4:3.

We know LAGS does this as does does HEVC and H264. In this lattwr case I convert the files to MKV which is accepted as 4:3 by my TV as long as you tell the mkv converter the aspect you want.

Having said that, if I really need 4:3 as a final aspect ratio, I encode to 720x540 or 764x576 which are both true 4:3s.

But surely this is a moot point as LAGS is only used as an interim codec before finally converting to MP4?

As for MPEG2, all my purchased 4:3 format DVDs are actually in 5:4. I assume there must be a code in the MPEG container to tell the DVD player to convert to the cirrect output fir the TV.

This is where life gets complicated and I doff my cap to the experts.

AndyW

"Just when I think I've learned the workrounds of MEP/MS the bounders go and update it"

Aorus Z690 Elite DDR4 Motherboard

12th Gen Intel(R) Core(TM) i7-12700K, 3600 Mhz, 12 Core(s) 20 Logical Processor(s)

64gb (4x16gb sticks) DDR4 3200Mhz

Intel(R) UHD Graphics 770

Gigabyte GeForce RTX 4060 Eagle OC 8Gb DDR6 DLSS3 Windforce

Corsair RM750 PSU, be quiet! Pure Rock 2 cooling

System drive 500Gb 4.0NVMe M,2 SSD, dedicated video/audio drive 2Tb Gen 4 NVMe SSD, 2x 500Gb Local Fixed Disks (Music etc), USB3 expansion drive 5Tb and 2Tb

Audio Onboard ALC1220 Amp-Up, Windows 11 Home updated as and when

Movie Studio 2025 Suite, Photo Manager Deluxe 13

Norton 360

All Drivers updated as they become available.

AAProds wrote on 10/3/2021, 10:11 AM

@me_again @jak.willis

Nah, MEP correctly interprets it as 4:3 when importing:

When you go to the Export screen, it shows 4:3. But as soon as you choose a codec, the export screen appears to ignore the project setting of 4:3 and jumps to 5:4. I suspect it is because the exporting engine isn't reading the file info properly and reverts to the pixel aspect ratio (which is, as you say, 5:4). In MEP's defence, Mediainfo also reports the DAR of my captures as 5:4, even though they are 4:3.

720x576 4:3 is the standard resolution for all "normal" SD video. Another example is HDV: it's 1440x1080 but coded with a 16:9 aspect ratio. it all depends on what the video Display Aspect Ratio (as opposed to the pixel aspect ratio) is set to.

But surely this is a moot point as LAGS is only used as an interim codec before finally converting to MP4?

Agree. Jak hasn't explained why they want to use LAGS. Although I will say it encodes much quicker that MP4.

This reminds me of a discussion years ago about MEP's "confusing" export of a still from a 720x576 4:3 DAR video. MEP will export it as 768x576 (ie PAR of 4:3), and on re-import, it displays properly but obviously 768x576 PAR (square pixel 4:3).

My head hurts!

Last changed by AAProds on 10/3/2021, 10:15 AM, changed a total of 3 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

johnebaker wrote on 10/3/2021, 10:32 AM

@me_again, @jak.willis, @AAProds

Hi

. . . . in practice, that 720x576 accepts 16:9 . . . .

Yes and no.

If the pixels were to remain square then the resolution for 16:9 would be 720 x 405 or 1280 x 576, depending on whether you keep the width or height constant.

To achieve the 16:9 AR the Pixel Aspect Ratio (PAR) is changed - to be more specific, each pixel is stretched horizontally to the correct aspect ratio so that the video appears as 16:9.

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 24H2 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.

jak.willis wrote on 10/3/2021, 11:11 AM

@me_again, @jak.willis, @AAProds

Hi

. . . . in practice, that 720x576 accepts 16:9 . . . .

Yes and no.

If the pixels were to remain square then the resolution for 16:9 would be 720 x 405 or 1280 x 576, depending on whether you keep the width or height constant.

To achieve the 16:9 AR the Pixel Aspect Ratio (PAR) is changed - to be more specific, each pixel is stretched horizontally to the correct aspect ratio so that the video appears as 16:9.

John EB

All this talk about aspect ratios brings me on to another potential issue that I have...

I own a Panasonic Blu-ray Recorder, as well as a Panasonic Blu-ray Player. When playing 4:3 content on the player, it looks like 4:3. However, when playing 4:3 content on the recorder, the 4:3 aspect ratio doesn’t look correct. In other words, the picture in between the two black bars looks more narrow.

me_again wrote on 10/3/2021, 11:35 AM

@AAProds

Although I will say it encodes much quicker that MP4

Sorry Al, not on my system anymore. Mp4 encoding for me flies in MEP 2022 - at last 😄

AndyW

"Just when I think I've learned the workrounds of MEP/MS the bounders go and update it"

Aorus Z690 Elite DDR4 Motherboard

12th Gen Intel(R) Core(TM) i7-12700K, 3600 Mhz, 12 Core(s) 20 Logical Processor(s)

64gb (4x16gb sticks) DDR4 3200Mhz

Intel(R) UHD Graphics 770

Gigabyte GeForce RTX 4060 Eagle OC 8Gb DDR6 DLSS3 Windforce

Corsair RM750 PSU, be quiet! Pure Rock 2 cooling

System drive 500Gb 4.0NVMe M,2 SSD, dedicated video/audio drive 2Tb Gen 4 NVMe SSD, 2x 500Gb Local Fixed Disks (Music etc), USB3 expansion drive 5Tb and 2Tb

Audio Onboard ALC1220 Amp-Up, Windows 11 Home updated as and when

Movie Studio 2025 Suite, Photo Manager Deluxe 13

Norton 360

All Drivers updated as they become available.

AAProds wrote on 10/3/2021, 6:57 PM

@me_again

Sorry Al, not on my system anymore. Mp4 encoding for me flies in MEP 2022 - at last 😄

Now you're taunting me, Andy! 😂

@jak.willis

I own a Panasonic Blu-ray Recorder, as well as a Panasonic Blu-ray Player. When playing 4:3 content on the player, it looks like 4:3. However, when playing 4:3 content on the recorder, the 4:3 aspect ratio doesn’t look correct. In other words, the picture in between the two black bars looks more narrow.

Probably caused by dodgy encoding of the content ie DAR/PAR/SAR not set correctly.

https://en.wikipedia.org/wiki/Pixel_aspect_ratio

Some players will play a file correctly, even though all the AR settings may not be spot on. Other players may not.

There may be a setting in the BluRay recorder controls that can set what to do if playing 4:3 content.

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