4.0.5 Channel changing

[mattyb]

Just upgraded to 4.0.5 and now my channel changing isn't working with IR Server Suite. It's been solid for years. Have tested it with the IRSS software and it's blasting correctly.

Any ideas? Logs attached. I've just tried changing to channels 53 and 52 respectively, both channels which should call the IRSS channel change.

[sub]

I cant see any blaster listed there. If you go to Settings->Devices, then double click the Colossus 2, do you see the blaster executable etc listed next to each channel? If not, enter the blaster details at the top of the screen, select the channels, right click 'update to current' to get them to pick up the blaster settings.

My guess is you accidentally erased the blaster settings by doing something.

[mattyb]

There's some odd behaviour going on here. I didn't do anything to erase the settings, haven't been in there in a while. Now when I'm in the device screen for the Colossus 2, the executable and arguments are there, but when I click on any of the channels they both disappear. I can select all the channels and add them back in, but that doesn't work either. Once I OK out and back again they're gone again. Does that make sense? In any case, the exec/args don't seem to 'stick'. Any thoughts?

[sub]

I've attached a screenshot to show you what a channels with blaster settings look like.

If you click on a channel in the list, it's normal for the "executable" and "arguments" fields to change to show you what is stored with that channel. So...if it's going blank, it's just telling you there is no blaster set for that channel.

To fix, select all the channels in the list, then select "Executable" in the "Changer" dropdown, then select your executable and args, then right click on those selected channels, and choose "update to current'. You should now see the executable listed next to each channel.

[mattyb]

I've attached a screenshot to show you what a channels with blaster settings look like.

If you click on a channel in the list, it's normal for the "executable" and "arguments" fields to change to show you what is stored with that channel. So...if it's going blank, it's just telling you there is no blaster set for that channel.

To fix, select all the channels in the list, then select "Executable" in the "Changer" dropdown, then select your executable and args, then right click on those selected channels, and choose "update to current'. You should now see the executable listed next to each channel.

Fixed - many thanks. Not sure how it ended up like that - all good now though.

[pBS]

other users have reported config.xml alterations with latest win10 update..