I'm using Version 2.5.8.0, but the important thing is that you have a version that can specify the beginning LBA address for built images.

Other than that, knowledge on how to make cue files correctly is a must!

The steps:

1. First you need to start with your cue file.
   1. Add your media files like normal, ensure the files you want are all there.
   2. Order isn't really important, neither is the text values.
   3. Once you have the music in place, add a second session, and add a track to this session (I believe any valid file can work, but a binary-mode file is preferred just in case).
   4. Save the cue file and have it added to the write cue.
2. Next we're going to find the LBA offset
   1. Switch to Write mode, insert a writable disk (preferably of the same type you're intending to actually make, i.e. a CD)
   2. Ensure Test Mode is checked (Or you'll end up with a broken disk that most computers will be very angry about) and execute the test burn.
   3. Once it's finished, find the log lines that look like this:
      

      I 21:02:58 Writing Session 2 of 2... (1 Track, LBA: 333350 - 358559)
      I 21:02:58 Writing Track 1 of 1... (MODE1/2048, LBA: 333350 - 358559)
      

      The first number is what we're after. Typically the session and track number will be the same for both session and track (in this case it's 333350).

   4. Write this number down! It's important!

3. Then we do spooky advanced things!

   1. Head into Tools -> Settings -> Build -> Page 1.

   2. Find the setting "Image Start LBA". It should be 0 by default.

   3. Replace that zero with the number we found above and hit OK

4. Build the ISO like normal

   1. Do the needful and make an ISO file. I haven't tried anything much more complicated than a typical image with no extra features, but in theory anything should be fine, maybe not bootable images though.

   2. Do note that of course you can't exceed the available sectors on the disk. I'm not entirely sure how to calculate that precisely, but I assume it should be somewhat less than the ending sector minus the starting sector we got above (and leave some room for LEAD OUT)

5. Go back to the cue file we made and update it

   1. You'll want to ensure that our session 2 track 1 file is correct, you can either edit the cue file by hand, or just recreate the cue file from scratch, but this time selecting your built ISO.

   2. BE SURE THE OTHER TRACKS ARE EXACTLY THE SAME AS BEFORE. If the files are different in any way the starting sector for session 2 will probably be different, and that will break the disk!

6. Load up the cue file again, and burn it!

   1. If you don't reload the cue file (either by re-building it in the editor, or re-selecting it in the Write mode image file picker, the calculated image size will be wrong, and you may not be told if the resultant image is too big for the target disk. Obviously, trying to burn an image that's too large is not usually a good idea.

   2. Assuming you've got this far, and the image is small enough to fit the disk, IMGBurn should burn the cue file just dandy.

   3. However, if the LBA offset we built the ISO from is wrong, the Verification phase will fail at the start while reading the TOC, usually while parsing the file system of the disk (It will say as much too). After that verification should go off without a hitch insomuch as reading the sectors and verifying the burn itself is concerned, but rest assured, the burn is bad!

   4. If the burn is good, once verification is done Windows will read the disk and everything is dandy, in My Computer the disk icon will be a CD with a green Plus sign. Double-clicking should launch your media player, and if you right-click -> Open you should see the files you put into the ISO!

   5. If the burn is bad most likely the LBA we set in step 3 is wrong, double-check what it's supposed to be from that last burn, and rebuild the ISO if necessary.

7. If all went as planned, congratulations! You made a CD-Plus disk!

thanks.

Hello everyone.

Could someone kindly recommend a burner that is particularly good at writing bd-r double layer (50 GB)?

Thank you very much.

But I do see, that some of the discs are getting damaged. And are no longer usable. So I make a copy of my current movies to keep it in case of disc failure.

As far as I know, in my country The Netherlands, it is legit to make a copy of your discs that you own. I emailed our agency "Brein" for it. The answered it is ok. No problem.

So I anasered back to them again with a 2nd question: Well, then if I sell the disc , their is nothing wrong that I give the digital copy as well right? I mean, the disc proofs legit ownership of the movie right? Brein, never answered back, This is a grey area. I understand they don't want to make an official statement, that it is ok. That can cause sue from movie companies, etc.

Some shops selling 2nd hand dvd also do not sell the copy with the original.

Personally I have the disc, it is the proof I legally own that specific movie. So no one can say I have stolen it, or whatsoever.

What are your thoughts about this?

the short answer is... install PlayOnLinux (sudo apt install playonlinux), then through PlayOnLinux install Wine v4.0.4 (I use 64bit (amd64)), configure Wine so it's using Windows XP mode, then ImgBurn will work as expected (and detect your CD/DVD drives with it's default ASPI mode). NOTE: everything is configured here through a GUI (graphic user interface) with the exception of the initial 'sudo apt install playonlinux' command from the terminal, which should be easier for novices (and not to mention people like clicking stuff instead of typing ). NOTE: for more details on setup/configuration see "TIP #1" and "TIP #2" etc below!

once your done you can simply load ImgBurn from the shortcut it creates on the desktop, or from within the PlayOnLinux program itself. PlayOnLinux does not need to be running for ImgBurn to work (although you run PlayOnLinux during initial setup/configuration of ImgBurn) as it's easiest to simply load ImgBurn from the desktop icon it creates as at this point it's works just like it does on Windows (as I was recently playing with ImgBurn and overburning a standard audio CD on a CD-RW disc etc and it worked). NOTE: PlayOnLinux is separate from your standard system Wine installation. so even if your using the standard Wine installation (i.e. https://wiki.winehq.org/Ubuntu ; after those six steps are done issue 'sudo apt install wine-desktop-files' which gives you the proper Wine entries on the Mint menu) and something gets out of whack, it won't effect your PlayOnLinux setup with ImgBurn since it's running in it's own what I think is referred to as a 'wine prefix', or 'virtual drive' one could say which people are probably a bit more familiar with that term.

TIP #1: for installing Wine v4.0.4 in PlayOnLinux... "Tools > Manage Wine Versions > Wine versions (amd64)" then scroll down to "4.0.4", left click it so it's highlighted, then click the ">" and it will download Wine v4.0.4 etc. then you can close out of this.

TIP #2: while you can probably install ImgBurn using PlayOnLinux's "Install a program" from it's main menu, I typically do everything I need to from the 'Configure' window from the main PlayOnLinux menu... so from the 'PlayOnLinux Configuration' window it will probably have 'default' highlighted already, click 'New' then click next etc and you will see 'What kind of virtual drive to you want to create' screen and I select '64 bits windows installation'. then on next screen you should see the "4.0.4" (if not, do "TIP #1" above first!). then on next screen you should see it ask you 'Choose the name of the virtual drive' and I just call it 'ImgBurn' (for example), then click next and it will probably do some automatic configuration stuff and then ask you to install 'Mono' and 'Gecko' which you just CANCEL out of those (and everytime you see them during installation as they are not needed for ImgBurn to work). now you will be back on the 'PlayOnLinux configuration' screen and then simply left click the 'ImgBurn' (in top left corner area of that window) and to the right of that you will see tabs "General / Wine / Install components / Display / Miscellaneous", we are only going to use General/Wine/Miscellaneous tabs to get ImgBurn working. but anyways, click the 'Wine' tab, then click 'Configure Wine' and after a few seconds you should see a 'Wine Configuration' screen popup with the 'Applications' tab already selected. but where it shows 'Windows Version: Windows 7' you want to change the 'Windows 7' to 'Windows XP' then click 'OK'. now back on the 'PlayOnLinux Configuration' screen click the 'Miscellaneous' tab you will see 'Run a .exe in this virtual drive', click this and guide it to wherever you downloaded your ImgBurn installer exe file to and proceed to install it like you typically would. after that done, back on the 'PlayOnLinux Configuration' window click the 'General' tab and then click the "Make a new shortcut from this virtual drive" which after a brief bit of time should find 'imgburn.exe', select this and it will basically make a ImgBurn shortcut on your desktop. your basically done and can completely close the PlayOnLinux program now and you simply run the ImgBurn shortcut from the desktop and ImgBurn should work as expected. NOTE: if you see any Mono/Gecko popups during initial loading of ImgBurn, just 'cancel' out of it and in the future when you load ImgBurn it will just load up ImgBurn like you would normally expect and should not nag you about Mono/Gecko stuff anymore.

NOTE: newer versions of Wine (Wine v5 series or newer) will usually work to but ImgBurn won't detect your CD/DVD burners in it's default state and requires you do the following in ImgBurn to get it working... 'Tools > Settings > I/O', then select 'SPTI - Microsoft' and where it says 'SPTI - Device Enumeration Method' I suggest changing that to 'Device Interface' and after you press OK and return to the main ImgBurn window you will now see it shows that your CD/DVD burners are now detected in the 'ImgBurn Log' window. but it's better to just use Wine v4 series if possible since it's probably a bit more proper and you won't have to use the SPTI stuff. also, one can install Wine v2.0.5 for example, as if you do this, you won't have to change Wine from Windows 7 back to Windows XP mode since it's Windows XP mode by default. but ImgBurn's fonts look a bit weird, so I suggest just using Wine v4.0.4 and change it from the default of Windows 7 mode to Windows XP mode. because if you try to load ImgBurn with Wine in it's default Windows 7 mode it will hang at the ImgBurn loading screen and simply won't work.

NOTE: if a person prefers to use ImgBurn with the standard Wine installation on Linux Mint v20.x through the repositories, which I think is Wine v5 series, you would simply issue "apt install wine-installer" from the terminal (which is how the Linux Mint team suggests installing the system installed Wine) but, if I recall correctly, this does not support opening .exe files through the file manager to install them. but a quick tip that should give you the gist of it is to issue "wine /location/to/imgburn/installer/SetupImgBurn_2.5.8.0.exe" (this is a example as you need to adjust that to the location of your ImgBurn exe accordingly) and it should install ImgBurn and give you a menu entry in the 'Wine' menu entry. then you run the 'Wine > Configure Wine' and on 'Applications' tab with the 'default settings' highlighted you can change 'Windows Version: Windows 7' to 'Windows XP' and click OK, OR if you want to leave your system Wine installation in it's default Windows 7 mode for other programs and still want to use ImgBurn, since it requires Windows XP mode, you can click the 'Add application' then guide it to the "ImgBurn.exe" in the "Program files (x86)" folder and click OK. but when you load ImgBurn it won't see any of your CD/DVD burners but you simply do that 'SPTI' tweak that I mentioned in the 'NOTE:' above and it will work well enough) ; but with all of this said, I suggest using PlayOnLinux instead as it's easy enough and should work reliably and I personally think it's better to use the default ASPI over having to change to SPTI for drive detection.

NOTE (but people likely won't bother with this since it's more difficult for no real reason): I am aware one can create their own Wine prefixes (so instead of saving ones Wine configuration to the default ".wine" in ones Home folder, you could do something like ".ImgBurn") through command line but I think people prefer easier in general. but since I already typed a novel so far I might as well post the gist of these commands if you want to try this method from your system installed Wine...

1)Install ImgBurn to it's own Wine prefix (I am assuming the ImgBurn installer exe is in the root of ones home folder)...

WINEPREFIX=$HOME/.ImgBurn wine "$HOME/SetupImgBurn_2.5.8.0.exe"

2)Configure Wine to use Windows XP mode...

WINEPREFIX=$HOME/.ImgBurn winecfg

3)Run ImgBurn and burn your CD/DVD's...

WINEPREFIX=$HOME/.ImgBurn wine "$HOME/.ImgBurn/drive_c/Program Files (x86)/ImgBurn/ImgBurn.exe"

you will obviously have to set ImgBurn to SPTI mode etc like I mentioned before though since on using the more 'official' method the Linux Mint team recommends to install Wine gives you Wine v5 series (at least the last I checked on Linux Mint v20.x) which does not work as well with ImgBurn by default like the Wine 4 series does.

p.s. I suggest getting ImgBurn v2.5.8.0 from the MajorGeeks website since it does not contain any junk in the installer. the sha-256 hash of that file is... "49aa06eaffe431f05687109fee25f66781abbe1108f3f8ca78c79bdec8753420" (and is 3,101,913 bytes in size) ; to check sha256 hash of a file on Linux from terminal you issue "sha256sum SetupImgBurn_2.5.8.0.exe" (it's case sensitive so whatever your ImgBurn is named as it's got to be precise with that command in the terminal) and I am assuming you got the ImgBurn exe file in the root of your home directory otherwise you need to type the precise location to it for it to check the hash.

==================================================================

Here is a screenshot I took of ImgBurn running on my Linux Mint v20.3-Xfce installation...

I have never done this with ImgBurn.

The .iso is less than 4.35GB but all that are available are DVD DL discs.

How can a SL size .iso be burned to a DL DVD with ImgBurn?

The PIONEER drive does not recognize my blank or recorded 100 GB triple layer M-DISCs, while my ASUS BW-16D1HT reads and writes 100 GB triple layer M-DISCs on the same PC ¿Even if it does not write M-DISC TL (100 GB) should it be able to read them if it is a BD-XL drive?
I haven't tried with normal BD TL because I don't have one, but the pioneer drive does read and write normal 25 GB BD's.

My main question is if the drive can read TRIPLE-layer M-DISC discs (100 GB), and another question is if it can read regular bd TRIPLE-layer discs (100 GB).

In the firmware notes it mentions triple layer support in firmware 1.50.

https://pioneer.jp/device_e/product-e/ibs/device_e/dev00002r_e.html#BDR-209DBK
 

This instruction manual also refers to the triple layer, but only associates it with writing, not reading.

https://www.pioneer.com.au/wp-content/uploads/2016/11/Instruction-Manual-for-BDR-209DBK.pdf

This pdf alludes to a low version of the firmware where the TL read function was removed.

https://images10.newegg.com/UploadFilesForNewegg/itemintelligence/Pioneer/BDR_209DBK_Pro_Spec_Rev1_20011445191870512.pdf

The M-DISC website states that it only records M-DISC single layer (25 GB) and DL (50 GB).

https://www.mdisc.com/drive-compatibility.html

Also say that the website has been out of date for some time and that firmware 1.50 is from 2018.

While IMGBURN says it does not read or write BD-XL, only single layer (25GB) and dual layer (50GB) blu-ray, which is what the M-DISC website says.

Thanks!

Sounds.zip

2) searched all tabs for wine 4.0.4, nothing, even typed in search window, nothing.  ended up using snap to download (using ubuntu)

3) found imgburn and it's being difficult. it has me browsing files, but install is obviously not the correct file. tried every folder in the install file with exact same error that wine crashed.

i really don't want to reload 7 or 10 just so i can image burn another debian based o.s.  i also don't want to turn a thumb drive into a hard drive, cause i'm still trying to figure out what o.s. i like best.  so far ubuntu is ok, but it seems to have a foul temperment when it comes to loading gaming platforms.   

This isn't really a big deal; however, I do burn many copies of an image and having to convert files prior to each burn of the image would be a bit taxing on my computers. (I use older machines for burning.)

I think this is only because I don't specify the REM file decoded size in my custom cue files from my program.

I did some more digging and I saw someone able to do it when they were creating a similar program of writing cue files with python. I personally am using Java for my program and there was no good way of getting the decoded size of an MP3 in MM:SS:FF format.

However, there is an easy way to just get the normal playable length of the MP3 file using java. This leads me to my question of: Can I just use the length of the MP3 file itself as the REM file decoded size?

I also read somewhere that the length should be almost the same and the only difference would be a couple of frames; there are 74 frames in a whole second of audio so I would only be compromising a maximum of a single second in audio? I really wouldn't notice that at all. But I just want to make sure that what I plan to do won't ruin the whole point of a traditional audio CD as opposed to a data CD of MP3s or MP3 CD.

Another general question I had about the way Imgburn works: are these decoded files whenever Imgburn performs the 'Analyzing Audio Files' constructed in memory as the disc burns? I still can't piece my around how I have normal cue files that do not correspond with a binary file of the raw data structure of an audio CD. I feel like I read somewhere on the forum that the files are constructed in small segments in memory as the burn proceeds but I just wanted to confirm.

I apologize for a very long initial post and I thank those who bother reading even a portion of it. Thanks for any help in advance!

Here's a possibly silly and quite belated concern:

I've started burning Audio CD's again, using .cue files that point to .flac files. If I am getting it correctly, the system uses the default FLAC decoder to decode the files on-the-fly, and pass them to ImgBurn for burning.

My concern is what the decoder might be doing to the audio. In this case, the excellent LAV Filters (its tray icons appear during burning).

In the attached, you can see a few options that may affect audio output, namely Mixing and Clipping protection. In the current configuration, Mixing shouldn't be an issue.

So, the question here is: can the LAV Filter settings (or any other DirectShow filter that may be used during Audio CD burning) interfere with what actually ends up in the CD, or is this all irrelevant and taken care of centuries ago?

Thanks

I hate the constant grinding noises that occur when browsing optical media full of small files. So, I guess what I am saying (or asking) is should I be using my optical media to archive only and not browsing the data on it as though it were an acceptable device for browsing the data it holds, other than possibly video files which would be written, and likewise, read mostly sequentially anyway. And therefore be larger files by the same token.

If anyone here has Verbatim DVD or Bluray burner (internal or external) please kindly share the name of its Buffer underrun protection brand?

ie Verbatim SmartBurn or SafeBurn or BurnProof etc?

Thanks for help

We need to "revive" a couple of old 32-bit utilities.  One was written for Win XP and the other for Win 7.  The companies that wrote both of these utilities have long since closed their doors, so there's no hope of any updates or support.

I'm a longtime Mac user with zero experience when it comes the [recommended] ImgBurn utility, so please bear that in mind.    Due to severe space limitations, we will need to invest in an old PC laptop to accommodate the 32-bit PC utilities mentioned in the first sentence of this post.  As this is all theoretical, at this point, I'd like to know if there are particular versions of ImgBurn that are better suited to 32-bit versions of both Win XP and Win 7?  In other words, are there specific versions [plural] of ImgBurn that were written exclusively for both Win XP and Win 7?  If there are, I'd really appreciate information about how to obtain both versions.

I appreciate the help ~

McQuad

• System
  
• Volume Set
  
• Publisher
  
• Data Preparer
  
• Application
  

I am trying to retrieve that information after burning a media. Not much success since i do not find a tool to read these identifiers. Even ImgBurn doesn't seem to show them in read mode.

PlexTools is showing at least the Publisher entry. But thats it.

How do I retrieve these data again?

I've discovered that, if you start a project by allowing Unicode support in the volume labels, entering in X number of Unicode characters into the label field. And then haphazardly going back to disable Unicode support in the labels, the ImgBurn software will not warn you that the final master will not be what you intended it to be? How did this situation arise to begin with? I'll tell you.

It happens when you eagerly start a label with Unicode characters but quickly realizing that you're volume label needs more than 66 (or whatever the max is) Unicode characters. So, this happened to me. I started my label with a few smiley faces for XXXXs and giggles. But then realized I needed more than 64 characters to describe all the data on the disc. I checked the "Disable Unicode support" box to double the volume label width and BOOM, no warning, no prompt, no erasure of the volume label to protect the user.

But this is just one gripe in a sea of many. What is the state of this software? If the author wants money to sell the rights, let us know. Open source this software if there's no interest in it anymore. Something, tell us something. This software is too good to just let it simply languish to death.

Case in point. Coincidentally on the same burn, there were several missing files that should have been where they were when they were added to the folder/file list but weren't. The software paused 5x so that I could add the missing files and I finished the burn without any issue whatsoever. That is amazing. Let's keep this goodness going.

Im not new to imgburn, first used it somewhere back in the 2000's. Im a little rusty with it. Im wondering how to name the cd, add its composer, and then add the filenames track/artist data. But how to add album icon??

Before IMGBURN, I used to use Fuerio! CD writer, and I had .bin and .cue already. Trying to write an audio cd with the artist/trackname/album, Windows media player makes track1, track2, etc... even with the proper names stored in the file, and music app on Mac writes track name, but track artist= playlist name, and then album name = (NO DATA). IMGBURN is AGAIN a life saver....

Will donate!

Here's the SPTI part of my code:
 

const UCHAR cdb[12] = {0xBE, 0, 0, 7, 42, 15, 0, 0, 1, 0x10, 0, 0};
UCHAR bufx[2352 * 1];
memset(&bufx, 0, 1 * 2352);
struct sptd_with_sense {
  SCSI_PASS_THROUGH_DIRECT s;
  UCHAR sense[20];
} sptd;
memset(&sptd, 0, sizeof(sptd));
sptd.s.Length = sizeof(sptd.s);
sptd.s.CdbLength = sizeof(cdb);
sptd.s.DataIn = SCSI_IOCTL_DATA_IN;
sptd.s.TimeOutValue = 30;
sptd.s.DataBuffer = bufx;
sptd.s.DataTransferLength = sizeof(bufx);
sptd.s.SenseInfoOffset = offsetof(struct sptd_with_sense, sense);
sptd.s.SenseInfoLength = sizeof(sptd.sense);
memcpy(sptd.s.Cdb, cdb, sizeof(cdb));
BOOL rx = DeviceIoControl(handle, IOCTL_SCSI_PASS_THROUGH_DIRECT, &sptd, sizeof(sptd), &sptd, sizeof(sptd), &dummy, NULL);
DWORD ex = GetLastError();

I want to know what is missing in my code. One more thing is that I wonder how could the raw data be "cooked", as I want to get mode1/2048 sector data.

(P.S. it's so cool that there is still a relatively active forum for the program, haha.)