Date   

Re: Tiny box "virtual switch"

ossandust
 

This TinyBox feature is also available in the UnO2 firmware. But maybe it's possible to do it in Ableton Live indeed, that I don't know. 


Tiny box "virtual switch"

James Wilkens
 

I noticed this feature in the Tiny Box video which allows you to trigger a foot switch with the expression pedal. 
I'm wondering if there is a way to do this without the Tiny Box. I would like to be able to turn on a wah effect by pushing the expression pedal all the way down like on a real wah.
I am using MIDI CC to trigger effects in Ableton Live. I'm thinking maybe an Ableton Live cue could toggle the effect on and off when it sees a specific CC value of 127 while also controlling the wah "pedal" on the same CC#.
Any way to do this? 

Jim W


Re: Tinybox setup

Timothy Payne
 

OK thanks for clearing this up.


Re: Tinybox setup

ossandust
 

No, the setlist content is stored in the TinyBox so you can use it without computer. You only need the computer (or Raspberry Pi) if you want to see sheet music or if you want to see the status page (which shows the current song title)


Re: Tinybox setup

Timothy Payne
 

Ok I can understand that. I will just have to be more careful. Does this mean that when you use the Tinybox on a gig you have to have it connected to a computer or Raspberry PI to have the setlist even if you don't upload charts or sheet music?

Tim
https://theguitarrag.com

Sent from my Samsung Galaxy S10+


On Sun, Jun 28, 2020, 11:26 AM ossandust <ossan.dust@...> wrote:
It's not possible to retrieve a setup from the TinyBox, because the TinyBox only receives part of the setup info. All bank names, preset names etc. are not stored in the TinyBox, they are just used by the web server which is part of ControlCenter to display them on the remote status page. The preset contents are compiled before being sent to the TinyBox so also that info would be difficult to restore from the compiled binary data.


Re: Tinybox setup

ossandust
 

It's not possible to retrieve a setup from the TinyBox, because the TinyBox only receives part of the setup info. All bank names, preset names etc. are not stored in the TinyBox, they are just used by the web server which is part of ControlCenter to display them on the remote status page. The preset contents are compiled before being sent to the TinyBox so also that info would be difficult to restore from the compiled binary data.


Tinybox setup

Timothy Payne
 

I have a question about the setup file once it has been sent to the Tinybox. Is there a way to retrieve the setup info that is stored on the Tinybox? For instance my computer crashed and I lost everything except my files. Fortunately I had saved the setup to a text file but I had made modifications to the setup on the Tinybox but not to the text file. No big deal but it would be nice to be able to pull the setup from the Tinybox and save it. If there is a way I can't see it. The Tinybox is working better than I imagined. Thank you for all your help!  


Re: FCB1010 OEM Rel 2.5 Firmware known bugs

ossandust
 

1) is known behavior, 2) is a known bug, 3) the SysEx format as described in the document is accurate.


Re: FCB1010 OEM Rel 2.5 Firmware known bugs

chrisw_63
 

I wonder if Bug#2 was my problem a while back.. I only had one MIDI DIN on my USB interface to feed my DAW, so had a pad controller feeding the FCB1010, that output feeding a Yamaha S90 so I could control it's volume when using native sounds, then the output of the S90 into my DAW.  Every now and then, the S90 would change sounds, randomly, in the middle of playing.  Changing the MIDI channel of the FCB1010 stopped the program changes.  A few weeks later I got an iConnectivity MIDI4+ (same as the mio4 now) with two extra MIDI DIN sets, and even when I changed the FCB1010 channel back, the problem stayed away.


FCB1010 OEM Rel 2.5 Firmware known bugs

Earth.Sky.Surf5@...
 
Edited

Does any one have a list of known bugs of the FCB1010 with the original OEM (Behringer) firmware release 2.5?

I am digging further into the more advanced "features" of this foot controller and finding more bugs and "outright annoying design features".

Some of these I have already mentioned in previous posts, but to keep it complete here is my list:

1) Bad feature: initial expression pedal movements will only register output if it changes by 10 or more units.
2) Bug: When the midi merge function is used, the output data gets mangled. Example, midi keyboard playing notes feeds into foot control midi input, foot controller sends expression pedal output.
3) Bug: SysEx dump of button assignments some times gives values consistent with what the hardware LED shows and some times not. Looks as if extra bytes are inserted randomly. I used Reaper to read the data then mapped it out in a spreadsheet. I looked at the first 5 buttons and it's a mess. Refs. [1] and [2] give an idea of what data is in there, but this is not exact either. Initially I had very little faith that when I send this SysEx data back to the foot controller that it will do it correctly. So I did some checks, save the output SysEx data, send it back to the foot controller, then back out again and compare the SysEx dumps -- no change, also checked button assignments using the foot controller LED no change as required. I then changed on byte of the SysEx where I know what bank, button and function it refers to, sent this back to the foot controller and used the foot controller LED to check the assignment: assignment change seen and was correct. From this I conclude the SysEx format is not regular, i.e. if you determine the SysEx format for one button for one bank, these will not necessarily appear by a constant memory offset for the next button. This renders Ref. [1] and [2] not accurate for version 2.5 OEM (Original Equipment Manufacturer) firmware. Whether the third party readers of the FCB1010 SysEx dump get it right or not for OEM firmware 2.5 is unknown.

Ref. [1] Source of _home_httpd_data_media-data_2_FCB1010_SysEx_Structure-.pdf
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwiDqfqSk5zqAhWaX30KHfPsCycQFjAAegQIAhAB&url=https%3A%2F%2Fc3.zzounds.com%2Fmedia%2FFCB1010_SysEx_Structure-2c6634e4d8b813c58d175d05a0def4d2.pdf&usg=AOvVaw0Q5NUm4mri_l_asQmLgSW5

Ref. [2] Source of 248-6208-behringer-fcb1010--40933.pdf
https://www.parts-express.com/pedocs/more-info/248-6208-behringer-fcb1010--40933.pdf


Re: FCB1010 Expression pedal mod?

chrisw_63
 

Not easily, no.  Normal expression pedals use a potentiometer - a variable resistor, usually 50k ohms.  The FCB1010 optical arrangement sends a voltage level based on the light hitting it.  While you certainly could investigate the correct voltage range rig up something to make a regular expression pedal work, it wouldn't be simple.  Have you asked Behringer what it would cost to replace the parts?  Or fix it for you?


FCB1010 Expression pedal mod?

ahab jones
 

One of the expression pedals has quit working and the opto circuit is bad for that pedal is there a way to convert the wiring to connect a seperate expression pedal to the unit to take the place of the broken one?


Re: TinyBox

Earth.Sky.Surf5@...
 
Edited

Thanks ossandust, just giving the midiStroke a burl now ... nice :) . Brilliant, just what I need to control Ableton. Thanks.


Re: TinyBox

ossandust
 

On Sat, Jun 13, 2020 at 08:31 PM, <Earth.Sky.Surf5@...> wrote:
Ableton does not allow midi messages to control things like delete clip
I don't have experience with Ableton. If a function is not MIDI controllable, maybe you can still assign a keyboard shortcut to it? And then use an app like midiStroke to convert MIDI commands into keystrokes 


Re: TinyBox

Earth.Sky.Surf5@...
 

Thanks ossandust. Your TinyBox has me intrigued.  Being both a keyboard and violin player, and in particular with the later, I do not have my hands free to trigger off things with a mouse or computer keyboard combinations, only have my feet to trigger off things. I use predominantly Ableton Live (lite). If have the FCB1010 with the original Behringer chip and am looking into the Uno offerings, i.e. Uno, Uno2 or TinyBox, since I am hitting the limits of what the OEM chip can do.

Standard midi message ok with Ableton, I can get by, but Ableton does not allow midi messages to control things like delete clip (I just recorded), so it can be used like a regular looper. Sure if I get Ableton Max I could program it, but at the moment that is way beyond my budget. So have you or any one else used the TinyBox to control Ableton Live much like Ableton's Push hardware? If so, could this be done with the Lite version of Ableton?

Thanks for the video.

I will have a peek at the group especially for the TinyBox.


Re: TinyBox

ossandust
 

On Sat, Jun 13, 2020 at 03:49 PM, chrisw_63 wrote:
Wow.. that was a lot of work!
Been working on it on and off for the past few years now, and it required a pandemic "Belgium-style" (2-month lockdown) to get it finally released... 


Re: TinyBox

chrisw_63
 

Wow.. that was a lot of work!


Re: TinyBox

ossandust
 

For your info : I started a separate TinyBox specific user group : https://groups.io/g/tinybox/ 

- the TinyBox purchase includes a specific firmware chip for the FCB1010, which turns it into a dummy slave for the TinyBox
- TinyBox connects with the FCB1010 through a 7-pins MIDI cable, so the FCB1010 needs to be equipped with a "Single Cable Kit" : FCB1010 Single Cable Kit  
- With this kit installed TinyBox does power the FCB1010, so no more mains cable needed for the FCB1010
- MIDI is being sent/received by the TinyBox only - there is a MIDI IN and a MIDI OUT connector, with a MIDI filter/mapper in between to transform MIDI which is passing through. And there is USB-MIDI IN/OUT to control software with the FCB1010 or to use the TinyBox as regular MIDI-USB interface. Lots of detailed info about MIDI routing in an appendix of the user manual ( https://www.tinybox.rocks/assets/files/TinyBox_Usermanual.pdf from p.65)
- the "UnO2" firmware is a shrinked down version of what's inside the TinyBox. It doesn't have any of the "MIDI filter/mapper" functionality, and it relies on the FCB1010 setup storage capacity, which is 1% of the TinyBox storage.  


Re: TinyBox

chrisw_63
 

This is pretty awesome!  So as far as I know, even Uno (1) doesn't allow the FCB to change state in reaction to received MIDI.  So this has to be the Uno2 chip in action???  You said in the release announcement that it was a smaller version of the TinyBox software.  Yet you have the TinyBox connected to the FCB in the video.  Is there a default setup to get them working together?
And it's connected with one cable that does MIDI In, MIDI Out, and power.  I'd like to know about that mod, too!  Has to be at least a 6-pin DIN.  Is it the standard All In One cable mod that's been around for years?  And it looks like the TinyBox is wired for it directly, so it needs that mod or a special cable...   Inquiring minds want to know!  :-)


Re: TinyBox

sirnothing23
 

Wow.  this seems totally revolutionary to me. 
I have so many questions, but to get started ... 
The FCB1010 is equipped with an Un0 chip?  Any version?
And is the midi / power cable a standard 5 or 7 pin MIDI? Once programmed, the TinyBox/Pi power supply powers the FCB too?  too cool !!! 

My other general questions are aboutMIDI routing - MIDI is being sent and received by the TinyBox and/or the FCB?  
I assume this is the place to ask these things.

I think I'm beginning to get it (slowly).  The FCB GUI on the iPad really brings it to life for me.  I'll just need to get it and play with it for a pandemic or two.  
I'm very excited.
thank you !!!

281 - 300 of 28963