Search Results for 'Nrpn'

[JKervinen]

"minimalist":3r9cw0nb wrote:

I was tweaking the VCF velocity and ALL the values of the amplifier has been affected, too (all sliders have the same position).[/quote:3r9cw0nb]

I came up with the same thing on mac while building the Roland JP-8080 Panel. Problem was gone after re-opening the panel, but came back while I was editing other knobs / buttons.

[atom]

i think i know what might be the problem it’s the vst indexing thing, i’ll have a look.

[minimalist]

With affecting other components I mean that I’m tweaking/moving ig a single slider and 10 other sliders (or uiCombos) also change their values.

But at the moment I’m sure it’s a bug, because when I’m reloading Ctrlr the problem is not appearing every time immediately. The pannel I’ll attach. Try to do some changes (moving components (also mutible), tweaking some components, deleting some components) and soon you should see what I mean. Thanks.

EDIT:
In the pannel you can see the last strange accident. I was tweaking the VCF velocity and ALL the values of the amplifier has been affected, too (all sliders have the same position).

[atom]

what do you mean that they are affecting other components ?

what sort of NRPN numbers are you using and what sort of components are on your panel. If you can please attach the panel here

[minimalist]

Hi. At the moment I’m creating a pannel for the Tetra. The MIDI message type I set to "Multi". Then I inserted a pre-defined NRPN message from the clipboard. After this I typed in the field "MIDI Controller number" the number of the parameter I want to control…. I think this is it how it works, right? Because if I tweak (or move) some specific componets they are effecting many, many other components aswell. I know there is a similar bugreport which should be solved. Some Days ago I’ve experienced a similar problem with CC messages, but that happend rarely and it solved itself after restarting Ctrlr. The behaviour with NRPN is much stronger and happens very often. I’m using build 351 on Mac.

Am I doing something wrong (if not the post could be used for a little howto guide ), or is it a bug?

[Wren]

"nrhyan":2sg4q4f1 wrote:

Hey Kidney, I’ll try and help out. First off, do you have any particular reason to want to send standard CC messages? Itll be just as easy to send NRPN and you will also be able to create controls for ANY/ALL of the Tetr4’s program and combo parameters. Make sure you have a tetr4 1.3 manual and let me know whats up. I’d be happy to send you a panel I’ve alreadymade for the Tetr4 too so you are able to see some working examples.[/quote:2sg4q4f1]

Hi Nrhyan, I’d LOVE if you could send me what you’ve already done with ctrlr panel for Tetra! I’ve also got another question, have you been able to set up the panel to be automated by Ableton Live editing boxes. Say you want a frequency sweep to be automated in Ableton Live on a MIDI track during certain parts, along with other parameters – is this possible?

Atom nice work, the potentials of this are astounding.

Thanks

[nrhyan]

Hey Kidney, I’ll try and help out. First off, do you have any particular reason to want to send standard CC messages? Itll be just as easy to send NRPN and you will also be able to create controls for ANY/ALL of the Tetr4’s program and combo parameters. Make sure you have a tetr4 1.3 manual and let me know whats up. I’d be happy to send you a panel I’ve alreadymade for the Tetr4 too so you are able to see some working examples.

[atom]

i think the TETRA uses NRPN messages not CCs, that’s what i remember from the v4 when i did a TETRA editor.

[nrhyan]

after loading the second time everything seemed to be functioning well and I had no crashes in the fifteen or so minutes testing my panel. I had trouble adding your NRPN preset to a Multi slider, so right now I’m going to go back to standalone to create a panel for Tetr4’s sequencer. Us Tetr4 and Mopho users could really help each other save time and have fun by sharing any work we’ve done on panels. So.. if someone has a panel for Tetr4’s sequencer, now would be a good time to share ” title=”Smile” /> . I will happily do the share the easy but somewhat time consuming panels I am able to do(these would include things like panels complete with all of Tetra’s NRPN program parameters). ” title=”Razz” /> Things like sysex parameter dumps I have not tried setting up components for and could probably use some help.

Some time yesterday I tried but could not log on to DeviceDB. I’ll try to give it another shot

[nrhyan]

"atom":1h75svau wrote:

well yes and no, there are no READY panels, but there is nothing stopping you from creating your own panels for your synths. and sharing those panels with others.

Right now v5 can do everything and more that v4 could you just need to make it do that. It’s all there. Once someone creates a panel for a device and decides to share it with us, you just open it in v5 and off you go.[/quote:1h75svau]

Earlier today I tried to make a post in this forum with a panel I made attached. Unfortuantely this did not work, a message popped up which read something to effect of "format not allowed".

I was really excited as I FINALLY figured out how to send nrpn changes(yet another easy task I managed to over-complicate/overlook) So anyway, now im really thirsty for more.. can we share our panels?

[atom]

yes my bad (or me beeing lazy). I forgot that the Evo requires a 4bit split on it’s messages (not the 7 bit split like in the NRPN/RPN), so additional two types of operators in the SysEx editor are added, use them to set up your evo. I’ll just post the new builds.

[atom]

set the midi type to MULTI and you can add multiple messages to the list, there are also templates for RPN NRPN and NRPNKorg that ready to use, you can ofcourse add them yourself.

[nrhyan]

I am been able to open the standalone v5 in 10.6.5, which is great. I have succesfully received a sysex program dump from my Tetr4 via usb, I have not yet tried sending from the app. I have had no trouble creating cc knobs and slider, the values of which have so far been accurately received on the Tetra via usb!!!

I had a question, if you have a couple minutes to help me out with an answer that would be awesome and I’d be able to really start trying the program out. I would like to know, how do you create a component (knob, slider, whatever.) that sends NRPN data to control things such as the LFO and sequencer parameters? In the component panel "Midi Message Type" menu I can choose from CC, Aftertouch, Channel Pressure, Note On, Note OFf, Sysex, Multi, or none. Is there a way to implement one of these options to do what I want?

Any help would be MUCH appreciated. Thanks again Atom.

Also, v5 brings a WHOLE lot more to the table next to v4. I already have all sorts of ideas for how Im going to use this. For someone like me who doesnt know how to use programs like Bome Midi Translator, ctrlr v5 will be a good send. If you need any more graphic design work, I’d be more than happy to try and help.. logos, buttons.. whatever. Thanks.

[minimalist]

Hi atom,

it has been a long time ago since I was in the forum… and now I read: THIS!!

At the moment I’ve to manage some annoing important problems which are time consuming, so I don’t have endless time for beta testing. But anyway, I really like to test v5 for you – and as I know myself I will spend more time with it as I should and my problems allowing. ” title=”Wink” />

If you like: I’m on Mac OSX 10.6.6 (32 bit), at the moment I have a DSI Tetra, Evolver (maybe I will sell soon), and a Virus C. As you can read in the Tetra thread there is a new OS version (1.3) which has many changes in the CC/NRPN messages (but it’s MUCH better than before!) if you need the new parameter list: just tell me and I will contact DSI. In the future I would love to host v5 in Ableton 7 and NI Maschine 1.6, so if you like I can test the VST (or AU) version aswell.

Best!

[atom]

I have a pre-release candidate ready, i’d like to post it in binary format but i’d like to know if there is someone out there willing to test it and if so, what sort of OS do you have so i can prepare builds for those platforms (i don’t have the build environment ready for all of them so i’d like to target this as much as possible). Also if you could tell me what sort of MIDI hardware you have to test it with, so that i can polish those features that might be most usable for this hardware (if it’s an old oberheim analog synth i’ll quickly add the planned SysEx features if it’s a DSI synth i’ll double check the NRPN implementation and so on).

Let me know, the fastest i can do is Windows (either 32 or 64bits) standalone app, cause that’s what i use for development.

[atom]

i wish i had a timeline, what i can say is that i code any free time i get, i don’t get that a lot but still, you can see what’s going on in the repo http://sourceforge.net/projects/ctrlrv4/ i try to commit whenever i change anything to keep track.

First step is to build a working engine with in-out working and some basic midi messages (cc/nrpn/rpn/simple sysex 80% done) and all the UI components working (90% done), do the vst layer (20% done) and that will be the alpha release, we’ll see from there.

I think i need a month to get a alpha release, if i have some more free time @work maybe earlier.

[atom]

yes for defined controllers like rpn,nrpn,cc the "number" property for a modulator element in the XML defines it’s number

[atom]

New windows builds are up (mac later today). Changes

– tetra fixes, ms2000 fixes
– engine update for dumping programs
– some dashboard work (soon to finish)
– more options
– new logging subsystem (you can enable logging in memory so you can track what happens without performance loss, just set how much memory you would like to use for logging and then have a look at Help->View Log)
– some engine fixes for NRPNs

right now i’m doing Dashboard work (while at work), and Program Dump/Send at home.

[analoguebus]

Oh yeah I forgot to mention I can try to help solve some NRPN issues if there are still any. Yes whomever came up with it was on crack indeed, I HATE IT, RozzBoxx uses it nearly exclusively.

Also I saw the issues acquiring a RTAS SDK. I can probably get this, and my old laptop was acting silly so I just got a new i7 one (its pretty cool) so I do not have Protools installed right now, mine is a really light crappy version and a few versions out of date, but it should work for tests. Hehehe, lets support TDM2 and SonicCore also I have been dying to have an excuse to get one, once we have the cash (I know the last part was being very silly, but the Soniccore system is soooo cool, the Solaris synth is being built up on it).

Also for Mac builds analoguebus uses them nearly exclusively (we have several machines). I use Microsoft stuff all day programming so its a nice change going home and using Apple stuff. I am also a registered Apple developer so anything we need on that front I can get it, but it looks like you have it well in hand.

[analoguebus]

atom,

Sorry for the delayed response. Got quite busy here at work getting a R&D whitepaper done, sorry about that. OSC is Open Sound Control, I basically see it (hopefully) slowly fading MIDI away (MIDI will always stay of course there is hardware that is old, etc. that was not designed, of course there will be retrofits for a small, small segment of items but probably isolated to a few elite items, when I say retrofit think of Eventide’s retrofits or HighlyLiquid). Dave Smith and company did a great job on the MIDI spec., but we got to admit it is quite antiquated. The limitations of MIDI are really starting to show. Specially now with the newer more complex synths, really for anything substational besides the REALLY basic stuff are having to resort to NRPN or SYSEX work arounds, then there is the bandwidth issue, and the low bit size. There is starting to be a very large acceptance in the community for OSC. The lemur like I and you mentioned really got it kicking, but I think the one project that blasted it out into the forefront was Brian Crabtree and the Monome. It uses a USB serial connection to a small server on the computer instead of the normal UDP or TCP network connection OSC uses. Now the software packages are picking it up or unbeknownst to most people they have had it for a long time. Max/MSP supports it, Reaktor, SuperCollider, CSound, Abelton Live, heck a great number of DAWs are putting in support, then there are starting to be physical instruments (mainly controllers) that are picking it up. The lemur and the monome were the big firsts on it, but now Livid bases their products on it, many many things are moving that way. Here is the big reason it’s stupidly simple, incredibly fast, and tons easier to process. It supports actual typed values: floats, ints, strings, binary blobs, etc. Instead of being a slow baud rate (now there are products these days that greatly abuse it, like my genoQs Octopus, it can basically outrun any MIDI device) and being subject to correct Endianess and having people who are non-programmers having to learn bit shifting, learning MSB, LSB basically trying to teach musicians bitwise math, its a simple as sending strings. For example say the DSI Mopho supported OSC a typical messages might look like (without the quotes) "/input/gain 100" for 100% or basically any message of the sort.
The latest spec 1.1 is here: https://docs.google.com/viewer?url=http … Cfinal.pdf

You said that it offers problems, the only issue I have ever had with it is with Reaktor 5.0 rather poor way of handling network connections, but I think this is rectified in 5.5 (which was a massive rewrite), and then a module I am developing for Eurorack, and Buchla modulars (heh but thats my stupid self messing it up). Stuff like the Lemur works flawlessly with everything I have tried, same with the Monome.

OSC is just one thing and not a super priority to me, but another nice tool to have in the toolbox. Now a big big thing to me and to people really yelling for it, is a nice tool like you have, but for a bit more advanced features (these will take a bit of prodding of some people to get the specs or more than likely reverse engineering it, and that is support for the patchable modular style synths, for example the Nord Modular micro, standard, rack, and 2 GX, then the Arturia Origin (someone has to really give this thing some loving soon or Arturia is going to have a angry mob, they have slipped many dates for firmware releases to add new modules and many have asked why do not they make a VST for controlling it, patching on the screen while quite elegant is also a pain). I just see this as making a new template for those two synths, just like that has been done with all the others. Now in your utility section that wonderfully automagically handles putting complex MIDI messages together, I could see some new utility functions going in to specifically handle this type of system. There is already an open source project that is a newer editor for Nords but it is Java based has issues on systems accessing MIDI and crashes quite a bit. Also it is not a VST or AU that can be automated. This project will make the Nord template pretty straightforward and hopefully gain some insight on how these patches are built up. You have probably seen or may own a Nord Modular (the ceasing of production on it was probably the stupidest thing they have ever done, people did not "get it" when they came out, now with modular synths back on the rapid rise suddenly it clicked and now they go for obscene prices) the patches can be quite brilliant and quite complex.

Sure that will be great if you can add a user for me (really for I and my parter in crime in our little analoguebus escapades). Like I mentioned in the first email we have been programmers forever who in the last 4 years or so have massively fell in love with synths. We have probably stupidly amassed quite a collection. It was a great learning experiance that is helping us now hopefully help pthers with both building community modular projects and helping other community projects like yours, and as soon as my kit arrives Mutable Labs Shruthi.

Ok I blabbered quite enough. I tend to be a bit long winded, I go a bit into stream of conscious typing probably misspelling the heck out of words.

Any help I can give I would love to give it, this project you have created is really well thought out.

Thanks!