qtractor-devel — Qtractor development discussion

Re: [Qtractor-devel] some requests

[Ralf M. <ral...@al...>]

My reply didn't came through the list, likely it's just delayed.

Begin forwarded message:

Date: Mon, 21 Dec 2015 23:56:19 +0100
From: Ralf Mardorf
To: qtr...@li...
Subject: Re: [Qtractor-devel] some requests


On Mon, 21 Dec 2015 23:49:19 +0100 (CET), mas...@al...
wrote:
>automatic crossfades  

Older versions of Qtractor provide cross fades. Somewhere at the end
of one overlapping track you can chose the length of the fade out with
the mouse and it's the same for the fade in at the beginning of the
other track. Test it with the mouse, IIRC there are squares you can
move forward and backwards to chose the fade length

Re: [Qtractor-devel] some requests

[Ralf M. <ral...@al...>]

On Mon, 21 Dec 2015 23:49:19 +0100 (CET), mas...@al...
wrote:
>automatic crossfades

Older versions of Qtractor provide cross fades. Somewhere at the end
of one overlapping track you can chose the length of the fade out with
the mouse and it's the same for the fade in at the beginning of the
other track. Test it with the mouse, IIRC there are squares you can
move forward and backwards to chose the fade length.

[Qtractor-devel] some requests

[<mas...@al...>]

Hi Rui,

It is possible to implement in the future automatic crossfades, gain level of the tracks without using the mixer and high resolution of the waveforms?

cheers

Massimo

Re: [Qtractor-devel] Playhead click moving

[Rui N. C. <rn...@rn...>]

On 12/21/2015 12:22 PM, Philip Yassin wrote:
> Hi everyone!
>
> It's cold out there and the new Qtractor 0.7.2 is fresh out :) life is
> peachy
>
> I have my empty session in front of me, and something strikes me.
> When I click in the timeline (I have two tracks, and nothing in it)
> nothing happens.

> That must be one of the reasons why the new users that I saw approaching
> it (not that many but still quite a few) found it "user hostile" (my
> daughter texted me that /this very morning///, adding that "the
> interface is even worse than cubase's" das my girl :) I think this is
> excessive to say the least) sometimes, it does nothing when you expect
> it to do something.

tell your doughter to make (or text if she likes) some festure 
requests--even better, nurture her to get into the open-source community 
and rant away for her self! ;)


> Clicking in the timeline on an empty zone of a track could position the
> playhead at that location. Heck, even (optionally) in a non-empty zone,
> when selecting a clip, I can see how some ppl would use it like that. I
> think I would.
> At the very least, clicking in the empty zone below the track could do
> that, instead of doing nothing.
>

it's been o long departure from early days, but did you ever thought 
that shift-click would do exactly what you/she want?


> I humbly thing it would go a long way towards peace, harmony and
> downright happiness :)
>
> Maybe with the mid... Hey, the middle button /does/ something! It
> positions the two markers... Wow... All across the timeline window...
> Countless moons and I didn't know that... Damned, that kinda ruins my
> previous rambling, well, at least half of it. Now, Qtractor does
> something. And let me tell you, it is a /very/ nice feeling, moving the
> markers around with a single click. Oh, and it doesn't mess with an
> existing loop markers, too, nice. Id love to move the playhead as well
> that way, instead of this "middle click, forward key (or is the playhead
> ahead in that case backwards)" foggy business, and come to think of it,
> I would not mind if that would only move the transcient, invisible "last
> play position" and not the left & right markers. So that basically would
> just move the playhead. Can't that be an option? I might add to my case
> that this is the standard behaviour in the timelines of most of the
> software I saw. I have Kdenlive opened now, and that is what it does,
> only with the left mouse button. Doing like the elders say is often a
> (the) good path :)

middle-click behavior can be optionally reversed... indeed, that was 
once a long time ago a request from danboid, for which i made it so. i 
don't always indulge on dan's requests (you can put that 
most-interesting-man-meme here:) but... just think on tempo ramps and 
what not :D

>
> Second: Is there a technical reason why the "spacebar" play (and the
> moving between markers) is disabled while a plugin interface is opened?
> I know it can be solved with a control surface. Aaah, yes, I know.
> That's because one can have a need for his space key /inside/ the plugin
> interface to enter letters, like to name a preset. Hm. Feel free to
> ignore me :/
>

spacebar is a hard-coded keyboard shortcut (cf. Help/Shortcuts...) and 
as such it only works when the main window is in focus. that said, when 
any other window gets on top, like some plugins GUI's do, qtractor is 
blind-folded re. keyboard shortcuts. and yes, MIDI controller shortcuts 
don't suffer from this GUI window focus state-of-things. :)

> I guess I just wanted to say hi ;) and thanks again for Qtractor. Hey,
> why can't we see the list of presets of SynthV1 (which is really a mean
> polyphonic beast but I already said that) in the track's right-click
> "preset" menu like in other well-groomed plugins? ;)
>

there are synthv1 presets and there are, otoh. qtractor named presets, 
which includes system wide lv2 presets btw. the later are the ones you 
have access from the generic plugin/properties... dialog. the former are 
specific to the plugin in question. that said, you can certainly map 
ones into the others. i guess that will be straightforward once you 
realize the difference.

hth.
cheers
-- 
rncbc aka. Rui Nuno Capela

[Qtractor-devel] Playhead click moving

[Philip Y. <ph...@gn...>]

Hi everyone!

It's cold out there and the new Qtractor 0.7.2 is fresh out :) life is 
peachy

I have my empty session in front of me, and something strikes me.
When I click in the timeline (I have two tracks, and nothing in it) 
nothing happens.
That must be one of the reasons why the new users that I saw approaching 
it (not that many but still quite a few) found it "user hostile" (my 
daughter texted me that /this very morning///, adding that "the 
interface is even worse than cubase's" das my girl :) I think this is 
excessive to say the least) sometimes, it does nothing when you expect 
it to do something.
Clicking in the timeline on an empty zone of a track could position the 
playhead at that location. Heck, even (optionally) in a non-empty zone, 
when selecting a clip, I can see how some ppl would use it like that. I 
think I would.
At the very least, clicking in the empty zone below the track could do 
that, instead of doing nothing.

I humbly thing it would go a long way towards peace, harmony and 
downright happiness :)

Maybe with the mid... Hey, the middle button /does/ something! It 
positions the two markers... Wow... All across the timeline window... 
Countless moons and I didn't know that... Damned, that kinda ruins my 
previous rambling, well, at least half of it. Now, Qtractor does 
something. And let me tell you, it is a /very/ nice feeling, moving the 
markers around with a single click. Oh, and it doesn't mess with an 
existing loop markers, too, nice. Id love to move the playhead as well 
that way, instead of this "middle click, forward key (or is the playhead 
ahead in that case backwards)" foggy business, and come to think of it, 
I would not mind if that would only move the transcient, invisible "last 
play position" and not the left & right markers. So that basically would 
just move the playhead. Can't that be an option? I might add to my case 
that this is the standard behaviour in the timelines of most of the 
software I saw. I have Kdenlive opened now, and that is what it does, 
only with the left mouse button. Doing like the elders say is often a 
(the) good path :)

Second: Is there a technical reason why the "spacebar" play (and the 
moving between markers) is disabled while a plugin interface is opened? 
I know it can be solved with a control surface. Aaah, yes, I know. 
That's because one can have a need for his space key /inside/ the plugin 
interface to enter letters, like to name a preset. Hm. Feel free to 
ignore me :/

I guess I just wanted to say hi ;) and thanks again for Qtractor. Hey, 
why can't we see the list of presets of SynthV1 (which is really a mean 
polyphonic beast but I already said that) in the track's right-click 
"preset" menu like in other well-groomed plugins? ;)

Phil


-- 
Philippe "xaccrocheur" Yassin
http://manyrecords.com
http://bitbucket.org/xaccrocheur / https://github.com/xaccrocheur

Re: [Qtractor-devel] Happy Bunny :)

[Will G. <wil...@mu...>]

On Mon, 14 Dec 2015 18:05:55 +0000
Philip Yassin <ph...@gn...> wrote:

> On 14/12/2015 10:25, Will Godfrey wrote:
> > On Mon, 14 Dec 2015 00:39:39 +0100
> > Albert Graef <ag...@gm...> wrote:
> >
> >> On Sun, Dec 13, 2015 at 4:35 PM, Philip Yassin <ph...@gn...> wrote:
> >>
> >>> I guess I'm going to have to wait ; Is there a debian binary package of
> >>> this plugin available yet?
> >>
> >> According to https://launchpad.net/ubuntu/+source/yoshimi, it looks like
> >> 1.3.7.1-1 is in Xenial (upcoming Ubuntu16.04 LTS),
> Aah, I see. I was under the impression that an up-to-date Yoshimi was in 
> the KXStudio repos. I guess I'll wait :|

Unfortunately KXstudio is over 2 years out of date. There have been *major*
developments since then :(

> > Do you know when their code freeze is for this release? I don't like to push
> > out Yoshimi versions too quickly (it's not fair on the distro packagers) but
> > there have been a lot of improvements recently. I was planning to push out
> > 1.3.8 sometime in January, but could bring it forward if it means sneaking it
> > in :)
> I found this 
> http://www.omgubuntu.co.uk/2015/10/ubuntu-16-04-release-schedule-release-schedule-date-xenial-xerus 
> :
> 
>   * *Alpha 1* – December 31st (for flavours)
>   * *Alpha 2 *– January 28th (for flavours)
>   * /Feature Freeze /— February 18th
>   * *Beta 1* – February 25th (for flavours)
>   * /UI Freeze/ — March 10th
>   * *Final Beta *– March 24th
>   * /Kernel Freeze/ — April 7th
>   * *Release Candidate *– April 14th

Ah, thanks. This is good news. I can aim to get between the alphas :)

-- 
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.

Re: [Qtractor-devel] Happy Bunny :)

[Philip Y. <ph...@gn...>]

On 14/12/2015 10:25, Will Godfrey wrote:
> On Mon, 14 Dec 2015 00:39:39 +0100
> Albert Graef <ag...@gm...> wrote:
>
>> On Sun, Dec 13, 2015 at 4:35 PM, Philip Yassin <ph...@gn...> wrote:
>>
>>> I guess I'm going to have to wait ; Is there a debian binary package of
>>> this plugin available yet?
>>
>> According to https://launchpad.net/ubuntu/+source/yoshimi, it looks like
>> 1.3.7.1-1 is in Xenial (upcoming Ubuntu16.04 LTS),
Aah, I see. I was under the impression that an up-to-date Yoshimi was in 
the KXStudio repos. I guess I'll wait :|
> Do you know when their code freeze is for this release? I don't like to push
> out Yoshimi versions too quickly (it's not fair on the distro packagers) but
> there have been a lot of improvements recently. I was planning to push out
> 1.3.8 sometime in January, but could bring it forward if it means sneaking it
> in :)
I found this 
http://www.omgubuntu.co.uk/2015/10/ubuntu-16-04-release-schedule-release-schedule-date-xenial-xerus 
:

  * *Alpha 1* – December 31st (for flavours)
  * *Alpha 2 *– January 28th (for flavours)
  * /Feature Freeze /— February 18th
  * *Beta 1* – February 25th (for flavours)
  * /UI Freeze/ — March 10th
  * *Final Beta *– March 24th
  * /Kernel Freeze/ — April 7th
  * *Release Candidate *– April 14th


-- 
Philippe "xaccrocheur" Yassin
http://manyrecords.com
http://bitbucket.org/xaccrocheur / https://github.com/xaccrocheur

Re: [Qtractor-devel] Happy Bunny :)

[Albert G. <ag...@gm...>]

On Mon, Dec 14, 2015 at 11:25 AM, Will Godfrey <wil...@mu...>
wrote:

> Do you know when their code freeze is for this release?


No, sorry, I'm not much into Ubuntu any more. Maybe someone else here knows?

-- 
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email:  ag...@gm...
WWW:    https://plus.google.com/+AlbertGraef

Re: [Qtractor-devel] Happy Bunny :)

[Will G. <wil...@mu...>]

On Mon, 14 Dec 2015 00:39:39 +0100
Albert Graef <ag...@gm...> wrote:

> On Sun, Dec 13, 2015 at 4:35 PM, Philip Yassin <ph...@gn...> wrote:
> 
> > I guess I'm going to have to wait ; Is there a debian binary package of
> > this plugin available yet?
> 
> 
> According to https://launchpad.net/ubuntu/+source/yoshimi, it looks like
> 1.3.7.1-1 is in Xenial (upcoming Ubuntu16.04 LTS),

Do you know when their code freeze is for this release? I don't like to push
out Yoshimi versions too quickly (it's not fair on the distro packagers) but
there have been a lot of improvements recently. I was planning to push out
1.3.8 sometime in January, but could bring it forward if it means sneaking it
in :)

-- 
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.

Re: [Qtractor-devel] Happy Bunny :)

[Albert G. <ag...@gm...>]

On Sun, Dec 13, 2015 at 4:35 PM, Philip Yassin <ph...@gn...> wrote:

> I guess I'm going to have to wait ; Is there a debian binary package of
> this plugin available yet?


According to https://launchpad.net/ubuntu/+source/yoshimi, it looks like
1.3.7.1-1 is in Xenial (upcoming Ubuntu16.04 LTS),

That's why I'm on Arch now -- always enjoy all the latest stuff without
waiting. :)

-- 
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email:  ag...@gm...
WWW:    https://plus.google.com/+AlbertGraef

Re: [Qtractor-devel] Happy Bunny :)

[Will G. <wil...@mu...>]

Answered off-list.

-- 
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.

Re: [Qtractor-devel] Happy Bunny :)

[Philip Y. <ph...@gn...>]

On 12/12/2015 22:57, Albert Graef wrote:
> Hi Will,
>
> On Thu, Dec 10, 2015 at 9:53 PM, Will Godfrey 
> <wil...@mu... <mailto:wil...@mu...>> wrote:
>
>     Just tried the latest Qtractor with Yoshimi as an LV2 plugin.
>
Is this me, or is this breaking news? I've been waiting for an LV2 
plugin version of Yoshimi for years!
I'd like to write a news item for LMP about it, as soon as I can get my 
hands on it. I had no luck building it, make failed with:

(...)
[ 44%] Building CXX object CMakeFiles/yoshimi.dir/main.cpp.o
Linking CXX executable yoshimi
/usr/bin/ld: cannot find -ljpeg
collect2: error: ld returned 1 exit status
make[2]: *** [yoshimi] Error 1
make[1]: *** [CMakeFiles/yoshimi.dir/all] Error 2
make: *** [all] Error 2

And going back into ccmake (that I don't recall having ever used before) 
it seems that all FLTK-something had the -NOTFOUND flag :( I think I 
have every fltk possible package installed...

I guess I'm going to have to wait ; Is there a debian binary package of 
this plugin available yet?

Phil

> Works very well indeed! As the Arch package on the AUR is out of date 
> right now, I've uploaded a new PKGBUILD which builds from the latest 
> git sources here: https://aur.archlinux.org/packages/yoshimi-git/
>
> Albert
>
> -- 
> Dr. Albert Gr"af
> Computer Music Research Group, JGU Mainz, Germany
> Email: ag...@gm... <mailto:ag...@gm...>
> WWW: https://plus.google.com/+AlbertGraef
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Qtractor-devel mailing list
> Qtr...@li...
> https://lists.sourceforge.net/lists/listinfo/qtractor-devel

-- 
Philippe "xaccrocheur" Yassin
http://manyrecords.com
http://bitbucket.org/xaccrocheur / https://github.com/xaccrocheur

Re: [Qtractor-devel] Happy Bunny :)

[Philip Y. <ph...@gn...>]

On 12/12/2015 22:57, Albert Graef wrote:
> Hi Will,
>
> On Thu, Dec 10, 2015 at 9:53 PM, Will Godfrey 
> <wil...@mu... <mailto:wil...@mu...>> wrote:
>
>     Just tried the latest Qtractor with Yoshimi as an LV2 plugin.
>
Is this me, or is this breaking news? I've been waiting for an LV2 
plugin version of Yoshimi for years!
I'd like to write a news item for LMP about it, as soon as I can get my 
hands on it. I had no luck building it, make failed with:

(...)
[ 44%] Building CXX object CMakeFiles/yoshimi.dir/main.cpp.o
Linking CXX executable yoshimi
/usr/bin/ld: cannot find -ljpeg
collect2: error: ld returned 1 exit status
make[2]: *** [yoshimi] Error 1
make[1]: *** [CMakeFiles/yoshimi.dir/all] Error 2
make: *** [all] Error 2

And going back into ccmake (that I don't recall having ever used before) 
it seems that all FLTK-something had the -NOTFOUND flag :( I think I 
have every fltk possible package installed...

I guess I'm going to have to wait ; Is there a debian binary package of 
this plugin available yet?

Phil

> Works very well indeed! As the Arch package on the AUR is out of date 
> right now, I've uploaded a new PKGBUILD which builds from the latest 
> git sources here: https://aur.archlinux.org/packages/yoshimi-git/
>
> Albert
>
> -- 
> Dr. Albert Gr"af
> Computer Music Research Group, JGU Mainz, Germany
> Email: ag...@gm... <mailto:ag...@gm...>
> WWW: https://plus.google.com/+AlbertGraef
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Qtractor-devel mailing list
> Qtr...@li...
> https://lists.sourceforge.net/lists/listinfo/qtractor-devel

-- 
Philippe "xaccrocheur" Yassin
http://manyrecords.com
http://bitbucket.org/xaccrocheur / https://github.com/xaccrocheur

Re: [Qtractor-devel] Happy Bunny :)

[Albert G. <ag...@gm...>]

Hi Will,

On Thu, Dec 10, 2015 at 9:53 PM, Will Godfrey <wil...@mu...>
wrote:

> Just tried the latest Qtractor with Yoshimi as an LV2 plugin.


Works very well indeed! As the Arch package on the AUR is out of date right
now, I've uploaded a new PKGBUILD which builds from the latest git sources
here: https://aur.archlinux.org/packages/yoshimi-git/

Albert

-- 
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email:  ag...@gm...
WWW:    https://plus.google.com/+AlbertGraef

Re: [Qtractor-devel] Happy Bunny :)

[Philip Y. <ph...@gn...>]

On 11/12/2015 11:38, Will Godfrey wrote:
> On Fri, 11 Dec 2015 08:55:43 +0000
> Rui Nuno Capela <rn...@rn...> wrote:
>
>> On 2015-12-10 20:53, Will Godfrey wrote:
>>> Just tried the latest Qtractor with Yoshimi as an LV2 plugin.
>>>
>>> All works very smoothly, and when running a fairly complex composition,
>>> Qjackctl
>>> is reporting just about the same DSP load as feeding MIDI direct to
>>> Yoshimi via
>>> aplaymidi.
>> thanks Will.
>>
>> btw. as LV2, have you tried to render to audio (menu Track/Export
>> Tracks.../Audio) ?
>>
>>
>> cheers
> I didn't know you could do that!
>
> Just tried it with one of my test files. This contains bank and program changes
> as well as volume and pan settings.
>
> If it is done from a 'clean' Yoshimi it gets the volume and pan settings wrong
> (I think it is just not seeing them). If it has been played through first, it
> gets them right - although it would probably miss changes in the middle of the
> tracks (there aren't any).
>
> Volume and pan are CCs embedded in the individual tracks shortly after the bank
> and program changes.
>
> How odd - I can't seem to reproduce that fault now :?
>
> Either way it chops off the end. I suspect it's looking at the last note-off
> and not allowing for the effect of reverbs and slow note release - which I use
> quite a lot of :)
That makes me think of something happening with the QMIDIArp LV2 plugin, 
that prevents the start (well, the 1st chord) of a MIDI clip to play 
when "sync tempo to host" is checked..? Excuse the noise if it has 
nothing to do with the matter at hand.
>
>
> Apart from that it's rather impressive!
It is (is everything exported, including post-instrument audio process? 
Wow) makes one wonder why a full master export is not possible ; not 
that there is anything wrong with mixing the song down to audacity. Ah 
yes, there is: Potential xruns, more programs to load at the same 
time... But mostly friends, asking where the option is ;)

BTW, this new "duplicate track" is a really cool thing. I forgot that I 
even needed it ;)


-- 
Philippe "xaccrocheur" Yassin
http://manyrecords.com
http://bitbucket.org/xaccrocheur / https://github.com/xaccrocheur

Re: [Qtractor-devel] Happy Bunny :)

[Will G. <wil...@mu...>]

On Fri, 11 Dec 2015 08:55:43 +0000
Rui Nuno Capela <rn...@rn...> wrote:

> On 2015-12-10 20:53, Will Godfrey wrote:
> > Just tried the latest Qtractor with Yoshimi as an LV2 plugin.
> > 
> > All works very smoothly, and when running a fairly complex composition, 
> > Qjackctl
> > is reporting just about the same DSP load as feeding MIDI direct to 
> > Yoshimi via
> > aplaymidi.
> 
> thanks Will.
> 
> btw. as LV2, have you tried to render to audio (menu Track/Export 
> Tracks.../Audio) ?
> 
> 
> cheers

I didn't know you could do that!

Just tried it with one of my test files. This contains bank and program changes
as well as volume and pan settings.

If it is done from a 'clean' Yoshimi it gets the volume and pan settings wrong
(I think it is just not seeing them). If it has been played through first, it
gets them right - although it would probably miss changes in the middle of the
tracks (there aren't any).

Volume and pan are CCs embedded in the individual tracks shortly after the bank
and program changes.

How odd - I can't seem to reproduce that fault now :?

Either way it chops off the end. I suspect it's looking at the last note-off
and not allowing for the effect of reverbs and slow note release - which I use
quite a lot of :)


Apart from that it's rather impressive!

-- 
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.

[Qtractor-devel] [ANN] Qtractor 0.7.2 - The Tacky Gluon beta release

[Rui N. C. <rn...@rn...>]

Season greetings y'all,

As cheesy as it might go, as a must already,

   Qtractor 0.7.2 (tacky gluon beta) is out!

Quite frankly, there's nothing really stopping you from an upgrade or 
rather update to taste! :)

   Qtractor [1] is an audio/MIDI multi-track sequencer application 
written in C++ with the Qt framework [2]. Target platform is Linux, 
where the Jack Audio Connection Kit (JACK [3]) for audio and the 
Advanced Linux Sound Architecture (ALSA [4]) for MIDI are the main 
infrastructures to evolve as a fairly-featured Linux desktop audio 
workstation GUI, specially dedicated to the personal home-studio.

Major highlights for this dot release are:

* MIDI Track/Instrument bank/programs menu (NEW)
* VST plug-ins preset/bank (FXP/FXB) files support (NEW)
* Duplicate track menu command (NEW)
* XRUN status bar indicator (NEW)

And, of course, Qtractor [1] is now built to Qt5 [2] as per configure 
default.


Hope you enjoy.


Website:
   http://qtractor.sourceforge.net

Project page:
   http://sourceforge.net/projects/qtractor

Downloads:
   http://sourceforge.net/projects/qtractor/files

- source tarball:
   http://www.rncbc.org/archive/qtractor-0.7.2.tar.gz

- source package (openSUSE 13.2):
   http://www.rncbc.org/archive/qtractor-0.7.2-20.rncbc.suse132.src.rpm

- binary packages (openSUSE 13.2):
   http://www.rncbc.org/archive/qtractor-0.7.2-20.rncbc.suse132.i586.rpm
   
http://www.rncbc.org/archive/qtractor-0.7.2-20.rncbc.suse132.x86_84.rpm

- wiki (help wanted!):
   http://sourceforge.net/p/qtractor/wiki/

Weblog (upstream support):
   http://www.rncbc.org

License:
   Qtractor [1] is free, open-source Linux Audio [5] software, 
distributed under the terms of the GNU General Public License (GPL [6]) 
version 2 or later.

Change-log:
- Yet another audio/MIDI time drift correction fix, now giving it some 
slack while turnaround looping on tempo changes.
- Prevent x11extras module from use on non-X11/Unix platforms.
- MIDI Track/Instrument cascading pop-up menus have been added, to main 
and MIDI clip editor windows.
- VST Plugin preset/bank files support (FXB/FXP) is now being integrated 
to the generic Plugin/Properties widget dialog.
- Added new Track/Duplicate menu command.
- Added simple XRUN red indicator to status bar.
- Make sure program change/presets are not selected on possibly 
multi-timbral instrument plugins when inserted on a MIDI bus.
- Prefer Qt5 over Qt4 by default with configure script.
- Fixed a potential crash-bug on first enabling either once the audio or 
MIDI metronomes.


References:

[1]  Qtractor - An audio/MIDI multi-track sequencer
      http://qtractor.sourceforge.net

[2]  Qt framework, C++ class library and tools for
      cross-platform application and UI development
      http://qt.io/

[3]  JACK Audio Connection Kit
      http://jackaudio.org

[4]  ALSA, Advanced Linux Sound Architecture
      http://www.alsa-project.org/

[5]  Linux Audio consortium of libre software for audio-related work
      http://linuxaudio.org

[6]  GPL - GNU General Public License
      http://www.gnu.org/copyleft/gpl.html

[7]  Qtractor Git repository on github.com
      http://github.com/rncbc/qtractor

[8]  Qtractor Git repository on sourceforge.net
      http://git.code.sf.net/p/qtractor/code


See also:
   http://www.rncbc.org/drupal/node/975


Hope you enjoy && have fun.
-- 
rncbc aka. Rui Nuno Capela

Re: [Qtractor-devel] Happy Bunny :)

[Rui N. C. <rn...@rn...>]

On 2015-12-10 20:53, Will Godfrey wrote:
> Just tried the latest Qtractor with Yoshimi as an LV2 plugin.
> 
> All works very smoothly, and when running a fairly complex composition, 
> Qjackctl
> is reporting just about the same DSP load as feeding MIDI direct to 
> Yoshimi via
> aplaymidi.

thanks Will.

btw. as LV2, have you tried to render to audio (menu Track/Export 
Tracks.../Audio) ?


cheers
-- 
rncbc aka. Rui Nuno Capela

[Qtractor-devel] Happy Bunny :)

[Will G. <wil...@mu...>]

Just tried the latest Qtractor with Yoshimi as an LV2 plugin.

All works very smoothly, and when running a fairly complex composition, Qjackctl
is reporting just about the same DSP load as feeding MIDI direct to Yoshimi via
aplaymidi.

-- 
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.

[Qtractor-devel] [ANN] Qtractor 0.7.1 - The Meson Dope beta release

[Rui N. C. <rn...@rn...>]

   Hey,

   Here's to all southerners for whom the so called Summer'15 didn't 
made much sense...

   Beg your pardon yet and again, but it's that time of year when 
grapefruit is about ripening, pretty fast and maybe late, at least on 
the northern hemisphere. No worries: harvesting has already been carried 
away. So it's your call now, wether it makes for ugly bad wine or, 
pretty good vinegar...

   "Quickly, bring me a beaker of wine so that I may wet my mind and say 
something clever." --Aristophanes

never mind,

   Qtractor 0.7.1 (meson dope beta) is released!

   Now, for the clueless:

   Qtractor [1] is an audio/MIDI multi-track sequencer application 
written in C++ with the Qt framework [2]. Target platform is Linux, 
where the Jack Audio Connection Kit (JACK [3]) for audio and the 
Advanced Linux Sound Architecture (ALSA [4]) for MIDI are the main 
infrastructures to evolve as a fairly-featured Linux desktop audio 
workstation GUI, specially dedicated to the personal home-studio.

   And for the ones who can aptly tell a TL;DR apart from a hangover:

   Besides the incidental bug-fixes and proverbial business-as-usual 
stance for this dot release, the most probable and hopefully significant 
news about it, is that this will the last to build against Qt4 by 
default. The time has come to move on up to Qt5. Remember that a Qt5 
build is and has been possible already for ages now but somewhat 
relegated on a subpar status due to the once lack of support for all 
non-Qt5 LV2 plug-ins GUIs out there. Not anymore! Starting from this 
very release onwards there's this so called <em>native</em> LV2 GTK2 and 
X11 UI support on Qt5. Also thriving, drobilla's libsuil is being 
updated to par just that as well. So things are all aligning up nigh.

   A special note to the voluntary packager: if you choose, for any 
reason you may find commendable, to build, package and distribute a Qt5 
build (via ./configure --enable-qt5 ...) please be sure that every LV2 
plug-ins around that take Qt as its UI framework are also build, 
packaged and distributed on the same premises, otherwise they might just 
fail and crash Qtractor [1] on show. Among those are of course the one 
comprised by the 'Vee One Suite', namely synthv1 [9], samplv1 [10] and 
drumkv1 [11], of course.

   Also as a(nother) side note: It has been for quite some time there's 
an alternate github.com [7] repository which is kept in sync with the 
sf.net one [8]. However, this doesn't mean that the Qtractor [1] project 
is about to migrate to brand new hosting whatsoever: the original 
upstream source code repository is, will be, as ever was, always kept 
somewhere else still in this world and universe. It's a Git [12] world 
out nowadays and as the mottos says, --everything-is-local, 
--distributed-is-the-new-centralized ;)

Enjoy.


Website:
   http://qtractor.sourceforge.net

Project page:
   http://sourceforge.net/projects/qtractor

Downloads:
   http://sourceforge.net/projects/qtractor/files

- source tarball:
   http://www.rncbc.org/archive/qtractor-0.7.1.tar.gz

- source package (openSUSE 13.2):
   http://www.rncbc.org/archive/qtractor-0.7.1-19.rncbc.suse132.src.rpm

- binary packages (openSUSE 13.2):
   http://www.rncbc.org/archive/qtractor-0.7.1-19.rncbc.suse132.i586.rpm
   http://www.rncbc.org/archive/qtractor-0.7.1-19.rncbc.suse132.x86_84.rpm

- wiki (help wanted!):
   http://sourceforge.net/p/qtractor/wiki/

Weblog (upstream support):
   http://www.rncbc.org

License:
   Qtractor [1] is free, open-source Linux Audio [5] software, 
distributed under the terms of the GNU General Public License (GPL [6]) 
version 2 or later.

Change-log:
...

References:

[1]  Qtractor - An audio/MIDI multi-track sequencer
      http://qtractor.sourceforge.net

[2]  Qt framework, C++ class library and tools for
      cross-platform application and UI development
      http://qt.io/

[3]  JACK Audio Connection Kit
      http://jackaudio.org

[4]  ALSA, Advanced Linux Sound Architecture
      http://www.alsa-project.org/

[5]  Linux Audio consortium of libre software for audio-related work
      http://linuxaudio.org

[6]  GPL - GNU General Public License
      http://www.gnu.org/copyleft/gpl.html

[7]  Qtractor Git repository on github.com
      http://github.com/rncbc/qtractor

[8]  Qtractor Git repository on sourceforge.net
      http://git.code.sf.net/p/qtractor/code

[9]  synthv1 - an old-school polyphonic synthesizer
      http://synthv1.sourceforge.net/

[10] samplv1 - an old-school polyphonic sampler
      http://samplv1.sourceforge.net/

[11] drumkv1 - an old-school drum-kit sampler
      http://drumkv1.sourceforge.net/

[12] Git distributed version control system
      http://git-scm.com


See also:
   http://www.rncbc.org/drupal/node/960


Enjoy && have fun.
-- 
rncbc aka. Rui Nuno Capela

Re: [Qtractor-devel] NoteOffs don't get sent on additional MIDI channels?

[Frank N. <bea...@we...>]

Hi Rui,

[..]

> > Rui, this looks like a bug, right? Or can I somehow adjust that 
> > behaviour
> > "per bus"?
> > 

> it is/was a very old "bug/feature" indeed...
> 
> it dealt with not setting an MIDI track's instrument name 
> properly--leaving it at "(No instrument)" was the culprit ever since... 
> ever?
> 
> i even remember you asked something about this back in the days, some 
> 8years+ ago, for which i replied that the all-shut-up messages were only 
> sent iif there was an instrument defined on the track/channel...
> 
> nevermind, it's hopefully fixed on git head (master) now aka. 
> qtractor-0.7.0.33+
>    http://sourceforge.net/p/qtractor/code/ci/ed2f56
>    http://github.com/rncbc/qtractor/commit/ed2f561

Great :-). Confirmed, looking good now. At least in my little example
setup with 2 MIDI busses, no more stuck notes are heard upon playback
stop. BLB++ ;-).

Greetings,
Frank

Re: [Qtractor-devel] NoteOffs don't get sent on additional MIDI channels?

[Rui N. C. <rn...@rn...>]

On 2015-10-04 10:59, Frank Neumann wrote:
> Hi list,
> 
> not sure if this is intended behaviour or a bug, so I am asking this
> here first -
> 
> I created a small "song" with 2 MIDI tracks.
> The first tracks plays out to "Master MIDI", the second is using an 
> additional
> MIDI bus ("Supernova") I have created via the "View->Buses" dialog.
> 
> Both tracks have a small MIDI clip, both play out fine. However, when I 
> stop
> playback via the <space bar> key, the notes played on the second track 
> don't
> get stopped.
> 
> I see from the "aseqdump" output that the respective messages do not 
> get sent
> when I stop playback.
> 
> Dumping output on "Master MIDI" bus:
> [playback is running]
> ...
> 130:0   Note on                 0, note 62, velocity 23
> 130:0   Note on                 0, note 67, velocity 23
> 130:0   Note on                 0, note 71, velocity 23
> [pressing space bar here]
> 130:0   Control change          0, controller 120, value 0   (All Sound 
> Off)
> 130:0   Control change          0, controller 123, value 0   (All Notes 
> Off)
> 130:0   Control change          0, controller 121, value 0   (Reset
> All Controllers)
> 
> -> All sounds are off
> 
> Dumping output on "Supernova" bus:
> [playback is running]
> ...
> 130:1   Note on                 0, note 50, velocity 64
> 130:1   Note off                0, note 50, velocity 0
> 130:1   Note on                 0, note 55, velocity 64
> 130:1   Note off                0, note 55, velocity 0
> 130:1   Note on                 0, note 43, velocity 64
> 130:1   Note off                0, note 43, velocity 0
> 130:1   Note on                 0, note 50, velocity 64
> [pressing space bar here]
> [no additional MIDI output here, but "stuck" notes are still being 
> heard]
> 
> Only when I press the "Panic" button, I see the expected:
> 130:1   Control change          0, controller 120, value 0
> 130:1   Control change          0, controller 123, value 0
> 130:1   Control change          0, controller 121, value 0
> 
> Rui, this looks like a bug, right? Or can I somehow adjust that 
> behaviour
> "per bus"?
> 

hi

it is/was a very old "bug/feature" indeed...

it dealt with not setting an MIDI track's instrument name 
properly--leaving it at "(No instrument)" was the culprit ever since... 
ever?

i even remember you asked something about this back in the days, some 
8years+ ago, for which i replied that the all-shut-up messages were only 
sent iif there was an instrument defined on the track/channel...

nevermind, it's hopefully fixed on git head (master) now aka. 
qtractor-0.7.0.33+
   http://sourceforge.net/p/qtractor/code/ci/ed2f56
   http://github.com/rncbc/qtractor/commit/ed2f561

byee
-- 
rncbc aka. Rui Nuno Capela

Re: [Qtractor-devel] NoteOffs don't get sent on additional MIDI channels?

[Rui N. C. <rn...@rn...>]

On 10/04/2015 12:19 PM, Rui Nuno Capela wrote:
>
> On 10/04/2015 12:17 PM, Rui Nuno Capela wrote:
>>> ...
>>> Rui, this looks like a bug, right? Or can I somehow adjust that behaviour
>>> "per bus"?
>>>
>>
>> yes, you're probably right, the three CC's 120, 123 and 121 should have
>> been qlwo sent to 2nd bus (Supernova; port 130:1) when playback stops,
>          ^^^^
>          also
>> not only when you hit "panic"!
>>

hi Frank,

i'm not seeing to reproduce this behavior:

a) stopping playback does send CC#120 (all sound off) and CC#123 (all 
notes off) on all playing MIDI output buses from their respective MIDI 
track/channels.

b) panic does the same as a), with an additional CC#121 (all controllers 
off) being sent as well.

is there anything i'm missing?

cheers
-- 
rncbc aka. Rui Nuno Capela

Re: [Qtractor-devel] NoteOffs don't get sent on additional MIDI channels?

[Rui N. C. <rn...@rn...>]

On 10/04/2015 12:17 PM, Rui Nuno Capela wrote:
>> ...
>> Rui, this looks like a bug, right? Or can I somehow adjust that behaviour
>> "per bus"?
>>
>
> yes, you're probably right, the three CC's 120, 123 and 121 should have
> been qlwo sent to 2nd bus (Supernova; port 130:1) when playback stops,
        ^^^^
        also
> not only when you hit "panic"!
>
-- 
rncbc aka. Rui Nuno Capela

Re: [Qtractor-devel] NoteOffs don't get sent on additional MIDI channels?

[Rui N. C. <rn...@rn...>]

hi Frank,

On 10/04/2015 10:59 AM, Frank Neumann wrote:
>
> Dumping output on "Supernova" bus:
> [playback is running]
> ...
> 130:1   Note on                 0, note 50, velocity 64
> 130:1   Note off                0, note 50, velocity 0
> 130:1   Note on                 0, note 55, velocity 64
> 130:1   Note off                0, note 55, velocity 0
> 130:1   Note on                 0, note 43, velocity 64
> 130:1   Note off                0, note 43, velocity 0
> 130:1   Note on                 0, note 50, velocity 64
> [pressing space bar here]
> [no additional MIDI output here, but "stuck" notes are still being heard]
>
> Only when I press the "Panic" button, I see the expected:
> 130:1   Control change          0, controller 120, value 0
> 130:1   Control change          0, controller 123, value 0
> 130:1   Control change          0, controller 121, value 0
>
> Rui, this looks like a bug, right? Or can I somehow adjust that behaviour
> "per bus"?
>

yes, you're probably right, the three CC's 120, 123 and 121 should have 
been qlwo sent to 2nd bus (Supernova; port 130:1) when playback stops, 
not only when you hit "panic"!

i'll have to confirm this

bbl.
cheers
--

rncbc aka. Rui Nuno Capela