Selecting Movie Settings with VP X16

Comments

emmrecs wrote on 8/27/2024, 3:30 AM

@rickduley

Hi Rick,

Coming a little late to this party... but certain data presented in your posts strike me as requiring some comment.

  1. DVD, by format definition, can only ever be SD (Standard Definition). It is a common misconception that DVDs are "High Definition". Hence, your 1920 x 1080 original footage can only ever be 720 x 576 on disc, unless you use the option to burn to AVCHD disc, but its storage capacity is then limited (a maximum of about 30 minutes playing time) and the discs require a BD drive to play them.
  2. I note the original file has an additional audio track and a text track. I don't think VPX will "cough" at that additional audio but I am not sure how it will handle the text track.
  3. I am also struck by the very low bit rate of the original, given it is said to be in BD format.
  4. Just pure speculation on my part: but I wonder if the "gap" at the beginning of your original file was actually the data which contained the Teletext and Visual Impaired Commentary. If so, again I suspect VPX would not know how to handle it.

I hope other users will continue to "chime in" on this but I think, since your final output (to DVD) can only ever be Standard Definition I would be tempted to run the file through a convertor, like Handbrake, and produce a more standard mp4 (at that higher resolution 1920 x 1080) and then try using that in VPX to burn a disc.

If the burn still fails this will only lose you some additional time (!!) but you will still have your original footage (and the converted mp4) to continue to play with!

Jeff
Forum Moderator

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, NVidia GTX 1660TI and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

rickduley wrote on 8/27/2024, 7:39 AM

@AAProds, is that the information you wanted? I just cut-and-pasted the text report. Is there something else you were looking for?

--------------------------------------------
Rick Duley
North Perth,
Western Australia
--------------------------------------------

My machine is Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz   3.00 GHz; 64-bit operating system, x64-based processor
Edition    Windows 11 Pro; Version    22H2
Installed on    ‎3/‎04/‎2024 OS build    22621.3447
Experience    Windows Feature Experience Pack 1000.22688.1000.0

rickduley wrote on 8/27/2024, 7:41 AM

@emmrecs, I have downloaded HandBrake-1.8.2-x86_64-Win_GUI.exe and will install and try in the morning.

--------------------------------------------
Rick Duley
North Perth,
Western Australia
--------------------------------------------

My machine is Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz   3.00 GHz; 64-bit operating system, x64-based processor
Edition    Windows 11 Pro; Version    22H2
Installed on    ‎3/‎04/‎2024 OS build    22621.3447
Experience    Windows Feature Experience Pack 1000.22688.1000.0

AAProds wrote on 8/27/2024, 9:18 AM

@rickduley

Rick, no, that's great.

A quicker thing to try before you do a complete re-render would be to change the MTS into an MP4 with AVIDemux; my guide here. In addition to that, on the Audio menu, choose "Select track" and untick everything except track 1.

Then, do a Save. AVIDemux should simply re-write the file header data and produce an MP4 quite quickly.

Import that into VPX and see if it renders all the way through during the Burn process.

If that fails, you can continue to use AVIDemux to do a full re-render or Handbrake, but that will come later.

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

Various other SSD and HDDs.

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

MEP 2021 version 20.0.1.80

Movie Studio 2023 version 22.0.3.172

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 8/27/2024, 12:47 PM

@rickduley

Hi Rick, Al

@AAProds commented

A quicker thing to try before you do a complete re-render would be to change the MTS into an MP4 with AVIDemux

I agree partly with this, however I would advise a full re-render.

Testing with a MTS file and a MP4 file with the same video and audio formats as your original mts file, both burns to ISO file took just over 1 hr each! The movie was only 1min 28 sec long.

Conversion of the MTS file to MP4 AVC/AAC and burning this file took 1min 12 secs to encode and create ISO image.

HTH

John EB

Last changed by johnebaker on 8/27/2024, 12:48 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 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.

rickduley wrote on 8/27/2024, 5:00 PM

I have Handbrake running

and it looks like taking a couple of hours to generate the MP4. However, there are other things I can do - like housekeeping! 😖

--------------------------------------------
Rick Duley
North Perth,
Western Australia
--------------------------------------------

My machine is Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz   3.00 GHz; 64-bit operating system, x64-based processor
Edition    Windows 11 Pro; Version    22H2
Installed on    ‎3/‎04/‎2024 OS build    22621.3447
Experience    Windows Feature Experience Pack 1000.22688.1000.0

rickduley wrote on 8/28/2024, 7:04 AM

Just watched Thirteen Days.

  1. About seven hours of processing;
  2. Movie ran just fine;
  3. Mild soft focus - acutance not as high as usual;
  4. Proves that VPX16 talks to my active DVD Drive.

--------------------------------------------
Rick Duley
North Perth,
Western Australia
--------------------------------------------

My machine is Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz   3.00 GHz; 64-bit operating system, x64-based processor
Edition    Windows 11 Pro; Version    22H2
Installed on    ‎3/‎04/‎2024 OS build    22621.3447
Experience    Windows Feature Experience Pack 1000.22688.1000.0