I had some probs with K3b at one point and just used dd to make an image copies of a couple of DVDs. Now that I’ve got K3b ripping DVDs again I want to rip these images.I’d burn the images onto DVDs but they’re around 6.5Gb and won’t fit on a standard DVD. Is there any way I can convince K3b that a file is a device?
I do not realy understand you. You copied the DVDs using dd. How comes your copy is now bigger then fits on a DVD? IMHO, you first hve to find out what went wrong here before you continue.
What was on the DVDs? When that is a file system (ISO probably), and the copied file is still containing that file system (but mark my remark above) you could try to mount the copied file on a directory via the loop device.
Suggestion somehing like
mount <copy-file-of-dvd> /mnt -t iso9660 -o loop
And about this:
Is there any way I can convince K3b that a file is a device?
You should understand that in Unix/Linux it is the other way around. Devices are seen as files. These are called “device special files” It is thus that a disk partition is seen as e.g.the file* /dev/sdb2*. And in this case you probably want to use your copied file as a device special file. And that as why I suggest to mount the copied file using the loop device.
Based on the size you mentioned, it sounds like you need to use Dual Layer DVD’s which are 8.5 GB each as I remember. I have not just copied a DVD image to my hard drive directly and always use k9copy for such DVD copy duties. But, to make a copy of a factory made DVD without compression, for personnel backup only, you need a DVD-DL disk and drive.
Thank You,
-
The DVDs were presumably dual-layer which is why they’re bigger than 4Gb
-
Mounting the iso doesn’t work - k3b still doesn’t offer the option to rip them - I’ve tried that
-
I know that *nix sees devices as files but k3b doesn’t give any way of opening a file as a device - I’m sure that in an earlier incarnation (probably KDE3) it did do this.
Dual-layer is also my assumption.
My DVD writer will handle dual-layer DVDs but a) I don’t have any and b) I’d only be making a physical copy for the sake of ripping it.
ISTR that k3b did (once upon a time) have the option to rip an iso image but now only rips physical DVDs
I’m also fairly sure that it was possible to define the devices by hand (or maybe that’s how I did rip ISOs before) but the device configuration is automatic now.
Mounting the ISO doesn’t help
I am still a bit lost about what you want and what goes wrong. Especialy because you only say things like:
Mounting the ISO doesn’t help
Does this imply that my question to you if the DVD contained an ISO file system is to be answered by you with: Yes? (you did not).
Does that mean that the mounting is OK, but that then you can not do with the files in there what you want, or is the mounting going wrong. In the last case my assumption is that you would at least report that with the appropriate session within CODE tags here. Thus we can realy see what happens.
I am also not quite sure about what you want to do: ripping mage files with k3b. I maybe a noob about ripping, but I thought that this is about e.g. making files in MPEG or OGG format from an audio CD. Now when you have an CD/DVD with an ISO file system, all on there is allready in the form of files. Thus “ripping” is no more then copying files from the ISO file system to another place (on another file system). Not what I call ripping, just copying. Does this mean that I am indeed completly misunderstanding about what you want?
On 2012-07-22 09:16, fudokai wrote:
>
> 1. The DVDs were presumably dual-layer which is why they’re bigger
> than 4Gb
>
> 2. Mounting the iso doesn’t work - k3b still doesn’t offer the option
> to rip them - I’ve tried that
I don’t understand. Ripping an ISO image is absurd, the ISO is already the result of ripping
the DVD. You can not rip it a second time, it is already ripped.
What is it you really want to do?
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Does this men you have the same question I have? I feel reassured by the fact that I am not the only one who does not understand this.
The OP is referring to K3B’s option to Extract Video form a DVD, i.e., convert to xvid or such.
OOTB K3B won’t allow you to select a DVD device, only the ones already recognized by the system as such.
I don’t know how to do this with K3B. When I have a DVD iso I want to convert to xvid or mp4 or whatever, ripping subtitles and multiple audio tracks if desired, I use Fairuse Wizard 2, a windows app that runs nicely in linux under wine. You might want to give it a try.
Note that Fairuse Wizard is a well-behaved app, it won’t convert protected (comercial) DVDs, although most DVD-to-ISO rippers remove scrambling when ripping.
On 2012-07-22 15:26, hcvv wrote:
> Does this men you have the same question I have? I feel reassured by
> the fact that I am not the only one who does not understand this.
Right 
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 2012-07-22 15:56, brunomcl wrote:
>
> robin_listas;2475780 Wrote:
>> What is it you really want to do?
>
> The OP is referring to K3B’s option to Extract Video form a DVD, i.e.,
> convert to xvid or such.
Ah!
I do not know if k3b would see a loop mounted iso image, probably not. Maybe if it is “mounted”
on /media/dvd? Maybe other ripping programs might, like ripit.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
This might be an needless remark, but IMHO the OP still has not confirmed that his file contains an ISO, nor has he posted what happens when he tries to loop mount it as an ISO file system. Thus we are now on tha way of guessing about guessing 
I also have a bash script you can use to automate the mounting of ISO files if you would like to try it: ISOMount - Allows you to mount and Browse ISO Files - Version 1.00 - Blogs - openSUSE Forums
Thank You,
Sorry, been busy with other things and not had chance to get back to this list.
Yes, what I’m trying to do is convert an ISO to avi or equivalent.
I have straight bit-by-bit copy of a DVD using
dd if=/dev/sr0 of=image.iso bs=1M
The original DVD must have been dual layer hence the image file being the size it is.
K3b will only recognise physical devices so mounting the ISO as a loop device doesn’t mean that k3b will see it as a physical device.
As I say I seem to remember that it was once possible in the configuration section of k3b to set a file as a device which k3b would then offer to rip as if it was a physical DVD.
These days k3b is much cleverer and finds the physical devices itself and there’s no way I know of to convince it to access as file instead - my question was to see if anyone knew of a way (outside of k3b) to somehow make an ISO file appear as a physical device - as I say mounting won’t work.
I managed to rip/extract the ISO file in the end from the CLI using transcode by looking through the k3b logs and finding a successful transcode command and editing that.
The ISO file was generated with
dd if=/dev/sr0 of=image.iso bs=1M
So it’s a straight bit-by-bit copy of the DVD which can be mounted as a loop device and media players (vlc, kaffeine etc.) can access and play.
K3b’s DVD ripping tool simply doesn’t see it even if it’s mounted as k3b only recognises physical devices and there’s no way I know of to get it to work with a DVD image.
Maybe I’m just using the term iso incorrectly
When you used dd as you said, it is indeed a straight bit to bit copy. But that said, it does say nothing about what it is. When it wasn’t an ISO, it will not become one by this dd action. And when it was a ISO, the copy is an ISO file system within one file.
In the latter case, it can be loop mounted ( which means that it is handled if the file was a device). And as you say that that mounting succeeds, then you prove it is an ISO.
BUT, while you say the mounting succeeds, you still have not showed that and thus for us it is not proven!. You have to post here the mount statement, of course it’s output and then an* ls -l *of the mountpoint. This will let us (and you) see if it is mounted and what is there.
When it is mounted it is simply part of the directory tree (up from the mountpoint). And is thus to be handled as directories and files.
As several people have tried to explain to you, if that is the case, there is no need for ripping at all, because it is allready files (and when you are correct that there should be music/moviies there, there could be MPEG, etc. files).
Please try to reread the whole thread. The fact that you was away all the time does not mean that we all have to run in circles and have to ask and explain the same things again.
Well, that would explain a lot, but it would make all talking to you as done in earlier posts rather futile. Thus please try to find some study material about “ISO 9660 file system” on e.g. Wikipedia. And when you think you do not understand enough from that, ask here. But do not start a conversation were each partner has a different definition about terms crucial in that conversation.
If you can mount the ISO image, you would copy the files from within it to somewhere else. You should be careful with the likes of dd which can copy bytes directly to sectors on your disk partition, depending on how you are using it. It may not have the result you had hoped for.
Thank You,
On 2012-07-28 17:26, fudokai wrote:
> Yes, what I’m trying to do is convert an ISO to avi or equivalent.
> I have straight bit-by-bit copy of a DVD using
> Code:
> --------------------
> dd if=/dev/sr0 of=image.iso bs=1M
> --------------------
I see.
> The original DVD must have been dual layer hence the image file being
> the size it is.
Possibly.
> K3b will only recognise physical devices so mounting the ISO as a loop
> device doesn’t mean that k3b will see it as a physical device.
Clever tools are a nuisance some times
> As I say I seem to remember that it was once possible in the
> configuration section of k3b to set a file as a device which k3b would
> then offer to rip as if it was a physical DVD.
I assume you can not point k3b to /dev/loopX ?
> I managed to rip/extract the ISO file in the end from the CLI using
> transcode by looking through the k3b logs and finding a successful
> transcode command and editing that.
Yes, that’s the way to go. I mentioned ripit, a perl script IIRC.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)