> On 12/19/2014 04:10 AM, Tres Finocchiaro wrote: > Does anyone object to me wrapping the open bugs into a single bug > report so that they can be addressed as a WIP when the opportunity arises?
> https://github.com/LMMS/lmms/issues/276 Maybe not a JACK problem: "I changed to JACK and re-tried. The distortion was gone.". If straight ALSA is OK, straight JACK is OK and an ALSA to JACK bridge isn't, I'd point a finger at the bridge. No idea on how it could break rendering. > https://github.com/LMMS/lmms/issues/523 > https://github.com/LMMS/lmms/issues/908 "Jack-inputs (for recording, eventually), Jack-outputs... Jack-transport support, freewheeling?" No comment on in/outputs. Transport support is probably not a huge thing to add when the single tempo track changes are done, locating to an absolute time should be possible. Locating to bar/beat/tick might be a bit trickier with the freely automatable time signature? Freewheeling should for the most part be quite like rendering, except that any JACK MIDI ports should be left enabled. But hey, there is no JACK MIDI support yet! Maybe add that to the list? > https://github.com/LMMS/lmms/issues/1048 Not sure this has anything to do with JACK, if the bug is visible in the internal meters and scope the bad math happens way earlier. -- [email protected] softrabbit on #lmms ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
