Very recently, after the latest Chrome update which includes Adobe Flash Player Version: 12.0.0.41, a flash app that's been running smoothly for years has begun to "hiccup" during one particular function.
Normal behavior - User logs in to app. App grabs some xml files then draws a calendar onscreen.
Hiccup behavior - User logs in to app. App grabs the xml files but feezes before executing the loadComplete function (according to trace). By freezes, I mean the little load spinner remains onscreen but stops spinning and the calendar doesn't appear onscreen.
Interesting/maddening notes - The mouse cursor responds as if the calendar has been drawn (arrow changes to pointer when mouse passes over an invisible calendar day) but according to my trace log the loadComplete and showCal functions haven't fired.
ALSO, any call to a function unfreezes the glitch (e.g. clicking an invisible calendar day, mousingOver a control button, etc. Anything that triggers a function.) and bam! everything's there and the trace log completes as it should.
As stated, this glitch only occurs in Chrome with the latest Flash Player update (12,0,0,41).
Installing the mozilla version of the flash player debugger (12,0,0,43) and instructing chrome to use it instead fixes the glitch, but using it in chrome opens up a whole new can of worms when it comes to flash player glitches (as is to be expected).
Maybe there's nothing I can do and it's just a fault with the latest Chrome flash player build, OR...
There's something fundamentally wrong with my code and Chrome's latest flash player is the only plugin that glitches on my "wrong" code?
I'll happily include some code snippets if someone is convinced my code is the problem but am leaving them off for now since this question is enormous. (you're a trooper for sticking with it)
I'm hoping someone else has experienced this or can at least explain it/fix it. Thanks in advance.
I'm seeing very similar symptoms on an application I work on Frankenscarf. All workarounds have been ineffective thus far. I can confirm it is specific to 12.0.0.41 Pepper Flash. I think you might need to wait for google to fix the lasted release...
I am also having problems with Flash 12.0.0.41 on YouTube, videos very laggy and dropping frames all the time even making the video stutter on 320p. I have disabled Chromes built in Flash player though Chrome://plugins, installed Chrome 11.7.700.260 and now have the videos running smoothly even at 1440p. Hopefully they will sort out the bugs soon.
I wasn't able to edit my original post...
UPDATE: I managed to get a workaround going. I set up a periodic timer (triggering every 500ms), that calls invalidateDisplayList() in my largest container. It is horrible, but it works....
Related
I have a website, that should play mp3 files after clicking on a logo. When a sound is played, the p5.js library (p5js-sound) draws some graphic on the background. Suddenly it has stopped working. In the Chrome console log, the problem is with this line. Without any reason after two years of working properly, it started to give this error
Uncaught TypeError: this.audiocontext.createScriptProcessor is not a
function.
I found out that it works in Firefox and on some computers with older versions of Chrome. How to solve this problem?
Newest versions of Chrome will not "autoplay" audio. Some kind of user interaction is required, ie. click on something to "start" the audio context. When I get it to work I will post code.
It is unlikely that this is a problem with your code or anything you have done to the p5.sound library.
On the contrary, it may be an out-of-date version of the library and the processing foundation may not have updated it yet. They are a non-profit organisation so cut them some slack but I suggest using an alternative library for now
You could use native functions like an onclick="" that controls whether a hidden <audio></audio> tag is playing - Good luck coding!
I would like to dive into WebRTC, particular audio recording. So I tried this DEMO and the first problem arose: when I record in the latest Google Chrome I always hear a high-pitched buzzing sound in the background which is very annoying and probably not intended.
Is that a problem with my computer / settings or is this just normal? Because if this is ordinary, WebRTC is pretty useless for my purpose.
If this is related to my audio-midi-settings – here are some screenshots:
Goto source code and comment this line:
// __stereoAudioRecorderJavacriptNode.connect(context.destination);
Actually microphone is connected with speaker. This causes the recorded audio to be played back in the speakers.
Updated:
This workaround doesn't seems to be working. Sorry.
It was taken from here.
When looking at my video player app yesterday morning, I noticed some odd behavior on the AS3 Chromeless player.
When using the setSize function as documented in the API, the giant play button that overlays the video is now suddenly becoming very large, not even close to the dimensions specified. However, once the play button is clicked, the video player itself is fine. This is throwing off all of the positioning in my app, and looks terrible.
I assume something changed on the Chromeless Player, but I need to get this to work sooner rather than later. Is anyone else experiencing this issue / does anyone have a work around?
Thanks for the help!
Each time you set the size, force a redraw. Its gonna do that when you click it, and apparently, in your case, doesn't.
This is a known problem with the Google Data API for Youtube. People seem to be clamoring for a fix, although Google has not been very responsive.
I've got a real problem with FlashPlayer. What I need is to have it working on full speed when it is in the THROTTLE mode - that means when FlashPlayer loose its focus and decrease framerate to about 4fps. This is commonly know as a feature for mobile phones or when you change a tab in your browser and your .swf movie doesn't run with full speed anymore.
I need this full speed because we run tests with flash swfs on virtual servers, and unfortunatelly tests run very long.
I found that in FP11.2 was ThrottleEvent introduced that inform you what Flash Player is doing. It can go to PAUSE, THROTTLE, or RESUME state. Unfortunatelly it seems that I can't force other stage.frameRate when it really goes into any of these states. I tried also with Event.DEACTIVATE, and Event.ACTIVATE without any results.
Can I go around this any way? Or if not, what version of FlashPlayer was the latest before Adobe incorporated this feature into FP?
Thanks for any response!
Kindest Pawel
you should try
stage.addEventListener(ThrottleEvent.THROTTLE, doStuff)
I'm currently working on a flash game and, at least on my machine, the audio seems to lag by a fraction of a second in Chrome, but not in IE or FF. This isn't a huge deal, the game is still playable, but it's a little bit annoying. Is there anything I can do from a development standpoint to fix this issue or is it something the user would have to fix?
Edit: I've now tested it on two other machines and the same thing happened. The audio is delayed in chrome but not Firefox or IE.
Edit 2: I've also tried the same thing in a few popular games on Newgrounds to the same effect. Is this just something wrong with Chrome?
Edit 3: I tried lowering the bit rate of the audio from 44kHz to 22 and it didn't do anything to fix it. (It also sounded terrible, predictably)
Edit 4: To prove it's not a memory management problem I created a blank SWF that just plays an audio file on mouse click, it also has the lag issue. This is definitely not a Flash or AS3 isolated issue.
I have/had the same problem with Chrome.
if you go to: chrome://plugins (->details) and disable PepperFlash, then it runs smooth. Not sure if Pepper is the default for Chrome, or if its the particular version of flash we installed.
C:\Users\ [USERNAME] \AppData\Local\Google\Chrome\Application\21.0.1180.75\PepperFlash\pepflashplayer.dll
I had an intermittent audio and then the video started to lag. The solution was two fold:
Re-install chrome.
Get the latest Adobe Flash Player.
I had to do both things for it work properly. To get the plugins type the following in chrome address bar: chrome://plugins
After you install the latest player you need to disable the older one.
Hope this resolves your problem as it did for me.