Interacting with VLC via a non supported language

[Zaxon]

I'm wanting to control VLC via a language not directly supported by VLC, in this case AutoIt, but the same question could be asked of PERL or anything else.

Ideally I'd interact with VLC via COM, and seeing ActiveX is an outgrowth of COM there maybe a way of tapping into it. ActiveX as presented on the VLC website seems to be suggesting you'd be embedding VLC in a browser. This isn't what I want. I want to launch VLC as a stand alone player and just communicate with it (read/write).

I've made attempts to control it via its DOS looking RC interface, but with no real success since it doesn't appear to be using the STDIN/STDOUT streams as expected. You can see examples of what I've tried so far at http://www.autoitscript.com/forum/index ... opic=43432

So, what's the best way of controlling (but not embedding) VLC from a language not directly supported?

[Jean-Baptiste Kempf]

You can use VLC with ActiveX without a browser.
If you need just basic interaction, http or rc interface can be a solution.

[Zaxon]

You can use VLC with ActiveX without a browser.

OK. I'll look into that further

If you need just basic interaction, http or rc interface can be a solution.

The type of functionality I require is things such as: stop, pause, what position am I currently playing in the file?, Jump to position x in the file.

Can that be achieved via http? Based on my current attempts I don't believe it can be acheived via the RC interface when controlling it via scripting. See the link in message one for examples of my attempt to do this. Of course RC is ideal if you're manually typing these commands in yourself.

[Zaxon]

OK. I'm attempting to go the ActiveX route. Given that there are no examples in the current language I'm using, I've gleaned as much as I can from the examples given and from the discussions I've found in this forum. Here is my code:

Code: Select all

$file="c:\temp\test.mpg" ; change this to a file that exists on your system $vlc=ObjCreate("VideoLAN.VLCPlugin.1") if @error then msgbox(0,"Error","Unable to create VLC object") exit endif dim $options[1] $options[0]=":vout-filter=deinterlace" enum $VLCPlayListInsert=00000001,$VLCPlayListReplace=00000002,$VLCPlayListAppend=00000004,$VLCPlayListGo=00000008,$VLCPlayListCheckInsert=00000010 $vlc.addTarget($file, $options,$VLCPlayListGo,0)

This code successfully launches the file in VLC which begins to play, showing that the basics are more or less there, but the script then crashes. This probably means one of my data types isn't quite right. What I've written is as close as I'm able to get given the examples I've found so far.

Can some one point out what change I need to make to stop the script crashing immediately upon the launch of VLC?

[Zaxon]

Is no one familiar with the correct syntax of the addTarget method, or is the fact that my example is in a different language throwing you?

[VDMGC]

I too use AutoIT, and the ActiveX is quite capable of receiving streamed media etc. Unfortunately I wish to also stream from the ActiveX. This was possible in the past, but that functionality is now supposedly deemed "unsafe". This is an absolute show stopper for any further development of VLC streaming applications using AutoIT -for all time. (And according to a 5 dozen other dissatisfied VB devs according to this forum, their existing stuff will now die a slow painful death too.)

Is there some way that VLC activeX can be set to ignore this so called "unsafe" flag, especially for Win32 applications operating on a LAN only? Searching thru this forum I discovered that I am one of a maaaany people trying to figure a way out of this security *bug* (yes boys, lets call it a spade!)

Now I already know that the VLC way is to tell me to get myself Linux, spend 3 years on the theoretical science of media streaming and careful study of the VLC source, then recompile it on my Linux PC, battle a further X years to get the stuff to compile, and then (haleluyah!) I can return to my current *real* project just in time to start all over again with VLC 16.5 on Windows 37.

Now if anybody on this forsaken forum knows (Yes, I know the devs dont or cant read this forum for some as yet undiscovered and bizzare reason) a way, or will be kind enough to upload a binary release without this pestilential security bug, I and every other current and future VB and AutoIT dev will absolutely praise you, credit you in every app etc. In fact, you will become my personal "VLC god/goddess" who's praises shall be sung in my software for all etirnity.

Now is there such a talented and capable person available here somewhere, who is actually willing to help the real world *users* of this really powerful program without the usual BS of do it yourself?