Jump to content

Ch3vr0n

Members
  • Content Count

    324
  • Joined

  • Last visited

Posts posted by Ch3vr0n


  1. You're using M-disc bd-r's aren't you?

     

    VERBAT-IMu-000

     

    I'm guessing the drive(s) do(es)n't like them very much.

     

    The bh16ns40 should read/burn them, but other drives not. M-disc support requires drive's specifically supporting them. They're not your average BD-R.

     

    Sent from my Nexus 6P with Tapatalk


  2. No longer able to install is bollocks. You've got multiple options

     

    1. Temp disable internet access. No internet? The opencandy dll can't load offers

    2. LOOK at the screens, don't go 'next next next', some offers ! LOOK unable to deselect but they're not

    3. Launch the installer with the /nocandy switch

    4. Extract the setup with something like 7zip, WinRAR,... and pull the exe. You won't have any desktop icon, or start menu entries by default but the program itself will work just fine.

     

    And probably a few more

     

    Sent from my Nexus 7 with Tapatalk


  3. I closed it and not going to waste time trying again.

     

    I just tried to see if it could read a BD data disk that was burnt a couple of months ago. The disc is seen as empty! Tried it in my bluray player (the one connected to the TV), and it works OK and I can see the files.

     

    I suspect failed Bluray laser. I might try it on another system at some point.

    Nobody's asking you to try again. And I doubt it's a faulty laser. Just go to the 'extra' menu I think it is, then 'imgburn log' to access the burn log. Copy and paste the FULL SECTION of the relevant burn. Without it, we can't help you.

     

    Sent from my Nexus 6P with Tapatalk


  4. OK, that was one attempt which threw that error. The 6x verbatim throws capability errors but that went away when I set Imgburn to 4x. Imgburn then burns to disk for 20-25 minutes, tells me it's successful, cycles tray, then tells me there's a mismatch when it tries to verify. It turns out that nothing has been burnt to the disk and that it's recognised as empty. I agree that the Phillips discs are cheap, but it was just another media I tried.

     

    Regarding Sony, that drive is immortal, so b-grade or not it hasn't let me down (10 years old and it only cost me about £12).

     

    I just tried again:

    I 13:28:03 Operation Successfully Completed! - Duration: 00:23:32

    I 13:28:03 Average Write Rate: 17,307 KiB/s (3.9x) - Maximum Write Rate: 17,685 KiB/s (4.0x)

    I 13:28:03 Cycling Tray before Verify...

    W 13:28:20 Waiting for device to become ready...

    I 13:28:49 Device Ready!

    E 13:28:49 CompareImageFileLayouts Failed! - Session Count Not Equal (1/0)

    E 13:28:49 Verify Failed! - Reason: Layouts do not match.

    Disk is still blank with no colouration on the disk to indicate that anything was burnt.

    FULL log please, not just the small verify part. The important stuff you're excluding.

     

    Sent from my Nexus 6P with Tapatalk


  5. Invalid address for write has nothing to do with the drive. The drive probably works just fine, the culprit is more likely cheap crappy blanks you're using.

     

    What type of discs are you using (if you know where to look, what's the MID?) That it burns DVD's fine is normal. Different type of discs, and uses a different laser.

     

    Philips is cheap crap, Sony is B-GRADE. What's the type of verbatim? If the MID is CMC (store bought discs) you've got the cheap version (life series), and you need to buy the proper ones online with the VERBAT-IM.-000 ones.

     

    Sent from my Nexus 6P with Tapatalk


  6. I have a file that's just a little too big for a cd so I have to use a dvd. The wav file will only burn to another wav file rather than to an audio format. I tried Nero burn and imgburn. Imgburn is just too cryptic. What's the solution I'm missing? I tried windows media player too.

    You're not making any sense

     

    WAV IS an audio format

    There's no such thing as an audio DVD

    You can't 'burn' wav to another wav, wav is an audio file extension type like mp3

     

    Imgburn only burns what you give it. If it's too big to fit a CD, then recode it like mp3 or lower the bitrate so it will fit

     

    Sent from my Nexus 6P with Tapatalk


  7. I haven't found single layer ones either, but thanks to a connection I made on the RedFox forums I did pick up 2 boxes of the legit DL versions. Same mid, I've been looking for help for years. Although I'd still like me a few boxes of the SL versions too, DL holds SL too.

     

    Sent from my Nexus 6P with Tapatalk


  8. Imgburn only burns what you feed it. Other than that it has ZERO impact on playback behavior of any kind.

     

    Try playing the source you used to burn, in a licensed software player such as PowerDVD. It'll probably fail too.

     

    Sent from my Nexus 6P with Tapatalk


  9. I just look thru the 100 page "Guide" from TEN years ago and since the GUI has changed considerably it's of little use. Running all of that in one single web page was ridiculous in the 1st place. It's not rreadable and I'm surely not printing out 200 pages (including the 100 or so additional settings pages.)

     

    All I want to do is burn some single files and I only see that Disc layout Editor after I click on 'Source'.

    What I don't see ins what to do after you choose the files you want. If I close the Editor popup it appears nothing was saved.

     

    I see where you can save the 'job', but this is a one time deal, I don't need/want to save it, just burn it. If I go into 'Write' mode, and open up the browser, these mp4 files that I choose apparently aren't supported as what seems most other video & audio files aren't either.

    Write mode is for iso's. You need build mode for mp4 etc

     

    Keep in mind your playback device will need to support playing back those file types from disc. Imgburn will NOT convert them to DVD format

     

    Sent from my Nexus 6P with Tapatalk


  10.  

     

    I have problems at burns from blurays

     

    logfile is:

    ; //****************************************\\

    ; ImgBurn Version 2.4.4.0 - Log

    ; Sonntag, 31 Dezember 2017, 17:15:05

    ; \\****************************************//

    ;

    ;

    I 16:45:59 ImgBurn Version 2.4.4.0 started!

    I 16:45:59 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1)

    I 16:45:59 Total Physical Memory: 8.364.208 KB - Available: 4.782.628 KB

    I 16:46:00 Initialising SPTI...

    I 16:46:00 Searching for SCSI / ATAPI devices...

    I 16:46:00 Found 1 BD-RE!

    I 16:48:12 Operation Started!

    I 16:48:12 Building Image Tree...

    I 16:48:15 Corrected file system selection for Blu-ray Video disc.

    I 16:48:15 Corrected UDF revision selection for Blu-ray Video disc.

    I 16:48:17 Calculating Totals...

    I 16:48:17 Preparing Image...

    I 16:48:17 Contents: 24 Files, 9 Folders

    I 16:48:17 Content Type: BD Video

    I 16:48:17 File System(s): UDF (2.50)

    I 16:48:17 Volume Label: Boston - 2014-10-02 - Nippon Budokan, Tokyo, Japan (BluRay)

    I 16:48:17 Size: 23.709.979.928 bytes

    I 16:48:17 Sectors: 11.577.154

    I 16:48:17 Image Size: 23.711.055.872 bytes

    I 16:48:17 Image Sectors: 11.577.664

    I 16:48:22 Operation Successfully Completed! - Duration: 00:00:09

    I 16:48:22 Operation Started!

    I 16:48:22 Source File: -==/\/[bUILD IMAGE]\/\==-

    I 16:48:22 Source File Sectors: 11.577.664 (MODE1/2048)

    I 16:48:22 Source File Size: 23.711.055.872 bytes

    I 16:48:22 Source File Volume Identifier: Boston - 2014-10-02 - Nippon Budokan, Tokyo, Japan (BluRay)

    I 16:48:22 Source File Application Identifier: ImgBurn v2.4.4.0

    I 16:48:22 Source File Implementation Identifier: ImgBurn

    I 16:48:22 Source File File System(s): UDF (2.50)

    I 16:48:22 Destination Device: [0:1:0] HL-DT-ST BD-RE BH10LS30 1.01 (E:) (ATAPI)

    I 16:48:22 Destination Media Type: BD-R (Disc ID: RITEK-BR3-00) (Speeds: 2x; 4x; 6x; 8x)

    I 16:48:22 Destination Media Sectors: 12.219.392

    I 16:48:22 Write Mode: BD

    I 16:48:22 Write Type: DAO

    I 16:48:22 Write Speed: 1x

    I 16:48:22 BD-R FastWrite: No

    I 16:48:22 Link Size: Auto

    I 16:48:22 Lock Volume: Yes

    I 16:48:22 Test Mode: No

    I 16:48:22 OPC: No

    I 16:48:22 BURN-Proof: Enabled

    I 16:48:37 Filling Buffer... (40 MB)

    I 16:48:37 Writing LeadIn...

    I 16:48:38 Writing Session 1 of 1... (1 Track, LBA: 0 - 11577663)

    I 16:48:38 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 11577663)

    W 17:13:56 Failed to Write Sectors 6639744 - 6639775 - Reason: Write Error

    W 17:13:56 Retrying (1 of 20)...

    W 17:13:56 Retry Failed - Reason: Invalid Address For Write

    W 17:13:56 Retrying (2 of 20)...

    W 17:13:56 Retry Failed - Reason: Invalid Address For Write

    W 17:13:56 Retrying (3 of 20)...

    W 17:13:56 Retry Failed - Reason: Invalid Address For Write

    W 17:13:56 Retrying (4 of 20)...

    W 17:13:56 Retry Failed - Reason: Invalid Address For Write

    W 17:13:56 Retrying (5 of 20)...

    W 17:13:56 Retry Failed - Reason: Invalid Address For Write

    W 17:13:57 Retrying (6 of 20)...

    W 17:13:57 Retry Failed - Reason: Invalid Address For Write

    W 17:13:57 Retrying (7 of 20)...

    W 17:13:57 Retry Failed - Reason: Invalid Address For Write

    W 17:13:57 Retrying (8 of 20)...

    W 17:13:57 Retry Failed - Reason: Invalid Address For Write

    W 17:13:57 Retrying (9 of 20)...

    W 17:13:57 Retry Failed - Reason: Invalid Address For Write

    W 17:13:57 Retrying (10 of 20)...

    W 17:13:57 Retry Failed - Reason: Invalid Address For Write

    W 17:13:57 Retrying (11 of 20)...

    W 17:13:57 Retry Failed - Reason: Invalid Address For Write

    W 17:13:57 Retrying (12 of 20)...

    W 17:13:57 Retry Failed - Reason: Invalid Address For Write

    W 17:13:57 Retrying (13 of 20)...

    W 17:13:57 Retry Failed - Reason: Invalid Address For Write

    W 17:13:57 Retrying (14 of 20)...

    W 17:13:57 Retry Failed - Reason: Invalid Address For Write

    W 17:13:57 Retrying (15 of 20)...

    W 17:13:57 Retry Failed - Reason: Invalid Address For Write

    W 17:13:57 Retrying (16 of 20)...

    W 17:13:57 Retry Failed - Reason: Invalid Address For Write

    W 17:13:57 Retrying (17 of 20)...

    W 17:13:57 Retry Failed - Reason: Invalid Address For Write

    W 17:13:57 Retrying (18 of 20)...

    W 17:13:57 Retry Failed - Reason: Invalid Address For Write

    W 17:13:57 Retrying (19 of 20)...

    W 17:13:57 Retry Failed - Reason: Invalid Address For Write

    W 17:13:57 Retrying (20 of 20)...

    W 17:13:57 Retry Failed - Reason: Invalid Address For Write

    W 17:14:17 Retrying (21)...

    W 17:14:17 Retry Failed - Reason: Invalid Address For Write

    W 17:14:18 Retrying (22)...

    W 17:14:18 Retry Failed - Reason: Invalid Address For Write

    W 17:14:19 Retrying (23)...

    W 17:14:19 Retry Failed - Reason: Invalid Address For Write

    W 17:14:20 Retrying (24)...

    W 17:14:20 Retry Failed - Reason: Invalid Address For Write

    W 17:14:20 Retrying (25)...

    W 17:14:20 Retry Failed - Reason: Invalid Address For Write

    W 17:14:20 Retrying (26)...

    W 17:14:20 Retry Failed - Reason: Invalid Address For Write

    W 17:14:20 Retrying (27)...

    W 17:14:20 Retry Failed - Reason: Invalid Address For Write

    W 17:14:21 Retrying (28)...

    W 17:14:21 Retry Failed - Reason: Invalid Address For Write

    W 17:14:21 Retrying (29)...

    W 17:14:21 Retry Failed - Reason: Invalid Address For Write

    W 17:14:21 Retrying (30)...

    W 17:14:21 Retry Failed - Reason: Invalid Address For Write

    W 17:14:22 Retrying (31)...

    W 17:14:22 Retry Failed - Reason: Invalid Address For Write

    W 17:14:23 Retrying (32)...

    W 17:14:23 Retry Failed - Reason: Invalid Address For Write

    W 17:14:23 Retrying (33)...

    W 17:14:23 Retry Failed - Reason: Invalid Address For Write

    W 17:14:24 Retrying (34)...

    W 17:14:24 Retry Failed - Reason: Invalid Address For Write

    E 17:14:27 Failed to Write Sectors 6639744 - 6639775 - Reason: Write Error

    E 17:14:27 Next Writable Address: 0

    I 17:14:27 Synchronising Cache...

    W 17:14:37 User opted to skip the 'Close Track/Session/Disc' functions.

    E 17:14:37 Failed to Write Image!

    I 17:14:41 Exporting Graph Data...

    I 17:14:41 Graph Data File: C:\Users\Ralle\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH10LS30_1.01_SONNTAG-31-DEZEMBER-2017_16-48_RITEK-BR3-00_1x.ibg

    I 17:14:41 Export Successfully Completed!

    E 17:14:41 Operation Failed! - Duration: 00:26:14

    I 17:14:41 Average Write Rate: 8.578 KB/s (1.9x) - Maximum Write Rate: 9.061 KB/s (2.0x)

    I 17:15:04 Close Request Acknowledged

    I 17:15:04 Closing Down...

    I 17:15:05 Shutting down SPTI...

    I 17:15:05 ImgBurn closed!

     

    what is wrong

     

    thanks for help

    Your ritek cheap crappy blanks, that's what's wrong.

     

    Sent from my Nexus 6P with Tapatalk


  11. No you can't do any of that. Imgburn burns AS IS only, it doesn't split anything. The maximum a bd50 will hold is 45.5gb. so even with overburning, there's no chance at all you can burn that much oversize.

     

    LG burns my DL's just fine. They're the only brand I use. And if it's video you're trying to burn, there's plenty tools that can shrink it down.

     

    Sent from my Nexus 6P with Tapatalk


  12. Thanks for the reply Lightning, but I am confused. Didn't I print your programs error logs? Shouldn't they provide what you need ?

     

    Let me know what you need or if I did not provide the right information.

     

    Thanks again :) .

    You did everything right, the issue is that the DRIVE is reporting a generic error (invalid field in cdb) that doesn't mean much, instead of reporting an actual real informative error such as 'write error...'. combining both topics on 2 forums and the fact that you're using quality media, I'd go with faulty drive.

     

    Sent from my Nexus 6P with Tapatalk


  13. As i told you there (and as is said in the pink box up top) you need to post the entire contents of the IMGBurn log window. Images alone mean squat.only then will lightningUK be able to troubleshoot the error(s)

     

    @lightning we've already confirmed at the AnyDVD forums he's using the latest firmware available for that drive and using the good stuff blank wise

     

    Sent from my Nexus 7 with Tapatalk


  14. You say you're aware but apparently not of what's said. If you were you'd know that the only thing is contained is the opencandy dll. It's that dll, NOT IMGBURN that's responsible for retrieving and showing the offers you see. Go complain to the ones responsible for opencandy, if you can find them. Opencandy itself has had support dropped by the devs.

     

    Sent from my Nexus 6P with Tapatalk

×

Important Information

By using this site, you agree to our Terms of Use.