On August 8, 2012 9:53:39 PM Robert Jonsson wrote: > Hi Tim and everybody, > > Sorry for being out of touch (more than usually even), I'm here and > infact recording quite a bit.
Yeah me too. But actually I am quite down about the recorded wave latency. I lost motivation to record, having to run at very low Jack periods to ensure recorded waves were not out of sync too much when played back. On playback I run Jack at 2048 period, run several instances of Guitarix and various MusE rack plugins, synths etc. Recorded wave latency is terrible at 2048 period. And *no* compensation, either automatically or by advanced (er *standard* actually) wave editing features. So having to exit MusE, set Jack to 128 frames, restart MusE, turn off any taxing tracks, avoid using Guitarix and so on just to record with low latency is a pain. 128 frames is very taxing with everything turned on and Guitarix running etc, Jack boots me out. Looky here! http://dl.dropbox.com/u/53315356/new_wave_editor_1.png Progress: Class WaveView which is a sub-class of View, is gone. Replaced by WaveCanvas, a sub-class of EventCanvas. Yep, in the picture yer' lookin' at 2 actual wave events (from 2 parts) drawn with CItem (Canvas Items) instead of the old custom pdraw() from the old WaveView. A tempo map and time signatures can be seen to be active and applied. Notice the blue selection rectangle, tick raster background lines, and green marker lines, all of which were *absent* with WaveView. The goal is to allow /selection/ and /movement/ of the wave events. Once selected, a dialog could be opened for more precise frame adjustment. Currently in the MusE wave editor, the red cursor moves in ticks. At high magnification you can get it down to single ticks but not frames. You'll notice the cursor jumps quite a bit at that resolution, for one whole tick. Sometimes you'll notice you can't get the cursor to go to some exact frame and it can be frustrating. So I will try to change it to single *frame* resolution, seems reasonable since all that inaccessible space between the single-tick cursor jumps is just frame-space. Once I colour (shade) the event rectangle drawings, you'll be able to see clearly the distinction between different wave event boundaries. Also, with wave events there is a special further wavefile position offset value called 'spos' which we must allow the user to adjust. Together the wave spos offset and movement of wave events (and some dialogs and toolbars for more precise movement) will allow for /basic/ correction of recorded wave latency. I mentioned before this is *not* the perfect solution for latency because if the record input has two sources with /differing/ latency, these movement features are useless. Only true low-level automatic compensation will correct for that, and as I mentioned I am trying to work that out but it is very difficult. Tim. > I'll give you guys a listen what I've > been up to sooner rather than later :) > > Also been doing some muse hacking but haven't really started of for > real, got some minor bugs that I want to take care of. Also some > crashes, mostly related to plugins. Will try to give more info later > on. > > As MusE is pretty much controlled through anarchy I've got nothing > much to add about peoples agenda. For the moment at least. In a month > or so we'll see how far we've come. > > Regards, > Robert ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
