Transcoding breaks Flash player's progress bar?
Posted: Tue Mar 10, 2009 6:48 pmI enabled transcoding using Lame 3.98.2, and I noticed that transcoded files will cause the Flash-based player's progress bar and total time indicators to fail, roughly in proportion to how compressed the output is. (My Lame downsample command, by the way, is "lame -S -h -b %b %s", which is default i think)
For example, I have a song encoded at 192kbps that is 4:00 long. When I set the player to trancode to 128kbps, the total time shows 6:01, and the 'buffered' bar only loads to about 2/3rd of the way (which is about 4:00). When I set the player to transcode to 64kbps, the total time shows 12:03 and the 'buffered' bar loads to about 1/3rd of the way (~4:00). Untranscoded files do not show this behavior.
Fortunately, the player does not stall upon reaching the end of the buffer bar, and instead skips to the next track as expected.
I'm just wondering if this is a known issue, and if there is anything I can do to fix it. It works fine, but it's a little confusing to people when the buffer bar only loads up part-way, as it gives the impression that the connection stalled.
thanks.
For example, I have a song encoded at 192kbps that is 4:00 long. When I set the player to trancode to 128kbps, the total time shows 6:01, and the 'buffered' bar only loads to about 2/3rd of the way (which is about 4:00). When I set the player to transcode to 64kbps, the total time shows 12:03 and the 'buffered' bar loads to about 1/3rd of the way (~4:00). Untranscoded files do not show this behavior.
Fortunately, the player does not stall upon reaching the end of the buffer bar, and instead skips to the next track as expected.
I'm just wondering if this is a known issue, and if there is anything I can do to fix it. It works fine, but it's a little confusing to people when the buffer bar only loads up part-way, as it gives the impression that the connection stalled.
thanks.