Cutting error with Tmpeg

[doot]

Hi all,

When I cut a Mpg (1 or 2) with Tmpeg I get this error come up after I click edit on the file after I set my start and finish points.

At address 73F91D04 , read error occurred against adrress 73F91D04

But sometimes it`ll let me carry on with the cut

Thanks

[Sefy]

Personaly, that sound like a RAM problem, do you happen to have two types of RAM chips in your system ?

It seems to be a TMPGenc bug, many people have this problem including myself. Luckily I have a dual boot win2000/xp. With win2000 I have no probs only in XP.


Wait for the next release..................

[Sefy]

Most problems are software problems, rarely it's also a hardware problem, but then it would be visible in other aspects of the PC usage (Crashes/BSOD)

I have Windows98SE, and i've got a fresh ghost backup, so if anything trashes my registry, I can restore a clean backup which I know is good, and that fixes all my problems.

As i've mentioned, try checking if you happen to have 2 diffrent RAM chips in your PC, and if you do, try taking one of them out and doing the cutting again

Sefy dude, what you are saying sounds like bullshit to me but if doot wants to experiment ripping out memory modules good luck

(especially when many tmpeg users have the same problem)

[Sefy]

It may sound like bullshit to you, but I don't bullshit, i've seen alot of systems crashing down (applications crashing for no reason) just because the PC has two incompatible RAM chips.

It can also be software, but if TMPGEnc gives an error, it gives it for a reason and it could also be a defective MPG file and a demux/remux can fix it and then he can try splitting.

But hardware problems is also a problem, and especialy with mixed ram chip

[Zogg]

I have the exact same problem with TMPGenc. It seems to do the cut okay, despite the error message, but is VERY imprecise - the start and end cut times I pick are in reality off by 30 seconds to several minutes. It takes a long trial and error procedure to get it right. I have to time the clip by hand and guess where to cut it.

I am running XP, and I have two memory sticks of different origin. I do have issues sometimes with ATI MMC File player or scheduler locking up, so it might indeed be the two RAM sticks. It might be XP but things were working fine previously (I had never tried the cut feature, though). About the time I upgraded the ATI s/w to 7.6 I also installed the extra memory, and that's when I started to notice a few problems. I was attributing it to the ATI s/w, but Sefy's post makes me think it might be the memory, which I hadn't thought of.

I'll check it out, but Doot might have a different problem.

[Zogg]

Well, I just noticed another post on the list with the same problem. The common thread? Windows XP.

[Sefy]

I don't know, although i'd love to blame XP, but I need more proof so it will stick
Zogg, try taking out one of the chips, and try the same operation again, if it fails, switch between them, and see if anything goes, especialy since you reported other random errors happening.

[doot]

I Might give the ram sticks a go as I have two. If not what other programs could I use that would cut mpg files.

[Sefy]

There are 3 more programs i'm familiar with that can cut mpegs, although there might be more (i'm quite sure there are more!), those that I know are:
Darim Vision M-Editor
Womble MPEG2VCR v3.11
MPEG Editor Professional

I Think Darim Vision M-Editor is free, i'm not sure, but I know the other two are not free.

[Zogg]

Okay, I finally was able to remove the cheap memory stick and leave in my good Crucial memory. I got the same error message with TMPGenc. I tried both 2.53 and the older 12a, same problem. For me, though, TMPGenc does actually cut the video, I just get the error message.

The output file looks fine, too, but the timing is off by at least 30 seconds. Maybe that has something to do with the file as it comes from ATI MMC, but it plays fine on everything so who knows.

I should have tried keeping in the cheapo memory and take out the Crucial, but I don't think it's the memory now. I think it is something to do with Windows XP on some systems.

I'm about ready to just pay for MyFlix XE to cut my MPEG2 files and be done with it.

[Sefy]

Does TMPGEnc give you any error if you try to Demuplex the MPG file ?

[Zogg]

Nope. No error messages doing a demux with 2.5.3.

[Sefy]

Great, now try remuxing the file but as Non-Standard , and see what the size it comes out as.

The reason i'm asking this, is cause i've had a few times where TMPGEnc made a file, it plays great, but the image always comes out huge, and when I demux and remux as non-standard the file itself actually comes out smaller!

[Zogg]

Sefy, I did what you asked and this is amazing and baffling.

I have been playing a bit with different programs to see which yields the best result when editing out the commercials from my ATI AIW Radeon captures. I just finished a Farscape video, 44 minutes total, which I edited using Womble MPEG2VCR. I demuxed then remuxed using Womble, since I read that can fix some issues with ATI audio encoding when capturing real time in MPEG2. The file was about the size of the original, 789MB. Then I edited the file, but the finished file was about the size of the original file, 798MB.

Using TMPGenc 2.5.3, I demuxed and then remuxed like you said and got 529MB. My first attempt at editing the file was with TMPGenc using the cut feature, and there I got 528MB (although the editing took hours because it's so imprecise). That file size seems reasonable.

So yes, the file was much smaller as you predicted. You said you have seen this with TMPGenc also. I wonder what is going on?

BTW they all look identical when played on the computer.

[Sefy]

Yup, just as I thought, I don't know yet if it's a bug in TMPGEnc, or something in the PC that is causing it, but lately i've been having the same problem, the weird thing is, it happened to me using any encoder, not just TMPGEnc.

So I just Demux and Remux and the file gets back to the size it should be.

Quick look out the window dudes I think you`ll see some pigs flying past...........

[Sefy]

Naaa... not in this area... pigs are not kosher, but maybe we'll see some cows flying instead

[Zogg]

Unfortunately DVDcutter doesn't do MPEG2, only MPEG1, as best I can tell from their web page.

And Sefy and I aren't claiming to have some miracle to make files smaller than they should be. For some reason some files are a lot BIGGER (about 25%) than they should be after encoding, so a demux and remux just makes the file what it SHOULD have been. No magic.

[00Herb]

I run WinXP, AMD1600XP, hyundai 256mB DDR stick and have had this problem since running XP.

It doesnt affect anything though it is just annoying

TMPGEnc Software bug, definitely

[SatStorm]

Some editors are adding some kind of Padding when they cut mpeg 2...
mpeg2vcr is one of them
Most of the times, when I cut a DVB file, I end up with some huge ones. I simply "demux"/"remux" as SVCD with TMPGenc and those files return to there original size.
There were times, a file looked 550MB and turn 78MB after that proccess!
Must be a bug or an option in mpeg2vcr, which I don't know how to disable it...

I have the same problem with cutting in Tmpgenc ,but with the new version 2.56 mpeg 1 no probs .Mpeg 2 most of the time it crashes when trying to cut/join??

Now I´m using M2-edit pro, works every time, only thing is it bloats up the output eg a 800mb Mpeg jumps up to 1.1 gigs. With a demux/remux in tmpgenc all is ok again.

Maybe in the next couple of versions this is fixed in Tmpgenc.

Cheers

[Craig Tucker]

I also get this error message when cutting, but only about 50% of the time. It does not seem to effect the cutting process however. I only have 1 stick of 512mb ram, so that cannot be the problem. Seems that it is probrably a bug with TMPGEnc.

Craig