I see that for small clips this does not happen. But when the size is large (say 2MB or so), the progress bar starts to display the left moving cross bars again (once the end is reached). An example is here: http://www.swview.org/node/34
I use Firefox in Linux, but I have seen this in IE as well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Regarding that thread, the fix doesn't seem to work. I've been using Flowplayer 1.15, but also tried version 1.11.1 to double-check and see if there was a regression. No such luck. As for the cause of the bug, there doesn't seem to be any correlation between file size and/or length. In fact, one source file was transcoded using Sorensen (h263) and using VP6 -- neither flv worked. For those of you who are new to the problem, what happens is that when a clip concludes, it should reset (the play button should have the play icon and the video should be set to the 1st frame). Or, in the case of a playlist, the video should advance to the next clip.
In this case, the video just stays stuck on the last frame and the progress indicator seems to show buffering. The video will not advance to the next item in the playlist (if there is one) or reset itself (in the absence of a playlist). FLVPlayer (http://www.jeroenwijering.com/?item=flash_video_player) doesn't not manifest this same behavior on these troublesome files. It would be great to get a fix for Flowplayer though.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes David, that thread discusses the same problem. At the end of the clip, the progress bar starts to show buffering again. And play button etc, does not function properly.
Though I am not sure, the issue was not occuring for small flv files in the limited number of tests I ran. For example:
I've been able to get this behavior with small files and big files alike. Sometimes I see it, sometimes I don't -- there doesn't seem to be any rhyme or reason. I wonder if the code doesn't account for an edge case and that's what creates this. I started poking around the code base and changing things, but haven't had any luck correcting the problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have checked http://www.swview.org/node/32 several times now yesterday and today and it does not show the buffering animation at the end when I have tried it. FlowPlayer receives notifications from the Flash player plugin when the video ends. It starts the buffering animation when the buffer memory is emptied. The buffer emptied notification is usually triggered at the end of the movie, but only after there has been a notification that the playback has stopped and in that case the buffer animation is not displayed. This is what happens when I try that video (I can see what events get triggered using the log inspector: http://www.kolumbus.fi/apiirain/video/FlashInspector.swf\)
One thing that I could do is to add a additional test so that it will not display the buffering animation if the playback is close to ending - if there is only 1 or 2 seconds time left.
The current behavior in the player is that the playback stops at the last frame of the video and stays there. The play/pause button resets to show the play symbol. It does not seek to the start of the video. When the user hits play the video starts from the beginning.
Regards,
Anssi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I forgot. The debug messages are for another round of playing. Not of the run I used to capture the video. And in other tabs of the logger, I didn't find messages.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There was already some end detection logic that is used in case there is no proper end notification from the Flash player. It assumed that the video has ended if it stops .05 seconds before the duration time encoded in FLV metadata. I changed this threshold value to .1 seconds and I think it works better with your video now.
Thanks a lot. Your new version is working correctly.
But I am wondering why such an end notification is not generated by the Flash Player. What is your guess? Is it a bug with the Flash Player itself or a complication with the notification receiving mechanism used by Flow Player? I have not been into Flash development. But in network programming identification of an end of a stream is not very complicated. But of cause here I see that the stream handling is done by the Flash Player than the Flow Player if I got it correct. What happens inside the Flash Player is beyond our control. Sometimes the Flash Player might be emitting the end of stream notification not on receiving the last byte but use some high level logic (like waiting for a specific piece of data at the end of a frame).
Or can this be a specific problem associated with the way I prepared .flv files? I used Kino to generate them. Kino internally uses ffmpeg.
Thanks again.
Kamal
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In this new version (1.17-m1), I see that there is a full screen mode and embedding ability.
1. Embedding might not be preferred by some sites because that can lead to copyright violations etc. So I suggest to dissable it by default but allow it to be displayed if enabled by a key in the html (flashvars). Default state should be dissabled for compatibility reasons.
2. I understand why the full screen mode takes you to the sourceforge site. A better way would be to dissable this by default and allow it to be enabled by a key in the html. Furthermore, a variable used to point to a full screen html page instead of the sourceforge page would please all of us. If such a variable is not used, you can by default use the sourceforge page. You know, in real businesses people won't like to display the full screen button if the page doesn't come up due to SF maintenence. That can lead to frustration. Furthermore, we would love to show the users our own customized pages. And again, the default state should be not to display the full screen button again due to backword compatibility.
I know that you might be experimenting with such features in M1. I just wrote my humble thoughts on it.
Regards,
Kamal
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The embed and full screen features were introduced in version 1.16. You can hide the menu items using the new 'menuItems' config variable. The demo page (http://flowplayer.sourceforge.net/showcase.html) hides them for some of the player instances.
You can also replace the default fullscreen page using the new fullScreenScriptURL variable. By default, it uses this script to open the full screen window: http://flowplayer.sourceforge.net/fullscreen.js You can use your own script that opens the window from your own site. Your own script is used after you specify it in the fullScreenScriptURL variable:
Aha... I only new about 1.15. In the upgrade, I now have to explicitly disable the embedding and full screen modes by changing html which I think is not the best approach in an upgrade process.
Disabling the embedding feature by default is good from the copyright point of view as well.
Full screen mode is a preferable adition in terms of functionality. The only problem with that is the need of a separate page. If such a file was not required, enabling by default would not cause any issue. Given that such a file is required, the best is to disable by default.
Just my thoughts you might consider!
Regards,
Kamal
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I see that for small clips this does not happen. But when the size is large (say 2MB or so), the progress bar starts to display the left moving cross bars again (once the end is reached). An example is here: http://www.swview.org/node/34
I use Firefox in Linux, but I have seen this in IE as well.
Sounds like you are seeing the behavior that was mentioned in this thread: http://sourceforge.net/forum/forum.php?thread_id=1637942&forum_id=453550
Regarding that thread, the fix doesn't seem to work. I've been using Flowplayer 1.15, but also tried version 1.11.1 to double-check and see if there was a regression. No such luck. As for the cause of the bug, there doesn't seem to be any correlation between file size and/or length. In fact, one source file was transcoded using Sorensen (h263) and using VP6 -- neither flv worked. For those of you who are new to the problem, what happens is that when a clip concludes, it should reset (the play button should have the play icon and the video should be set to the 1st frame). Or, in the case of a playlist, the video should advance to the next clip.
In this case, the video just stays stuck on the last frame and the progress indicator seems to show buffering. The video will not advance to the next item in the playlist (if there is one) or reset itself (in the absence of a playlist). FLVPlayer (http://www.jeroenwijering.com/?item=flash_video_player) doesn't not manifest this same behavior on these troublesome files. It would be great to get a fix for Flowplayer though.
Yes David, that thread discusses the same problem. At the end of the clip, the progress bar starts to show buffering again. And play button etc, does not function properly.
Though I am not sure, the issue was not occuring for small flv files in the limited number of tests I ran. For example:
1. Playing this clip does not trigger the problem (relatively small size): http://www.swview.org/node/20
2. Playing this clip created by following the same steps trigger the issue (About 2MB): http://www.swview.org/node/32
I also realized that flvtool2 has nothing to do here.
My guesses are that this might occur due to an integer overflow or some kind of timing/synchronizing issue.
Kamal,
I've been able to get this behavior with small files and big files alike. Sometimes I see it, sometimes I don't -- there doesn't seem to be any rhyme or reason. I wonder if the code doesn't account for an edge case and that's what creates this. I started poking around the code base and changing things, but haven't had any luck correcting the problem.
Hello,
I have checked http://www.swview.org/node/32 several times now yesterday and today and it does not show the buffering animation at the end when I have tried it. FlowPlayer receives notifications from the Flash player plugin when the video ends. It starts the buffering animation when the buffer memory is emptied. The buffer emptied notification is usually triggered at the end of the movie, but only after there has been a notification that the playback has stopped and in that case the buffer animation is not displayed. This is what happens when I try that video (I can see what events get triggered using the log inspector: http://www.kolumbus.fi/apiirain/video/FlashInspector.swf\)
One thing that I could do is to add a additional test so that it will not display the buffering animation if the playback is close to ending - if there is only 1 or 2 seconds time left.
The current behavior in the player is that the playback stops at the last frame of the video and stays there. The play/pause button resets to show the play symbol. It does not seek to the start of the video. When the user hits play the video starts from the beginning.
Regards,
Anssi
I wonder whether you will find the following useful:
Adobe Systems Incorporated
Flash Player 9 for Linux
Version 9.0.31.0
January 2007
http://www.swview.org/tmpupload/log.jpg
http://www.swview.org/tmpupload/info.jpg
http://www.swview.org/tmpupload/debug.jpg
http://www.swview.org/tmpupload/flowplayer-problem.avi (8.5MB)
The images show the end sections of the logs. I am glad to send any further details you need.
Time to sleep now :) It's 11.54pm here in Sri Lanka.
Regards,
Kamal
I forgot. The debug messages are for another round of playing. Not of the run I used to capture the video. And in other tabs of the logger, I didn't find messages.
Kamal,
There was already some end detection logic that is used in case there is no proper end notification from the Flash player. It assumed that the video has ended if it stops .05 seconds before the duration time encoded in FLV metadata. I changed this threshold value to .1 seconds and I think it works better with your video now.
Please try with this one: http://www.kolumbus.fi/apiirain/video/flowplayer-1.17-m1.zip
Anssi
Anssi,
Thanks a lot. Your new version is working correctly.
But I am wondering why such an end notification is not generated by the Flash Player. What is your guess? Is it a bug with the Flash Player itself or a complication with the notification receiving mechanism used by Flow Player? I have not been into Flash development. But in network programming identification of an end of a stream is not very complicated. But of cause here I see that the stream handling is done by the Flash Player than the Flow Player if I got it correct. What happens inside the Flash Player is beyond our control. Sometimes the Flash Player might be emitting the end of stream notification not on receiving the last byte but use some high level logic (like waiting for a specific piece of data at the end of a frame).
Or can this be a specific problem associated with the way I prepared .flv files? I used Kino to generate them. Kino internally uses ffmpeg.
Thanks again.
Kamal
Anssi,
Just two suggestions:
In this new version (1.17-m1), I see that there is a full screen mode and embedding ability.
1. Embedding might not be preferred by some sites because that can lead to copyright violations etc. So I suggest to dissable it by default but allow it to be displayed if enabled by a key in the html (flashvars). Default state should be dissabled for compatibility reasons.
2. I understand why the full screen mode takes you to the sourceforge site. A better way would be to dissable this by default and allow it to be enabled by a key in the html. Furthermore, a variable used to point to a full screen html page instead of the sourceforge page would please all of us. If such a variable is not used, you can by default use the sourceforge page. You know, in real businesses people won't like to display the full screen button if the page doesn't come up due to SF maintenence. That can lead to frustration. Furthermore, we would love to show the users our own customized pages. And again, the default state should be not to display the full screen button again due to backword compatibility.
I know that you might be experimenting with such features in M1. I just wrote my humble thoughts on it.
Regards,
Kamal
The embed and full screen features were introduced in version 1.16. You can hide the menu items using the new 'menuItems' config variable. The demo page (http://flowplayer.sourceforge.net/showcase.html) hides them for some of the player instances.
You can also replace the default fullscreen page using the new fullScreenScriptURL variable. By default, it uses this script to open the full screen window: http://flowplayer.sourceforge.net/fullscreen.js You can use your own script that opens the window from your own site. Your own script is used after you specify it in the fullScreenScriptURL variable:
fullScreenScriptURL: 'http://www.mysite.edu/myfullscreenopener.js'
By default both of those features are now enabled, let's see if I need to change that...
Anssi
Hi Anssi,
Aha... I only new about 1.15. In the upgrade, I now have to explicitly disable the embedding and full screen modes by changing html which I think is not the best approach in an upgrade process.
Disabling the embedding feature by default is good from the copyright point of view as well.
Full screen mode is a preferable adition in terms of functionality. The only problem with that is the need of a separate page. If such a file was not required, enabling by default would not cause any issue. Given that such a file is required, the best is to disable by default.
Just my thoughts you might consider!
Regards,
Kamal
Anssi,
This didn't fix playback of my clip. What was helpful in getting this resolved on my end was the information that I found here: http://www.quip.net/blog/2007/flash/actionscript-20/how-to-determine-completion-of-flv.
Cheers,
David