Forum user: Joust Dissapointed with noone to fix aac hanging bug.

Is there a way to force content plugin to behave with large content that does not fit in the declared dimensions?

i.e.:

titleBar: { 
	url: '/flash/flowplayer.content-3.1.0.swf',
	backgroundColor: '#000000',
	border: '0px none',
	padding: 10,
	html: '<p>Some long paragraph text that will not fit in width or height in the container</p>',
	display: 'block',
	height: 50,
	width: '100%',
	top: 0,
	left: 0,
	style: {
		'p' : {
			color: '#ffffff',
			fontSize: 21,
		}
	}
}

.. Despite the given height, if the width is too low the text inside container will wrap down and jump out of the black box.

Naturally there should be a way to control it. In css container we could use height:auto, overflow: hidden or at least (cheap workaround) white-space:nowrap.

If it's not implemented, any ideas how to emulate it ?

ps: please stop messing with js on flowplayer page :) My left/right arrow keys are not working, so there must be some background event handler capturing those.

Hello!

I've found an "inflexibility" of the page scrolling logic.

• Go to the following demo:http://flowplayer.org/tools/demos/scrollable/navigation.html
• Now scroll down to the second example ("Page scroll").
• We see [0][1][2][3][4]
• Use your mouse wheel to scroll one item ahead (visible [1][2][3][4][5])
• Click on RIGHT ARROW icon
• it scrolls all the way to [10][11][12][13][14] (!?)

It is supposed to scroll 5 items ahead, but instead it detects we are after page 1 (but not on 2), so it skips to page 3 ?

It might be consistent with the API or whatever, but it is totally unusable and confusing for the user. I believe that paging navigation should be handled in regard to current offset.

Cheers!

It's still here with the newest version and Flash updates. So unless you stick to the very basic configuration and dump autoBuffering, you're out of luck. Or dump MP4, who would use that anyways? Or get another player.

And still no workaround.

Generally this issue is related to flash rendering of audio or video. I can reproduce this issue on ANY website with any flash player (vimeo, youtube, etc.).

I have 2 monitors (on DVI and HDMI) and Windows Vista. When switching from one to another windows changes default audio playback device (also directsound device). If I switch to a different monitor WHILE having Firefox open, flash will hang after 1-3 seconds on every video because it can not fill the audio buffers.

Note that switching back doesn't help and it's "hang" most of the time. Only closing/reopening whole FF helps. This is because firefox works on single process, while for example Google Chrome creates new process for each tab - in Chrome if flash playback hangs it's enough just to open new tab with the same URL.

This bug is present since early flash 8.0.

Nope. How do you know someone will fill their buffer? Basically it works like this: someone enters site, sees the player and 10:00 length, clicks in the middle then play - and *boing* *crash*

bump.

What is going on? 4 weeks ? That could be a new record. Any news?

Forget the previous!

http://mirror.facebook.com/apache/apr/CHANGES-APR-1.2

Changes with APR 1.0
[...]
  *) Add apr_strtoff() function for converting numeric strings
 into apr_off_t values.  [André Malo <nd perlig.de>, Joe Orton]

Your apr is too old ! (pre 1.0). I've been compiling under apr-1.3.3 and apr-1.2.11-2. Please update your apr and try again.

Please try adding the following to the beginning of mod_flvx.c file and let me know:

#include "apr.h"
#include "apr_strings.h"

Any news?
Is fix/workaround coming ? (please)

Please test the simplest one:

autoPlay = autoBuffering (in terms of flash calls)

Now the question is, how fast can you pause the video? First frame? first keyframe?

Bottomline: when autoBuffering:true imply autoPlay:true, but pause at the very first frame (possible).

Sounds like a cheap workaround. Cheap, because many streams don't use extensions (i.e. /stream/9192do9rqqsw002312/331).
Workaround, because disabling scrubber helps with nothing. Widely adopted H264 is the new standard for flash (as Adobe states), and proprietary FLV is going to it's retirement. not mentioning AAC.

I'd rather see the "play-before-scrubbing" workaround, even if it jerks a little bit at start. At least we don't loose the functionality.

Consider UI repercussions! - user sees that his video is buffered (like on youtube) - GREAT! He clicks the scrubber but nothing happens - conclusion: seeking doesn't work on this #$@^*&@# site [bounce]

Same here. We're waiting for this critical bug to be fixed before paying. Don't have skills to dig into fla code though.

[...] a quarter- to half-second of video plays from the beginning before it's able to seek. [...]

You could buffer the call to compensate or put the call into an event (onstart, onplay?).

Nope. How would you explain, that seeking after clicking play works, but seeking before clicking play doesn't? It doesn't feel like flash problem, because component decides when to start buffering/playing/seeking. Even if flash has a bug, that makes handling mp4 vs. flv different, the workaround has to be dead simple (like described above). Flowplayer can read type of video from the stream (and/or meta).

It is very hard to believe that it's flash fault, because the UI is controlled by Flowplayer, so at least there is a way to work around it.

Without going into API or tech details...

• Buffering MP4+AAC works.
• Playback works.
• Seeking to ANY pos after pushed play works
• Seeking to any non-buffered part after pushing "play" works (AKA streaming).

We have all the pieces needed to make auto-buffering seek-first solution!

So, beeing totally ignorant to the implementation, our test case could be handled as following:

1. Video auto-buffers itself
2. User clicks any position on the scrubber
3. Flowplayer remembers the clicked position, moves the scrubber head... and sits tight.
4. After user clicks play button, flowplayer executes THE SAME PROCEDURE that it would normally exec when playing from start, but soon after that it seeks to remembered position
5. (optional) If the seeking pos is outside of buffered range, flowplayer buffers (streams) from the given byterange
6. Video playback starts from the selected position

DONE! Simplest workaround in the world :)