|
|
Post by esofron on May 10, 2019 16:38:16 GMT
Hi esofron , My apologies - I was missing an END in the code. I have corrected that, so you should paste the amended code above, but here are the steps in MidiFire: 1. Use the '+' menu and drop the input port that represents the hardware pedal 2. Drop an Event Monitor onto the canvas and connect the pedal to it. 3. Use the detail cog to open the Event Monitor 4. Move the pedal - you should see events and the CC that is being generated. They should all start with the same two bytes BX XX (where X will be values in the monitor) 5. When you have those two bytes that your pedal is sending, add a StreamByter to the canvas and connected the pedal port to it 6. Paste the code above into the StreamByter and change ASS K0 = B0 01, replacing B0 and 01 with the two bytes you got from step 4 7. Press 'Install Rules' and hopefully no errors. 8. Drop BiasFX output port onto canvas and connect StreamByter to it. 9. Switch to BiasFX, enable learn mode for the wah and move the hardware pedal. It should learn B0 50 (or CC 80 on channel 1) Now, when you move the pedal up it will engage the way at full on as soon as it goes positive and off when it goes back to 0. Regards, Nic. On step 9 when i move the hw pedal it recognize it as 07. |
|
nic
Soapbox Supremo 
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on May 10, 2019 16:51:12 GMT
Either the XX = XX +B line was removed too early, or BiasFX is listening to your hardware pedal directly. I suspect the latter. Please make sure in BiasFX' MIDI configuration that while doing the learn that it is not listening to the hardware pedal.
If BiasFX cannot be configured to not listen to the pedal directly, does it allow you to enter a CC manually for that wah control? If so, you just need to set to 81, channel 1 (assuming you made the change from 50 to 51 as per previous email)
|
|
|
|
Post by esofron on May 10, 2019 17:02:00 GMT
ok i try this one. for sure i can assign the CC # directly. i have to options to complete 1. Toggle cry wah 2. cry wah which is the pedal. i believe i have to complete manually the CC 81 to the #1 option, correct? Attachments:
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on May 10, 2019 17:29:32 GMT
Oooh, I would leave it at CC85 and change the script to ASS K2 == B0 55, so the top of the script should now look like:
# BiasFX autowah engage by audeonic
IF LOAD
ASS K0 = B0 07 # this needs to be the CC your pedal sends
ASS K2 = B0 55 # BiasFX wah CC 85
...
Regards, Nic.
|
|
|
|
Post by esofron on May 10, 2019 21:41:09 GMT
Nic thanks a lot it worked. Thanks for your support.
here is the final code.
# Enter rules here
# Press 'Install Rules' when done
# BiasFX autowah engage by audeonic
IF LOAD
ASS K0 = B0 07 # this needs to be the CC your pedal sends
ASS K2 = B0 55 # this is our secret CC
ASS L80 = 0 # flag for toggling wah just the once
END
# trap the hardware CC
IF M0 == K0 K1
# hardware pedal went to 0, disengage wah
IF M2 == 2
IF L80 == 1
SND K2 K3 00
ASS L80 = 0
END
END
# hardware pedal went positive, engage wah
IF M2 > 5
IF L80 == 0
SND K2 K3 7F
ASS L80 = 1
END
END
# block hardware pedal CC whilst learning
# XX = XX +B
END
|
|
|
|
Post by esofron on May 10, 2019 21:46:24 GMT
i just have another issue now.
If the midifire is running with this stream byter, the biasfx cannot accept other CC commands.
I have other 4 buttons that sends CC commands for load/unload pedals.
Can you help solve this one?
thanks.
|
|
|
|
Post by esofron on May 10, 2019 22:09:59 GMT
Even when I create single connection then the CC commands stops working. it looks that it accepts the commands but cannot processed. if I remove the connection between them it works. any thought what is the fault? Attachments:
|
|
|
|
Post by esofron on May 10, 2019 22:53:45 GMT
Ok I solved it by using different channel on bias fx and use a channel strip to remap from ch1 to bias fx channel. i don’t know if it is correct , but it works. why is this happening? Can you please explain? thanks Attachments:
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on May 11, 2019 7:06:29 GMT
Hi esofron , Yes, it is because BiasFX is seeing the button messages from both the pedal and MidiFire simultaneously so probably switching on and off or just getting confused. Your channel strip trick will work, or you put XX = XX +B right at the bottom of the StreamByter script to block all events, so the only thing coming out of MidiFire is the wah engage/disengage message. Regards, Nic. |
|
|
|
Post by esofron on May 11, 2019 8:39:49 GMT
Hi esofron , Yes, it is because BiasFX is seeing the button messages from both the pedal and MidiFire simultaneously so probably switching on and off or just getting confused. Your channel strip trick will work, or you put XX = XX +B right at the bottom of the StreamByter script to block all events, so the only thing coming out of MidiFire is the wah engage/disengage message. Regards, Nic. excellent. thanks a lot again for your great support. i am gonna test the XX = XX + B also. how can i learn to program in streambyter? is there any how to etc? many thanks again. |
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on May 13, 2019 9:40:36 GMT
Hi esofron , > how can i learn to program in streambyter? is there any how to etc?Right now, the built-in manual is the definitive reference although there is obviously loads of code and help here on the forum. You may have noticed that I released 'StreamByter University' which is designed to get started with StreamByter programming. Unfortunately, right now it is for the StramByterAU version so not relevant to MidiFire just yet. MidiFire will soon get the new StreamByter features at which point it will be of use. There is the old Stream Byter Guide which was written for MidiBridge - this gives you an understanding of the pattern matching rules which are supported in MidiFire. Regards, Nic. |
|
|
|
Post by esofron on May 17, 2019 10:53:16 GMT
Hi Nic. i havent noticed the streambyter university. how can i get access ?
I am going to wait for the update with the new streambyter on midifire.
thanks.
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on May 17, 2019 11:14:30 GMT
|
|
|
|
Post by vaultnaemsae on May 21, 2019 12:24:24 GMT
Hi all,
Another quick question on this one...If one wants to delay the de/activation of the triggered ON/OFF CC in this script which part do you need to adjust?
In my case, the switching creates very fast changes in tone quality and feels a little unnatural for certain applications.
Thanks,
Luke
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on May 21, 2019 12:44:35 GMT
Hi vaultnaemsae , Just add a delay to the SND rule (there are two of them in the script above, so you can specify a different delay for engage/disengage). This will delay the event for 500ms; the only place in StreamByter where you use a decimal number natively! ;-) SND K2 K3 00 +D500Regards, Nic. |
|
