Default preset when using expansions.
-
@rzrsharpeprod I don't think the default preset works with expansions
-
@rzrsharpeprod That's what I was worried about.
I can do the old trick of saving and compiling with the one I want to be default loaded. This compiles fine but when you load it in DAW it looks as if it is loaded (shows as current preset on label etc) but in reality nothing is actually set so nothing plays.
I was hoping there was a way around this but it seems maybe not?
-
@rzrsharpeprod said in Default preset when using expansions.:
I can do the old trick of saving and compiling with the one I want to be default loaded. This compiles fine but when you load it in DAW it looks as if it is loaded (shows as current preset on label etc) but in reality nothing is actually set so nothing plays.
I thought this method should work
-
@d-healey That's what I thought but it just loads the expansion correctly and changes the label correctly to the preset name but it is not selected in the preset browser and therefore presumably it is not actually selecting the preset, just remembering some of the settings from when it was compiled
-
@rzrsharpeprod said in Default preset when using expansions.:
it is not selected in the preset browser
That's just a visual thing and is the same with projects that don't use expansions. I find it annoying because it's not clear to the user that the preset is loaded. Might look into fixing this at some point.
-
@d-healey That makes sense, but the preset not being loaded doesn't as nothing plays for sure and I'm not sure why?
-
@rzrsharpeprod said in Default preset when using expansions.:
but the preset not being loaded doesn't as nothing plays for sure and I'm not sure why?
All the preset does is store and restore the state of controls on the UI. So if they are showing up in the same state as when you last saved the project then the preset is loaded. So the issue is that the sample map isn't loading?
-
@rzrsharpeprod That would make sense. I'll have a look through my code as have another project where it does recall whatever preset was active when you compiled. I'll compare the 2 and see if I can find it
-
@d-healey I just did a test build with the expansion and samplemap comboboxes visible so I could see if they loaded empty.
Both comboboxes are populated in DAW so now I'm even more confused as what you said made sense but looks like it isn't the case. -
@rzrsharpeprod Does it work in a non-expansion project?
-
@d-healey I figured out what it was - there was a line of code clashing with another and it was unloading the expansion when it went back to the grid.
Tested it and it worked...happy days or so I thought.My colleague has just confirmed that it isn't working on Mac though even though I took the offending line of code out.
In fact none of the mac builds ever have a preloaded sound whether they are expansions or straight presets. I have never been able to figure it out so the above is hardly a surprise really.Have you got any idea why the mac version would act differently to the windows version in daw
when it is the same code? -
@rzrsharpeprod I don't know what could cause that.
I would make a new project for testing. Make it as simple as possible.
Start with just a sample map preloaded, export and test on both OS.
Then build on it. Add a combo box to select between two sample maps, test.
Then add presets that use the combo box, test.
The add expansions
etc.
etc. -
@d-healey so there's nothing that you know of that would cause it to happen on Mac when it works fine on windows?
It's the exact same code for both versions and has happened on every project ever regardless of whether it used expansions or just regular presets.
It looks like it loads the preset and samplemaps but no sound plays on Mac but it does on the windows version.
There's no extra setting or process that needs to be turned on/off on Mac or anything?
It seems odd that it's every project but I know little about macs TBF, they're a mystery to me. I only have it to build the Mac version, everything is built on windows
-
@rzrsharpeprod said in Default preset when using expansions.:
so there's nothing that you know of that would cause it to happen on Mac when it works fine on windows?
The only thing I can think of is the Global App Data folder setting in project preferences which sometimes causes strange issues.
-
@d-healey I'll have a look at that thankyou. I may have set it/not set it correctly from one OS to another maybe
