monokinetic

Aha :) but terminate what? The DIN/DOUT chain? If so then can you point me towards where this is described, I don't see it anywhere on ucapps.de.... is this a new thing? My DIN/DOUT chain has been working as is for over 3 years now.

Err I'm not sure if I understand? Arnold?

Hi all, While preparing to finish my upgrade to MBSEQv4 I have found a strange problem on my Core32 board. Currently I have my SDCard working, LCDs working, external power ready. But when I hooked up my DIN/DOUT boards they seem to not be working correctly. I got the same behaviour with or without a customised HWConfig file on my SDCard. After lots of following cables and making sure I have the SC/RC/SI/SO lines connected correctly, I tried checking the Core32 J8/J9 connector to make sure R31 (the 4x220 Ohm SIL resistor) is working correctly. I found that something was very odd, I could measure 30k resistance between VS and SC/RC/SI/SO! I removed the SIL resistor and found I have no resistance on the SC/RC/SI/SO lines. I tested the SIL resistor now that I have removed it and it seems fine i.e. 220 Ohms from the dotted pin to each other pin. Before I install a new 220 Ohm SIL resistor, I would like to ask if it would be worth trying the connection to my DIN/DOUT boards without the 220 Ohm SIL resistor installed? Or should I just install the new one and see what happens with that one? Thanks in advance for any help. David

TK I would also be interested in a CV record function. If this was combined with an AOUT things could get very interesting. I can imagine recording control voltages from a softpot for example could be lots of fun, especially if the CV could be quantised :) From what you were imagining, would it be possible to record the CV as both a CC type track and a note track (maybe not the right term but i hope you know what I mean!). I think both would be useful, but the second option would obviously require a gate in to the core32. Also I imagine we would have to put some overvoltage etc protection on whatever pin was used as the CV in if we wanted to interface to modular synth CVs. I'm sure you know how to do such a thing, but if anyone is interested the sequencer schematic here has a good example of protecting a microprocessor from too high/negative voltages. http://www.acoupel.com/sequencer/schemas/ACS%20Sequencer%20schema.pdf (Im adding one of these to my modular, lots of fun as well!) David

wow TK, you are unstoppable :) Well I for one am very interested in the OSC as I'm a Kyma user. Just have to finish that darn Ethernet board and I will start bugging you with support requests :D

Wow that was quick! Well my understanding was that we could use this to test OSC going from the MBSeq to iPad. I don't see how OSCulator would be involved here? The problem for me is that I still have not finished soldering my Ethernet for the MbSeq so I can't test it on the hardware. Hopefully during the week I can get it done. Anyone else got an iPad + Ethernet enabled MbSeq apart from TK? :) David

Damn, it is a shame that you are having problems with the iOS version, this would be a killer app for me. I have tried pinging my iPad and I get similar average times to you. This seems strange though, I have been using OSCemote and TouchOSC to send OSC to trigger Kyma and I have not had any noticeable datatransfer problems, even when sending a large amount of data (ten fingers with X,Y position and other TUIO stuff) I haven't noticed any timing issues. I realise this is just sending data one way, but a quick Google shows iPads doing similar sequencer editors for Ableton and SuperCollider. Also I could mention that my initial problems with iPad and OSC were solved by updating my Asus wirless router to the latest firmware.... Just brainstorming here, but would it be worth trying a purely OSC based solution to see if the iPad is up to the job? I could quite easily create a TouchOSC layout with the required buttons, that might at least identify if it is a problem with the iPad hardware / Juce software. Other than that I'm not sure what else could be worth trying.... David

Hiya nILS, Ok cool thanks! David

Hi, I just finished my AC sensorizer. I will be using it with some pressure sensors mounted on a glove under my finger tips :) I'm not sure if the 2.5 m cable going from the MIDI box running AC Sensorizer to my glove with sensors should be shielded or not? The cable is carrying 5v, ground + 4 outputs from the sensors back to the Midibox. If you think shielded is best, then do I connect both ends? I have a feeling that you usually just ground one end of shielding, but I'm not sure what's best in this case.... Thanks in advance David

Hi tk, Ok thanks for the clarification. I had a feeling that would be the situation, I guess I will have to put my name down anyway and wait patiently on the front panel group buy, then I can have 2 MBSeqs ;) David

Wow, it looks great! I have an old MB Seq panel (from the V3 template posted on ucapps) which is 19 inch. Would it be possible to use this case, and have the extra length of the 19 inch case as rack ears? Or does the whole front panel have to sit inside the case? David

PCBs landed safely in Prague last week, thanks Seppo!

I'm a big fan of puredyne, I gave up with Planet CCRMA after I came across it. I have used it a portable OS and also installed to a partition. However, I must confess I haven't ever used it for any of my Midibox stuff, my Mac does that :) Puredyne is a really stable distro and is focussed on media artists type thangs (Processing, PureData etc). I would recommend doing a bit of digging through the mailing list archives to make sure your audio hardware will be compatible with it first though (I got caught out with a Firewire interface last year, seemed that USB was the way to go...). HTH David

I am slowly finishing my first panel of analogue modular synth and my next panel will have a Midibox CORE8 running the SID V2 firmware + AOUT CV board. There is no need for the physical SID chip, PCB etc, you just use a CORE8 and AOUT of your choice but you get access to the SID engine to send to your CV gear. If you read through the SID V2 manual there is a good explanation of the AOUT modulation capabilities. If I understand it correctly (i.e. I haven't actually tested it yet) then you can send all of the amazing synth engine stuff from SID V2 to CV outs. That means you get envelopes, wave sequencer and LFOs. The other possibility would be to use the Analogue toolbox available from the MIOS download page, that has some envelope and LFO to CV stuff. But personally I'm going the SID route, it looks much more interesting :) David ps obviously once nILS finishes his MIOS32 version then these options may increase further.

Hiya Seppo, Invoice received, checked and paid. Time to start watching the postbox! Thanks for running this, the boards will be most appreciated... David

Hi TK, Just to throw my 2 Euro cents in for this part of MBSeq - My main idea with the MIDI file import is to load in simple MIDI files generated with Recycle. Just in case you don't know Recycle, the related MIDI files represent slices of a looped sample (samples being played by a hardware sampler in my case). The MIDI files are monophonic and usually consist of 8- cca. 50 notes, one after another. My dream is to have these imported into a Seq track and then be able to play around with Recycled beats :) not sure if this is doable with Seq4 yet, I am using my Core32 board for other things than MBSeqv4 at the moment.... David

Seppoman, After a quick search I have not found a schematic for this board, correct me if I'm wrong :) So I will ask instead: Would this PCB also be suitable for putting into a modular system? If yes, then I presume it is ok running on +/-15V? David

Wow, this one almost passed me by! Nice work man, I had a very quick look through it and it looks very interesting. Guess I need to ask SmashTV if there are still plans to offer these boards? David

Of course. Gave it a quick try this evening, just on one computer but it seems to have the same behaviour as MSD v1.0 i.e. not recognised usb device, core resetting. Ah well, to be honest I would rather our time goes towards something that makes noise rather than an SD Card reader :) Cheers David

Hi Thorsten, What a funny coincidence, this afternoon I was just thinking, what I would need is a way to test this on MBSeqV4 firmware and a few hours later I found your post!!! I will more than happily try it..... I uploaded MBSeqV4 beta 16 and the result of entering sdcard in MIOS Studio V2 is this: [46078.002] SD Card Informations [46078.002] ==================== [46078.002] -------------------- [46078.002] CID: [46078.002] - ManufacturerID: [46078.002] - OEM AppliID: [46078.002] - ProdName: SD128 [46078.002] - ProdRev: 0 [46078.002] - ProdSN: 0x00004661 [46078.002] - Reserved1: 41 [46078.002] - ManufactDate: 82 [46078.002] - msd_CRC: 0x38 [46078.002] - Reserved2: 1 [46078.002] -------------------- [46078.003] -------------------- [46078.003] - CSDStruct: 0 [46078.003] - SysSpecVersion: 0 [46078.003] - Reserved1: 0 [46078.003] - TAAC: 127 [46078.003] - NSAC: 0 [46078.003] - MaxBusClkFrec: 50 [46078.003] - CardComdClasses: 437 [46078.003] - RdBlockLen: 9 [46078.003] - PartBlockRead: 1 [46078.003] - WrBlockMisalign: 0 [46078.004] - RdBlockMisalign: 0 [46078.004] - DSRImpl: 0 [46078.004] - Reserved2: 0 [46078.004] - DeviceSize: 1943 [46078.004] - MaxRdCurrentVDDMin: 5 [46078.004] - MaxRdCurrentVDDMax: 6 [46078.004] - MaxWrCurrentVDDMin: 5 [46078.005] - MaxWrCurrentVDDMax: 6 [46078.005] - DeviceSizeMul: 6 [46078.012] 0 root dir entries, data area commences at sector #2069. [46078.012] 123873 clusters (253691904 bytes) in data area, filesystem IDd as FAT32 [46078.013] Content of root directory: [46078.013] - MIOS [46078.013] Found 1 directory entries. [46078.013] -------------------- [46078.013] [46078.013] Checking SD Card at application layer [46078.014] ===================================== [46078.014] Deriving SD Card informations - please wait! [46079.464] SD Card: 'NO NAME ': 253 of 253 MB free [46079.464] File MBSEQ_B1.V4: doesn't exist [46079.465] File MBSEQ_B2.V4: doesn't exist [46079.465] File MBSEQ_B3.V4: doesn't exist [46079.465] File MBSEQ_B4.V4: doesn't exist [46079.465] File MBSEQ_B5.V4: doesn't exist [46079.465] File MBSEQ_B6.V4: doesn't exist [46079.465] File MBSEQ_B7.V4: doesn't exist [46079.465] File MBSEQ_B8.V4: doesn't exist [46079.465] File MBSEQ_M.V4: doesn't exist [46079.466] File MBSEQ_S.V4: doesn't exist [46079.466] File MBSEQ_G.V4: doesn't exist [46079.466] File MBSEQ_C.V4: doesn't exist [46079.466] File MBSEQ_HW.V4: doesn't exist or hasn't been re-loaded [46079.466] done. Wow, what a really helpful tool! These are exciting times in the world of Midibox, thanks for all your hard work everyone involved in the new MIOS studio! (Now we just need to get it working over IP and we could do remote assistance of people's hardware over the net :thumbsup: ) Anyway, I get no power reset type behaviour when plugging in the SD Card when running the new MBSeqV4 beta 16 i.e. the status LED stays on. So I guess that means the Core32 is reading the SD card fine and the problem is with the USB MSD firmware? If I can be of any assistance with finding out why the USB MSD firmware is not working, please let me know :) Otherwise consider this case closed. Kind Regards David

Hi TK, Thanks for the speedy reply. I would say this is exactly what is happening. For sure it is 3.3v. I originally had R30, but I removed it after rechecking the MBSEQ interconnection PDF and making my first post :) I have double checked a few times, there is no short to be measured between those 4 lines, when the SD card adapter is plugged in or not. The only thing I have found with a good poking around with my multimeter on j16 is that between VSS and VCC there is a resistance which seems to constantly shift around. This is regardless of the SD card adapter being plugged in or not. I guess this is ok? So I'm a bit stuck now :sad: Any other ideas, or should I try to make another SD adapter? Best Regards David Edited for smilies!

Hi, As I have to wait to recable my LCDs in my MBSEQ till the weekend, I thought I would test my newly soldered MBSD cable and MB_CORE_32 using the USB Mass Storage device app available in MIOS32 downloads. I have used the ultra low cost MBSD route i.e. a Mini SD adapter with the cables soldered then putting a Micro SD card into the adapter. When I plug in my Mini SD card, I get all the right signs from Windows XP SP2, an STM Mass storage device is found. But it seems that as Windows trys to create the removable device something goes wrong. The Removable device starts to appear in My Computer, then disappears. This appearing/disappearing goes round continuously but the device is never actually available (this creates a great glitchy sound of Windows alert playing all over the place, cool but not what I want!). I've tried this on 4 different machines today, Windows XP and Vista plus Macbook and Ubuntu desktop. The Windows machines at least try to recognise the SD card, Mac OS and Ubuntu see nothing. I always connect direct to a USB port, that is I have no hubs etc involved. I've been over my Mini SD adapter and checked continuity, all fine. I've triple checked the schematic and I'm 99 percent sure that's fine (admit to being human though!). I have measured 3.3v on the SD card when hooked up to the CORE_32, fine. I've tried 3 different Micro SD cards, a SanDisk and two no names. Always the same behaviour :( The only thing which seems a bit strange is that the status LED starts to flash once I plug in the SD card. Is it supposed to do that? Or is that a sign that the USB power can't handle powering up the SD card? Other than that, does anyone have any suggestion why this may be happening? Thanks in advance David

[i'm not 100 percent sure this applies to the MBSID forum or somewhere else, mods please move as appropriate.] Hi, I have been reading through the SID source code because I want to compile for quite a specific setup. I do not plan to use any SID modules (I'll leave the SID's for the rest of you!) or slave cores, my core + aout would be on the All in one AOUT PCB which I got in the group buy. I plan to have a minimal control surface and most importantly the analogue ins because I want to use the SID engine to control some modular synth oscillators and so on, as well as process modular signals via the 5 analogue ins. I will be putting some over/negative volatge protection on the J5 pins. I plan on using a PIC18F4620 as the source code mentions in my specific hardware setup (i.e. no slaves, no SIDs) it is still ok. I am pretty used to compiling my own MIOS apps, so I'm trying to customise the SID source to my hardware. I realised that by default SID V2 is setup to use pins on J6 for the AOUT SCLK etc connections, whereas the All in one PCB is routed to use the default MBCV pinning i.e. J10. I checked in SIDV2 main.inc and found where the AOUT pinning is overridden. Is it ok to try and revert this setting back to the default J10 or is this going to cause me problems running the SIDV2 app? If so, do I need to explicitly set the pins (as seen in )? Or can I just comment out the part in SIDV2 main.inc that overrides the AOUT pinning? Thanks in advance David

Hi, it is nice of you to come back to us :) Thanks for fixing the links in the Wiki page, I checked them and they work. I have not got much time at the moment as well, too much to do for University. But once I get some etching time again I will let you know..... David