EOS - How to keep score

[boundupone]

Hi guys,

Am thinking about a future estim tease using EOS, and I am wondering how I would go about keeping score, and varying the estim volume on the basis of your performance.

For example you have to answer questions, and if you get the right you are rewarded, but if you get them wrong you are punished. So the more incorrect ones the stronger the estim gets (higher volume) and the nastier the file used

I have no clue how to implement this, and if it is too complex I will shelve the plans for now

Cheers

[Batman314]

I think you will have to use the Eos api to script your audio since you cannot assign volume from a variable using the basic Audio: Play action. So maybe something like this: Sound.get('example').setVolume(estimAmp).

But I would scale the score to decibels rather than linear amplitude since that's how we perceive volume changes. The script would look something like this:

/*this is in decibels, a 2 or 3 dB difference seems to be a large difference for estim, so I would increase/decrease by 0.25 or 0.5 at a time, making sure it does not go higher than 0. dB*/
var estimScore = -5.

/*this converts decibels to amplitude. The max decibel level is 0. dB, which gives an amplitude of 1.*/
var estimAmp = Math.pow(10., (estimScore / 20.))

You can test how estim levels feel with different decibel changes using my Estim Control App: viewtopic.php?f=26&t=22365

-Batman

[undeniable_denial]

What Batman says.

Also, to switch to a "nastier" sound file:

Code: Select all

Sound.get("nasty").pause();
Sound.get("nastier").play();

That is assuming you have prior play actions for both of them. You may want to immediately pause them right away, so they're not playing at the same time and, yet, have them ready to be played by code logic.

Technically you could do this with just if- and play-actions, but it would be a bit rough, I imagine. However, as Batman explained you need to code the volume changes anyway, therefore it will be cleaner and less interuptive if you do it entirely by code. I'm sure there are more than enough nerds around to help you out with that.

[lolol2]

Am thinking about a future estim tease using EOS, and I am wondering how I would go about keeping score, and varying the estim volume on the basis of your performance.

Also thought about this kind of feature.
The problem is like always the varity of devices out there, everyone will have different results.

So I had the idea to let the user decide the range of volume increase.
I would create the stim files all with the same volume level and set the actually volume with EOS.

So for example you select "normal" range, so the volume would start with a value of 80% and every increase would add +1% to the volume, so you have the chance to create 20x a little increase.

If you select a "large" range you could start with 60% and add +2% with every increase, so you will get more volume increase and don't have to change your script.

Simple example:

Define variables at the start which can be set by user selection/input.
volstart = 60;
volincrease = 2;
volume = volstart;

In the tease start the audio with using the "volume" variable and if you want an increase just raise the variable like:
volume = volume + volincrease;

So you can change the range just with change two variables at the start and the user can decide, always the best to get everyone happy.

If your tease is very long and the range is not enough you can also build a little if/else script to trigger a recalibrate when you reach 100% volume, because you can't exceed this value 100/100.
Like "Let us recalibrate the device", then you set the volume back to the volstart for example and tell the user to increase the device volume that it feels like before. Then you can make again 20x increases.

Of course you can have different volume values for normal or pain files. ;)
Just my simple solution which will maybe implemented in my next tease.

[Tedlington9099]

Of course you can have different volume values for normal or pain files. ;)
Just my simple solution which will maybe implemented in my next tease.

WOW ... Please ... Please ... Please ... Try and do this lolol2 ...

This will potentially solve most of the problems of device variations and allow users to
fine tune to their own likes and tolerances.

I have a 2B and a 3rdH box and the output from the same file can be vastly different ...

As you are so free and generous in sharing your fantastic work another possibility would
be to allow downloads for offline use ... then users could tune or alter sound files to suit
their own tastes.

If there were such a thing as "Tease Personality of the Year" you would win hands down ...

[boundupone]

Am thinking about a future estim tease using EOS, and I am wondering how I would go about keeping score, and varying the estim volume on the basis of your performance.

Also thought about this kind of feature.
The problem is like always the varity of devices out there, everyone will have different results.

So I had the idea to let the user decide the range of volume increase.
I would create the stim files all with the same volume level and set the actually volume with EOS.

So for example you select "normal" range, so the volume would start with a value of 80% and every increase would add +1% to the volume, so you have the chance to create 20x a little increase.

If you select a "large" range you could start with 60% and add +2% with every increase, so you will get more volume increase and don't have to change your script.

Simple example:

Define variables at the start which can be set by user selection/input.
volstart = 60;
volincrease = 2;
volume = volstart;

In the tease start the audio with using the "volume" variable and if you want an increase just raise the variable like:
volume = volume + volincrease;

So you can change the range just with change two variables at the start and the user can decide, always the best to get everyone happy.

If your tease is very long and the range is not enough you can also build a little if/else script to trigger a recalibrate when you reach 100% volume, because you can't exceed this value 100/100.
Like "Let us recalibrate the device", then you set the volume back to the volstart for example and tell the user to increase the device volume that it feels like before. Then you can make again 20x increases.

Of course you can have different volume values for normal or pain files. ;)
Just my simple solution which will maybe implemented in my next tease.

Interesting, I had not thought of that. I havent started anything yet and the replies here are pretty technical (well, for me anyway :) ) so I may not have time to do something this complex. But thanks again