Page 1 of 1

JVLC issue

Posted: 20 Oct 2006 20:13
by jakechoi
Hi,

We were highly attracted by the cross platform video playing
capability in the VNC and decided to use it in our CDN application
based on Java.

We have added VLC plugin to communicate with our CDN application
and want to share with anyone who is interested in.
And at the same time we also want to have good help from anyone who
is familiar with problems we are dealing with.

We have some problems to do with JVLC (0.8.5) such as video
is not always embbedded in the window frame (JPanel) we
have created.

It works most of times, but it doesn't very rarely (1 in 100).
(It shows video in the separate window. And this is why we
create the our version of plugin to work around...)

If anyone know how to solve this, please let us know.


Thank you,

Jake Choi

Posted: 26 Jan 2007 14:00
by otrofox
Is it possible to hang your version? We are all having the same problem.

Posted: 27 Jan 2007 00:50
by ahmdprog
hi,

the JVLC is very very * 1000000000 * very experimental.

don't think that it is easy job to call JNI and have video and audio working fine with JVM.

the biggest problem with JVLC is not the features and JPanel or something like this. the problem it is not stable with JVM.

I have compiled the JVLC more than 100 times changing the code trying to know why the _--please stay polite-- JVM crashed sometimes when trying to create instance of JVLC(createInstance).

I think, it is better to start writing JNI be myself rather than depending on other people code.

Posted: 27 Jan 2007 02:13
by ballofking
I agree with ahmdprog.JVLC is too instable.

Posted: 14 Mar 2007 14:18
by littlejohn
I agree with ahmdprog.JVLC is too instable.
JVLC for windows is. The same code under Linux works fine. We want it to be stable for all the platforms, so instead of just complaining help us to do so.

Cheers

Posted: 14 Mar 2007 17:29
by ahmdprog
No one is complaining, the JVLC was very poor and unstable at all, i have compiled the JVLC many many times, and i tried to build the JVLC under windows, Fedora Core 6 and Debian, and Suse 10.2, looking for stable one.

I have rewrite all the JNI staff, trying to make stable one, I have asked the JVLC developer for that, and I asked any one who know the C code of VLC to help me in writing JNI, but useless.

I have send my JVLC to many many people for testing. all of us are looking to have JVLC working fine, and if we complain, that means we need it working propably.

so, no one is complaining.

Regards,
Ahmad.

Posted: 07 May 2007 15:41
by otrofox
Not sure but, IMHO, the main unstability problem of JVLC for Windows is related to the asynchronism of JNI calls. If, after a call (i.e. playlist.play(-1, null)) you wait 400ms, the JVM doesn't crash. By contrast, if you try to make a lot of calls at the time without a little sleep time between them, it will crash for sure.
I think littlejohn is working on it, as it is reported on Trac.
The problems are being solved so, let's wait a little to get this project working.

Posted: 07 May 2007 20:44
by littlejohn
Not sure but, IMHO, the main unstability problem of JVLC for Windows is related to the asynchronism of JNI calls. If, after a call (i.e. playlist.play(-1, null)) you wait 400ms, the JVM doesn't crash. By contrast, if you try to make a lot of calls at the time without a little sleep time between them, it will crash for sure.
I think littlejohn is working on it, as it is reported on Trac.
The problems are being solved so, let's wait a little to get this project working.
... or send patches :)

Re:

Posted: 24 Jun 2008 17:46
by agussi
Not sure but, IMHO, the main unstability problem of JVLC for Windows is related to the asynchronism of JNI calls. If, after a call (i.e. playlist.play(-1, null)) you wait 400ms, the JVM doesn't crash. By contrast, if you try to make a lot of calls at the time without a little sleep time between them, it will crash for sure.
I think littlejohn is working on it, as it is reported on Trac.
The problems are being solved so, let's wait a little to get this project working.
... or send patches :)

what is the state of the work ?
is there some patch to correct this problem ?