Home › Forums › General › Using Ctrlr › yamaha fb-01
Tagged: FB-01
- This topic has 20 replies, 14 voices, and was last updated 3 years, 2 months ago by teevee.
-
AuthorPosts
-
May 28, 2010 at 6:22 pm #112
yamaha fb-01
hi tried to use the dx21 instrument as a start, as they are pretty closely related, but it doesnt seem to do anything
would be cool if you could drop one for this little thing many thanks
brought some old keyboards back to life ” title=”Smile” />
cant find much info on it either sorryJune 7, 2010 at 9:25 pm #1491[url:vjql1fbb]http://www.soundprogramming.net/manuals/Yamaha_FB-01_Manual.pdf[/url:vjql1fbb]
fb01 manual. Has the midi info.page 45 onwards
June 7, 2010 at 9:51 pm #1492some very weird parameters, will look into that but i’ll have to be looking at that along with the normal manual those descriptions of the parameters don’t tell me much. very weird unit
June 7, 2010 at 11:22 pm #1493[url:3futcv0h]http://sourceforge.net/projects/fb01editor/[/url:3futcv0h]
another solution is to check how this guy is doing it via i midimonitor like xmon ” title=”Wink” />
no need to go crazy with badly translated yamaha fm manuals ” title=”Wink” />
June 7, 2010 at 11:27 pm #1494yeah that will simplify things.
i’m looking at this editor and i can’t figure out this unit, is it a rom-pler is it a FM synth, operatos and some "piano" sounds note ranges for instruments, weird.
June 8, 2010 at 12:54 am #14954-op fm synth….
with just sines (unlike tx81z which has 8 waveforms this has only sine)June 13, 2010 at 8:30 pm #1496does this editor you linked work ? it transimts some weird messages.
July 9, 2010 at 7:52 pm #1497sorry havent had time to test it yet will do this week though
hoever i think i found in the service manual what you are looking for. on page 19
[url:2xok5art]http://manuals.fdiskc.com/flat/Yamaha%20FB-01%20Service%20Manual.pdf[/url:2xok5art]the voice parameter list
May 11, 2015 at 3:10 pm #46572How have things gone on the FB-01 front?
Any test-panels available?October 14, 2015 at 2:03 pm #60206are there CC numbers for the parameters?
i guess not all synths have CC. but that’s the easiest way to get things going right?
December 27, 2016 at 8:24 pm #70822an old thread but if anyone is still into it, I found this, might help?
December 27, 2016 at 9:31 pm #70823an old thread but if anyone is still into it, I found this, might help?
I already know most of the SysEx secrets of the FB01 and an FB01 ctrlr panel is on my TODO list. I know how to do it, but don’t have much time to do it.
And yes, the FB01 is a strange unit where SysEx implementation is concerned. Very different from DX21 and TX81Z. But also very powerful. And I am not talking about those 8 waveforms that are not as important as some people think. I have written SysEx editors for both FB01 and DX21/TX81Z in the 90’s (YSEDITOR for ATARI ST) so I know what I am talking about.December 27, 2016 at 11:59 pm #70826Very cool! Excited for this.
May 14, 2017 at 11:20 pm #72157Hi! It’s great to see people working on FB01. I have two of them and try to manage them properly from my Linux box.
Some time ago (2010) I tried to write driver for JSynthLib, still work in progress and meanwhile JSynthLib seemed to stop development. So couple days ago I started a panel in Ctrlr. You can see what is done till now (system and instrument sections) in attachment. Comments welcome 🙂
I’m now stuck with multiple parameters in one message. I imagine it could be solved if there was a way to reference modulator’s value other modulators` mapping expressions. Something like my imaginary modValByName function:
modulatorValue * 127 + modValByName("otherModulator")
Second question could be probably answered by @m.tarenskeen probably. In FB01 MIDI docs I see that LFO values (speed, waveform, amd etc.) can be changed by different SysEx messages, for example for waveform: “F0 43 75 k0 10 0C ls F7”, but also “F0 43 75 k0 k1 13 ls F7”. Do you have idea why is that?
Attachments:
You must be logged in to view attached files.May 14, 2017 at 11:50 pm #72159About the LFO parameter change:
I think it has something to do with FB01’s way to handle the LFO in a multi/configuration vs. voiceparameters in a single voice.
Configuration parameterchange values are 7-bits (one byte), Voice parameterchange values are 8-bits (2 bytes with 4-bits used in each).
It’s easier to write a Ctrlr panel for the configuration parameters than for the voice parameters. The FB01 voiceparameter sysex will need some custom LUA coding to be handled.
BTW: I have started creating a FB01 panel myself, but hardly have any time to work on it.
December 16, 2017 at 6:39 pm #73866i just picked up an fb-01, has anybody made any progress with the panel?
December 16, 2017 at 8:03 pm #73869from what someone said the other day, Feedback and Algorithm select
are at the same address: 0C 00xxxyyy page53 of the manual.feedback is xxx, algorithm is yyy
so to change either independently, you’re going to have to know
what the other one is.yyy is easy: it’s always 0-7 (8 values) – 000-111 binary
but if you just change that – say you leave xxx as 000,
you will always get the same feedback amount.in the same way, xxx can be 000-111 (and then you have those 2
unused bits: you can send anything you want at those, they
won’t make any difference. in terms of decimal, you could use
numbers where the leftmost bit was always 1, for example, or
both could always be 1, it won’t affect what’s going on a
xxx and yyy.but because you have Lua, you don’t have to worry about that;
you just have to know what both values are each time you send
a sysex message – ie: ‘get’ both values; because if you want to
set yyy, you have (0-7)=8 situations x the 8 values you want to
select.so you want to getValue for feedback, you have to getValue for
algorithm too. so you want to change the feedback value, you
getValue on both:
‘algo= panel:getModulatorByName..etc..:getValue()
fbck= panel:;getModulatorByName..etc..:getValue()
for i=0,7 do
if algo == i then –[ oo dear, lua-newb, i’m getting lost here lol ]–
for k,v in pairs –[ think a table would probably help ]–
–[ at this point someone more competent comes to the rescue! ] —
end
end
end`something like that will deliver your correct *combination of values*
and then you will have what you need to send your sysex.October 9, 2020 at 4:59 am #120170Hello All,
I’m new here, just got a FB-01 on ebay and I really like it. I’m creating(editing) some sounds on it with a program I found online named FB01 Sound Editor V2.2. (From Meslin Frederic). I managed to store a couple of modified sounds on it, but it doen’t edit everything. Has someone figured out a panel for the FB-01?
(I already posted this on another thread, so I’m adding it here too for visibility)
ThanksDecember 20, 2020 at 8:05 am #121151I have started a panel for the FB-01, the matter goes very slowly given my ignorance about CTRLR, Lua, MIDI (from what I am seeing ..) and everything in general.
Attached is my progress in the form of the panel itself.
I prepared a table with the sysex parameters of the three FB01 reception modes.
But there are many things that I do not understand:
1.- the parameters that modify several different values in one byte
55h -> [aa0 *****] is used for “Keyboard scaling (rate) depth” and for “Attack rate”
I see that I have to change one just keeping the other in another different control, I don’t understand this.2.- Global variables, I’ve been searching for days in the forum and I can’t find a clear way to declare this global variable, I think I did it for the midi channel of my sysex chain, but I don’t know how I did it.
The panel is missing a lot, I just did a little positioning of controls but I can’t quite decide how to place them, so in this one I had already deleted many.
Attachments:
You must be logged in to view attached files.December 21, 2020 at 9:11 pm #121175I am also still working on an FB01 panel. I can assure you: this one will need a fair amount of LUA programming. The FB01 really has a tricky SysEx implementation. For now I will be concentrating on FM patchparameter control, which can’t be done on the unit itself.
I will not show any pictures if there is nothing actually working yet. I am not like Behringer promising another xxxxx clone “soon” 😉
Be patient ….
-
AuthorPosts
- The forum ‘Using Ctrlr’ is closed to new topics and replies.