Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems in Safari on Win7 #27

Open
sam1337 opened this issue Feb 27, 2013 · 4 comments
Open

Problems in Safari on Win7 #27

sam1337 opened this issue Feb 27, 2013 · 4 comments

Comments

@sam1337
Copy link

sam1337 commented Feb 27, 2013

Hi,
I am using Recorder.js and it works fine on Firefox, Chrome and IE, but not in Safari.

The recording doesn't start, even if I get the Flash auth, and the "started" event is fired. No "progress" event and no recording.

What is weird is that if I record/stop, play/stop multiple times, then at some point it starts to work, but only one time (if I stop and record again it still doesn't work)

Anything I could try to make this work?

@sam1337
Copy link
Author

sam1337 commented Feb 27, 2013

Does seem to do the same thing with the Upload. (works sometimes only).
I guess there is a problem with the link between the javascript and the flash.
Also, Safari's log console shows nothing. no errors... :(

@sam1337
Copy link
Author

sam1337 commented Feb 27, 2013

Using Recorder.flashInterface().debugLog() I got the following traces. (see attached images)
They are the output of the debuglog after each time it works or not.
I have to play/pause to make it work, and it seems to work until I play/pause again.

At first, not working:
NotWorking
Then after play/stop, it works:
Working
Then after another play/stop it stops working.
Working2
After another play/stop working again.
NotWorking2

What does it mean?

@sam1337
Copy link
Author

sam1337 commented Feb 27, 2013

After removing Recorder.stop() before recording, I am able to record if I stop/re-record.
At start it works one time out of two, and after a couple times it works only 1/4, 1/5...
There must be something not clearing or added in events that shouldn't be there.

@sam1337
Copy link
Author

sam1337 commented Feb 27, 2013

I bypassed the problem by adding a timeout function to stop/re-record if the "progress" is not called after 2 seconds

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant