Home › Forums › General › Panels, Components, Macros › Roland D-110 panel
- This topic has 201 replies, 18 voices, and was last updated 6 years, 5 months ago by human fly.
-
AuthorPosts
-
February 7, 2017 at 10:09 pm #71152
On PART SET / Part 2 if I press enter I get: `F0 41 10 16 12 03 00 18 64 01 F7
`
Is that what you’re looking for? Tell me what to press and I’ll do it 🙂February 7, 2017 at 10:10 pm #71153it is intended to be run in editor mode.
not in VST format yet, some way to go for that.February 7, 2017 at 10:21 pm #71154(skip>>)
February 7, 2017 at 10:30 pm #71155Sorry, with you now: Tone E/Partial 2 TVA-ENV TKF = 1
F0 41 10 16 12 04 02 6D 01 0C F7February 7, 2017 at 10:39 pm #71156I got a different value but I might have got the wrong menu setting, can’t see the screen very well:
F0 41 10 16 12 04 02 67 03 10 F7Pretty cool though!
Just trying your pre-alpha now
February 7, 2017 at 11:45 pm #71157that looks ok..TVA ENV TKF is envelope time follow/kb scaling,
at value =01. 0C is the checksum, forget about that for now.
so the address of TVA ENV TKF 2 is 04 02 6Dif mongoosander checked TVA ENV L3, that’s 04 02 67
the value is 03. i should have specified at value = 00 😉- This reply was modified 7 years, 1 month ago by human fly.
February 8, 2017 at 12:00 am #71158February 8, 2017 at 6:53 am #71162checksum is indeed wrong. here’s a good little
no-install free checksum converter that worksFebruary 8, 2017 at 7:12 am #71163the JD800 panel has a Lua for calculating the checksum
by the look of things.February 8, 2017 at 9:13 am #71167ok, fixed those TVA sysex errors. it was mainly the
TVA2 levels i got wrong when doing my parameter list
ages ago, where it ‘crosses’ the MSB and goes 00 7F
(highest possible value, cannot have 80h) and goes
to 01 00h.- This reply was modified 7 years, 1 month ago by human fly.
February 8, 2017 at 9:44 pm #71183okay folks, dasfaker has just suggested the solution
to that problem with the checksum, so i’ll get on it.- This reply was modified 7 years, 1 month ago by human fly.
February 9, 2017 at 11:44 am #71191skip>>
February 10, 2017 at 2:26 pm #71209anyone have any joy with the panel yet?
i think i might have a solution for the Partial on/off
buttons; it is a lua method but i could do with some help
putting it together. i’ve got the conditions set out, and
i think that could do it but i need help with the syntax
and form.February 10, 2017 at 5:52 pm #71213Yes, panel now working on middle section without checksum errors. As you predicted, stuff on left and right still poorly.
Could you make the panel open again for now please, as I’d like to wade in and help too, and it might help me (and others) to learn too from your adventures!
February 10, 2017 at 8:30 pm #71221i will, i just want to get these buttons working first, to
retain the integrity of it – i plan to take this thing
quite a bit further, don’t worry. the first file isn’t
much different.i did it as a standalone exe for user-convenience. it’s a
bit of a drag when you hit panel mode and get the properties
pane jumping up. these files are very ‘fragile’, and i’ve
had to spend a lot of time cleaning it up. it’s very easy
to screw it up terminally with bad copy and paste technique;
and objects jumping around the place. in any case i want another
decent meditation session on it, because i might simplify the
structure a lot.
best to go with that first file for now, and change all
z5’s to z4 – why? this is all, as it turns out, explained in
the very good documentation file. z is the type of checksum,
and the 5 – or 4 – is the number of bytes to apply checksum
to. JV has 5 bytes, and D-110 has 4. so it was a simple fix.
i found a few other errors while i was in there, fixed those.
next up is to assign VST index numbers in order of the parameter
list. i ‘m being very careful how things appear in the modulator
list, to keep it reasonably easy to view.how did you find it with the D-110, make it easier to produce
new Tones?February 10, 2017 at 8:38 pm #71222Good find about that z4/z5 thing. I wondered how you could have a hex value of “Z”!! 😀 Lesson learnt – I’m going to read the manual too!
@how did I find it – I nearly wept for joy. I have never managed to get anything other than presets out of it up to now 😀February 10, 2017 at 8:42 pm #71223I just did a 2-second edit on your original panel file – changed all z5 to z4 – everything worked all along!! So something else I just discovered – you can hand edit the file if it’s a tedious change like that to make.
February 10, 2017 at 8:46 pm #71224—
February 10, 2017 at 9:02 pm #71225– – –
- This reply was modified 7 years, 1 month ago by human fly. Reason: waffle
February 10, 2017 at 9:08 pm #71226this is the best bit of the mapping done. the rest is less critical,
but still very useful with lots of possibilities. it’s repetitive, mainly.the trouble with what i’ve done so far is that it’s all on MIDI ch1 only.
i would like another variable for MIDIchannel somewhere. if you select
Timbre via Progchange, which is one way to do it, and do this on the
basic channel, it changes the Patch(multi) which is no good. so if you
want to scroll through timbres on Part1, it will scroll Patches instead.
i have to look to see if there is a sysex slection of Timbre. -
AuthorPosts
- The forum ‘Panels, Components, Macros’ is closed to new topics and replies.