Category Archives: Updates

Broken Links

Due to a change made by DropBox, a number of the links on this site to user manuals and software have been broken. I am fixing these as quickly as possible so I would ask you to be patient while I do this.

Update: I’ve been through all the links and hopefully all have been fixed 🙂

If you find any other broken links please do post a comment below to let me know.

Advertisements

Minor Update to BN Librarian

I’ve noticed that a few people, myself included ;-), sometimes forget that, when uploading  new DSP code, the Blue Nebula must be powered from the 12V DC supply input. If you only have the USB cable attached it will appear to work but in fact the new code will not have been uploaded – only the effect names will have changed.

(Technical note: this is because the USB cable only powers the microcontroller and the LCD in the Blue Nebula but the memory chips require 12V from the DC input jack).

To try to avoid this confusion, I’ve added a reminder message that will pop up when you click the Upload DSP button:

2017-08-22

Once you click OK the usual file selector dialog box will open and you can proceed as normal.

This Version of the BN Librarian is 4.04 and, as always, you can download it from the ‘Latest Updates Here’ link at the top of this page.

Blue Nebula Librarian Updated

I’ve just updated the Blue Nebula Librarian app which is now Version 4.03. Apart from a couple of cosmetic improvements the main change is to correct a bug that caused the Librarian to send incorrect values for the P2 ‘flag’ when uploading a DSP program to MEM 2. This flag tells the Blue Nebula whether to display P2 as ‘ABCEF’ or as a numeric value between 0 and 100.

You can download the latest version of Librarian for Windows 32-bit and 64-bit on the Latest Updates Here page – link above in the menu bar. Update: Apple macOS X version is now available 🙂

Librarian Update to 4.01

Reminder: You need to have Java installed on your computer to be able to run the Librarian. If you have the 32-bit version of Java you will only be able to run the 32-bit Librarian even if your OS is 64-bit. If you have a 64-bit Windows Operating System, please check this page for information on which version of Java you should download if you don’t already have it.

Librarian Version 4.01 is an update that fixes a bug in the previous Version 4.00.

The bug prevented the Librarian from correctly interpreting the ‘Heads’ data sent by the Blue Nebula for emulations with numbers between 5 and 15 that use the ‘coded’ ‘A’, ‘B’, ‘C’, ‘E’ and ‘F’ values. It caused the wrong head letter to be received by the Librarian and all head settings became ‘A’ instead of the correct letter value from the Blue Nebula patch. This incorrect value would have been saved in any patch files saved with the Save Patches button in the Librarian. If this patch data was subsequently sent back to the Blue Nebula using the Send All Patches button it will have corrupted the heads value in the Blue Nebula’s patches. You should check and correct the Heads settings in any affected patches and resend them to the Blue Nebula.

The Blue Nebula Firmware 3.02 does not require a fix for this bug, only the Librarian.

The updated software can be downloaded from the Latest Updates Here link above.

Make sure you download the correct version depending on your Windows Operating System: 32-bit or 64-bit. The 32-bit Librarian will work on 64-bit Windows systems but the 64-bit version of Librarian will not work on a 32-bit Windows OS.

The update for Mac OSX will be available as soon as possible.

 

Latest Versions Page Updated

I realized that the version of Firmware 3.30 I posted on the updates page was compiled for a MONO LCD so those who have gone to the expense of fitting an RGB LCD were not getting the benefit so I’ve added a new Version 3.30 compiled for RGB LCDs. You can download all the latest firmware and software by clicking on the ‘Latest Updates Here’ link in the banner above.

The RGB display uses some different screen colours to indicate the different modes that your eTap2HW is operating in. For example:

Setting-MIDI-Channel IMG_7101_7086_edited-1 Advanced-Editing-(pots)

LCD – Common Anode or Common Cathode?

It has come to my attention recently that there are some LCD display modules on sale that are ‘Common Cathode’ types (e.g. this one from SparkFun) , rather than the more common ‘Common Anode’ type (e.g. this one from Adafruit).

Why would you care about this?

Because the two types of display essentially operate with ‘inverted’ logic signals relative to each other, you will probably find that your LCD display is very dark after you upload the ‘wrong’ Automation code. Essentially the ‘common cathode’ type is insisting that white is black and black is white – just like some people we know!

If you’re got an RGB display then all the other colours will not appear as intended either and they won’t match what’s stated in the User Guide.

As a result I’m now providing two versions of the Automation code on the Updates page so make sure you use the correct one for your LCD type.

If, after uploading, your screen is very dark then try the other version.

A handy feature I’ve added to the code (thanks to Eric Thacker for prompting me to implement it), the unit now ‘remembers’ the last preset or user patch that you used and starts up with this when it’s next switched on, rather than always defaulting to Preset 0: Apache. This is actually very convenient if there is a favourite patch you use a lot 🙂

Automation Firmware 3.21

This is a minor improvement to the Automation firmware (software) for the Arduino in your EchoTapper. Taking up a useful suggestion from my Finnish friend Rolf Holmberg, I have changed the number range displayed for the Mix, Program and Feedback knobs, when editing a patch in either the Basic Editor or Advanced Editor modes..

Previously the values were displayed using a range of 0-255 but now the values are shown in a 0-100 range. This should make it a little easier to ‘translate’ from a patch setting to a knob position on a non-automated eTap2HW and vice versa. For example if someone says “I set Feedback to 3.5 for that tune” you can use a value of 35 when setting up a similar patch.

Firmware Version 3.21