On May 12, 2015 05:18:40 AM Andrew Deryabin wrote: > Hi guys! > > I'm also making some improvements to master. I wanted to write a demo song > to present all changes but don't know when my imagination will help me :). > So there is a list of changes: > > SimpleDrums now have per-channel outputs, preserving backward compatibility: > > 0-1 channels are mix of all 16 internal tracks as before. Output channels > starting from 2 are individual channel stereo outputs. > Gui now has an ability to route each channel not only to dedicated output, > but also control if it is mixed to 0-1 output or not. Those changes are > saved and restored to/from song file. > > SimpleDrums config file version changed to '3' from '2', so this change will > not break previously written songs. > > I also added meters to each channel in the gui, so now it looks rather > beautiful :). > > With these changes there is no need to use external drum samplers (As I > think :)). Sidechaining/custom effects to each drum sample are now > possible.
Wow, totally awesome! Man, that's the most channels I've had to deal with on a track so far! It's a great test for my graphical router. So uh, I guess you are wondering about the overlap of our work, and the disappearance of synth stereo routing in my branch: I wrote: "In current MusE, only synthesizer tracks are true multi-channel, allowing users to route the individual channels anywhere. But the somewhat clumsy routing popup menu for these, with its mono and stereo listings, (which Geoff Beasely once complained was 'silly'), is gone now. In its place is a uniform system for all audio tracks. Users will either use an Omni route, or if they care to, go deeper by routing the single individual channels. There is no more 'mono' and 'stereo' synth track routes." Don't worry, I didn't nuke the old capability of synth 1/2-channel routing, the engine still supports a multi-channel route. I simply removed it from the routing popup menu. I had no plans to actually nuke it for now... Give me a few days to back-peddle a bit and try to support multi-channel buses at least in the graphical router. --- Why did I simplify it down to single-channel routing? You see, I was thinking of eventual full multi-channel tracks (3 or more channels) and how complicated the menus would be if we provided for all possibilities (say a 5 channel synth with 3-to-3, 4-to-4 and 5-to-5 routing etc.). Maybe too much? See below. Really the synth stereo-to-stereo listings thing was meant as a convenience so users wouldn't have to manually route two or more single channels. So I said screw it, and decided to simplify it to just Omni and SINGLE channel routing. I decided that Omni takes care of the first 'N' common channels, and applies panning ONLY to the first two channels Thus if you have a 34-channel synth and an Audio Output track, and provide an Omni route from the synth to the Audio Output track, Omni will route the first two (or one) channels of the synth to the output track and leave the other channels alone. If the Audio Output track were a 3-channel track, Omni would route the first three channels of the synth to the output, while applying pan to the first two channels only. And so on... I decided that if the user wants anything more complicated they can route any remaining channel pairs as single individual routes to other stereo tracks. Just it's now two user operations, not one. The idea was that the new graphical router would eliminate the need for multi-channel buses, because all the single routes are laid out, and I allow multiple selections. So you would select two channels of an item on the left pane, two channels of an item on the right pane, hit the connect button, and it connects TWO individual routes. No need for 'buses' with 2 or more channels. But with some changes I can turn that into a SINGLE two-channel route. A hard part will be drawing thick buses which diverge to the small connecting lines at each end and terminate at an item's channel bar. See, the weird thing is either way, the user must select two items on the left and two on the right. So for me it was like... why bother complicating it with buses? As for the popup menus, rethinking, for now I should try to reinstate the stereo listings but simplify as much as possible like I have done in my branch, where I now use the LED channel bars instead of copious items. Maybe we could show mono and stereo routing but maybe nothing more complicated than that, even with 3 or more track channels. Gimme some time to work this out. Thanks for reading! Whaddya think? Cool stuff man. Tim. > > There is another improvement: new class MusECore::WavePreviewDialog (and > it's global instance MusEGlobal::wavePreviewDialog). It's derived from > QfileDialog class and can be used to audition and select audio files. Now > it's used in SimpleDrums only, but when I'll be sure that it's stable, I > think it can be applied to audio import dialog also. > > Features: > > - automatic sample rate conversion > - auto play on file change (can be toggled) > - start/stop button > - audition channel works like audio metronome. > > That's all for now :) > > > Just a ping. > > > > I just saw I had missed a whole bunch of checkins, christmas, nice! :) > > > > /Robert ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
