Closed GoogleCodeExporter closed 9 years ago
i checked it with the 2014.0 Build and this does not work either....
(on our church´PC the 2014.0 is still working...)
Original comment by MisterSi...@gmail.com
on 21 Jun 2014 at 5:19
Are you sure you only have one version of VLC on your system, and this version
is the latest one? If you have two versions (an older and a newer one) then
Quelea may see the older one first, and complain that the version of VLC is too
old.
(The above is the only way I've been able to reproduce this issue.)
Original comment by berry...@gmail.com
on 26 Jun 2014 at 12:32
Hy Michael.
On my system i had two versions installed.
So i deleted both, downloaded the actual version 2.1.3 and installed it.
The "Installed Software" in the Win7 system page now shows just one installed
VLC...
The "cannot find VLC" is still there
ummmm, that´s strange...
Original comment by MisterSi...@gmail.com
on 26 Jun 2014 at 9:45
I searched the registry for VLC entries and found some old ones and deleted
them...with no effect to the error.
Original comment by MisterSi...@gmail.com
on 26 Jun 2014 at 10:34
Hy Michael!
Very interresting what i found out now:
I started 2014.0 with from the quelea.exe => VLC can be found and is working
i started 2014.0 from commandline java -jar Quelea.jar => VLC cannot be found
I´m sure this is also the reason why the Nightly builds are not working ->
they are started from commandline ?
What i could imagine what causes this:
VLC (and quelea) is installed to the Program Files(X86) folder.
This folder has different labels depending on the Windows Version installed
(Language dependent)
On a German Windows7 installation the Program Files (x86) is displayed as
"Programme (x86)
Maybe this is a problem when starting quelea from the commandline ?
Or is there any other reason why Quelea is not working when it´s started from
the commandline?
-> i attached the logfile when starting 2014.0 with CMD
Original comment by MisterSi...@gmail.com
on 26 Jun 2014 at 10:40
Attachments:
here is the commandline output from the 2014.1 version:
The output referring to the vlc problem is very similar to the one when 2014.0
is started via CMD
Original comment by MisterSi...@gmail.com
on 26 Jun 2014 at 10:45
Attachments:
Hi Simon, it appears that when running from the command line you are using your
systems default Java install which is 64 bit.
When you run from the packaged .exe, it uses the bundled Java install which is
32 bit.
Your VLC installation is in 32 bit, and so won't run with 64 bit Java. You can
either install the 64 bit VLC or change your default system Java to whichever
version of VLC you're using.
To do that, go to Control Panel, type 'Java' into the search box and open the
program, go to the Java tab, then hit 'View...' and make sure that only one
Java installation is ticked, and that it is in the Programme (x86)\Java\ folder.
This should do it, but if you need more help then get back to me.
Ben
p.s. I have attached a screenshot, but its slightly different because I use 64
bit for testing purposes.
Original comment by bengoodw...@gmail.com
on 1 Jul 2014 at 5:45
Attachments:
Hy Ben!
The installation of Java 32 bit did not work...
but i installed a 64bit VLC and now the video support in 2014.1 is working,
Thank you!
Simon
Original comment by MisterSi...@gmail.com
on 2 Jul 2014 at 2:16
Original comment by bengoodw...@gmail.com
on 28 Jul 2014 at 2:20
Original issue reported on code.google.com by
MisterSi...@gmail.com
on 21 Jun 2014 at 1:19