qmidiarp-user Mailing List for QMidiArp (Page 2)
Linux MIDI arpeggiator, phrase generator and controller LFO
Status: Alpha
Brought to you by:
emuse
Menu
▾
▴
qmidiarp-user — qmidiarp user discussion
You can subscribe to this list here.
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(20) |
Jul
(3) |
Aug
(1) |
Sep
|
Oct
|
Nov
(5) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2012 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(1) |
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2014 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(3) |
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Frank K. <goe...@ya...> - 2012-01-21 18:00:59
|
Hi there! QMidiArp 0.4.5 is now available for download and contains two bugfixes for issues reported on the IRC by quilzo. http://sourceforge.net/projects/qmidiarp/files/qmidiarp/0.4.5/ qmidiarp-0.4.5 (2012-01-21) Fixed Bugs o JACK Transport start with ALSA backend was broken in 0.4.4 o Crash when events not matching any channel in any module were received in JACK MIDI backend For those who want to check out some new features under development, the current "globalstore" git branch contains a new global parameter store handler allowing to switch all settings in one click at a defined time which can be very handy in live situations. For this, git clone git://qmidiarp.git.sourceforge.net/gitroot/qmidiarp/qmidiarp cd qmidiarp git checkout globalstore autoreconf -i ./configure make Best Frank |
|
From: Frank K. <goe...@ya...> - 2011-12-24 13:55:22
|
To all who have already grabbed the tarball before two hours ago, may I ask you to grab it again. Although the tarball worked, it contained one wrong source file producing debug output, which is not very clean. Thanks to Nedko who has quickly seen this Apologies....again Frank ----- Mail original ----- > De : Frank Kober <goe...@ya...> > À : "qmi...@li..." <qmi...@li...>; linux-audio-user <lin...@li...>; Linux Audio Announce <lin...@li...>; "qmi...@li..." <qmi...@li...> > Cc : > Envoyé le : Samedi 24 Décembre 2011 9h59 > Objet : [LAU] QMidiArp-0.4.4 released > > One month after the last one, QMidiArp 0.4.4 comes as a bugfix release, > and the only new 'feature' is that the JACK MIDI backend can run > without JACK Transport too. > > Everyone is encouraged to upgrade to this version available at > > http://qmidiarp.sourceforge.net > > With many thanks to the reporters (and christmas wishes of course :) ) > > Frank > > -------------------------------------------------- > direct link: > > http://sourceforge.net/projects/qmidiarp/files/qmidiarp/0.4.4/qmidiarp-0.4.4.tar.bz2/download > > qmidiarp-0.4.4 (2011-12-24) > > New Features > o JACK MIDI backend doesn't require Jack Transport anymore > > Improvements > o Better usability of the sequencer loop marker > o Improved LFO offset slider behavior > o Quantization to the minimum stepwidth in Arp modules active when > changes in Arp patterns occur > > Fixed Bugs > o Crash on startup in JACK MIDI mode on certain systems > o When cloning modules, the current play direction wasn't copied > o Unmatched MIDI event forwarding didn't work with Arp modules > o Typo in english manpage > _______________________________________________ > Linux-audio-user mailing list > Lin...@li... > http://lists.linuxaudio.org/listinfo/linux-audio-user > |
|
From: Frank K. <goe...@ya...> - 2011-12-24 09:00:02
|
One month after the last one, QMidiArp 0.4.4 comes as a bugfix release, and the only new 'feature' is that the JACK MIDI backend can run without JACK Transport too. Everyone is encouraged to upgrade to this version available at http://qmidiarp.sourceforge.net With many thanks to the reporters (and christmas wishes of course :) ) Frank -------------------------------------------------- direct link: http://sourceforge.net/projects/qmidiarp/files/qmidiarp/0.4.4/qmidiarp-0.4.4.tar.bz2/download qmidiarp-0.4.4 (2011-12-24) New Features o JACK MIDI backend doesn't require Jack Transport anymore Improvements o Better usability of the sequencer loop marker o Improved LFO offset slider behavior o Quantization to the minimum stepwidth in Arp modules active when changes in Arp patterns occur Fixed Bugs o Crash on startup in JACK MIDI mode on certain systems o When cloning modules, the current play direction wasn't copied o Unmatched MIDI event forwarding didn't work with Arp modules o Typo in english manpage |
|
From: Frank K. <goe...@ya...> - 2011-12-20 19:42:36
|
Hi there, due to the big bug crashing qmidiarp for some of you at startup I think the best would be a bugfix release soon. There are a couple of other small issues that I have fixed since 0.4.3 in git, and if you find the time please check out the current git version and let me know if it works as expected. Don't hesitate to report also small issues and ideas so that we can hopefully end the year with a proper qmidiarp version. Have it a try, best regards Frank |
|
From: Frank K. <goe...@ya...> - 2011-12-05 21:57:49
|
Dear all, as reported by some users, in certain cases QMidiArp-0.4.3 crashed with a floating point exception directly on startup when used with JACK MIDI. This exposed only on a few systems, at least one of them AVLinux (unfortunately not mine), but is still a big bug due to a missing initialization. It is now fixed by a patch that can be found here: http://sourceforge.net/projects/qmidiarp/files/qmidiarp/0.4.3/qmidiarp-0.4.3-fix-transport.patch/download It is applied with cd qmidiarp-0.4.3 patch -p1 < qmidiarp-0.4.3-fix-transport.patch Thanks to the two reporters and Robi for the remote access to a system exposing the bug. Frank |
|
From: Sascha S. <ung...@gm...> - 2011-11-22 07:57:26
|
Archlinux Package is in AUR https://aur.archlinux.org/packages.php?ID=11218 greetings and thanks to speps for the package |
|
From: Louigi V. <lou...@gm...> - 2011-11-21 14:18:08
|
Guys, anyone packaged a deb? -- Louigi Verona http://www.louigiverona.ru/ |
|
From: S C R. <rig...@gm...> - 2011-11-21 14:16:07
|
On Sun, Nov 20, 2011 at 12:34 PM, Frank Kober <goe...@ya...> wrote: > Here it is, a new QMidiArp version has arrived! The main new features are > JACK MIDI, > > which is the default backend now, JACK Session support, and a new > in-sequence loop > > marker that can be used to bounce the play direction or to loop at a > mouse-clicked > > position in the sequence. Note that you can still get the alsa backend by > starting with > qmidiarp -a . > > The full list of noticeable changes is below. > > Thanks again to all having reported ideas and bugs and given their support. > > > Masters of the step sequencer, Enjoy! > > I've been playing around with the new release a bit this morning and I pleased to say that I haven't noticed any of the jitter issues I was experiencing a few months ago with the earlier releases. Great work! --Steve |
|
From: Frank K. <goe...@ya...> - 2011-11-20 18:34:57
|
Here it is, a new QMidiArp version has arrived! The main new features are JACK MIDI, which is the default backend now, JACK Session support, and a new in-sequence loop marker that can be used to bounce the play direction or to loop at a mouse-clicked position in the sequence. Note that you can still get the alsa backend by starting with qmidiarp -a . The full list of noticeable changes is below. Thanks again to all having reported ideas and bugs and given their support. Masters of the step sequencer, Enjoy! ----------- Feedback as usual to qmi...@li... or on the IRC #qmidiarp Website with documentation: http://qmidiarp.sourceforge.net ----------- New Features 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 o New user positionable loop marker in Seq module. The marker is placed by left or right mouse click on the bottom cursor line of the sequencer and represents an additional return/loop point. It can be removed again by clicking in the bottom left or right area of the Seq screen. o Triggered one-shot play of LFO and Seqs improved o JACK MIDI backend available. This is now default, use the -a option for getting the ALSA backend o JACK Session support when using JACK MIDI backend Fixed Bugs o A rounding error led to desync when Arps were used with groove shift o MIDI controls for Groove did not initialize upon "New..." o MIDI Controllers assigned to multiple destinations stopped at the first one encountered and ignored all others General Changes o JACK MIDI is now the default backend, -a option enables ALSA backend o Obsolete .qma text file import removed |
|
From: Frank K. <goe...@ya...> - 2011-11-03 22:49:44
|
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 |
|
From: Frank K. <goe...@ya...> - 2011-08-28 12:53:31
|
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 |
|
From: Sascha S. <ung...@gm...> - 2011-07-17 20:41:41
|
Just if other users stumble about this problem, too. I tried configuring QMidiArp with a couple of sequences to use an incoming midi clock signal from Renoise. Using R. it only worked with the "trigger" and "restart" checkbox UNCHECKED, otherwidse qmidiarp won't start. With other programs like seq24 it was not nessesary to uncheck these boxes. greetings, sascha |
|
From: Sascha S. <ung...@gm...> - 2011-07-10 16:26:00
|
got it, compiled it and it runs fine on my arch. seems to start a bit faster. nice new display features :) will test more this evening thanks, sascha 2011/7/10 Frank Kober <goe...@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/ > > ------------------------------------------------------ > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Qmidiarp-user mailing list > Qmi...@li... > https://lists.sourceforge.net/lists/listinfo/qmidiarp-user > |
|
From: Frank K. <goe...@ya...> - 2011-07-10 08:44:29
|
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/ ------------------------------------------------------ |
|
From: Frank K. <goe...@ya...> - 2011-06-24 18:03:31
|
> Probably a dumb question, but how to check out the git version? > No dumb question git clone git://qmidiarp.git.sourceforge.net/gitroot/qmidiarp/qmidiarp cd qmidiarp autoreconf -i ./configure make sudo make install ---- Frank |
|
From: S C R. <rig...@gm...> - 2011-06-24 16:42:22
|
On Wed, Jun 15, 2011 at 4:01 PM, Frank Kober <goe...@ya...> wrote: > OK thanks again Steve, that rules out some suspects. I'll have to have a closer look, > I beleive one other person has had similar problems, and they seem to > be appearing only on some systems, and, strangely not with other alsa sequencers, > so a fix must exist in some way. > For the time being I can only recommend checking out the latest git version that > has one transport start fix that appeared only when seq24 was in the jack transport > group, probably won't fix your issue though. > I'll let you know if there is a fix in sight > > Others, please report if you have similar timing jitter issues. > > > Frank > Probably a dumb question, but how to check out the git version? --Steve |
|
From: Frank K. <goe...@ya...> - 2011-06-20 20:07:06
|
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 |
|
From: Frank K. <goe...@ya...> - 2011-06-15 21:43:30
|
----- Mail original ----- > De : S C Rigler <rig...@gm...> > À : Frank Kober <goe...@ya...> > Cc : ""qmi...@li..."" <qmi...@li...> > Envoyé le : Mercredi 15 Juin 2011 14h33 > Objet : Re: Re : Re : Re : [Qmidiarp-user] Feature Request: Export Functionality [...Timing issues...] I remembered this LAU thread about timing in ALSA seq, and particularly one info from Pedro might be useful to find out more about timers used in ALSA seq. Maybe the timers used by different seq queues differ on your system? ----------------------------LAU Message------------------------------ Re: Is ALSA using hrtimer? by Pedro Lopez-Cabanillas :: Rate this Message: | View Threaded | Show Only this Message On Thursday, May 27, 2010, Grant wrote: > I have hrtimer support compiled into my kernel, but when I watch 'top' > while music is playing I can see that 'timer' uses CPU cycles but > 'hrtimer' never does. How can I find out if ALSA is using hrtimer? > > - Grant In addition to Clemens' message, ALSA MIDI sequencer can use several timer sources. To see which ALSA timers are available, use a command like this: $ cat /proc/asound/timers When a program is using the ALSA MIDI sequencer, you can query the timers assigned to each queue using another command: $ cat /proc/asound/seq/timer Alternatively, the utility "drumstick-sysinfo" [1] shows this information using a friendly format. Regards, Pedro |
|
From: Frank K. <goe...@ya...> - 2011-06-15 21:01:22
|
----- Mail original ----- > De : S C Rigler <rig...@gm...> > À : Frank Kober <goe...@ya...> > Cc : ""qmi...@li..."" <qmi...@li...> > Envoyé le : Mercredi 15 Juin 2011 14h33 > Objet : Re: Re : Re : Re : [Qmidiarp-user] Feature Request: Export Functionality > > On Tue, Jun 14, 2011 at 1:38 PM, Frank Kober <goe...@ya...> wrote: >> Thanks Steve, >> the examples clearly show the problem, however more questions before > digging into what this could be (I clearly don't reproduce it here on an old > 2.6.33 rt kernel): >> 1) Does the jitter appear as well when not using jack transport sync? No > proof needed if your impression is so. >> 2) What is your JACK latency ? >> 3) Do you use a CPU frequency governor like ondemand that might vary CPU > frequency during play? >> >> Reasons for my questions are, I'd like to know whether qmidiarp just > poorly syncs due to some reason or whether the ALSA timer for some reason is > unstable >> >> Thanks in advance >> Frank >> > > I experimented with it a bit more and I can't for sure say if there is > a difference between using jack transport sync and the internal timer. > It sounds like it's in time without jack transport sync, but to > compare, I tried using jack transport sync with no accompaniment and > it sounded fine there as well. So it seems that it's just when there > are other parts playing that it sounds like it's not in time. > > But anyways, to answer your other questions: I went back to a rt patch > 2.6.33 kernel to record the examples. Just FYI, my laptop isn't > completely supported until 2.6.35 and one of the workarounds I need to > keep it from locking up on older kernels is to boot with "nohpet". > The behavior is the same, though, between 2.6.39 and 2.6.33-rt. > > According to Qjackctl, the latency is 2.9ms (64 frames/period, 2 > periods/buffer). The CPU frequency governor is configured for > "performance". > > --Steve OK thanks again Steve, that rules out some suspects. I'll have to have a closer look, I beleive one other person has had similar problems, and they seem to be appearing only on some systems, and, strangely not with other alsa sequencers, so a fix must exist in some way. For the time being I can only recommend checking out the latest git version that has one transport start fix that appeared only when seq24 was in the jack transport group, probably won't fix your issue though. I'll let you know if there is a fix in sight Others, please report if you have similar timing jitter issues. Frank |
|
From: S C R. <rig...@gm...> - 2011-06-15 12:34:03
|
On Tue, Jun 14, 2011 at 1:38 PM, Frank Kober <goe...@ya...> wrote: > Thanks Steve, > the examples clearly show the problem, however more questions before digging into what this could be (I clearly don't reproduce it here on an old 2.6.33 rt kernel): > 1) Does the jitter appear as well when not using jack transport sync? No proof needed if your impression is so. > 2) What is your JACK latency ? > 3) Do you use a CPU frequency governor like ondemand that might vary CPU frequency during play? > > Reasons for my questions are, I'd like to know whether qmidiarp just poorly syncs due to some reason or whether the ALSA timer for some reason is unstable > > Thanks in advance > Frank > I experimented with it a bit more and I can't for sure say if there is a difference between using jack transport sync and the internal timer. It sounds like it's in time without jack transport sync, but to compare, I tried using jack transport sync with no accompaniment and it sounded fine there as well. So it seems that it's just when there are other parts playing that it sounds like it's not in time. But anyways, to answer your other questions: I went back to a rt patch 2.6.33 kernel to record the examples. Just FYI, my laptop isn't completely supported until 2.6.35 and one of the workarounds I need to keep it from locking up on older kernels is to boot with "nohpet". The behavior is the same, though, between 2.6.39 and 2.6.33-rt. According to Qjackctl, the latency is 2.9ms (64 frames/period, 2 periods/buffer). The CPU frequency governor is configured for "performance". --Steve |
|
From: Frank K. <goe...@ya...> - 2011-06-14 18:38:46
|
> Yes, this is 0.4.1 with the patch applied. Originally I had Qtractor > using set to "default" for the queue timer, but I've since it > changed > it to "System Timer (1000HZ)"...probably the same thing. > > I uploaded a couple of examples to my dropbox. They are all using > Qtractor as the transport master and at 115BPM recorded into MixBus > with Hydrogen doing a click: > Thanks Steve, the examples clearly show the problem, however more questions before digging into what this could be (I clearly don't reproduce it here on an old 2.6.33 rt kernel): 1) Does the jitter appear as well when not using jack transport sync? No proof needed if your impression is so. 2) What is your JACK latency ? 3) Do you use a CPU frequency governor like ondemand that might vary CPU frequency during play? Reasons for my questions are, I'd like to know whether qmidiarp just poorly syncs due to some reason or whether the ALSA timer for some reason is unstable Thanks in advance Frank |
|
From: S C R. <rig...@gm...> - 2011-06-14 00:27:27
|
On Mon, Jun 13, 2011 at 4:57 AM, Frank Kober <goe...@ya...> wrote: > > > ----- Mail original ----- >> De : S C Rigler <rig...@gm...> >> À : Frank Kober <goe...@ya...> >> Cc : "qmi...@li..." <qmi...@li...> >> Envoyé le : Lundi 13 Juin 2011 1h55 >> Objet : Re: Re : [Qmidiarp-user] Feature Request: Export Functionality > > > > Another question that came to my mind: Which qmidiarp version are you using? > If it is 0.4.1 be sure to have the patch applied before building > Cheers > Yes, this is 0.4.1 with the patch applied. Originally I had Qtractor using set to "default" for the queue timer, but I've since it changed it to "System Timer (1000HZ)"...probably the same thing. I uploaded a couple of examples to my dropbox. They are all using Qtractor as the transport master and at 115BPM recorded into MixBus with Hydrogen doing a click: The original "source arp" with QMidiArp sequencing Yoshimi: http://dl.dropbox.com/u/9838571/qmidiarp_arp.mp3 The first 4 bars of the "source arp" cleaned up and looped 4 times in Qtractor sequencing Yoshimi: http://dl.dropbox.com/u/9838571/qtractor_arp.mp3 The same 4 bars as before, this time with seq24 sequencing Yoshimi: http://dl.dropbox.com/u/9838571/seq24_arp.mp3 Thanks, Steve |
|
From: Frank K. <goe...@ya...> - 2011-06-13 12:06:07
|
----- Mail original ----- > De : S C Rigler <rig...@gm...> > À : Frank Kober <goe...@ya...> > Cc : "qmi...@li..." <qmi...@li...> > Envoyé le : Lundi 13 Juin 2011 1h55 > Objet : Re: Re : [Qmidiarp-user] Feature Request: Export Functionality Another question that came to my mind: Which qmidiarp version are you using? If it is 0.4.1 be sure to have the patch applied before building Cheers |
|
From: Sascha S. <ung...@gm...> - 2011-06-13 11:15:53
|
Hi Frank 2011/6/13 Frank Kober <goe...@ya...>: > Hi Sascha, > > > > ----- Mail original ----- >> De : Sascha Schneider <ung...@gm...> >> À : qmidiarp-user <qmi...@li...> >> Cc : >> Envoyé le : Lundi 13 Juin 2011 10h15 >> Objet : [Qmidiarp-user] Feature Request >> >> Would it be possible to have some settings >> that let you choose the actual midi-interface to use as 1 or 2?? >> Or let QMidiArp use hardware midi-interfaces in addition?? >> I'm working with hw-synths and have to use QJackCtl to route the >> midi-connections, cause Alsa-Patchbay crashes on my systems. >> I have one Midi-pair on my Audiophile 2496 and 2 Midi-Pairs on my >> Edirol UM-2G and I would love to route directly from within qmidiarp. >> > > I understand your need for routing, but: What's the point of not using the venerable > QJackCtl for this? > It even gives you a patchbay to restore connections at every time you launch it. > You could also use Ladish and a2jmidid for getting your studios routed. > > Anyway, I won't do MIDI routing from within QMidiArp. > Developing this internally would just be a duplicate of other efforts don't you think? > Cheers > Frank > Yes sorry, big missunderstanding of my side, should RTFM more. After setting autostart of Jack in Qjackctl to no I can simply do the midi-routing with it. Thanks, greetings from belgium |
|
From: Frank K. <goe...@ya...> - 2011-06-13 09:19:44
|
Hi Sascha, ----- Mail original ----- > De : Sascha Schneider <ung...@gm...> > À : qmidiarp-user <qmi...@li...> > Cc : > Envoyé le : Lundi 13 Juin 2011 10h15 > Objet : [Qmidiarp-user] Feature Request > > Would it be possible to have some settings > that let you choose the actual midi-interface to use as 1 or 2?? > Or let QMidiArp use hardware midi-interfaces in addition?? > I'm working with hw-synths and have to use QJackCtl to route the > midi-connections, cause Alsa-Patchbay crashes on my systems. > I have one Midi-pair on my Audiophile 2496 and 2 Midi-Pairs on my > Edirol UM-2G and I would love to route directly from within qmidiarp. > I understand your need for routing, but: What's the point of not using the venerable QJackCtl for this? It even gives you a patchbay to restore connections at every time you launch it. You could also use Ladish and a2jmidid for getting your studios routed. Anyway, I won't do MIDI routing from within QMidiArp. Developing this internally would just be a duplicate of other efforts don't you think? Cheers Frank |
