When using SDK 50.2.4.5, error #2004 occurs in NetStream.play(). about adobe-runtime-support HOT 6 OPEN

Hi - you should only call play(null) once .. is there a specific need to call it multiple times?
We've got some protection in there now because of some other changes we'd made around this - so calling play(null) on an already-playing stream isn't valid. I guess we could add the condition that it's okay if you'd previously started the stream with the same call...

I would be interested if you think there is a need for that, or whether you could update your code so that only the first call is made, without any other side effects?

thanks

from adobe-runtime-support.

@koreaflash
Also make sure you don't use ns.play(""); anymore. #3098

from adobe-runtime-support.

I will try update the code.
Thank you.

from adobe-runtime-support.

• We provide educational content.
• Users can learn page by page and move pages freely.
  => Users can access pages containing netstream from time to time.
• There is a function to preload the front or back page of the current page.
  => Users can also use 3 netstreams at the same time.

For the above reasons, play() is called frequently.
Is there a solution...?

from adobe-runtime-support.

Well we can change it so that play(null) is accepted as long as the previous play() calls also had the null argument. But you could just omit that call after the first time; you're calling in the reset action which would have the same effect? or is there then a delay between switching videos whilst the data already sent in is still being processed?

Previously, calling "play(null)" on a netstream which was already playing would just have reset/orphaned everything and set up a new playback pipeline. So there's not a huge difference between that and creating a new NetStream object. But we can add back in the capability, with that security check to ensure it's not being switched between different modes...

from adobe-runtime-support.

Ah - I just checked the code, and this is actually already what it's trying to do. But the check for if the argument is "null" is failing because we're checking that after a string conversion and the object itself then comes out as a non-null object (containing a string with contents "null"!!) -> switching the check here to null-check the original argument, rather than the stringified version...

thanks

from adobe-runtime-support.