KorsaR-ZN / wami-recorder

Automatically exported from code.google.com/p/wami-recorder
0 stars 0 forks source link

WAMI gets JS errors and fails to upload anything #3

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Clone current version of WAMI (72:31f72ebbe172)
2. Load the demo in wami-recorder/example/client/

What is the expected output? What do you see instead?

Expected is that sound will record and playback. Instead on playback get a JS 
alert saying "Security error while playing: 2048". Sometimes get "HTTP Error: 
0" (or something like; it doesn't happen consistently) when record button is 
toggled off.

Error in Firefox JS console (Firebug):
Wami.getRecordingActivity is not a function
var level = Wami.getRecordingActivity();

Error in Chrome JS console:
Uncaught TypeError: Object #<Object> has no method 'getRecordingActivity'

Additional warning in Chrome JS console:
event.layerX and event.layerY are broken and deprecated in WebKit. They will be 
removed from the engine in the near future.

What version of the WAMI recorder are you using? What version of Flash are you 
using?  In what browser?  On what operating system?

WAMI version: 72:31f72ebbe172
Flash version: 11.1.102.55
Operating system: Mac OS X 10.7.2

Describe your server-side set-up if it is relevant to this issue.

Demo uses wami-recorder.appspot.com, so no server side set up on my end. 
Although I also tried making my own WSGI app (self hosted with Paste)and set 
Wami.startRecording to send to it. Same JS errors, plus what's sent to my 
server has Content-Length of zero and CONTENT_TYPE is an empty string. 
Attaching my WSGI app just in case you want to test it too.

Please provide any additional information below.

N/A

Original issue reported on code.google.com by andrew.l...@gmail.com on 3 Jan 2012 at 7:44

Attachments:

GoogleCodeExporter commented 9 years ago
There are actually a few different issues that your post brings up.  The first 
is a bug, which I've just fixed and committed.  I renamed getRecordingActivity 
to getRecordingLevel, but it wasn't changed everywhere that it needed to be.  
This should be fixed now.

I cloned the repository and went directly to 
https://my-clone-name.googlecode.com/hg/example/client/index.html
I was able to record and play just fine... so I'm not able to repeat any of 
your other errors.

With respect to error 2048, usually this is a cross-site scripting problem.  In 
particular, the domain of the flash app isn't supposed to be different from the 
domain of the WAVs being played.  I don't think it matters for recording, but I 
could be wrong.  Anyway, you have to put the crossdomain.xml file in the "root" 
of the domain at which your WAVs will be hosted (e.g. 
http://wami-recorder.appspot.com/crossdomain.xml)

In any case, thanks for filing a ticket.  Feel free to file another if you run 
into any more bugs.

Original comment by mcgrawian@gmail.com on 3 Jan 2012 at 10:16

GoogleCodeExporter commented 9 years ago
I just modified my WSGI script to serve a crossdomain.xml file and the 2048 
error went away and the file saved. So, yes, you do need crossdomain.xml even 
for recording. And now we know.

Original comment by andrew.l...@gmail.com on 4 Jan 2012 at 6:55