infiniter

Just wanted to report this bug. I made an image of 2 session DVD+DL. It seems the image contains session 1 and 2, whereas session 2 usually includes session 1, so session 1 is double. At least it explains the huge image. The log excerpt below states that session 2 is read from the beginning of the disc. ImgBurn version: 2.5.5.0 HL-DT-ST DVDRAM GH22NS50 TN01 (SATA) Current Profile: DVD+R DL Disc Information: Status: Complete State of Last Session: Complete Erasable: No Sessions: 2 Sectors: 4.026.304 Size: 8.245.870.592 bytes Time: 894:46:04 (MM:SS:FF) File System Information: Sectors: 4.026.304 Size: 8.245.870.592 bytes Time: 894:46:04 (MM:SS:FF) TOC Information: Session 1... (LBA: 0) -> Track 01 (Mode 1, LBA: 0 - 3447839) Session 2... (LBA: 3447840) -> Track 02 (Mode 1, LBA: 3447840 - 4026303) -> LeadOut (LBA: 4026304) Track Information: Session 1... -> Track 01 (LTSA: 0, LTS: 3445792, LRA: 0) Session 2... -> Track 02 (LTSA: 3447840, LTS: 578464, LRA: 0) Disc Control Blocks Information: PLEXTOR PX-B920SA Physical Format Information (Last Recorded - L0): Disc ID: MKM-001-00 Book Type: DVD-ROM Part Version: 1 Disc Size: 120mm Maximum Read Rate: Not Specified Number of Layers: 2 Track Path: Opposite Track Path (OTP) Linear Density: 0.293 um/bit Track Density: 0.74 um/track First Physical Sector of Data Area: 196.608 Last Physical Sector of Data Area: 16.433.087 Last Physical Sector in Layer 0: 2.283.519 Physical Format Information (Last Recorded - L1): Disc ID: MKM-001-00 Book Type: DVD-ROM Part Version: 1 Disc Size: 120mm Maximum Read Rate: Not Specified Number of Layers: 2 Track Path: Opposite Track Path (OTP) Linear Density: 0.293 um/bit Track Density: 0.74 um/track First Physical Sector of Data Area: 196.608 Last Physical Sector of Data Area: 16.433.087 Last Physical Sector in Layer 0: 2.283.519 Layer Information: Layer 0 Sectors: 2.086.912 (51,83%) Layer 1 Sectors: 1.939.392 (48,17%) When reading, the log says: I 16:05:12 Reading Session 1 of 2... (1 Track, LBA: 0 - 3445791) I 16:05:12 Reading Track 1 of 1... (MODE1/2048, LBA: 0 - 3445791) I 16:05:12 Reading Layer 0... (LBA: 0 - 2086911) I 16:11:09 Reading Layer 1... (LBA: 2086912 - 3445791) I 16:14:25 Reading Session 2 of 2... (1 Track, LBA: 0 - 578463) I 16:14:25 Reading Track 1 of 1... (MODE1/2048, LBA: 3447840 - 4026303) I 16:14:25 Reading Layer 0... (LBA: 0 - 2086911) I 16:20:18 Reading Layer 1... (LBA: 2086912 - 4026303) Apart from that, I suggest the READ function should let the user select the session(s) to include in the image OR let the user make an ISO which contains the data as it is shown in Windows: merged. This would not be an 1:1 image, but at least of almost the same size as the disc.

Perhaps I should check, but first I want to tell this: I burned a third dual layer DVD with the 2.4.4. No change. So it's not the version. Then I thought about what could be the reason or difference between previous AVCHDs I've burned with ImgBurn and now. I have a BD9 with Hancock. This was an ISO I downloaded somewhere, some time ago. I burned it with ImgBurn and it runs fine as AVCHD on my PS3. In order to compare Hancock with my new disc, I used IsoBuster. IsoBuster tells me the same UDF version, disc type etc. blablabla about both discs. It can even tell they were burned using ImgBurn. Where is the difference? There must be something even Isobuster can't tell. One thing is also different: the simple BD9 of Hancock comes without menu, so it's a true AVCHD. The new BD9 has a menu. It's just a downscaled Blu-Ray and it has some more folders like on the original disc, but these are empty. I don't think it's the folders. The BD9 is thus also a Blu-Ray, only on a DVD media. Since I did this before (downscaling Blu-Ray to fit onto DVD9 media) and it worked fine with ImgBurn and my PS3, I also doubt it to be the Blu-Ray format itself.

I always used Verbatim DL and I burned some AVCHD before with older version of ImgBurn and it always was fine. I suspect the 2.5.0.0 to not burn UDF2.5 correctly. I will try with the older version again and report here.

No offense, man. I was giving a little bit of your charme back. If there was a log, I would post it. ImgBurn does not save logs aotomatically. And the program was, of course, already closed when I detected this problem on my PS3. So I'm trying again. I'll do it the same way as before. I just drop the two folder, BDMV and CERTIFICATE, into ImgBurn. It says "It seems like you....BluRay..." and also tells me the data type should be set to MODE 1/2048. Then I want to make a TEST burn, but it say DVD+R DL does not support TEST burns, so I decided to do a real burn. Let's see... OK, burned that disc. Don't see anything wrong in the log. Now testing it on my PS3... Too bad, the same thing: data disc. When I open "Information" about the disc, it say "0 titles, 0kb". When I browse the folders to STREAM, some .m2ts files are marked as "incompatible". The others can be played. Well, now that is strange... ImgBurn.log

It is an option, so why should be it in a "functions" guide? If there was an "Option guide", I would have read it. "MODE1 is intended for the storage of computer data" tells me, that it was the wrong setting. Well, fifty-fiftychance to now get a correct disc. About the file system: of course UDF 2.5, as I wrote above. But there is also the new option "Data type" for the filesystem and this was set to MODE 2048, as I also wrote in the post above, that you didn't read. ;o)

Hi there! I have burned several BDMVs to DVD+R DL media as so-called BD9 before. With former versions of ImgBurn. These were recognized as BDMV and ran fine by my PS3. Now with 2.5.0.0, when I created such a disc the first time, it reported something like "Your data contains a folder called BDMV, so let's assume it's going to be a Blu-Ray disc". Well, nice idea. It also asks to change the layout to Blu-Ray by using UDF 2.5. So far, so good. I burned the disc and put it in my PS3 and the PS3 said "Data disc" and shows the BDMV and CERTIFICATE folders. So there must be something wrong with the automatic settings. I saw, there's a new setting "DATA TYPE" in "IMAGE OPTIONS". This is not yet explained in the ImgBurn guide for burning Blu-Rays. I couldn't find it elsewhere, too. So, how has it to be set for UDF/Blu-Ray? It was in MODE 2048 and I suppose it should have been "MODE 2/FORM1/2332". Correct? A request to the ImgBurn programmers: also update documentation when adding new features.

The alternative to authoring program is a freeware tool called "multiAVCHD".