AxisCommunications/locomote-video-player

Media Player in Adobe Flash with RTSP support

Andrey

@insonifi

@drowzy, I added keepAlive parameter for Player. Disabled by default. Check my pull request when you have time. :)

Simon Thörnqvist

@drowzy

Alright :)

Andrey

@insonifi

What is motivation behind

destroy: function() {
      window.LocomoteMap[this.tag] = {
        __playerEvent: function () {},
        __swfReady: function () {}
      };
//...
}

And not assigning null. Since, if I initialise player again with same id. I'll never get new player:

// Instance already initialized. Return it.
    if (window.LocomoteMap[tag]) {
      return window.LocomoteMap[tag];
    }

Andrey

@insonifi

@drowzy , @h-no check my question, please :)

Simon Thörnqvist

@drowzy

I think it's to prevent calling functions on null if the locomote obj was destroyed before it could be stopped properly.

Andrey

@insonifi

Maybe, we should check result of __swfReady() then, instead of object existence?

Andrey

@insonifi

@drowzy, another question considering __swfReady property, isn't it tad misleading that it is boolean_ most of the time and suddenly becomes _function on destroy? Wouldn't it be better to just assign __swfReady = false on destroy? or null to distinguish from "not ready yet" state.

my bad, I confused {boolean} swfready and {function} __swfReady

Simon Thörnqvist

@drowzy

@insonifi easy to get confused :).

Andrey

@insonifi

@drowzy, I'm afraid pull request you merged had a glitch. swfready might be false so, I should have tested for undefined value to account for it. I didn't make it in time to update pull request, so created new one.

Andrey

@insonifi

@drowzy, also updated RTSP player pull request, as per your comment

Simon Thörnqvist

@drowzy

@insonifi not sure if its a problem. But I see your point.

Andrey

@insonifi

well, it is incorrect to re-initialize a "not-ready" player. It's API misuse anyway.

Simon Thörnqvist

@drowzy

Yup

Andrey

@insonifi

@drowzy, another pull request. Now, in the MJPEGClient Handle. I found that Basic Auth wasn't working, because socket was closed twice when calling disconnect().

Simon Thörnqvist

@drowzy

Yes, very good. Think it's best to keep the debug message though.

Andrey

@insonifi

@drowzy, I added log message back to disconnect().

Andrey

@insonifi

@drowzy, if I need to show single image, e.g. a poster or a preview, what is a preferred way of doing it?

Simon Thörnqvist

@drowzy

So a preview of the stream in its current state? Or just the same preview picture everytime?

Andrey

@insonifi

I'd say a preview that I get from server as an image. It's not the same all the time, but it downloaded from HTTP server.

Simon Thörnqvist

@drowzy

Ok, I would just overlay the player with the picture. We use wmode=transparent in locomote so it shouldn't be a problem

Andrey

@insonifi

Cool, background style works like a charm!

Simon Thörnqvist

@drowzy

Neat :)!

Hannes

@h-no

FYI: after contacting contributors of Locomote regarding the license of Locomote and changing it to a more permissive license, we have decided to change the license to https://opensource.org/licenses/BSD-3-Clause

We'll tag a new release shortly....

Gaétan Collaud

@gaetancollaud

Thank you for asking to the contributors. ;)

off topic : Since flash will be removed from all browser eventually, what is your plan for locomote ?

In my company we use it to play video stream from axis camera (and AVHS). But sooner or later we will have to move to html5. Do you plan to adapt locomote to html5 or will it be another separate project ?

I don't know if you already have though about that at Axis ?

Simon Thörnqvist

@drowzy

We are working on it, it will be seperate from locomote.

Gaétan Collaud

@gaetancollaud

Thanks for the clarification

Andrey

@insonifi

Are you going to implement WebRTC client?

Omar Gonzalez

@s9tpepper

Anyone around? Got a quick question, I'm trying to compile Player.swf so that it doesn't make ExternalInterface calls, so I went in the source and commented out all of the calls to ExternalInterface.call() and recompiled with gulp. But I'm still getting errors from a ExternalInterface.call() in the axis.ErrorManager class, even though I commented it out, anyone have any suggestions?

Alexander Olsson

@noseglid

Caching perhaps. Or you’re not installing/reloading it from the correct place. Or there are even more ExternalInterface.call in the code.

Omar Gonzalez

@s9tpepper

i had to pull the source into my test project to get it to stop doing it, probably an IntelliJ compiler cache or something

Alexander Olsson

@noseglid

Switch to Atom :elephant:

Good you got it working

Omar Gonzalez

@s9tpepper

now just trying to get it to play an RTSP url streaming from VLC - I added a policy socket server but I never see any requests come from AS3, after I call play() it waits a few seconds and then sends a streamStopped event

RTMP url plays fine, tested one just to make sure the Player class was running correctly

Alexander Olsson

@noseglid

RTMP is not subject to socket policy, which may indicate a socket policy issue.

But you should get a error callback then.

Omar Gonzalez

@s9tpepper

yea that's what I figured, and I'm not seeing any requests come from AS3 to the policy server

Alexander Olsson

@noseglid

Is it running on port 843 ?

Omar Gonzalez

@s9tpepper

yea

$ python -c 'print "<policy-file-request/>"' | nc 127.0.0.1 843
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "/xml/dtds/cross-domain-policy.dtd">

<cross-domain-policy>

<site-control permitted-cross-domain-policies="master-only"/>

<allow-access-from domain="*" to-ports="*" />

</cross-domain-policy>

i tested it like that from the cli

Alexander Olsson

@noseglid

Networking issues?

Omar Gonzalez

@s9tpepper

AIR app and VLC are both running on same computer

Alexander Olsson

@noseglid

Odd, and how are you specifying the RTSP url?

Omar Gonzalez

@s9tpepper

i've tried "rtsp://:8554/" and "rtsp://192.168.1.11:8554/"

Where communities thrive

People

Repo info

Activity