CLI freaking: wanna video\music in as much min-stic env as possible

[Misalf]

If you want to compile MPlayer, have a look here:
http://forum.tinycorelinux.net/index.php/topic,18142.0.html

You would load  compiletc.tcz  to have the basic build tools.
I might be able to send my build to you for testing. Not before tomorrow though and it currently has more deps than actually needed.

[gerald_clark]

You do not need graphics-KERNEL.tcz for Mplayer-nodeps.

I am playing a video right now on CentOS 6 with onboot.lst
alsa-config.tcz
libpng12.tcz
libjpeg-turbo.tcz
freetype.tcz
libXext.tcz
Mplayer-nodeps.tcz

[gerald_clark]

With a onboot.lst of:
alsa-config.tcz
mplayer.tcz

I can also play videos, but the video performance is much worse than the mplayer-nodeps from Core 5.

[Scampada]

With a onboot.lst of:
alsa-config.tcz
mplayer.tcz

I can also play videos, but the video performance is much worse than the mplayer-nodeps from Core 5.

I couldn't with "/dev/fb0: No such device" error.

mplayer -vo fbdev file.avi

[Scampada]

It works for me with graphics-kernel, but now I'm getting trouble with mplayer. It doesn't want to play some videos because of some scale or colorspace issue. Here:

MPlayer 1.1-4.9.1 (C) 2000-2012 MPlayer Team
MMX supported but disabled
MMX2 supported but disabled
SSE supported but disabled
SSE2 supported but disabled

Playing Lowrider.avi.
libavformat version 54.6.100 (internal)
AVI file format detected.
[aviheader] Video stream found, -vid 0
[aviheader] Audio stream found, -aid 1
VIDEO:  [FMP4]  640x360  24bpp  25.000 fps  350.8 kbps (42.8 kbyte/s)
Clip info:
 Software: Lavf52.64.2
Load subtitles in ./
Opening video filter: [scale w=1024 h=600]
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
libavcodec version 54.23.100 (internal)
Unsupported PixelFormat 61
Unsupported PixelFormat 53
Unsupported PixelFormat 81
Selected video codec: [ffodivx] vfm: ffmpeg (FFmpeg MPEG-4)
==========================================================================
==========================================================================
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
Unknown/missing audio format -> no sound
ADecoder init failed
Requested audio codec family [vorbis] (afm=libvorbis) not available.
Enable it at compilation.
Opening audio decoder: [tremor] Ogg/Vorbis audio decoder
AUDIO: 44100 Hz, 2 ch, s16le, 96.0 kbit/6.80% (ratio: 12000->176400)
Selected audio codec: [tremor] afm: tremor (OggVorbis audio)
==========================================================================
[AO OSS] audio_setup: Can't open audio device /dev/dsp: No such file or directory
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
[swscaler @ 0x8774380]BICUBIC scaler, from yuv420p to bgra using C
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.

FATAL: Could not initialize video filters (-vf) or video output (-vo).


Exiting... (End of file)

tried mplayer -vo fbdev -fs Lowrider.avi

[Scampada]

Another one video I tried to view was OK, but it won't get fullscreen, even with -fs set. Nor did -zoom option do. It played in the middle of screen, right "above" the console.

[Juanito]

I had big performance problems with MPlayer too. So, for personal use, I compiled it from source and made sure it included MMX and SSE instructions, which are not present in the build available from the 6.x repo.

As long as your version follows "-march=i486 -mtune=i686", please feel free to submit to replace the current version

[Misalf]

I definitely consider to do so, but only if it works out well. It will need at least one rebuild (I hope not more than that since it takes quite some time). I'm not sure if I can make a -nodeps version but I want to slim it down as much as I can. Now that I know how to compile MPlayer, it should be just a matter of time. (:

[Scampada]

I definitely consider to do so, but only if it works out well. It will need at least one rebuild (I hope not more than that since it takes quite some time). I'm not sure if I can make a -nodeps version but I want to slim it down as much as I can. Now that I know how to compile MPlayer, it should be just a matter of time. (:

Does it? I'd built Wesnoth and it did not take lot of time. I left it in VT and watched some video, or played some game or something. If you have no time you can explain me what do I need to make a build in TC (you said I need compiletc.tcz, is it enough?), send me your configure settings and tell where to get the same source as yours. Then I would test it on my own and share the results, does it work and do I see any improvements etc.

It would be great if there were no X libraries dependence in mplayer.tcz. I have no X, so what for am I waiting longer? It concerns also graphics.kernel; in its dep file there are lots of X libraries that I do not need necessarily... But the graphics kernel I do need; hmmm; what if I load manually only those dependencies from it that I need? And leave all X libs behind... I'll try and see. I tried to throw X library out of the mplayer.dep file, but it won't work then. Even in no X environment.

[Misalf]

Different software takes different amounts of time to compile.
IIRC, MPlayer took about 50 minutes to compile on my netbook (OC'ed @ 2GHz, 2GB RAM, 460MB compressed Swap in RAM + No Swap Drive).

You can get valuable hints about compiling MPlayer in the thread I posted a link to @ Reply #30, so you don't need to do the same mistakes I did.

compiletc.tcz  contains only the basic build tools. Anything else needed is either mentioned in MPlayer's readme or will be told to you via error message when running  ./configure  or  make .

Also read this:
http://wiki.tinycorelinux.net/wiki:creating_extensions
And this:
http://tinycorelinux.net/book.html

[Scampada]

The bootcode
home=hdXY
will automatically setup /home/tc
to "bind" to /mnt/hdXY/home/tc. The home boot code lets Tiny
Core coexist with other Linux installations by inserting the tc user
directory under a pre-existing /home directory. Also, Tiny Core
cannot auto-detect a persistent home directory, so the home boot
option is always required.

Ah, so da naa! There was another explaining somewhere in an old installation FAQ that I misunderstood concluding that boot 'home' option will sort of format my partition or something...
So that option will only create a directory inside an existing partition, even in existing /home folder? I have a /sda5 partition including /home for my openSUSE distro and some other sensitive files (old /home deprecated folders), I can just mount it to TC as home=sda5 ? It'll be okay, then?

[Misalf]

Correct.  home=sda5  will simply use  /sda5/home  as the home directory, and, if not already present, will also create the directory  tc  in  /sda5/home .

The boot code  opt=  works the same way, but may interfere with already installed versions of Linux.
The boot code  home=  is quite safe to use though.

[Scampada]

Well, I have read the book and based on what I understood I would like to ask if my onboot modules are copied to RAM or mounted. There are several modes, mount and copy. It is said in the book to get a module copied you must mark it with some kind of copy2fs flag. But no examples were given. Here I have my own onboot.lst:

wifi.tcz
links.tcz
mplayer.tcz
alsa-config.tcz
graphics-3.16.6-tinycore.tcz

I want them all loaded to RAM. What do I add to my onboot.lst?

[gerald_clark]

Run the following 2 commands:

ce
touch copy2fs.flg

[Scampada]

Before I reboot: is it ok to create a symlink /sda5/home -> /sda5/tinycore/home and pass home=sda5 to kernel?
I want to keep all tc files into tinycore folder... wouldn't like to scatter all those folders...