Tagged: getting started
June 14, 2012 at 10:30 pm #621
Recorded this today, sorry for the accent and all i’m on some weird drugs that make me talk weird, anyway this will help those of you who want to create panels but don’t know how.
https://sourceforge.net/apps/mediawiki/ … PanelGuideJune 15, 2012 at 5:28 am #4411
nice one. was useful the Sysex understanding as wellJune 15, 2012 at 11:37 am #4412
Fantastic. Solved some questions.
Maybe is posible to download this vidtutorial with more resolution?
Another question: wath is the image editing soft used to make the "image buttons/knobs" ?June 15, 2012 at 3:01 pm #4413
it’s called Knobman
http://www.g200kg.com/en/software/knobman.html i’ll add those links on the WIKIJune 15, 2012 at 3:05 pm #4414
Vimeo has the original AVI file as a download option i don’t think i can provide a higher resolution than that ” title=”Smile” /> is there something unreadable i was using a pretty high res on my PC next time i’ll try to tone it down a little with the resolution. It was my first attempt expect more ” title=”Smile” />September 12, 2012 at 12:49 am #4415
Excellent stuff. I’m facing the project of perhaps having to do some CTRLRs then… as I have synthesizers not listed in the panels list. ” title=”Wink” /> I found my way back to this site after googling a little on "Yamaha TG77 editor Mac" – no such luck at all. There is a Windows editor that looks decent, including a 30 day free option, and I can install Windows using some of the virtual tools having it run side by side with OS X on the same screen. Problem is I am using an Emagic AMT8 and I don’t even know if there are any Windows drivers for it. So perhaps it’s going to have to be a CTRLR if I am going to be able to create some patches with the TG.
Has anyone tested the XP30 editor with a JV synth btw, like JV1080?September 14, 2012 at 11:26 am #4416
dasfakerParticipant"bitleyTM":ldn0ecv2 wrote:Has anyone tested the XP30 editor with a JV synth btw, like JV1080?[/quote:ldn0ecv2]
Both XP and JV share the same architecture (even the MC505), but the XP30 has fewer options in some parameters. For example, the Xp30 cannot select waves from PCM, and there are several parameter related to the outputs (the XP30 only have LR Outputs) that differ from a JV.
I’m planning to make a panel for each JV/XP synth, covering those differences between models.September 18, 2012 at 7:53 pm #4417
Awesome!!! Please do. I am a big JV fan. The extra terrestrial thing to do would be to add all waveform names from all expansion cards. ” title=”Very Happy” /> And let the user select SRJV80 card via a drop menu or so. My 1080 has experience II, dance, session and hiphop.September 19, 2012 at 1:16 pm #4418
This is something I’m still thinking about. Maybe I would need that Ctrlr could save some external config file for a panel to select only once the expansion cards you have and store this in the config file. Right now you would have to select your expansion cards each time you open the panel.January 30, 2017 at 12:17 pm #70982
Any chance of posting another link to your video tutorial? The link is broken.
neomiraSeptember 11, 2017 at 4:31 pm #72884
Link only takes you to: https://sourceforge.net/apps/mediawiki/ now…
Huge pity, as I’m about to dive into this.
Atom – any chance you can upload to youtube?
RocheySeptember 11, 2017 at 9:01 pm #72889
best advice: (i know it sounds unhelpful)
check out existing panels – demos mainly deal with Lua issues
earlier panels with less Lua coding will be most helpful at first.
in fact, forget Lua to start with: get used to creating ‘modulators’
and arranging a basic panel – have a look at the rightside pane for
all the parameters, see what they do. mess around with colours, and
appearance, text and value displays. put things into Groups or onto
Tabs. find out how they copy and paste, there are some inherent
behaviours to get used to.
find out a file saving system you are comfortable with..
and be aware that Ctrlr opens up with a temporary file
it has saved that is not necessarily your last named, saved
file! if you want that one, close current, and re-open from
your saved file !
other important stuff: if you copy a modulator(‘object’),
and paste it onto the workspace, it *does not automatically
lose it’s group or tabs ownership status – if you do not
delete this, and save, and close, when you re-open you will
find your objects have ‘disappeared’. but they are still there,
hidden. they will exist in the Modulator List. you can make a
real mess of things here, and get very discouraged, and waste
a lot of work/time. so copy and paste carefully. best is the paste
to the workspace, and then check, and delete ‘tabs’ and ‘groups’
ownership, since it is no longer relevant. if you don’t…screws
things up every time. it is a main first problem to be aware of.
so make a mockup to get started, put things in groups, or on
panel tabs. save and reload, and see how you got on. then try
copying stuff, and avoiding the problems described above, save
and re-open, check if it is the way it is suppsed to be.
this will save you huge headaches and lost work later. it is
a fundamental premise to get to grips with.
save your files with your own names, is MY advice, and avoid
versioning – you don’t have to, i don’t fully grasp versioning –
and always remember that the current file it loads with is only
what you CLOSED it as. your last saved version is the file YOU
NAMED (and gave a version number to ie: v01, v02, v03 etc.)
hope this helps. no probs answering further questions.
have a look at the (long) D-110 topic, it’s all about
starting from scratch.
You must be logged in to reply to this topic.