All Activity

Sorry. Yeah, it's a Blu-ray video BD-R. It was created with tsmuxer. The original file is an mp4 (or mp2...I'll have to check), but once muxed, it's a m2ts, and I've included chapters in that muxing. It's the same way I've always created them; the only difference is that I'm trying to burn two folders onto the disc instead of the usual one, so I didn't know if that had something to do with it. I know that doesn't sound technical, but that's about my extent 🤣

Well, this isn't much to go on. You haven't said what created your BD. Is this a Blu-Ray Video BD? If so, something created the BDMV, which may not have made it correctly. Are you playing MP4 or some other video container file type burned to BD-R in your player? If so, does the container file itself actually have chapter marks in it?

Howdy! If this is the wrong section of the forum, I apologize--just let me know. I've been using imgburn for years for my BDs and have never had this problem. I burned two movie titles (folders) to a BD for the first time (I had only done single-title discs before this), and the chapters are not working for either movie. I'm sure the chapters are part of the files because I had previously burned one by itself and was able to use them. Does anyone know why this may be? Thanks!

Still, GUIDs on Windows systems always include the date/time because it's one of the things that changes constantly and, therefore, imparts uniqueness when things need to be this way. A volume set identifier would need to be unique as well so there's a good chance the developer uses a date/time as "part of" the volume set identifier.

Yeah, the Volume Label. I couldn't think of its name at the time.

Yes, in the volume label, unless you were referring to something else. Just depends on how many similar or different things I'm burning onto a specific BD-R disc I guess.

And you could, if you've got spare Label characters, put the date in there.

Yes, something along those lines will work, if, he doesn't use a date/time stamp in that Volume Set Identifier. I just had another idea also. There are 5 fields you can populate with data on the "Labels" tab called "Volume Identifiers". One of them is called "System" so I could just generate a date/time and cut'n'paste into that field. But, reading those fields would only be easy using ImgBurn, I imagine. So.....maybe a text file with the most recent date/time in the root of the DISC as you suggested. Even in the volume label itself if you don't need the full 128 ASCII characters that a UDF label provides. Just kicking around some ideas. Or I could just go old skhool and pickup a sharpie after the burn and....you get the idea! I've actually done this before on a few platters.

I don't know this for sure, but I don't think there's any metadata burned to a disc by ImgBurn that tells when it was written. The closest you can probably get is to check the date/time stamps on files on the media and you might get an idea. One thing I do when Building an ISO is put a folder in the root directory with the current date to let me know when it was created.

I'd like to know if the media creation date is stored in the "Volume Set Identifier" by chance and if so, is it a date and time, just a date, and how many characters do I need to convert it to an actual operating system date and time? I know the log file stores enough data to possibly get it from there but let's pretend that got deleted by accident or corrupted. And I wanna get it from the media itself. Is this possible?

Yes, everything is fine and as it should be.

hi sorry english is not my native language so , the log is perfect , i dragged a cue and started to burn and in the log there is SAO so it's perfect for audio cd sao , isn' it? just i remember some software have an option to select dao , sao or tao thanks

Like I said, it's the same thing. That's why the option says DAO/SAO and they aren't 2 different options. No extra session gets opened and you've burnt the disc in one go without any forced gaps. That's DAO. The MMC specs just referred to it as SAO for CD and so that's why the program calls it what it does.

hi i have burned a cue +wavfile and in the log there is write type sao how can i push imgburn to use dao? thanks

Unless you’re creating a CD-Extra disc, there won’t be any additions sessions and so you’ve essentially just burnt in DAO mode. So that would be the standard method of burning an audio cd in ImgBurn anyway. If you want control over the gaps between tracks, you just need to avoid TAO.

Hi but when i burn an audio cd , imgburn does it perform always a sao burning i have always read disc at once should be the best for audio cd is there a way to push imgburn to use dao (disk at once) ? thanks

I think where I live, the US, it's a year.

24 months on most electronics, at least in my part of Europe.

I'm pretty sure you only get a 12 month guarantee on most electronics.

I hope it was still in guarantee.

Of course, right after I praised the ASUS for going strong for 1.5 years, I had to replace it Sunday night. So, it lasts for about 18 months with rigorous near daily use before it needed replacing. It developed an issue with its red laser.

Well, I stand corrected. My external USB blu ray burner Verbatim 43889 that I bought in 2023 is a Pioneer drive. But the drive that I bought several days ago - same Verbatim 43889 BD burner - is actually an LG drive :( I guess it's ok for single layer BD's, but I wouldn't trust it with double or triple layer Blu ray discs.

In order to look more like Explorer, the program will now round up rather than doing bankers rounding. So a 0 byte file will show 0 KiB but a 1 byte file will show 1 KiB. A 1024 byte file will show 1 KiB but a 1025 byte file will show 2 KiB.

Good God, I just checked the file again in Windows File Explorer on Windows 10 and it reported the 71 byte file in 3 different sizes. In the "Preview Pane" when the file is selected it reports the size exactly as 71 bytes. In the File Explorer "Size" column it reports as 1K. And when you right-click the file and select the "Properties" dialog box it reports the size correctly at 71 bytes but it reports "Size on disk" as 0 bytes. It's serving up a little bit of everything I guess.

It uses Bankers rounding for all of that stuff. The top pane is a component and its code basically seems to return 1KB if it's anything less than 1. Explorer must be rounding up as it calls a 1025 byte file 2KB.