LIGHTNING UK!
-
Posts
30,521 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by LIGHTNING UK!
-
-
M4a seems to have 2 codecs associated with it. AAC and ALAC. So even if something says it supports M4A, it doesn’t meant it’ll support both codecs.
As your OS install can’t decode the files you’re feeding it (well, feeding into ImgBurn), that tells us you need another codec installed on the system.
It sounds like you’ve got it working ok now having installed that DirectShow filter, so that’s good.
-
None of these packages are from Microsoft.
Anything not supported ‘out of the box’ requires 3rd party DirectShow filters.
Having Googled a bit for ‘alac DirectShow filter’, this one got mentioned a lot.
http://dsp-worx.de/?n=15 -
What type of audio files are you actually trying to use? File extension / codec please.
-
That disc only has a single, mode 1 track on it, so ISO would be the default extension / format.
Iso is mode 1 / ‘user data’ of a sector - 2048 bytes per sector.
Bin is for raw sectors - 2352 bytes per sector.
That’s why the bin is bigger. -
There’s overhead of the file system(s) you decide to use on the disc.
-
Were you using the same drive you're having issues with in one of your threads?
Beyond that, I've no idea.
-
DVD-R holds more.
Same for DVD-RW.As taken from the Media Testing section of the forum...
DVD-R
Free Sectors: 2,298,496DVD+R
Free Sectors: 2,295,104DVD-RW
Free Sectors: 2,298,496DVD+RW
Free Sectors: 2,295,104 -
I figured you'd just zip it over multiple floppies or something.
Another option would be to remove the hdd from that machine, hook it up to another (more recent one!) and back the drive up properly.
You may run into issue with the program not being able to read some of the 'in use' files if you're trying to backup the OS drive from within that same OS. ImgBurn is not a hdd backup tool.
-
I pretty sure even the latest (2.5.8.0) works on 98SE.
-
Discovery mode is for zero filling discs (burning all zeros to them) - used when running disc quality checks.
Don’t use it for anything beyond that.
The size reported by the program is what the drive reports. If it’s changing, either your drive is messed up or you’ve got some 3rd party software messing around with the response. The program isn’t actually ‘counting’ the sectors itself. -
It depends on how your player plays them.
It might read their ID3 tags and arrange them into albums. It might then order them by track number from the ID3 tag or by name if that isn't available.
At the end of the day, it's a data disc. The files are sorted into alphabetical order within the file system. If your player doesn't make use of the ID3 tags, that's the order it'll end up playing them in and that's when renaming the files to fit your desired order is required.
If media player works for what you want, it would make sense to use that instead.
-
Unfortunately, there’s no way to specify the name of the data file when using CCD. That’s why ImgBurn has to rename its usual ‘bin’ file to ‘img’. The CUE file can then just be told to use the img file.
Back when ImgBurn (or perhaps its predecessor) came about, DAEMON Tools was a much simpler application. It grew and grew, had a few driver issues (which slowed down real optical drives) and people liked the basic nature of virtual clone drive. There’s no doubt that Daemon tools is more capable and fully featured (both in terms of features and its ability to faithfully emulate a physical drive), but if VCD works for you, that’s great. -
2 minutes ago, Ken852 said:
Is there any advantage to using IMG/CCD over BIN/CUE?
I have installed Daemon Tools Lite 10.14 and I was able to mount the BIN/CUE files and have it present as Audio CD in File Explorer and have it play some tunes off of it in VLC.
I'm supposed to point Daemon Tools at the CUE file rather than the BIN file? By trying to mount the BIN file, I got the same error as I got previously using Virtual CloneDrive ("disc might be corrupt"). But selecting the CUE file instead made all the difference! I can tell now why I must keep the CUE files. Good lesson!
Similarly, with IMG/CCD files I need to point at the CCD file rather than the IMG file? I had ImgBurn write a second set of files for me, this time selecting IMG for file destination. It made IMG/CUE files instead. Little did I know I have to enable the CCD box in settings. Thanks @dbmin
It's past midnight here, I will do some more testing in evening tomorrow.
Not where ImgBurn is concerned, no.
BIN/CUE is what ImgBurn started off supporting for CD images. I added support for CCD purely so people had the option of using VirtualCloneDrive instead of DAEMON Tools.
Yes, you should always point the tools at the info files (CUE/CCD/MDS etc) rather than the data files (BIN/IMG/MDF). Otherwise, you're just giving them a load of data without any info on how to interpret it.
-
How do you figure it's 2352 bytes per sector? I'm just curious. I have seen mentions of 2048 bytes per sector for CD discs on various forums and other places. For the disc I used in my example the reported size is 434108416 bytes and number of sectors is 211967. That comes out to 2048 bytes per sector. I'm no expert, but that would seem fitting for an ISO file? I know nothing about sessions, tracks and indexes. So in regard to these details it may be more fitting to use BIN/CUE files.
That’s just what CDDA is. Check the MMC specs for optical drives and the various types of sectors used for what can be stored on a CD.
Please just take it from me that the program is telling the truth. Don’t attempt to read an audio disc to a single file that you’ve given the ‘iso’ extension to. It won’t work... in anything.
Bin/cue is very common for anything CD related. Bin/cue can be mounted in lots of virtual drive programs (the main one is / was Daemon Tools).
Virtual CloneDrive is by the same people that made CloneCD, hence why it supports CCD/IMG instead, rather than Bin/cue.
A virtual drive program that can fully process a bin/cue combo and emulate an optical drive/disc with it will be usable in the same way as if you had the original disc in a real optical drive.
-
An ISO is dumb. It's a basic 2048 bytes per sector (purely 'user data') dump of the disc. It knows nothing of sessions, tracks, indexes etc and is always assumed to be single session, single track.
Audio discs are complex. 2352 bytes per sector and you have the option of multiple tracks and multiple index points. That's why BIN/CUE is used. The CUE file is required for all of the extra info about the disc and the BIN is a 2352 bytes per sector dump of the disc. Without the CUE, your BIN file is useless - do not delete it.
ImgBurn can also create a CCD file - which is very similar in function to the CUE file. VirtualCloneDrive doesn't actually (fully) support BIN/CUE, which is why ImgBurn can make CCD/IMG - VCDs native format.
-
Post the log please.
Chances are, you're trying to erase a disc that can't be erased. Only rewritable discs can be erased, not your standard CD-R/DVD-R/DVD+R/BD-R.
-
No. I've been very busy for the past 6 or 7 years
The version with that in will be released one day. Definitely this year.
-
Sorry, no. ImgBurn can't help you with this.
You've basically made a multisession disc.
ImgBurn can send the commands to close tracks, sessions, discs etc.... but they're only useful for when those commands didn't work the first time around.
Your disc has been left unfinalised and with a new session open (that you can add data to) on purpose. The only way to finalise it is to add more data to it (again, can't be done with ImgBurn) and then ensure it's closed/finalised - do not let the software make yet another new session.
It might just be easier to make a new disc. Use ImgBurn in build mode, add your MP3 files and burn.
-
You could try enabling the 'Perform OPC Before Write' option in the settings to see if that helps.
Failing that, if your drive can't seem to burn the discs you're (MID/Disc ID: MBI 01RG40) using, try some different ones.
-
The program reads the sectors in chunks. When the drive returns an error, it drops down to reading them 1 at a time so it can pick out the bad one.
What’s happened here is that the drive errored out when reading the chunk, but then succeeded to read them all when doing it 1 by 1.
I would the disc has the potential to be unreliable. Maybe do a stand-alone verify on it and see if the drive fails to read it again in those same locations. -
If you’re trying to burn an XP install CD, why aren’t you following the XP guide instead of the Vista+ one?
How to create a Windows XP installation disc (bootable) using ImgBurn.
https://forum.imgburn.com/index.php?/topic/11190-How-to-create-a-Windows-XP-installation-disc-%28bootable%29-using-ImgBurn -
That drive is a dvd writer, not a BD writer.
It only ‘reads’ bd-roms.
-
I've checked the code and can't see any obvious way to silence those I'm afraid.
-
You're going to need a drive that can overburn DVD+R DL media in order to burn that disc.
https://www.vinpowerdigital.com/t/categories/Optical-Drives
458 MB BIN or 399 MB ISO?
in ImgBurn Support
Posted
It's probably easier if you just google for the various sector formats/structures possible on a CD. There's Mode 1, Mode 2 Form 1, Mode 2 Form 2 and CD-DA.
If you look at the TOC info, you'll see if it has multiple tracks or a non Mode 1 track.
If it isn't single session/track/mode 1, use BIN.
That's what the program defaults to anyway, so just go with what it suggests.
If you want to faithfully reproduce (or emulate) the disc, you should keep its sectors in the format they're supposed to be in.