This is a message.

Forum user: lawinfo

Basic information

Registered Jun 26, 2008
Last login Apr 10, 2012
Forum posts 15
Direct URL http://www.flowplayer.org/forum/users/4480

Latest forum posts

Posts:

Registered:

» problem with cluster plugin when all hosts fail

Posted: Jan 12, 2011

I suddenly experienced the exact issues described. Did you ever get a solution?

Posts:

Registered:

» » » Cannot upgrade multidomains license!!

Posted: May 11, 2010

Is the upgrade from multi-domain license 3.1.5 to 3.2 free?

Posts:

Registered:

» » » » Flash plugin: Analytics - Customizing Tracked Values

Posted: Feb 19, 2010

Yeah, I've tried that. Those values are used for labeling the actual event that happens (Play, Stop, etc.), and not for tagging the media on which the event occurred.

BTW: nice profile picture.

Posts:

Registered:

» » Flash plugin: Analytics - Customizing Tracked Values

Posted: Feb 19, 2010

But the clip section require that the 'ga.js' be included. I'm using the flash plug-in so I don't have to use the 'ga.js' script.

The plug-in currently works great except that GA groups the events by the URL that the video is played on, which as you mentioned, creates 100's of categories. That's why I want to dynamically set a specific value, to something like 'Videos', so all events are tracked under the same category.

Additionally, it would be nice to also set the value for the 3rd parameter to be a logical name, human readable title of the video, instead of a cryptic url and filename.


Then, could you change "private function doPlayerTrackEvent()" to use its current values (_embeddedURL, _eventLabel, _player.playlist.getClip(0).completeUrl, _player.status.time) as defaults only if none are specifically passed into it. This would allow for backward compatibility and extend the functionality.

Posts:

Registered:

Flash plugin: Analytics - Customizing Tracked Values

Posted: Feb 19, 2010

I'm using version 3.1.5 fromhttp://flowplayer.org/plugins/flash/analytics.html. Is there a way to customize the values that are tracked?

Instead of the calls to Google being:
trackEvent( host:http://www.example.com/video.html, start,http://www.example.com/video.flv, 0 )

can the 1st and 3rd values be passed in like:

trackEvent( My Own Category, start, My Video Title, 0 )

Something similar to the way its done onhttp://flowplayer.org/demos/events/google-analytics.html by using some of the 'clip' values.

Posts:

Registered:

» » Product keys don"t work after upgrade

Posted: Oct 13, 2009

We did buy the upgrade to 3.1.4 but the problem is that all the 3.0.7 keys are no longer valid when used with 3.1.4. We have the player on over 50 domains and it is going to be a big project to go through all of them to update the license. Even with a 'major' upgrade, why would previous version keys no longer work?

Posts:

Registered:

Product keys don"t work after upgrade

Posted: Oct 13, 2009

I just upgraded our commercial version from 3.0.6 to 3.1.4 and now all the previous "Product keys" don't work. Looking at the list of product keys in our FlowPlayer account (http://flowplayer.org/account/products.html ), I see that they have all changed and don't match what they were before the upgrade. How do I get the old keys back??

Posts:

Registered:

» » works with 3.0.5 swf

Posted: Apr 1, 2009

So I have a final resolution. I talked to our network admin and he tried TURNING OFF gzip for SWF files ... and the player loads consistently!! Anyone else having this issue, try turning off gzip compression on the server for swf files.

Thanks all for your help!

Posts:

Registered:

» works with 3.0.5 swf

Posted: Apr 1, 2009

fjaif, no luck. I created a pagehttp://www.lawinfo.com/API/preroll3.html that is identical to the ones mentioned above using 3.0.5 instead but still get the 'black screen'. It's on the server that is using gzip compression.

Posts:

Registered:

Mute button ignores "buttonColor" value

Posted: Apr 1, 2009

I am using "flowplayer.commercial-3.0.7.swf" and am unable to get the mute button to take on the "buttonColor" value. I even tried specifying a different control version as in the example below but was still unsuccessful. Is this a bug or is there another way to style the mute button?

Flowplayer forum example

HTML setup for the player

<!-- include latest Flowplayer javascript file -->
<script language="javascript" src="path/to/flowplayer-3.2.8.js"></script>

<!-- player container with optional splash image -->
<a href="path/to/video_file" id="playerContainer">
	<img src="path/to/splash_image" />
</a>


JavaScript coding

Following script will install Flowplayer into our player container


<script language="javascript">
// our custom configuration is given in third argument
flowplayer("playerContainer", "path/tohttp://releases.flowplayer.org/swf/flowplayer-3.2.11.swf",{
plugins:  { controls:  {  url:'flowplayer.controls-3.0.4.swf',backgroundGradient:[0.2, 0.8, 0.9, 0.8, 0.2],volume:false,fullscreen:false,height:25,scaling:'scale',autoHide:'never',backgroundColor:'#9e9e9e',timeColor:'#ffffff',progressColor:'#1c478b',progressGradient: 'high',bufferColor:'#9baecc',bufferGradient:'high',sliderColor:'#c6d1e2',sliderGradient:'high',buttonColor:'#1c478b',buttonOverColor:'#3888e9' } },
});
</script>


Posts:

Registered:

» » No more "black screen"!!

Posted: Mar 31, 2009

I have not experienced the problem on any flowplayer.org pages. This got me thinking if it could be related to the server that serves the swf file. So, I revertedhttp://www.lawinfo.com/API/preroll.html to use "flowplayer.commercial-3.0.7.swf" and "flowplayer-3.0.6.min.js" and am able to reproduce the "black screen" consistently with this combination.

I then setup another identical test pagehttp://www.lawinfo.com/API/preroll2.html that also uses "flowplayer.commercial-3.0.7.swf" and "flowplayer-3.0.6.min.js" but pulls the swf from a different server setup that is actually in a different location. Suprise, suprise. I am not able to reproduce the "black screen". Bernd, do you see the same results from these 2 pages?

If you also find thathttp://www.lawinfo.com/API/preroll2.html 'fixes' the problem, then the question is, why does that server serve the file differently? Cache, firewall, proxy. If I get some free time, maybe I'll try investigate further.

Posts:

Registered:

» No more "black screen"!!

Posted: Mar 30, 2009

Well, maybe not. Soon after posting the previous post, I was able to recreate the problem several times. It seems to happen mostly when doing a hard refresh (ctrl+F5) on the page but also with a plain F5 refresh. It's very inconsistent which is frustrating.

Posts:

Registered:

No more "black screen"!!

Posted: Mar 30, 2009

I tried thehttp://piimaa.info/js/flowplayer.min.js but it didn't seem to help so I then tried the "flowplayer-3.1.0-dev.swf" with "flowplayer-3.1.0-dev1.min.js" and they worked!! I have not been able to reproduce the 'black screen' onhttp://www.lawinfo.com/API/preroll.html using those 2 files. Thank you very much!

Is there a "3.0.8" version of the swf that has this 'preloader tweak' applied? I am about to release a major update to our legal video library -http://resources.lawinfo.com/en/Videos/index.html - and it would be great if this bug was fixed when I release.

Thanks again for your great work on this player!

Posts:

Registered:

» » same problem here

Posted: Mar 25, 2009

Thanks for the reply Jules. I tried moving the js to the very bottom but it didn't seem to make a difference. I did notice however, that in firebug 'flowplayer.commercial-3.0.7.swf' loads twice, which seems pretty weird. The first instance is 94k but the second instance is only 7k.

Tero: any idea or input on what could be going on here?

Posts:

Registered:

frequent "black screen" issue

Posted: Mar 24, 2009

I'm also having the same problem in FF 3.0.7 on winxp (ie6 even works w/o fine)-http://www.lawinfo.com/API/preroll.html

I added 'debug:true,' to the script and all that displays in the console is '$f.fireEvent ["onBeforeLoad"]' instead of all the other events.

Hope this sheds some more light on the 'black screen' issue. Look forward to any suggestions to test for a possible fix.