Search Results for 'Nrpn'

[sempervirent]

Yes, everything except a few esoteric things are covered by NRPN. See page 258 in the PDF manual for a couple of exceptions. I don’t think these exceptions are related to actual sound manipulation.

[atom]

allright i’ll use NRPN, i guess they have all messages covered with them but i can’t be really sure, if someone could double-check if all parameters are covered by NRPN messages.

and i’ll get to it soon, i just need to finish some stuff in the engine.

[sempervirent]

Thanks, between this and some further research I understand the technical aspect of NRPN messages a bit better. I looked around and it seems like virtually every DAW [i:2jxd1132]except[/i:2jxd1132] Ableton Live can handle NRPN data. So I guess that’s the way to go. Too bad I just started using Live! Maybe in the next version they will finally meet the MIDI specs of the 1980s…

[atom]

the last question nrpn/sysex

nrpn is a set of 4CC messages put together to create one 14bit message, sysex is non-standard way of sending any amount of any data on the midi wire. NRPN is more likely to be included in any DAW (since it’s pure CC messages). Sysex is always the last on the list, since it’s more complex.

[sempervirent]

[quote:2udl2f89]1) what is the Child ID, Parent ID stuff
2) what’s the Parent Page[/quote:2udl2f89]

I can only guess, but I’d suspect that within their implementation, turning a knob sends an audio-affecting command and also sends a message to the CPU that tells it to draw the GUI for a set of parameters related to the knob that was changed. For example, if you turn the filter cutoff knob, the GUI always redraws to show you that value and a lot of related values.

You can also press the "View" button for some clusters of related elements, which will show the same screen. This lets you peek at a value without turning a knob (and altering a value). For example, each LFO has its own screen, each filter and oscillator have their own screen. The GUI shows a lot of options that aren’t accessible via the front panel).

If you look at page 34 in the A6 manual…
[url:2udl2f89]http://www.alesis.com/stuff/contentmgr/files/0/a816dee61d9ad11686c04cf912d15fcd/file/a6_manual.pdf[/url:2udl2f89]

…you’ll see a photo of what the A6 GUI looks like. It’s a tab interface paradigm like you see on many websites. I’d assume that the Parent is the top row (groups of related parameters), and the Child is the bottom row (the actual param values).

[quote:2udl2f89]3) beginning at page 18 are the parameters, some of them look like controls for some gui/view stuff in the andromeda menu, like the seq graph_tab switch and others, is there ANY need to add them to a midi editor (i think not, but please correct me if i’m wrong)[/quote:2udl2f89]

I don’t think so. The tabbed GUI is one of the worst aspects of the A6 and one of the main reasons why a VST interface is so desperately need. The A6 team probably did the best they could, considering that they had to find a way to represent thousands of parameters, but it actually makes the complexity of the synth more impenetrable than it already is.

[quote:2udl2f89]also it looks like the A6 reacts to both NRPN and sysex, i was wondering if there is a preference witch type to use.[/quote:2udl2f89]

Not sure how the interface between the hardware and software works. I know that some DAWs (such as Ableton Live) don’t work very well with NRPNs (if at all). And I don’t think most of the knobs on the A6 will output CCs. I actually just tried this in Live; it will record the basics like pitch wheel, mod wheel, volume control, but not things like oscillator volume and filter cutoff.

Hope this helps.

[DBM]

[img:3luwzd96]http://img198.imageshack.us/img198/9058/micronnrpnlist4.jpg[/img:3luwzd96]

[DBM]

[img:3cbwhsop]http://img812.imageshack.us/img812/888/micronnrpnlist3.jpg[/img:3cbwhsop]

[DBM]

[img:3ek03lzf]http://img801.imageshack.us/img801/2752/micronnrpnlist2.jpg[/img:3ek03lzf]

[DBM]

[img:1bjx85yy]http://img706.imageshack.us/img706/7003/micronnrpnlist.jpg[/img:1bjx85yy]

[atom]

Does the miniak send NRPN messages ? Or maybe there is someone here with an Ion and can see if the Ion sends them, there are some missing parameters, i imported all from the micronizer (it has most of them in XML format) but there are some missing. I’ll post a list of witch ones are missing but i need to know if it’s possible to record them.

[atom]

Well i started to work on this, did the filters/pre-filters section. But this is a weird device, the micronizer transmits messages that should be not accepted by the micron, all messages are +1024, for ex when a controller should be 44 micronizer sends 1068, but when i change a parameter on the micron it sends out 44, so the midi feedback does not work. Now i’m wondering how to solve this. I can’t access all micron parameters (need to read the manual, i can’t find a way to edit parameters from the unit panel) so i can’t see what all values are, i can assume they’re all 1024 less then those in the micronizer but i don’t know if this assumption is right.

I’ll be adding the rest of parameters this week, i did fome fixes on the midi feedback stuff it should be working better with new builds. I also made the midi input monitor working, for all you guys who want to see what’s going on, on the midi input both in raw format and in a translated format (nrpns are actually 4 CC messages stitched together).

[atom]

I’ve rebuild all ctrlrs at this point, fixed some bugs, like the NRPN stuff, Moog Voyager got some fixes, Prophet08 work is started (visible parameters work, the rest will be added soon).
First LUA scripting draft is in the engine, you can see how it works in the AN1x XML (and yest that’s comming soon too). LUA will give the ability to do almost everything without any
re-building, it’s a work in progress but it’s comming along nicely. Some UI fixes too.

At this point i’d like to thank all you guys who made donations, i keep that in the paypal account, once i reach some point i’ll get a box of Your choice and build a Ctrlr for that ” title=”Smile” /> i promise.

Give the new builds a try and let me know about any bugs, i’m sure there are many. New MAC builds will follow tomorrow.

[atom]

I was looking through the sysex specs for the A6 and i have a question (just one for now). Could someone look at those specs here http://www.alesis.com/andromeda and tell me
1) what is the Child ID, Parent ID stuff
2) what’s the Parent Page
3) beginning at page 18 are the parameters, some of them look like controls for some gui/view stuff in the andromeda menu, like the seq graph_tab switch and others, is there ANY need to add them to a midi editor (i think not, but please correct me if i’m wrong)

points 1 and 2 are bytes used in sysex messages so i was wondering how to represent the graphicly on the editor.

also it looks like the A6 reacts to both NRPN and sysex, i was wondering if there is a preference witch type to use.

[atom]

well the midi feedback i partialy there, some controls like CCs NRPNs RPNs and some SysEx will respond to midi feedback, some tropical modulators like CC Pairs weird SysEx custom NRPNs will need more work, but will work soon.

I’ll fix the LFO selection today and post new builds asap.

kay, should be fixed, also fixed the lfo trigger button.

[atom]

when you start the ctrlr under a debugger, you will see a lot of messages look for any "can’t register component" stuff this means the XML names and the editor names don’t match.

[crayolon]

Heh, I think I must just have made a total mess of the whole thing… Jucer isn’t generating those methods (unless I’m looking for them in the wrong place) and I’m not sure where to put the code. I might start fresh with a more basic ctrlr as a template and try to understand it.

(EDIT: Oh, I found the methods in the individual tabs’ cpp files, but adding the handlers manually hasn’t made any difference so I must have messed up somewhere else.)

[atom]

well that depends, if you added new tabs/components you need to tell the Ctrlr engine where they are, theese are the few lines of code i was talking about.

1) register all your components with Manager->registerComponents()
2) make sure that every change of the componenet is registered with the Ctrlr engine, the jucer generates those methods for you you just need to paste one line per method on the end of each method, those methods are:
[code:qv0aogxy]
sliderValueChanged (Slider* sliderThatWasMoved);
and you must add Manager->controllerEvent (sliderThatWasMoved, sliderThatWasMoved->getValue());

comboBoxChanged (ComboBox* comboBoxThatHasChanged)
and you must add Manager->controllerEvent (comboBoxThatHasChanged, comboBoxThatHasChanged->getSelectedId()-1);

buttonClicked (Button* buttonThatWasClicked)
Manager->controllerEvent (buttonThatWasClicked, buttonThatWasClicked->getToggleState());

[/code:qv0aogxy]

that’s it, everything should work

[crayolon]

So I had a fully working CC-mapped Supernova Ctrlr last night, based on the Xio. Then I started changing the Xio template in The Jucer so I could have multiple tabbed areas on a single page and also broke out some of the groups into separate sections etc…and now, while I can build and run the Ctrl fine, none of the knobs or sliders send ANY messages to ANYWHERE! All component names and xml names are correct (same as before, but I double-checked them) and the only stuff that’s changed is UI layout. Can messing with this stop a Ctrlr from sending MIDI?

[crayolon]

Woohoo! Thanks for that fix atom – I can now send NRPN to the Supernova II! Actually, I think you have a typo in EdoModulatorManagerParser.cpp line 31 – should it be ‘nrpn_korg’? Anyway, it doesn’t matter, as I’ve got ‘rpn_korg’ in my xml.

All CCs for the Supernova II are implemented, and I’m going to add a choice few useful NRPNs as well (doing the whole lot – hundreds – would be ridiculous). When I’m done, should I build a release and send it to you to put on the site, atom?

[crayolon]

Update in case my experiences can help others:

"crayolon":1j8rfpsk wrote:

Cheers, here’s the Supernova manual: [url:1j8rfpsk]http://uk.novationmusic.com/uk/support/download/supernova_ii_keyboard_user_guide/132[/url:1j8rfpsk]

Your Ctrlr sources use the dot operator for accessing members of some Image related stuff, which builds fine, but I’ve discovered that if you edit and save a <whatever>Editor.cpp with TheJucer, it saves ‘->’ in place of ‘.’ and does a few other weird things that break it. I’m using the prebuilt Jucer from ‘extras’ within the juce package – I thought it was the latest version, but maybe I actually need to build it myself, what do you think? Worth pointing out in case others come across this problem, though.
[/quote:1j8rfpsk]

atom told me how to fix this – I needed to build my own Jucer exe from the source, as the bundled pre-built exe is out of date. The current one lets you edit/generate cpp fine.

[quote:1j8rfpsk]

Some other very weird and inconsistent build errors cropped up for no reason that I could tell, and if they happen again (I’m sure they will!) I’ll try to document them on here. Anyway, a real problem I’ve got now is that no matter what I try, the build process won’t parse my adjusted XML – every time I build, I check the standalone executable’s Preferences and see all the OLD (i.e. xio prefix) modulators listed, even though my XML contains all new ones (snv prefix – supernova). My prebuild process seems to contain the XML thingy that we discussed on IRC, so I don’t know what’s going wrong OR where the hell it gets the old data from! It shouldn’t exist any more! Any suggestions would help to stop me going bald with frustration ” title=”Smile” />
[/quote:1j8rfpsk]

Fixed too, as atom explained to me that the prebuild step in the VC project needs to be given explicit filename targets according to the Ctrlr nomenclature. This can be edited in Project Properties in VC++/etc. The binarybuilder uses the specified XML file to generate a .cpp and a .h file (called MycontrollerMapping.cpp/h), so if you keep getting the old values in your controller exe, try deleting those and making sure the pre-build command is doing what it’s supposed to.

[quote:1j8rfpsk]
Edit: oh, by the way, do you have some secret and magical way of generating the XML files, or does it have to be all done by hand (like I’m doing now)?[/quote:1j8rfpsk]

Heh, I think this remains a job to be done by hand, but it’s not too arduous. It will be once I start on the NRPNs though ” title=”Wink” />