[Qmidiarp-devel] Re : Re : More News from the git cuisine

[Frank Kober <goemusic@ya...>]

Helllooo



----- Mail original -----
> De : Frank Kober <goemusic@...>
> À : Frank Kober <goemusic@...>; Sascha Schneider <ungleichklang@...>
> Cc : "qmidiarp-devel@..." <qmidiarp-devel@...>
> Envoyé le : Samedi 5 Novembre 2011 18h38
> Objet : Re : [Qmidiarp-devel] Re :  More News from the git cuisine

> OK this part seems to be fixed now, was not a drama after all, but I had missed 
> testing it on my old 32bit machine...:)

In addition to the play direction switch we now have an, no, THE in-sequence loop marker available.
This one is, I think, what Sascha suggested as a feature. 
You can place a loop marker using left or right mouse buttons on the bottom frame (where the cursor is).
The loop marker goes away again when clicking in the left or right bottom corners.
Suggestions to make this better are welcome.
There was also a fix regarding MIDI Clock Sync not starting upon the second time the
MIDI clock started. MIDI Clock sync anyway has still a lot of jitter on my machine, 
and I don't seem to get this tackled easily. 

See ya

Frank

[Qmidiarp-devel] Re : Re : More News from the git cuisine

[Frank Kober <goemusic@ya...>]

----- Mail original -----
> De : Frank Kober <goemusic@...>
> À : Sascha Schneider <ungleichklang@...>
> Cc : "qmidiarp-devel@..." <qmidiarp-devel@...>
> Envoyé le : Samedi 5 Novembre 2011 10h12
> Objet : [Qmidiarp-devel] Re :  More News from the git cuisine
> 
> Hi Sascha,
> 
>> De : Sascha Schneider <ungleichklang@...>
>> second test on another machine:
>> Archlinux: Kernel-rt 2.6.33
>> qjackctl 0.3.8
>> jack2 1.9.7-2
>> 
>> - builds fine.
>> - runs fine with alsa
>> - qmidiqarp -j works ... for a while ..
>> I see qmidiarp in Jack-Midi tab and if I press start on qjackctl qmidiarp 
> runs ... but not long ... qmidiarp stops playing after different times and I get 
> no error messages at all.

OK this part seems to be fixed now, was not a drama after all, but I had missed testing it on my old 32bit machine...:)
However I cannot reproduce the other (connection) error, so If this affects others please tell.

Thanks Sascha
Frank

>

[Qmidiarp-devel] Re : More News from the git cuisine

[Frank Kober <goemusic@ya...>]

Hi Sascha,

>De : Sascha Schneider <ungleichklang@...>
>second test on another machine:
>Archlinux: Kernel-rt 2.6.33
>qjackctl 0.3.8
>jack2 1.9.7-2
>
>- builds fine.
>- runs fine with alsa
>- qmidiqarp -j works ... for a while ..
>I see qmidiarp in Jack-Midi tab and if I press start on qjackctl qmidiarp runs ... but not long ... qmidiarp stops playing after different times and I get no error messages at all.
>stop/restart jackplay runs qmidiarp but again it stops after a while (sometimes 4 steps as a minimum and sometimes 2 loops as a max)


Thanks for your reports.

Hmmm, that is not what I expected. I tested it on two machines here, both running jack2 though and it ran flawlessly with Jack MIDI. I have a third (slower) machine available today and will test it there.
Is the first machine (where you get the "port not available" messages) running jack1? 

If there are machine-dependent errors that's a bad sign...

I hope we can this sorted and look forward to more info. I'll be around on IRC #qmidiarp, too.

Cheers
Frank

Re: [Qmidiarp-devel] More News from the git cuisine

[Sascha Schneider <ungleichklang@gm...>]

Hi Frank,

second test on another machine:
Archlinux: Kernel-rt 2.6.33
qjackctl 0.3.8
jack2 1.9.7-2

- builds fine.
- runs fine with alsa
- qmidiqarp -j works ... for a while ..
I see qmidiarp in Jack-Midi tab and if I press start on qjackctl qmidiarp
runs ... but not long ... qmidiarp stops playing after different times and
I get no error messages at all.
stop/restart jackplay runs qmidiarp but again it stops after a while
(sometimes 4 steps as a minimum and sometimes 2 loops as a max)

greetings, sascha

2011/11/3 Frank Kober <goemusic@...>

> Hi all,
>
> just to give some more updates on the current qmidiarp git version (did I
> say that autumn..ah...phew..)
> I have included some new features that might be interesting to some of you.
> Here's the summary:
>
>   o Groove functions now work for all modules, not only Arps
>   o Effect of groove settings is displayed in the Arp/LFO/Seq screen
>   o LFOs can be triggered and restarted by the keyboard
>   o When reducing the size of LFO waves or Sequences, the original data
>     is kept in memory and is also saved to the session file as a whole
>   o LFO and Seq play direction can now be chosen, and bouncing loops are
>     possible
>
>
> If someone finds the time to test this and the program as a whole (don't
> forget to use -j option
>
> once in a while to get JACK MIDI) that'd be really helpful, the signs of a
> new release start
>
> appearing, and it could be somewhen in november if there is not too much
> mess with
>
> the current version.
>
> Enjoy and let me know :)
> Best
>
> Frank
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Qmidiarp-devel mailing list
> Qmidiarp-devel@...
> https://lists.sourceforge.net/lists/listinfo/qmidiarp-devel
>

Re: [Qmidiarp-devel] More News from the git cuisine

[Sascha Schneider <ungleichklang@gm...>]

Hi Frank,

tested the git and it builds perfect.
qmidiarp runs well with alsa but with the option "-j" I get:
# jack process callback registered
# float exception (original => Gleitkomma Ausnahme)
and the jack messages show something like:
# Output port index = 7 not found for application ref = 3

and a little cosmetic issue:
in the step-sequencer the "Display"-options could be a dropdown (Full,
Upper, Lower ....) that would save some height.

will test more this weekend

Greetings, Sascha

2011/11/3 Frank Kober <goemusic@...>

> Hi all,
>
> just to give some more updates on the current qmidiarp git version (did I
> say that autumn..ah...phew..)
> I have included some new features that might be interesting to some of you.
> Here's the summary:
>
>   o Groove functions now work for all modules, not only Arps
>   o Effect of groove settings is displayed in the Arp/LFO/Seq screen
>   o LFOs can be triggered and restarted by the keyboard
>   o When reducing the size of LFO waves or Sequences, the original data
>     is kept in memory and is also saved to the session file as a whole
>   o LFO and Seq play direction can now be chosen, and bouncing loops are
>     possible
>
>
> If someone finds the time to test this and the program as a whole (don't
> forget to use -j option
>
> once in a while to get JACK MIDI) that'd be really helpful, the signs of a
> new release start
>
> appearing, and it could be somewhen in november if there is not too much
> mess with
>
> the current version.
>
> Enjoy and let me know :)
> Best
>
> Frank
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Qmidiarp-devel mailing list
> Qmidiarp-devel@...
> https://lists.sourceforge.net/lists/listinfo/qmidiarp-devel
>

[Qmidiarp-devel] More News from the git cuisine

[Frank Kober <goemusic@ya...>]

Hi all,

just to give some more updates on the current qmidiarp git version (did I say that autumn..ah...phew..)
I have included some new features that might be interesting to some of you.
Here's the summary:

  o Groove functions now work for all modules, not only Arps
  o Effect of groove settings is displayed in the Arp/LFO/Seq screen
  o LFOs can be triggered and restarted by the keyboard
  o When reducing the size of LFO waves or Sequences, the original data
    is kept in memory and is also saved to the session file as a whole
  o LFO and Seq play direction can now be chosen, and bouncing loops are
    possible


If someone finds the time to test this and the program as a whole (don't forget to use -j option 

once in a while to get JACK MIDI) that'd be really helpful, the signs of a new release start 

appearing, and it could be somewhen in november if there is not too much mess with 

the current version.

Enjoy and let me know :)
Best

Frank

[Qmidiarp-devel] JACK MIDI progress

[Frank Kober <goemusic@ya...>]

Dear friends,

Summer is almost over, not much has happened around QMidiArp development.

Wait, there was one thing: JACK MIDI support. There is some progress on that end, and those
of you in need of a JACK MIDI interface for QMidiArp might want to checkout the jack-midi git
branch. As things stand, this is currently fully working, at least from my testing point of view.
Nothing has improved regarding input latency (which is two ticks now, about 20 ms), but at least
those having trouble with unstable ALSA timers might see an improvement over the ALSA driver.
To go beyond that, some more work and Nedko's (with who's help the architecture
changes up to now could be done) competences will be badly needed, since I still don't feel 

comfortable in real-time programming.


To get the test version do a git clone and checkout the jack-midi branch:

git clone git://qmidiarp.git.sourceforge.net/gitroot/qmidiarp/qmidiarp 

cd qmidiarp
git checkout jack-midi
autoreconf -i
./configure
make
sudo make install

you can now call qmidiarp with 

qmidiarp -j 


to use the JACK MIDI backend, otherwise the alsa backend is used as before.

You'll need a transport master such as qjackctl or qtractor aside to start qmidiarp in JACK mode.

I'd like to know whether it works for you as well as it does here. I must say I use an rt-kernel and a 128ms jack period. No xruns.


Have fun, and let me know whether it does as it should, also, does the old ALSA interface still work as before?


Cheers
Frank

Re: [Qmidiarp-devel] Re : Feature ideas for the sequencer

[Sascha Schneider <ungleichklang@gm...>]

2011/7/14 Louigi Verona <louigi.verona@...>

> Ha! Nice video, I am convinced!
>
> --
> Louigi Verona
> http://www.louigiverona.ru/
>
>
> ------------------------------------------------------------------------------
> AppSumo Presents a FREE Video for the SourceForge Community by Eric
> Ries, the creator of the Lean Startup Methodology on "Lean Startup
> Secrets Revealed." This video shows you how to validate your ideas,
> optimize your ideas and identify your business strategy.
> http://p.sf.net/sfu/appsumosfdev2dev
> _______________________________________________
> Qmidiarp-devel mailing list
> Qmidiarp-devel@...
> https://lists.sourceforge.net/lists/listinfo/qmidiarp-devel
>
>
Had some time to GIMP :)

http://ungleichklang.imgur.com/qmidiarp

greetings, Sascha

Re: [Qmidiarp-devel] Re : Feature ideas for the sequencer

[Louigi Verona <louigi.verona@gm...>]

Ha! Nice video, I am convinced!

-- 
Louigi Verona
http://www.louigiverona.ru/

Re: [Qmidiarp-devel] Re : Feature ideas for the sequencer

[Sascha Schneider <ungleichklang@gm...>]

2011/7/14 Louigi Verona <louigi.verona@...>

> Hey Sascha!
>
> Nice ideas there, although not sure if playing a sequence backwards is that
> interesting. Gotta try it with Pure Data and see if it delivers any
> interesting results.
>

As for loop marker - I guess it is a nice idea. I very much enjoy that
> QMidiArp now duplicated mute mask when you increase length of the sequencer
> - it helps to build up sequences. Loop marker might be a good idea there as
> a logical step.
>
> Louigi Verona.
> http://www.louigiverona.ru/
>

Hey Louigi,

first of all, I love the loops you did,
and for looping backwards and change loop-lenght I really enjoy this vid
http://www.youtube.com/watch?v=pQoNqtzVvKo

greetings, sascha

Re: [Qmidiarp-devel] Re : Feature ideas for the sequencer

[Louigi Verona <louigi.verona@gm...>]

Hey Sascha!

Nice ideas there, although not sure if playing a sequence backwards is that
interesting. Gotta try it with Pure Data and see if it delivers any
interesting results.

As for loop marker - I guess it is a nice idea. I very much enjoy that
QMidiArp now duplicated mute mask when you increase length of the sequencer
- it helps to build up sequences. Loop marker might be a good idea there as
a logical step.

Louigi Verona.
http://www.louigiverona.ru/

Re: [Qmidiarp-devel] Re : Feature ideas for the sequencer

[Sascha Schneider <ungleichklang@gm...>]

2011/7/14 Frank Kober <goemusic@...>:
> Hi Sascha,we'll be giving priority to make some changes under the hood in
the next weeks with Nedko.
> But it is definitely helpful to track your suggestions here for after that
:)
>
>
>> 1st feature: variable playlength of sequence
>> it would be nice that if I add a sequence of f.e. 16 steps and alter
>> the "length" live to f.e. 8, that after switching back to length of 16
>> the sequencer does not just double the first 8 steps, but has the old
>> steps set in mind.
>> Or that there is something under the sequence-bar that runs with the
>> sequence, where I can determine, to which point the sequence loops.
>
> Thanks for your input here. Jeremy and I had left comments regarding this
in the feature-request tracker,
> and the only problem with that seems to be (again) how storage to disk
should be done.
> Maybe a loop marker as you suggest is a good solution to this.

I'll post my ideas to feature-tracker so that we have an overview

>
>> 2nd feature: playing direction of sequence
>> add new playing directions live to a sequence
>> play left-to-right, right-to-left, forward-backward-forward, random
>> Means, f.e. if sequence runs from left-to-right and loops and I switch
>> the play-direction, it will start playing backwards at the end of the
>> loop
>
> Sounds interesting to me, too.

I'll add this to the feature-tracker, too

>
>> 3rd feature: group 2 sequences
>> this way I could join 2 sequences of f.e. 8 steps to one sequence of
>> 16 step but with the ability to change the play-direction of just one
>> of them or mute one of them
>>
>> Yes I know, weird ideas, but they would be fun :)
>
> Not that weird, ....well the last one a bit maybe :)
> One planned feature are multi-patterns for each sequencer, a bit like in
the arp modules. But there again, a logical way of storage (with session
file, with application rc file, both....) has to be found first.
>
>
> Thanks again
> Cheers
> Frank
>
>>
>
thanks and greetings back,

Sascha

[Qmidiarp-devel] Re : Feature ideas for the sequencer

[Frank Kober <goemusic@ya...>]

Hi Sascha,we'll be giving priority to make some changes under the hood in the next weeks with Nedko.
But it is definitely helpful to track your suggestions here for after that :)


> 1st feature: variable playlength of sequence
> it would be nice that if I add a sequence of f.e. 16 steps and alter
> the "length" live to f.e. 8, that after switching back to length of 16
> the sequencer does not just double the first 8 steps, but has the old
> steps set in mind.
> Or that there is something under the sequence-bar that runs with the
> sequence, where I can determine, to which point the sequence loops.

Thanks for your input here. Jeremy and I had left comments regarding this in the feature-request tracker, 
and the only problem with that seems to be (again) how storage to disk should be done.
Maybe a loop marker as you suggest is a good solution to this. 

> 2nd feature: playing direction of sequence
> add new playing directions live to a sequence
> play left-to-right, right-to-left, forward-backward-forward, random
> Means, f.e. if sequence runs from left-to-right and loops and I switch
> the play-direction, it will start playing backwards at the end of the
> loop

Sounds interesting to me, too.

> 3rd feature: group 2 sequences
> this way I could join 2 sequences of f.e. 8 steps to one sequence of
> 16 step but with the ability to change the play-direction of just one
> of them or mute one of them
> 
> Yes I know, weird ideas, but they would be fun :)

Not that weird, ....well the last one a bit maybe :)
One planned feature are multi-patterns for each sequencer, a bit like in the arp modules. But there again, a logical way of storage (with session file, with application rc file, both....) has to be found first.


Thanks again
Cheers
Frank

>

[Qmidiarp-devel] cosmetic changes

[Sascha Schneider <ungleichklang@gm...>]

Hi Frank,

wanted to ask if it is possible to make the "display:" section in the
sequencer a drop-down??
would save some space to add more sequences/LFO to on window-set.

greetings, sascha

[Qmidiarp-devel] Feature ideas for the sequencer

[Sascha Schneider <ungleichklang@gm...>]

I played a lot with the sequencer of qmidiarp the last days and I have
a couple of ideas that might be worth considering for the future.

I admit that it is all stolen from the way f.e. a doepfer darktime
works or the older "softwerk" from the ardour-project
and yes, I know that those features are maybe a bit "hardcore"

1st feature: variable playlength of sequence
it would be nice that if I add a sequence of f.e. 16 steps and alter
the "length" live to f.e. 8, that after switching back to length of 16
the sequencer does not just double the first 8 steps, but has the old
steps set in mind.
Or that there is something under the sequence-bar that runs with the
sequence, where I can determine, to which point the sequence loops.

2nd feature: playing direction of sequence
add new playing directions live to a sequence
play left-to-right, right-to-left, forward-backward-forward, random
Means, f.e. if sequence runs from left-to-right and loops and I switch
the play-direction, it will start playing backwards at the end of the
loop

3rd feature: group 2 sequences
this way I could join 2 sequences of f.e. 8 steps to one sequence of
16 step but with the ability to change the play-direction of just one
of them or mute one of them

Yes I know, weird ideas, but they would be fun :)

greetings from belgium, Sascha

[Qmidiarp-devel] QMidiArp 0.4.2 released

[Frank Kober <goemusic@ya...>]

Hi all,

Great feedback from some users, especially Louigi Verona, Sascha Schneider and Jeremy Jongepier 
have kept the inspiration level up, and some bugs could be squeezed since the last release.

Louigi has even used QMidiArp in Live sessions that you can now listen to on the qmidiarp website at

http://qmidiarp.sourceforge.net/qmidiarp_demos_en.html

I'd also like to thank Nedko again for great discussions and answers in most cases

Two major issues had been addressed in a provided patch, but other small ones are now done in this
release. But there are even some new features, most of them inspired by you guys:

qmidiarp-0.4.2 (2011-07-10)

New Features
  o LFO wave lengths up to 32 bars for very low frequencies
  o Groove Settings and LFO & Seq resolutions now also MIDI-controllable
  o One-click duplication of LFO and Seq modules
  o Option to add new modules in muted state
  o Vertical Zoom switch for Seq module display
  o ToolBars can be positioned vertically
  o Nested arrangement of modules allows more flexible layouts

Fixed Bugs
  o 0.4.1-patch had been available for the following two:
    o Jack Transport sync arbitrarily stopping with only arp modules
    o Instability with ALSA clock with only Seq and LFO modules
  o Faster response to Jack Transport state changes
  o Incorrect response to two Seq sliders

General Changes
  o Jack Transport sync uses jack process callback not sync callback


Enjoy!
------------------------------------------------------

http://qmidiarp.sourceforge.net/

http://sourceforge.net/projects/qmidiarp/files/qmidiarp/0.4.2/

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

[Qmidiarp-devel] Two new tracks by Louigi Verona available

[Frank Kober <goemusic@ya...>]

Hi all,

Louigi Verona has put two very nice new live tracks on soundcloud. 

They are heavily featuring Seq and LFO modules!

Check them out here if you are interested, they are embedded on the qmidiarp demo page here:
http://qmidiarp.sourceforge.net/qmidiarp_demos_en.html

Cheers
Frank

[Qmidiarp-devel] Re : Further testing

[Frank Kober <goemusic@ya...>]

Hi Brendan,



----- Mail original -----
> De : Brendan Jones <brendan.jones.it@...>
> À : qmidiarp-devel@...
> Cc : 
> Envoyé le : Mardi 7 Juin 2011 3h02
> Objet : [Qmidiarp-devel] Further testing
> 
> Hi guys
> 
> I have been playing around with the git version from yesterday.
> 
> I have experienced some unusual behaviour with jack transport. 
> Occasionally playback will cease after stopping and starting. I'll 
> outline my setup:
> 
>   - I have both jackctlmmc and a2jmidi daemons queued to start after 
> jackd starts.
>   - Qmidiarp in jack transport mode
>   - I have a midi controller sending transport messages to jackctlmmc 
> Jack midi port
>   - midi controller also sends input to a Qmidiarp sequencer
>   - seq24 sequencer with jack as transport master (midi out to hydrogen)
>   - Qmidiarp output port to either/and yoshimi / hardware synth
> 
> Two issues I have noticed
> 
> 1 - if I rapidly stop start jack transport via the controller 
> occasionally qmidiarp will only play the first note and playback will stop
> 2 - if I have set the midi sequencer to retrigger on input occasionally 
> playback will stop - however subsequent note velocity input can be seen 
> to update the GUI
> 
> In the first instance stopping and starting transport will cause the 
> playback to continue

There are some changes on git which _might_ improve (1), at least reaction to transport start and stop should now be faster. Could you try with the current git ?

(2) is something I don't get here so it probably didn't change for this issue.

Thanks for the feedback

Cheers
Frank

Re: [Qmidiarp-devel] Re : feedback

[michael noble <looplog@gm...>]

On Wed, Jun 8, 2011 at 2:49 AM, Frank Kober <goemusic@...> wrote:
>
> 1) The docking is a Qt feature, but it can be adjusted. I have changed one of the allowed
> features enabled for docking, and it might be that this used to be the default in earlier
> qt versions, but I am not sure. Anyway, please try whether this enables the possibility of
> doing the layout as you say.
>
> 2) I'm not sure why the toolbars don't resize automatically when in vertical orientation, but I've added
> a workaround that works OK giving correct vertical sizes at least with my Qt style here.
>

Thanks for looking at that. I'll try the new build on the weekend and
let you know if there are any further problems.

-michael

[Qmidiarp-devel] Re : feedback

[Frank Kober <goemusic@ya...>]

Hello Michael,


----- Mail original -----
> De : michael noble <looplog@...>

> Likewise, the toolbar's are movable, but they only
> really are useful when docked horizontally - the icons are not visible
> when you dock them vertically, as I like to do on my netbook to make
> the most of the screen dimensions on that machine.

> 
> Is the docking something that can be adjusted, or is it a limitation
> of the QT toolkit?

1) The docking is a Qt feature, but it can be adjusted. I have changed one of the allowed
features enabled for docking, and it might be that this used to be the default in earlier
qt versions, but I am not sure. Anyway, please try whether this enables the possibility of 
doing the layout as you say.

2) I'm not sure why the toolbars don't resize automatically when in vertical orientation, but I've added
a workaround that works OK giving correct vertical sizes at least with my Qt style here.

Hope this addresses you questions ;)
Thanks for the feedback, glad you can work without glitches so far
Frank

[Qmidiarp-devel] Further testing

[Brendan Jones <brendan.it@gm...>]

Hi guys

I have been playing around with the git version from yesterday.

I have experienced some unusual behaviour with jack transport. 
Occasionally playback will cease after stopping and starting. I'll 
outline my setup:

  - I have both jackctlmmc and a2jmidi daemons queued to start after 
jackd starts.
  - Qmidiarp in jack transport mode
  - I have a midi controller sending transport messages to jackctlmmc 
Jack midi port
  - midi controller also sends input to a Qmidiarp sequencer
  - seq24 sequencer with jack as transport master (midi out to hydrogen)
  - Qmidiarp output port to either/and yoshimi / hardware synth

Two issues I have noticed

1 - if I rapidly stop start jack transport via the controller 
occasionally qmidiarp will only play the first note and playback will stop
2 - if I have set the midi sequencer to retrigger on input occasionally 
playback will stop - however subsequent note velocity input can be seen 
to update the GUI

In the first instance stopping and starting transport will cause the 
playback to continue

In the second its not immediately apparent how I can restart playback - 
usually a combination of turning off jack transport / stopping / 
starting / stopping Qmidiarp and re-enabling jack transport.

In all cases seq24 receives and acts on transport messages correctly.

Anyway - I hope this is clear. Let me know if there is anything else you 
need.

regards,

Brendan

[Qmidiarp-devel] feedback

[michael noble <looplog@gm...>]

Hi Frank,

I finally had a chance to test out the latest git code and it works
great. Very stable, no problems with either the transport or random
crashes.

I just have a question regard the way objects are docked in the main
window. The behavior of docking seems kind of arbitrary. In earlier
releases I could basically dock eight visible LFOs at once as a grid
with the center missing (3 on top row, 2 in middle, 3 on bottom). Now,
I can only dock three on top, and two on the bottom and middle rows.
If wanted to have say two sequencer modules in a top row, with 6 LFOs
in two rows below this, this doesn't work. Similarly, if I wanted to
put 4 LFOs in the top row, which should fit into the resolution of my
montior, I can't. Likewise, the toolbar's are movable, but they only
really are useful when docked horizontally - the icons are not visible
when you dock them vertically, as I like to do on my netbook to make
the most of the screen dimensions on that machine.

Is the docking something that can be adjusted, or is it a limitation
of the QT toolkit?

regards

Michael

Re: [Qmidiarp-devel] Re : Re : Proof QMidiArp is stable and some feedback after a 32 minute live session

[Louigi Verona <louigi.verona@gm...>]

Just built it now, will check.

Stops occurred when I added a new sequencer during play. To avoid this, I
created a template with 8 sequencers already loaded, so hopefully this will
not happen again.




-- 
Louigi Verona
http://www.louigiverona.ru/

[Qmidiarp-devel] Re : Re : Some feedback on QMidiArp 0.4.1

[Frank Kober <goemusic@ya...>]

Thanks Brendan,



----- Mail original -----
> De : Brendan Jones <brendan.jones.it@...>
> À : qmidiarp-devel@...
> Cc : 
> Envoyé le : Vendredi 3 Juin 2011 23h53
> Objet : [Qmidiarp-devel] Re :  Some feedback on QMidiArp 0.4.1

> Just an update - I have not experienced any crashes or stoppages - only 
> one very minor issue with the Transpose slider in the sequencer. It only 
> works with the mouse if you drag on the slider knob directly - if you 
> click anywhere on the slider the slider knob itself moves but the key is 
> uchanged. As I said minor - I can't really see why you'd want to control 
> 
> the key by sight in this way. Dragging the knob, or using the textbox or 
> ext. MIDI controller works as expected.
> 

This is fixed on git now, it was supposed to be a "feature" but it didn't work with MIDI CC...
Good catch

Cheers
Frank

[Qmidiarp-devel] Re : Re : Proof QMidiArp is stable and some feedback after a 32 minute live session

[Frank Kober <goemusic@ya...>]

>De : Louigi Verona <louigi.verona@...>

>2. Sliders behaviour.
>What about when you use midi input? I used LFOs to change the volume of what was played by feeding midi from LFO directly into QMidiArp. The slider moves around but volume changes do not happen. But if I use my mouse - they do.


Good catch! These were the two sliders I had changed response for to allow for the pre-set and go by enter without noticing MIDI-learned controllers didn't work any longer. They are back to normal now, thanks.


>
>3. Three state check-box of piano roll zoom.
>Looks really great! However (hehe) can you add an option to view the center portion? Because often note C is the central note of the sequence, so jumping from upper to lower is like not that convenient.


GUI is at least not bigger yet, so we can have this a try.

Both are on git

BTW: I noticed some stops in your last music piece, the one with sync to harmonySEQ. Are these transport sync shortcomings or were they on purpose? Did you sync with JACK Transport or MIDI Clock?


Frank