On Wed, 31 Mar 2010 10:37:58 +1300, Steve Currington wrote: Here is hoping that USB3 has more of the advantages that Firewire had over USB2 (latency and sheer data throughput). I also hope that USB3 has better controls for cheapskate companies putting out devices with the same ID (which an inordinate quantity of cheap enclosures do) so when you put two external drives on the bus things go haywire. W. > ha ha although it will just mean I can screw things up 10 x faster.. > ha ha ha.. > > S. > On 31/03/2010, at 10:34 AM, Steve Currington wrote: > >> Roll on USB3 and gear with USB 3 interfaces. >> USB3 is out there and is about 10 times faster than USB2 so that >> might also help Just a nadge as too much stuff on USB2 can slow the >> whole bus down and so add latency due to USB "traffic jambs" >> >> Just another thing to consider. >> >> >> On 31/03/2010, at 5:58 AM, gil_gillian wrote: >> >>> Perhaps something to add. Quoting from >>> http://www.digitalprosound.com/2001/01_jan/features/midi2001-3.htm >>> >>> "He found the latency in the USB interfaces to be between seven and >>> eight milliseconds, about three times that of the classic >>> interfaces. This is not in itself an insurmountable problem, >>> because musicians adjust to small latencies in sound sources quite >>> well˜a bass player and a lead guitarist standing seven feet away >>> from each other usually have no trouble staying together." >>> >>> This would suggest non USB latency to be less than 3 msec and USB >>> midi latency to be less than 9. However as a player you compensate. >>> Note the speed of sound is approximately 1000 feet per second. So, >>> an acoustic guitarist hears what he is playing about 2 msec direct >>> and possibly 10-20 msec reflected (in a small room) after what he >>> plays.Two players standing 10 feet apart have a 10msec latency >>> between them. >>> >>> Regarding singer latency, I may be wrong here but it rather sounds >>> like you may getting the input and output signals mixed up. Logic >>> adjusts for audio latency when recording. Is the record channel >>> fader down? If you wish to here this just bring the fader up on on >>> a record channel while you are recording. For a full explanation of >>> Logic Audio Latency Compensation see >>> http://www.logic-users-group.com/index.php?q=record_latency.html >>> >>> Good luck, >>> Gil >>> >>> --- In Logic_Cafe@yahoogroups.com, GAmoore@... wrote: >>>> >>>> Yeah thats a good additional point - is that some beats you flub and >>>> some you hit right on - so take a mental note of which ones you hit. >>>> What I like to do is to hit the notes in a pattern of four in a square >>>> so I can see which beat automatically rather than counting or thinking. >>>> >>>> All midi has delays. Its designed to not be electrically coupled so >>>> there is an optical interface of some sort. Say that its 20 >>>> milliseconds (1/500 of a second). Maybe my math is wrong here, but say >>>> you have a tempo of 120 bpm, then thats two beats per second. If logic >>>> is 960 ticks per quarter note, thats 1920 ticks that occur in that >>>> second. So each tick is 1/1920 or .52 millseconds each. So 20 ms / .52 >>>> = 40 ticks. In other words, even if you play right on the beat, the >>>> midi delay (if we assume 20ms) is 40 ticks. This is why its a good idea >>>> to slide the matrix notes to the left 40 ticks - just to bring them to >>>> where they should have been. Then use the quantize to adjust the feel >>>> of the playing. >>>> >>>> Greg >>>> >>> >>> >> >> >> >> [Non-text portions of this message have been removed] >> >> >> >> ------------------------------------ >> >> Yahoo! Groups Links >> >> >> > > > > ------------------------------------ > > Yahoo! Groups Links > > >
Message
Re: [Logic_Cafe] Re: A Question
2010-03-30 by Steven Woolgar