philetaylor

I have found this which looks interesting http://www.circuitcellar.com/archives/viewable/Birsan207/index.html If I get a spare few hours (days?) I may have a play with this...... Cheers Phil

That could be interesting, have you seen espeak? http://espeak.sourceforge.net/ Cheers Phil

Hi. I remember playing around with the SP0256 20 (odd) years ago! It was find but pretty basic. There is a MIDIbox project that has similar (but much improved) functionality based around the SpeakJet IC.Take a look at http://ucapps.de/mbh...c_speakjet.html for more information and http://www.midibox.o...idibox_speakjet Cheers Phil

While it would (I suppose) be overkill, if you wanted to use the newer STM32 based CORE32 rather than the CORE8, you could use Jonathan Farmer's dpot (Digital Potentiometer) driver. Digital Potentiometers work in a similar way to their analogue counterparts but are controlled by an SPI interface rather than fingers :) The code is available here and currently supports the MCP41xxx series of dpot IC's. You would probably need a simple op-amp as well as you don't want to feed the audio straight through the dpot. Obviously no PCB's or indeed software (other than MIOS32 and the dpot driver) exist to achieve this so it is something that you would need to create yourself. I know that Lyle has suggested the MB-Mixer and this is another great solution to the problem with the added benefit that the software has already been written !!! If you are looking at a DIY solution as a way to save money against a commercial one then I think that you will be disappointed, unless you find a 'kit' that already does exactly what you want, you will probably end up spending more than €198. What DIY gives you is the warm fuzzy feeling that you created it yourself :) Cheers Phil

Got mine in the UK today !!!!! Cheers Phil

Hi. No you "checkout" the SVN which effectively copies the whole source tree to your local machine. You can then run SVN update to download just the changed files. SVN is simply a way of synchronizing your machine with the master repository. Cheers Phil

Hi. I know it is a bit hidden but on that page under "SVN Repository" it has a link to the page about SVN which contains full instructions for downloading/installing TortoiseSVN. It also has instructions for setting up Putty/Pageant if you are going to be writing back to the repository (although you will need to post your SSH public key in the public key section first!) http://www.midibox.org/dokuwiki/windows_toolchain_svn Cheers Phil

Hi Julien Instructions are on page 12 of this thread, look at post Cheers Phil

Many of us here spend a lot of our time helping beginners (we were all beginners once) but you must understand that many people join this community with big ideas of building a DIY MIDI controller with tons of faders and lots of buttons and encoders and ask us how to do it so the standard response until the "newbie" shows at least some commitment on their part by reading www.ucapps.de and wiki.midibox.org tends to be to read as much as they can on those sites and then come back with specific questions. What you are talking about doesn't sound like it can be achieved using any of the 'standard' midibox projects apart from possibly MIDIboxmixer in which case it is probably going to require a reasonable skill in electronics and C/assembly programming. I would suggest that you try building one of the standard projects listed under MBHP projects on www.ucapps.de first. Take a note of what modules are required (CORE, AIN etc etc) and then visit http://www.avishowtech.com and order the kits for the modules and build them. Sorry but I don't know of a basic intro to electronics website as there were no websites when I was studying electronics at college :) Cheers Phil

Are you sure that you haven't enabled an "echo" feature on midi-ox, I can't run it at the moment to check...... If you don't get the problem with any other program I wouldn't worry about it :) Cheers Phil

If this is just happening in midi-ox then I suggest that midi-ox is echoing received midi data back. One way to test this is when it happens, disconnect the MIDI Out from midi-ox. It has been a while since I last used midi-ox so this may be complete rubbish :) Cheers Phil

Try Juce 1.50 (as that is the recommended version). Juce seems to change prototypes between versions so it is likely that the definition for TableHeaderComponent has changed! Cheers Phil

Hi. I would take a look at the MIDIboxMixer project: http://www.midibox.o...id=midiboxmixer This is the only MIDIbox project that handles audio (other than the MIDIbox SID/FM synths) so may give you some idea. It is basically a MIDI controllable analogue mixer. I have no idea what the current status is so it may not be practical for your application :) Cheers Phil

If you update your SVN repository, you should see a new build directory for VS2010 which will hopefully work for you! Cheers Phil

Hi. I haven't build the latest SVN for Windows for a while (I usually only build it when TK wants to release a new version). Those errors are all in the latest additions and usually just require specific casting of the variables as GCC is a bit more tolerant than VC++ I will try and build it tomorrow and update SVN. Cheers Phil

Juce must be extracted parallel to the mios32 directory. /trunk /mios32 /juce Cheers Phil

Hi. SVN won't like that URL as it is the web interface to SVN not the repository itself. There are 2 svn repositories, MIOS and MIOS32. MIOS Studio 2 is located within the MIOS32 repository so: "svn co svn://svnmios.midibox.org/mios32" should work. Cheers Phil

Yes I already reached the same conclusion :( There are other boards available that allow the LCD to use SPI but it looks like for some reason the manufacturer left that off, probably because the SPI for the SD card is also shared with the Touchscreen controller...... It doesn't even look like the other configuration pins are available anywhere on the board to force SPI mode. The other problem is that because of the shortage of I/O on the CORE32, J15 goes via the 74HC595 so reading registers/memory 'from' the LCD is also out of the question which does limit certain things, for example I was hoping to be able to use the LCD controllers buffer memory to save having a screen buffer on the STM32. The downside with this is that anything above 2-3 bit colour is pretty much out of the question. I haven't quite got the display connected yet (hopefully this weekend) ! Cheers Phil

Hi. Not sure about the second problem but they may both be related. I guess that you are using the latest CodeSourcery toolchain? There seem to have been various changes which cause the memory overflow error. Either use an older (2009) version of their toolchain or download the MIDIbox one. Instructions are =mios32&s[]=toolchain]here Cheers Phil

Usually where audio is concerned, yes. You would find that your SID's have an added whistle or buzz when compared to ones powered with a linear supply. There are audio grade switch-mode supplies but they tend to be much more expensive due to the complexity required to reduce the amount of noise that they generate. Cheers Phil EDIT: Damn nILS beat me to it!

LCD's have arrived today, bit busy so I won't be able to do anything tonight with them. They have an SDCard slot on the back which is quite interesting..... Cheers Phil

That looks fine, from re-reading the datasheet I am more convinced that this is the problem :) Cheers Phil

Not sure about in the US but this is what I bought from Farnell in the UK: http://uk.farnell.com/jsp/search/productdetail.jsp?CMP=i-ddd7-00001003&sku=1023035 Cheers Phil

That should be 'fairly' easy to fix....... With the DOG CLCD's, unlike usual CLCD layouts where line 2 is at offset 0x40, each line sometimes runs consecutively so 0x00=line1, 0x10=line2 etc. If this is the case with your display then you would need to change MIOS_LCD_YAddressSet to 0x10 (instead of the default 0x40). This is set in seq_lcd.inc so a quick 'hack' would be to change the line in SEQ_LCD_SetPageOffsets from "movlw 0x40" to "movlw 0x10". I have never used the 2 line version so I'm not sure if this will work but it is worth a try :) Cheers Phil EDIT: Alternatively, you may need to alter the initialization in the dog lcd driver/module as per: http://www.lcd-module.com/eng/pdf/doma/dog-me.pdf

The only difference between the DOG CLCD and the standard CLCD driver is the initialization sequence, I would imagine that the MB808 is expecting to talk to a standard CLCD and not a DOG. This explains why it works if the LCD has already been initialized by the DOG driver. If you have recompiled the app with the DOG driver as the custom LCD driver (modules/app_lcd/dog). You then need to either specifically select the custom LCD in your app or change the PIC ID to 0000-0000-0000-7000 to select the custom LCD driver. Cheers Phil