On Sat, Feb 5, 2011 at 1:30 PM, Julie S <[email protected]> wrote: > I guess we could just not recalculate in this scenario, and just let people > they are actually getting 123 msec or 124 msec (when in reality they are not). > > ... > > I think as long as the Sequencer or nothing else is breaking, I think we > should just let people type what they want in this box and not bother with > adjusting it to the "real time."
The issue is I am using markers in RG to align with makers I have set in Ardour to synch to specific frames in a video (using xjadeo). Sometimes the markers don't hit right on a beat so I use Ardour's seconds & milliseconds clock to figure out the marker's position and this was when I discovered this curious behavior. If I want to input 467, I have to type 578. Another option might be to have a video synch value (like 24 fps or 29.97 or whatever) and be able to enter the frame value directly. -- Brett W. McCoy -- http://www.electricminstrel.com ------------------------------------------------------------------------ "In the rhythm of music a secret is hidden; If I were to divulge it, it would overturn the world." -- Jelaleddin Rumi ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
