F.A.Q.

I've got a FX rack in my home/professional studio and I don't know if Hickory or Dickory will fit in. How big they are exactly?

Relax, we got you covered! Hickory and Dickory have a 19 inch x 3RU (48.26cm x 13.33cm) standard panel. Both of them come with the necessary screrwing holes.

 

Which type of power supply do I need?

None at all. Both devices can be updated and powered via their USB type B connector. They also send MIDI messages through it.

 

Do I have to manually install any drivers?

No. Just plug the device to your USB port and wait for the OS to automatically install the drivers for you. Before that they will be recognized by your host.

 

Can Hickory or Dickory be used to control other plugins apart from FabFilter's ProQ/Pro C?

Of course. Although they are designed for controlling Pro Q and Pro C, both devices are MIDI controllers and can be used to control anything that supports MIDI control via Control Change messages.

 

Can the default MIDI channels or Control Change numbers be modified?

We are working hard to develop a tiny application so you can modify any of this parameters (and more) in a simple way. We’ll keep you updated. In the meantime the only way to change them is to modify the source code and update the firmware in the Teensy microcontroller.

But maybe you don’t feel very comfortable with programming. If that is the case, you can always use some intermediate software like ReaLearn (if you are using REAPER) or Midi Translator, which, among other things can transform any incoming MIDI message into anything you want.

Finally, if you have a very strong need of modifying any of this parameters from factory, you can contact us and we could send you a custom version of the firmware.

 

My host is running, but it seems to ignore the controller when I turn it on. What can I do?

Any MIDI controller must be powered on before launching your host app, otherwise it will not be recognized. Hickory and Dickory are no different in that way. Because we don't work in Microsoft we can't be shure about what the reason is, but we suspect it has something to do with Windows and how it manages the drivers.

In any case the right way for using any MIDI controller is to power it on BEFORE your running your host.

 

Why Hickory and Dickory don't come with a case? Is this not just WEIRD?

Oh, we’ve though a lot about that. And we came to the conclusion of get rid of it. Why?

Short answer: it's unnecessary and expensive.

Long answer: in OhMyBytes we came from the modular synth world, a beautiful place where each module came with their circuits exposed, and the only box you have to care about is the rack where everything is going to be screwed up. And as you can suppose that gave us the happy idea to get by without a case.

The thing is that Hickory and Dickory are MIDI controllers designed to live in a rack, not on a desktop. It’s true that in a desktop device a case for holding and protecting all the circuits have a lot of sense. However, the rear side of a rack is not usually exposed to any elements or unwanted fingering.

On the other hand and as a general rule of thumb: electronic equipment overheats. So using a case may have imply to use some kind of cooling system (like a fan, for example). And this imply more cost. In our case, even though both Hickory and Dickory have a minimum current consumption and they barely heat up, we think that the best cooling system for them is to let them be in the open air.

Last but not least: making a custom case for an electronic device like this is surprisingly expensive (almost as the rest of the circuit). And from the beginning our goal is to make quality devices as cheap as possible.

 

Can I use Hickory or Dickory with MAC?

Unfortunately we don’t have any of this wonderful computers to perform a detailed research. Nevertheless, we have to say that we could make a brief test using a MacBook Air with no problems at all.

 

There are two versions of each product. Why is that?

In OhMyBytes we are great DIY fans, so much we don’t want to take away that from our friends XD. And also we think that to offer people the chance to save some money by acquiring an unassembled kit is always a good thing.

 

What is the point of the tiny cable in the MAIN PCB between Teensy's microUSB and the board USB? Why not use a microUSB cable directly connected to the Teensy?

There are two reasons for that. First is connector strength. In devices of this kind the USB connector is often the most vulnerable point, and precisely the Teensy's microUSB connector is, by construction, much less solid than an USB type B one.

The second reason is that the power supply signal from the computer is not going directly to the board. Instead, it goes through the on/off switch and a filter circuit, as recommended in this FTDI application note. Filtering supply signal, apart from being always a good praxis, is necessary to avoid the ADC from taking noisy values that could make our plugin controls “magically” move by their own on screen.

 

Is there any method to avoid the hassle of mapping all the MIDI parameters?

Well, yes and no. We know that assigning all the Control Change messages one by one can be a bit overwhelming. Luckily, all  PRO Q2/ Pro C2/ Pro L plugins have a MIDI LEARN function to make things easier.

Our initial intention was to provide everyone with a downloadable pre-configured preset in order to make it as straightforward as possible. Unfortunately, it seems that when completing all the MIDI learn stuff and saving the preset the MIDI information is not saved in the .ffp file. It’s true that the MIDI mapping works on every new track or session you would possibly do, but if you export the preset to any other computer the mapping information is gone. Which means that the host stores the MIDI learn information somewhere else and we can’t do this task for you.

So, the good news are that as with any other MIDI controller, this is something you only will have to do once. Here you can find a table with the default MIDI Control Change numbers assigned to the panel switches and pots.

BUT again if you use Reaper things get more interesting. There is a fee and HYPER USEFUL JS plugin called ReaLearn, which inserted in the input FX section of any track can be used not only to map any MIDI parameter to any plugin, but also to adjust the behaviour of any control switch/pot/button you have. And YES, all this mapping can be exported as a ReaLearn preset. And also YES, we have done this presets available for you to download. You’re welcome! XD