Thread: RRFusion- My Fusion Brain plugin for RR

Dude... you really, I mean REALLY need to stop smoking that S#IT!!!!!

Originally Posted by JohnWPB

Dude... you really, I mean REALLY need to stop smoking that S#IT!!!!!

Originally Posted by JohnWPB

Yea, that is in Sonic's source code, which I do not have. I see there is a way to alter analog correction values, but that's for something I have no idea what it is

From the RRFB.ini

"Analog correction values pertain to the static voltage divder types only"

i can add correction values for temp sensors too. Thats no problem.

That would be fantastic! It would give a quick fix to tweak the temp values a bit. With it matched up to another digital thermometer, And "tuned" for each individual sensor, I bet one could get better than the +/- 1.5 degrees. Heck, I would be happy to be within just a couple degrees actually, 15 degrees of makes it almost pointless to use.

BTW, if ya wanna check out the plugin I wrote for the FB you are welcome to, just drop me a PM. Still needs a little polishing up, but it is working well. I used the labels you made available with your RRFusion Plugin

One other nice feature would be to be able to have event driven fired events for the analog ports. This would only require minimal code additions

/,Analog# = <TYPE(RAW or OPT)>;<LIMIT>;<OPERATOR(< or > or <>)>;<ALERT>

Add a "<>" to the operator options, which would then fire the <ALERT> as the event if that ports value changes by more than the +/-<LIMIT>.

Make sense, I hope? This would be nice in the instance of say Johns Plugin where it wouldn't have to constantly check if the value changed, becuse it would fire off an even saying it did, which then another PI/app could act upon it, saving wasted resources for something that might have not changed or changed by a little bit 2-3 values...

The more flexible this is the more one can use it for with minimal extra coding and resources.

I just wanted to say I think it is funny how the development of this plugin pretty much mirrors that of MDX.

Every feature on here was requested before and I implemented it almost in the same order. I wouldnt be surprised if you made a function parser soon so that instead of static offsets, the entire equation could be customized. And if you do I already have the code for that, so I can give it to you!

Keep up the good work, it just makes me giggle a bit that is so closely related!

Well 2k, we DID try to get you to make or spear-head a RR plugin in the first place I have to say, that the integrated plugin is a much better option.

I know you spend countless hours on MDX, and it is a fantastic piece of software! But, just having all the commands native to RR, with no need for another program to be running, and have all of the commands native to RR is just the better option. Plus not having to skin to seperate programs, and being able to use RR"s native skins with transparencies, intermixed labels ect. I can put a temp label in the main menu, lighting control switch on the audio screen, RR indicators mixed with the FB indicators on a control screen ect ect.

Using the labels and var's that sonic exposed, I wrote that lil plugin mentioned above for automatic dimming, or manual overide by using the Potentiometer. I am sure there will be many more cool plugins to come now that all the readings have been exposed to RR natively.

Originally Posted by Blue ZX3

One other nice feature would be to be able to have event driven fired events for the analog ports. This would only require minimal code additions

/,Analog# = <TYPE(RAW or OPT)>;<LIMIT>;<OPERATOR(< or > or <>)>;<ALERT>

Add a "<>" to the operator options, which would then fire the <ALERT> as the event if that ports value changes by more than the +/-<LIMIT>.

Make sense, I hope? This would be nice in the instance of say Johns Plugin where it wouldn't have to constantly check if the value changed, becuse it would fire off an even saying it did, which then another PI/app could act upon it, saving wasted resources for something that might have not changed or changed by a little bit 2-3 values...

The more flexible this is the more one can use it for with minimal extra coding and resources.

Could be the loratab i'm on... could be because i havent looked at the stuff you just helped me add.. but isnt that what you helped me with? lol Explain the difference.

Originally Posted by 2k1Toaster

I just wanted to say I think it is funny how the development of this plugin pretty much mirrors that of MDX.

Every feature on here was requested before and I implemented it almost in the same order. I wouldnt be surprised if you made a function parser soon so that instead of static offsets, the entire equation could be customized. And if you do I already have the code for that, so I can give it to you!

Keep up the good work, it just makes me giggle a bit that is so closely related!

Thats already been requested and considered.. i just had the slightest idea how to implement it. I will certainly look at your code once i get back into RRFusion development. For now i'm trying to get movietimes back up and running.

Originally Posted by JohnWPB

Well 2k, we DID try to get you to make or spear-head a RR plugin in the first place I have to say, that the integrated plugin is a much better option.

There is a RR plugin already available as well just FYI.