Open GoogleCodeExporter opened 9 years ago
See http://flowplayer.org/forum/support.html?id=98855
Original comment by blacktrashproduct
on 4 May 2012 at 12:37
Note that this does also NOT happen with flowplayer 3.2.7, rtmp 3.2.3, and
bwcheck 3.2.5:
http://flowplayer.blacktrash.org/test/bwcheck-dynamic.html#player2
Confirmed by customer as it happened with the upgrade.
Original comment by blacktrashproduct
on 4 May 2012 at 12:41
I rechecked this using my videos: the combo works with absolutely clean encoded
videos.
It's somehow ironic that Flowplayer > 3.2.7 targets higher Flash versions, but
fails on higher Flash versions - that's at least how it looks to the user. Note
the encoding/muxing of the failing videos is not particularly bad. I can
diagnose no obvious mistakes.
Original comment by blacktrashproduct
on 5 May 2012 at 1:34
Ok, this one also does not work in 3.2.7 - works with cleanly encoded/muxed
clips in both versions, closing. Flash 11 IS annoying though.
Original comment by blacktrashproduct
on 6 May 2012 at 12:25
I'll have to do a thorough test with 11.2 which I now have, I think I am now
experiencing the issue across many things and they've broken something !
Original comment by electrot...@gmail.com
on 7 May 2012 at 3:01
I have the same problem with all different kind of video.. some of which
originate form Youtube, some of which I encoded myself. In fact, all videos
should be ok AFAIK. How would I go about checking the cleanness of
encoding/muxing of my videos to test further and confirm that is the problem?
Original comment by haris.zu...@morescreens.tv
on 16 May 2012 at 2:47
More info:
Audio is always present and working fine when I do not use the start parameter.
Even with the same start parameter set for exmaple 97 seconds, the audio
sometimes works, sometimes not.
On any subsequent seek in the player the missing audio reappears, and from then
works perfectly.
Seems to be only the initial start of the audio when there is an initial skip
requested with start parameter.
Does it ring any bells for anyone :) ?
Original comment by haris.zu...@morescreens.tv
on 16 May 2012 at 3:32
As this comes up again and again:
http://flowplayer.org/forum/support.html?id=102183
let's have another look at it, or perhaps someone has an idea.
From my perspective it looks like this:
1) Flash 11+ is extremely picky wrt video encoding/muxing. The issue appears in
working setups once upgraded to Flash 11.2 and greater.
2) I cannot reproduce with videos I encoded myself. But also could not detect
any obvious problems with sample videos which exhibited the problem.
So I am at a loss as to what exactly this is about.
Original comment by blacktrashproduct
on 26 Jul 2012 at 8:36
Minimal examples by customer:
http://www.tv2east.dk/nocmsdocs/debug/flowplayer_sound_issue_2.html
Original comment by blacktrashproduct
on 26 Jul 2012 at 9:10
Needle in a haystack have asked for a download of the file + streaming server
information.
Original comment by electrot...@gmail.com
on 28 Jul 2012 at 11:32
looks like a possibly wowza sever issue, if its the latest version a bug report
might need to be made.
Original comment by electrot...@gmail.com
on 1 Aug 2012 at 4:50
Is there a possibility getting more information, it's a little hard to
replicate at the moment.
Original comment by electrot...@gmail.com
on 13 Aug 2012 at 2:24
I got no information to go on cannot replicate anything, ok to close ?
Original comment by electrot...@gmail.com
on 15 Aug 2012 at 4:46
We have now solved this problem at our company, by changing the RTMP streaming
server.
Please read the following updated description of the error and the solution
here: http://www.tv2east.dk/nocmsdocs/debug/flowplayer_sound_issue_2.html
Original comment by acsand...@gmail.com
on 16 Aug 2012 at 9:02
Hi that technically doesn't explain anything I'm afraid. Thanks for getting
back to us. I'll close this for now as it's not easy to replicate and possibly
some strange wowza issue on the particular version you had.
Original comment by electrot...@gmail.com
on 17 Aug 2012 at 8:06
It looks a lot like a problem with Wowza. Here's another one - just plain rtmp
without bwcheck:
http://flowplayer.org/forum/8/102841
Wowza 2.2.3, I'm waiting for a link to download the clip, so I can verify
whether deploying from FMS (cloudfront) makes the difference.
Original comment by blacktrashproduct
on 22 Aug 2012 at 1:27
http://x32.elijst.nl/x264faacx.mp4
Original comment by Jan.Ehrhardt@monitor.nl
on 22 Aug 2012 at 1:51
[deleted comment]
I don't think much can be done with patches with older minor versions as there
is a newer miner version and obviouslly they must of fixed it ?
Original comment by electrot...@gmail.com
on 22 Aug 2012 at 3:39
Here's an excerpt from the Wowza server log. Note duplication of the mp4
extension:
rtmp://video4.sessiondatabase.net/vod/x264faacx.mp4.mp4
(still unclear why this only happens only in Flash 10.2 and greater.
#Version: 1.0
#Start-Date: 2012-08-22 03:49:28 CEST
#Software: Wowza Media Server 2.2.3 build26454
#Date: 2012-08-22
#Fields:
date time tz x-event x-category x-severity x-status x-ctx x-comment x-vhost x-ap
p x-appinst x-duration s-ip s-port s-uri c-ip c-proto c-referrer c-user-agent c-
client-id cs-bytes sc-bytes x-stream-id x-spos cs-stream-bytes sc-stream-bytes x
-sname x-sname-query x-file-name x-file-ext x-file-size x-file-length x-suri x-s
uri-stem x-suri-query cs-uri-stem cs-uri-query
[snip]
2012-08-22 04:39:09 CEST app-start application INFO 200 _definst_ vod/_definst_
- - - 211508.995 - - - - - - - - - - - - - - - - - - - - - - - - -
2012-08-22 04:39:09 CEST connect-pending session INFO 100 85.223.116.227 - _defa
ultVHost_ vod _definst_ 0.063 109.69.216.71 1935 rtmp://video4.sessiondatabase.n
et/vod 85.223.116.227 rtmp https://sessiondatabase.net/flowplayer/flowplayer-3.2
.11.swf WIN
11,3,300,271 1671830514 3454 3073 - - - - - - - - - - - - - rtmp://video4.sessio
ndatabase.net/vod -
2012-08-22 04:39:09 CEST connect session INFO 200 85.223.116.227 - _defaultVHost
_ vod _definst_ 0.063 109.69.216.71 1935 rtmp://video4.sessiondatabase.net/vod 8
5.223.116.227 rtmp https://sessiondatabase.net/flowplayer/flowplayer-3.2.11.swf
WIN
11,3,300,271 1671830514 3454 3073 - - - - - - - - - - - - - rtmp://video4.sessio
ndatabase.net/vod -
2012-08-22 04:39:09 CEST create stream INFO 200 - - _defaultVHost_ vod _definst_
0.0 109.69.216.71 1935 rtmp://video4.sessiondatabase.net/vod 85.223.116.227 rtm
p https://sessiondatabase.net/flowplayer/flowplayer-3.2.11.swf WIN
11,3,300,271 1671830514 3508 3411 1 - 0 0 - - - - 0 0.0 rtmp://video4.sessiondat
abase.net/vod rtmp://video4.sessiondatabase.net/vod - rtmp://video4.sessiondatab
ase.net/vod -
2012-08-22 04:39:09 CEST comment server INFO 200 - PlaylistPlayer.play[vod/_defi
nst_/x264faacx.mp4]: Dynamic Stream Markers are
on. - - - 211509.042 - - - - - - - - - - - - - - - - - - - - - - - - -
2012-08-22 04:39:09 CEST play stream INFO 200 x264faacx.mp4 - _defaultVHost_ vod
_definst_ 0.031 109.69.216.71 1935 rtmp://video4.sessiondatabase.net/vod 85.223
.116.227 rtmp https://sessiondatabase.net/flowplayer/flowplayer-3.2.11.swf WIN
11,3,300,271 1671830514 3605 3453 1 419989 0 0 x264faacx.mp4 - C:\Program Files
(x86)\Wowza/content mp4 25427848 488.597 rtmp://video4.sessiondatabase.net/vod/x
264faacx.mp4.mp4 rtmp://video4.sessiondatabase.net/vod/x264faacx.mp4.mp4 - rtmp:
//video4.sessiondatabase.net/vod -
2012-08-22 04:39:19 CEST stop stream INFO 200 x264faacx.mp4 - _defaultVHost_ vod
_definst_ 10.093 109.69.216.71 1935 rtmp://video4.sessiondatabase.net/vod 85.22
3.116.227 rtmp https://sessiondatabase.net/flowplayer/flowplayer-3.2.11.swf WIN
11,3,300,271 1671830514 3648 747202 1 435157 0 743315 x264faacx.mp4 - C:\Program
Files
(x86)\Wowza/content mp4 25427848 488.597 rtmp://video4.sessiondatabase.net/vod/x
264faacx.mp4.mp4 rtmp://video4.sessiondatabase.net/vod/x264faacx.mp4.mp4 - rtmp:
//video4.sessiondatabase.net/vod -
2012-08-22 04:39:19 CEST destroy stream INFO 200 x264faacx.mp4 - _defaultVHost_
vod _definst_ 10.093 109.69.216.71 1935 rtmp://video4.sessiondatabase.net/vod 85
.223.116.227 rtmp https://sessiondatabase.net/flowplayer/flowplayer-3.2.11.swf W
IN
11,3,300,271 1671830514 3648 747202 1 - 0 743315 x264faacx.mp4 - - - - - rtmp://
video4.sessiondatabase.net/vod/x264faacx.mp4 rtmp://video4.sessiondatabase.net/v
od/x264faacx.mp4 - rtmp://video4.sessiondatabase.net/vod -
2012-08-22 04:39:19 CEST disconnect session INFO 200 1671830514 - _defaultVHost_
vod _definst_ 10.234 109.69.216.71 1935 rtmp://video4.sessiondatabase.net/vod 8
5.223.116.227 rtmp https://sessiondatabase.net/flowplayer/flowplayer-3.2.11.swf
WIN
11,3,300,271 1671830514 3648 747398 - - - - - - - - - - - - - rtmp://video4.sess
iondatabase.net/vod -
Original comment by blacktrashproduct
on 22 Aug 2012 at 5:46
On my laptop I upgraded to Wowza Media Server 2 Developer 2.2.4 build27452.
The issue was not solved.
Original comment by Jan.Ehrhardt@monitor.nl
on 22 Aug 2012 at 8:09
If you let this one play until the end, the sound will re-appear at the play
again.
https://sessiondatabase.net/flowplayer/start7m.php
Original comment by Jan.Ehrhardt@monitor.nl
on 22 Aug 2012 at 8:16
Isn't the latest Wowza version 3.1.x?
http://www.wowza.com/pricing/installer
Original comment by blacktrashproduct
on 22 Aug 2012 at 9:44
Yes, but there a no unlimited developer licenses for Wowza 3, so I develop and
deploy still with Wowza 2.
Original comment by Jan.Ehrhardt@monitor.nl
on 22 Aug 2012 at 9:48
I have one more observation about this issue.
Wowza Streaming + Flowplayer (earlier mentioned version numbers): Sound does
not start at all.
Bitgravity Streaming + Flowplayer: Sound does start - but only some seconds
later than video. Lipsynch is OK.
Either Wowza or Bitgravity + Streaming + JW Player: Sound starts OK.
Best regards; András
Original comment by acsand...@gmail.com
on 22 Aug 2012 at 11:55
Just to avoid confusion here.
jwplayer's start parameter is the equivalent of:
clip: {
onStart: function () {
this.seek(position);
}
}
Flowplayer has no problem with this either - Just tested it again. This bug is
about Flowplayer's clip.start parameter, "something completely different":
clip: {
start: position
}
which afaik is not offered by jwplayer: you cannot seek back before `position'.
Original comment by blacktrashproduct
on 22 Aug 2012 at 2:36
A workaround is to combine the two:
https://sessiondatabase.net/flowplayer/start7m_combined.php
Set a start position and then this.seek(1). I tried this.seek(0), but that does
not work.
Original comment by Jan.Ehrhardt@monitor.nl
on 23 Aug 2012 at 1:38
I upgraded Wowza to 3.1.2 build1624. Wowza3 does not have the sound issue:
https://sessiondatabase.net/flowplayer/start7m.php
Original comment by Jan.Ehrhardt@monitor.nl
on 23 Aug 2012 at 2:30
For Opera users:
https://sessiondatabase.net/flowplayer/start7m_wowza3.php
Original comment by Jan.Ehrhardt@monitor.nl
on 23 Aug 2012 at 2:49
http://www.wowza.com/media-server/developers#developer-license wowza developer
license is there.
Original comment by electrot...@gmail.com
on 23 Aug 2012 at 3:20
I know, but it is limited to 180 days. The Wowza2 developer license did not
have that limitation.
Original comment by Jan.Ehrhardt@monitor.nl
on 23 Aug 2012 at 3:29
Hi you can reissue your license, I just did. Have you consulted wowza about the
issue at all ? It's likely they don't even support version 2 anymore also. They
have forum support also. I would also use the same version as production.
Original comment by electrot...@gmail.com
on 23 Aug 2012 at 4:42
I can't replicate an issue with your file on wowza 3.1.2 which is the only
available download.
I am however seeing an issue with the rtmp plugin with the start time, the
duration does not update I'm not sure if this is a recent change , is this
correct ?
Original comment by electrot...@gmail.com
on 23 Aug 2012 at 5:07
I cannot either replicate the issue with Wowza 3.1.2. See comment 28: "I
upgraded Wowza to 3.1.2 build1624".
Please clarify what you mean by the duration not being updated. I have fixed
the duration of the part I want to show on 60 seconds. The current position
start happily at 00:00 until it is at 01:00. That is the expected behaviour.
Original comment by Jan.Ehrhardt@monitor.nl
on 23 Aug 2012 at 5:19
That was a comment for blacktrash. Id advice to contact wowza regarding your
issue in Wowza 2.
Original comment by electrot...@gmail.com
on 24 Aug 2012 at 4:04
Original issue reported on code.google.com by
blacktrashproduct
on 4 May 2012 at 12:34