Verified
Status Update
Comments
jo...@gmail.com <jo...@gmail.com> #2
Could you please provide additional detail on which TV make and model, and what specific content you have the issue with.
th...@gmail.com <th...@gmail.com> #3
TV set is a 2012 model Samsung UE40D8005YUXXE. And the content is all that
are available on-demand from the national norwegian broadcaster NRK.
All material are 25/50 FPS as is common in Europe.
Both my Chromecast and my MythTV box are powered continiously.
When the TV set is switched on, I have to set the MythTV HDMI framerate to
50Hz manually - every time. I believe that the TV set initializes the HDMI
framerate to 60 Hz at power on.
If you need a tester, I will gladly cooperate with you.
9. sep. 2014 22:17 skrev <google-cast-sdk@googlecode.com> følgende:
are available on-demand from the national norwegian broadcaster NRK.
All material are 25/50 FPS as is common in Europe.
Both my Chromecast and my MythTV box are powered continiously.
When the TV set is switched on, I have to set the MythTV HDMI framerate to
50Hz manually - every time. I believe that the TV set initializes the HDMI
framerate to 60 Hz at power on.
If you need a tester, I will gladly cooperate with you.
9. sep. 2014 22:17 skrev <google-cast-sdk@googlecode.com> følgende:
jo...@gmail.com <jo...@gmail.com> #4
Thanks for the details.
Could please confirm what you have set for the following settings on your TV:
Film Mode (Menu->Picture->Picture Options)
Motion Plus (Menu->Picture->Picture Options)
Also, could please reboot your Chromecast device, then after 1 min, start the Chromecast app on your mobile device, select your Chromecast device from the list of devices and then use the menu option to submit a feedback report. Please prefix the report feedback title with " Issue 374 :" so that we can find it.
Could please confirm what you have set for the following settings on your TV:
Film Mode (Menu->Picture->Picture Options)
Motion Plus (Menu->Picture->Picture Options)
Also, could please reboot your Chromecast device, then after 1 min, start the Chromecast app on your mobile device, select your Chromecast device from the list of devices and then use the menu option to submit a feedback report. Please prefix the report feedback title with "
im...@chromium.org <im...@chromium.org> #5
Settings are (and have been) as requested and feedback is returned.
Settings have no effect on judder. Judder is most visible when panning.I should wish there were an option to set HDMI framerate in Chromecast.
Settings have no effect on judder. Judder is most visible when panning.I should wish there were an option to set HDMI framerate in Chromecast.
tr...@gmail.com <tr...@gmail.com> #6
We got your feedback, but the chromecast device logs is missing. Please make sure that the 'Send device logs' checkbox is checked in the Chromecast app for you device and please resend the feedback with the same title.
ma...@gmail.com <ma...@gmail.com> #7
This is caused by the fact that Chromecast plays 25fps/50fps content at 60Hz output video refresh rate (as is evident by the fact that the reporter has the same juddered behavior when he plays 25/50 content on his other devices using 60Hz video mode).
Since 25 is not an exact multiple of 60, the frames are played out at an uneven rate:
2-2-3-2-3-2-2-3-2-3
(each number represents an incoming 25p input video content frame and the value is the amount of HDMI output frames that contain the input frame)
For 50p content played back at the Chromecast 60Hz video mode:
1-1-1-1-2-1-1-1-1-2
So every fifth frame is duplicated, while the rest of the frames play too fast, causing a judder effect.
However, my experience is that only about 5-30% of people actually notice such judder (and many of those don't care). This has still come up many times in the Chromecast Help Forums, for example, however.
The judder is especially noticiable in panning shots and sports content.
Similar issue happens with most movie and North American TV series content as well. Both of those are 24p (or 23.976p), and thus playing them back on a 60hz video mode causes the following frame cadence:
2-3-2-3-2-3-2-3-2-3
This is much less noticiable than the 50p/25p issues since the "pattern" is short, but still an issue (you can google for "chromecast 24p" to find people suffering from this).
To fix this, Chromecast should automatically (or add an API to allow the application "manually" to) switch the HDMI video mode to 50Hz output (e.g. CEA-861 VIC 31) for 25/50fps content and 24Hz/23.976Hz (VIC 32) for 24/23.976fps content. Doing this automatically is the behavior of e.g. Samsung blu-ray players (and others) when using Netflix, when playing e.g. British TV content the video mode switches to 50Hz and when playing back movies it goes to 24Hz (as can be seen in the TV UI as video mode), instead of being fixed to 60Hz like on Chromecast.
I'm also experiencing this issue with all of the TV content here in Finland (which is 25p or in some cases 50p). I've tried on LG 55LH5000, LG 42LH2000 (with all motion interpolation related settings off) and on some other models, but this should affect all TV models. I can provide more info if needed.
Since 25 is not an exact multiple of 60, the frames are played out at an uneven rate:
2-2-3-2-3-2-2-3-2-3
(each number represents an incoming 25p input video content frame and the value is the amount of HDMI output frames that contain the input frame)
For 50p content played back at the Chromecast 60Hz video mode:
1-1-1-1-2-1-1-1-1-2
So every fifth frame is duplicated, while the rest of the frames play too fast, causing a judder effect.
However, my experience is that only about 5-30% of people actually notice such judder (and many of those don't care). This has still come up many times in the Chromecast Help Forums, for example, however.
The judder is especially noticiable in panning shots and sports content.
Similar issue happens with most movie and North American TV series content as well. Both of those are 24p (or 23.976p), and thus playing them back on a 60hz video mode causes the following frame cadence:
2-3-2-3-2-3-2-3-2-3
This is much less noticiable than the 50p/25p issues since the "pattern" is short, but still an issue (you can google for "chromecast 24p" to find people suffering from this).
To fix this, Chromecast should automatically (or add an API to allow the application "manually" to) switch the HDMI video mode to 50Hz output (e.g. CEA-861 VIC 31) for 25/50fps content and 24Hz/23.976Hz (VIC 32) for 24/23.976fps content. Doing this automatically is the behavior of e.g. Samsung blu-ray players (and others) when using Netflix, when playing e.g. British TV content the video mode switches to 50Hz and when playing back movies it goes to 24Hz (as can be seen in the TV UI as video mode), instead of being fixed to 60Hz like on Chromecast.
I'm also experiencing this issue with all of the TV content here in Finland (which is 25p or in some cases 50p). I've tried on LG 55LH5000, LG 42LH2000 (with all motion interpolation related settings off) and on some other models, but this should affect all TV models. I can provide more info if needed.
im...@chromium.org <im...@chromium.org> #8
Please reboot your Chromecast device, then after 1 min, start the Chromecast app on your mobile device and select your Chromecast device from the list of devices. Make sure that the 'Send device logs' checkbox is checked in the Chromecast app for your device, then use the menu option to submit a feedback report. Please prefix the report feedback title with " Issue 374 :" so that we can find it.
ka...@google.com <ka...@google.com> #10
Hi from Germany,
I an experiencing the same issue with any other TV I have used so far, because chromecast won't switch to 50Hz and all video material in Europe is 50Hz.
MT
I an experiencing the same issue with any other TV I have used so far, because chromecast won't switch to 50Hz and all video material in Europe is 50Hz.
MT
jo...@gmail.com <jo...@gmail.com> #11
Same problem for me. Chromecast is always running in 60Hz causing judder for 50Hz content.
/Andreas
/Andreas
jo...@gmail.com <jo...@gmail.com> #12
[Comment deleted]
[Deleted User] <[Deleted User]> #13
[Comment deleted]
sc...@chromium.org <sc...@chromium.org> #14
Same issue here in sweden. Looking on sport gets me dizzy and a bit headache. Chromecast is connected to applicera Yamaha and tv Panasonic. Same issue if i connect direct to tv
sc...@chromium.org <sc...@chromium.org> #15
Same problem here. I even tried to run Chromecast through the HDMI in on my Xbox One console and forcing 50 Hz output. Yet the judder persisted.
All tv carriers and many content provideres in Europe broadcast in 50 Hz. Thus it's imperative that a viable solution is found.
BR,
Anders
All tv carriers and many content provideres in Europe broadcast in 50 Hz. Thus it's imperative that a viable solution is found.
BR,
Anders
sc...@chromium.org <sc...@chromium.org> #16
Same issue here (Denmark). Chromecast is basically useless for 25/50Hz and for 24Hz.
I have returned it for a refund.
I have returned it for a refund.
sc...@chromium.org <sc...@chromium.org> #17
I didn't notice this behaviour until this evening when I was watching supposedly smooth output from YouTube. The juddering effect on my UK TV (almost the same Samsung model D8000 as above, with Game Mode enabled) is very distracting!
I very much hope this is not a case where 'you get what you pay for' :(
I very much hope this is not a case where 'you get what you pay for' :(
sc...@chromium.org <sc...@chromium.org> #18
Will this be fixed? Or is that impossible due to hardware limitations? That would be really sad...
sc...@chromium.org <sc...@chromium.org> #19
Same here. 24p content looks really ugly on Chromecast.
Armchair developer speaking here:
The framerate is a meta-information that comes with the video stream. The Chromecast firmware should be able to parse this information and then switch the video mode's framerate.
The stick's hardware is probably able to do this (these days it's tough to find SoC video hardware that can't switch to 24/25/50/60 framerates), so it's more a driver/firmware issue.
Please add this feature. Thx.
Armchair developer speaking here:
The framerate is a meta-information that comes with the video stream. The Chromecast firmware should be able to parse this information and then switch the video mode's framerate.
The stick's hardware is probably able to do this (these days it's tough to find SoC video hardware that can't switch to 24/25/50/60 framerates), so it's more a driver/firmware issue.
Please add this feature. Thx.
sc...@chromium.org <sc...@chromium.org> #20
It would be really nice to see this issue solved in the next FW version.
Regards
Regards
sc...@chromium.org <sc...@chromium.org> #21
I am starting to wonder whether this is hardware limitation. This issue has been know for a while and there has been no statement from Chromecast team whatsoever. It has been discussed several times on user product forum: https://productforums.google.com/forum/#!forum/chromecast with no particular outcome.
sc...@chromium.org <sc...@chromium.org> #22
Just guessing:
I doubt it's a hardware limitation, but it could be a usability "feature" in favour of KISS.
There are TVs that do not support 24p. By using 60p only, the Chromecast never shows a black screen to users who own a TV like that.
I doubt it's a hardware limitation, but it could be a usability "feature" in favour of KISS.
There are TVs that do not support 24p. By using 60p only, the Chromecast never shows a black screen to users who own a TV like that.
sc...@chromium.org <sc...@chromium.org> #23
This is a feature that has existed in DVD, mediaplayers and set top boxes for ages. Even the chinese Android TV sticks can change refresh rates. That Google could not get it to work would be astonishing. All HDMI tv sets report which resolutions they are capable of. All signs point to laziness from Goggles side.
As mentioned, all European movies, tv shows and especially sport which contain camera panning or moving objects are a pain to watch due to stuttering. Until this is fixed I could never recommend this product.
As mentioned, all European movies, tv shows and especially sport which contain camera panning or moving objects are a pain to watch due to stuttering. Until this is fixed I could never recommend this product.
pa...@gmail.com <pa...@gmail.com> #24
Same issue confirmed by me watching svtplay (sweden) I bought this device in USA and though it might be a different version of the cromecast HW. Seams not to be the case. Until this is solved the device has limited usage in my home.
sc...@chromium.org <sc...@chromium.org> #25
Same Issue with my TV (LG 42LM620S) when streaming YouTube or from the Plex Media-Server.
pa...@gmail.com <pa...@gmail.com> #26
Same problem here in Germany with my Sony KDL 46NX715, for example when streaming from Plex - movies are not watchable. Don't use the chromecast any more until this issue is fixed.....
sc...@chromium.org <sc...@chromium.org> #27
Samsung UE55ES7090
Chromecast ruckelt bei Kameraschwenks... (ansonsten ruckelt der TV nicht !)
Chromecast ruckelt bei Kameraschwenks... (ansonsten ruckelt der TV nicht !)
sc...@chromium.org <sc...@chromium.org> #28
Same issue for me (Germany).
Brought back to the shop after 10 minutes of usage.
Could not believe it.
My prediction: It will NOT be fixed.
Brought back to the shop after 10 minutes of usage.
Could not believe it.
My prediction: It will NOT be fixed.
la...@google.com <la...@google.com> #30
This issue is the reason why I will not buy Chromecast or recommend it to anyone. Smooth framerate, and matching of hdmi frequency to video content is a must have for a video player.
fi...@chromium.org <fi...@chromium.org> #31
Same problem - chromecast and android hdmi output does not switch to the 50p or 24p Video framerate and this produces extreme stuttering. This needs to get fixed!
fi...@chromium.org <fi...@chromium.org> #33
We appreciate everybody's input on this issue. Our engineers have spent some time investigating the issue and have worked with our hardware partners to consider various solutions. Our conclusion is that the TV is in the best position to handle HDMI refresh rates. Chromecast cannot attempt to handle changes in HDMI refresh rates since it is very hard to accurately identify the incoming frame rate. Also, every time there is a HDMI mode change, it usually leads to flashing or loss of picture for a few seconds. Blu-ray players can handle this issue because discs have extra metadata that would allow players to output at the most suitable rate. This is very hard to pull off with streaming content.
da...@chromium.org <da...@chromium.org> #34
Then why are you not providing a MANUAL setting through Chromecast app, or are we forced to buy an AppleTV, which actually works in 50hz?
fi...@chromium.org <fi...@chromium.org> #36
unbelievable....
da...@chromium.org <da...@chromium.org> #37
@lnicho: That's a joke, isn't it? **head shake**
bu...@chromium.org <bu...@chromium.org> #38
How can Inicho... say that the TV is in the best position to handle HDMI refresh rate when the Chromecast is only outputting 60hz???
Come on, please provide at MANUAL setting then in the app if you cant fix it other wise. We need this baaaadly in Europe.
Come on, please provide at MANUAL setting then in the app if you cant fix it other wise. We need this baaaadly in Europe.
da...@chromium.org <da...@chromium.org> #39
They won't read any new comment, I think. This issues status is "closed", so they will ignore this thread from this moment.
They will never fix this issue (or rather offer an manual setting) as the US are the center point of the Universe, and they are not interested in problems around them.
They will never fix this issue (or rather offer an manual setting) as the US are the center point of the Universe, and they are not interested in problems around them.
al...@chromium.org <al...@chromium.org> #40
The refresh rate really only needs to be changed when playback is started,
at the point the app will know what refers rate is required. The app needs
a way to tell the Chromecast what to do. The Chromecast doesn't need to
figure out anything.
Plenty of networked media players do this automatically, perhaps Google
engineers could have a look at the many open-source projects that are
available?
at the point the app will know what refers rate is required. The app needs
a way to tell the Chromecast what to do. The Chromecast doesn't need to
figure out anything.
Plenty of networked media players do this automatically, perhaps Google
engineers could have a look at the many open-source projects that are
available?
[Deleted User] <[Deleted User]> #41
I expect that statement be should be enough to get a refund under consumer protection laws but personally I'm disappointed that Google is incapable of finding a solution which means I won't be looking to Google for any future media playback devices.
Google knows the origin of the apps, set the default refresh appropriately. For multinational content providers like Netflix offer a selection option which could be hidden in the settings menu, or just add a switch refresh rate option in the Chromecast app as suggested above.
I understand why Google wants friction free viewing, but for those of us who know what the problem is and its causes and who are bothered enough to complain is there really going to be no fix or workaround.
With the Chromecast references to H2G2-42 and MST3K there must be someone in Google smart enough to find a solution :P
Google knows the origin of the apps, set the default refresh appropriately. For multinational content providers like Netflix offer a selection option which could be hidden in the settings menu, or just add a switch refresh rate option in the Chromecast app as suggested above.
I understand why Google wants friction free viewing, but for those of us who know what the problem is and its causes and who are bothered enough to complain is there really going to be no fix or workaround.
With the Chromecast references to H2G2-42 and MST3K there must be someone in Google smart enough to find a solution :P
sc...@chromium.org <sc...@chromium.org> #42
Unbelievable ignorance.
Just a manual setting of the frame rate would satisfy most here.
Just a manual setting of the frame rate would satisfy most here.
[Deleted User] <[Deleted User]> #43
Quote : Our conclusion is that the TV is in the best position to handle
HDMI refresh rates
That is correct, our TVs are capable of handling all different refresh
rates, but the Chromecast forces all input to 60hz!!!
So please Google give us at least a workaround by means of a manual setting
or whatever.
There is more than only 60Hz in the world :(
2014-11-26 9:46 GMT+01:00 <google-cast-sdk@googlecode.com>:
HDMI refresh rates
That is correct, our TVs are capable of handling all different refresh
rates, but the Chromecast forces all input to 60hz!!!
So please Google give us at least a workaround by means of a manual setting
or whatever.
There is more than only 60Hz in the world :(
2014-11-26 9:46 GMT+01:00 <google-cast-sdk@googlecode.com>:
[Deleted User] <[Deleted User]> #44
Approx 30 people have complained about this - how many Chromecasts have been sold? That, regrettably, is the reason this is a 'wontfix.'
A shame, but there you go. Perhaps the next generation of Chromecast hardware will address this. <shrug>
A shame, but there you go. Perhaps the next generation of Chromecast hardware will address this. <shrug>
da...@chromium.org <da...@chromium.org> #45
This response does not make much sense.
"It is very hard to accurately identify the incoming frame rate."
Obviously, the video mode's refresh rate should only be changed when the video stream's meta data contain the refresh rate information. Otherwise, using a 60Hz default should be fine.
"Also, every time there is a HDMI mode change, it usually leads to flashing or loss of picture for a few seconds."
Then make the ability for video mode refresh rate change an optional and disable it by default. (That's how my blu ray player does it, too.)
"Our conclusion is that the TV is in the best position to handle HDMI refresh rates."
Yes. But the Chromecast uses 60Hz, only. The TV or the user both cannot override that.
"It is very hard to accurately identify the incoming frame rate."
Obviously, the video mode's refresh rate should only be changed when the video stream's meta data contain the refresh rate information. Otherwise, using a 60Hz default should be fine.
"Also, every time there is a HDMI mode change, it usually leads to flashing or loss of picture for a few seconds."
Then make the ability for video mode refresh rate change an optional and disable it by default. (That's how my blu ray player does it, too.)
"Our conclusion is that the TV is in the best position to handle HDMI refresh rates."
Yes. But the Chromecast uses 60Hz, only. The TV or the user both cannot override that.
ev...@techmission.org <ev...@techmission.org> #46
[Comment deleted]
da...@chromium.org <da...@chromium.org> #47
Simple explanation why this is "no issue" for most is basically described here: https://www.change.org/p/hdtv-manufacturers-please-stop-making-smooth-motion-the-default-setting-on-all-hdtvs . As long as hardware manufacturers rely on IFC and similar systems, mass users will not see any difference with Chromecast outputting on 60hz, as any judder (including the natural "film look" of 24p) gets washed away by SDK. The artifacts and unpleasantness of resulting image goes unnoticed by most, unfortunately.
I still, however, do not see a point in not including this setting in dev mode or in SDK for the respective apps to instruct Chromecast (e.g. BBC to output in 50hz etc.).
I still, however, do not see a point in not including this setting in dev mode or in SDK for the respective apps to instruct Chromecast (e.g. BBC to output in 50hz etc.).
ev...@techmission.org <ev...@techmission.org> #48
Sorry for beating the dead horse, but please search for
XBox One 50Hz
with your favourite search engine.
Microsoft's game console was affected by this problem, as well, and it resulted in quite a stink, see <http://www.theguardian.com/technology/2013/nov/26/xbox-one-juddering-plagues-uk-tv-watchers > as an example.
The guys at Microsoft have been able to fix this with a later firmware update, so I wonder what's stopping the Chromecast team.
XBox One 50Hz
with your favourite search engine.
Microsoft's game console was affected by this problem, as well, and it resulted in quite a stink, see <
The guys at Microsoft have been able to fix this with a later firmware update, so I wonder what's stopping the Chromecast team.
da...@chromium.org <da...@chromium.org> #49
[Comment deleted]
da...@chromium.org <da...@chromium.org> #50
[Comment deleted]
sc...@chromium.org <sc...@chromium.org> #51
We should open an new issue-thread. I don't think, that they read any comments on closed threads (arrogantly).
ev...@techmission.org <ev...@techmission.org> #52
I develop video software for a living and have done so for the last 15 years. I fully understand the difficulties in reliably parsing the frame rate from streams where the incoming timestamps dictate the rate of video play and the joys of HDMI control.
Europe has a large installed base of TVs made prior to the advent of good video post processing. These TVs will not cope with 60Hz streams and pull out the originating 24Hz/23.97Hz/25Hz content then motion interpolate it to a higher rate as many newer sets do.
It is extremely remiss of you not to provide an option to force the default output rate of the device to 50Hz as nearly every other player in this space has done (albeit it belatedly in some cases). They should also however be providing a force 24Hz option too but many don't giving you an opportunity to beat the rest.
Europe has a large installed base of TVs made prior to the advent of good video post processing. These TVs will not cope with 60Hz streams and pull out the originating 24Hz/23.97Hz/25Hz content then motion interpolate it to a higher rate as many newer sets do.
It is extremely remiss of you not to provide an option to force the default output rate of the device to 50Hz as nearly every other player in this space has done (albeit it belatedly in some cases). They should also however be providing a force 24Hz option too but many don't giving you an opportunity to beat the rest.
ev...@techmission.org <ev...@techmission.org> #53
> Blu-ray players can handle this issue because discs have extra metadata that
> would allow players to output at the most suitable rate. This is very hard to
> pull off with streaming content.
If this is a reference to my comment regarding Samsung Blu-ray players doing automatic refresh rate switching, note that I talked about *streaming* content, not discs. They can automatically switch to 24p or 50p when needed.
It could well be the streaming application that sets the refresh rate (rather than the player probing the video stream), though, but IMHO that would probably be "good enough" for Chromecast as well - the ability for the Cast receiver to set a preferred refresh rate via the API, similar to Android "preferredRefreshRate" attribute added to WindowManager.LayoutParams in Android 5.0 Lollipop for presumably exactly this purpose (http://developer.android.com/reference/android/view/WindowManager.LayoutParams.html#preferredRefreshRate ).
> would allow players to output at the most suitable rate. This is very hard to
> pull off with streaming content.
If this is a reference to my comment regarding Samsung Blu-ray players doing automatic refresh rate switching, note that I talked about *streaming* content, not discs. They can automatically switch to 24p or 50p when needed.
It could well be the streaming application that sets the refresh rate (rather than the player probing the video stream), though, but IMHO that would probably be "good enough" for Chromecast as well - the ability for the Cast receiver to set a preferred refresh rate via the API, similar to Android "preferredRefreshRate" attribute added to WindowManager.LayoutParams in Android 5.0 Lollipop for presumably exactly this purpose (
bu...@chromium.org <bu...@chromium.org> #54
I would advise everyone who has this issue to return their chromecast. Maybe that will make google listen. Pretty pathetic.
bu...@chromium.org <bu...@chromium.org> #55
This is awful, it should be easy to allow the HDMI refresh rate to be changed :S
bu...@chromium.org <bu...@chromium.org> #56
"We appreciate everybody's input on this issue. Our engineers have spent some time investigating the issue and have worked with our hardware partners to consider various solutions. Our conclusion is that the TV is in the best position to handle HDMI refresh rates. Chromecast cannot attempt to handle changes in HDMI refresh rates since it is very hard to accurately identify the incoming frame rate. Also, every time there is a HDMI mode change, it usually leads to flashing or loss of picture for a few seconds. Blu-ray players can handle this issue because discs have extra metadata that would allow players to output at the most suitable rate. This is very hard to pull off with streaming content."
Huh?
If the metadata is missing, let the user manually override. (With both a system default, and a per-session setting)
If the metadata is there, use it.
Also: Use your Google clout to make sure streams DO CONTAIN this metadata.
Flicker from the TV? Who cares? Switching channels also gives "flicker". I don't care if the image is lost for a few seconds just when the casting starts. It's at least 5000 seconds of shitty vs. nice motion coming up, so I can sacrifice two seconds to get the good version. Makes sense, no?
If you don't take video seriously, what's the point of using your video products?
Huh?
If the metadata is missing, let the user manually override. (With both a system default, and a per-session setting)
If the metadata is there, use it.
Also: Use your Google clout to make sure streams DO CONTAIN this metadata.
Flicker from the TV? Who cares? Switching channels also gives "flicker". I don't care if the image is lost for a few seconds just when the casting starts. It's at least 5000 seconds of shitty vs. nice motion coming up, so I can sacrifice two seconds to get the good version. Makes sense, no?
If you don't take video seriously, what's the point of using your video products?
bu...@chromium.org <bu...@chromium.org> #57
... and do you really expect anyone in Europe to buy into Android TV? More beta hardware to go with your beta software... :/
is...@google.com <is...@google.com> #58
Plees fix
Description
Google Chrome: 16.0.912.75 (Official Build 116452)
OS: Mac OS X
WebKit: 535.7 (@103989)
JavaScript: V8 3.6.6.15
Flash: 11.1.102.55
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.75 Safari/535.7
Command Line: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome -psn_0_13274280 --flag-switches-begin --enable-print-preview --flag-switches-end
Executable Path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Profile Path: /Users/joshua/Library/Application Support/Google/Chrome/Default
URLs (if applicable):http://www.vizualrecords.com/wordpress/wp-content/audio/VIZLP1-01_128.mp3
OS version: Mac OSX 10.6.8 (Snow Leopard)
Network (such as Cable/DSL/Dial up etc): Cable/Wireless
Audio/Video format (if applicable): MP3 128kbps CBR 44.1/Stereo
Special chrome flags (if applicable):
Behavior in Safari (if known): File plays Safari 5.1.2 (6534.52.7)
Behavior in Firefox (if known): File plays Firefox (8.0.1)
Video issue, Audio issue, both, neither? Audio
Flash or HTML5? HTML5
What steps will reproduce the problem?
Try to play certain mp3 files using Google Chrome.
What is the expected result?
File will play.
What is the actual result?
File won't play.
Any additional information (anything else which may help us debug the
issue)?
Came across this issue when troubleshooting the MP3 jPlayer plugin (1.7.3) for WordPress (3.3.1) although the problem occurs independently of these. Certain mp3 files simply won't play in Chrome although they will play in Safari and Firefox. I've been going back and forth with the developer of the MP3 jPlayer plugin to try to figure out why and we are stumped.
Go to this URI in Chrome:http://www.vizualrecords.com/wordpress/wp-content/audio/VIZLP1-01_128.mp3
It won't play. Will play in Safari and Firefox.
I'm thinking it's something in the encoding that Chrome doesn't like. This file was encoded with iTunes-LAME. Recently encoded mp3 files using iTunes (without the iTunes-LAME encoder) and Pro Audio Converter (using LAME encoder 3.98.4) play fine in Chrome.
That said, this file was encoded with iTunes 10.4.1 (without LAME) and Chrome won't play it either:http://www.vizualrecords.com/wordpress/wp-content/audio/VIZLP1-10_128.mp3
As I am using HTML5 audio to preview songs I'm selling, I'll probably have to re-encode a bunch of files so that they play in Chrome but I would really like to know what is causing this. Hopefully it will be resolved in an update.
Please attach the HTML5/JavaScript code or audio/video files as well as
screenshot and/or videos (if applicable)