- This topic has 30 replies, 4 voices, and was last updated 8 years, 5 months ago by
.
-
Posts
-
not found that file yet. maybe because i’m on .102?
oh, i see, the *.overrides file in the Roaming folder.
and i can just edit that?>strange issue with modulator list >
2 or more item at same entry, stacked up.
?
managed to sort it out, had several, but not sure what it is
down to, or, really, how i fixed it 🙂 i entered a different
coordinate to move it, and the dodgy ones showed up, and i was
able to delete them,but doesn’t always work 1st time..
———————————————————–
oh yeah, this is very nice now. i can just follow the parameter
list in my hardware device manual, and assign Index# consecutively,
refrshing by hitting the ‘index’ column tab twice, and my list
orders itself -this is looking much better already.
>? i don’t think Labels and Groups would need Index#, though? so
that should free up some Indexes.ok, i can see how to sort the Modulator List now… 😉
very useful.
COPY+PASTE of objects evidently requires careful handling
and maybe some routines, to avoid nasty suprises when re-opening
projects – certainly in the 5.2.102 version i’m running on 32bit
Vista.i’ve had frequent strange re-positioning: this is because ‘Group’
ownership doesn’t necessarily update with the new copy, and may
keep inherited appartenance.so then it can jump to position 0,0,..
on top of previous object in that Group – big pain, if you don’t
have some way of repositioning; i’ve ended up re-unlocking and
resizing a whole bunch of group/tab/group etc.pulling my hair out.but you don’t need to go through this if you know how to find things
in the Modulator List, and you can re-enter screen coordinates there,
if you can find your new object. selecting it there makes it
selected in the Edit pane on main screen, so all if not lost.
————————–
NOTE: i’m getting to like this program very much. for it’s ease of use, once
you learn to observe certain rules/disciplines in naming Groups (and in
USING Groups).
Loading a panel into the VST version, and exporting a locked
instance is very cool.>i think there are one or two navigation things that could be improved,
for fasting working:
-NOT scrolling values without clicking first, i’ve created mistakes doing
that without realising
-would be good to preserve scroll-point, whilst switchingback and forth
between modulators. pretty sure that doesn’t always happen
-when pasting, that objects land positioned more predictably,-and they ‘jump’
on 1st click.Tabs within tabs: it appears that it would be wise to put a ‘subtabs’ inside a Group before putting it onto a main Tab 😉 >sorts out this Ownership bizness, by the look of things. Groups, Groups!!
———————
ah…not exactly: i tried copying a Group with 12 smaller subgroups (repeating
parameters), using ‘with children’ and it only copied empty subgroups, not the
parameters. confused. this was in order to save work, and placement.> mmm…something very nasty just happened. i had a feeling about it,
a wrong click/mis-click. terribly dangerous.
2 of my tabs have inverted. i still have tofigure out what the damage is.>*masses* of work here, 400+ parameters involved(a drums set-up), all have
just been vstindex-numbered, carefully and painstakingly named.
i have to see if i can fix it..> i think lots of things are dangerous and fragile in this software.
something to look out for, and improve on.(not being negative, just
factual)>i’ve found some good routines for organising parameters in the list.
doing this drums setup was useful for that. it involves a lot of work
ensuring everything is correctly named+numbered.
>i still don’t know how this will turn out in use; i’m just seeing
how far i can take it.
—————–
EDIT: phew, that’s a relief: i’d accidentally changed a tab index, so
that 2 had ‘0’…put it right, saved and reloaded, all back in order
with no trauma!Panel structure is now complete, and has all required parameters created,
and given dummy VST Index#s in order – it’s quite a bit more than 64 ‘max
exported’, and i have gaps in the numbering – is this why params no longer
load with a default value? i noticed when copying groups that they would
stop doing this.>i don’t think Groups and Tabs or Labels would need Index#
>something strange has happened with componentTabName; these are not what they
should be. fortunately it hasn’t caused problems with positioning/appearance
within the correct Group and Tab.(do i have to go through and change all of
these? would renaming of current Tab fix that? to try…)>all Group names/references are correct.
>i think next step is to number my indexes in strict order.
Q: is’0′ a valid VST Index number?(!)Q:what is ‘custom Index’ and customIndexGroup’?
>i had a load of errors created by accidental scrolling, was easily
resolved by calling up the parameter column in Modulator List, and
going down the list resetting the value. Modulator List is really
good in this respect, saves a lot of time.>i’ve got to a good stage: layout is done, maybe some minor changes,
but it’s all there. i need some finer points of Lua for naming patches,
and i wouldn’t know how to retrieve patch data, that’s all a bit beyond
my skills, and i have no plan to learn any of that at this point.>this is a Panel for Roland D-110(will probably also work for D10/20 and
maybe D5) -it’s a neglected machine capable of some good sounds, this
should make it moreprogrammable and usable.>i’m going to see it i can get some assistance/collaboration for this,
it isn’t like it’s a commercial project or anything.
>so i’m just going to put that request out,while i fine up what i’ve got,
get VST Index in order, and start entering the sysex.>i have one doubt: these Roland multi-timbral machines can effectively
use any channel for editing; i’m planning on MIDI ch1 at present. so i’m
thinking someone may have away of making MIDI channel a variable, so that
it could be specified. not sure how useful this is. i would generally use
one ‘Part’, ie: part1 for the Tone editing, and Timbre assign, save those,
and assign Timbres to Parts in the Patch, where you set levels, pan, keyrange,
offset tuning etc. (it’s a huge headache on the front panel, and almost
impossible to get the most out of the machine)>if you look at the MIDI data list/sysex in the D-110 manual, you can see
this. you have unit# and basic channel etc.http://cdn.roland.com/assets/media/pdf/D-110_OM.pdf
>here’s a png of the main view at the moment. i haven’t used any external
images except for the structure select png borrowed from d50 panel and
edited a bit. colours aren’t final, emphasis is on function+ease of access.
comments welcome.
>it may be fairly trivial to get this up to top standard. i lack the
programming skills for Lua and the finer points, so it would be good
to get some assistance to get this at least to a working v1.
- The forum ‘Using Ctrlr’ is closed to new topics and replies.