Forum rss-feed

Forum

Pico: Pico MIDI only setup

Most Recent

written by: geert

Hi Paugui,

I understand what you want to do, the problem here is that there a large number of ways to handle this, most probably dependent on the preference of the player, the instrument, playing style, etc. You could want to simply add data on several data stream and as soon as the maximum is reached, keep it there, you could want to average, you could want them to be mutually exclusive based on different approaches (first started, last ongoing, ...), you could have a deriviate value of one (velocity for pressure for instance) be a constant baseline for the other data streams, ... and so on.

While we haven't discussed this particular feature record amongst us yet (I'm back from vacation tomorrow), I personally think the place for such a feature is not in the MIDI routing matrix. EigenD allows access to the data streams in between agents, and I think it's probably going to be better to have a series of small agents that treat the data of several signals and combine that into one. This would then be connected to the routing matrix and converted to MIDI CC.

Writing such agents should be totally possible as an open-source effort, so maybe someone at the developer conference will pick it up as a project and it could become a new feature soon.

Take care,

Geert

written by: carvingCode

Mon, 24 Oct 2011 20:56:16 +0100 BST

When this setup is loaded, I get no feedback from the Pico when trying to select MIDI output, etc. Just no clue how to proceed.

I'm wondering, is this intended for Windows7?


written by: geert

Mon, 24 Oct 2011 21:04:04 +0100 BST

@CarvingCode, you'll have to install a MIDI driver on Windows for this to work, virtual or real. People have been using LoopBe as a virtual MIDI device on Windows, Mac has this built in.


written by: carvingCode

Tue, 25 Oct 2011 01:14:14 +0100 BST

I've got LoopBe installed. I use MIDI out of the Pico in my setups - no problem. I just don't have a clue what I'm to do with your MIDI setup, Geert. Sorry.


written by: geert

Tue, 25 Oct 2011 06:32:45 +0100 BST

@CarvingCode, it doesn't provide much more than MIDI in the factory setups, mainly the scroll keys are replaced my 3D MIDI controller keys. Some of the features that are configurable through the main mode key, moved to Stage widgets instead. Did you browse for your MIDI port by pressing the appropriate button in Stage?


written by: carvingCode

Wed, 26 Oct 2011 00:28:16 +0100 BST

I don't see a 'MIDI Port' option in the Stage loaded from this setup. What would be useful is something like the Quick Reference guide. With that, I'm able to see what every key and combination should do in the standard setup. With the MIDI setup, and even the '4 VST/4MIDI' setup, I'm just not able to see what the keys are doing.


written by: geert

Wed, 26 Oct 2011 06:17:52 +0100 BST

@carvingCode, please redownload it, I think you might have the first version that didn't have the browse midi button in Stage. There's not going to be quick reference of this setup, it is not a factory setup and one we created partly to show how to build a setup from scratch using Belcanto. The finished setup is a just a nice side effect for people that want a MIDI only system. In this setup everything is configured through Stage or Belcanto, that's the approach, not keys.

Best regards,

Geert


written by: paugui

Sat, 7 Jan 2012 12:33:49 +0000 GMT

I was trying to use the Pico today with my Korg Radias but I'm not being able to make the strip do anything useful...
When I tried to assign it to Pitch Wheel, the only thing I get from moving my fingers on it is some kind of added noise, but no real change in pitch...
I just used the MIDI Behaviour menu and just used the settings suggested by the software....
What shall I do in order to obtain a perfect pitch bending?


Thanks in advance,
Best

Paulo


written by: NothanUmber

Sat, 7 Jan 2012 14:13:35 +0000 GMT

Perhaps more pitch bend events were generated than the synth can handle - in that case try to play with the data decimation settings in the midi converter dialog.
Or you didn't press the strip firm enough or reached the non-reactive area at the ends.


written by: paugui

Sat, 7 Jan 2012 14:50:37 +0000 GMT

The only pitchbend effects I'm generating is the standard one with the keys (I guess it's not even possible to remove that one, right?), and the Strip Position one...
The strip works pretty well for the software, so that shouldn't be the problem...

I tried to make the breath send as pitch wheel too, but the results are pretty similar...

So far, the only thing I could assign was the breath to dampler on/off...
The pitch wheel messages don't seem to be sent out right...


I guess I'll just try with a different synth then...


written by: paugui

Sat, 7 Jan 2012 15:07:11 +0000 GMT

I was trying with my Yamaha FS1r and the strange noise with the pitch wheel stays on...

But on at least one patch the, CC General Purpose Controller 1 to which the strip is assign controls the filter and I can definitely notice that it works pretty smoothly...
I tried to apply that one to the breath and it works pretty well too...


written by: carvingCode

Sat, 7 Jan 2012 15:13:50 +0000 GMT

I'm just beginning to work with the MIDI Routing controls, so can't offer much assistance yet. I do notice that different synths and different paths within the synths offer different controls. So it probably is a matter of making sure to match up the MIDI Router control to the synth/patch control.

Again, not much help. Sorry.

Randy


written by: paugui

Sat, 7 Jan 2012 15:18:38 +0000 GMT

I tried to remove the pitchbend from the keys and now the strip works pretty well.

I was trying to use the strip and the breathe at the same the time, with the filter as I mentioned before, and I could definitely hear some noise when using both at the same time...

Will it be possible to correct this in a future upgrade?
Is that sometimes it can be useful to use two controls for the same thing, but it seems it doesn't handle it that well...


written by: john

Sat, 7 Jan 2012 15:33:53 +0000 GMT

This sounds more like an issue with the synth you're driving or the routing you've set up than anything that we could fix in EigenD. You can drive one controller from two sources, the only difference is that the data rate goes up, and values can jump around as the two sources send the data.

If you're getting some kind of spurious noise then this could be caused either by something being routed to an internal control on the synth that makes that sound or, as NothanUmber suggested, more probably by too high a data rate being sent to the device, ie, more data than it can handle. It would be worth turning up the data decimation rate in the routing matrix to see if that helps. Quite a few synths are just not able to cope with much performance data as they're designed for an earlier age when it all went a lot slower. The fact that it improved when you sent less pitchbend data by turning it off on the keys is a pretty big clue pointing in this direction.


written by: paugui

Sat, 7 Jan 2012 16:31:05 +0000 GMT

What I noticed is that, if I try to have 2 different controls for the same thing and both are in use, the result is not that good.
And both synths I've tried so far aren't exactly old synths (I even think the Radias is still in production), so there shouldn't be a problem handling MIDI controls...

I understand that if you have two sources, the amount of data you get is bigger.
But if the data is mixed inside the software, so that only the total result is output to the synth, wouldn't this solve the problem?
I'm not sure if other problems wouldn't arise from this, but it should be possible to do something like this, no?


written by: geert

Sat, 7 Jan 2012 17:37:59 +0000 GMT

@paugui, there isn't much that can be done about this, when you use two controls for the same MIDI CC parameter, they will independently send different values for the same MIDI CC parameter which will make the control in the synth jump around very quickly between whatever values are being sent by the two controls. This can often result into weird noise and erratic sounding behavior. This is the case for anything that sends out data for the same MIDI CC when you use them at the same time.


written by: paugui

Sun, 8 Jan 2012 01:08:50 +0000 GMT

I understand that and it definitely makes sense that is the cause of the noise.

But what I meant is... shouldn't it be possible to process the MIDI signal before in order to get rid of the overload of data?
If the signal is merged inside the software, I wouldn't expect any problem to occur.
But I've never done any programming involving MIDI...

That's basically what I was wondering if was possible or not.


written by: keyman

Sun, 8 Jan 2012 03:19:38 +0000 GMT

Hi, paugui
As @ NothanUmber mention already - Decimate !!
either globally - Settings - minimum data decimation
or per control - Data decimation

It just works...
Give you an example; connecting for instance the Pico with the Ipad using the camera connection kit, one has to decimate to use controls or it simply don't give you any sound at all.

A bit technical (from eigenlabs site):
Keys
Sampled at 2000 samples/second, per key.
10 bit (1024 values) resolution.


written by: geert

Mon, 9 Jan 2012 08:54:35 +0000 GMT

Hi Paugui,

I understand what you want to do, the problem here is that there a large number of ways to handle this, most probably dependent on the preference of the player, the instrument, playing style, etc. You could want to simply add data on several data stream and as soon as the maximum is reached, keep it there, you could want to average, you could want them to be mutually exclusive based on different approaches (first started, last ongoing, ...), you could have a deriviate value of one (velocity for pressure for instance) be a constant baseline for the other data streams, ... and so on.

While we haven't discussed this particular feature record amongst us yet (I'm back from vacation tomorrow), I personally think the place for such a feature is not in the MIDI routing matrix. EigenD allows access to the data streams in between agents, and I think it's probably going to be better to have a series of small agents that treat the data of several signals and combine that into one. This would then be connected to the routing matrix and converted to MIDI CC.

Writing such agents should be totally possible as an open-source effort, so maybe someone at the developer conference will pick it up as a project and it could become a new feature soon.

Take care,

Geert



Please log in to join the discussions