Search Results for 'z1'

[SWB]

soundtable(index) calls the function soundtable() and passes the value of ‘index’ to this function. In this function I use the value for ‘index’ as an index to an array of preset names. In my script I actualy don’t use ‘index’ as a variable name, but I thought to make it more clear by using this name.Yes, it is sloppy code up to now, but this was just an example. When testing this code I’m 100% sure ‘mt’ and ‘index’ get values (using the input midi monitor to verify this).

This is the code for the soundtable() function, with the idea of displaying preset names in the lcd-component:

function soundtable(index)

sounds = {“Piano1″,”Piano2″,”ElGrand1″,”Rhodex1″,”Wurlitz1″,”DXPiano1″,”Clavin.1″,”Vibes”,”Harpsi1″,”Organ1″,”Pipe1″,”Strings”,”Choir”,”Mutesynt”,”StrBell”,”A.Bass”,”RockPian”,”HonkyTnk”,”ElGrand2″,”Rhodex2″,”Wurlitz2″,”DXPiano2″,”SynClavi”,”Marimb”,”Harpsi2″,”Organ2″,”Pipe2″,”Atkstrin”,”AtkChoir”,”SlowSynt”,”SlowBell”,”E.Bass”}

lcd_basic_text1 = “1.”

lcd_basic_text2 = “2.”

panel:getComponent(“LCD”):setComponentText(lcd_basic_text1..sounds[index]..”   -Pg “..”\r”..lcd_basic_text2..sounds[index+1])

end

[bitleyTM]

[b:1wqrlqe9]racks[/b:1wqrlqe9]
proteus 1
proteus 2
procussion
tx81z
jv1080 w experience, dance, session, sound fx
jv1080 w hiphop
vz10m
k3m
k4r
k4r
tg77
e5000 ultra
d110
eps 16 plus

[b:1wqrlqe9]keys[/b:1wqrlqe9]
sp250
d50
jx8p
juno2
nl2
blofeld black
lambda (broken!)
d20
ht3000
trinity plus
01wfd
mox6

[b:1wqrlqe9]groovers[/b:1wqrlqe9]
esx1 sd
r5
s3

[b:1wqrlqe9]misc[/b:1wqrlqe9]
m120
m240
rx1602
amt8
miniFex x4
rokit 5’s
pmG5 w motu 2408/2 x ADA8000
mac mini
logic
reason 1 2 2.5 3 4 5 6 6.5
kontakt 5
cubase ai
korg legacy
yamaha b60 organ

[url:1wqrlqe9]http://bitley.laconicsounds.net[/url:1wqrlqe9] homepage
[url:1wqrlqe9]http://soundcloud.com/bitleytm[/url:1wqrlqe9] soundcloud
[url:1wqrlqe9]http://youtube.com/bitleytm[/url:1wqrlqe9] youtube

[msepsis]

[img:aqz1mllg]http://www.monstrummedia.com/stuff/PULSE-2-ctrlr.jpg[/img:aqz1mllg]
yeah, I know the synth isn’t even out yet, but I started working on a layout. Once I get some details on the compatibility between the pulse2 and pulse I’ll make this panel work for both, complete with a skin change depending on which version of the synth you’re using. The Waldorf site states full backwards compatibility but that might only be for sounds/programs, not necessarily identical CC/Sysex per parameters…

I’ll also be making all CV parameters available for the pro version of the pulse, again details are sketchy on the pulse2 although it’s still supposed to be released in the summer of 2012.

Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen

[marcianus]

"Layzer2":tqkano6q wrote:

probably the most important thing to know about CTRLR is the xx variable.

when you add a control, ie; a slider or button…. you tell the control
what value you want to send using the xx variable.

for example, setting a control with a range of 0 – 127 will
give xx a value of 0-127 in a midi message like : F0 11 22 43 09 xx F7 plugged into the control’s midi message box

good luck and have fun making CTRLRS!!!!![/quote:tqkano6q]

I am a newcomer to Ctrl (this is my first post).
My first "Hello World" is a Tooggle Button to ON/OFF GM Mode in a Roland Jv2080

I need to send [F0 7E 7F 09 01 F7] (GM ON) or [F0 7E 7F 09 02 F7] (GM OFF)

From the upper example, I configure the modulator (Tooggle Button):

MIDI MESSAGE TYPE: 5 – SYSEX
SYSEX FORMULA: F0 7E 7F 09 xx F7

But, where I configure the "real" values (01 , 02) to pass to xx?
Where to assign values 01 and 02 to the two positions of Toggle Button

(my "Hello World" sends xx=00 and xx=01, not 01 and 02)

---

More questions:

What is exactly ‘xx’?. I think is a variable value controled via modulators, used by internal code of Cntrl to create SYSEX strings).

Ok, there is more ‘named’ variables (example from JP8080 panel):
F0 41 10 00 06 12 01 00 k0 32 xx z5 f7

k0: I think is a global variable (there are, by inspection, k0 to k16). Are they global to a individual panel o to all panels open?

xx: I think is the same

z5: usually this byte is CHECKSUM for ROLAND SYSEX Mssgs. Where is it calculated? Internal code not accesible?
There is a z0, z1, etc, etc?

Are more ‘named’ variables I need to know?

Sorry if the question seems too dumb.

[LilCthulhu]

Hi ” title=”Wink” />

Well basically I now have 4 "sub-panels" for each tone, 1 other for "active tone" (that is when you modify multiple tones at once), I have the common and effects parts "sub-"-panel also ” title=”Wink” /> I’m currently able to modify the patch in the temporary section, I’m able to read the patch from the synth… but somehow there is an issue with writing the patch back to the synth (it does come back with slight difference). So I have around 390 modulators in the panel. You need 4 sub-panels because you need to keep a memory of all settings… The active tone subpanel is not yet working… and I plan of adding to that a library (separate from a program manager) that would include around 4000 unique patch I gathered on the internet in different format and will convert them in a format that will be able to be sent back to the synth and ctrlr ” title=”Wink” />

I will surely need someone to beta-test this when I’m ready for that ” title=”Wink” /> And in any case I abandon the project for time issue, I can now count on someone else to take over ” title=”Wink” />

Here’s a preview, I’m quite happy with the look ” title=”Wink” /> Without having to design additional controls, I’ve been able to replicate the look and feel of the JDs. I just wished that we could make the slider "indicator" square instead of rounded ” title=”Wink” />…

[img:2y8xz14n]http://dl.dropbox.com/u/4540586/ctrlr/jd-800.png[/img:2y8xz14n]

[Tronic]

"atom":n1a2z13g wrote:

there is the modulator list option that can export to csv, html, xml but if you want to "import" it later then it’s not for you, why do you want to export/import parameters ?[/quote:n1a2z13g]
I try to give an example of use.
My synth has internally different machines for the synthesis, a section fx, and a section lfo.
each machine has different parameters for synthesis, for example: start the sample, the end of the sample, etc..
then save to a file only the synthesis section, and then recall it, but without changing the fx section, or LFO, which would eventually even they can be saved in separate files, so you have the sub-patch, for each group of parameters.
So you do not have a patch only saved as a program, but you can load presets for example only the synthesis section.

[darlock]

My gear list.
Hardware-Gear:
Access Virus Powercore
Access Virus TI Keyboard
Alesis Andromeda A6
Casio VZ-10m
Clavia NordLead III
KORG MS2000R
KORG Z1EX
Novation K-Station
Novation Supernova II PRO-X Keyboard
Novation Nova laptop
Quasimidi Sirius
Roland JP-8080
Roland SH-201
Roland V-Synth
Waldorf micro Q
Waldorf Microwave PC
Waldorf D-Coder
Yamaha S90ES+MLAN+3xPLG150-AN Boards
Yamaha FS1R
Yamaha AN200
Yamaha ED-10
Yamaha SW1000XG+PLG150-VL board
Powercore DSP array(mk1, mk2, firewire)
Creamware DSP array(pulsar+pulsarII)
UAD DSP CARD
MOTU MIDI Timepiece AV
Steinberg midex 8 2x
Magma PCI extender
Recording:
DBX Quantum
DBX 376
RME HDSP9652 3x
Yamaha i88x
Presonus FireStation
Behringer ADA-8000
Yamaha DS2416+DS2416+AX16AT
Samson Rubycon R6a
Rode NT1
NADY TCM1050
Apogee DA1000E-20

[minimalist]

"omutumo":3emc9z1r wrote:

Can you make Ctrlr pick up the currently selected preset on the Pulse as you scroll through[/quote:3emc9z1r]
As far as I know: Not at the moment but later.

2. question: The answer you can find in your other thread. The magical word is "FixedSlider". ” title=”Wink” />

[atom]

[b:3rqapaz1]Please try to read them and use them.[/b:3rqapaz1]

1. Post bugs (any small ones, big ones, quick ones) in the Bugs section, it allows anonymous posting
2. Post new feature requests or change of existing features in the Feature Requests section, it allows anonymous posting
3. Read the Changelog section once in a while there might be things that are already fixed/implemented[/size:3rqapaz1]
4. have phun

i’m on Gtalk: kubiak.roman [at] gmail.com
i’m on IRC: Freenode #ctrlr nickname a_tom

that’s all.

[atom]

that’s definetly going to happen, i want my CZ1000 working in my setup i love that synth.

[ViktorNova]

This software looks so nice! Kudos for using Juce and other multi-platform toolkits! I am very excited for Ctrlr to be available to the Linux community, and I am confident that it will be embraced with open arms and used by countless people. Us Linux users are extremely loyal to good software, currently what is meeting this need is JSynthlib, which is old and ugly and doesn’t seem to have been updated in 5 years. Your software looks WAY nicer, and so rad it’s available as a VST. We have less options than the other operating systems, and there are also some really awesome new VST hosts for Linux (energyXT, Renoise, Jost) and not a whole lot of native VSTs, so as word gets out about Ctlrlr you are going to see a huge spike in users from the Linux community.

Can you put together some quick step-by-step instructions for compiling Ctrlr in CodeLite for Linux, or add it to the wiki? I have CodeLite installed and eventually figured out how to open the CZ1000 workspace, but can’t figure out where to go from there, this is totally confusing! Is this something that CodeLite can do via the command-line? If so, I’d be willing to help make a spec file/SRPM which would make it super easy for packagers to make Ctrlr packages for different distros. I am working in Unity Linux, a close derivative of Mandriva, and would love to use Ctrlr on this platform.

I’m also developing a distro geared at show automation using MIDI/DMX/OSC and would love to include Ctrlr if possible as well

[atom]

I’m doing the CZ1000 editor, the CZ series is a weird line of synths, but it’s possible to edit them.

[atom]

ok so i updated all the windows builds, x64 is back.

A major bug was found while doing some Blofeld work that caused Ctrlr to crash (any) that’s fixed, there shouldn’t be any startup errors anymore. I took me 2 nights to find that bug it was a nasty one.

Blofeld now works both ways, i did some testing myself as i got the unit for tests from a guy from a polish music magazine that talked to me (http://eis.com.pl).

SE ATC1x is up and can be tested, current queue is Oberheim Matrix 6R, Casio CZ1000, Yamaha AN1x, i had some feedback that a nice user is starting the UI work
on the A6 editor.

There are some new settings for UI and Midi, for now only the base colour works for some editors, this will be all implemented later on.
A new Window menu is added there is one option that you can try with editors that have no Tabs, this will break up groups into smaller windows you can move
around. I’ll add tab support later on, and some other stuff to that, then those colours in the settings will work, for now it’s all hardcoded sorry for that.

the MIDI settings will be added i’m just thinking how to do that so it’s as simple as possible.

As you can see i moved the whole project to sf.net cause googlecode was pissing me off, i hope the sf will be better.

MAC builds are comming next week once i set up a new PC, working in VMware is not what i expected it to be, and it’s not a good debugging solution, i don’t
want to post more MAC builds that crash or do not work, so please be patient i’ll post them when i’m sure they will work.

I fixed some other editors that had the old engine so they should work now (MKS70, Juno106, Matrix 1000)

There is a "Trac" link on the top, i’ll try to use that from now on, adding milestones progress and resolving tickets if anyone
wants to post some issues there it might be a bit better then using the forum.

Oh yeah i had to disable the email feature on the forum since sf.net does not allow sending emails from websites hosted
on their servers, it’s not my fault, i disabled the need to confirm accounts via email but you won’t receive any PM notifications
and stuff. Sorry for that, but i want to keep all the project stuff in one place.

[rabies]

i forgot: controller for the yamaha qy series as well, particularly the qy70. thanks mucho!

[rabies]

i love this site. what a great help. thanks!

i hope you could come up with a controller for the casio cz101/1000 in the near future.

keep up the good work.

thanks again!

[atom]

For now i’ve been using CodeLite to do Linux builds, get that it’s a very nice little IDE for Linux, there is a Casio – CZ1000 workspace, load that in CodeLite and try to build the EdoController first, you will definetly need latest juce source and VST SDK 2.4, there are 2 paths in the project settins (compiler settings, include search paths) that need to point to those elements, and that’s it, the EdoController should build.

give that a try and let me know.

[atom]

1) forum was down cause hostnine my ISP crashed
2) i’m doing a major change in the engine that will allow multiple instances of the same plugin without problems, before the change all settings were shared (it’s a whole static memory contents)
3) the rewrite forced me to change the engine but it did some good, after the change there will be no need to write any actual C++ code, just one line
[code:fntlwaso]
new MyEditor()
[/code:fntlwaso]
the rest will be taken care by the engine
4) no more prefixes for controller names, they can be named in any way you want
5) LUA is there is a better way, you will be able to do almost anything in the Ctrlr without C++ compiling, moving and resizing UI components and also creating new ones
6) i started to build the librarian engine, it will be LUA based, but it will allow for simple SysEx dump/send implementations for all devices
7) an additional feature for Synths like the CZ1000 is added, that will send entire SysEx program each time you change any parameter, the CZ1000 editor is beeing built now too
once i’m done i plan on creating a screencast that will guide you step by step how to build your own Ctrlr using freely available tools, i think this will better then writing lines of text that might not cover everything.

this might take a few days since i need to manualy change all the existing Ctrlr to work with the new engine so be patient, once i’m done new builds will be posted.

that’s it, atom out.

[atom]

Well i’m with you on that one, i created this to control my 80s digital hardware (dx21, tx7, cz100, jx8p) cause programming them is hard and often makes me hate making music, so i don’t make music.

I wanted to create a simple webpage where requests would be posted with links to manuals(midi specs) and people could click yes/no so i knew how much need is for a particular ctrlr.

[atom]

it’s something i’ve been planning for some time, i started it once, i have the CZ1000 it’s the same unit. Once i get the engine stuff working i’ll add support for theese devices. By theese devices i mean those that don’t use short messages to change one parameter, they take all the parameter data and put it in one big chunk of SysEx data, everytime you change something all that data must be transmitted. It’s a bit different approach but it can be done and will be done, since there are a lot more devices like that.

[ozoneau]

DRUMS:
Machinedrum SPSUW mk2 + TM, Yamaha RY30+2cards, Roland R8+8cards, Korg ER1, Korg ES1, Jomox Mbase01, Kawai -5
SYNTHS:
Korg Z1, Alesis Micron, Yamaha SY85, Waldorf MicroQ, Mam MB33 mk2, DSI Mopho, Yamaha DX200, Korg EA1, Casio VZ8m, Korg Wavestation AD, Yamaha TX81z, Kawai K1m, Korg X5/DR, Roland GR1
EFFECTS:
Yamaha FX900 + FC900, Alesis 3630, Alesis Quadraverb+, Roland GP8, Roland EF303, Pioneer EFX500, Boss GT8
OTHER:
Imac 24inch c2d, Ableton Live 7.0.18, Yamaha RS7000, Motu 828 mk2, NI Audio Kontrol 1, Roland GI20, Motu Microlite, Emagic MT4, Godin Freeway SA, Yamaha Promix01, Adam A7, Korg Padkontrol, KDJ500, Technics/Pioneer Headphones, Ableton Live 7, Meinl Djembe, Samick Guitars, Classical Guitar, Guitar Pedals

Should upgrade to Live 8 but mchinedrum is too much fun and I don’t like ‘rumours of crashes.’

@ DBM: the Akai Miniak its the same as the Alesis Micron, meaning you can use "MICRONAU’ if you re on a mac… it works perfectly in Live, and its free!