From: Florian J. <flo...@we...> - 2012-06-17 16:03:21
|
forget my last mail (partially), i'm trying to solve this on my own ;) greetings flo Am 17.06.2012 02:35, schrieb Tim E. Real: > On June 17, 2012 12:49:04 AM you wrote: >> Hi >> >> with commmit 1304, you introduced changes which auto-connect ports/their >> default out routes to the MIDI tracks. (said svn blame) >> >> however, this is imho broken. try the following: >> >> create several tracks using port 1 and channels different than 1 >> create several tracks using a port other than 1 >> open the midi port config dialog >> change the device associated with port 1 (for example, create a new jack >> device, or justs et it differently) >> >> expected results: the device is changed, nothing else happens >> >> actual result: ALL midi tracks are set to port=1, channel=1! > > Good catch. Thanks a lot. > Flo and Geoff, try it now. > > We are only interested in altering tracks using the port being > changed in the midi port list. > > And it may not be terribly obvious, but under the column "Def out chan" > I recently allowed for UN-checking the default output channel number > so that NO port is output default and NO tracks are altered. > > Tim. > >> >> this only happens if you change the device associated with port 1, or >> more specifically, if you change the device associated with the port >> which owns the default route. >> >> IMO, changing port mappings may not touch tracks; if you re-connect your >> devices (different midi->usb bridge etc), you don't want this behaviour. >> >> IMHO, this default out port is currently pretty senseless anyway ;) >> (true, with multiple out routes this might become useful) >> >> >> my solution for this would be to remove code around confmport.cpp, line >> 920-930, but i'm not sure >> >> >> please review this, and change it appropriately... >> >> >> >> in general, i think, 'default in/out/whatever routes/blah' should ONLY >> affect newly created tracks automatically, and there should always be a >> BUTTON or MENU entry which allows you to apply the default routes to >> all/a single/the selected track(s). never automatically, and never ever >> without asking! >> >> please fix this ASAP. >> >> (ceterum censeo documentationem esse scribendam, or in english: as a >> side note, i think you should write some documentation ;) especially >> about the source code. if you do, then fewer mails like this would be >> required, because i can read the docs, understand the source and do the >> right thing on my own.) >> > >> greetings >> flo > > ------------------------------------------------------------------------------ > 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 > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > |