player control stops working in release LC 7.0.1 stable

[Coffee1633]

App-y New Year everyone
Here's to a feature rich, stable and robust LiveCode in 2015.

I just switched over to version 7.0.1 stable from 7.0.1 rc4 and my player controls stopped working. Huh?... Using them to play mp3 audio files on desktop and mobile. Is anyone else having problems with their player controls in the most latest release of LC commercial: 7.0.1 stable?
It's not me, right? For now I'm just going back to rc4 version and will sort it out later.

Coffee16

[Axel-Erfurt]

same on 7.02

[Klaus]

Hi guys,

unfortunately this is another (new) bug in LC 6.7.x and 7.x
This will be addressed in the next release.

Clicking the "play" button in the controller does not start the player,
but there is a workaround, which requires scripting.

Dont work:
start player XYZ

Works:
set the playrate of player XYZ to 1

No idea how THIS could have slipped through the dev team!?


Best

Klaus

[Coffee1633]

I'm so glad someone else is having the same problem. I was worried it was something I was doing wrong but I couldn't image what it could be. playing audio is pretty straight forward.

btw, I am always reluctant to post a bug report cause I just think that it is something that I am doing wrong and not the engine and I don't want to waste the LC engineer's time. It's hard for me to tell if it's just me or is it LC.

Thanks for the work around. I couldn't use the latest version 7.0.2 because none of my audio was playing.

UPDATE
After playing around with the playrate prop, I see that the fix is also a bug. My player starts playing when I set the playrate. That doesn't sound right at all.
Looking forward to the bug fix

[Klaus]

Hi Coffee113,

My player starts playing when I set the playrate. That doesn't sound right at all.

this is intended behavior, but maybe bad or missing documentation, since it will actually start a player when
setting the playrate to any integer <> 0


Best

Klaus

[Coffee1633]

it will actually start a player when
setting the playrate to any integer <> 0

that is the behavior I am getting but it just doesn't seem right on first thought. I was planning on changing the audio playback speed in a settings panel to either "fast", "normal" or "slow" which correspond to something around 1.3, 1.0, 0.7 the playrate prop but not play any audio at that time. Only when the user clicks the play button does any audio play. Said another way, I thought that setting the playrate prop, like any other prop, would not or should not play any audio. "play" is the command that should play the audio. It seems to me that the playrate prop is also broken, I just want it to set the prop.
But since the play command is broken, it is a convenient work around but it seems a coincidence to me. In this case two wrongs make a "work-around".

What do you think?

[Klaus]

Setting the playrate does work as indicated since it was introduced, and since I am an (very ) old user, this is "normal" behavior for me.