Announcement

Collapse
No announcement yet.

Possible bug

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Possible bug

    Testing the new cinivia work around and during the burn process the task time left is 00.00.00 but the %complete is still progressing.
    A minor flaw so far. If the copy doesn't work I'll post back later.
    Last edited by W&B; 01-08-2014, 10:50 PM.

    #2
    See another minor bug there.
    When path contains & it takes it as underline for next character.
    人生は贈り物であり、完全な喜びを経験する必要があります
    Life is a gift and should be experienced in full joy

    Comment


      #3
      Originally posted by Blazkowicz View Post
      See another minor bug there.
      When path contains & it takes it as underline for next character.
      I didn't notice that

      So far it's playing back no problem about an 1 hour and 10 minutes in (The Social Network). Also I set my PS3 to output thru the HDMI cable only so if it should kick in if detected.

      Comment


        #4
        Originally posted by W&B View Post
        Testing the new cinivia work around and during the burn process the task time left is 00.00.00 but the %complete is still progressing.
        A minor flaw so far. If the copy doesn't work I'll post back later.
        i got something like that in ver 68 could be a bug from there
        Attached Files
        For Win7 C:\Users\User Name\My Documents\DVDFab\Log
        or Vista C:\Users\User Name\Documents\DVDFab\Log
        or for XP C:\Documents and Settings\User Name\My Documents\DVDFab\Log
        Please use attachment button and attach your most recent, Internal and Burn log(s)and post right here.

        Comment


          #5
          Originally posted by DiabloZoe View Post
          i got something like that in ver 68 could be a bug from there
          Hi DiabloZoe
          That is a analyzing process,not begin ripping,so i think that's not a bug.
          Joe

          Comment


            #6
            Just got some time to look at my log for the VSO burn engine:

            2011-01-13 16:29:25 ---- ******************** Log session stop 13-Jan 16:29:25.994 PID 2476********************
            2011-01-13 16:29:11 Info WRITE SUCCESS: Disc written
            2011-01-13 16:29:11 Info Finalization Time 00:00:03 - Total completion time 01:07:43
            2011-01-13 16:29:07 Info Write finished in 01:07:39 - Finalization start here. Avg. burn rate 6.22
            2011-01-13 15:21:42 Info Lead-in burning time (mS) 14383
            2011-01-13 15:21:27 Info Write started 15546176 sectors to write
            2011-01-13 15:21:27 Info Writing speed requested x2.0, effective x2.0
            2011-01-13 15:21:27 Info Format completed
            2011-01-13 15:21:27 Info Available write speed: 2x
            2011-01-13 15:21:27 Info Media ID: MEI-T01-7D
            2011-01-13 15:21:27 Info Media type: BD-RE
            2011-01-13 15:21:27 Info DMA is not available on this bus type
            2011-01-13 15:21:27 Info Scanned files #885, folder #29 - total size 31832262471 b. (29.65 Gb.)
            2011-01-13 15:21:27 Info Inserted media type : BD-RE
            2011-01-13 15:21:27 Info Write started
            2011-01-13 15:21:09 Info Rewritable disc BD-RE inserted. Ready to erase and write
            2011-01-13 15:21:07 Info Compatible media types : DVD-R, DVD-RW Seq., DVD-RW RO, DVDRAM, DVD+R, DVD+RW, CD-R, CD-RW, DL DVD+R, DL DVD-R, Blu Ray-R Seq., Blu Ray-R Rnd., Blu Ray-RE
            2011-01-13 15:21:07 Info Drive has Serial ATA physical interface
            2011-01-13 15:21:07 Info New Drive selected : 3:1:0 - PIONEER BD-RW BDR-203 1.13 [D] (Ide)
            2011-01-13 15:21:07 Info WRITE SUCCESS: Disc written
            2011-01-13 15:21:07 Info Scanned files #885, folder #29 - total size 31832262471 b. (29.65 Gb.)
            2011-01-13 15:21:07 Info Inserted media type : Hard Disc
            2011-01-13 15:21:07 Info .fso Image file will contain only the filesystem entries.
            2011-01-13 15:21:06 Info Write started
            2011-01-13 15:21:05 Info New ISO path selected : C:\Users\W&B\AppData\Local\Temp\244fa7\min.fso
            2011-01-13 15:20:56 Info Rewritable disc BD-RE inserted. Ready to erase and write
            2011-01-13 15:20:13 Info Compatible media types : DVD-R, DVD-RW Seq., DVD-RW RO, DVDRAM, DVD+R, DVD+RW, CD-R, CD-RW, DL DVD+R, DL DVD-R, Blu Ray-R Seq., Blu Ray-R Rnd., Blu Ray-RE
            2011-01-13 15:20:13 Info Drive has Serial ATA physical interface
            2011-01-13 15:20:13 Info New Drive selected : 3:1:0 - PIONEER BD-RW BDR-203 1.13 [D] (Ide)
            2011-01-13 15:20:08 Info Compatible media types : DVD-R, DVD-RW Seq., DVD-RW RO, DVDRAM, DVD+R, DVD+RW, CD-R, CD-RW, DL DVD+R, DL DVD-R, Blu Ray-R Seq., Blu Ray-R Rnd., Blu Ray-RE
            2011-01-13 15:20:08 Info Drive has Serial ATA physical interface
            2011-01-13 15:20:08 Info New Drive selected : 3:1:0 - PIONEER BD-RW BDR-203 1.13 [D] (Ide)
            2011-01-13 15:20:03 Info Compatible media types : DVD-R, DVD-RW Seq., DVD-RW RO, DVDRAM, DVD+R, DVD+RW, CD-R, CD-RW, DL DVD+R, DL DVD-R, Blu Ray-R Seq., Blu Ray-R Rnd., Blu Ray-RE
            2011-01-13 15:20:03 Info Drive has Serial ATA physical interface
            2011-01-13 15:20:03 Info New Drive selected : 3:1:0 - PIONEER BD-RW BDR-203 1.13 [D] (Ide)
            2011-01-13 14:50:48 Info Disc (BD-ROM) not empty.
            2011-01-13 14:50:46 Info Compatible media types : DVD-R, DVD-RW Seq., DVD-RW RO, DVDRAM, DVD+R, DVD+RW, CD-R, CD-RW, DL DVD+R, DL DVD-R, Blu Ray-R Seq., Blu Ray-R Rnd., Blu Ray-RE
            2011-01-13 14:50:46 Info Drive has Serial ATA physical interface
            2011-01-13 14:50:46 Info New Drive selected : 3:1:0 - PIONEER BD-RW BDR-203 1.13 [D] (Ide)
            2011-01-13 14:49:58 Info Current Drive selected : 3:1:0 - PIONEER BD-RW BDR-203 1.13 [D] (Ide)
            2011-01-13 14:49:58 Info Using Advanced SPTI interface
            2011-01-13 14:49:58 Info System default language : English (United States)
            2011-01-13 14:49:58 Info User default language : English (United States)
            2011-01-13 14:49:58 Info DLL Version : 4.0.15.480
            2011-01-13 14:49:58 Info DLL : C:\Program Files (x86)\DVDFab 8\vso_hwe.dll
            2011-01-13 14:49:58 Info Version : 8, 0, 7, 0
            2011-01-13 14:49:58 Info ExeName : C:\Program Files (x86)\DVDFab 8\DVDFab.exe
            2011-01-13 14:49:58 Info OS : Microsoft Windows 7 Ultimate (Build 7600)
            2011-01-13 14:49:58 ---- ******************** Log session start 13-Jan 14:49:58.283 PID 2476********************

            I checked the MID with ImgBurn and it shows with v.2550 MEI-T01-001 and it used to show with v.2540 and previous versions that I can remember MEI-T01-01 :
            (I read the ImgBurn changelog and understand that the MID may change so I suggest everyone that uses the AWS feature make sure it is still set correctly, not a big deal).

            I'm wonder if it's a bug with VSO or does it just read the MID differently, obviously? The log itself looks like it was glitching (lack of a better analogy)

            I watched the disc completely thru and no cinavia popup or muted audio, just thought I'd report back for anyone curious.

            EDIT: correction, ImgBurn changelog may show more FIRMWARE info not MID as I previously posted. But the MID has changed in any case.
            Last edited by W&B; 01-14-2011, 03:05 AM. Reason: corrected info

            Comment


              #7
              Hi W&B
              Why does the log also show
              2011-01-13 15:21:27 Info Writing speed requested x2.0, effective x2.0
              2011-01-13 16:29:07 Info Write finished in 01:07:39 - Finalization start here. Avg. burn rate 6.22
              thats strange
              CBR929
              Even 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 Forum

              Comment


                #8
                I noticed that also but have no clue why, all I can guess is VSO lacks drive control unlike ImgBurn...also I corrected my post, see the edit. It's kind of odd to me and I've never seen this before because the reported MID's between VSO and ImgBurn have always matched up perfectly that I can remember.

                Comment


                  #9
                  Originally posted by W&B View Post
                  I noticed that also but have no clue why, all I can guess is VSO lacks drive control unlike ImgBurn...also I corrected my post, see the edit. It's kind of odd to me and I've never seen this before because the reported MID's between VSO and ImgBurn have always matched up perfectly that I can remember.
                  Maybe it is a bug in the VSO burn engine as I have seen this on more that one occasion., where the burn rate was higher than the requested and could cause playback issues if burnt to fast.
                  CBR929
                  Even 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 Forum

                  Comment


                    #10
                    Yep same here, maybe team Fab should contact VSO since they are the license holders? It's not a big deal as I mainly use ImgBurn but if it helps to improve the program (DVDFab and VSO).
                    Another thought is that VSO should pop over here and provide some support for their burn engine LOL

                    Comment


                      #11
                      Originally posted by W&B View Post
                      Yep same here, maybe team Fab should contact VSO since they are the license holders? It's not a big deal as I mainly use ImgBurn but if it helps to improve the program (DVDFab and VSO).
                      Another thought is that VSO should pop over here and provide some support for their burn engine LOL
                      That would be real nice, but I do not foresee that happening.
                      Good night my friend
                      CBR929
                      Even 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 Forum

                      Comment


                        #12
                        I made a backup and compressed to a 25GB BD-RE disc using the normal backup steps just to make sure cinavia would kick in on my ps3 with firmware v.3.50, it did lol

                        Before it did I noticed the a/v was out of sync, I'll set my codec options to all software for any future backups until this is resolved.

                        DVDFab 8.0.7.0 (2011/01/13 17:08:12)
                        0m 01.00s: option dvd2dvd 1 dvd2mobile 1 bluray2bluray 1 bd2mobile 1 bd23d 1 bd2dvd 1 file2mobile 1 filemover 1
                        0m 15.68s: got bdmv
                        0m 15.76s: got extended bdinfo
                        1m 50.61s: Blu-ray Copy: Full Disc
                        1m 50.61s: Source: C:\Users\W&B\Documents\DVDFab\FullDisc\THE_SOCIAL_ NETWORK\BDMV\
                        1m 50.61s: SourceSize: 30352 MB
                        1m 50.61s: RemoveHDAudio: 0
                        1m 50.61s: ProtectedDisc: 0
                        1m 50.61s: OutputTarget: BD25
                        1m 50.61s: OutputVideo: 1080p/i
                        1m 51.98s: Video reencode bitrate (8716 kbps)
                        1m 51.98s: compress begin: Blu-ray groups clips(00000.m2ts), playtime(14431 ms), size(24 MB)
                        1m 52.00s: processing source(00000.m2ts)
                        1m 52.00s: try to use gpu acceleration(1) for video decoding
                        1m 53.14s: h264_encode: encode param profile(2) level(41) bitrate(8716)
                        2m 18.20s: group(00000.m2ts ) playtime(14431 ms) source(24 MB) request(17 MB) real(13 MB) bitrate(8716 kbps)
                        2m 18.20s: compress finished: groups request(17 MB, 17 MB) real(13 MB) average_bitrate(8716 kbps)
                        2m 20.34s: Video reencode bitrate (10640 kbps)
                        2m 20.34s: compress begin: Blu-ray groups clips(00081.m2ts), playtime(60060 ms), size(112 MB)
                        2m 20.36s: processing source(00081.m2ts)
                        2m 20.36s: try to use gpu acceleration(1) for video decoding
                        2m 21.37s: h264_encode: encode param profile(2) level(41) bitrate(10640)
                        2m 58.46s: group(00081.m2ts ) playtime(60060 ms) source(112 MB) request(80 MB) real(14 MB) bitrate(10640 kbps)
                        2m 58.48s: compress finished: groups request(80 MB, 80 MB) real(14 MB) average_bitrate(10640 kbps)
                        3m 00.40s: Video reencode bitrate (16086 kbps)
                        3m 00.40s: compress begin: Blu-ray groups clips(00101.m2ts), playtime(42208 ms), size(119 MB)
                        3m 00.42s: processing source(00101.m2ts)
                        3m 00.42s: try to use gpu acceleration(1) for video decoding
                        3m 01.45s: h264_encode: encode param profile(2) level(41) bitrate(16086)
                        3m 39.78s: group(00101.m2ts ) playtime(42208 ms) source(119 MB) request(86 MB) real(64 MB) bitrate(16086 kbps)
                        3m 39.79s: compress finished: groups request(86 MB, 86 MB) real(64 MB) average_bitrate(16086 kbps)
                        3m 40.48s: Video reencode bitrate (16276 kbps)
                        3m 40.50s: compress begin: Blu-ray groups clips(00104.m2ts), playtime(42208 ms), size(120 MB)
                        3m 40.51s: processing source(00104.m2ts)
                        3m 40.51s: try to use gpu acceleration(1) for video decoding
                        3m 41.54s: h264_encode: encode param profile(2) level(41) bitrate(16276)
                        4m 19.82s: group(00104.m2ts ) playtime(42208 ms) source(120 MB) request(87 MB) real(64 MB) bitrate(16276 kbps)
                        4m 19.84s: compress finished: groups request(87 MB, 87 MB) real(64 MB) average_bitrate(16276 kbps)
                        4m 20.57s: Video reencode bitrate (18667 kbps)
                        4m 20.57s: compress begin: Blu-ray groups clips(00011.m2ts), playtime(7227220 ms), size(29217 MB)
                        4m 20.61s: processing source(00011.m2ts)
                        4m 20.62s: CoreAVC for video decoding enabled
                        4m 21.75s: h264_encode: encode param profile(2) level(41) bitrate(18667)
                        60m 15.57s: group(00011.m2ts ) playtime(7227220 ms) source(29217 MB) request(22713 MB) real(22680 MB) bitrate(18667 kbps)
                        60m 15.61s: compress finished: groups request(22713 MB, 22713 MB) real(22680 MB) average_bitrate(18667 kbps)

                        Comment


                          #13
                          I checked the MID with ImgBurn and it shows with v.2550 MEI-T01-001 and it used to show with v.2540 and previous versions that I can remember MEI-T01-01 :
                          (I read the ImgBurn changelog and understand that the MID may change so I suggest everyone that uses the AWS feature make sure it is still set correctly, not a big deal).
                          There's no real hard and fast rule on how that last bit should be written, it's just a number between 0 and 255.

                          I saw that the firmware in some drives (according to MCSE) displayed it using 3 digits rather than 2 - which makes sense because 255 doesn't fit in 2! - so I changed it.

                          But I changed it back in 2.5.3.0, not in the most recent one.

                          At the time, I totally overlooked the issue with configured AWS data for those discs then being incorrect - sorry about that.

                          Comment


                            #14
                            Originally posted by LIGHTNING UK! View Post
                            There's no real hard and fast rule on how that last bit should be written, it's just a number between 0 and 255.

                            I saw that the firmware in some drives (according to MCSE) displayed it using 3 digits rather than 2 - which makes sense because 255 doesn't fit in 2! - so I changed it.

                            But I changed it back in 2.5.3.0, not in the most recent one.

                            At the time, I totally overlooked the issue with configured AWS data for those discs then being incorrect - sorry about that.
                            Thanks for coming here to explain the logic of it all and no need to be sorry about that.
                            Thankyou for the hard work you put in to it and again thanks for taking the time for the further explanation, not many devs will stray from their home forum and do that

                            Comment


                              #15
                              Originally posted by W&B View Post
                              Thanks for coming here to explain the logic of it all and no need to be sorry about that.
                              Thankyou for the hard work you put in to it and again thanks for taking the time for the further explanation, not many devs will stray from their home forum and do that
                              I agree, it is nice to see developers chime in if we are using their product and supporting it ,even if some the members we suggest to use ImgBurn make a donation it's better than nothing.
                              Thanks LIGHTNING UK! for a great product
                              CBR929
                              Even 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 Forum

                              Comment

                              Working...
                              X