Cannot Find User Data at Iframe 5433 in file temp00.mpg
 

Keep getting this error when muxing 704x480 SVCD with BBMPEG.

The file will mux with TMPGEnc, but how do I determine the cut point for 2 disks?

Does anyone know why this error is occuring?

You can mux by size or by time in BBMpeg's options.
If your total muxed video is say 1,400MB, just set the cut point to 705MB or so, and BBMpeg will mux two mpeg files. Just be careful that you don't specify a size smaller than half, because then you'll get three files :!:

-kwag

You didn't really see the problem Kwag : bbmpeg crashes on this case !

And it does the same for me so often that I do not do any muxing with it now. But as I do not do 2 discs encoding, I do not have the problem of nicksteel.
(and mplex do not work either !)

I see :roll:
Then it must be an MPEG-2 related problem, because I've never had a single failure when muxing MPEG-1 encodes, as VCD or as SVCD (header trick ) :!:

-kwag

I never encode in MPEG2 !
And that is a problem of SVCD as it appears when bbmpeg does the svcd scan offset;

Yeah, same error in mplex.

I've even muxed successfully in TMPGEnc, demuxed with TMPGEnc and remuxed with BBMPEG. Same error.


I am trying to cut with TMPGEnc, although it is hard to get to the file's midsize point. Can be done by several trys, though. :?: Is this in any way related to unchecking scene detection in TMPGEnc?

:?: Also, is there another mux program I can try that can split onto multiple discs without "trial and error" splitting with TMPGEnc?

Solution
 

Separate into 2 d2v files in DVD2AVI. Process separately and mux separately with TMPGEnc. End of problem.

Jorel, Kwag, anyone...........
 

:?: Is it necessary to check "Scan SVCD Offsets" in BBMPEG for SVCD?

The Iframe error only occurs when this is checked. This is the error that occurs in BBMPEG and mplex on some SVCD films. The only thing that muxes these seems to be TMPGEnc, which will not file split during mux, and which will only file split in MPEG_Tools on time, necessitating many trial and error runs to get desired file sizes.

I wish someone would develop a mpeg2 file splitter based upon file size rather than time, similiar to BBMPEG. I've tried everything I I can find to no avail. Mpeg-vcr also splits on time only.

The problem is this:

If You enter a name for the final MPG-file and You want to splitt the movie for 2 or more discs bbMpeg will crash when it starts the second part.

It only tells you that it didn't find the first part.
If instead don't enter a filename at 'PS' it will save Your movie in the same folder as Your source as temp00.mpg, temp01.mpg and so on.

If You knew this You'll never has this problem, but it is still a bug of the program...

This isn't the problem, as I never enter a PS name and always let it generate temp00.mpg, etc. The Iframe error only occurs with some files. I am muxing 704x480 svcds from the KDVDx3-MPEG-2-NTSCFilm.mcf template.

:?: Is it necessary to check "Scan SVCD Offsets" in BBMPEG for SVCD?

I found an old posting by Maudib that stated that this was not necessary. Muxed with it unchecked and problem went away. Everything played ok.

no nick,don't need to check!
i never use it for my skvcds(480x480).
see details using bbmpeg x tmpgenc
where tmpgenc give me problems:

http://www.kvcd.net/forum/viewtopic....ghlight=#44336

the perfect result was using bbmpeg:
svcd
uncheck "add svcd scan offsets"
uncheck "align sequence readers"
adjust "forced mux rate(in 50 byte/sec units)" to ZERO (0)!

:wink:

I have the problem:

CouldNot find user data at I-frame 3007 in file temp00.mpg

Is working for me now :lol: :lol: :lol: :lol:

Thanks Jorel

If you do'nt add the scan offset while muxing, they will be added afterwards by the tool taht make the SVCD.
And if you use Nero for that, that will add up to 100 MB to your video :!:

Be carrefull so...

Mamy Thanks

I will use it, only if give error :D

strange Phil,it never happen with me. the muxed file always have few mbs more than audio/video size....round 5 or 6 MB after mux!
always got :arrow: less size than using scan offset after mux and i build vcdeasy image with chapters and burn in nero or any other burn iso file prog!

I said that the problem is due to the programm used to MAKE the SVCD, not to burn it. Here you are using VCDEasy to make the SVCD and not Nero.
If you use Nero for both steps (creating the image AND burning it) then you can have a big surprise.

no surprises Phil, just the same cos without vcdeasy the file is just a few small and i never had problem! i only mux the audio and video in bbmpeg, clicking in svcd,unchecking "add svcd scan offsets" and "aline sequence headers", then adjust "forced mux reate" to zero,load the video and audio,mux.
get the file, load in nero, build little menus, burn and all is ok! :wink:

:arrow: see the example that i'm doing now (not for cdr 80 minutes of course):
video: 1,02GB (1.074.224Kb) + audio: 165Mb (169.781KB) = 1,185GB (1.244.005kb) before mux
1,20GB (1.263.510Kb) :arrow: after mux using that parameters in bbmpeg!

only more 15MB for that big file!

I never ay this is the case any time.
In fact, taht is a BIG coincidence ! But look at that thread :

http://www.kvcd.net/forum/viewtopic....022&highlight=

I don't know yet if that is the same problem, but chance are big that it is !
:-)

That's also what I have 99% of the time. But one day... boooom... 100 MB more ! And I'm not the only one :-)

Note : previous release of vcdeasy showed a warning "this video will be pad on the fly" or something like this to warn you that you should have problems in this case. Last release do not show it anymopre, perhaps they modified something in the tool ? I don't know.

oh yes Phil and you did the right answer there cos he got that error after do a wrong mux!
maybe using wrong adjusts in tmpgenc mpegtools --> simple multiplex-->type..(wrong type choosed give that error!:wink:
if you remember was you that show me how to right use mpegtools in tmpgenc choosing the right "type"! :)
in my first encode i did the same error and muaddib show me how to do exact like i posted and never more had problems with BBmpeg.

sometimes i get that advices from vcdeasy but after tests i don't found something wrong and continue...then i burn and all is ok.
maybe the vcdeasy developer only remove that advice in news versions,but the program still working in the same way. :?