Open GoogleCodeExporter opened 8 years ago
Original comment by Owen.R.E...@gmail.com
on 1 Nov 2013 at 4:32
Works on OS/X 10.8.5 (Mountain Lion) with Chrome (30.0.1599.101) on a MacBook
Air (Mid 2012 model).
Also, works OS/X Mavericks with Firefox (25.0), from the Original Reporter.
Original comment by Owen.R.E...@gmail.com
on 8 Nov 2013 at 1:07
Tested on (Ender's) new MacBook Pro running OS/X Mavericks (10.9) (original
installation, not upgrade), and Chrome (30.0.1599.101). Recording a clip for
the Perception video, while logged in as Owen, worked fine!
This seems to rule out:
* OS/X version
* Chrome version
* Flash version
Potential outstanding factors which might affect why it didn't work on the
Original Reporter's machine, and did on Ender's, include:
* Flash permissions (set when the 'Adobe Flash Player Settings' window pops up)
* Chrome plug-ins
* Some effect of upgrading to Mavericks rather than having an original
installation
* Any issue related to a specific username or video (unlikely, but un-tested)
Original comment by Owen.R.E...@gmail.com
on 8 Nov 2013 at 8:04
Tested on (Josh's) MacBook Air, upgraded from OS/X 10.8.5 (Mountain Lion) to
OS/X 10.9 (Mavericks) using Google Chrome (30.0.1599.101), and video
http://youdescribe.ski.org/rel/player.php?v=37aUB92yvHI (the same as the
Original Reporter).
This seems to leave only:
* Flash permissions (set when the 'Adobe Flash Player Settings' window pops up)
* Chrome plug-ins
* Any issue related to a specific username
Original comment by Owen.R.E...@gmail.com
on 9 Nov 2013 at 1:39
Also verified with Safari 7.0 on Mavericks on that same MacBook Air, using the
video http://youdescribe.ski.org/rel/player.php?v=37aUB92yvHI.
Original comment by Owen.R.E...@gmail.com
on 11 Nov 2013 at 6:27
Changing to Low priority, since this appears to only affect one user, and that
user has a work-around by using Firefox.
Original comment by Owen.R.E...@gmail.com
on 11 Nov 2013 at 7:48
While doing some research on replacing the capture.swf Flash module, this
comment seems to match our issue:
http://stackoverflow.com/questions/17061582/when-encoding-to-mp3-in-shinerecorde
r-encoding-stops-if-volume-is-too-high
"Okay, basically we have the jRecorder implemented in our website which
provides the ability for us to capture audio in WAV format.
Now, after the capture, we use the ShineMP3Encoder to convert that WAV to MP3
(to save on file size). This all works fine.
Numerous people have encountered an issue in that if the recorded audio levels
are too high, MP3 encoding will completely stop and the file will become
corrupt/short. When performing this with a WAV, it seems the WAV doesn't care
how loud the recorded audio is and will happily play it back as is."
Based on this, and some other research, I suspect capture.swf is using the
ShineMP3Encoder; the comment "the file will become corrupt/short" exactly
matches our observation.
Original comment by Owen.R.E...@gmail.com
on 25 Feb 2014 at 6:00
Some other audio issues for descriptions recorded using Chrome on OS X have
occurred; in this case, the MP3 file is not bad/corrupt, but the audio seems to
be played back too fast.
http://youdescribe.ski.org/test/vidinfo.php?v=zMGrvoo-RWU&format=html
According to YouDescribe's log file, the clips were recorded using Chrome
v33.0.1750.117 on OS X 10.6.8 (Snow Leopard). That version of Chrome was
released on Feb 20th, so it's basically up to date, and Flash is built-in with
Chrome, so it's not an issue with an old version of Flash.
This is not identical to the issue originally reported, but is still an issue
with Chrome on Mac OS/X.
Original comment by Owen.R.E...@gmail.com
on 25 Mar 2014 at 12:47
Another user with OS/X 10.9.2 (Mavericks) and Chrome 34.0.1847.116 (which
includes Flash 13.0.0) has been able to consistently repeat the behavior of
creating bad (short & not valid MP3) audio clips. Some new code in YouDescribe
is able to detect and log this situation, but no error is presented to the user.
I upgraded a Windows 7 machine to Chrome 34.0.1847.116 (the latest Windows
version, also including Flash 13.0.0), and was once able to reproduce the bad
clip creation. Since then, I've been unable to reproduce it with this version
of Chrome on Windows 7.
Original comment by Owen.R.E...@gmail.com
on 14 Apr 2014 at 5:48
Original issue reported on code.google.com by
Owen.R.E...@gmail.com
on 1 Nov 2013 at 4:29