• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu

HOW TO: Installing Streaming Audio and Video Support in Firefox/Seamonkey

Started by Glenn, 2009.05.29, 01:16:59

Previous topic - Next topic

Glenn

http://www.os2world.com/content/view/17999/2/
QuotePosted by Robert Mauro - Wednesday, 30 April 2008


This ". .. .
npmp_test.zip is not available anymore at the given address. However, OS/2 site (http://www.os2site.com/sw/mmedia/video/mplayer/npmp_test.zip) got it on time.

Pete

Hi Glenn

The npmp.dll in the current mplayer package should work - worth knowing where to pickup this version though, just in case  :-)

Regards

Pete

Glenn

Quote from: Pete on 2009.05.29, 15:29:52
The npmp.dll in the current mplayer package should work - worth knowing where to pickup this version though, just in case  :-)

Thanks for the piece of information, Pete !

There is, however, two things that bother me:

1- from the previous conversations on that topic, I still don't understand if MediaPlayer connectivity has to be installed or if the plugin is self-sufficient. Instructions say that the associations should be deleted, installing MPC needs the associations, discussion seems to indicate that MPC is still required. All of that seems to be self-contradictory, and I don't know what to believe.

2-a For whomever coded/ported this code: it would be great if the program could look into its own directory/subdirectories when handling libraries, thus avoiding users to add lengthy paths to the path and especially to the libpath. Even without putting all my programs into the \Program(s) directory, the length of my Libpath is almost at its maximum value, and adding the paths for mplayer make it too long (with the usual doscall1.dll error).
2-b To solve the libpath/path length errors, I would be willing to sponsor (in the limit of what I can still afford at the end of the month, given my student's earnings at the beginning), in form of an os2world bounty, the creation of a program that would concentrate libraries in a common directory. This program would be run by the user before a program is installed and after it has been installed (before rebooting), look at the differences in the libpath. If there is any difference, then the program would list the libraries in the added directory, go through the other libpath libraries (or just through the existing libraries in the common folder) to see if there is any library newer than the ones just installed but with the same name, and copy the libraries of the recently installed program into the common folder, just discarding those that are already installed in a more recent version. Given the size of today's hard drives, having two copies of the same libraries (one in the original folder and one in the common folder) is not a lot of lost space, but it would allow using the available space when installing more programs without getting a libpath-length error.

A.

Pete

Hi Glenn

1] MPC is used to hook up an external player (browser "helper" app) and is not needed for those vid clips that mplayer can play.

2a] What libpaths for mplayer? - not sure how long the libpath can be offhand but mine is only 287 chars.

2b] Common lib files such as the ibc*.dll files should be collected together in 1 location; on an ecs system that should be \ecs\dll, on os/2 that would be \os2\dll


Regards

Pete


RobertM

Quote from: Glenn on 2009.05.31, 07:34:45
Quote from: Pete on 2009.05.29, 15:29:52
The npmp.dll in the current mplayer package should work - worth knowing where to pickup this version though, just in case  :-)

Thanks for the piece of information, Pete !

There is, however, two things that bother me:

1- from the previous conversations on that topic, I still don't understand if MediaPlayer connectivity has to be installed or if the plugin is self-sufficient. Instructions say that the associations should be deleted, installing MPC needs the associations, discussion seems to indicate that MPC is still required. All of that seems to be self-contradictory, and I don't know what to believe.

I maybe should have been more clear in my intent in that section. Let me try to clarify. If you want something to be displayed in a site in it's window by mPlayer, do NOT associate that object (let's say an .MPG file) to MPC or mPlayer will not work well with it.

MPC does not need to be installed to get such things to work. MPC is a different type of plugin. Let me try to explain:
(1) MPC allows association and launch of various media files into a standalone player (like "Launch WAV files with z!")
(2) the mPlayer plugin allows playing media inside of a site (in it's video window location). Where the video would normally be on a Windows system, you will get a black window that says "Click to play" or something similar. Do just that.

What this allows is sites that embed video, expecting your browser to launch your QuickTime or WMP browser plugin, will then be usable directly in your site by instead launching the mPlayer plugin. Inotherwords, all this simply does is assign the mPlayer plugin as the "replacement" for Windows users' Quicktime and WMP browser plugins.

Now, perhaps you see the issue with associating the files to MPC as well.

Regardless, I use both MPC and mPlayer plugin - I simply uncheck the video formats in MPC that I want mPlayer plugin to handle. I have had limited success in getting both to coexist with both associated to the same type of media file - but your mileage may vary... inotherwords, feel free to try leaving MPC associated to MP4, MPG, AVI, MOV, FLV, etc files and see what happens... worst case, you will have to simply disable those associations to get the mPlayer plugin to handle those files correctly.


Quote from: Glenn on 2009.05.31, 07:34:45
2-a For whomever coded/ported this code: it would be great if the program could look into its own directory/subdirectories when handling libraries, thus avoiding users to add lengthy paths to the path and especially to the libpath. Even without putting all my programs into the \Program(s) directory, the length of my Libpath is almost at its maximum value, and adding the paths for mplayer make it too long (with the usual doscall1.dll error).

These are the relevant lines, which should not affect your path statement.

SET MPLAYER_HOME=D:\HOME\DEFAULT\.mplayer
SET MPLAYER_CODECS_DIR=D:\APPS\MPLAYER\codecs
SET MPLAYER_PATH=D:\APPS\MPLAYER\mplayer.exe


The relevent text that DOES affect your path statement is the inclusion of "D:\APPS\MPLAYER" in it at a point before the WinOS2 references so that Win16 Media Player isnt launched instead.

And of course the mPlayer config file changes/additions.

Quote from: Glenn on 2009.05.31, 07:34:45
2-b To solve the libpath/path length errors, I would be willing to sponsor (in the limit of what I can still afford at the end of the month, given my student's earnings at the beginning), in form of an os2world bounty, the creation of a program that would concentrate libraries in a common directory. This program would be run by the user before a program is installed and after it has been installed (before rebooting), look at the differences in the libpath. If there is any difference, then the program would list the libraries in the added directory, go through the other libpath libraries (or just through the existing libraries in the common folder) to see if there is any library newer than the ones just installed but with the same name, and copy the libraries of the recently installed program into the common folder, just discarding those that are already installed in a more recent version. Given the size of today's hard drives, having two copies of the same libraries (one in the original folder and one in the common folder) is not a lot of lost space, but it would allow using the available space when installing more programs without getting a libpath-length error.

A.

I simply do that on my own for many of the programs and/or support DLLs I need/use. I have a BIN and a DLL directory on my boot drive, which is where I place virtually all of that stuff.

Rob


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


RobertM

Quote from: Pete on 2009.05.31, 17:50:20
Hi Glenn

1] MPC is used to hook up an external player (browser "helper" app) and is not needed for those vid clips that mplayer can play.

2a] What libpaths for mplayer? - not sure how long the libpath can be offhand but mine is only 287 chars.

2b] Common lib files such as the ibc*.dll files should be collected together in 1 location; on an ecs system that should be \ecs\dll, on os/2 that would be \os2\dll

I used to use the method in 2b, but then opted for separate DLL and BIN directories to simplify updating many ports that always seemed to be in flux (such as the earlier libc ports, earlier emx, etc). The other reason I do so is so that when I set up certain server systems that rely on various add-on dll's, I can simply copy a complete \DLL directory to the new setup without having to try to dig through the OS2\dll directory to find the needed DLLs (as copying the whole directory can be a bad thing if one is not sure what "update" status both systems are at. Either method works though for most users.


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|