Jump to content

dftf

Members
  • Content Count

    8
  • Joined

  • Last visited

About dftf

  • Rank
    Newbie
  1. If it's not necessary perhaps remove it from http://daily.cdburnerxp.se/ then? It is silly to bump the version number when there have been no changes -- you should just freeze the version number at whenever the last code change was made. I can't think of any other company which does this except when there have been actual code changes to older, supported versions (e.g. Microsoft with Service Packs for older products; Java when 1.6 was still updated alongside 1.7; Adobe with older versions of Reader for Linux, old versions of Mac or Windows 2000). As the 4.4.x series will ask you to auto-u
  2. Looking back through this forum I found a number of posts where this change has caught users out: https://forum.cdburnerxp.se/topic/9469-problem-with-reading-burned-cd-with-mp3-files-in-car-players/ https://forum.cdburnerxp.se/topic/9444-cd-plays-on-computer-but-not-car/ https://forum.cdburnerxp.se/topic/9434-mp3-cd-udf-format-instead-of-cdfs/ https://forum.cdburnerxp.se/topic/9389-dont-burn-correctly-mp3-files-for-many-weeks/ https://forum.cdburnerxp.se/topic/9321-cd-r-wont-play-in-car-or-computer/ https://forum.cdburnerxp.se/topic/9313-problem-playing-cd-in-car/ It isn't good whe
  3. The reason for the report is that the 4.4.x version is still made available, and due to some of the issues in 4.5.x (e.g. cannot import older multi-session discs, no overburning) some people will keep using it. This post, for example, you actively advise a user to download an older version due to 4.5.x not being able to import their older multisession discs: https://forum.cdburnerxp.se/topic/9145-version-4503661/?hl=4.5 As does someone else in this post: https://forum.cdburnerxp.se/topic/9360-why-feature-removed-for-new-version/?hl=4.5 I don't feel it's wise to encourage users to
  4. Or is it this bug I previously reported lingering on: https://forum.cdburnerxp.se/topic/9115-c-grab-disc-file-type-isomds-dropdown-chooses-wrong-format/ I can't say I've ever been able to repeat that but it is interesting in 4.4.2.4376 that choosing "ISO" as the rip format seems to give you two files (".iso.mdf" and ".iso.mds"), which the larger one renamed to ".iso" doesn't work. But if you ask it to rip in MDS format, then rename the ".MDS" extension to ".ISO" -- VirtualBox mounts it fine. So... is the "MDS" setting in the 4.4.x series actually producing an ISO file but giving it an M
  5. The 4.4 series is still being actively updated, when 4.5 is now the current one. This creates two areas of confusion, I feel: • Are there features the 4.4 branch has the 4.5 doesn't, or is it still around due to compatiblity reasons? • Does the Development Log here (http://cdburnerxp.se/development) only apply to 4.5 series or 4.4 as well? Could anyone explain why 4.4 may still be required? And if the Development Log does not apply, does anyone know if a change log for the 4.4. series is available anywhere?
  6. A friend uses CDBurnerXP to create data discs with MP3 music files on to play in their car stereo. Recently, the discs have all come up as "Disc Not Recognised" in the car CD deck. My friend asked me why this might be. It seems that the car CD deck doesn't support UDF format discs, only ISO 9660. He told me he had recently had an update message from CDBurnerXP and updated (I'm sensing from a 4.4.x version to a 4.5.x version). It seems that while the 4.4.x series used "ISO 9660/Joilet" as the default format, 4.5.x now uses "UDF 1.02". After asking my friend to go to Disc > Change
  7. Reporting a possible ISO ripping bug. I've ripped some Linux distros from discs to ISO files on my computer using the latest versions of CDBurnerXP. Frequently getting issues with the 4.4.x branch, but never with the 4.5.x branch. CDBurnerXP 4.4.2.4376 • All images are ripped as two files, "<name of file>.iso.mdf" (the image) and "<name of file>.iso.mds" (a descriptor file). • Renaming "<file>.iso.mdf" to just "<file>.iso" then makes Windows treat it as an ISO, and software like CDBurnerXP, Windows Disc Image Burner and PowerArchiver load them witho
  8. Hi All A minor issue in CDBurnerXP -- if you go to rip a disc to an image whichever format you choose in the "File Type" dropdown in the Copy Disc dialog the opposite format is used instead (see screenshot). I'm not sure if I choose "ISO (Single Track)" in this example where CDBurnerXP is ripping in ISO format, but incorrectly giving the file an .MDS extension or if it actually is ripping in the wrong format for each selection. Either-way it's confusing and could do with being addressed. I am seeing this as-of version 4.4.2.3613. Kind regards dftf
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.