BBMPEG Error...

[mguru]

First time I have ever run acrossed this error message in BBMPEG.

"Could not find user data at I-Frame XXXX in file: XXXXXXXXXX"

It happens after the 3rd of 4 segments right at the end of the Scan Offsets task.

My disk space is fine. My m2v was encoded normally with TMPG, and plays fine with mediaplayer. I also tried changing my Forced Data Rate and cut size to see if that fixed it...it didn't. Anyone know what is going on?

mGuru

[djc]

Originally posted by mguru
First time I have ever run acrossed this error message in BBMPEG.

"Could not find user data at I-Frame XXXX in file: XXXXXXXXXX"

It happens after the 3rd of 4 segments right at the end of the Scan Offsets task.

My disk space is fine. My m2v was encoded normally with TMPG, and plays fine with mediaplayer. I also tried changing my Forced Data Rate and cut size to see if that fixed it...it didn't. Anyone know what is going on?

mGuru


Hello,

All TMPG versions after .130 crash BBMPEG with the very same error. It would be very nice if someone could tell us why this happen. Is that a problem of TMPG or BBMPEG ?


Thanks

Djc

[mguru]

Interesting. I have used bbmpeg for well over a year with tmpg and this is the first time I got this error. I guess it is only in extraordinary circumstances. I ended up just fooling around with the start/stop second options with bbmpeg and finally got my movie segmented. But it was a major pain in the @ss to have to deal with that error.......thanks for responding!

mGuru

[djc]

Originally posted by mguru
Interesting. I have used bbmpeg for well over a year with tmpg and this is the first time I got this error. I guess it is only in extraordinary circumstances. I ended up just fooling around with the start/stop second options with bbmpeg and finally got my movie segmented. But it was a major pain in the @ss to have to deal with that error.......thanks for responding!

mGuru


Hello,

I'm been using TMPG for the last 6 months or so, since CCE is not respecting the low bitrate settings. I never had this problem. Now, i have tried to upgrade to the latest TMPG encoder and i ALWAYS have this error. So i switch back the .130 version.

Djc

[djc]

Originally posted by mguru
First time I have ever run acrossed this error message in BBMPEG.

"Could not find user data at I-Frame XXXX in file: XXXXXXXXXX"

It happens after the 3rd of 4 segments right at the end of the Scan Offsets task.

My disk space is fine. My m2v was encoded normally with TMPG, and plays fine with mediaplayer. I also tried changing my Forced Data Rate and cut size to see if that fixed it...it didn't. Anyone know what is going on?

mGuru

Hello,

Do you have the "padding" option enabled ?

I unchecked that option and all versions of TMPG work very well and i don't get the error you write above.

I hope that helps



Djc

[mguru]

Thanks! I'll try that option and see if it works.

mGuru

[Plant_Guy]

I tried your suggestion of removing the padding option, and that did not work. I also reset my GOP from Kwag's values back to the standard, and that did not work. Changing the audio values did not change anything either. Could someone please help, b/c DVD2SVCD is useless for me if I cannot solve this issue.

TomG. - aka Plant_Guy

[KClout]

I'm a newbie... I was having the same problem until I set my bitrates back to the default. It seemed to stop the problem for me.

[Plant_Guy]

If I cannot set the bitrates, then what good is it? The flexibility of the software is in the bitrate settings. Are you sure the problem was solved? In another thread, one of the moderators said that he solved the problem by unchecking the "scan for SVCD offsets" option in advanced settings under bbMPEG tab. To do this, you must have DVD2SVCD set to advanced mode, which is under the misc. tab. I will try this when I get home tonight.

TomG. - aka Plant_Guy

[KClout]

My problem started when I tried to get Harry Potter on two discs. I had to lower the bitrate quite a bit to fit it. Thats when it started giving me that error. After a week of repeated failures, I reset the bitrates. The problem went away.

[KClout]

Oh... and a response to the bitrates... I still change them when necessary, the software seems to freak out when I change them too much.

[Plant_Guy]

Try my suggestion above and let me know if it is a success with you. I will do the same tonight.

TomG. - aka Plant_Guy

[djc]

Originally posted by Plant_Guy
I tried your suggestion of removing the padding option, and that did not work. I also reset my GOP from Kwag's values back to the standard, and that did not work. Changing the audio values did not change anything either. Could someone please help, b/c DVD2SVCD is useless for me if I cannot solve this issue.

TomG. - aka Plant_Guy

Hello.

Just finished "Domestic Disturbance" with John Travolta. With Padding enabled i had bbmpeg crashing, with Padding off everything worked fine.

The only change i have in the default bitrate is the min set to 800 because of my Pioneer 444,


Djc

[Plant_Guy]

With Padding enabled i had bbmpeg crashing, with Padding off everything worked fine.

Djc,

I am wondering if we are talking about the same error. I am talking about the problem that occurrs when bbMPEG is doing the scan for SVCD offsets. Disable the scan for SVCD offsets option, and everything works just fine. That solution works. Now, I do not know what that option does, so I cannot say what the consequences are of turning it off, but my "Beautiful Mind" rip plays beautifully :D. Leave the padding option on, and follow my advice. Without the padding, on certain scenes with little or no motion, some players will stutter, so don't use that solution, it will only bring you grief (probably when you are sitting in front of the TV to enjoy a movie you ripped).

TomG. - aka Plant_Guy

[avdmb]

@djc, in case your issues come from struggling with low bitrate to solve blocky video on your Pioneer DV-444, definitely switch to I-Author muxer and you will never again face problems, even with CCE and min bitrate 300. Search this forum with "I-Author" and "Pioneer".

[adam]

The SVCD scan offsets aid in maintaining sync in your svcd, especially when seeking. Though they are not required for compliance I do believe that there are a number of dvd players which will have problems maintaining sync without them, again probably most apparant during seeking. I have noticed that on my apex if I don't use them then it takes a good 4 secs before the audio kicks in after I ff/rw or jump to a new chapter or track. If your svcd plays ok without them, then you probably don't need them.

I have gotten this error once before with TMPGenc and numerous times with CCE. Still its pretty rare and seems to be totally random. Every single time I have gotten the error I simply re-encoded using the exact same settings and remultiplexed with the exact same settings and the error went away so I do not think this error has anything to do with how you encode per se. I'm wondering if this is maybe a hardware problem, I know that the checksum error in cce is more prominent on Via chipsets and is basically caused because a cache is not cleared fast enough (something like that.) Perhaps a hardware issue is causing us to have corrupt mpg streams. I wonder how many of us here have Via chipsets, I do for one. Also I'm using Win2k.

[djc]

Originally posted by avdmb
@djc, in case your issues come from struggling with low bitrate to solve blocky video on your Pioneer DV-444, definitely switch to I-Author muxer and you will never again face problems, even with CCE and min bitrate 300. Search this forum with "I-Author" and "Pioneer".


Hello.

After having a VERY hard time to get I-Author, i did two SVCDs during the weekend, with TMENG and CCE. Both with the default bitrate setings (even 300 low).

The results played VERY well in my Pioneer 444 even on low bitrate scenes. But i can't add intro and changecd pictures.

I think everybody with those problems should try that!

Thanks for the help, since it is not always possible to find the right answer in the high volume forums.


Djc

[djc]

Originally posted by adam

I have gotten this error once before with TMPGenc and numerous times with CCE. Still its pretty rare and seems to be totally random. Every single time I have gotten the error I simply re-encoded using the exact same settings and remultiplexed with the exact same settings and the error went away so I do not think this error has anything to do with how you encode per se. I'm wondering if this is maybe a hardware problem, I know that the checksum error in cce is more prominent on Via chipsets and is basically caused because a cache is not cleared fast enough (something like that.) Perhaps a hardware issue is causing us to have corrupt mpg streams. I wonder how many of us here have Via chipsets, I do for one. Also I'm using Win2k.

I have Windows 2000 Pro and Via (athlon 1700+). I have this error only with TMPGenc and never with CCE 2.5 (CCE version after 2.5 don't work in my system). I have run the memtest and everything with 100% success (but i have to use the default bios settings to be ok).

Djc

[Plant_Guy]

Every time I have done the encoding, the error stayed. Redoing the process only resulted in a repetition of the problem exactly as before, the problem did not go away. Also, every movie started doing the same thing, so the situation was intolerable after a while. Without the offsets, everything is OK.

TomG. - aka Plant_Guy

[mguru]

ok, here's the result of my tests...the Padding option under the VBR Bitrate selection window in TMPG seems to be causing this error. It seems to be creating havoc with ANY multiplexor I try, not just bbmpeg. I recenty started checking it for encodes, so I guess that is why I "coincidently" recently started getting this error. I'll make a note of it in the TMPG BB.

Now, how to solve it. First is to re-encode the video without padding. Then try to re-multi with bbmpeg. Should work perfectly.

Second, if you want to try to salvage what you have, you can try to see if VCD-Easy will take it. My experience is that this causes the mysterious "shortened bin" problem that many people are having with VCD-Easy; ie. it will only read up to the error packet causing only a fraction of the mpeg file to be recognized. I found a quick fix for this by using VCDGear mpeg->mpeg with fix option. This corrects the packet errors, and from what I can tell does not harm the stream at all. Then the mpeg segment has scan offsets and can be authored and burned normally.

Third, if the bbmpeg error comes on a "middle" segment and halts with the error, you still have to multiplex the remaining segments. Do this with the time start and stop functions. It'll take a little investigation but it's faster than re-encoding.

Lemme know if this helps.

mGuru

[Plant_Guy]

mguru,

I tried encoding w/out the padding option, and still get the error.

TomG. - aka Plant_Guy

[mguru]

hmmmmm...that is not what I have had happen on my sys. Taking off padding clears all errors up for me. Just curious: what is your minimum bitrate? I seem to keep mine between 300 and 700 depending on the quality I want. Maybe its not just padding, but also a bitrate problem. Of course this is only speculation as I don't really know specifics about TMPG's padding.

mGuru

[Plant_Guy]

My minimum bitrate is 500. sometimes I like to set it to 1000.

TomG. - aka Plant_Guy

[gizmau]

allready tried to multiplex using mplex (mjpegtools)? dont think so...

[dave268]

I'm admittedly not too knowledgeable, but for what it's woth, using TMPGEnc to create SVCD's, I've done about 30 and got the "Could not find User Data at I-Frame..." error about 3 times. The last time I got it I just clicked the couple of OK buttons and the SVCD's created were fine anyway - I saw nothing weird about them. It sucks that the error insists that you click the OK buttons thereby hanging the process. At least it's near the end so it's only about 30 to 60 min more to complete the process. It would be better if the error was reported at the end of the log file since aborting at the point of the error is of minimal advantage since you're about 95 % done anyway.

The bitrate stuff had previously been quite bewildering to me so I just experimented a lot.I kindof get the feeling that the error was the consequence of going outside of standard SVCD bitrates.

[hawk1309]

Hi,

I've seen this error on occasions when I'm doing DIVX to SVCD conversions using DVD2SVCD.

What works for me is clicking the OK button on the error screen and then clicking OK button inside BBMPEG. The process falls back to DVD2SVCD and you should see the progress bar running in the LOG tab, could take some time before it starts just wait. After that all should continue as normal.

I've been looking thru the source code a little and think it's an error inside BBMpeg somewhere. The only problem that I had to do the same conversion twice with the same encoder ( TMPGENC latest ) and seetings, once it produced the error and the other time it didn't, so it is not really reproducable everytime.

I'm now working on a patched version og BBMpeg which doesn't popup the error window but just displays the error in the info field of BBMpeg and continues the normal process. Furthermore I'm am putting in log output to file.

Regards,

Hawk

[Kryzzle]

@hawk1309:

Made any progress lately? I am running out of idea already...:scared:

[hawk1309]

I haven't had time to look for any errors in the code( holliday), but made a patched version as said. The only issue is now that it creates a logfile in the BBMpeg directory instead of the project directory. I'm thinking about a solution for this as well as timestamps inside the logfile. By the way I won't be able to supply my version to you because DVD2SVCD won't support it. However I could give you the changes I made to the sourcecode, so you could build your own version. If I find anything I will come back.

Regards,

Hawk