philetaylor

It is an environment variable problem! Firstly for CORE32, you use MIOS32_PATH not MIOS_PATH and secondly, it depends which version of make you are using. If you are using the make that comes with MSYS then you must use /DRIVE/DIRECTORY if using the modified one that comes with MINGW, you just use /DIRECTORY. There are various variables that must be set: For the MSYS version of make, use: For the modified MiNGW version use: Cheers Phil

As the person that first asked julianf if he could make me one of Wilba's MB-SEQ front panels, I can attest to the quality of his workmanship. I would also like to add that I find 12mm standoffs epoxied into 2mm deep blinds to be a very satisfactory method of fixing the PCB. I haven't 'stress' tested it but I wouldn't be surprised if they were at least as strong, if not stronger than threaded blinds as there is much more surface area to aid adhesion. Cheers Phil

I am guessing that you always had the warnings but the compiler didn't bother to tell you before :) One of the recent changes that TK has made is add -Wall to the global CFLAGS (in $MIOS32_PATH/include/makefile/common.mk) This causes GCC to enable ALL warnings (including signed/unsigned mismatch) which makes debugging easier especially as a signed char can only store a 7 bit value (positive or negative) whereas unsigned is 8 bit positive only and the difference can lead to all sorts of problems !!! Cheers Phil

"read the wiki n00b!" Sorry I couldn't resist..... Anyway, in answer to your questions, yes encoders require 2 DIN inputs (up and down). Switched encoders need 3. Therefore I make it that you need 77 DIN ports (3 DIN modules) The CORE8/CORE32 question is a very difficult one to answer at the moment. If you have no C programming knowledge then you would have much more chance of getting a CORE8 based controller working however if you want to change anything, most CORE8 projects are written in PIC assembler which is MUCH more difficult to learn than C although it is also possible to use C to write programs for the CORE8... There are no actual "released" projects for the CORE32 at the moment although there are beta versions of SEQ/SID and LC, none of which would really help you get a working Traktor controller although the LC is probably the closest.... Unless what you are building has exactly the same hardware spec as an already working project, you are unlikely to get away without doing ANY C or assembler programming. I don't wish to discourage you but we do need to be realistic. If you have NO programming skills then you may struggle a bit... Hold on though, if you can write an autohotkey script then you have some programming skills :) Adding a single motorized fader would potentially be a problem as you would need an MF module (which supports up to 8 faders) and you would probably need to add MF support to whatever project you based your controller on yourself..... Cheers Phil

If you are using Windows, you are best to download the CodeSourcery toolchain. This includes the gnu gcc cross-compiler and newlib which are required for building MIOS32 apps. You are welcome to download the source for binutils/gcc/newlib etc yourself but building a cross-compiler is not a straight-forward task (especially on Windows). TK and I have been working on providing a "MIDIbox" toolchain using the same versions of all tools for Windows/Linux/Mac OS X but this may take some time as the latest version of gcc or newlib compiles larger code than older versions (we aren't really sure which yet). If you just want to compile MIOS32 apps on Windows then the CodeSourcery toolchain is the way to go at the moment but beware, if you are compiling SEQv4 then don't use the latest CodeSourcery release (2010q1) as "nuke" found You are best to download 2008q3 at the moment. Cheers Phil

What version of the CodeSourcery toolchain are you using? It looks like the version you are using is based on gcc 4.4.1 so I suspect it is the latest 2010q1-188 release which uses Newlib 1.17. Over the last few days, TK and I have been "playing" with various gcc/newlib combinations in an attempt to find the perfect combination which works on all platforms. This is taking quite a long time as each change requires a 30 minute rebuild of the toolchain :) It appears that later versions of Newlib are compiling to larger binaries and as SEQv4 almost fills the RAM of the current CORE32, our current thought is that an older version of Newlib may be better as it generates smaller code and most of the enhancements are irrelevant to MIDIbox anyway! If you are "desperate" to recompile, I suggest you try the CodeSourcery 2008q3-66 release which uses Newlb 1.16. It is available here Cheers Phil

Oops I missed that! Well spotted Smash! COM=GND(Black) V_OHM=+(Red) Cheers Phil

The 7805 would probably cope BUT C4 and C5 might go pop ;) To be honest i'm not too sure what the 7805 would do but assuming the OP has his probes the correct way round, I really can't see what else it could be! Cheers Phil

My guess is that you have connected the Bridge rectifier (X1) the wrong way round! Cheers Phil

Hi. Yes it is certainly possible but it isn't currently supported! The easiest thing would be to use one of the USART's (you would lose a MIDI port) but you would need to create a module to do the actual talking to the display. How is your C programming?? Cheers Phil

Here is my mockup of the CS: :) Phil

http://www.ucapps.de/howto_debug_midi.html Cheers Phil

Earlier in the year, I ported the MicroVGA (http://www.microvga.com/) driver to MIOS32 http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fmodules%2Fmicrovga%2F As this also includes a PS/2 keyboard port, I did think that it might be quite nice to adapt SEQv4 to support this. Then you could use a VGA monitor for the display and a standard PC keyboard to operate it. Obviously none of the work has been done to support this but it would be quite nice IMHO... Maybe I will have a play! Cheers Phil

That link will only work for members with specific access to the Programmers Lounge, other users will get an error. hpmk, you have found the solution anyway but if you plan to do some development, i'm sure TK will grant you access to the lounge. Cheers Phil

Here's me thinking I was the only MIDIboxer in leicester :) I will keep an eye on the headphones..... Phil

I am guessing for that price he made the PCB himself. A single-sided PCB is fairly easy to make yourself but you will need the equipment to do it. These will include copper clad board, some sort of etch-resist, and an etchant solution. You can get some quite good results but they won't have that professional look! Cheers Phil

Google is your friend :) NRPN (Non-Registered Parameter Number) http://en.wikipedia.org/wiki/NRPN LSB (Least Significant Bit) http://en.wikipedia.org/wiki/Least_significant_bit Cheers Phil

Hi Attitude, yes I have a Tascam TM-D1000 as well (with the external TDIF to ADAT convertor). I still love that desk but whenever I use it I miss the motorized faders of the 01v96 :) Hawkeye, my personal take is that the Mackie construction started to be a bit "cheaper" with the newer desks. I have no real evidence to back that up, just my opinion! Another digital option is the Behringer DDX3216. It was basically a copy of the 01v and each XLR input includes a TRS insert, they seem to fetch about £300 on Ebay, they received some pretty good reports back in the day, SOS did a review back in 2002 http://www.soundonsound.com/sos/apr02/articles/behringerddx3216.asp Cheers phil

I have used many "small" desks over the years but for a recording or small live situation, I always take my Yamaha O1v96v2 It is small enough to carry with relative ease and with external pre-amps (and a bit of creativity) will support up to 40 inputs! My personal favourite very small desk (because I have had it for many many years) is a Mackie 1402 (again not VLZ). Built like a tank and sounds fine for a small desk. Cheers Phil

That was julianf. He made windows for Wilba's MB Seq front panel but he only made enough for the customers that bought panels IIRC. Cheers Phil

Unfortunately, I have got a BCD2000 and a BCA2000 but not a BCR/BCF.... I may see if I can pick one up on ebay as I am quite interested in playing with this. I note that the clock speed (12Mhz) is quite a bit slower than the CORE32 but other than that it could be quite a useful device, especially with so much RAM etc.... Cheers Phil

I am pretty sure. As MIOS is built for each specific PIC, it knows where each region of memory is. Cheers Phil

It is possible to bridge "anything" if you use enough solder :) It may be a good idea to take some photos of the back of the board and post them here. It is difficult to diagnose without seeing exactly what you are seeing. Cheers Phil

According to sysex_implementation.txt you can use the "X1" command to read pretty much everything from the PIC. The usage and various examples are listed in the above .txt file but the command "F0 00 00 7E 40 00 01 20 00 00 20 F7" will read the contents of the internal EEPROM Cheers Phil EDIT: Fixed link to sysex_implementation.txt

Hi. Yes you are wrong :) Hopefully this will make things clearer. MIOS is just the operating system so you need to upload an application as well. This is also handled by the bootloader. As each part of the MIDIbox software is stored in a particular location on the PIC, I don't think it will work without the bootloader as that is what starts your application (if it doesn't receive a response to it's upload request) Also MIOS Studio gives you a very easy method of uploading software to your MIDIbox and simply needs a MIDI IN and OUT connection to the CORE. Thanks Phil EDIT: In case I wasn't clear enough, the bootloader is NOT optional :)