Capturing Mini DV: Is it possible to adjust the output file type ?

Comments

AAProds wrote on 11/19/2021, 5:17 AM

Backstory-Germany has been badly de-interlaced and the interlacing is now "burnt in"; changing the framerate isn't going to fix this. The top image is from the original file, the bottom is the video with a deinterlace filter applied and the framerate doubled to 59.94:

ย 

ย 

Last changed by AAProds on 11/19/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

CubeAce wrote on 11/19/2021, 8:30 AM

@AAProds

Are you sure the project files are burnt in Alwyn and not just the export?

Ray.

ย 

ย 

Windows 10 Enterprise. Version 22H2 OS build 19045.5608

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.2130 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."

johnebaker wrote on 11/19/2021, 9:48 AM

@CubeAce

Hi Ray

It could be Defender, though I never saw this message appear before I went back to Avast.

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.

CarpentersMate wrote on 11/19/2021, 1:15 PM

Hello friends .... I really appreciate all your help thank you ...

I posted those VOB's for content critique ONLY - the main question/issue of 'archiving' using MPEG-2 files (as opposed to AVI) came up as result of trying to export using MEP. I'm using MEP to capture removing stress on these older Mac desktops, (there's a lot to capture). I partially solved the problem using 'Wondershare' to convert an AVI file to an MPEG file (which requires less processing time). However still having issues with specifically MPEG-2 ???? I will find a solution! ๐Ÿ˜

Most media was originally captured (beginning 2006) using these parameters:

http://www.ww2survivorstories.com/G5-File-ID.jpg

Wondershare conversions and info:

http://www.ww2survivorstories.com/Mov-1.jpg

http://www.ww2survivorstories.com/Mov-2.jpg

http://www.ww2survivorstories.com/Mov-3.jpg

You might get a prompt to DOWNLOAD- SAVE this file:

http://www.ww2survivorstories.com/242-MID-2539-ARC-43760-1.mpg

I'd like to avoid discussion regarding the SD footage (that's a beaten dog). ๐Ÿ˜ซ I can work with that later... ๐Ÿ˜…

What have I missed? We will solve the issue with MPEG-2 .....

Thank You

Mike

ย 

ย 

Last changed by CarpentersMate on 11/20/2021, 12:11 AM, changed a total of 13 times.

For Magix: Running Windows 10 Professional 64 bit - Dell Precision Workstation 3620 - i7 7700K 4.20 GHz Processor - 32GB Memory - (onboard video), Asus PCI Sound Card - iGPU - Two Twin esata 2TB External Drives. And for other software: Two Mac Pro Desktops with PCI & PCIe Soundcards & nVidia GeForce Graphics Cards - Mimimum memory of 16GB with #10 2TB esata Twin External Drives.

http://www.ww2survivorstories.com/

CubeAce wrote on 11/19/2021, 2:03 PM

@CarpentersMate

Hi Mike.

I see nothing wrong with that mpg file. Even at full screen it is quite reasonable.

I don't get much useful information from the data in the jpgs though.

I'm wondering if some of the conversions used the wrong parameter when converted to mpeg-2 from avi such as asking the program to use the wrong field first. That would make the combing effect worse I think.

You say some were done using filmora?

Ray.

ย 

Windows 10 Enterprise. Version 22H2 OS build 19045.5608

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.2130 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."

CarpentersMate wrote on 11/19/2021, 2:16 PM

Hello again Ray

"I see nothing wrong with that mpg file. Even at full screen it is quite reasonable"

I think we solved the MPEG-2 issue? ๐Ÿ˜ณ

This is how the file reads and opens in the Mac - Check this out:

http://www.ww2survivorstories.com/Picture2a.jpg

What does 'MPEG2 Muxed' mean? As long as the Bit Rate is higher than a QT .Mov file I think the conversion will be helpful-useful (as opposed to AVI)?

Alwyn where are you? Are you ready for a Chicken Dinner? ๐Ÿ˜‰

Thank You

Mike

Last changed by CarpentersMate on 11/20/2021, 12:12 AM, changed a total of 2 times.

For Magix: Running Windows 10 Professional 64 bit - Dell Precision Workstation 3620 - i7 7700K 4.20 GHz Processor - 32GB Memory - (onboard video), Asus PCI Sound Card - iGPU - Two Twin esata 2TB External Drives. And for other software: Two Mac Pro Desktops with PCI & PCIe Soundcards & nVidia GeForce Graphics Cards - Mimimum memory of 16GB with #10 2TB esata Twin External Drives.

http://www.ww2survivorstories.com/

CubeAce wrote on 11/19/2021, 2:24 PM

@CarpentersMate

Hi Mike.

I meant the data on the files doesn't show whether each file is interlaced or not or which field was encoded first which could have made the combing worse rather than eliminating it. It just gives the file type and resolutions.

I got the warning again, probably a problem at my end as John suggested. I could do both, download or view.

Ray.

ย 

Windows 10 Enterprise. Version 22H2 OS build 19045.5608

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.2130 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."

CarpentersMate wrote on 11/19/2021, 2:37 PM

Hey Ray see my REVISED post above! ๐Ÿ˜ƒ

For Magix: Running Windows 10 Professional 64 bit - Dell Precision Workstation 3620 - i7 7700K 4.20 GHz Processor - 32GB Memory - (onboard video), Asus PCI Sound Card - iGPU - Two Twin esata 2TB External Drives. And for other software: Two Mac Pro Desktops with PCI & PCIe Soundcards & nVidia GeForce Graphics Cards - Mimimum memory of 16GB with #10 2TB esata Twin External Drives.

http://www.ww2survivorstories.com/

CubeAce wrote on 11/19/2021, 5:08 PM

@CarpentersMate

Hi Mike.

Muxing is just combining everything you do in a video editor such as edit the video and sound tracks as well as titling etc and compress into the final container format as a single file to be read by a player.

As I said, those images give no indication as to which field of the interlaced video was played back first for each frame when exporting. I assume getting it correct gives a well timed interlaced frame whereas possibly reading the wrong field first would mean the interlocking images are out of step producing the comb effect. At least that is what logic is telling me. I have never had to deal with interlaced material and the only experience I have has been from reading various posts here.

I think it is time to give Alwyn a new headache ๐Ÿคฃ๐Ÿคฃ๐Ÿคฃ

Ray.

ย 

Windows 10 Enterprise. Version 22H2 OS build 19045.5608

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.2130 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."

CarpentersMate wrote on 11/19/2021, 5:20 PM

Editing in FC I rarely deal with AVI files (the captures are always QT files).

With archiving/storage, as long as the Bit Rate is higher than a QT .Mov file I think the conversion will be helpful-useful (as opposed to a much larger AVI file), or a lower resolution MPEG-4 ....

Do you agree?

ย 

For Magix: Running Windows 10 Professional 64 bit - Dell Precision Workstation 3620 - i7 7700K 4.20 GHz Processor - 32GB Memory - (onboard video), Asus PCI Sound Card - iGPU - Two Twin esata 2TB External Drives. And for other software: Two Mac Pro Desktops with PCI & PCIe Soundcards & nVidia GeForce Graphics Cards - Mimimum memory of 16GB with #10 2TB esata Twin External Drives.

http://www.ww2survivorstories.com/

AAProds wrote on 11/19/2021, 7:12 PM

Alwyn where are you? Are you ready for a Chicken Dinner?ย 

Had a lamb roast last night and just got up! ๐Ÿ˜‰

"Muxing" is short for Multiplexing, where the video stream and audio stream are joined together to form the final file. The opposite is demuxing, or demultiplexing, where the video stream and audio stream are split. This is often done to work on the video portion/stream of a file. After the video stream has been worked-on, it is multiplexed, or muxed, again, to re-create the file.

Those MP4s are definitely Progressive videos (also, Mediainfo reports as such), and the interlacing artifacts (combing) are baked in and cannot be corrected easily. If I'm following Mike's workflow correctly, I'd say it is Wondershare that is messing up the conversion from DV to MP4. @CubeAce Ray, open that file in MEP and step through to a motion portion. You can see the combing. MEP won't display the combing if the file is Interlaced. I use the term "combing" loosely, because "combing" and interlace artefacts are two different beasts. For example, a comb filter is not required when using S-video, and is beneficial when using Composite video (or the other way round, I'm not sure which). It is not related to the interlacing of fields and frames.

Editing in FC I rarely deal with AVI files (the captures are always QT files).

I think Apple's confusing you. A Quicktime file could be anything. In this case, I suspect that the QT MOVs you are editing are simply DV-AVI format files in the MOV "container" or file extension. Have a close look at the screenshot of the file details posted earlier: about half way down the table is the codec: "DV/DVCPRO". If you're capturing/transferring from a DV camera, even with an Apple computer, your files will be DV, it's just that Apple calls them MOVs or generically "Quicktime movies", whereas Windows calls them what they really are, AVIs.

With archiving/storage, as long as the Bit Rate is higher than a QT .Mov file I think the conversion will be helpful-useful (as opposed to a much larger AVI file), or a lower resolution MPEG-4 ....

Do you agree?

Nope. If the bitrate is higher than the QT MOV file (which I think is simply the captured DV-AVI), the result will be an even bigger file. You may as well just keep the DV AVIs for archiving.

Regarding your versions of MEP, I would definitely use MEP 2016; every later version has improved it's handling of the various file types (I remember early on that MEP couldn't even open an MPEG; now it loves them).

So, back to the problem: lack hard disk space. I suggest capture each tape, then convert it with MEP 2016 to MPEG 2 (Interlaced, Bottom Field First) at 12,000kpbs for archiving/later editing. That MPEG will be about 80mb per minute, as opposed to DV, which is 216mb per minute, and will be easily editable in MEP 2016 with your Windows system. Those MPEGs probably will not open in Apple.

If you want to use Apple, the only option you will have is to either archive the DVs (QT MOVs) and use those for editing, or convert the DVs to MPEG-4, so that Apple can open them. As I alluded to earlier, editing MP4s is less desirable.

ย 

ย 

ย 

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

CarpentersMate wrote on 11/19/2021, 8:11 PM

"Had a lamb roast last night"

Was going to buy you a Chicken Dinner! ๐Ÿ˜†

"A Quicktime file could be anything. In this case, I suspect that the QT MOVs you are editing are simply DV-AVI format files in the MOV "container" or file extension"

"DV/DVCPRO"

Thank You - I understand that now ... ๐Ÿ™‚

"convert it with MEP 2016 to MPEG 2"

I'm using a work-around for the incompatible MPEG-2 issue converting the captured AVI to MPEG-2 with wondershare. Final Cut and QT Player in the Apple OS now both recognize that file ... The output MPEG-2 file has a higher Bit Rate than the MPEG-4 export using MEP - The output MPEG-2 (in size) is greater than the MPEG-4 export but smaller than the AVI. It does appear to minimize the archive while retaining quality.

"I would definitely use MEP 2016"

I'll try that but this other work-around seems to suffice? For another discussion: What I'm thinking about is eventually continue editing in FC, then possibly use MEP for higher quality captions and titles ....?

Thank You Alwyn

Mike

Last changed by CarpentersMate on 11/19/2021, 8:28 PM, changed a total of 4 times.

For Magix: Running Windows 10 Professional 64 bit - Dell Precision Workstation 3620 - i7 7700K 4.20 GHz Processor - 32GB Memory - (onboard video), Asus PCI Sound Card - iGPU - Two Twin esata 2TB External Drives. And for other software: Two Mac Pro Desktops with PCI & PCIe Soundcards & nVidia GeForce Graphics Cards - Mimimum memory of 16GB with #10 2TB esata Twin External Drives.

http://www.ww2survivorstories.com/

AAProds wrote on 11/19/2021, 8:44 PM

@CarpentersMate

The output MPEG-2 (in size) is greater than the MPEG-4 export but smaller than the AVI. It does appear to minimize the archive while retaining quality.

OK, that's good.

The other thing that has to be addressed/fixed is that "combing" effect as pointed out by Ray, for example in the Back Story Germany file. It spoils what is otherwise a fantastic production. What workflow/process/programs did you use to produce that final MP4?

What I'm thinking about is eventually continue editing in FC, then possibly use MEP for higher quality captions and titles ....?

Not advisable because to move from FC to MEP will require an encode, creating another generation. Then, adding even simple captions and titles in MEP will require yet another complete encode of the file you edited in FC. I suggest you stick with one or the other: do your editing and titling in one go and encode to MP4 as the final file.

ย 

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

CarpentersMate wrote on 11/19/2021, 9:16 PM

The Germany piece? You guys must have missed the description/explanation? ๐Ÿ˜ช

Those 'Back Story' pieces were extracted VOB's - they were not FC exports ... I posted them strickly for 'content critique' so promptly took them down from this post... Due to health, I was forced to relocate 3 times in 3 years, never had opportunity to set up shop again.... ๐Ÿ˜Ÿ

I can mail you a copy of the 'DVD Back Story'? Message me your address ๐Ÿ˜‰

This was the set up back in 2006 - Now I use two display monitors and #8 externals connected via esata

"Not advisable to move from FC to MEP"

Then its highly unlikely to move 'everything' over to a 'Windows World' without investing in some hefty PC's ..

I will never give up ...

Thanks Alwyn

Mike

Last changed by CarpentersMate on 11/20/2021, 10:06 PM, changed a total of 13 times.

For Magix: Running Windows 10 Professional 64 bit - Dell Precision Workstation 3620 - i7 7700K 4.20 GHz Processor - 32GB Memory - (onboard video), Asus PCI Sound Card - iGPU - Two Twin esata 2TB External Drives. And for other software: Two Mac Pro Desktops with PCI & PCIe Soundcards & nVidia GeForce Graphics Cards - Mimimum memory of 16GB with #10 2TB esata Twin External Drives.

http://www.ww2survivorstories.com/

AAProds wrote on 11/20/2021, 8:27 PM

@CarpentersMate

Mike,

To clarify a statement I made earlier about MEP's MP4 export times, I have run some export-time tests. Here are the results:

Source file: 11:55 720x576 4:3 DV-AVI

Encoding parameters: 720x576 4:3 MPEG-4 at Average bitrate of 6000kbps, Max 8000kbps, 192kbps AAC audio.

Times:

MEP Default MPEG-4 encoder: 26:28

MEP Main Concept MPEG-4 encoder: 5:39

VideoRedo: 5:36.

I don't have a GPU to speak of, so this is just CPU-only encoding. I expect you are in a similar boat.

I don't know whether MEP 2016 has access to the Main Concept MPEG-4 encoder, but if it does, you can expect much quicker export times than I alluded-to before. My comment about MEP export being a dog applies only to the default MPEG-4 encoder.

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

CarpentersMate wrote on 11/20/2021, 10:04 PM

Thanx for the timed export tests - Wondershare is 'ok' too ...

"My comment about MEP export being a dog applies only to the default MPEG-4 encode"

Understood

"If MEP 2016 has access to the Main Concept MPEG-4 encoder, you can expect much quicker export times"

Understood

I keep the # 2 Mac's offline - strickly for editing. I need to pick up a 'later' model used Dell with faster processor. Will also keep that offline - strickly for editing. (Currently having intermittent freezes) using MEP, the processor is too slow ...

Still not totally set up with Apple Desktops ... all in good time ...

I'll try to message you requesting your location ....

Thank You Alwyn ๐Ÿ˜Ž

Mike

ย 

For Magix: Running Windows 10 Professional 64 bit - Dell Precision Workstation 3620 - i7 7700K 4.20 GHz Processor - 32GB Memory - (onboard video), Asus PCI Sound Card - iGPU - Two Twin esata 2TB External Drives. And for other software: Two Mac Pro Desktops with PCI & PCIe Soundcards & nVidia GeForce Graphics Cards - Mimimum memory of 16GB with #10 2TB esata Twin External Drives.

http://www.ww2survivorstories.com/

johnebaker wrote on 11/21/2021, 4:49 AM

@CarpentersMate, @AAProds

Hi

When I played the video clips with the 'artifacts' at first I though they were a deliberate 'old film effect' very poorly done, however after stepping through then they look more like a loss of signal during a line scan, were the originals used to create the VOBs on tape?

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.

CarpentersMate wrote on 11/21/2021, 12:39 PM

Hello John - Nice to see you ..

"the VOB's were not FC exports ... they were not exported from the original tape, they were extracted from a DVD using wondershare ..they were older, and posted strickly for 'content critique' and convenience since I did not have any equipment set up at that time"

The thread/issue here (which was addressed), was finding a work-around to export-convert the archived AVI to a more manageable archive file size 'MPEG-2'

Using MEP to capture was also a way to take some stress off the older Mac's. (There's about 50-60 Mini Tapes remaining) which could potentially have up to 8 hours of content on each of them ....๐Ÿ˜ฉ

Happy Thanksgiving John! ๐Ÿ˜†

ย 

Last changed by CarpentersMate on 11/21/2021, 2:07 PM, changed a total of 2 times.

For Magix: Running Windows 10 Professional 64 bit - Dell Precision Workstation 3620 - i7 7700K 4.20 GHz Processor - 32GB Memory - (onboard video), Asus PCI Sound Card - iGPU - Two Twin esata 2TB External Drives. And for other software: Two Mac Pro Desktops with PCI & PCIe Soundcards & nVidia GeForce Graphics Cards - Mimimum memory of 16GB with #10 2TB esata Twin External Drives.

http://www.ww2survivorstories.com/