0.9724 overrides per instance/hidden preferences

[seb@plogue]

I've added a way to override some preferences per instance (i.e. a given copy of the .exe/.app for Bidule).

OS X:
This is done through the Info.plist file that is located inside the application bundle, you will need to add keys of a specific
type.

Windows:
This is done through a .ini file having the same name of the .exe and in the same directory, the expected format
is (one per line)
KEYNAME=VALUE

Keys:

ReWireModeCheck (as an integer or boolean on OS X, an integer on Windows)
The default is 1/true, if this is set to 0 this will never check if it's running under ReWire, usually
useful for people wishing to have one instance running in ReWire mode and other instances as standalone

SampleRate (as an integer)
BufferSize (as an integer)
FFTSize (as an integer)
FFTOverlap (as an integer)
Using these you can have an instance running at different DSP settings than the one stored in the preferences

OSCServerPort (as an integer)
Each instance can use a different port for incoming OSC messages

DefaultLayout (as a string)
The absolute path to the default layout used by this instance

CreateVirtualMIDIPorts (OS X only, as a boolean)
Create virtual MIDI ports or not per instance

VirtualMIDIPortName (OS X only, as a string)
Prefix that will be used to name the virtual MIDI ports for this instance

Some older hidden options:

Plugin mode : added possibility to have a different window size through config

OS X:

open a Terminal window:
defaults write com.plogue.bidule MainWindow.pluginModeWidth -int <desired width>
defaults write com.plogue.bidule MainWindow.pluginModeHeight -int <desired height>to remove values:
defaults delete com.plogue.bidule MainWindow.pluginModeWidth
defaults delete com.plogue.bidule MainWindow.pluginModeHeight

Windows :

under HKEY_CURRENT_USER\Software\PlogueBidule
add DWORD values named MainWindow.pluginModeHeight and MainWindow.pluginModeWidth
set to desired values
remove values to get back to default (or set to 800x600)


Presets : added possibility to change scaling
(to have the more natural integer scaling as seen with Variable Int)

OS X:

open a Terminal window:
(to enable)
defaults write com.plogue.bidule Parameter.presetUsesIntegerScaling -int 1(to disable)
defaults write com.plogue.bidule Parameter.presetUsesIntegerScaling -int 0


Windows :

under HKEY_CURRENT_USER\Software\PlogueBidule
add a DWORD value named Parameter.presetUsesIntegerScaling
set to 1 to have presets behave with integer scaling
set to 0 for default behaviour



Step Sequencer : added possibility to turn off cursor

OS X:

open a Terminal window:
(to disable cursor)
defaults write com.plogue.bidule StepSequencer.showCursor -int 0
(to enable cursor)
defaults write com.plogue.bidule StepSequencer.showCursor -int 1


Windows :

under HKEY_CURRENT_USER\Software\PlogueBidule
add a DWORD value named StepSequencer.showCursor
set to 0 to not see the step sequencer cursor
set to 1 for default behaviour

[new in 0.9724]
Switch mutation behaviour to use the parameter range instead of the current value
int (on OS X), DWORD on Windows
Parameter.useMutateOverRange
1 to enable, 0 to to get default/old behaviour

[reezekeys]

I'm having trouble making this work, appreciate any help...

I opened the .plist file from the app bundle in an editor called "PlistEdit Pro" (OSX). This is what I saw:



I clicked on "New Child", then added the line which is highlighted:



I then saved the .plist back into the app bundle. When I run PLB the sample rate remains 44.1K, which is what it was set at previously. I see this previous value in the com.plogue.bidule.plist file in ~/Library/Preferences. What's interesting is that, in that file it's called "DSP.sampleRate", not "SampleRate."

[seb@plogue]

Did you add the "," by yourself or did PlistEdit Pro did that? Have you tried 96000 directly?
You should also check the bidule.log file, IIRC if the an override key is found it's written in there although I'm not sure the read value is automatically logged or not...

[seb@plogue]

Using the built-in plist editor from the dev tools:

If I type 96000, this is what I get in the bidule.log:

I:0x 2:2894746304:4522223734:instance override sample rate : 96000
I:0x 2:2894746304:4522223857:DSPInfo ctor
I:0x 2:2894746304:4522223866:Using SampleRate: 96000
I:0x 2:2894746304:4522223879:Using BufferSize: 256
I:0x 2:2894746304:4522223885:Using FFTSize: 512
I:0x 2:2894746304:4522223891:Using FFTOverlap: 2

If I attempt to type 96,000 this automatically become 96 (that could be because of my Formats settings)
and in the bidule.log:

I:0x 2:2894746304:4640229658:instance override sample rate : 96
I:0x 2:2894746304:4640229758:DSPInfo ctor
I:0x 2:2894746304:4640229767:Using SampleRate: 44100
I:0x 2:2894746304:4640229779:Using BufferSize: 256
I:0x 2:2894746304:4640229786:Using FFTSize: 512
I:0x 2:2894746304:4640229792:Using FFTOverlap: 2

[reezekeys]

Did you add the "," by yourself or did PlistEdit Pro did that? Have you tried 96000 directly?

I typed 96000, PlistEdit Pro added the comma. Not sure what you mean by trying 96000 "directly."

I'll check the log files when I get my computer back from my 11-yr-old daughter.

It makes no sense that the program would actually put the comma in there, except for display purposes.

[reezekeys]

Now I'm thinking this should be in "Bugs & Problems" but I don't want to break the thread continuity.

The log file says I'm at 96K, but Bidule is still running at 44.1.

I:0x 102:2687816960:54783806992:instance override sample rate : 96000
I:0x 102:2687816960:54783807096:DSPInfo ctor
I:0x 102:2687816960:54783807111:Using SampleRate: 96000
I:0x 102:2687816960:54783807130:Using BufferSize: 128
I:0x 102:2687816960:54783807140:Using FFTSize: 512
I:0x 102:2687816960:54783807149:Using FFTOverlap: 2



OSX 10.6.4 on a MacBook Pro

[seb@plogue]

No that is working as expected, the values in preferences are the one saved in the .plist file in ~/Library/Preferences, the point of the override values is to bypass them, not change them. If you add a Constant in your layout and set it to Sample Rate you will see 96k.

[reezekeys]

OK, now I get it!!

I would feel free to delete all the messages in this thread, below your initial one