These don't cause me any issue. MuLab is a DAW and the two processes activate the skins VU section.balala wrote:removing the [mProcessFoobar] and [mProcessMuLab] measures fixed the issue,
Commenting out these sections does NOT stop the error?!
I know I found that out I thought I solved it by adding a Y=7R, but as I wrote this I think I misunderstood! You mean they have the same db value, yes? I didn't twig that one! So Thanks for pointing it outbalala wrote:this section had been set to place the meters which use it, to X=(26+200*[mPeakLeft]), which means that both peak meters are placed on the same position
This seems to limit the peak value, which means it stops it going right to the end of the metre dependant on the value set in the variable. Set it to 0.5 and it only goes half way, set it to 0.3 it goes only 30% towards the right.balala wrote:Add the following two options to both the [mPeakLeft] and [mPeakRight] measures:
Code: Select all
IfCondition=(#CURRENTSECTION#>=#ResetLevel#) IfTrueAction=[!DisableMeasure "#CURRENTSECTION#"][!UpdateMeasure "#CURRENTSECTION#"][!EnableMeasure "#CURRENTSECTION#"]
This didn't work!balala wrote:with this solution if any of the maxs doesn't change for three seconds, the appropriate peak is reset.
Also add the following two measures:
At first I thought all the code was required, but Then I read the part at the end that said "Now you have to decide which solution do you prefer." So I commented out the first 'IfCondition' lines and just used the second part, which is just as you preferred!
But neither method works for me!