Forum Replies Created
-
AuthorPosts
-
>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 found i’ve introduced – and copied…- errors in ‘fallback base value’
and ‘decimal places’…because it is very easy to scroll these accidentally.
hundreds of these to correct now. so care should be taken with this – it is
near unavoidable, i was aware of the risk.
another cleaning-up session.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’?
precisely the figure i had in mind. how did that go then?
it’s back to 64 in 5.2.102> 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!- This reply was modified 8 years, 4 months ago by human fly.
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.- This reply was modified 8 years, 4 months ago by human fly.
HOW TO SORT OUT A MESS IN MODULATOR LIST/PANEL BAD COPY/PASTE
…- This reply was modified 8 years, 4 months ago by human fly.
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.- This reply was modified 8 years, 4 months ago by human fly.
hehe…exported restricted instance 1st draft 😉 exciting.
ok, i can see how to sort the Modulator List now… 😉
very useful.
>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.- This reply was modified 8 years, 4 months ago by human fly.
Roland multitimbral synths have an address+offset address system,
whereby you sum address+offsets to get parameter addresses on any ‘part’,
and you access modes other than just ‘tone edit’ that way also.
maybe something similar with your synth?i don’t think programming multiple tabs would be too problematic,
just do the 1st one exactly as you want it, all objects in a group,
and then copy-with-chidren (maybe lock everything first 😉 ) and
paste into as many channels/parts as you want to do.
as for VST index…mmm maybe make an ‘editor’ standalone, and then
a ‘performance map’ for the controls most likely to be used for
real-time?- This reply was modified 8 years, 4 months ago by human fly.
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?(i’m just going to quote Chat, as it might be useful to other
newbs who come across this thread..and if Goodweather wants to
include such stuff in his doc)
“(re: getting MIDI values 0-100 to display as -50 to +50 in Panel)
gfgf:
in the Modulator part of the panel (on the right side) there is “Expression to evaluate when…” part with the default setting “modulatorValue” in your case you will have to change it to “modulatorValue – 50″ and now if you connect your uiLabel to that modulator it will be getting your modulator values as a rage from -50 to 50.”re: default start-up values for params:
” default value could be done with Lua so every time your panel loads all your modulators will get certain value. i dont think it can be set from the Ctrlr interface thou.”ok, think i’ve got that 🙂
i think i can cope with a 2K param limit !
but what is ‘override’????!!!i’m making current project mainly as a patch editor;
ok, so i’ll save 0-127 for ‘most likely to be automated’
or is it literally 1-128? i suppose it must be, if no
VST Index#0..meanwhile, i can order Modulator List the way i want with
temporary ‘fake’ #s.>any idea how many Index#s are allowed in other hosts?
256? etc.?
-i can have the ‘ableton set’, and go progressively deeper
with other hosts haha.mind you, i haven’t donea count-up yet…(count) i’m already
up to over 200, but yeah it’s workable. no way would you want
to automate some of those.>HANG ON THOUGH: ableton doesn’t support sysex.
MMyeah, well that didn’t work too well.
saved it and re-opened and somehow one of my groups
has double all objects in it.i think it’s really important to have precise control
over cut+paste, -where they land, and in front – and
things like moving multiple objects with ctrl+alt+select.i’m really trying to avoid hidden objects i don’t know
about !!
—————-
right, well that was sorted out quickly without too
much trauma, but only because i knew -man, i was sooo
careful not to produce doubles.
—————-
i’m figuring i can re-order my modulator list with
VST Index renumbering, if that’s permissable.- This reply was modified 8 years, 4 months ago by human fly.
(this all refers at present to 5.2.102 build)
It would be nice if you could sort the Modulator List view manually,
with Move Up/Down, like in Layer View. i had to do a cut+paste of
multiple buttons from one tab to another, and it…didn’t exactly
go wrong but they all landed where i couldn’t see them, and i had to
dig them out of a corner, where they were stacked (10 of) and then
gave up on their order, and changed suffix numbering afterwards, so,
mindful of order, i renumbered them in order, but now they aren’t
in numerical order in the list,and alphanumerical auto-sorting isn’t
doing it as expected.
> eg: i’d ideally like more control over the list, it makes it
easier+quicker to check through and find anomalies.i was disappointed i couldn’t do something like’lock’ them, and
ensure they cut+pasted properly.so i concluded that the best way to move multiple objects, in a Group,
is to copy-with-children, and delete the original afterwards. don’t
know if there’ll be a reason why that wouldn’t be a good idea yet.copying groups containing modulators causes a lot of same VST Index.
i don’tknow if this is a problem, if you can re-number afterwards.
but how do you determine #s to use?a shared # is handy if you want synced response from 2 modulators.
apparently if you try that with more than 2, it doesn’t work
(?must ‘use Lua’?)>VST Index -so i’ve realised i don’t know much about this either.
what is a/the VST Index?
i was assuming it would be a global Index for a plugin for registering parameters, like an address in sysex.>i saw mention of max. of 256 re: ‘VST Index’. Puppeteer tells me:
‘ableton support up to 128 *Index’s* -suggesting each param has/is
an index.
>AND that ableton only supports 128 *index*s (so you can have more than
128 parameters, with only 1st 128 being ‘mappable’ >?controllable by remote?
stored in a patch memory?
>i know i’ve put a lot more than 128 params in VST plugins in SE …
ANYWAY> i have here an Index # at 732 – it is a UITabs, so i s’pose it
wouldn’t matter re: automation. what sort of numbering is ideal in a
project?
i’m thinking i’d want to use #s in usable range :0-255, or 0-127 etc.
or can i assign any # i want to any item: control/group/tab/label/etc
?
;O) just wanna get this clear before i go and create some big horrible mess.>looking at my current Panel Modulator List:
>project only has an empty UItabs structure(with 7tabs), with 1 UIgroup
outside that, containing 5 buttons, and then there is a logo UIlabel, by
itself in the Layer.(i’m building the GUI structure before populating it
with parameter objects from the sysex data list)
Q’s:
-is it agood idea to put the UItabs in its own uiGroup?(why?)
-same for stray uiLabel
-i note that the uiGroup has no Index -or Index #/value –
(seems logical, but also, why would a uiLabel have an Index?!)
(or a UItab, etc. >non-control elements)
-why does the label/logo, or group have a ‘modulator value’? have i got
them defined wrong?
-what is (modulator)CUSTOM INDEX?
– i see also MIDI messg type (@’5′)and Ctrl#(@’1′) – i havn’t done anythg
with these yet, what do they correspond to?
————-
ok,that’s my Q’s for this morning :O)
i assume i can continue and re-assign VST Index # afterwards?
i’m curious re: whether Ctrlr will starting assigning low #s consecutively
if i re-number from eg: 0(or 1) onwards, now.
also, it seems to start at ‘modulator-1 each time i start it,having given
everything a name from previous session.soz, elementary questions, just want to be clear on all this.
Q: oh yes: i’m about to re-name my UIgroup – both’componentGroupName’
and ‘componentTabName'(is*isn’t in a Tab anymore,but was created in one
originally, i think) -hoping this is safe, spose i’ll find out when
i restart it.
Q: the BIG Question: so what’s the difference between a ‘modulator’ and
a ‘component’? you ‘Add componenent’, and then eg: uiSlider appears,called
‘modulator-1’ ??! understanding/explanation of this is key to the LONG
parameter sidebar.
>NB: I WISH EACH MODULATOR VIEW WOULD RETURN TO SAME VIEW WHEN YOU GO BACK
TO IT!!! it jumps back to top, after you’ve carefully scrolled down, not ideal.
(thanks!! – for reading my confused blurb -) -
AuthorPosts