Bazille MIDI learn bug?

[AusDisciple]

I originally made a post in the Bazille public beta thread about a possible Bazille MIDI learn bug but it no doubt got lost amidst the fast paced discussion there so I figured it would probably be best to post the report here in its own topic.
Here's a copy of what I posted:

27th May, 2014
Last night, I was working on a new tune and had set Bazille filter cutoff controls to midi learn the 2nd modulation wheel on my SY77 which is controller no. 13 and it worked as expected. However, after I had saved the project (using REAPER 4.62 on Win8) and later reopened it, Bazille did not respond to the midi controller 13 data sent from the REAPER track. I had to reconnect my SY77 and do the midi learn process again. After that Bazille once again responded to the midi data sent from the REAPER track.

I thought perhaps the lock function on the cutoff knobs might 'lock' the midi learn state into those controls (I probably should read the manual to see what that really does) but that made no difference. Once I closed the REAPER project and reopened it, I had to go through the midi learn process again to get it to respond to the REAPER midi data. Even saving the patch after doing the midi learn process didn't help.

It seems Bazille is not remembering midi learn.

I forgot to mention this is with version 2370. I haven't tried with the previous beta.

[#rob]

Does Bazille forget *every* MIDI assignment?

Try this:

Open an instance of Bazille, go through the MIDI assignments again, close the Bazille GUI first and then quit your host software.

Wherever you installed the VST2 plugin, there should also be a folder called Bazille.data.
Inside the Bazille.data folder, look for this file:
\Bazille.data\Support\com.u-he.Bazille.midiassign.txt

If it's there - what's the latest modification date?
Is it dated to roughly when you did the MIDI assingment(s)?
Please send it to us!

If the file's not there - you're probably a victim of Windows' restrictive file access permissions.
Go to our website's FAQ section, click on the Installation, Locations & Permissions category and open the first item in the list: "How do I solve File Permission issues on Windows?"
The step-by-step instructions there should help you sort out the permission issues, should they have been the culprit.

[AusDisciple]

Thanks heaps for the quick reply Rob. I'll give those things a shot after I post here and will report back.
Loving Bazille and Diva so far and have plans to purchase Ace and Zebra at some stage soon too. Great work guys.
I'll have some photo's of some of my analog gear to send you to add to the Zebra gallery too (Roland System 700 Sequencer and complete System 100 synth are two I don't see in your gallery yet).

[AusDisciple]

Hmmm... This is rather odd. It all seems to be working now and I haven't changed anything!
The Bazille dll file is located with my other VST plugins in C:\Program Files (x86)\Steinberg\VstPlugins
The MIDI assignment data file is in C:\VstPlugins\u-he\Bazille.data\Support and it is being written to and contains the MIDI assignment data. In this case, the file contains:

// Global MidiCC Map


15:3=Filt1:Cutoff, normal, 0, Continuous7bit, Yes //Filter1:Cutoff
15:3=Filt2:Cutoff, normal, 0, Continuous7bit, Yes //Filter2:Cutoff
15:3=Filt3:Cutoff, normal, 0, Continuous7bit, Yes //Filter3:Cutoff
15:3=Filt4:Cutoff, normal, 0, Continuous7bit, Yes //Filter4:Cutoff


I have no idea why it wasn't working the other day but when I first loaded Bazille today it wasn't recalling the previous MIDI assignments and the file had none of the four lines relating to the four filters I had assigned to the second mod wheel. I then opened REAPER, added a new instance of Bazille, redid the MIDI assignments, saved the patch, saved the REAPER project and the file was as above. Upon reboot, everything works as expected.
Perhaps there was some weird OS permissions thing going on and temporarily preventing writing to that folder the other day. Whatever happened then, it is all working for now. I will report back if anything changes.

[#rob]

Are you by any chance using 3rd party software (Automap etc.) that might be interfering with MIDI messages -- or that might not when the application isn't running?

Do you have Antivirus software with a "live" file check activated?
AV scanners are known causers of temporarily locked files.

[AusDisciple]

Thanks for getting back to me again Rob.

I do have LoopBe30 installed but I only use it when I'm patching internally between apps on this DAW.
The MIDI setup I am using for Bazille is SY77 -> RME Fireface UFX -> REAPER -> Bazille.
As far as anti-virus goes on this PC, I am only running Windows 8 stock Defender. I generally don't browse dodgy sites, I don't run cracks and I have regular backups in the rare event that a virus may get through. Win Defender has actually been surprisingly good so far.

Whatever happened the other day I am not sure but things are still OK today. Perhaps it was something I hadn't assigned properly in the REAPER MIDI devices page. I think I was running the SY77 into my MOTU MIDI Timepiece on the other project and yesterday I had it running into the RME.

Either way, it is all good for the time being and I'll report back if anything goes amiss again.

I very much appreciate the support though. Thanks again Rob.