when I run it, i get:
===
VLC media player 1.0.5 Goldeneye
[0x4c0500] main libvlc error: no memcpy module matched "any"
[0x4da320] main interface error: no interface module matched "hotkeys,none"
[0x4da320] main interface error: no suitable interface module
[0x4c0500] main libvlc error: interface "hotkeys,none" initialization failed
[0x4c0500] main libvlc error: option drawable-xid does not exist
[0x4c0620] main interface error: no interface module matched "signals"
[0x4c0620] main interface error: no suitable interface module
[0x4c0500] main libvlc error: interface "signals" initialization failed
[0x4c0620] main interface error: no interface module matched
"globalhotkeys,none"
[0x4c0620] main interface error: no suitable interface module
[0x4c0500] main libvlc error: interface "globalhotkeys,none"
initialization fail
ed
[0x4c0500] main libvlc: Running vlc with the default interface. Use
'cvlc' to use vlc without interface.
[0x4c0620] main interface error: no interface module matched "any"
[0x4c0620] main interface error: no suitable interface module
[0x4c0500] main libvlc error: interface "default" initialization failed
====
I do have the last SDL, qt4 and all (I believe) the possible gcc
What do I need?
Is there some file to configure?
thanks
piesse
Are you sure that your vlc is beta 1 ?
Those messages are displayed because VLC cannot find any plugins.
You can use "--plugin-path" option to specify the path of plugins.
But beta 1 does not require this option if VLC package was unzipped in
its directory structure.
--
KO Myung-Hun
Using Mozilla SeaMonkey 2.0.3
Under OS/2 Warp 4 for Korean with FixPak #15
On AMD ThunderBird 1GHz with 512 MB RAM
Korean OS/2 User Community : http://www.ecomstation.co.kr
Yes
vlc --version
VLC media player 1.0.5 Goldeneye
VLC version 1.0.5 Goldeneye
Compiled by root@.unknown
Compiler: gcc version 4.4.2 (GCC)
This program comes with NO WARRANTY, to the extent permitted by law.
You may redistribute it under the terms of the GNU General Public License;
see the file named COPYING for details.
Written by the VideoLAN team; see the AUTHORS file.
>
> Those messages are displayed because VLC cannot find any plugins.
>
> You can use "--plugin-path" option to specify the path of plugins.
>
> But beta 1 does not require this option if VLC package was unzipped in
> its directory structure.
>
Do I need to download the plugins separately?
piesse
with the --plugim-path it gets better: the graphic interface shows up,
but the following are still on the tect screen:
===
[D:\]vlc --plugin-path usr\local\lib\vlc
VLC media player 1.0.5 Goldeneye
[0x5fc700] main interface error: no interface module matched
"globalhotkeys,none"
[0x5fc700] main interface error: no suitable interface module
[0x4c43e0] main libvlc error: interface "globalhotkeys,none"
initialization failed
[0x4c43e0] main libvlc: Running vlc with the default interface. Use
'cvlc' to use vlc without interface.
WARNING: QApplication was not created in the main() thread.
====
Trying a short mp3 file gets:
[0x6eb1e0] main demux error: no meta reader module matched "any"
[0x6e6fa0] main input error: ES_OUT_SET_(GROUP_)PCR is called too late,
increasing pts_delay to 1000 ms
[0x6e6fa0] main input error: ES_OUT_RESET_PCR called
[0x6e6fa0] main input error: ES_OUT_SET_(GROUP_)PCR is called too late,
increasing pts_delay to 1000 ms
[0x6e6fa0] main input error: ES_OUT_RESET_PCR called
[0x6e6fa0] main input error: ES_OUT_SET_(GROUP_)PCR is called too late,
increasing pts_delay to 1016 ms
[0x6e6fa0] main input error: ES_OUT_RESET_PCR called
[0x6e6fa0] main input error: ES_OUT_SET_(GROUP_)PCR is called too late,
increasing pts_delay to 1017 ms
[0x6e6fa0] main input error: ES_OUT_RESET_PCR called
[0x6e6fa0] main input error: ES_OUT_SET_(GROUP_)PCR is called too late,
increasing pts_delay to 1038 ms
[0x6e6fa0] main input error: ES_OUT_RESET_PCR called
[0x6e6fa0] main input error: ES_OUT_SET_(GROUP_)PCR is called too late,
increasing pts_delay to 1049 ms
[0x6e6fa0] main input error: ES_OUT_RESET_PCR called
etc...
The file is apparently read, but there is no audio
piesse
Now I'm sure that you're using 'Technology Preview' not 'Beta'.
You can download beta1 on hobbes.
http://hobbes.nmsu.edu/h-search.php?key=vlc&pushbutton=Search
And those warnings are harmless. Don't worry about it.
--
ok, thamks!
piesse
"Unable to open SDDHELP$ helper device driver!"
Bart
Toronto
First, are you sure that SNAP was installed correctly ?
Second, are you setting LIBPATHSTRICT=T ? If so, remove it.
--
Bart
It is possible to install and use SDDHELP.SYS by itself (without the
rest of SNAP). You'll also need graphics.bpd from the SNAP installation.
--
[Reverse the parts of the e-mail address to reply.]
>> "Unable to open SDDHELP$ helper device driver!"
>
> Second, are you setting LIBPATHSTRICT=T ? If so, remove it.
Hmm... is that why the MPlayer plugin has never worked? Surely that can
be fixed.
>>> "Unable to open SDDHELP$ helper device driver!"
>>
>> Second, are you setting LIBPATHSTRICT=T ? If so, remove it.
>
> Hmm... is that why the MPlayer plugin has never worked? Surely that can
> be fixed.
Indeed! Thanks for the hint, based on previous knowledge from Rich
Walsh's efforts, it was quite simple to fix; only one instance of 'DLL'
has to be changed to 'dll' in snapwrap.dll. Anyone interested can get
my modified version here:
http://www.os2bbs.com/os2news/snapwrap.dll
>>> First, are you sure that SNAP was installed correctly ?
>>
>> I did not read about a requirement for SNAP, this PC has Panorama
>
> It is possible to install and use SDDHELP.SYS by itself (without the
> rest of SNAP). You'll also need graphics.bpd from the SNAP installation.
I believe there is some software that checks for SNAP being installed
based on the presence of SDDHELP$ being loaded. Some people discovered
that the Panorama driver was actually a lot faster at some operations if
the SDDHELP$ driver was loaded, so perhaps that is the situation here.
Hopefully that is not the default (bastardized) configuration.
No. You don't have to have SNAP.
The reason why I asked is that SDDHELP$ is apart of SNAP.
If you use Panorama, I don't understand why SDDHELP$ is referred.
Maybe, Panorama has a dependency on SDDHELP$ ?
And for details, please use the following command.
vlc -vvv --extraintf=logger
You can get vlc-log.txt. Attach it, please.
I know, SNAP itself doesn't like LIBPATHSTRICT=T.
BTW without LIBPATHSTRICT=T, MPlayer plugin works ?
> If you use Panorama, I don't understand why SDDHELP$ is referred.
Me neither :)
> And for details, please use the following command.
>
> vlc -vvv --extraintf=logger
>
> You can get vlc-log.txt. Attach it, please.
Sorry, I switched to SNAP, now the error is gone.
But thanks for VLC!!!
Bart
>> http://www.os2bbs.com/os2news/snapwrap.dll
> prev snapwrap I had was 123,507
> yours is only 37,606
> should I worry?
No - mine has been processed by lxLite. I'm not sure why KO doesn't do
that prior to distribution - it not only loads faster, it cuts down on
the size of the archive and the files on disk.
>>> Second, are you setting LIBPATHSTRICT=T ? If so, remove it.
>>
>> Hmm... is that why the MPlayer plugin has never worked? Surely that can
>> be fixed.
>
> I know, SNAP itself doesn't like LIBPATHSTRICT=T.
That is not correct, see the fix in my other message.
> BTW without LIBPATHSTRICT=T, MPlayer plugin works ?
Yes.
Steve Wendt wrote:
> On 06/11/10 07:31 am, KO Myung-Hun wrote:
>
>>>> Second, are you setting LIBPATHSTRICT=T ? If so, remove it.
>>>
>>> Hmm... is that why the MPlayer plugin has never worked? Surely that can
>>> be fixed.
>>
>> I know, SNAP itself doesn't like LIBPATHSTRICT=T.
>
> That is not correct, see the fix in my other message.
>
snapwrap.dll does not load any dll directly at all. See the sources of
'snapwrap.dll'. SNAP SDK loads it, instead.
SNAP SDK is 'SNAP itself'.
>>> I know, SNAP itself doesn't like LIBPATHSTRICT=T.
>>
>> That is not correct, see the fix in my other message.
>
> snapwrap.dll does not load any dll directly at all. See the sources of
> 'snapwrap.dll'. SNAP SDK loads it, instead.
> SNAP SDK is 'SNAP itself'.
I see what you meant now. It's too bad that IBM never fixed all the
bugs related to LIBPATHSTRICT, but at least there are some easy workarounds.
Unfortunately the screen saver locks up after a few minutes now! Ah, well...