MAGIX Video deluxe 2026-encoding failed

Alfns wrote on 9/23/2025, 4:38 PM

Burning a project to a VIDEO_TS file is aborted with the error message ´The burning process was aborted with the following error: “Encoding failed. Encoding of the movie failed. OK Show log file. See attachment.” It seems as I cannot enclose the "Videodeluxe.log2"-file here. I have also tried with some BAK.MV_projects. What could be the cause of this?

Comments

Alfns wrote on 9/24/2025, 2:35 AM

The burn procedure is completed after about 30 minutes and a vob.file, 0.99 GB, has been created.

Can the project's track 1 (the movie) and track 2 (titles), and perhaps the chapter markers, be saved and then imported into a new project?

AAProds wrote on 9/24/2025, 3:21 AM

@Alfns

Can the project's track 1 (the movie) and track 2 (titles), and perhaps the chapter markers, be saved and then imported into a new project?

Yes. By "new" I assume you mean "another" project.

Save your current project. It will be saved as an MVP.

Open the other project. Then open this project. You'll get some prompts closing or adding. Choose the appropriate steps. The second project will be added to the already-open one.

Alternatively, you can save the movie you just made as an MVD (single movie file) and import that into the other project. Use the File>manage project menu for that.

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

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

Magix Video Deluxe 2026 Ultimate (although it comes up as "Premium").

Magix Video Easy version 7.0.1.145

System 2

(Still in use for TV and videotape capture)

Windows 10 Home Version 2009

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

Movie Studio 2023

Movie Studio 2024

VPX 12

System 3

Lenovo Yoga laptop

Windows 11

CPU i5-8250U (1,6ghz)

8GB DDR4 2400 RAM

GPU iGPU UHD620

2TB NVME HDD

Video Deluxe 2026

johnebaker wrote on 9/24/2025, 4:06 AM

@Alfns

Hi

. . . . Encoding failed. Encoding of the movie failed . . . .

This usually means there is something on the timeline, at the same time point on the timeline as the failure occurs, that the encoder cannot handle.

Try exporting the video as a MPG video, watch the Movie time in the export dialog and note the time the export fails, if it does, and look at the time region on the timeline to see what is their eg a transition, image change or effect.

. . . . The burn procedure is completed after about 30 minutes and a vob.file, 0.99 GB, has been created. . . .

Is it playable with no issues?

. . . . Can the project's track 1 (the movie) and track 2 (titles), and perhaps the chapter markers, be saved and then imported into a new project? . . . .

Edit:

I use MVD export method Al mentioned, File, Manage project, Export movie file, Magix movie (* .mvd)

You can then load this file into a new or existing project.

The only downside to this method is that the media must be in the original location as it is in the project from which you exported the MVD file.

Other methods such as making a Backup of the project and media, duplicates the media used.

HTH

John EB
Forum Moderator

Last changed by johnebaker on 9/24/2025, 4:09 AM, 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.

Alfns wrote on 9/24/2025, 8:17 AM

Thanks for all the comments. I wonder what's going on here though. After four attempts it has failed and a vob.file (0.99 GB) has been created each time and contains the first 22 minutes of the movie. Then I chose the option to export the file as an mpeg-4 file and it was successful. The file size was 3759 MB. Then I made a fifth attempt to burn files to a VIDEO_TS folder. Then it was successful and the folder size was 3.73 GB. Strange.

AAProds wrote on 9/24/2025, 6:43 PM

@Alfns

Then I made a fifth attempt to burn files to a VIDEO_TS folder.

You can't "burn" (or more accurately "encode") straight to the VIDEO_TS folder. You either have to burn a physical DVD or "burn" to ISO using the "Image Recorder" option. Only then can you access the VIDEO_TS folder and only then can you access the VOBs.

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

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

Magix Video Deluxe 2026 Ultimate (although it comes up as "Premium").

Magix Video Easy version 7.0.1.145

System 2

(Still in use for TV and videotape capture)

Windows 10 Home Version 2009

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

Movie Studio 2023

Movie Studio 2024

VPX 12

System 3

Lenovo Yoga laptop

Windows 11

CPU i5-8250U (1,6ghz)

8GB DDR4 2400 RAM

GPU iGPU UHD620

2TB NVME HDD

Video Deluxe 2026

Alfns wrote on 9/25/2025, 2:57 AM

?
Over the course of the year I have used four different editions of Magix Edit software and almost always finished the project by selecting "Burn-DVD-Encode in folder" and there selecting a VIDEO_TS folder that I created on the computer's hard drive. I have then burned the VIDEO_TS folder to a DVD that can then be played on a DVD player. See attachments. So I don't know what AAProds means.

johnebaker wrote on 9/25/2025, 3:23 AM

@Alfns

Hi

Why do you not burn direct to disc?

John EB
Forum Moderator

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.

AAProds wrote on 9/25/2025, 3:28 AM

@Alfns

almost always finished the project by selecting "Burn-DVD-Encode in folder" 

My profuse apologies, I forgot about the "encode in folder" option.

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

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

Magix Video Deluxe 2026 Ultimate (although it comes up as "Premium").

Magix Video Easy version 7.0.1.145

System 2

(Still in use for TV and videotape capture)

Windows 10 Home Version 2009

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

Movie Studio 2023

Movie Studio 2024

VPX 12

System 3

Lenovo Yoga laptop

Windows 11

CPU i5-8250U (1,6ghz)

8GB DDR4 2400 RAM

GPU iGPU UHD620

2TB NVME HDD

Video Deluxe 2026

Alfns wrote on 9/25/2025, 5:16 AM

"Why do you not burn direct to disc?"

The reason is that I want to have a backup to use if the disk fails.

emmrecs wrote on 9/25/2025, 8:52 AM

@Alfns

The reason is that I want to have a backup to use if the disk fails.

The process of creating the DVD/BD files in all Magix video editing products automatically creates a folder containing ALL the files needing to be burned to the disc before the actual burning takes place. That folder is not removed or deleted unless the user chooses to do so.

Essentially, the Image Recorder option also creates that same folder and then creates the .iso file which can be used to burn the disc(s) and can be retained permanently by the user. I certainly keep ALL the .iso files I have created over a number of years so that I can, quite easily, burn a replacement or additional disc without problem. To be clear, I don't retain the folder of files but I do retain the single .iso file which contains everything needed for the disc burning process.

HTH

Jeff
Forum Moderator

Win 11 Pro 64 bit, Intel i7 14700, 32 GB RAM, NVidia RTX 4060 and Intel UHD770 Graphics, Audient EVO 16 audio interface, VPX, MEP, Music Maker, Vegas Pro, PhotoStory Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

Alfns wrote on 9/25/2025, 9:26 AM

I see.

AAProds wrote on 9/25/2025, 7:58 PM

@emmrecs @Alfns

Jeff, the files for DVD burns aren't arranged in a VIDEO_TS folder, they are just plopped in a folder of the project's name. Bluray folders are OK because they don't live in any singular folder anyway. This is what Magix produces during the burn process (that base folder is the one I set in Settings>Folders):

The DVD files folder could be renamed, of course.

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

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

Magix Video Deluxe 2026 Ultimate (although it comes up as "Premium").

Magix Video Easy version 7.0.1.145

System 2

(Still in use for TV and videotape capture)

Windows 10 Home Version 2009

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

Movie Studio 2023

Movie Studio 2024

VPX 12

System 3

Lenovo Yoga laptop

Windows 11

CPU i5-8250U (1,6ghz)

8GB DDR4 2400 RAM

GPU iGPU UHD620

2TB NVME HDD

Video Deluxe 2026

emmrecs wrote on 9/26/2025, 3:30 AM

@AAProds

Hi Al,

the files for DVD burns aren't arranged in a VIDEO_TS folder, they are just plopped in a folder of the project's name.

I agree! That's what I meant when I wrote about VdL automatically creating a folder... 

Jeff

Win 11 Pro 64 bit, Intel i7 14700, 32 GB RAM, NVidia RTX 4060 and Intel UHD770 Graphics, Audient EVO 16 audio interface, VPX, MEP, Music Maker, Vegas Pro, PhotoStory Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

johnebaker wrote on 9/26/2025, 5:09 AM

@AAProds

Hi Al

The folder Jeff mentioned is the first half, ie render all the video files needed, of a 2 stage burn process, it is the second stage, the actual burn, whether to disc or ISO file, that creates the correct folder structure from the prerendered files folder.

ImgBurn, Nero Burning ROM can use the prepared files to create the correct on disc folder structure, below is an ImgBurn prep from the 1st stage files produced by VDL 2026.

Note all the required support files for the player are also created.

@Alfns

Hi

. . . . I want to have a backup to use if the disk fails . . . .

Understandable, why not burn to disc and then make a backup copy of it using good quality branded disks - I use Ritek discs, one for use and the other for backup. The backup is stored in a black DVD/BD case in a cool, dry, dark space.

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.

AAProds wrote on 9/26/2025, 5:57 AM

@johnebaker

it is the second stage, the actual burn, whether to disc or ISO file, that creates the correct folder structure from the prerendered files folder.

John, @Alfns point is that the VIDEO_TS folder is not created on the PC as a folder by the process. It goes onto a disk, yes, and it gets buried in an ISO, yes, but it isn't easily accessed by both of those processes.

I can understand the desire to create just the VIDEO_TS in one go. After, that can easily be used to burn a disk later.

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

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

Magix Video Deluxe 2026 Ultimate (although it comes up as "Premium").

Magix Video Easy version 7.0.1.145

System 2

(Still in use for TV and videotape capture)

Windows 10 Home Version 2009

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

Movie Studio 2023

Movie Studio 2024

VPX 12

System 3

Lenovo Yoga laptop

Windows 11

CPU i5-8250U (1,6ghz)

8GB DDR4 2400 RAM

GPU iGPU UHD620

2TB NVME HDD

Video Deluxe 2026