nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Aug 22, 2018 15:47:37 GMT
Hi drkeys, Feel free to email me your scene file and happy to take a look. Regards, Nic
|
|
|
Post by drkeys on Aug 31, 2018 9:42:50 GMT
Hi Nic, I created some simple scenes to test this. Scene-Metro basic 02.mfr (1.97 KB) Scene-Metro basic 01.mfr (1.97 KB) If I load either one of these scenes, then close MidiFire and restart it, I can start and stop the clock, see clock tick messages, and hear clicks from MidiMetro. However, if I then either reload the same scene or load the other scene the clock stops working. I took a similar approach to checking the Keep Alive routine, and I believe that's working ok. (I was initially confused by the fact that loading a scene to start the active sense messages stops the clock from working.) Regards, Dave.
|
|
|
Post by drkeys on Aug 31, 2018 11:58:42 GMT
Hi Nic,
It seems it's not so simple. The above test was done with only MidiFire and MidiMetro running. The iPad was powered direct by a DC supply.
Since then I connected a keyboard via my PreSonus AudioBox iTwo, and opened various sound apps, iRig BlueBoard and Midi Designer (Pro 2). Then the clock seemed to be controlling MidiMetro and continuing to do so through multiple scene changes.
Eventually I went back to the two scenes I send with the previous post. Metro could be started from the Dynamic clock block. I could hear clicks but there were no messages of any kind in event monitor. I then closed apps one by one, but clock kept working despite scene changes.
Two other things I noticed:
1. Active sense messages from Keep Alive also stopped appearing event monitor. (I can't tell whether they were actually being generated.)
2. Clock seemed to revert to the last tempo it received from Midi Designer on about the 4th click after being started. this happened even after MD was shut down.
Finally, I disconnected the lightning connector to isolate the AudioBox and keyboard (which sends active sense). This didn't change anything either. Clicks still started and stopped.
Closing MF and restarting it caused behaviour to revert to the situation I described in the previous post.
Regards, Dave.
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Sept 5, 2018 11:01:24 GMT
Hi drkeys, Sorry for the delay in getting to look at this. I have been swamped this week with something. I will try and investigate as soon as I am out of the woods. Regards, Nic.
|
|
|
Post by drkeys on Sept 5, 2018 15:21:54 GMT
No problem. No rush on this. I'm swamped myself with preparations for our annual student concert. With great regret I decided to go back to MidiBridge for this, but I'll be working with MidiFire again when it's all over (17thSep). Dave.
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Sept 12, 2018 10:47:46 GMT
Hi drkeys , OK, I had a play with this today, and you're right, there is a problem with reconnecting the clock to its destinations on scene load. This is going to be a problem for Metro since it won't listen to MidiFire's clock signal directly, which could have made a quick workaround. I can't think of any other way of working around this without me actually fixing it. It's on my list of bugs to fix in MidiFire for next release. Sorry about that. Regards, Nic.
|
|