| There are several editing tools posted at the Yahoo fcb1010 group. I'm confused - why are there so many? Which one should I use? |
Yes, there are several out there. The key difference between Ripwerx and other popular tools is that it's a Java application - this means it will run on PCs, Macs, Linux boxes, whatever. Ripwerx is also different in that, as of Version 2.0, it is compatible only with UnO-equipped FCB1010s.
|
| Will this application work with my FCB1010, that is, my unit's firmware version? |
| FCB1010 Firmware Version |
Ripwerx-compatable? |
Notes |
| Official Behringer Firmware - any version |
No |
Ripwerx (as of version 2.0) now supports only UnO 1.0.2 |
| Gordius Little Giant replacement firmware |
No |
Your FCB1010 is now slave to the LG. Use the Little Giant Control Center. |
| Unofficial UnO v1.0.0 |
No |
|
| Unofficial UnO v1.0.1 |
No |
|
| Unofficial UnO v1.0.2 |
Yes |
☺ |
|
| Why does Ripwerx no longer support units having original Behringer firmware? |
Continued maintenance and testing of conditional logic required for Ripwerx to 'adapt' to users' firware would simply take too much time and effort. Therefore, if supporting only one family of firmware, it's logical to support the 'best' firmware. Other editors are available for original, non-UnO units for both PC and Mac.
Now, for some personal opinions - from a not-so-impartial UnO advocate: An editing tool often comes into play when an FCB1010 user's setup becomes so eleborate that hand-programming (the 'Riverdance') is too tedious. Frankly, if you have an elaborate setup and use an editing tool then an UnO upgrade seems to be a no-brainer. Face it, you are a power-user, so, get an UnO chip and get more utility from your FCB1010. Check out http://groups.yahoo.com/group/fcb1010_UnO/. |
| The GettingStarted page indicates I need Java J2SE Runtime Environment 5.0 (1.5.0) or higher. How do I check Java my version? |
Open a command-line window and execute...
java -version
or
java -fullversion
Refer to your system documentation for opening a command line window.
|
| Which MIDI interfaces will work with Ripwerx? |
Ripwerx is intended to be device-independant. Core Java functions are used for MIDI I/O in an attempt to guarantee universal interoperability. However, problems have been reported with the following devices:
| Digidesign Digi002 |
 |
| Behringer BCF2000/BCR2000 |
 |
| SoundBlaster !Live |
 |
| Midisport UNO (1 in, 1out) |
 |
Generally, these devices work OK during a Version Check. However, exchanging the FCB1010's presets and global settings requires a much more lengthy message than the version check - some MIDI interface units cannot handle large messages (> 2000 Bytes). Get more information from a database at the UnO Yahoo group.
Ripwerx includes a "Loop Test" feature. This loop test uses a large Sysex message - larger than the FCB1010's. This test should validate your MIDI interface's ability to support Ripwerx.
|
| I just downloaded and unzipped the application. This .jar file does not look like a program - it has the general "file" icon. Does this mean it won't run? |
No. This file will execute as long as your computer has a JRE (see GettingStarted.html, System Requirements). You may wish to create a shortcut to the file and then you may change the shortcut's icon. Refer to your system documentation for creating shortcuts and changing icons. Here is a sample Windows icon and source images.
Some computers have an "association" for .jar files. If this is the case, executing the file may result in a 'browse' window displaying the file's contents instead of running the application. Refer back to GettingStarted.html for special instructions to start the Ripwerx application. |
I tried to launch the application for the first time and received the following error message:
 |
It is likely your computer has and old version of Java's JRE. Refer back to GettingStarted.html and take another look at System Requirements. |
| I just loaded a message into the editor for the first time. I only see PRG CHG 1. Where are PRG CHG 2 - 5? |
Certain functions are hidden from view (or perhaps disabled) by default. To customize the editing view, see Setting Preset View Options in the User Guide. |
| After using the application, a file appeared on my system (FCB1010EdPref.prop). What is this? |
This is a "properties" file containing your application preferences, see Application Preferences in the User Guide. |
| After using the application, a file appeared on my system (tmpFcb1010Report.htm). What is this? |
This is a "report" file generated as the result of using the Show Report feature. You may delete this file at will. |
| After using the application, a file appeared on my system (LoopTestRecv.syx). What is this? |
This file was generated as the result of using the Loop Test feature. You may delete this file at will. |
| After using the application, a file appeared on my system (LoopTestSent.syx). What is this? |
This file was generated as the result of using the Loop Test feature. You may delete this file at will. |
| I use a Mac. Why do I need "Plum Stone" or "Mandolane"? |
With respect to Java runtime components, Apple "rolls ether own". For Windows and other platforms, the Java team (Sun) provides the runtime environment. When it came to MIDI, apparently Apple had a working MIDI implementation before Sun. Later, Sun's implementation matured, however it differed from Apple's. The end result is that Apple's MIDI implementation is "custom". This means that cross-platform MIDI applications won't work completely on a Mac. Plumstone is an add-in which allows Ripwerx (or any other cross-platform Java application using MIDI I/O) to function correctly.
It would have been possible to create Ripwerx in such a way as not to require plumstone, but, then it would not function correctly on other platforms. Cross-platform useability is a prime goal for the Ripwerx project and is the only reason for using Java technology.
Another resource is also available: http://www.humatic.de/htools/mmj.htm. |
|
|
| I use an Intel-Mac and this application is too slow to be used. |
Very sorry about this. There is no immediate solution. Here are some dissapointing suggestions:
- Run Windows on your Mac
- Go back to using original Behringer fimware. You can then use iFCB
|
| My question has not been answered here and the User Guide isn't helping either. What should I do? |
You are welcome to contact the author, Mike Riley the-bug@att.net for questions pertaining to this application.
For questions about the UnO-equipped FCB1010 or its capabilities, refer to http://launch.groups.yahoo.com/group/fcb1010_uno/.
For questions about an original FCB1010 or its capabilities, refer to http://groups.yahoo.com/group/fcb1010/. This group has a huge pool of knowledgeable FCB1010 users.
|