ir widget time mode save inconsistency: nothing to save

[rct]

I know the timing modes are deprecated, but I'm posting this as a minor FYI for anyone who might come across this:

After capturing a signal in IR Widget Time mode, IRScope won't allow the signal to be manually saved, an error pop-up says "Nothing to save".

However, if auto save of .ict files is enabled, it will save the recorded signal. IRScope is able to read back the auto-saved .ict file. So this is a work around.

Alternate very kludgy workaround: IRScope will allow saving of a signal imported by entering a timing list, so copying the timing list from the summary window into import will work (after you've made a guess, or entered 0 for carrier).

Again, I'm not expecting a fix or response for this given that count mode should be used.

[vickyg2003]

I know the timing modes are deprecated, but I'm posting this as a minor FYI for anyone who might come across this:

After capturing a signal in IR Widget Time mode, IRScope won't allow the signal to be manually saved, an error pop-up says "Nothing to save".

Actually you can save the signal by just highlighting it in the decode window.

However, its a lot more convenient to make a whole set of signals describing each one with a note, and then saving the whole big thing as one large ICT file. This way you can pass the whole thing.

In addition, Graham made a special feature for me. On the Advanced menu, there is a common folder. If you are doing a lot of projects this will allow you to set each device you are learning into its own folder, and all the exports and summaries will be found there too.

Graham said that no two people use IRScope in the same way.

[rct]

Actually you can save the signal by just highlighting it in the decode window.

Thanks for your reply. Sorry if I cause any confusion, I was pointing out a bug related to the rarely used IR widget time mode. It all works as expected in IR Widget Count mode, the default.

[vickyg2003]

Actually you can save the signal by just highlighting it in the decode window.

Thanks for your reply. Sorry if I cause any confusion, I was pointing out a bug related to the rarely used IR widget time mode. It all works as expected in IR Widget Count mode, the default.

Whoops. I didn't get that. What do you use time mode for?

[rct]

I know the timing modes are deprecated, but I'm posting this as a minor FYI for anyone who might come across this

Sorry I meant to mention I only tested this with IRScope 2.01.

[rct]

Whoops. I didn't get that. What do you use time mode for?

In general I think JP1 people are only (and probably should only be) using Count mode.

Time mode is from older (and probably home made widgets). It uses an IR demodulator which can pick up signals over longer distances, but can't figure out the carrier frequency used since it only reports the edges of the on signal, not the count of pulses.

IR demodulators introduce some amount of error in the signal timing since they have to wait some period of no pulses before reporting the falling edge indicating the transition to the off time. So the result is on times wind up being reported longer than they really are and the following off interval is as a result shorter than it actually is. Consumer electronics that receives IR signals generally use IR demodulators.

For precise decoding of IR signals, Count Mode is the clearly better choice.