NVidia - MPlayer

Ellops · 12-29-2005, 08:30 PM

I cannot open .mov files with Mplayer (nor any other player so far)

I got an NVIdia card

I found this in the MplayerHQs:
----
It's recommended to use the binary nVidia drivers for X before using this VIDIX driver, because some of the registers which need to be initialized haven't been discovered yet, so it will probably fail with the Open Source XFree86 nv.o driver.

Currently only codecs capable of UYVY colorspace output can work in conjunction with this driver. Unfortunately, this excludes every single decoder from the libavcodec family. This leaves us with the following usable popular codecs: cvid, divxds, xvid, divx4, wmv7, wmv8 and some others. Please note that this is only a temporal inconvenience. The usage syntax is as follows:
-----

Actually, I got confused cuz all the other drivers work except the VIDIX (and the xmga) for avi's, wmv's and such formats.

Did anybody got it to work with .mov.

Is there any other way, at least, to play .mov files?

thanx

gilead · 12-29-2005, 10:55 PM

I'm using the binary NVidia drive (installed from NVIDIA-Linux-x86-1.0-8174-pkg1.run) with mplayer version 1.0pre7try2. I used the install procedure from the README file I extracted from MPlayer-1.0pre7try2.tar.bz2 as well as the codecs from essential-20050412.tar.bz2 and the fonts from font-arial-iso-8859-1.tar.bz2.

I can play mov files without any problems. Did you install mplayer from a package or compile it from sources?

Ellops · 12-29-2005, 11:19 PM

I compiled it from source. and the codecs are in $prefix/lib/codecs, the essential ones.
When using VIDIX an err msg "Error opening/initializing the selected video_out(-vo) device" appears, while when usin others theres sound but no picture.

That's a typical out (running as root)>

Code:

vo: X11 running at 1280x1024 with depth 24 and 32 bpp (":0" => local display)
Failed to open /dev/rtc: No such device (it should be readable by the user.)
Selected font is fixed-width.
Selected font is fixed-width.
Selected font is fixed-width.
Selected font is fixed-width.
Selected font is fixed-width.
Selected font is fixed-width.
Selected font is fixed-width.
Playing /root/azureus/the Prodigy - Smack my Bitch up.mov.
ISO: File Type Major Brand: Original QuickTime
QuickTime/MOV file format detected.
--------------
MOV track #0: 1097 chunks, 6852 samples
MOV: AVC decoder configuration record atom (46)!
Image size: 320 x 240 (24 bpp)
Display size: 320 x 240
Fourcc: avc1  Codec: 'h264'
--------------
MOV track #1: 1606 chunks, 12844 samples
Audio bits: 16  chans: 2  rate: 48000
Audio extra header: len=79  fcc=0x77617665
MOV: Found MPEG4 audio Elementary Stream Descriptor atom (39)!
Fourcc: mp4a
--------------
MOV: longest streams: A: #1 (12844 samples)  V: #0 (6852 samples)
VIDEO:  [avc1]  320x240  24bpp  25.000 fps    0.0 kbps ( 0.0 kbyte/s)
Clip info:
 name: the prodigy - smack my bitch u
==========================================================================
Opening audio decoder: [faad] AAC (MPEG2/4 Advanced Audio Coding)
AUDIO: 48000 Hz, 2 ch, s16le, 64.0 kbit/4.17% (ratio: 8000->192000)
Selected audio codec: [faad] afm:faad (FAAD AAC (MPEG2/MPEG4 Audio) decoder)
==========================================================================
No vidix driver name provided, probing available ones (-v option for details)!
vosub_vidix: Couldn't find working VIDIX driver
Error opening/initializing the selected video_out (-vo) device.

Seems don;t find VIDIX drivers, but Iv installed the bins..

I configured(I guess)with most of not autodetected features

Ellops · 12-29-2005, 11:26 PM

Oh, now I ran it with the -v opt:

Can't open input config file /root/.mplayer/input.conf: No such file or directory
Can't open input config file /usr/local/etc/mplayer/input.conf: No such file or directory
Falling back on default (hardcoded) input config

But, I dont know what this is suposed to mean...

gilead · 12-30-2005, 04:57 AM

That last part just says you don't have any settings configured so it's using default values. Try running mplayer with different values for vo. I use vo = gl2 (it was x11 with a previous video card). Also, what are the permissions on your /dev/rtc? Mine are:

Code:

cr--r--r--  1 root root 10, 135 1996-05-30 10:06 /dev/rtc

Ellops · 12-30-2005, 12:16 PM

the permissions for /dev/rtc are
>ls -l /dev/rtc
crw-rw-r-- 1 root root 10, 135 2005-12-30 09:46 /dev/rtc.

It says that it must have r perms for the user, and that makes me worry. Though that the user have r perm , something goes wrong. I try to access it from user mod and the acces is denied. This also happens wiht other files and dirs, though I have give permss to the user...

PS: I change the vo, through thw gui menu. Ive tried them all

Ellops · 12-30-2005, 10:01 PM

Ok mow I ran it with option: 'gmplayer -vo drv[:xvidix]'
and the message: No vidix driver name provided, probing available ones (-v option for details)!
vosub_vidix: Couldn't find working VIDIX driver
didn't appear..

However the the:
Error opening/initializing the selected video_out (-vo) device.
remains.

I guess it has to do with the /dev/rtc, that it cannot open, though that the perimisions are 755..

ough...

I dont know what to think

gilead · 12-30-2005, 10:14 PM

Have you tried running the following as root?

Code:

echo 1024 > /proc/sys/dev/rtc/max-user-freq

Ellops · 12-30-2005, 10:29 PM

I was about to ask about that one seeing it in the other thread.

there isnt any such dir in proc/sys/dev, nor somewhere else in the system..

Only here /usr/share/oprofile/rtc, but it contains only two files, events + unit_masks

Ellops · 12-30-2005, 11:15 PM

I would say that I haven't compiled RTC in the kernel, But in 2.6.14 i haven't seen any RTC option...

Searching through my .config I saw an # CONFIG_RTC is not set
under the 'Watchdog Cards' section...

Can I set it on?
Where?

Ellops · 12-30-2005, 11:25 PM

Oh *&!#^$^!*@&^#&!^@&6ΑΡΓΚ

Know I checked a doc in LKML.org that says
about the additions in 2.6.14-rc2

Mr Clemens Ladisch added these in the kernel:

[ALSA] ad1889: add AD1889 driver
[ALSA] ad1889: add AD1889 driver docs
[ALSA] hdsp: always initialize card name
[ALSA] usb-audio: add SNDRV_PCM_INFO_BATCH flag
[ALSA] sparse address space annotations
[ALSA] opti93x: optimize a register access
[ALSA] rtctimer: add option to make RTC timer the default sequencer timer
[ALSA] set owner field in struct pci_driver

I guess I have the rc1....

Or itis irrelevant and I gonna waste my time????

gilead · 12-30-2005, 11:27 PM

It needs to be compiled into the kermel (or as a module). Maybe someone here knows where you can download it already compiled as a module, but I think it will only work if your kernel is expecting it there as a module. /proc/sys/dev/rtc/max-user-freq is where mplayer is looking for its settings, but do you get anything if you type:

Code:

cat /proc/driver/rtc

If you do, then you probably already have the RTC support compiled in, you just need the /proc/sys/dev/rtc/max-user-freq setting for mplayer. I get the following:

Code:

rtc_time        : 15:23:28
rtc_date        : 2005-12-31
rtc_epoch       : 1900
alarm           : 11:59:12
DST_enable      : no
BCD             : yes
24hr            : yes
square_wave     : no
alarm_IRQ       : no
update_IRQ      : no
periodic_IRQ    : no
periodic_freq   : 1024
batt_status     : okay

Ellops · 12-30-2005, 11:38 PM

No there isn't any /proc/driver/rtc either..

But somewhere I saw the option "store time in GMT in RTC" or something like that.
Shouldn't it have adaptability for the RTC module, with an option like that? I didnt find any though...

I guess that by compiling this module /proc/sys/dev/rtc/max-user-freq will be automatically created, no?

I dont know, Ill propably download the newer version of 2.6.14. Isn't that gonna solve the problem?

Ellops · 12-31-2005, 07:12 PM

..............

Ellops · 12-31-2005, 07:13 PM

Well, finally I got it workin!

I downloaded patch-2.6.15-rc7 and enabled the RTC Support in Device Drivers > Sound > ALSA

However, I still cant play *mov files since it failes to load the 'VIDIX' driver.

>>>Error opening/initializing the selected video_out (-vo) device.<<<

I think is installed properly, having a VIDIX dir within the MPlayer's install dir.

Could be the configuration file?

PS: I applyied everything mentioned above