Okay, here's what I'm trying to do. I'd like to record a radio show every Saturday morning when I'm gone on my MD recorder and at five minute intervals, place an index/track mark by having the remote hit "Record" every five minutes (so if I have to stop and restart playback, I'm not left with one looooooong track to FF though.

Everything works fine (power on, source, record, power off), except for the repetitive record bit.

I've noticed that you are able to place more than one Timer function for each timer, but I don't think that the Pronto will execute any more than two. For instance, on one button, I have a timer function that turns everything on, and then 11 timer functions, spaced at 5 minutes apart, and then one to shut it all down. The Pronto will turn everything on and begin recording, enter another track number five minutes later, and then... nothing. Can the Pronto handle only two timer functions per timer?

I know that there are not-too-elegant work arounds - like a separate timer button for each of the 11 track marks and even making huge delays (which would make the remote useless during that hour if I or someone else is home during that time). It just seems to me that I'm doing something wrong.

Anyone have any suggestions?

Oh, and while I'm on the topic of timers, I noticed that there is a "weekly" checkbox. If I set the timer for "Saturday," doesn't that already imply that it's weekly? Why would I need to check the weekly box?

Thanks!
Merrill

weekly = repeat action every week. if it is not checked the timer will run only once and then it will cancel itself .

Thanks, Anthony. One down, one to go.

Anybody?

You are right with your choices:

- a separate timer event for each action

- one very long executing macro

What is wrong with the 11 multiple timers? You have 11 separate events. That is what timers are for.

Peter, it's just the long way around the problem. ProntoEdit allows you to assign multiple timer actions to the same timer button, each with its own start time.. but it only executes two from the list. I will assume that this is a bug because 1) if this is the case, then the program should not allow you to enter more than two actions, or 2) seeing that it allows you to enter more than two actions, it should execute them all.

I am now a bit confused. What do you mean by "more than 2 actions".

A timer can have 2 events - a start event and a stop event. Each of these has a different time. These can be totally unrelated and thus 2 are unnecessary. Philips has provided this as a convenience as you might want to have one event to start a VCR and another to stop it later on.

Merrill do you mean timers in the action list of a button? If someone is using the Pronto won't that interfere with the timers, especially since it has something to do every 5 min.?

Anthony, what I'm trying to say is this:
When you double click on a timer button in ProntoEdit, at the far bottom of the left side, you have a "Timer" button that will allow you to asign a start and stop timer action to that button's action list. ProntoEdit will, however, all you to hit that timer action button multiple times so you have multiple "[T] TimerAction"'s assigned to the button's action list. If the pronto can only execute two actions per button, why would the program allow you to assign multiple TimerActions? I've had as many as twelve in there (though only two worked). The program shouldn't allow you to save that many TimerActions to the button.

As for the timed function interfering with someone doing something at that time, I suppose it would, but 99% of the time, no one will be home.

Timers aren't actually part of an action list. They're just stored there. As long as a timer has enough data -- time, days and what to do -- it's active. It doesn't matter what button its on, or how many are on a button. However, if you want to be able to edit a timer on the remote it must be stored on the Macro side and be the only action for that button, elsewise the Pronto will treat that button as a macro when editing.