I have a desktop and a laptop computer, both running Ubuntu 18.04, and
both with Qtractor installed.
On the desktop computer, when I start a new project in Qtractor and
click on "Save As", the expected dialog appears. As expected, the "OK"
button is greyed out until I start to enter a name for the new project.
At that point the "OK" button becomes usable, and the project can
eventually be saved.
However, on my laptop computer, the "OK" button remains greyed out all
the time. This is true whether or not I have made any changes since
starting the new session. So I can't save any of my work. Currently,
therefore, Qtractor is effectively unusable on the laptop.
What could be causing this problem?
David
I'm probably trying to use QMidiArp for something it's not designed to
do, but I thought I'd ask this anyway:
In the Global Store section of the program, it looks like you can make a
pattern automatically switch after it completes, but I don't see any way
to specify for how many repititions it should run before switching.
Certainly QMidiArp doesn't aim to be a sequencer, so I'm not expecting
it to have everything, but I can't think of very many times that I've
wanted an arpeggio to play only once before switching to something else.
I do see that you can trigger almost anything it can do with learned
MIDI commands, so perhaps you're expected to have another sequencer do
the pattern switching by commanding QMidiArp via MIDI as needed? Or
perhaps this is all just meant for live improv under manual control? It
just seems like a repeat count would make the Global Store section way
more useful as a sequencer in an actual song.
DrumGizmo 0.9.19 Released!
DrumGizmo is an open source, multichannel, multilayered, cross-platform
drum plugin and stand-alone application. It enables you to compose drums
in midi and mix them with a multichannel approach. It is comparable to
that of mixing a real drumkit that has been recorded with a multimic setup.
This release is a feature release with some rather interesting new
features in it.
Highlights:
* Default midimaps now read from drumkit file so no explicit loading
of midimap are needed for kits that provide these.
* Add OSX retina display UI scaling.
* Sample selection default values improved
* UI rendering speed improvements
* New powermap feature, to make it easier to get a good natural
feeling when playing a midi-drumkit.
* Improved dgvalidater tool to include a lot more validation checks.
* Add gettext support to plugin UI with French translation.
* Per instrument voice limit feature to enable playing very fast with
low latency without the engine dropping out.
* Resampling quality (and thereby cpu usage) can now be controlled.
And a lot of bugfixes.
As usual read the detailed description of all the new shiny features,
see the detailed changelog: [1].
And now, without further ado, go grab 0.9.19!!! [2]
[1]: https://drumgizmo.org/wiki/doku.php?id=changelog:drumgizmo-0.9.19
[2]: https://drumgizmo.org/wiki/doku.php?id=getting_drumgizmo
Zita-avc1 0.1.0
----------------
'Analog' style vocoder, inspired by the famous EMS vocoders
from the 1970's. Standalone app, using Jack for audio and
MIDI I/O.
Zita-avc1 uses two sets of 24, 6th order bandpass filters
to analyse the voice input and to impose the same spectral
envelope on another signal. The filters span a frequency
range from approx. 70 Hz to 14 kHz. Filter spacing is 1/4
octave over most of this range.
Voiced / Unvoiced detection is based on the power ratio of
the high vs low frequency bands.
A sawtooth oscillator and a noise source are provided, but
normally you should use external signals, at least for the
voiced excitation. Bright strings-like signals seem to work
well, but anything with a dense 'pinkish' spectrum should do.
The voice input should be a clean, full-bandwidth voice signal,
speaking or singing.
This is very much an alpha version, released to invite comments
and suggestions.
Future developments may include:
- Pitch tracking.
- Filter band matrix.
- Store and recall formants with MIDI control.
- ...
See the README for a quick guide.
Available at the usual place:
<http://kokkinizita.linuxaudio.org/linuxaudio/downloads/zita-avc1-0.1.0.tar.…>
Ciao,
--
FA
Hi
Mamba release v1.8 is out
Mamba is a Virtual MIDI keyboard with some extended, unique features.
Virtual MIDI Keyboard
Mamba comes with some predefined key-maps, qwertz, qwerty, azerty(fr)
and azerty(be), but you could define your own with the included Key-map
Editor as well. Beside the computer keyboard and mouse, Mamba supports
jack-interconnect-ALSA MIDI I/O. Every channel use it's own Color to
display the played Notes per channel.
Jack and ALSA connections could be managed within the connection menu.
16 Channel Live MIDI Looper:
To record a loop, press "Play" and then to start recording press
"Record". To stop recording press record again. Playback will start
immediately.
The first recorded channel will become the Master channel. This one set
the time frame for all later recorded loops. For the Master Channel the
recording time will be stretched/clipped to match the next full beat
time point.
To record a new loop, switch to a other channel, select your instrument
and press "Record" again to start recording.
The later recorded loops will be synced to the master loop. When the
recording time extend the absolute Master loop time record will be
switched off. Absolute time is not bound to the loop point, so you could
record loops crossing it. You could as well stop recording by press
"Record" again before the time expires.
Each Channel could be cleared and re-recorded separate at any time. even
when you press "Record" on a already recorded channel, it will be
cleared before recording starts.
You could record the connected input device or play the Keyboard itself.
MIDI File player
You could select a MIDI file with the File Selector, or just drag'n drop
it in from your Filemanager. It will be loaded in the play buffer of the
first channel, regardless how much channels it use. You could use then
channel 2 - 16 to record your own playing into it. To play along with it
you could use any channel. A loaded file will become the Master channel
for the looper.
To save your work just go to Menu -> "File" -> "Save MIDI file as",
select the path and enter a file name. If you don't give the usual file
extension Mamba will add the extension .midi befor save it.
Fluidsynth
When you load a Sound-font via the Menu -> "Fluidsynth" -> "Load
Sound-font", or just drag'n drop it in from your Filemanager Mamba will
start the Fluidsynth engine and do the needed connections so that you
could just play along. Menu -> "Fluidsynth" -> "Settings" will pop-up a
new Window were you could select the Instrument for the channel and do
settings for Fluisynth Reverb and Chorus. All your Settings will be
saved on exit, so on next start you could just play along.
Mamba is released under the BSD Zero Clause License license
The GUI is build on libxputty - A damn tiny abstraction Layer to create
X11 window/widgets with cairo surfaces
https://github.com/brummer10/libxputty
To build Mamba from source, the following dependencies must be meat.
* libfluidsynth-dev
* libc6-dev
* libsmf-dev
* libcairo2-dev
* libx11-dev
* liblo-dev
* libsigc++-2.0-dev
* libjack-(jackd2)-dev
* libasound2-dev
So, here is the project page:
https://github.com/brummer10/Mamba
and here you'll find the last release:
https://github.com/brummer10/Mamba/releases/tag/v1.8
regards
hermann
On Sat, 21 Nov 2020 12:59:49 +0100 Hermann Meyer <brummer-(a)web.de>
wrote:
> Am 21.11.20 um 12:38 schrieb David Sumbler:
> > > On Fri, 20 Nov 2020 18:58:04 +0100,
> >
> > wrote:
> > > Date: Fri, 20 Nov 2020 18:58:04 +0100 Hermann Meyer <
> > > brummer-(a)web.de>
> > > wrote:
> > >
> > > Am 20.11.20 um 17:40 schrieb David Sumbler:
> > > > In Qtractor I can play the tracks through Timidity. The Track
> > > > dialogue offers me sounds from the FLuidR3_GM soundfont and
> > > > also soundbank-emg. But these sound identical, and I think
> > > > only FluidR3_GM is being used, which I have set as the default
> > > > in Timidity.
> > > >
> > > > I would like to use other sound fonts (e.g. Virtual-Playing-
> > > > Orchestra3), but I have never worked out how to achieve this.
> > >
> > > Virtual-Playing-Orchestra3 is in the sfz format, to use it you'll
> > > something like this:
> > > https://github.com/sfztools/sfizz
> > >
> > > For using other sf2 files you may checkout this one:
> > > https://github.com/brummer10/Fluida.lv2
> >
> > Thank you for those suggestions. I have now managed to get Fluida
> > installed (in addition to WhySynth). I also now have the relevant
> > directories showing up in Qtractor's View_Options_Plugins window,
> > and
> > both items show up in the MIDI/Instrument section of Track
> > Properties.
> >
> > However, even if I select an instrument from one of these, I still
> > do
> > not hear the appropriate sounds. I assume that I should be able to
> > connect WhySynth or Fluida to Qtractor in the Connections window;
> > but
> > as I mentioned in my previous email, they don't show up there.
> >
> > Using the MIDI tab of Qtractor's Connections window I have "Midi
> > Through" and "Qtractor" in the Readable column, and "Midi Through",
> > "Timidity" and "Qtractor" in the Writable column. If I connect
> > Qtractor to Timidity, I hear the FluidR3_GM sound regardless of
> > which
> > Instrument I have selected in Track Properties. If I disconnect
> > Qtractor and Timidity, then I hear nothing at all.
> >
> > I am sure there must be something very basic I am missing here, but
> > I
> > have no idea what to do next. How do I get the Instrument I
> > specify
> > for a track in the Track Properties window actually to sound when I
> > play the track in Qtractor?
> >
> > David
>
>
> You need to activate the plugin (the little round toggle beside the
> plugin name) and enable 'montor' in the mixer strip for the track you
> want to hear.
Thank you for that (and also to Rui for his reply). I hadn't realised
that the little dot was a toggle and not merely a sort of "bullet-
point".
But even having activated the plugin as sugessted, I still had no
sound. Eventually it occurred to me that, since (as I already
mentioned) I wasn't seeing anything in the Connections window that I
could connect Qtractor's output to, the problem was perhaps with Jack,
rather than Qtractor. Most of the many settings in QJackCtl mean
little or nothing to me, but I did spot that "Output Device" was set to
"hw:NVidia". Even I could recognize that that was inappropriate, so I
changed it to "default" and everything now works as expected.
Thank you again for your help in this.
David
On Sun, 22 Nov 2020 13:38:21 +0000
Ben Bell <bjb-linux-audio-user(a)deus.net> wrote:
> Replying to my own thread for xkcd/979 reasons.
What did you see, DenverCoder9?
Thanks for tyhe followup :)
--
======================================================================
Joe Hartley - UNIX/network Consultant - jh(a)brainiac.com
Without deviation from the norm, "progress" is not possible. - FZappa
On Tue, Nov 10, 2020 at 09:14:16AM +0000, Ben Bell wrote:
> I've got an opportunity to pick up a Behringer Wing relatively cheaply if
> I'm quick. So, obvious questions first: Has anyone got experience of the
> Behringer Wing with Linxu and indeed Ardour?
Replying to my own thread for xkcd/979 reasons.
I got the Wing. It shows up as a class-compliant USB audio interface and
seems to support 48 in, 48 out audio without any fiddling. I'm getting a
few xruns which I can reduce but not eliminate by raising buffer sizes.
This is my first USB audio interface so I'm inclined to think it's as likely
to be my machine as the Wing. I'm working through the usual processes of
trying to track down the cause.
One other glitch is that power it off has, a few times, triggered a rapid
descent into hard lock-up in the computer. I'll experiment a bit more but
suspect yanking the USB Audio interface out from underneath jack while
running it with high realtime priority is an unwise thing to do.
Switching it to DAW mode for use asa control surface with Ardour took a bit
of figuring out but once I had spotted there was a "DAW mode" button as well
as the setup screen, it worked reasonably well with Mackie, Mackie + Extender
and Mackie + 2 Extenders modes. The maps aren't 100% and if I keep it I'll
probably want to tweak things. On the Wing itself there's the option of
mapping various user defined buttons to actions, but so far I haven't seen
a way of sending arbitrary MIDI or OSC data. Shame.
Talking of OSC, it seems at a glance to have a comprehensive implementation
which is thoroughly documented (unlike most of the Wing) in an official but
third party document on Behringer's site.
One downside is the sheer physical size: I'm having to completely rebuild
my studio around it. Obviously you can read the specs and measure out on
the desk, but it didn't prepare me for quite how imposing it is and the
extent to which it makes reaching anything else (like a keyboard) a
challenge.
The AES50 extension boxes, its routing UI and actually pretty much
everything else about it is so far impressive. There's no manual to speak
of so the things that aren't intuitive take some figuring out. Once you
know them though the workflow is quick and easy. I'd quite like to have
had the opportunity of a Compact or Rack version but I imagine they'll
come.
In short, after a day's use there's definitely no show stoppers and with a
bit of tweaking it could be great for anyone whose needs match its specs.
If anyone has questions, feel free to contact me. In the mean time I'll
continue digging into it and seeing how it goes.
bjb
