@AAProds

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

Ray.

@CubeAce

Hi Ray

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

John EB

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

@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.

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

@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.

Hey Ray see my REVISED post above! 😃

@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.

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?

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.

"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

@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.

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

@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.

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

@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