the onMouseMove event is to make the volume “knob” appear at the correct position along the “track” - this needs to update whenever the “knob” moves so it seems logical to use the onMouseMove event…please correct me if i’m missing something here.

However - It appears that the mute button does work i.e. i have traced to see if it knows it has been clicked and it does. I’m gonna take a while to work out what it is that doesn’t work though!

Mike

Thanks for taking a look at this and making me dig around a bit more…it’s good to learn that way and i like the challenge.
I do know about the trace function and have used it in other parts of my code but hadn’t actually thought of using it to check when the button had been pressed.

Also, thanks for the pointer on the onMouseMove event….makes perfect sense.

Sorry the code was so long but i just copied and pasted it as it stood and there’s a lot of comments and old code in there for me to be able to see what’s going on.

watch this space please and thanks again.

Mike

I read through the relevant parts of your code (at least, what I thought would be relevant!), and it looks all right so far. Granted, it’s the end of a long day for me. I do notice you have an if statement in the mute button’s event handler, so that means it isn’t just a click-and-respond item: there’s some decision-making involved, and that might lead to what you’re seeing.

Do you know about the trace() function? That might really come in handy for you, because it lets you see what’s going on under the hood. It’s one of those very lightweight, but indispensable, tools that eventually become a consistent part of your everyday workflow.

The first thing you’ll want to do, as you begin troubleshooting, is get into the habit of questioning your assumptions. It seems like the button doesn’t respond on the first click — but are you sure? (You might actually be right; if so, there’s a reason for the necessary second click … but you might just as well have misjudged something, and trace() will help you track down whatever’s unclear.

All trace() does is send message to your Output panel, but that’s a useful thing. Pop that function into your event handler just prior to the if:

mute.onRelease = function():Void {
  trace("mute button clicked")
  if (isMuted) {
    isMuted = false;
    // ...

… that’ll tell you right off the bat if the button does (or does not) respond to the first click. If it does, you’ll see the phrase “mute button clicked” in the Output panel, even if nothing else seems to happen. At that point, you can start tracing other values, such as variables like isMuted, to start poking around even more.

I confess, I didn’t pore through every line of your code carefully, but a couple probably unrelated things jumped out at me: a) you probably don’t want to send mute’s timeline to a frame in response to an onMouseMove event, simply because that event can fire hundreds of times in succession (seems like all you really need to do is invoke that gotoAndStop() method once, during the course of the onPress handler you’re already in, and b) in one of your commented mute button event handlers, you’re checking of so’s volume is greater than 100. In theory, it should only ever fall between 0 and 100, so you might want an >= comparison there instead.

my mute button has four different state with frame labels for each and a stop action in frame 1. labels are as follows:
on, onOver, mute and muteOver

i would like to be able to control the playhead for the mute movieclip position via the AS. I hope that makes sense and sorry for not mentioning the movieclip before, (although i guess you may have spotted what i was doing/trying to do.)

Thanks in advance for any help,

Mike

I’m surprised i can’t find the answer to my issue here already.

I’ve been using this blog/thread to work out how to control a volume knob for my FLV player and to work out how to control a mute button.
Thanks to this thread and others i have a working fader and had managed to have a mute button that toggles on and off and puts the fader knob back to the correct place when toggled back off etc…

If i mute my audio then i drag the slider the audio responds as i would like HOWEVER…my mute button does not respond on the first click but does if it is clicked a second time.

I’m guessing this is because i have some code in the wrong place or just got something horribly wrong!

I’d really appreciate some help and expect this to be useful for others too if they are having the same problem.

hers my code i hope:

// sound control starts here
_root.createEmptyMovieClip(”vSound”,_root.getNextHighestDepth());
vSound.attachAudio(ns);

var so:Sound = new Sound(vSound);

so.setVolume(50);
// set initial volumeknob position to half way along track
// ****
volumeknob._x = track._x + (track._width/2)
volumeknob._y = track._y

// trace various positions to check position of volumeknob compared to track
trace(track._x);
var trackpositionr:Number
trackpositionr = (track._x + track._width);
trace(trackpositionr);
// trace the sidth of track and store in var
trace(trackpositionr - track._x);
var trackwidth = (trackpositionr - track._x);
// these next two values should be the same if all is well
trace(track._x + trackwidth/4);
trace(volumeknob._x);
// ****

// slider sound controls start here i hope
var ratio:Number = track._width / 100;

volumeknob.onPress = function():Void {
var vertical:Number = track._y + (track._height / 2);
this.startDrag(
true,
track._x,
vertical,
track._x + track._width,
vertical

);
this.onMouseMove = updateKnobOutput;
// make “mute” state display the not muted position because the volumeknob as ben moved
mute.gotoAndStop(”on”);
}

volumeknob.onRelease = function():Void {
this.stopDrag();
delete this.onMouseMove;

// set preVolume to equal the volumeknob current position value so that
// if “mute” is depressed again the volumeknob doesn’t get altered
// not sure if this is the correct way of implementing but it seems to work
prevVolume = volumeknob._x;
}

volumeknob.onReleaseOutside = knob.onRelease;

function updateKnobOutput():Void {
so.setVolume((volumeknob._x - track._x) / ratio);

}
// slider sound controls end here

// ****
// new mute on or off starts here

var isMuted:Boolean = false;
var prevVolume:Number = 0;
mute.onRelease = function():Void {
if (isMuted) {
isMuted = false;
volumeknob._x = prevVolume;
so.setVolume((volumeknob._x - track._x) / ratio);
mute.gotoAndStop(”on”);

}
else {
isMuted = true;
prevVolume = volumeknob._x;
volumeknob._x = track._x;
so.setVolume((volumeknob._x - track._x) / ratio);
mute.gotoAndStop(”mute”);
}
}

// me trying to get the rollover states of mute working again
// ****
// this was the code for the mute prior to having a volume slider
// with code that automatically turned the mute on or off and
// reset the position of the volumeknob when pressed
// ****
//mute.onRollOver = function() {
// if(so.getVolume()== 100) {
// this.gotoAndStop(”onOver”);
// }
// else {
// this.gotoAndStop(”muteOver”);
// }
//}

//mute.onRollOut = function() {
// if(so.getVolume()> 100) {
// this.gotoAndStop(”on”);
// }
// else {
// this.gotoAndStop(”mute”);
// }
//}
//
//mute.onRelease = function() {
// if(so.getVolume()== 100) {
// so.setVolume(0);
// this.gotoAndStop(”muteOver”);
// }
// else {
// so.setVolume(100);
// this.gotoAndStop(”onOver”);
// }
//}
// ****

// mute on or off ends here
// ****
// Still need to check when mute is on so that if it is and the volumeslider is moved
// the “mute” button movie clip moves to the “on” label therefore displaying
// the mute off state
// ****

Someone else recently asked me the same question, and it’s a good one. I told the other reader I would add this question to my to-do list (and I have!), but I don’t know when I’ll get the chance to write about that particular one. I’m in the middle of a new book for O’Reilly (as of Feb 2008) and have been falling behind on everything else!

I am beginner in flash, i am working on one flash video player. In that i want to run 10 flv on one same seek bar continually like one FLV. Is there any solution?

can i join the 10 flv to produce one flv as a result, if yes please help me

The SharedObject class is exactly the solution I was going to suggest! Have you made a few small tests first, just to make sure you’ve got the hang of how it works? You can use SharedObject to carry over whatever data you want, but because you’re also dealing with FLVPlayback and other ActionScript, there might simply be too much going on for you to see clearly what you’re dealing with. (I do this all the time! Then I have to remind myself to slow down, isolate the new idea in a completely new FLA [or set of FLAs] and take small steps until I understand exactly what the new code does.)

You might very well be carrying over the volume, but not retrieving it correctly from the next page — or maybe you’re not carrying it over, and the 100% winds up occurring because it’s default.

For every page that has this slider, you’re going to want to: a) use ShareObject.getLocal() to check for the existence of your “Flash cookie”; b) if a cookie exists, use the volume setting from that or an arbitrary default; and c) in addition, use the same getLocal() method whenever the slider sets the volume, then follow that with flush(), to make sure the cookie does get created and set immediately.

I have successfully implemented the volume slider on my page with your suggestions, thanks again! Works great on a single HTML page.

I’ve encountered a situation in my application where my SWF needs to be loaded into a sequence of HTML pages, and the volume slider value is getting reset to 100% with each new load. I currently have a single SWF that has an FLV component (plus the slider code), the FLV file name itself is set via a variable so the name of the file is called inside the HTML page.

I need to find a way to have the slider value carry from page to page as the SWF is loaded and show the slider in that “variable” position.

I’ve looked into using a shared object but I am unable to have it affect the volume slider. It keeps setting the volume to 100% when it’s loaded. Any suggestions, or is the shared object not the way to go?

Thanks!! Chris

I will need to carry over the current volume setting and slider position

If you’re seeing something about the on event handler, my guess is that you’ve placed your code on the buttons themselves, rather than in a timeline keyframe. The Actions panel updates its focus depending on what you’ve selected when you start typing. In pre-AS3 documents, you can select objects (buttons, movie clips, components) and add code directly to the object — in which case you don’t need instance names because Flash already knows which object(s) you mean.

Because you’re using instance names (the more modern, and Adobe-recommended, approach), you’ll need to remove that code from the buttons. See if my museum pieces article helps you out. Chin up!