Wow, you've been busy!

sent from a mobile device...

Hi,

sound great! I got some build errors after updating form git, I will do a fresh clone later to sort it out and will report about possible problems.

when building, should I add or not the

+= rtmidi

option now?

tarmo

On Wednesday 06 November 2013 21:00:10 Andres Cabrera wrote:

Hi,

I've added internal MIDI support in CsoundQt instead of relying on the Csound rtMIDI modules. This seems to be working better, but I would like to hear from more people testing. The code is up on git and the nightly build for OS X now has this fix:

https://sourceforge.net/projects/qutecsound/files/CsoundQt/nightly-osx/

I hope this lays this issue to rest.

Cheers,
Andrés

Hi,

I got the new version built now. At first I failed since I had steill the headres of rtmidi-1.15 in my source tree and the new code does not work with that any more. Should there be some version checking in the code?

I dowloaded rtmidi-2.01, declared the correct rtmidi path and problems solved.

And it works! (linux, csound 6.01), Thanks!

I can attach a MIDI controller knobs to widgets and it works fine.

The greatest thing for me is now, that it is now possible to use the same MIDI device for both csound input AND controlling widgets (before it needed some tricks through virtual midi)!

I am a bit confused still about the new midi section ConfigWindow ->Run Tab

It is confusing, what options are meant for internal midi (controlling widgets) and which for using midi for Csound. Before it was clearly separated

I understand that "MIDI input interface" stands for intenal midi, right?

What is "MIDI Output interface" then? What is CsoundQt:0 option amoung the interfaces?

And I assume, I can define the Csound MIDI interfaces only when I check "Use Csound MIDI modules"? Or how can I specify that I want use module "virtual"?

When I select "None" for MIDI input device and check "Use Csound MIDI modules" and select Module "virtual" or also "alsaraw" and correct input device, there is no midi input in csound.

Seems that to be able to get also MIDI input in Csound, MIDI intput interface must be chosen. But there is no "virtual"?

When I select correct MIDI input interface, it actually does not matter, If I check "Use Csound MIDI modules" or not at all. It works both ways well, but it does not seem to have any influence.

But this is only external things, with some clarifications, that is no problem, of course.

tarmo

On Wednesday 06 November 2013 21:00:10 Andres Cabrera wrote:

Hi,

I've added internal MIDI support in CsoundQt instead of relying on the Csound rtMIDI modules. This seems to be working better, but I would like to hear from more people testing. The code is up on git and the nightly build for OS X now has this fix:

https://sourceforge.net/projects/qutecsound/files/CsoundQt/nightly-osx/

I hope this lays this issue to rest.

Cheers,
Andrés

Hi,

I got myself finally testing the CsoundQt MIDI again.

In short: it works very well (below description of all the tests).

Only one thing, user has to know: you cannot select a MIDI device as MIDI input interface AND select it also under Csound MIDI modules ( at least with alsaraw) - then csound gives error:

ALSA: error opening MIDI input device: 'hw:4,0,0'

*** error opening MIDI in device: -1 (Unknown MIDI error)

In that case don't check "Use MIDI modules", your chosen MIDI input device will work for csound anyway, too.

All other combinations, including using physical and virtual device and two midi devices, worked without any problems.

I noticed also in the git log that there were commits "Added midi learn functionality" and "Added midi control for buttons" but I did not figure out how to use those (assinging midi cc to button did not have any affect), niehter midi lear dialog did not fire up when I selected a widget (although I saw message MidiLearnDialog::setCurrentWidget in the console.

I did not have time to dig into code, nut these funcitonalities would absolutely great! Very exciting.

Thanks a lot!

tarmo

---------

CsoundQt midi tests

A one external MIDI interface

1) MIDI input interface chosen, Use MIDI modules unchecked

- play in CsoundQt:

midi input from the physical device works for midi in csd and also controlling widgets works (Keystation)

- run in term - no MIDI input (as expected)

2) MIDI input interface chosen, Use MIDI modules checked, alsaraw, Input Device chosen

- play in CsoundQt:

Error:

ALSA: error opening MIDI input device: 'hw:4,0,0'

*** error opening MIDI in device: -1 (Unknown MIDI error)

- run in Term:

Error:

ALSA: error opening MIDI input device: 'hw:4,0,0'

*** error opening MIDI in device: -1 (Unknown MIDI error)

3) MIDI input interface "None", Use MIDI modules checked, alsaraw, Input Device chosen:

- play in CsoundQt:

playing CSound instruments works, controlling widgets not (as expected)

- run in Term:

playing CSound instruments works

4) MIDI input interface "None", Use MIDI modules checked, virtual:

wokrs both ways - virtual keyboard nicely shown (not controlling the widgets, of course)

5) MIDI input interface chosen, Use MIDI modules checked, virtual:

CsoundQt - virtual keyboard controls csound and physical controller widgets. Cool!

B Two midi pgysical MIDI devices (one keyboard, other controller)

1) One device for CsoundQt and one for Csound modules - works fearly well, in some point the controller for widgets stopped working. Detaching and reconnecting the device helped (ie not Csound/CsoundQt problen,m probably hardware)

----------

On Thursday 07 November 2013 10:00:41 Andres Cabrera wrote:

Hi Tarmo,

Using Csound rt MIDI modules like "virtual" should now work again.

Cheers,
Andrés

On Thu, Nov 7, 2013 at 4:26 AM, Tarmo Johannes <tarmo.johannes@otsakool.edu.ee> wrote:

Hi,

I got the new version built now. At first I failed since I had steill the headres of rtmidi-1.15 in my source tree and the new code does not work with that any more. Should there be some version checking in the code?

I dowloaded rtmidi-2.01, declared the correct rtmidi path and problems solved.

And it works! (linux, csound 6.01), Thanks!

I can attach a MIDI controller knobs to widgets and it works fine.

The greatest thing for me is now, that it is now possible to use the same MIDI device for both csound input AND controlling widgets (before it needed some tricks through virtual midi)!

I am a bit confused still about the new midi section ConfigWindow ->Run Tab

It is confusing, what options are meant for internal midi (controlling widgets) and which for using midi for Csound. Before it was clearly separated

I understand that "MIDI input interface" stands for intenal midi, right?

What is "MIDI Output interface" then? What is CsoundQt:0 option amoung the interfaces?

And I assume, I can define the Csound MIDI interfaces only when I check "Use Csound MIDI modules"? Or how can I specify that I want use module "virtual"?

When I select "None" for MIDI input device and check "Use Csound MIDI modules" and select Module "virtual" or also "alsaraw" and correct input device, there is no midi input in csound.

Seems that to be able to get also MIDI input in Csound, MIDI intput interface must be chosen. But there is no "virtual"?

When I select correct MIDI input interface, it actually does not matter, If I check "Use Csound MIDI modules" or not at all. It works both ways well, but it does not seem to have any influence.

But this is only external things, with some clarifications, that is no problem, of course.

tarmo

On Wednesday 06 November 2013 21:00:10 Andres Cabrera wrote:

Hi,

I've added internal MIDI support in CsoundQt instead of relying on the Csound rtMIDI modules. This seems to be working better, but I would like to hear from more people testing. The code is up on git and the nightly build for OS X now has this fix:

https://sourceforge.net/projects/qutecsound/files/CsoundQt/nightly-osx/

I hope this lays this issue to rest.

Cheers,
Andrés

thanks, tarmo -- this report is extremly useful.
best -
	joachim


Am 29.11.2013 09:18, schrieb Tarmo Johannes:
> Hi,
>
> I got myself finally testing the CsoundQt MIDI again.
>
> In short: it works very well (below description of all the tests).
>
> Only one thing, user has to know: you cannot select a MIDI device as
> MIDI input interface AND select it also under Csound MIDI modules ( at
> least with alsaraw) - then csound gives error:
>
> ALSA: error opening MIDI input device: 'hw:4,0,0'
>
> *** error opening MIDI in device: -1 (Unknown MIDI error)
>
> In that case don't check "Use MIDI modules", your chosen MIDI input
> device will work for csound anyway, too.
>
> All other combinations, including using physical and virtual device and
> two midi devices, worked without any problems.
>
> I noticed also in the git log that there were commits "Added midi learn
> functionality" and "Added midi control for buttons" but I did not figure
> out how to use those (assinging midi cc to button did not have any
> affect), niehter midi lear dialog did not fire up when I selected a
> widget (although I saw message MidiLearnDialog::setCurrentWidget in the
> console.
>
> I did not have time to dig into code, nut these funcitonalities would
> absolutely great! Very exciting.
>
> Thanks a lot!
>
> tarmo
>
> ---------
>
> CsoundQt midi tests
>
> A one external MIDI interface
>
> 1) MIDI input interface chosen, Use MIDI modules unchecked
>
> - play in CsoundQt:
>
> midi input from the physical device works for midi in csd and also
> controlling widgets works (Keystation)
>
> - run in term - no MIDI input (as expected)
>
> 2) MIDI input interface chosen, Use MIDI modules checked, alsaraw, Input
> Device chosen
>
> - play in CsoundQt:
>
> Error:
>
> ALSA: error opening MIDI input device: 'hw:4,0,0'
>
> *** error opening MIDI in device: -1 (Unknown MIDI error)
>
> - run in Term:
>
> Error:
>
> ALSA: error opening MIDI input device: 'hw:4,0,0'
>
> *** error opening MIDI in device: -1 (Unknown MIDI error)
>
> 3) MIDI input interface "None", Use MIDI modules checked, alsaraw, Input
> Device chosen:
>
> - play in CsoundQt:
>
> playing CSound instruments works, controlling widgets not (as expected)
>
> - run in Term:
>
> playing CSound instruments works
>
> 4) MIDI input interface "None", Use MIDI modules checked, virtual:
>
> wokrs both ways - virtual keyboard nicely shown (not controlling the
> widgets, of course)
>
> 5) MIDI input interface chosen, Use MIDI modules checked, virtual:
>
> CsoundQt - virtual keyboard controls csound and physical controller
> widgets. Cool!
>
> B Two midi pgysical MIDI devices (one keyboard, other controller)
>
> 1) One device for CsoundQt and one for Csound modules - works fearly
> well, in some point the controller for widgets stopped working.
> Detaching and reconnecting the device helped (ie not Csound/CsoundQt
> problen,m probably hardware)
>
> ----------
>
> On Thursday 07 November 2013 10:00:41 Andres Cabrera wrote:
>
> Hi Tarmo,
>
> Using Csound rt MIDI modules like "virtual" should now work again.
>
> Cheers,
> Andrés
>
>
>
> On Thu, Nov 7, 2013 at 4:26 AM, Tarmo Johannes
> >
> wrote:
>
> Hi,
>
> I got the new version built now. At first I failed since I had steill
> the headres of rtmidi-1.15 in my source tree and the new code does not
> work with that any more. Should there be some version checking in the code?
>
> I dowloaded rtmidi-2.01, declared the correct rtmidi path and problems
> solved.
>
> And it works! (linux, csound 6.01), Thanks!
>
> I can attach a MIDI controller knobs to widgets and it works fine.
>
> The greatest thing for me is now, that it is now possible to use the
> same MIDI device for both csound input AND controlling widgets (before
> it needed some tricks through virtual midi)!
>
> I am a bit confused still about the new midi section ConfigWindow ->Run Tab
>
> It is confusing, what options are meant for internal midi (controlling
> widgets) and which for using midi for Csound. Before it was clearly
> separated
>
> I understand that "MIDI input interface" stands for intenal midi, right?
>
> What is "MIDI Output interface" then? What is CsoundQt:0 option amoung
> the interfaces?
>
> And I assume, I can define the Csound MIDI interfaces only when I check
> "Use Csound MIDI modules"? Or how can I specify that I want use module
> "virtual"?
>
> When I select "None" for MIDI input device and check "Use Csound MIDI
> modules" and select Module "virtual" or also "alsaraw" and correct input
> device, there is no midi input in csound.
>
> Seems that to be able to get also MIDI input in Csound, MIDI intput
> interface must be chosen. But there is no "virtual"?
>
> When I select correct MIDI input interface, it actually does not matter,
> If I check "Use Csound MIDI modules" or not at all. It works both ways
> well, but it does not seem to have any influence.
>
> But this is only external things, with some clarifications, that is no
> problem, of course.
>
> tarmo
>
> On Wednesday 06 November 2013 21:00:10 Andres Cabrera wrote:
>
> Hi,
>
> I've added internal MIDI support in CsoundQt instead of relying on the
> Csound rtMIDI modules. This seems to be working better, but I would like
> to hear from more people testing. The code is up on git and the nightly
> build for OS X now has this fix:
>
> https://sourceforge.net/projects/qutecsound/files/CsoundQt/nightly-osx/
>
> I hope this lays this issue to rest.
>
> Cheers,
> Andrés
>
>
>
>
>
>

Hi,

> On Friday 29 November 2013 06:48:51 Andres Cabrera wrote:
> 
> I'm surprised that the virtual keyboard controls the CsoundQt widgets. This
> is not happening for me, although the virtual keyboard works as expected.
No, I was vague in my explanation, I could not control widgets with virtual, 
just the csd midi.

> 
> 
> To use MIDI learn, go to View->MIDI Learn. This will open a floating window,
> and while this window is visible, you can select a widget and move a
> controller on your MIDI device and it will be assigned. That you didn't
> find it points to an issue of discovery, how do you think we can make this
> feature clearer?
Right, View-MIDI learn is a good place. But it could be also closer to 
widgets, perhaps in the context menu of the Widgets panel and why not also it 
the context menu of a widget?

What about button MIDI control? Does it work for you?

greetings,
tarmo

> 
> Cheers,
> Andrés



On Fri, Nov 29, 2013 at 12:18 AM, Tarmo Johannes 
 wrote:

Hi,
 
I got myself finally testing the CsoundQt MIDI again.
 
In short: it works very well (below description of all the tests).
 
Only one thing, user has to know: you cannot select a MIDI device as MIDI 
input interface AND select it also under Csound MIDI modules ( at least with 
alsaraw) - then csound gives error: 
 
ALSA: error opening MIDI input device: 'hw:4,0,0'
*** error opening MIDI in device: -1 (Unknown MIDI error)
 
In that case don't check "Use MIDI modules", your chosen MIDI input device 
will work for csound anyway, too.
 
All other combinations, including using physical and virtual device and two 
midi devices, worked without any problems.
 
I noticed also in the git log that there were commits "Added midi learn 
functionality" and "Added midi control for buttons" but I did not figure out 
how to use those (assinging midi cc to button did not have any affect), 
niehter midi lear dialog did not fire up when I selected a widget (although I 
saw message MidiLearnDialog::setCurrentWidget in the console. 
I did not have time to dig into code, nut these funcitonalities would 
absolutely great! Very exciting.
 
Thanks a lot!
 
tarmo
 
 
---------
CsoundQt midi tests
 
A one external MIDI interface
 
1) MIDI input interface chosen, Use MIDI modules unchecked
- play in CsoundQt:
midi input from the physical device works for midi in csd and also controlling 
widgets works (Keystation) 
- run in term - no MIDI input (as expected)
 
2) MIDI input interface chosen, Use MIDI modules checked, alsaraw, Input 
Device chosen
 
- play in CsoundQt:
Error:
ALSA: error opening MIDI input device: 'hw:4,0,0'
*** error opening MIDI in device: -1 (Unknown MIDI error)
- run in Term:
Error:
ALSA: error opening MIDI input device: 'hw:4,0,0'
*** error opening MIDI in device: -1 (Unknown MIDI error)
 
 
3) MIDI input interface "None", Use MIDI modules checked, alsaraw, Input 
Device chosen: 
- play in CsoundQt:
playing CSound instruments works, controlling widgets not (as expected)
 
- run in Term:
playing CSound instruments works
 
 
4) MIDI input interface "None", Use MIDI modules checked, virtual:
wokrs both ways - virtual keyboard nicely shown (not controlling the widgets, 
of course) 
 
5) MIDI input interface chosen, Use MIDI modules checked, virtual:
CsoundQt - virtual keyboard controls csound and physical controller widgets. 
Cool!
 
 
B Two midi pgysical MIDI devices (one keyboard, other controller)
1) One device for CsoundQt and one for Csound modules - works fearly well, in 
some point the controller for widgets stopped working. Detaching and 
reconnecting the device helped (ie not Csound/CsoundQt problen,m probably 
hardware) 
 
----------
 
 
 
 
On Thursday 07 November 2013 10:00:41 Andres Cabrera wrote:

Hi Tarmo,


Using Csound rt MIDI modules like "virtual" should now work again.

Cheers,
Andrés




On Thu, Nov 7, 2013 at 4:26 AM, Tarmo Johannes 
 wrote:

Hi,
 
I got the new version built now. At first I failed since I had steill the 
headres of rtmidi-1.15 in my source tree and the new code does not work with 
that any more. Should there be some version checking in the code? 
 
I dowloaded rtmidi-2.01, declared the correct rtmidi path and problems solved.
 
And it works! (linux, csound 6.01), Thanks!
 
I can attach a MIDI controller knobs to widgets and it works fine. 
The greatest thing for me is now, that it is now possible to use the same MIDI 
device for both csound input AND controlling widgets (before it needed some 
tricks through virtual midi)! 
 
 
I am a bit confused still about the new midi section ConfigWindow ->Run Tab
 
It is confusing, what options are meant for internal midi (controlling 
widgets) and which for using midi for Csound. Before it was clearly separated 
 
 
I understand that "MIDI input interface" stands for intenal midi, right?
What is "MIDI Output interface" then? What is CsoundQt:0 option amoung the 
interfaces? 
 
And I assume, I can define the Csound MIDI interfaces only when I check "Use 
Csound MIDI modules"? Or how can I specify that I want use module "virtual"? 
 
When I select "None" for MIDI input device and check "Use Csound MIDI modules" 
and select Module "virtual" or also "alsaraw" and correct input device, there 
is no midi input in csound. 
 
Seems that to be able to get also MIDI input in Csound, MIDI intput interface 
must be chosen. But there is no "virtual"? 
 
When I select correct MIDI input interface, it actually does not matter, If I 
check "Use Csound MIDI modules" or not at all. It works both ways well, but it 
does not seem to have any influence. 
 
 
But this is only external things, with some clarifications, that is no 
problem, of course. 
 
tarmo
 
 
 
 
 
 
 
On Wednesday 06 November 2013 21:00:10 Andres Cabrera wrote:

Hi,


I've added internal MIDI support in CsoundQt instead of relying on the Csound 
rtMIDI modules. This seems to be working better, but I would like to hear from 
more people testing. The code is up on git and the nightly build for OS X now 
has this fix:

https://sourceforge.net/projects/qutecsound/files/CsoundQt/nightly-osx/


I hope this lays this issue to rest.

Cheers,
Andrés