
On 11 Sep 2004, at 00:26, Ben Kennedy wrote:
This contains a minor change which I am hoping MIGHT be related to the MIDI/non-audio issue.
Woah! I think you did it! This is way cool. I ran 3 (well, 3-and-a-half) tests, and all were very successful. I hooked it all up and pressed play on DB, and DB started the deck recording, with strong audio output from the get-go. Very strong! I had to dial back the output volume to avoid peaking on my deck :) So then I stopped it (I think I tried to stop it by stopping DB first, and I think I remember this didn't work, but this is not a big deal at present) and DB, and then just for the heck of it I pressed play on DB and it successfully zeroed the record track before restarting it (with audio all good). It did seem to stagger a bit when doing so, but basically worked. Still, I manually stopped the deck and DB again, manually zeroed the deck and (with levels OK now), pressed play for a proper "drum take". It ran fine all the way through and stopped neatly at the end. I ran the same test again twice more, noting the final stopping times, and got very close results. The VS-1680 (and probably other Roland devices) counts in an SMPTE kind of way, in hours, minutes, frames (1/30 sec), and sub-frames (1/100 frame). In my three tests, the particular dbsong was clocked in by the DB UI at 5.55 (with a little "ring" after the last "hit"). In the three tests, my deck stopped at: 5m56s27f31sf 5m56s29f10sf 5m56s28f81sf That suggests, perhaps, that the MIDI output from my iBook may be a little flaky (and hey, it's going through a USB<>MIDI adapter). Given that only lag at the beginning of the piece matters much, I'm not sure how noticeable it will be. But I look forward to finding out! IMO, this is pretty excellently cool. I plan to slap some guitar and bass on my new drum part and then go back to try swaping out the drum part using the MMC start feature and see how it sounds (though not tonight .... :)
Re the midi issue, one other thing that you might check is to ensure that in prefs, the input device is set to "none" (since presumably you are not using your deck to start doggiebox, or are you?)
No, but theoretically I could, if it were possible to set DB as the slave. I'm not sure whether or not there would be a good reason to do this. In any event, I admit I didn't check the input device setting this time; I just plugged it in to see if it worked, and basically it did. So: cool :) Cheers, Carl -- Carl Edlund Anderson http://www.carlaz.com/