Emulgator
-
Posts
9 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Emulgator
-
-
3 years later:
I would pay for a DDP/CMF plugin too. Lets make it a plugin that can be activated by a donation.
Users will see the greyed-out plugin and maybe the one or another will buy it anyways.
The ImgBurn userbase is huge, I suppose...
The structure I see in a DVD-9 DDP (Folders LAYER_0 and LAYER_1)
built in Sony DVD-Architect Pro 5.2 seems to be quite simple:
CONTROL.DAT (32KB) starting with 01 02 31 10 00 03 00 00 00 F2 80 7F 00 18 D0 BF,
the rest to address 0x7fffh filled with zeroes. This content is the same for Folders LAYER_0 and LAYER_1
DDPID ( the only content is one line, containing the version number of DDP,
followed by descriptors, less than 1KB)
For LAYER_0:
DDP 2.10 DV2020OB00V0000 VVVMD2 0000001600193024 DV00 017CONTROL.DAT VVVMD0 0142969600196608 DV00 017IMAGE.DAT
For LAYER_1
DDP 2.10 DV2021OB00V0000 VVVMD2 0000001600193024 DV00 017CONTROL.DAT VVVMD0 0074169601626303 DV00 017IMAGE.DAT
and the respective
IMAGE.DAT, containing the image for that layer.
Size and content of this image does differ from that built by ImageBurn, though.
-
+1 from me. I would pay for that too. Lets make it a plugin that can be activated by a donation.
Users will see the greyed-out plugin and maybe the one or another will buy it anyways.
The ImgBurn userbase is huge, I suppose...
The structure I see in a DVD-9 DDP (Folders LAYER_0 and LAYER_1)
built in Sony DVD-Architect Pro 5.2 seems to be quite simple:
CONTROL.DAT (32KB) starting with 01 02 31 10 00 03 00 00 00 F2 80 7F 00 18 D0 BF,
the rest to address 0x7fffh filled with zeroes. This content is the same for Folders LAYER_0 and LAYER_1
DDPID ( the only content is one line, containing the version number of DDP,
followed by descriptors, less than 1KB)
For LAYER_0:
DDP 2.10 DV2020OB00V0000 VVVMD2 0000001600193024 DV00 017CONTROL.DAT VVVMD0 0142969600196608 DV00 017IMAGE.DAT
For LAYER_1
DDP 2.10 DV2021OB00V0000 VVVMD2 0000001600193024 DV00 017CONTROL.DAT VVVMD0 0074169601626303 DV00 017IMAGE.DAT
and the respective
IMAGE.DAT, containing the image for that layer.
Size and content of this image does differ from that built by ImageBurn, though.
-
+1 from me. I would pay for that too. Lets make it a plugin that can be activated by a donation.
Users will see the greyed-out plugin and maybe the one or another will buy it anyways.
The ImgBurn userbase is huge, I suppose...
The structure I see in a DVD-9 DDP (Folders LAYER_0 and LAYER_1)
built in Sony DVD-Architect Pro 5.2 seems to be quite simple:
CONTROL.DAT (32KB) starting with 01 02 31 10 00 03 00 00 00 F2 80 7F 00 18 D0 BF,
the rest to address 0x7fffh filled with zeroes. This content is the same for Folders LAYER_0 and LAYER_1
DDPID ( the only content is one line, containing the version number of DDP,
followed by descriptors, less than 1KB)
For LAYER_0:
DDP 2.10 DV2020OB00V0000 VVVMD2 0000001600193024 DV00 017CONTROL.DAT VVVMD0 0142969600196608 DV00 017IMAGE.DAT
For LAYER_1
DDP 2.10 DV2021OB00V0000 VVVMD2 0000001600193024 DV00 017CONTROL.DAT VVVMD0 0074169601626303 DV00 017IMAGE.DAT
and the respective
IMAGE.DAT, containing the image for that layer.
Size and content of this image does differ from that built by ImageBurn, though.
-
After another short session of burns the error was still there with 2.4.4.0, Dell and AD7173A ,
but intermittent.
The purged filter driver load order seemed to help, but not completely.
In the end this occurrence seemed to be limited only to the AD 7173 A,
which is sitting in a Plextor External DriveBox, connected via Firewire 1394.
(Controller chipset: Initio INIC-1530L A112P, Agere FW802B)
(Here I replaced the original Plextor PX-740A drive with the AD7173 A
years ago and only used this drive for reading.
By chance a week ago I seem to have changed my mind
and started to use this drive for burning DVD+R DL,
because it would allow to burn MKM-001 (2.4x) at 8x)
The ND3520 drives do work properly now with 2.4.4.0.
These are sitting in 2 Mapower Boxes MAP H51C1P
(Controller chipset: Prolific PL-3507, Agere L-FW802C)
connected via Firewire 1394.
When I searched for a firmware update for the AD 7173 A(mine is 1.01)
I found that 1.04 is the current one and decided to update firmware.
Trying to flash via firewire failed.
cdfraks report that flashing may not be successful while using Firewire connection
because of commands that are unsupported within a 1394 connection.
Maybe this could be a hint to the developers and betatesters,
maybe there is a command used
which in coincidence with a firewire connection to this particular chipset may lead to a failure.
Maybe the drive is fishy, not sure yet. At least reading is fast and reliable.
I will have to build the drive into a friend's TowerPC to flash up to 1.04
and will report back in a few days.
-
After backinstalling to 2.4.2.0 on Dell (no removing of filters yet)
4 burns went fine, the fifth stalled as described.
In 2.4.2.0 removed 3 Lower Class Filters
cdrblock(Canopus from Edius 4.61),
clbstor(Cyberlink from PowerDirector7),
cdrbsdrv(B's Recorder from TAW4).
SiRemFil I will still need for connecting BD-Writer via eSATA.
PxHelp20 I may need for direct BD-Writing from DVDitProHD
Then installed 2.4.4.0 over 2.4.2.0, kept settings, checked filters,
filter settings were correctly taken over from 2.4.2.0
Start Burn, Writing Lead-in ok. Writing sectors ok.
Seems solved, now using 2.4.4.0 !
Again, Many thanks for a fast and really professional solution !
My donation was not in vain.
(If I compare this to the non-existent support from heavy payware companies
like Adobe, Sony, Sonic...better keep my mouth shut.)
BTW, the 2nd system (Toshiba) does not have any of these authoring and writing apps installed,
only AnyDVDHD, but was the first system I found that 2.4.4.0 issue on, will check this later...
-
Many thanks for the fast response !
I will remove all 3 Lowers first,
I don't need nor want my authoring apps to write discs, better leave this to ImgBurn;-)
On Dell I kept SP2 for fear reasons...
Many expensive pieces of video and authoring apps.
Yes, I really bought this stuff, and it takes 2 weeks to rebuild and fine-tune that system if something giggles.
-
Oops. More than I expected to have.
I remembered 2 Uppers and 2 Lowers in the beginning of using ImgBurn back in 2006.
Good idea !
===============================================
Filter Driver Load Order - ImgBurn v2.4.2.0
===============================================
Upper Device Filter: redbook
Upper Class Filter: SiRemFil
Device: CD/DVD-ROM Device
Lower Class Filter: cdrblock
Lower Class Filter: clbstor
Lower Class Filter: cdrbsdrv
Lower Class Filter: PxHelp20
Lower Class Filter: AnyDVD
Lower Device Filter: imapi
Filter Name: redbook
File Name: C:\WINDOWS\system32\DRIVERS\redbook.sys
File Version: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
File Description: Redbook-Audiofiltertreiber
Product Name: Betriebssystem Microsoft
-
Was ok in 2.4.2.0 on all systems some hundred burns,
Installing 2.4.4.0. broke these.
Installed 2.4.4.0 over 2.4.2.0
Kept existing settings.
Checked on two systems, similar results:
1.:Dell XPS M1710 running WinXPPro SP2,
External Drive AD7173 via Firewire 1394.
AnyDVDHD autostarted, but not active.
2.:Toshiba Satellite 5200-801 running WinXPPro SP3,
External Drive ND-3520 via Firewire 1394.
AnyDVDHD autostarted, but not active.
Mode: Build to Drive
DVD-Video VIDEO_TS folder
on Verbatim DVD-R blanks No.43533 (MCC03RG20).
Burning starts as usual...Filling buffer.
Writing Lead-In.
Drive seems to write Lead-In but never returns.
ImgBurn is stuck there.
Manual Abort request after a minute acknowledged,
but drive won't react and ImgBurn is again stuck there.
Have to disconnect firewire drive connection manually to make Imgburn return and close with an error.
Power-down external drive. Power-up. Open tray.
The disc contains a burned track of 2mm width.
Checked this first with my customised favourite settings.
Then with default settings.
Uninstalling 2.4.4.0.
No power-down.
Installing back to 2.4.2.0.
Reloading my settings from previously exported 2.4.2.0 regkey.
Now Failure again in Dell !
OK in Toshiba after power-down/power-up.
AnyDVDHD was autostarted on these systems, but not activated.
Next I will try Dell with AnyDVDHD not autostarted,
Imgburn uninstall, PC PowerDown, PowerUp.
Reporting later...
and after system powerdown/powerup
ImgBurn 2.4.2.0 is running ok as before.
So 2.4.4.0 seems to bring something in here...
I/OError via eSATA on DVD+R only, DVD-R is fine
in ImgBurn Bugs
Posted · Edited by Emulgator
Win7U64SP1 Notebook, ImgBurn 2.5.8.0, 4 optical drives in total
1 internal BD-RE (UJ-240)
Dawicontrol ExpressCard (SiI3132) to 2x eSATA (1 used for external writers)->
Port Multiplier box 1x eSATA to 4x eSATA
3 eSATA cables to 3 external writers:
2x DVD+-RW NEC 3520 (each with eSATA to PATA plug-on board in external enclosure)
1x BD-DE Pioneer BDR-208 native SATA via eSATA in external enclosure.
All 4 drives write DVD-R and DVD+R DL without problems.
DVD+R can be written only on the notebook's internal drive (UJ-240)
DVD+R on all 3 external drives:
Shortly after lead-in writing is attempted these report I/O Error, device removal, anything and abort.
The NEC drives say they would finalise and write nothing (disc is still blank),
the BDR-208 says he would finalise and indeed wastes the disc writing an estimated 1GB track.