On 09/20/2013 01:50 PM, Harry van Haaren wrote: I'm glad you asked! :) A fully functional, comprehensively tooled up (including keybinding functionality for as much as possible) jack midi sequencer, that doesn't do audio or plugins (we have decent apps for those already), but does midi......comprehensively. (and including properly functioning MMC, MTC, bank and patch management, a full set of keybinding functions for as much as possible, including navigation, folder tracks (containers) for handling a lot of tracks, a complete pianoroll toolset for input/edit/remove including bindings for things like toggle step input, just to name a few.....) And a gui that works, and saves position, size and midi clip values like CC lanes assigned per track that display in the pianoroll (1st violins track might have velocity/volume/pitchbend/modulation CC lanes, and tubas might only have volume and velocity, as an example) Did i mention keybinding functionality for as much as possible? And complete non-session-manager and OSC functionality? That should keep you busy for a while. :) Regards, Alex.

On Fri, 2013-09-20 at 12:50 +0100, Harry van Haaren wrote: IMO: New drivers for audio hardware and more often updates for some existing drivers. Kernel-rt longtime versions packages for all major distros that don't cause issues, such as graphic driver troubles. When reading musician forums: Seemingly many people are missing fashion software, such as auto-tune and all the stuff that Live FX does provide. Not a fashion, but for understandable reasons missing, but wanted by many musicians are orchestras and choirs like those EastWest stuff, synth like Alchemy etc. pp.. Especially for me: A new DAW, Qtractor with the precision and comfort of Ardour2, regarding to latency compensation and storing and restoring an audio session on what machine, from what directory ever, not to forget a cancel option for the editors. Ardour3 isn't what I'm looking for, it should provide a Qtractor like workflow, but I want exact enough latency compensation and even if Qtractor would be exact enough (it isn't yet), in addition it should be possible to switch between different latencies, also impossible when using Qtractor, the compensation is keept for the recorded latency when changing the latency. The way things are saved and restored for Qtracor is a real PITA and that it seems to be impossible to cancel changes, when leaving an editor.

On Fri, 2013-09-20 at 13:37 +0100, Harry van Haaren wrote: No, I contributed for a long time as Qtractor tester and this request is years old, Rui is aware about it and explained that he focus other things, such as automation first. So there's no need to do it, because it's already done. That's why I neither Cc'ed to Rui, nor to qtractor-devel(a)lists.sourceforge.net . I really was very active with testing Qtractor, but when started and never finished a translation, my life situation changed. Fortunately somebody else did the translation. I don't have the time to do as much testing as in the past, so usually I stay with the packages provided by the distos I'm using and don't build it from SVN anymore, or at least do it very seldom.

On Fri, 2013-09-20 at 14:36 +0100, John Rigg wrote: I know it, but never tested it. Can it do all those disgusting things, e.g. such as the Black Eyed Peas do? Sometimes it is done nicely, e.g. by Daft Punk, while I don't listen to their music, it anyway is ok. Can it be used to auto-tune the news etc.? I guess those auto-tune folks want to use it as a real effect processor, comparable to a vocoder and others want to make speech singing. Btw. while I'm comfortable with the existing Linux vocoders, I understand that some folks are missing a lot for the ones available for Linux.

On Fri, Sep 20, 2013 at 05:44:49PM +0200, Jeremy Jongepier wrote: Please note that zita-at1 is _not_ a vocoder, it just resamples the signal while skipping or repeating cycles to preserve the original timing. There is no formant correction, so it should be used only to correct small errors (unless you want the effect). Ciao, -- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow)

On Fri, Sep 20, 2013 at 7:50 AM, Harry van Haaren <harryhaaren(a)gmail.com>wrote;wrote: Since you asked and it was recommended to me some time back to chat with you about this... ;) The state of audio restoration tools on Linux is abysmal. The short version is, nothing on Linux comes close to options in other OSes. There are some options to run via Wine (ie. I run WaveARTs plugins via Wine) but many more options that do not (ie. iZotope). The tools I can think of... Hum/Buzz Removal -- Essentially Notch filters, that are harmonically linked. Broadband Noise Removal -- Even a good multiband gate can help, as that is close to what WaveARTs MRNoise is, and it is noticeably better than options on Linux. I am not sure what iZotope does for it's destructive process, but I believe is also a form of multiband gating. Click/Pop removal -- Not something I use a lot, so can't comment here Expander -- A decent expander is surprisingly difficult to come by. Most options on Linux are gates instead of true expanders, and the expanders I can find like Calf, I haven't been to happy with the results I have been able to get out of it. I would suggest looking at MRNoise from WaveARTs for a great example of this, it honestly is one of the best expanders I have used. There is one last component to this, which is a destructive environment to work in, actually non-realtime is a better term for what I am looking for. Believe it or not this is one of the few areas I personally believe a non-realtime workflow is better than realtime/non-destructive. I prefer being able to find areas with a spectrograph to sample to set my multiband gating process off of, and then apply to areas in the same way. I prefer to do this non-realtime because in the same audio clip delivered to me by a video editor, I may need to do this multiple times, with different settings each time, for each edit point they have at times. The workflow I would ideally see is the ability to open the file in the editor, apply Hi/Lo-pass filtering as appropriate, hum and buzz removal if needed, sample a section of audio for setting any appropriate settings for hum/buzz and for broadband noise removal, then finally remove the noise via multiband gating or whatever. The last step for me personally is downwards expansion to hopefully provide just a slight amount more cleanup at the end. The use case is pretty much a given for anyone that gets video from editors in any form(But especially dialog), and has to edit the audio together. It also works wonders if used appropriately on field recordings for SFX, Dialog, etc. It is the one thing I wasn't able to stay in Linux for when working on the recent Tube trailer. So that should be a few years worth of work for you, should you choose to accept it:) Seablade