How about the latest release 9026? Please try it, Rex.
-
-
It also could be your video driver."Beer is living proof that God loves us and wants us to be happy."
- Benjamin Franklin 1706-1790Comment
-
-
Hi Greg. I updated my driver a couple of days ago to 314.07 and no change. It starts to encode, and quickly reaches around 13 MB/s, but when it gets around 10 percent in, it stops, and the MB/s slowly go down to 0.Originally posted by GregiBoy View Post
I'm not using my video card, but software, so I'm not sure if the driver would matter.Comment
-
Did you enable Light-recoding? Please uncheck it and try again.
What's more, how about copy from the original bluray disc? Please give a try and then feedback.Comment
-
Hi Terry I tried from the disc and a disc I've compressed before. I unchecked light-recoding and the same thing. I don't get why it starts to compress and at a pretty fast rate (13MB/s) and then just stops at around 10 percent, and it's every blu ray I try to compress. I've tried older versions of DVDFab and the same thing. I've tried using my graphics card and I've tried using my Sandy Bridge software and it's always the same result.Last edited by Rex; 02-21-2013, 05:23 PM.Comment
-
Hi Rex
You posted your burn log, you will need to post your internal log.
CBR929Even if it's a little thing, do something for those who have need of help, something for which you get no pay but the privilege of doing it.
Setting Up ImgBurn and DVDFab to work together
Tips for Posting DVDFab Logs in the ForumComment
-
Sorry.Comment
-
NULL DATA AT WORK:
I don't like fussy math so I pulled this out of the log file to look at.
You can't handle a value properly if you don't understand its nature. A common misconception is that a null value is simply an empty field or no value at all. That's not true. A null value indicates that the data is missing or unknown. Occasionally, a null value does mean that the data doesn't exist or isn't valid for that particular record, but the concepts aren't interchangeable so this may need looking into.
Comment
-
First off it's "fuzzy math", and secondly if one is making an attempt at being condescending, they should possess the intellect to pull it off.Originally posted by glenns View PostNULL DATA AT WORK:
I don't like fussy math so I pulled this out of the log file to look at.
You can't handle a value properly if you don't understand its nature. A common misconception is that a null value is simply an empty field or no value at all. That's not true. A null value indicates that the data is missing or unknown. Occasionally, a null value does mean that the data doesn't exist or isn't valid for that particular record, but the concepts aren't interchangeable so this may need looking into.
Last edited by Rex; 02-24-2013, 03:58 PM.Comment
-
Rex:Golly can you give a guy the rit of habeas corpus as I was trying to point out In your many log files you had this:
300m 15.72s: Warring : Null Data at Work and i don't see that in most log files so i took it out for the developers to look at.
Comment
-
SureOriginally posted by glenns View PostRex:Golly can you give a guy the rit of habeas corpus as I was trying to point out In your many log files you had this:
300m 15.72s: Warring : Null Data at Work and i don't see that in most log files so i took it out for the developers to look at.Comment
-
Rex:Have to tried going back in time with system restore to a date where Fab was working ?Comment
-
All your logs show you were using 9.0.2.6 have you tried 9.0.2.7?
Have you tried a older version of fab that worked well at compressions like 8.0.8.5 ?Last edited by glenns; 02-25-2013, 10:30 AM.Comment
-
Are you using bit defender by any chance?Comment
Comment