Newbie trying to see VDC and DVD with Totem.
Brian Durant
globetrotterdk at gmail.com
Tue Feb 15 16:17:50 UTC 2005
Jon and I have had a little one on one offlist. It seems HFS may have
something to do with this problem. Anyone else seen this in dmesg?
Cheers,
Brian
On Tue, 15 Feb 2005 16:03:05 +0000, Jon Dixon <dixon.jon at gmail.com> wrote:
> I've seen those hdX messages on mine too, so I'll check a VCD when I
> get home. Am working at the minute.
>
> Odd that it appears to try and use HFS for your sr0 - maybe it's just
> a common message that we never really notice but it could be worth
> googling or posting about it to the list.
>
> On Tue, 15 Feb 2005 22:57:08 +0700, Brian Durant
> <globetrotterdk at gmail.com> wrote:
> > Sorry to post all of the following from dmesg, but it could be of
> > interest. hdg and hdh are my internal CD/DVD drives and I believe that
> > sr0 is the USB 2 CD/DVD drive. I have something installed to read Mac
> > drives that I don't really use. It looks like there is something going
> > on with that doesn't it?:
> >
> > dev hdg, sector 152
> > Buffer I/O error on device hdg, logical block 38
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 156
> > Buffer I/O error on device hdg, logical block 39
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 160
> > Buffer I/O error on device hdg, logical block 40
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 164
> > Buffer I/O error on device hdg, logical block 41
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 168
> > Buffer I/O error on device hdg, logical block 42
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 172
> > Buffer I/O error on device hdg, logical block 43
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 176
> > Buffer I/O error on device hdg, logical block 44
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 180
> > Buffer I/O error on device hdg, logical block 45
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 184
> > Buffer I/O error on device hdg, logical block 46
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 188
> > Buffer I/O error on device hdg, logical block 47
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4328
> > Buffer I/O error on device hdg, logical block 1082
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4332
> > Buffer I/O error on device hdg, logical block 1083
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4336
> > Buffer I/O error on device hdg, logical block 1084
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4340
> > Buffer I/O error on device hdg, logical block 1085
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4344
> > Buffer I/O error on device hdg, logical block 1086
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4348
> > Buffer I/O error on device hdg, logical block 1087
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4352
> > Buffer I/O error on device hdg, logical block 1088
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4356
> > Buffer I/O error on device hdg, logical block 1089
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4360
> > Buffer I/O error on device hdg, logical block 1090
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4364
> > Buffer I/O error on device hdg, logical block 1091
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4368
> > Buffer I/O error on device hdg, logical block 1092
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4372
> > Buffer I/O error on device hdg, logical block 1093
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4376
> > Buffer I/O error on device hdg, logical block 1094
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4380
> > Buffer I/O error on device hdg, logical block 1095
> > hdg: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
> > hdg: media error (bad sector): error=0x30
> > end_request: I/O error, dev hdg, sector 4384
> > Buffer I/O error on device hdg, logical block 1096
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4388
> > Buffer I/O error on device hdg, logical block 1097
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4392
> > Buffer I/O error on device hdg, logical block 1098
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4396
> > Buffer I/O error on device hdg, logical block 1099
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4400
> > Buffer I/O error on device hdg, logical block 1100
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4404
> > Buffer I/O error on device hdg, logical block 1101
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4408
> > Buffer I/O error on device hdg, logical block 1102
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4412
> > Buffer I/O error on device hdg, logical block 1103
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4416
> > Buffer I/O error on device hdg, logical block 1104
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4420
> > Buffer I/O error on device hdg, logical block 1105
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4424
> > Buffer I/O error on device hdg, logical block 1106
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4428
> > Buffer I/O error on device hdg, logical block 1107
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4432
> > Buffer I/O error on device hdg, logical block 1108
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4436
> > Buffer I/O error on device hdg, logical block 1109
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4440
> > Buffer I/O error on device hdg, logical block 1110
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4444
> > Buffer I/O error on device hdg, logical block 1111
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
> > hdg: media error (bad sector): error=0x30
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
> > hdg: media error (bad sector): error=0x30
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4320
> > Buffer I/O error on device hdg, logical block 1080
> > hdg: command error: status=0x51 { DriveReady SeekComplete Error }
> > hdg: command error: error=0x54
> > end_request: I/O error, dev hdg, sector 4324
> > Buffer I/O error on device hdg, logical block 1081
> > cdrom: hdg: mrw address space DMA selected
> > cdrom: hdg: mrw address space DMA selected
> > cdrom: This disc doesn't have any tracks I recognize!
> > VFS: Can't find a HFS filesystem on dev sr0.
> > SGI XFS with ACLs, security attributes, realtime, large block numbers,
> > no debug enabled
> > SGI XFS Quota Management subsystem
> > VFS: Can't find a HFS filesystem on dev sr0.
> > cdrom: This disc doesn't have any tracks I recognize!
> > cdrom: This disc doesn't have any tracks I recognize!
> >
> > Cheers,
> >
> > Brian
> >
> > On Tue, 15 Feb 2005 15:25:32 +0000, Jon Dixon <dixon.jon at gmail.com> wrote:
> > > If Ubuntu picks up the external drive properly, any disc you insert
> > > should behave the same way as with the internal ATAPI devices.
> > >
> > > If you check dmesg, it should tell you what name is assigned to the device.
> > >
> > > Then do a : mount -t iso9660 /device/name /mount/point
> > >
> > > Should hopefully appear on the desktop then.
> > >
> > > On Tue, 15 Feb 2005 22:20:26 +0700, Brian Durant
> > > <globetrotterdk at gmail.com> wrote:
> > > > One thing I could try is to connect a USB 2 CD-R, RW, DVD-R to see if
> > > > I get the same problem with that. The other 2 are internal ATAPI
> > > > drives, I believe. Actually, I have connected it but only audio CDs
> > > > and CD-R media pop up (CD Creator window). Not sure where it is
> > > > located or how to mount a VCD or DVD to the desktop to try totem-xine
> > > > with it.
> > > >
> > > > Cheers,
> > > >
> > > > Brian
> > > >
> > > >
> > > > On Tue, 15 Feb 2005 15:07:39 +0000, Jon Dixon <dixon.jon at gmail.com> wrote:
> > > > > Not sure what else to suggest.
> > > > >
> > > > > Always difficult when the example I have works.
> > > > >
> > > > > Hopefully someone else will join in on our conversation :)
> > > > >
> > > > > On Tue, 15 Feb 2005 21:59:31 +0700, Brian Durant
> > > > > <globetrotterdk at gmail.com> wrote:
> > > > > > No, I get the same result on both. While I don't have mplayer, I have
> > > > > > downloaded what I believe to be all of the codecses (?) codecsi (?)
> > > > > > that could possibly be used by Mplyer or any other player to get
> > > > > > VCD/DVD playback. That includes the win32 codecs.
> > > > > >
> > > > > > Cheers,
> > > > > >
> > > > > > Brian
> > > > > >
> > > > > >
> > > > > > On Tue, 15 Feb 2005 14:40:07 +0000, Jon Dixon <dixon.jon at gmail.com> wrote:
> > > > > > > Sorry. I use both mplayer *and* totem-xine depending on what I am doing.
> > > > > > >
> > > > > > > Does it matter which drive you try it in?
> > > > > > >
> > > > > > > Because I have mplayer installed, I also have the win32 codecs package.
> > > > > > >
> > > > > > > Maybe that is a difference.
> > > > > > >
> > > > > > > On Tue, 15 Feb 2005 21:30:06 +0700, Brian Durant
> > > > > > > <globetrotterdk at gmail.com> wrote:
> > > > > > > > OK, I have libmad and gstreamer0.8-mad installed. What is this that
> > > > > > > > you are talking about an Mplayer GUI for totem-xine? It doesn't say
> > > > > > > > anything about this in the description in totem-xine. I have 2 CD/DVD
> > > > > > > > drives installed and I don't believe I made a symlink for either, but
> > > > > > > > they pop up on the desktop when I insert a VCD/DVD.
> > > > > > > >
> > > > > > > > Cheers,
> > > > > > > >
> > > > > > > > Brian
> > > > > > > >
> > > > > > > >
> > > > > > > > On Tue, 15 Feb 2005 13:59:27 +0000, Jon Dixon <dixon.jon at gmail.com> wrote:
> > > > > > > > > For me, DVDs autoplay with totem-xine. It also has better menu support
> > > > > > > > > than mplayer, i.e. mplayer doesn't have it yet :)
> > > > > > > > >
> > > > > > > > > For VCD, I just tell totem-xine to 'play disc' or with mplayer gui I
> > > > > > > > > right-click in the video window and select VCD -> Open disc.
> > > > > > > > >
> > > > > > > > > It pays to have libmad and gstreamer0.8-mad installed for VCD from
> > > > > > > > > what I recall (should write stuff down).
> > > > > > > > >
> > > > > > > > > I also changed the device to /dev/hdc as it played up when using the
> > > > > > > > > /dev/dvd symlink.
> > > > > > > > >
> > > > > > > > > On Tue, 15 Feb 2005 20:35:06 +0700, Brian Durant
> > > > > > > > > <globetrotterdk at gmail.com> wrote:
> > > > > > > > > > I'm playing them from VCD/DVD (i.e. CD-R, RW, DVD-R), not HD. I'm
> > > > > > > > > > using the totem gui in Warty.
> > > > > > > > > >
> > > > > > > > > > Cheers,
> > > > > > > > > >
> > > > > > > > > > Brian
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Tue, 15 Feb 2005 12:58:46 +0000, Jon Dixon <dixon.jon at gmail.com> wrote:
> > > > > > > > > > > That's not an extension I recognise either.
> > > > > > > > > > >
> > > > > > > > > > > Are you playing things from a drive, or from a CD?
> > > > > > > > > > >
> > > > > > > > > > > Are you running totem from a shell, or the GUI?
> > > > > > > > > > >
> > > > > > > > > > > I've played VCDs and DVDs fine using both totem-xine and mplayer,
> > > > > > > > > > > under both warty and now hoary.
> > > > > > > > > > >
> > > > > > > > > > > On Tue, 15 Feb 2005 19:33:42 +0700, Brian Durant
> > > > > > > > > > > <globetrotterdk at gmail.com> wrote:
> > > > > > > > > > > > Trying to play a VCD or DVD returns the following error message:
> > > > > > > > > > > >
> > > > > > > > > > > > "Totem could not play 'file:///media/sdg4/ffastun.ffo'.
> > > > > > > > > > > > The specified movie could not be found."
> > > > > > > > > > > >
> > > > > > > > > > > > The play disc command returns a window prompt to locate a file. Has
> > > > > > > > > > > > anyone seen this before?
> > > > > > > > > > > >
> > > > > > > > > > > > Cheers,
> > > > > > > > > > > >
> > > > > > > > > > > > Brian
> > > > > > > > > > > >
> > > > > > > > > > > > On Tue, 15 Feb 2005 09:27:08 +1100, Lex Hider <Lex.Hider at gmail.com> wrote:
> > > > > > > > > > > > > I can't comment on VCDs, but you should be able to watch DVDs if you use
> > > > > > > > > > > > > totem-xine instead of totem-gstreamer. totem-gstreamer will play hardly
> > > > > > > > > > > > > anything in comparison to totem-xine.
> > > > > > > > > > > > >
> > > > > > > > > > > > > totem-xine can be found in the universe repositories.
> > > > > > > > > > > > > You may also need the libdvdcss2 package to get around the CSS copy
> > > > > > > > > > > > > protection stuff on some CDs.
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Mon, 2005-02-14 at 16:27 +0700, Brian Durant wrote:
> > > > > > > > > > > > > >Hi again,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >I am trying to get Totem to behave so that I can watch VCDs and DVDs.
> > > > > > > > > > > > > >I have skimmed through the various HowTos, FAQs, etc. and I believe
> > > > > > > > > > > > > >that I have all of the codecs downloaded properly from the alternative
> > > > > > > > > > > > > >repositories. Totem just doesn't seem to be able to do anything. I
> > > > > > > > > > > > > >have looked at the add proprietary plug-ins section of Totem prefs and
> > > > > > > > > > > > > >don't find anything in there. Do I have to symlink or navigate to the
> > > > > > > > > > > > > >win32 codecs, gstreamer et.al. or is there another way to do this? I
> > > > > > > > > > > > > >know someone is going to post with the suggestion that I try Mplayer,
> > > > > > > > > > > > > >but I don't have a virgin system, I don't want to upgrade to Hoary yet
> > > > > > > > > > > > > >and after the debacle I have had with trying different CD burners to
> > > > > > > > > > > > > >burn an audio CD and none of them as of yet being able to do anything,
> > > > > > > > > > > > > >I would prefer to start slowly with Totem and try to get that to work
> > > > > > > > > > > > > >before moving on to anything else.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >Cheers,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >Brian
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > ubuntu-users mailing list
> > > > > > > > > > > > ubuntu-users at lists.ubuntu.com
> > > > > > > > > > > > http://lists.ubuntu.com/mailman/listinfo/ubuntu-users
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > If knowledge can create problems, it is not through ignorance that we
> > > > > > > > > > > can solve them.
> > > > > > > > > > > - Isaac Asimov
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > ubuntu-users mailing list
> > > > > > > > > > > ubuntu-users at lists.ubuntu.com
> > > > > > > > > > > http://lists.ubuntu.com/mailman/listinfo/ubuntu-users
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > If knowledge can create problems, it is not through ignorance that we
> > > > > > > > > can solve them.
> > > > > > > > > - Isaac Asimov
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > ubuntu-users mailing list
> > > > > > > > > ubuntu-users at lists.ubuntu.com
> > > > > > > > > http://lists.ubuntu.com/mailman/listinfo/ubuntu-users
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > If knowledge can create problems, it is not through ignorance that we
> > > > > > > can solve them.
> > > > > > > - Isaac Asimov
> > > > > > >
> > > > > > > --
> > > > > > > ubuntu-users mailing list
> > > > > > > ubuntu-users at lists.ubuntu.com
> > > > > > > http://lists.ubuntu.com/mailman/listinfo/ubuntu-users
> > > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > If knowledge can create problems, it is not through ignorance that we
> > > > > can solve them.
> > > > > - Isaac Asimov
> > > > >
> > > >
> > >
> > > --
> > > If knowledge can create problems, it is not through ignorance that we
> > > can solve them.
> > > - Isaac Asimov
> > >
> >
>
> --
> If knowledge can create problems, it is not through ignorance that we
> can solve them.
> - Isaac Asimov
>
More information about the ubuntu-users
mailing list