Sean M. Pappalardo wrote:
> Albert Santoni wrote:
>> 1) Was that aseqdump log captured from the output of Mixxx or the
>> input to the SCS.3d device?
> 
> I just tried aseqdump on the SCS.3d port and it only shows what the
> SCS.3d is sending, not receiving. So I'm quite sure the aseqdump on the
> Mixxx port shows what Mixxx is sending, not what the SCS.3d is receiving.
> 
> I wonder if I should try to pipe the device through JACK's MIDI and see
> what happens.
> 
>> I wonder if the USB-MIDI kernel module is intentionally
>> limited to sending at the MIDI baudrate.
> 
> Even if that's the case, data shouldn't be *lost,* just delayed.

That depends on the buffer sizes used.

Essentially MIDI is fundamentally limited in baud rate and one could 
wonder whether it's a good idea to delay messages for a long time. Same 
remark holds for just dropping them of course.

I don't know about how the USB-midi driver/spec handles this, I only 
know that the spec for MIDI transport over firewire using AMDTP 
explicitly mandates that you don't send faster than the wire rate.

I should note that the FFADO code for the SCS.1 devices does not have 
this limitation as it doesn't use AMDTP encapsulation. The HSS1394 
protocol that stanton developed doesn't have any speed limitation. The 
FFADO aseq-HSS1394 bridge basically acts like aseqdump, so it should be 
interesting to see whether all data arrives there.

If you run the test-scs bridge with the -v7 option you should be able to 
see some traces of data passing through the bridge. Alternatively you 
can hack some debug statements in the writeHSS1394Message function in
src/genericavc/stanton/scs.cpp.

Greets,

Pieter

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Reply via email to