|
Unofficial CD-Architect Supported Drives List maintained by Brent Aliverti Last updated 12 Nov 2002 LATEST NEWS After discontinuing it two years ago, Sonic Foundry has listened to customer demand and released a brand-new version of CD Architect. I haven't checked it out yet, but it looks to be a nice update, introducing a few new features, although not CD-Text (yet). I'll keep this page up indefinitely, as it still has some useful info pertaining to the previous version of CD Architect (4.0). Thanks for bringing back this great tool Sonic Foundry! INTRODUCTION In late 2000, Sonic Foundry quietly discontinued their extremely powerful and easy-to-use CD authoring software, CD Architect. This software worked hand-in-hand with SoundForge 4.5 and together they provided a complete solution for mastering DAO (Disk-At-Once) CDRs and creating replication-ready CD masters. Sonic Foundry no longer offers professional CD burning capabilities in any of its products. However, the most recent version of SoundForge (version 5.0) does contain the less desirable ability to burn TAO (track-at-once) CDRs. When CD Architect was discontinued, Sonic Foundry ceased issuing updates to support new CD burners. They maintain a list of officially supported drives but those drives are all older models at this point. They have become increasingly difficult to find, and they are old-technology, with low burn speeds and lacking current desirable features such as "burn-proof" technology. Luckily, the final update of CD Architect (4.0g) allows the option of selecting a generic "SCSI MMC compatible" or "ATAPI(IDE) MMC compatible" drive. MMC is short for "Multi Media Command" and is a standard that was implemented a few years back to make it easier for CD software to communicate with the many brands of CD burners on the market. Theoretically, it means that any piece of software written to comply with MMC-compatible drives should work 100% with any drive claiming to be MMC-compliant. In practice however, at least with regards to CD Architect, this is not the case. The most commonly reported issues with using the "MMC Compliant" workaround are incorrect time remaing displays during burning, and being limited to "Max" for burn-speed options. Other than that, most people are reporting successful burns. The purpose of this webpage is to document which current models of CD burners are supported by CD Architect, and what some of the caveats may be. It should be underscored that this page is completely unofficial and not connected with Sonic Foundry (though the idea of creating this page was suggested by a Sonic Foundry employee). Thanks to all who have already submitted their specs!
Anyone that is using CD Architect with a current model "officially unsupported" drive is urged to help add to the user knowledge base by answering the following questions and submitting your answers here. NOTE: This email address is only for questionnaire submissions. For other issues, see other resources at bottom of page. Thanks in advance to all those who submit information! Regards, Brent 1) Manufacturer and Model # of CD burner: 2) Type of Interface: (IDE/SCSI/USB/FIREWIRE/PCMCIA) 2b) If SCSI, indicate "internal or external", type of SCSI card, and manufacturer
3) Maximum stated CDR burn speed: 6) Windows O/S: (95, 98, 98SE, ME, NT, 2000, XP) 7) Is drive basically compatible with CD Architect via MMC?: (Yes/No) 7b) What features are not supported? What tweaks/workarounds did you implement to make it work or improve performance? 8) Submitted by: (your name, email address, and/or handle)
OTHER INFORMATION These tips were submitted by other users: There is a technique I have used for some time to get CD Architect to work with fairly recent drives; I suspect it is confined to MMC compliant drives and will undoubtedly attract sneers of derision from the official support folks but the bottom line it that it works - and is simple to implement! In the CDA main directory you will find a large number of files with the .CDD extension. These contain a lot of tables and quite probably executable code peculiar to individual drives. The files of interest in this case are ATAPIMMC.CDD and SCSIMMC.CDD. Open the file of interest with a hex editor and search for, say, PLEXTOR. Very soon you will come across some table entries for the Plextor drives supported by that module. Simply modify the drive identification code to that of your modern drive; job done!
Using this method I have achieved 100% success in getting CDA to support a
Yamaha 8424, and Plextor models 1210A and 8220. It is only with my most
recent acquisition (Plextor 2410A) that I've encountered a problem. As I
said, up to now my other drives have all worked 100% including the selection
of available burn speeds - I guess these are read from the target drive. But
my newest drive only allows a speed of 'max' and it gets the 'time remaining'
calculations all wrong. However, the resultant burn is fine, given
sufficiently good media. I assume that CDA in its quaint old way doesn't
believe that a drive could possibly report '24' as a burning speed :-)
All modern Plextor IDE CDRWs work well in CDA. You may want to note that it is unlikely CDA will work at all in Windows XP. The CDPBurn app that Colin Hill wrote (and has posted about on this group) works great in XP. I just found that out last night, so XP and CDA can work together with the help of this app. -SR RELATED LINKS AND RESOURCES
Sonic Foundry CD Architect 5.0
back to antimatter containment field
|