Hello. Another question about the read ahead and write behind code in ugen(4). It seems that if a write call comes in with a block of data, and a second write call comes in with a second block of data before the first block of data has been written to the USB device, the two blocks of data get concatinated into one USB xfer to the device. Questions:
1. Am I understanding this correct? 2. If so, is that correct behavior? It seems like most processes using the ugen(4) device would be expected to read and write well formed USB packets to and from the ugen(4) driver, meaning the ugen(4) should treat each read and write request as a discrete transaction to the USB device. By catting write requests together, it seems like it might confuse some devices, which is what I'm seeing. Thoughts? -thanks -Brian
