twilo123
Active Member
i am interested in feedback for one of the options we are working on in the remote edition app. on the 3rd item we are doing punch through - punch to however right now we strictly map it to the same button from another existing device. i am wondering if we should allow for re-mapping of the button to another button on the 2nd device also in case people want to do this and am looking for use case examples. at this point the GUI is hard defined based on about 11 pre-defined device types (tv, cable box, satellite receiver, video accessory, vcr/dvr, laser disc, dvd, a/v receiver, audio amplifier, cd, home control). we will eventually have a method for remote skinning of icons so you can input your own set. we are also exploring the idea of allowing people to move buttons around on the screen itself like a drag/drop method. so i think if we do those functions people will want to start mapping buttons independent of what the button originally is when you add a device in at first. any thoughts or examples relating to this?
Total Control Remote Edition New Features Video Link
0:00 – 0:25 = auto start into GUI option. Here you can choose to start right into a gui of a device so after this is done you can basically just start the app and have it start right into a gui of a device all the time if you want. Great for small setups where you always use the same device only or initially.
0:25-0:50 = macro example. name the macro whatever you want and call it from the bitwise unit. the macro is stored directly on the bitwise unit. why do this? 1. instant macro support. the macro is called directly on the unit itself. no need to process it on the app side or send multiple commands, etc. 2. less chance of interference with macro. by doing it this way we just send a single quick command to the bitwise unit. if we had long commands coming from the app then there could be issues with latency, wifi connections, processing commands in order on unit if they receive them out of order, etc. it becomes more efficient this way.
0:51-end = punch through example – map any existing device button to another existing device button. example: you use your cable tv GUI all the time but when you click volume up/down you really want to control the tv or a/v receiver volume buttons without having to go to that device for control. now you will be able to easily select one button and map it to that button from another device.
Total Control Remote Edition New Features Video Link
0:00 – 0:25 = auto start into GUI option. Here you can choose to start right into a gui of a device so after this is done you can basically just start the app and have it start right into a gui of a device all the time if you want. Great for small setups where you always use the same device only or initially.
0:25-0:50 = macro example. name the macro whatever you want and call it from the bitwise unit. the macro is stored directly on the bitwise unit. why do this? 1. instant macro support. the macro is called directly on the unit itself. no need to process it on the app side or send multiple commands, etc. 2. less chance of interference with macro. by doing it this way we just send a single quick command to the bitwise unit. if we had long commands coming from the app then there could be issues with latency, wifi connections, processing commands in order on unit if they receive them out of order, etc. it becomes more efficient this way.
0:51-end = punch through example – map any existing device button to another existing device button. example: you use your cable tv GUI all the time but when you click volume up/down you really want to control the tv or a/v receiver volume buttons without having to go to that device for control. now you will be able to easily select one button and map it to that button from another device.
