qtractor-devel — Qtractor development discussion

Re: [Qtractor-devel] {SPAM 01.7} Re: Strange behaviour of tempo changes

[David S. <da...@ae...>]

On Wed, 2017-01-04 at 15:06 +0000, Rui Nuno Capela wrote:
> David.
> 
> sorry to tell but all tempo and time-signature changes, as well
> location 
> markers, are always quantized into the nearest bar/measure locations.
> 
> this is not a bug--it's working as (long ago) designed--a law deeply 
> engraved in old qtractor's stone.
> 
> cheers

Thanks for that information.  This means that any midi track with tempo
changes that are not at a bar line will have their timing distorted -
and Qtractor is therefore not usable for them.

Perhaps there are certain types of music where tempo changes only
happen at barlines, but why does it need to be enforced by the program?
- especially when the Tempo Change/Marker window strongly implies that
any position within 1/1000 of a beat can be chosen.

David

Re: [Qtractor-devel] Strange behaviour of tempo changes

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

David.

sorry to tell but all tempo and time-signature changes, as well location 
markers, are always quantized into the nearest bar/measure locations.

this is not a bug--it's working as (long ago) designed--a law deeply 
engraved in old qtractor's stone.

cheers
-- 
rncbc aka. Rui Nuno Capela

[Qtractor-devel] Strange behaviour of tempo changes

[David S. <da...@ae...>]

Although the Tempo Map/Markers window in Qtractor shows the position of
markers with an accuracy of 1/1000 of a beat, it seems that Qtractor
actually only permits tempo changes and markers to occur at beat 1.000
of a bar.  If any other position is specified, I find that the change
is placed at the start of the following bar.

For the type of thing I want to do this probably isn't too much of a
problem if I am recording new material.  But if I import midi tracks it
disastrously distorts the timing of the music, because in fact
Qtractor's behaviour is even more bizarre than what I have already
described.

Here is an illustration of the sort of thing that happens.  I have a
midi file of a saxophone quartet.  The original midi file was generated
by Lilypond.  The file was then converted to csv using midicsv, edited
to produce some needed tempo changes, ritardandos etc., and then
converted back to midi using csvmidi.

The file plays well in timidity, and I was able to generate an
acceptable mp3 from it.

But if I import the file (or one of its 4 tracks) into Qtractor the
tempo map and therefore the performance is complete nonsense.  Some
tempo changes are ignored and the rest are all placed on the first beat
of a bar.  But things are much worse still, because in most cases the
actual bar in which Qtractor puts a tempo change is the wrong one by
quite a large margin.

The first 10 lines of the tempo map as shown by Qtractor are these:

Bar  Time    Tempo Marker
  1  1.1.000 104.0 4/4
  2  2.1.000  77.0 4/4
  3  3.1.000 104.0 4/4
  6  6.1.000 109.0 4/4
  7  7.1.000 134.0 4/4
  8  8.1.000 159.0 4/4
  9  9.1.000 189.0 4/4
 10 10.1.000 200.0 4/4
 11 11.1.000 104.0 4/4
 20 20.1.000  84.0 4/4

If Qtractor were reading the files correctly, they should look like
this:

Bar  Time    Tempo Marker
  1  1.1.000 104.0 4/4
  4  4.1.000  95.0 4/4
  4  4.2.000  86.0 4/4
  4  4.3.000  77.0 4/4
  5  5.1.000 104.0 4/4
 13 13.1.000  97.0 4/4
 13 13.2.000  90.0 4/4
 13 13.3.000  83.0 4/4
 13 13.4.500 104.0 4/4
 14 14.2.000 109.0 4/4

Even if Qtractor does not like so many tempo changes in one bar, I
cannot see why it puts, for instance, the tempo change which should
happen at bar 14 at the start of bar 6.  The tempo change Qtractor
shows for bar 20 should actually occur in bar 50!

The fact that the tempo map quotes "Time" to 3 decimal places of a beat
suggests that Qtractor ought to accept a change at any time.  Perhaps
the design of the tempo map window is ahead of the current capabilities
of the program?

I emphasize that timidity reads this file perfectly satisfactorily and
responds to all the tempo changes correctly.

This appears to me to be a major bug, but perhaps it is just a by-
product of some other feature of the program.  In any case, is this
behaviour likely to be changed in the near future?

David

[Qtractor-devel] Fwd: [LAD] LAC2017: Call for Papers / Posters / Workshops / Speed Geeking / Music / Multimedia Installations

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

Please forward to anyone who might be interested! Sorry for cross-posting.

====== Apologies if you receive multiple copies of this document =========

LAC2017: Call for Papers / Posters / Workshops / Speed Geeking / Music /
Multimedia Installations

Name: LINUX AUDIO CONFERENCE 2017 (LAC2017)
URL: https://lac2017.univ-st-etienne.fr/
Dates: May 18-21, 2017
Location: Saint-Etienne University, FRANCE

======== LAC 2017 – Linux Audio Conference ========
Jean Monnet University - Saint-Etienne / 18-21 May, 2017

1.Call for Papers / Posters / Workshops/ Speed Geeking
2.Call for Music / Multimedia Installations

==  1. Call for Papers / Posters / Workshops / Speed Geeking ==
Deadline for submission: Friday, February 10, 2017 (23:59 UTC)
Online (only) submission on https://lac2017.sciencesconf.org/

LAC2017 invites submissions of papers, posters and workshops addressing all
areas of audio processing based on Linux and open source software. All
submissions and presentations are in English. Submissions can focus on
technical, artistic or scientific issues and can target developers or
users. This includes (but is not limited to) the following categories:

Audio and Music Languages
Audio Hardware Support
Audio Plugins
Realtime Kernel and Linux Distributions
Drivers, System and Sound Architecture
Education and E-Learning
Games
Interactive Art
Interface Design
Live Coding
Live Performance
Media Art
MIDI,OSC...
Mobile Audio
Music Production
Music Production Tools
Networked Audio
Physical Computing
Projects Realized using Linux Audio
Signal Processing and Sound Synthesis
Sound Spatialisation
Standards and Protocols
Video
. . .

== PAPERS ==
Papers should be written and presented in English. The length of the talks
is 25 minutes followed by 5 minutes discussion.
The length of the paper is 4 to 8 pages, with up to 5 keywords, and an
abstract of 50 to 100 words. The abstract will be published on the
conference website once the paper has been accepted. The full paper will be
available on the website during and after the conference.
All papers are peer reviewed by a committee of experts from different
disciplines. The reviewers may suggest improvements to the author(s), or
require changes in order to accept the submission.
The duration of the presentation is 25 minutes followed by 5 minutes
discussion.

== POSTERS ==
The poster presentation should be 1 page, with up to 5 keywords and an
abstract of 30 to 60 words. The abstract will be published on the
conference website once the poster has been accepted.
All posters are peer reviewed by a committee of experts in different
disciplines. The reviewers may suggest improvements to the author(s), or
require changes in order for the poster to be accepted.

== WORKSHOPS ==
The workshop presentation (max duration of 2h) should be 1 page, with up to
5 keywords, and an abstract of 30 to 60 words to be published on the
conference website.
Submit a brief description of the workshop including URL (if available).

== SPEED GEEKING ==
This new session aims to create links and collaborations between developers.
Are you running an open source project? Come and tell the community in 3mn
and 1 slide on your project and share your experience.
You start a new project, come and explain your projects in 3 min. and 1
slide and recruit developers.
Are you a developer eager to participate in an exciting open source
project? Come and follow the SpeedGeeking session to discover the
project(s) in which you want to invest your time.
Submit a brief description of the project including URL (if available), and
one presentation slide.

== How to submit? ==
•       The deadline for papers, posters, workshops and speed geeking
submission is Friday, February 10, 2017, 23:59 UTC.
•       Do not send proposal via email instead please use the paper upload
form in our conference management system.
•       The required file format is PDF, formatted for A4 paper. Authors
should use the templates for paper formatting available on the download
page of the conference website.
•       Authors of papers selected to be included in the printed conference
proceedings may also have to supply supplemental material like
illustrations needed to layout the printed proceedings separately.

Please notify us if you need a special technical setup for your
presentation. The standard setup will be:
•       microphone or head set
•       projector with XVGA input (min. resolution 1024 × 768)
•       stereo playback with mini jack input
Also, if you are not able to bring your laptop along with you, please
notify us in advance.

== Important Dates ==
•       Deadline for submissions: February 10, 2017
•       Acceptance notification: March 10, 2017
•       Final deadline for 'camera ready' paper: April 10, 2017
•       Author registration deadline: April 20, 2017
•       Final program: May 1, 2017
•       LAC 2017 conference: May, 18-21, 2017

==  2. Call for Music / Multimedia Installations ==

Deadline for submission: Tuesday, February 10, 2017 (23:59 UTC)
Online (only) submission on https://lac2017.sciencesconf.org/

LAC2017 invites also submissions of Electroacoustic Works and Multimedia
Installation.

A jury will select the compositions and installations to be included in the
conference program according to artistic merit and technical feasibility.
Please be prepared to perform your work yourself and make sure that you
have all resources needed to perform your piece at your disposal (e.g.
instruments, props, other performers, etc.).
Unfortunately, LAC 2017 cannot pay a fee neither for you nor for any
additional performers, and LAC 2017 cannot organize or pay for travel or
accommodation neither of you nor of any additional performers.
Electroacoustic Works and Multimedia Installation can address all areas of
digital audio and audiovisual art. This includes (but is not limited to)
the following categories:
•       Acoustic Music
•       Acousmatic Music
•       Electronic Music
•       Mixed Music
•       Sound installation
•       Interactive art
•       Audiovisual installation
•       Game in art
•       Web and connected art
•       New interfaces
All submissions are peer reviewed by a committee of experts in music and
arts.

== How to submit? ==
•       The deadline for Music and Multimedia Installations submission is
Tuesday, February 10, 2017, 23:59 UTC.
•       Do not send files via email instead please use the file upload form
in our conference management system.
•       The required file format is PDF, formatted for A4 paper. It
includes:
-       registration form available on the download page of the conference
website;
-       technical rider of the work;
-       video or audio link to the project;
-       an artbook.
Important Dates
•       Deadline for submissions: February 10, 2017
•       Acceptance notification: March 10, 2017
•       Artist and Musician registration deadline: April 20, 2017
•       Final program: May 1, 2017
•       LAC 2017 conference: May, 18-21, 2017

Please visit conference website: https://lac2017.univ-st-etienne.fr/, for
details.

We are sure that you will have a wonderful experience of visiting
Saint-Etienne during the LAC 2017.

We look forward to welcoming you in FRANCE in 2017!

Laurent Pottier

-------------------------------

Email: la...@li...
WWW: https://lac2017.univ-st-etienne.fr/


--
********************************************
Université Jean Monnet
CIEREC - EA3068
35, rue du 11 novembre
42023 Saint-Etienne Cedex 02 - France
port. : +33(0)6 21 66 28 76
tel : +33(0)4 77 42 16 61
fax : +33(0)4 77 42 16 84

lau...@un...
********************************************


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

Re: [Qtractor-devel] Can't get more than 1 LinuxSampler track to work in Qtractor SOLVED

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

Hi again,

[..]

> >>> Have I misunderstood something about how tracks and channels of Linuxsampler
> >>> are supposed to work from within Qtractor? Do I need to change something in
> >>> Qsampler before confirming the properties of a new channel?
> >>>
> >>
> >> you probably missed the little secret part that MIDI channel numbers
> >> must match each other, between qtractor MIDI tracks and corresponding
> >> linuxsampler sampler channels.
> >>
> >> from the above you say nothing about which MIDI channel you set up the
> >> second linuxsampler channel, which by default gets to MIDI channel 1
> >> while a second MIDI track in qtractor, most probably, gets to number 2.
> > 
> > Oops, sorry for not stating that info. Yes, you are right, I used the "default"
> > in LinuxSampler/qsampler which is channel 1. However, even if I change it to the
> > same channel number (2 in this case) of the corresponding Qtractor track, the error
> > is still there:
> > 
> > 22:21:46.876 Channel 1 setup...
> > 22:22:21.677 Channel 1 lscp_set_channel_audio_device: The audio output device 'Plugin' cannot be dropped from this sampler channel! (errno=100)
> > 22:22:21.682 Channel 1 lscp_set_channel_midi_device: The MIDI input port 'Plugin' cannot be altered on this sampler channel! (errno=100)
> > 22:22:21.686 Channel 1 MIDI port: 0.
> > 22:22:21.688 Channel 1 MIDI channel: 1.
> > 22:22:21.746 Channel 1 Engine: SFZ.
> > 
> > What's a little irritating is that above it still says "MIDI channel: 1." but I
> > guess Qsampler/LinuxSampler is starting to count from 0 since channel 3 would
> > appear as "2" there.
> > 
> > However, still no luck so far :-\. Does this kind of setup work for you?
> > 
> 
> yes, it works, and sounds, as advertised, despite the same "error"
> messages as yours
> 
> i'm out of ideas now

Hm..."oops". Actually, it works for me as well, but the error messages were so
intimidating that I didn't even dare to test whether it actually works :-).
Seems then that the wrong MIDI channel in QSampler was my only problem.

So, yes, I can now create 2, 3, 4 tracks in Qtractor and corresponding channels
in QSampler, all loaded with different .sfz instrument files, and it works just
fine, as expected. Thanks, this makes me a good deal happier! :-)

Of course, the next natural question is then why we see those really
irritating error messages - are Qtractor/Qsampler and LinuxSampler not speaking
the same protocol/version? I mean, this is "as unintuitive as it can get"; please
don't say now "works as expected", ok? :-)

Greetings,
Frank

Re: [Qtractor-devel] Can't get more than 1 LinuxSampler track to work in Qtractor

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

On 12/12/2016 09:26 PM, Frank Neumann wrote:
> 
> Hi Rui and all,
> 
>>> not sure who is at fault here (likely me :-), but maybe some from the Qtractor
>>> community can help..I am trying to set up a simple session with Qtractor and
>>> LinuxSampler: 2 MIDI tracks, each holding an instance of LinuxSampler (LV2) as a
>>> plugin. When I attempt to load an .sfz file into the 2nd instance, I get an error message:
>>>
>>> The audio output device 'Plugin' cannot be dropped from this sampler channel!
>>> The MIDI input port 'Plugin' cannot be altered on this sampler channel!
>>>
>>> Let me describe what I am doing, step by step:
>>>
>>> - Start QJackctl, start JACK, start Qtractor
>>> - Qtractor: Create new track, type MIDI, add plugin -> LV2 -> LinuxSampler, confirm with ok
>>> - Start QSampler, click on that track, "Setup channel", select SFZ engine and some .sfz file, confirm with ok
>>>   MIDI Input Type is "Plugin", Device: MIDI Plugin Device 0
>>>   Audio Output Type is "Plugin", Device: Audio Plugin Device 0
>>> - Qtractor: Connect MIDI keyboard to Qtractor, play into that track 
>>>
>>> = all fine so far =
>>>
>>> - Qtractor: Create another track, again type MIDI, add plugin -> LV2 -> LinuxSampler, confirm with ok
>>> - In QSampler, click on that track, "Setup channel", select SFZ engine and some other .sfz file, confirm with ok
>>>   -> at this point QSampler says "Channel 1  Some channel settings could not be set.  Sorry."
>>>      and in Qtractor's console I see:
>>>      Starting disk thread...OK
>>>      EQ support: no
>>>      Stopping disk thread...OK
>>>      Starting disk thread...OK
>>>      EQ support: no
>>>      The audio output device 'Plugin' cannot be dropped from this sampler channel!
>>>      The MIDI input port 'Plugin' cannot be altered on this sampler channel!
>>>
>>>      though it then continues to say:
>>>      ...
>>>      Instantiating LADSPA effect 'triplePara'.
>>>      LADSPA effect 'triplePara' activated.
>>>      Scheduling '/tmp/x/wa_synth_drums/drum kits/sfz/z_all percussion dissonant hits.sfz' (Index=0) to be loaded in background (if not loaded yet).
>>>      Loading sfz file '/tmp/x/wa_synth_drums/drum kits/sfz/z_all percussion dissonant hits.sfz'...OK
>>>      Loading sfz instrument ('/tmp/x/wa_synth_drums/drum kits/sfz/z_all percussion dissonant hits.sfz',0)...OK
>>>      Caching initial samples...OK
>>>
>>> Net effect is still that on this new track no audio is being played out. The
>>> first track continues to work fine.
>>>
>>> Used versions:
>>> - Qtractor 0.8.0 (built from Git on Dec 6th)
>>> - libgig, liblscp, linuxsampler, qsampler built from today's svn state
>>>
>>> Have I misunderstood something about how tracks and channels of Linuxsampler
>>> are supposed to work from within Qtractor? Do I need to change something in
>>> Qsampler before confirming the properties of a new channel?
>>>
>>
>> you probably missed the little secret part that MIDI channel numbers
>> must match each other, between qtractor MIDI tracks and corresponding
>> linuxsampler sampler channels.
>>
>> from the above you say nothing about which MIDI channel you set up the
>> second linuxsampler channel, which by default gets to MIDI channel 1
>> while a second MIDI track in qtractor, most probably, gets to number 2.
> 
> Oops, sorry for not stating that info. Yes, you are right, I used the "default"
> in LinuxSampler/qsampler which is channel 1. However, even if I change it to the
> same channel number (2 in this case) of the corresponding Qtractor track, the error
> is still there:
> 
> 22:21:46.876 Channel 1 setup...
> 22:22:21.677 Channel 1 lscp_set_channel_audio_device: The audio output device 'Plugin' cannot be dropped from this sampler channel! (errno=100)
> 22:22:21.682 Channel 1 lscp_set_channel_midi_device: The MIDI input port 'Plugin' cannot be altered on this sampler channel! (errno=100)
> 22:22:21.686 Channel 1 MIDI port: 0.
> 22:22:21.688 Channel 1 MIDI channel: 1.
> 22:22:21.746 Channel 1 Engine: SFZ.
> 
> What's a little irritating is that above it still says "MIDI channel: 1." but I
> guess Qsampler/LinuxSampler is starting to count from 0 since channel 3 would
> appear as "2" there.
> 
> However, still no luck so far :-\. Does this kind of setup work for you?
> 

yes, it works, and sounds, as advertised, despite the same "error"
messages as yours

i'm out of ideas now

byee
-- 
rncbc aka. Rui Nuno Capela
rn...@rn...



-- 
rncbc aka. Rui Nuno Capela
rn...@rn...

Re: [Qtractor-devel] Can't get more than 1 LinuxSampler track to work in Qtractor

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

Hi Rui and all,

> > not sure who is at fault here (likely me :-), but maybe some from the Qtractor
> > community can help..I am trying to set up a simple session with Qtractor and
> > LinuxSampler: 2 MIDI tracks, each holding an instance of LinuxSampler (LV2) as a
> > plugin. When I attempt to load an .sfz file into the 2nd instance, I get an error message:
> > 
> > The audio output device 'Plugin' cannot be dropped from this sampler channel!
> > The MIDI input port 'Plugin' cannot be altered on this sampler channel!
> > 
> > Let me describe what I am doing, step by step:
> > 
> > - Start QJackctl, start JACK, start Qtractor
> > - Qtractor: Create new track, type MIDI, add plugin -> LV2 -> LinuxSampler, confirm with ok
> > - Start QSampler, click on that track, "Setup channel", select SFZ engine and some .sfz file, confirm with ok
> >   MIDI Input Type is "Plugin", Device: MIDI Plugin Device 0
> >   Audio Output Type is "Plugin", Device: Audio Plugin Device 0
> > - Qtractor: Connect MIDI keyboard to Qtractor, play into that track 
> > 
> > = all fine so far =
> > 
> > - Qtractor: Create another track, again type MIDI, add plugin -> LV2 -> LinuxSampler, confirm with ok
> > - In QSampler, click on that track, "Setup channel", select SFZ engine and some other .sfz file, confirm with ok
> >   -> at this point QSampler says "Channel 1  Some channel settings could not be set.  Sorry."
> >      and in Qtractor's console I see:
> >      Starting disk thread...OK
> >      EQ support: no
> >      Stopping disk thread...OK
> >      Starting disk thread...OK
> >      EQ support: no
> >      The audio output device 'Plugin' cannot be dropped from this sampler channel!
> >      The MIDI input port 'Plugin' cannot be altered on this sampler channel!
> > 
> >      though it then continues to say:
> >      ...
> >      Instantiating LADSPA effect 'triplePara'.
> >      LADSPA effect 'triplePara' activated.
> >      Scheduling '/tmp/x/wa_synth_drums/drum kits/sfz/z_all percussion dissonant hits.sfz' (Index=0) to be loaded in background (if not loaded yet).
> >      Loading sfz file '/tmp/x/wa_synth_drums/drum kits/sfz/z_all percussion dissonant hits.sfz'...OK
> >      Loading sfz instrument ('/tmp/x/wa_synth_drums/drum kits/sfz/z_all percussion dissonant hits.sfz',0)...OK
> >      Caching initial samples...OK
> > 
> > Net effect is still that on this new track no audio is being played out. The
> > first track continues to work fine.
> > 
> > Used versions:
> > - Qtractor 0.8.0 (built from Git on Dec 6th)
> > - libgig, liblscp, linuxsampler, qsampler built from today's svn state
> > 
> > Have I misunderstood something about how tracks and channels of Linuxsampler
> > are supposed to work from within Qtractor? Do I need to change something in
> > Qsampler before confirming the properties of a new channel?
> > 
> 
> you probably missed the little secret part that MIDI channel numbers
> must match each other, between qtractor MIDI tracks and corresponding
> linuxsampler sampler channels.
> 
> from the above you say nothing about which MIDI channel you set up the
> second linuxsampler channel, which by default gets to MIDI channel 1
> while a second MIDI track in qtractor, most probably, gets to number 2.

Oops, sorry for not stating that info. Yes, you are right, I used the "default"
in LinuxSampler/qsampler which is channel 1. However, even if I change it to the
same channel number (2 in this case) of the corresponding Qtractor track, the error
is still there:

22:21:46.876 Channel 1 setup...
22:22:21.677 Channel 1 lscp_set_channel_audio_device: The audio output device 'Plugin' cannot be dropped from this sampler channel! (errno=100)
22:22:21.682 Channel 1 lscp_set_channel_midi_device: The MIDI input port 'Plugin' cannot be altered on this sampler channel! (errno=100)
22:22:21.686 Channel 1 MIDI port: 0.
22:22:21.688 Channel 1 MIDI channel: 1.
22:22:21.746 Channel 1 Engine: SFZ.

What's a little irritating is that above it still says "MIDI channel: 1." but I
guess Qsampler/LinuxSampler is starting to count from 0 since channel 3 would
appear as "2" there.

However, still no luck so far :-\. Does this kind of setup work for you?

Thanks,
Frank

Re: [Qtractor-devel] Can't get more than 1 LinuxSampler track to work in Qtractor

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

hi Frank,

On 12/11/2016 10:08 PM, Frank Neumann wrote:
> 
> Hi Rui&all,
> 
> not sure who is at fault here (likely me :-), but maybe some from the Qtractor
> community can help..I am trying to set up a simple session with Qtractor and
> LinuxSampler: 2 MIDI tracks, each holding an instance of LinuxSampler (LV2) as a
> plugin. When I attempt to load an .sfz file into the 2nd instance, I get an error message:
> 
> The audio output device 'Plugin' cannot be dropped from this sampler channel!
> The MIDI input port 'Plugin' cannot be altered on this sampler channel!
> 
> Let me describe what I am doing, step by step:
> 
> - Start QJackctl, start JACK, start Qtractor
> - Qtractor: Create new track, type MIDI, add plugin -> LV2 -> LinuxSampler, confirm with ok
> - Start QSampler, click on that track, "Setup channel", select SFZ engine and some .sfz file, confirm with ok
>   MIDI Input Type is "Plugin", Device: MIDI Plugin Device 0
>   Audio Output Type is "Plugin", Device: Audio Plugin Device 0
> - Qtractor: Connect MIDI keyboard to Qtractor, play into that track 
> 
> = all fine so far =
> 
> - Qtractor: Create another track, again type MIDI, add plugin -> LV2 -> LinuxSampler, confirm with ok
> - In QSampler, click on that track, "Setup channel", select SFZ engine and some other .sfz file, confirm with ok
>   -> at this point QSampler says "Channel 1  Some channel settings could not be set.  Sorry."
>      and in Qtractor's console I see:
>      Starting disk thread...OK
>      EQ support: no
>      Stopping disk thread...OK
>      Starting disk thread...OK
>      EQ support: no
>      The audio output device 'Plugin' cannot be dropped from this sampler channel!
>      The MIDI input port 'Plugin' cannot be altered on this sampler channel!
> 
>      though it then continues to say:
>      ...
>      Instantiating LADSPA effect 'triplePara'.
>      LADSPA effect 'triplePara' activated.
>      Scheduling '/tmp/x/wa_synth_drums/drum kits/sfz/z_all percussion dissonant hits.sfz' (Index=0) to be loaded in background (if not loaded yet).
>      Loading sfz file '/tmp/x/wa_synth_drums/drum kits/sfz/z_all percussion dissonant hits.sfz'...OK
>      Loading sfz instrument ('/tmp/x/wa_synth_drums/drum kits/sfz/z_all percussion dissonant hits.sfz',0)...OK
>      Caching initial samples...OK
> 
> Net effect is still that on this new track no audio is being played out. The
> first track continues to work fine.
> 
> Used versions:
> - Qtractor 0.8.0 (built from Git on Dec 6th)
> - libgig, liblscp, linuxsampler, qsampler built from today's svn state
> 
> Have I misunderstood something about how tracks and channels of Linuxsampler
> are supposed to work from within Qtractor? Do I need to change something in
> Qsampler before confirming the properties of a new channel?
> 

you probably missed the little secret part that MIDI channel numbers
must match each other, between qtractor MIDI tracks and corresponding
linuxsampler sampler channels.

from the above you say nothing about which MIDI channel you set up the
second linuxsampler channel, which by default gets to MIDI channel 1
while a second MIDI track in qtractor, most probably, gets to number 2.

just saying
cheers
-- 
rncbc aka. Rui Nuno Capela
rn...@rn...

[Qtractor-devel] Can't get more than 1 LinuxSampler track to work in Qtractor

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

Hi Rui&all,

not sure who is at fault here (likely me :-), but maybe some from the Qtractor
community can help..I am trying to set up a simple session with Qtractor and
LinuxSampler: 2 MIDI tracks, each holding an instance of LinuxSampler (LV2) as a
plugin. When I attempt to load an .sfz file into the 2nd instance, I get an error message:

The audio output device 'Plugin' cannot be dropped from this sampler channel!
The MIDI input port 'Plugin' cannot be altered on this sampler channel!

Let me describe what I am doing, step by step:

- Start QJackctl, start JACK, start Qtractor
- Qtractor: Create new track, type MIDI, add plugin -> LV2 -> LinuxSampler, confirm with ok
- Start QSampler, click on that track, "Setup channel", select SFZ engine and some .sfz file, confirm with ok
  MIDI Input Type is "Plugin", Device: MIDI Plugin Device 0
  Audio Output Type is "Plugin", Device: Audio Plugin Device 0
- Qtractor: Connect MIDI keyboard to Qtractor, play into that track 

= all fine so far =

- Qtractor: Create another track, again type MIDI, add plugin -> LV2 -> LinuxSampler, confirm with ok
- In QSampler, click on that track, "Setup channel", select SFZ engine and some other .sfz file, confirm with ok
  -> at this point QSampler says "Channel 1  Some channel settings could not be set.  Sorry."
     and in Qtractor's console I see:
     Starting disk thread...OK
     EQ support: no
     Stopping disk thread...OK
     Starting disk thread...OK
     EQ support: no
     The audio output device 'Plugin' cannot be dropped from this sampler channel!
     The MIDI input port 'Plugin' cannot be altered on this sampler channel!

     though it then continues to say:
     ...
     Instantiating LADSPA effect 'triplePara'.
     LADSPA effect 'triplePara' activated.
     Scheduling '/tmp/x/wa_synth_drums/drum kits/sfz/z_all percussion dissonant hits.sfz' (Index=0) to be loaded in background (if not loaded yet).
     Loading sfz file '/tmp/x/wa_synth_drums/drum kits/sfz/z_all percussion dissonant hits.sfz'...OK
     Loading sfz instrument ('/tmp/x/wa_synth_drums/drum kits/sfz/z_all percussion dissonant hits.sfz',0)...OK
     Caching initial samples...OK

Net effect is still that on this new track no audio is being played out. The
first track continues to work fine.

Used versions:
- Qtractor 0.8.0 (built from Git on Dec 6th)
- libgig, liblscp, linuxsampler, qsampler built from today's svn state

Have I misunderstood something about how tracks and channels of Linuxsampler
are supposed to work from within Qtractor? Do I need to change something in
Qsampler before confirming the properties of a new channel?

Thanks,
Frank

Re: [Qtractor-devel] MIDI file import folder is getting collapsed after every D&D

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

Hi Rui and all,

> > It works better now, but - well, not perfect still. Folders are not
> > collapsed any more after a D&D operation, but what is now awkward
> > is what happens if you add e.g. Track 1 of a MIDI file to one
> > Qtractor track, and attempt to just D&D Track 2 into another 
> > Qtractor track. This doesn't work because the previous track did 
> > not get unselected after the first D&D, so you are now attempting 
> > to D&D 2 tracks at the same time (kind of "multi-select" I guess). 
> > It can worked around by additional clicks to unselect everything, 
> > but that's trading one ugliness for another :-).
> > 
> > That's perhaps the reason why you only commented that one line in 
> > the source code instead of removing it right away. I believe what 
> > should happen here instead of the "QTreeWidget::reset();" is 
> > something like "un-select all items in the widget" (no idea what 
> > that's called in Qt speech).
> > 
> 
> no, not so easy. there's either some idiosyncrasy of QTreeWidget or
> it's me being an idiot :)
> 
> had to take measures and got into a hacky solution in 0.8.0.6git.b304c2
> beware! things might get worse now on some other front...
> i count on you to find them ;)

Aha! Yes, this is much better! And, since the same code is (I guess) used
for both MIDI and audio files, it's fixed for both at the same time :-)
(I remember having seen that issue before, and that was when creating&using
groups of audio files).

Thanks a lot, and "SELB++" if you know what I mean ;-),
Frank

Re: [Qtractor-devel] MIDI file import folder is getting collapsed after every D&D

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 12/05/2016 10:10 PM, Frank Neumann wrote:
> 
> Hi Rui,
> 
>>>> another little ugliness seen today: I import a MIDI file into
>>>> the "Files" window on the right side of the arranger, click
>>>> on the imported file to see its individual tracks ("Track 0",
>>>> "Track 1" and so on), and when I drag&drop a track into a
>>>> qtractor track, the expanded file view is getting collapsed
>>>> again each time so I have to click on it again to see the
>>>> tracks in it. Can this be fixed, please?
>>> 
>>> 
>>> confirmed. a rather "micro-ugliness" should i say :) i'll have 
>>> a look, whenever i get the time.
>>> 
>> 
>> fixed in 0.8.0.5git.c4d31d
> 
> Thanks for this :-). Yes, it is a "micro-ugliness", but many of 
> these combined also contribute to some kind of "uncomfortable" 
> feeling after a while; usability should not be underestimated.
> 
> It works better now, but - well, not perfect still. Folders are not
> collapsed any more after a D&D operation, but what is now awkward
> is what happens if you add e.g. Track 1 of a MIDI file to one
> Qtractor track, and attempt to just D&D Track 2 into another 
> Qtractor track. This doesn't work because the previous track did 
> not get unselected after the first D&D, so you are now attempting 
> to D&D 2 tracks at the same time (kind of "multi-select" I guess). 
> It can worked around by additional clicks to unselect everything, 
> but that's trading one ugliness for another :-).
> 
> That's perhaps the reason why you only commented that one line in 
> the source code instead of removing it right away. I believe what 
> should happen here instead of the "QTreeWidget::reset();" is 
> something like "un-select all items in the widget" (no idea what 
> that's called in Qt speech).
> 

no, not so easy. there's either some idiosyncrasy of QTreeWidget or
it's me being an idiot :)

had to take measures and got into a hacky solution in 0.8.0.6git.b304c2
beware! things might get worse now on some other front...
i count on you to find them ;)

cheers
- -- 
rncbc aka. Rui Nuno Capela
rn...@rn...
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEml2OG8nT8/KXriugSepTUDAa1MgFAlhGB2AACgkQSepTUDAa
1MiLhQgAkJoturTElPFqCMkjlpEpxItPpDhrFgTuHI7l62L1//bTGefQd7G13jLu
v1J9zOzHi6hGfQ9MX+B7nXXjmjNLIsAr68BjwICCv1AzbzXXZ0D+3dM2SBaspq2x
4x9IMrtFGH0wu+mR4c4fIYYxnt0Ob3t90/vmhZ4oqLB1EFeMu+8c3LIupenQ8hCH
WT69NohxcierOlvohp8n0MlpRIy0GvenZlo+GSflVK1Fy1J4v/bpH2hlGhxzaOHy
WoI+XGMFUIzHplBD7tG4QGaH+SOUojYX+ZMm27rVuSs3Cm2G1o1fqATXiaDtRMjc
+7H3ct69bbhxdkymYVO5f/QD1uB40Q==
=RAPo
-----END PGP SIGNATURE-----

Re: [Qtractor-devel] MIDI file import folder is getting collapsed after every D&D

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 12/05/2016 10:10 PM, Frank Neumann wrote:
> 
> Hi Rui,
> 
>>>> another little ugliness seen today: I import a MIDI file
>>>> into the "Files" window on the right side of the arranger,
>>>> click on the imported file to see its individual tracks
>>>> ("Track 0", "Track 1" and so on), and when I drag&drop a
>>>> track into a qtractor track, the expanded file view is
>>>> getting collapsed again each time so I have to click on it
>>>> again to see the tracks in it. Can this be fixed, please?
>>> 
>>> 
>>> confirmed. a rather "micro-ugliness" should i say :) i'll have
>>> a look, whenever i get the time.
>>> 
>> 
>> fixed in 0.8.0.5git.c4d31d
> 
> Thanks for this :-). Yes, it is a "micro-ugliness", but many of
> these combined also contribute to some kind of "uncomfortable"
> feeling after a while; usability should not be underestimated.
> 
> It works better now, but - well, not perfect still. Folders are
> not collapsed any more after a D&D operation, but what is now
> awkward is what happens if you add e.g. Track 1 of a MIDI file to
> one Qtractor track, and attempt to just D&D Track 2 into another
> Qtractor track. This doesn't work because the previous track did
> not get unselected after the first D&D, so you are now attempting
> to D&D 2 tracks at the same time (kind of "multi-select" I guess).
> It can worked around by additional clicks to unselect everything, 
> but that's trading one ugliness for another :-).
> 
> That's perhaps the reason why you only commented that one line in
> the source code instead of removing it right away. I believe what
> should happen here instead of the "QTreeWidget::reset();" is
> something like "un-select all items in the widget" (no idea what
> that's called in Qt speech).
> 

no, bot so easy. there's either some idiosyncrasy of QTreeWidget or
it's me being an idiot :)

had to take measures and got into a hacky solution in 0.8.0.6git.b304c2
beware! things might get worse now on some other front...
i count on you to find them ;)

cheers
- -- 
rncbc aka. Rui Nuno Capela
rn...@rn...
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEml2OG8nT8/KXriugSepTUDAa1MgFAlhGB0QACgkQSepTUDAa
1MiCoAf+Lv9j/4yXTwcBkRdbHjteYYY3RHMYrJdhwZB92OrqEqK/ImPjyNEpSamE
GCpGHjsk3A6tql2KPqiARK1X1sbgGSiiDBuQ/ixK5gisA4bfz29ELuxalqajyWzh
OhYXwPagf8RTYBO/fNzybA2ZGhYYvE213FgfWSu/47BzYXPk4w+VjqU6+IxRE9ji
7m9QBRixW6gOxMAAVimpfy2RiSOK+gaU4BR5gDCwcbWkX0VVsNW893NskeRWHWkr
t5Ud7R/ByUXgaVRiXW5zSIlP2niSySm+WQ/QmryBZ3ebP9o8smYrqEtnimyzEjq2
YgavjIMyk4IriLGuqHMZY/DCYWq9gA==
=IEn9
-----END PGP SIGNATURE-----

Re: [Qtractor-devel] MIDI file import folder is getting collapsed after every D&D

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

Hi Rui,

> >> another little ugliness seen today: I import a MIDI file into
> >> the "Files" window on the right side of the arranger, click on
> >> the imported file to see its individual tracks ("Track 0", "Track
> >> 1" and so on), and when I drag&drop a track into a qtractor
> >> track, the expanded file view is getting collapsed again each
> >> time so I have to click on it again to see the tracks in it. Can
> >> this be fixed, please?
> > 
> > 
> > confirmed. a rather "micro-ugliness" should i say :) i'll have a
> > look, whenever i get the time.
> > 
> 
> fixed in 0.8.0.5git.c4d31d

Thanks for this :-). Yes, it is a "micro-ugliness", but many of these
combined also contribute to some kind of "uncomfortable" feeling after a
while; usability should not be underestimated.

It works better now, but - well, not perfect still. Folders are not
collapsed any more after a D&D operation, but what is now awkward is what
happens if you add e.g. Track 1 of a MIDI file to one Qtractor track, and
attempt to just D&D Track 2 into another Qtractor track. This doesn't work
because the previous track did not get unselected after the first D&D, so
you are now attempting to D&D 2 tracks at the same time (kind of "multi-select"
I guess). It can worked around by additional clicks to unselect everything,
but that's trading one ugliness for another :-).

That's perhaps the reason why you only commented that one line in the source
code instead of removing it right away.
I believe what should happen here instead of the "QTreeWidget::reset();"
is something like "un-select all items in the widget" (no idea what that's 
called in Qt speech).

Greetings,
Frank

Re: [Qtractor-devel] MIDI file import folder is getting collapsed after every D&D

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 12/04/2016 08:38 PM, Rui Nuno Capela wrote:
> hi Frank,
> 
> On 12/04/2016 06:14 PM, Frank Neumann wrote:
> 
>> another little ugliness seen today: I import a MIDI file into
>> the "Files" window on the right side of the arranger, click on
>> the imported file to see its individual tracks ("Track 0", "Track
>> 1" and so on), and when I drag&drop a track into a qtractor
>> track, the expanded file view is getting collapsed again each
>> time so I have to click on it again to see the tracks in it. Can
>> this be fixed, please?
> 
> 
> confirmed. a rather "micro-ugliness" should i say :) i'll have a
> look, whenever i get the time.
> 

fixed in 0.8.0.5git.c4d31d

byee
- -- 
rncbc aka. Rui Nuno Capela
rn...@rn...
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEml2OG8nT8/KXriugSepTUDAa1MgFAlhFrycACgkQSepTUDAa
1Mj84Qf+JhjX/C51PgOgsoDj4HRokWGY3Xn3y1GymI/t2I6fj+FO4NWf1GnOFPvw
i3/Vt/uI9Rjz0NFzx/u6GtiT6Qmss5y0DyjK1CGDsuKwZeKWNxdcqRco7WaNFq0s
1ktB5f9gAPsDEJ4sMCQhoOONtD/awpYUWGOUrO7mMLL2qyoQmurLTzubogGiQXiZ
1lt9hZ8KOjRykC9j7XkBIfKJPdE3Nd+9mYbAHjom10f4CKF0CkHI4lGwC2hrj2C7
vp1sC2h/1gEirryCPFnJ43W60Uy0v35a2mB1W5UOo5daoSwtsfQy/ba9xf/HE07p
WRiLrijnVRhZ//iaVm2tqFHzuQk7YA==
=BCye
-----END PGP SIGNATURE-----

Re: [Qtractor-devel] MIDI file import folder is getting collapsed after every D&D

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

hi Frank,

On 12/04/2016 06:14 PM, Frank Neumann wrote:
> 
> another little ugliness seen today: I import a MIDI file into the
> "Files" window on the right side of the arranger, click on the
> imported file to see its individual tracks ("Track 0", "Track 1"
> and so on), and when I drag&drop a track into a qtractor track, the
> expanded file view is getting collapsed again each time so I have
> to click on it again to see the tracks in it. Can this be fixed,
> please?
> 

confirmed. a rather "micro-ugliness" should i say :)
i'll have a look, whenever i get the time.


> Sidenote/request: MIDI .mid files often come with multiple tracks
> of which only some contain actual data (MIDI notes). Is there a way
> to indicate this per track in the "Files" window (like, # of MIDI
> events contained in a track, as part of the "Name" column?) Might
> be useful, as it would avoid some "trial&error" to find useful
> tracks.
> 

that would demand to read and parse the whole .mid file at once, and
not just the SMF header--something that i try to avoid ever since day
one :)

none of the above seems to be critical or top priority though, so i'll
ask you to file a ticket (sf.net) or an issue (github.com), if it
matters that much. jftr.

byee
- -- 
rncbc aka. Rui Nuno Capela
rn...@rn...
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEml2OG8nT8/KXriugSepTUDAa1MgFAlhEfo8ACgkQSepTUDAa
1MjRwwf/fREQVRiAmG/z53w9Fzb4oBLpWfEOACs5gPAynSEI/u/ExkWLbHdm1i8v
S20e6HDL3fRQOjkG/cwbgnhosBuxmmqD8e6asAJN1M2+R1c9HQl0258eYK5zryyJ
HrvpP4iaUtFCfPdpPSqvqkWzyz47KXMidRbI31hTxwktHdmWWlAfH3WBxUErp7Vv
zsNcWKF3fJNbkAH0l7Sl140gQwQgNOUGVO57Pjmm6OLs1+Eps5dzqmt8nX/Cx6S1
Llmb0Ntzdf0c5Y23tU6MdzBkaaMSkV0TR5z4jW/sxz4w2urUtfJ18u45iHmeCf+9
WsWicotqAfpNJXG2dn2TTqQQMc91QQ==
=Y3/N
-----END PGP SIGNATURE-----

[Qtractor-devel] MIDI file import folder is getting collapsed after every D&D

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

Hi Rui and all,

another little ugliness seen today: I import a MIDI file into the "Files" window
on the right side of the arranger, click on the imported file to see its individual
tracks ("Track 0", "Track 1" and so on), and when I drag&drop a track into a
qtractor track, the expanded file view is getting collapsed again each time so I
have to click on it again to see the tracks in it.
Can this be fixed, please?

Sidenote/request: MIDI .mid files often come with multiple tracks of which only
some contain actual data (MIDI notes). Is there a way to indicate this per track
in the "Files" window (like, # of MIDI events contained in a track, as part of
the "Name" column?)
Might be useful, as it would avoid some "trial&error" to find useful tracks.

Thanks,
Frank

Re: [Qtractor-devel] qtractor should send NoteOff's when switching tracks in arranger

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

hi Frank et al.

On 12/03/2016 11:04 AM, Frank Neumann wrote:
> 
> I found a little "ugliness" in Qtractor: Create 2 MIDI tracks, put
> some synth into each of them, connect your MIDI keyboard, play a
> note onto the first track, and then, with your keys still down,
> click on the second track in the arranger window. The (still
> playing) note from the first track is not silenced. I can of
> course click back on the first track and play the stuck notes again
> (and then they are silenced), but I believe it would be more
> intuitive if NoteOffs for all active notes are getting sent to the
> "old" track in the moment I switch to another.
> 

i'm sorry but this is just normal behavior (re. Track > Auto monitor).

when you're switching MIDI tracks, you probably are also switching the
target MIDI channel and filter, so that a note-on that was received on
an earlier track, which also gets delivered to that track's instrument
plugins if any, won't match to a later note-off channel that gets
emitted when you release the key on the MIDI keyboard, let alone the
note-off event that is now routed into a different track plugin chain.

so, nope. sorry.
- -- 
rncbc aka. Rui Nuno Capela
rn...@rn...
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEml2OG8nT8/KXriugSepTUDAa1MgFAlhCtkgACgkQSepTUDAa
1MhlTggAiJSobil76K7Qv8Y4ZNx3UVg+EzQ0JkCNYebgxm1kCKKi0JN1wrwywrR0
HIqzKnvIU+nYlnpCmaWnnKw/tXj4UQccISdde3nPc+9QVelcD+6FQ3ioDLZH5HRW
1J4POvx1wtsGlgs3Wq+r88ycdQxiSIjZ+uFC4wO3ySMp4STkEt6EpdJbyj+z6ELh
E5/8i2BLfGHUnzU22WXqKls/+gYHPyL/uO26fms2j8rNQqFQRSc5GTrRDR3pbqFQ
boiJvz0bSOOq98HTwXqdFztdeJnmBOeIq7GtKqIPOEdh5wyUAagGo4l5PkUntaS3
1PmcwgrV5pCxC2g1wK8W2DB5M4djhw==
=m3zh
-----END PGP SIGNATURE-----

Re: [Qtractor-devel] qtractor should send NoteOff's when switching tracks in arranger

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

On Sat, 2016-12-03 at 12:04 +0100, Frank Neumann wrote:
> I found a little "ugliness" in Qtractor: Create 2 MIDI tracks, put some synth
> into each of them, connect your MIDI keyboard, play a note onto the first track,
> and then, with your keys still down, click on the second track in the arranger
> window.
> The (still playing) note from the first track is not silenced. I can of course
> click back on the first track and play the stuck notes again (and then they are
> silenced), but I believe it would be more intuitive if NoteOffs for all active
> notes are getting sent to the "old" track in the moment I switch to another.

Then Qtractor needs to detect, if the note is send by an external MIDI
source or played by events that are already recorded and also to decide
what to do, if the same not is played by an external source, as well as
by recorded events, or do you expect note-offs for recorded midi notes,
too, when playing a song and switching from one to another track. It's a
chain from MIDI in to MIDI out and you expect a behaviour for MIDI out,
that is related to MIDI in.

Regards,
Ralf

[Qtractor-devel] qtractor should send NoteOff's when switching tracks in arranger

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

Hi Rui and all,

I found a little "ugliness" in Qtractor: Create 2 MIDI tracks, put some synth
into each of them, connect your MIDI keyboard, play a note onto the first track,
and then, with your keys still down, click on the second track in the arranger
window.
The (still playing) note from the first track is not silenced. I can of course
click back on the first track and play the stuck notes again (and then they are
silenced), but I believe it would be more intuitive if NoteOffs for all active
notes are getting sent to the "old" track in the moment I switch to another.

Thanks,
Frank

Re: [Qtractor-devel] hexter DSSI plugin not working correctly in qtractor?

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

On Mon, 28 Nov 2016 19:58:51 +0100, Frank Neumann wrote:
>yesterday I wanted to compare several "DX7" emulating synths for Linux
>(OxeFM, Dexed, Hexter) against original DX7 sounds "from YouTube"

Hi,

I can't help you with your issue, but I can provide some information
about Hexter compared to a real DX7. I own a first generation DX7 since
33 or 34 years.
I tested Hexter with TerrTec EWX 24/96 and RME HDSPe AIO sound cards.
Hexter emulates a DX7 very well, the synthesis isn't just a fake, it's
like a real DX7, just the sound quality of Hexter is not nearly as good
as a real DX7, it sounds much thinner and colder than a DX7. While
a real DX7 doesn't sound as warm as a real analog CEM based synthesizer,
such as an Oberheim (I own an Oberheim since decades, too), a DX7 sounds
still much warmer than any virtual analog synth. The velocity response
characteristic also differs between Hexter and a DX7. IOW if you play
Hexter with a real DX7 as master keyboard, it sounds like playing a
real DX7, with another master keyboard, instead of playing it by it's
own keyboard. The only advantage of Hexter over a DX7 is the
signal-to-noise ratio. A DX7 is a professional keyboard, producing less
noise, than a consumer's home organ, but it does produce audible noise.
Hexter doesn't produce noise, at least not when using a professional
sound card.

Regards,
Ralf

Re: [Qtractor-devel] hexter DSSI plugin not working correctly in qtractor?

[Holger M. <ho...@ma...>]

On Mon, 28 Nov 2016, Frank Neumann wrote:

> 
> Hi Holger and all,
> 
> [..misbehaved hexter]
> 
> > > Can someone else test this on his setup and tell me whether it's just me? :-)
> > > Running Hexter in the jack-dssi-host app works fine, by the way.
> > 
> > Last time I checked *one* Hexter instance behaved fine, with *two* I got
> > strange delays. Some people told me that it was Hexter's fault because
> > if its internal programming.
> 
> Hm..never mind. I realized now that though my Hexter version is the latest that
> got released "back then", my installed binary is already 2 years old - so I
> simply recompiled and installed version 1.0.3, and now it's all fine :-}.
> I guess "ideally this should not happen", but perhaps not all software updates
> that got installed into my system in the meantime were compatible with the
> state of November 2014..

Do me a favour and use several tracks with hexter, e.g. 4 tracks and at
least one track with another instrument plugin, e.g. fluidsynth or
linuxsampler with drums. And set jackd's buffer size to a big value,
e.g. -n 2 -p 2048. I need such sizes when mixing songs with lots of
tracks and plugins. The bigger jackd's buffer size the more obvious the
timing issues became. Please use fast-attack, percussive hexter sounds
to check if the notes are in sync (xylophone). It would be very
interesting if this issue still exists.

Regards
Holger

Re: [Qtractor-devel] hexter DSSI plugin not working correctly in qtractor?

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

Hi Holger and all,

[..misbehaved hexter]

> > Can someone else test this on his setup and tell me whether it's just me? :-)
> > Running Hexter in the jack-dssi-host app works fine, by the way.
> 
> Last time I checked *one* Hexter instance behaved fine, with *two* I got
> strange delays. Some people told me that it was Hexter's fault because
> if its internal programming.

Hm..never mind. I realized now that though my Hexter version is the latest that
got released "back then", my installed binary is already 2 years old - so I
simply recompiled and installed version 1.0.3, and now it's all fine :-}.
I guess "ideally this should not happen", but perhaps not all software updates
that got installed into my system in the meantime were compatible with the
state of November 2014..

Thanks anyway,
Frank

Re: [Qtractor-devel] hexter DSSI plugin not working correctly in qtractor?

[Holger M. <ho...@ma...>]

On Mon, 28 Nov 2016, Frank Neumann wrote:

> Hi Rui and all,
> 
> yesterday I wanted to compare several "DX7" emulating synths for Linux (OxeFM,
> Dexed, Hexter) against original DX7 sounds "from YouTube", and noticed that
> Hexter wouldn't behave quite well.
> 
> I start from an empty qtractor (0.8.0) session, create a MIDI track, instantiate
> the Hexter DSSI plugin (version 1.0.3), activate the synth, create my MIDI
> connections, and press some keys on a connected keyboard.
> 
> The first keypress comes out fine, but after that I sometimes only get a
> short sound on key _release_, or no sound at all, except for a full-scale
> crackle sound on both press and release. I see no suspicious CPU load spikes
> and also no buffer Xruns, but it appears as if a note is cut off immediately
> after key press for some reason.
> 
> Can someone else test this on his setup and tell me whether it's just me? :-)
> Running Hexter in the jack-dssi-host app works fine, by the way.

Last time I checked *one* Hexter instance behaved fine, with *two* I got
strange delays. Some people told me that it was Hexter's fault because
if its internal programming.

I use Dexed now and it works fine.

Another try might be encapsulating Hexter in Carla (LV2). Hexter sounds
a bit brighter than Dexed so some people prefer Hexter's sound.

Regards
Holger

[Qtractor-devel] hexter DSSI plugin not working correctly in qtractor?

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

Hi Rui and all,

yesterday I wanted to compare several "DX7" emulating synths for Linux (OxeFM,
Dexed, Hexter) against original DX7 sounds "from YouTube", and noticed that
Hexter wouldn't behave quite well.

I start from an empty qtractor (0.8.0) session, create a MIDI track, instantiate
the Hexter DSSI plugin (version 1.0.3), activate the synth, create my MIDI
connections, and press some keys on a connected keyboard.

The first keypress comes out fine, but after that I sometimes only get a
short sound on key _release_, or no sound at all, except for a full-scale
crackle sound on both press and release. I see no suspicious CPU load spikes
and also no buffer Xruns, but it appears as if a note is cut off immediately
after key press for some reason.

Can someone else test this on his setup and tell me whether it's just me? :-)
Running Hexter in the jack-dssi-host app works fine, by the way.

Thanks,
Frank

Re: [Qtractor-devel] Has the handling for Copy/Paste changed?

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

Hi Rui, Holger and all,

[..]

> > With 0.7.9.39 (built on Nov 10th), this doesn't seem to work - while Ctrl-C
> > seems to do "something" (at least the selected notes are being de-selected),
> > Ctrl-V has no visible effect.
> > Also, Paste Repeat doesn't seem to do anything either.
> > 
> > Now I wonder whether it's just me, or whether it's actually a bug.
> > I even tried moving my current ~/.config/rncbc.org/Qtractor.conf out of the
> > way in case it contains some old/incompatible config settings, but to no
> > avail.
> > 
> > Any idea?
> > 
> 
> yes it was a self-inflected bug which was contained and fixed a week ago
> 
> would you please try and update from a later git pull?

You're both right :-). I'm rebuilding Qtractor pretty often (like at least
once a week or so), and haven't really ever had any regressions so far, but
this time it seems to have struck me :-).
Grabbed current Git, built it, installed it, tested, all fine. Happy again!

Thanks,
Frank