Jump to content

lukas412

Programmer
  • Posts

    269
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by lukas412

  1. Totally understand. I'm just honestly curious. I was left feeling quite the same way when I finished mine, but now that I have had it and used it for a month I'm really liking it. Simply for the sound quality alone it's worth it in my opinion. I have been using mine as an external effect from ableton. The real time mode has been the most fun for me so far.

    Luke

  2. I've built one of these up and I have to say it's an amazing project. I love it. So crispy and crunchy. I plan to add one of Seppo's 2044 setups to it. I've run it through the one I have on my MB6582 and it sound beautiful. It has an effect mode that lets it just process incoming audio in real time. Really fun stuff and a very easy build.

    Luke

  3. Maybe your PS is sagging under load?

    I had one that would sometimes work, sometime not.

    When you measure it directly (under no load) it'll show 5v+ ?

    But when you measure it while plugged into your 6582 it's showing less?

    The psu seems to always show +5v, that's the weird part. Even when the base pcb is showing +2v, the pins of the psu are showing +5v. So I think something is going bad on the base pcb, but I'm not sure. I have a desktop power supply that I'm going to try to see if its the psu before I do anything to the MB. Another weird thing is that once it starts, it never flakes out on me. Works just fine. It's only an issue when first starting the synth. Think it could be a bad cap or something maybe?

    I agree, sounds like the brick is sagging under load. You could try removing SIDs and see if the problem happens less often, that would prove it's a current load problem.

    I tried removing all pics and sids except on core one and I got the same kinda behavior as far as I could tell. But I will certainly try that again. What makes it kinda tricky to debug is that once I've been using it for a while the problem seems to go away. I will try using my bench supply to eliminate that as a possibility.

    Then just put the same MIDI In/Out circuit as you'd find on a Core PCB - i.e. the optocoupler and 220 Ohm resistors... these could fit behind whatever MIDI sockets you use, so you only need 5V/TX/RX/Gnd connected to the 4th PIC.

    This is great news, I was originally hoping I could just use the included midi io but wasn't sure I would be able to since there are no pins for it on the pcb. I will give this a shot over the weekend.

    btw are you connecting the MB-6582 to AOUT_NG via the expansion port? Maybe there are spare pins for this extra MIDI channel... female 5-pin DIN plugs are easily available.

    Yes it is, and this is exactly what I had hope to be able to do. I am currently working building an additional enclosure that has the same width and height dimension as the pt10 case but thinner and not slanted so I can sit the MB6582 on top of it and just connect it via the expansion port.

    but it's probably best to only use PIC18F4685 in that socket since there's a diode bridging pins which are used for LCD output in other PIC types.

    The application that I wrote for the ESX is currently running on a 4685, so this should work out perfectly. I'll give a shot and let you all know how it goes. I'm sure I'll run into something I'll need help with.

    Thanks,

    Luke

  4. I finished my MB6582 just about a year ago and have been using it off and on since, I've always liked the synth. I have finally gotten around to getting an aout_ng and an ssm2044 board put together. I am just completely floored by how amazing this setup is. I have owned and had access to many synths over the years and this is right there at the very top of the list in my opinion. The only thing I have ever heard that was as ballsy as this setup is a mini. It's increadibly warm and organic, it never tires my ears out. Before I just liked the synth, now I am fully in love.

    I just wanted to say thanks again to TK, Wilba, Seppoman, and everyone else who has helped me and contributed to this project. You guys should be very very proud.

    So now for a question. Somewhat recently I have been running into a problem. When I first turn on the synth often times it doesn't start. The power led will light up, but not fully, its dim. Some times it will eventually turn itself on, but more often if I leave the power switch turned on and unplug the psu and replug it in to the power jack on the synth once or twice it will start up. I have taken some measurements when the power is on and the led is dim. I am only getting about 2v at any of the 5v pins on the base pcb. A lot of the time the synth will actually start up as a result of me taking a measurement. Once the pic boots up the readings are normal everywhere a nice solid 5v. Usually after I have been using the synth for a while it will turn off and on normally.

    My first thoughts are that the psu is bad. Its an original c64 psu that supplies 9v and 5v. This could very well be the problem, but when I take a measurement from the pins on the power jack I'm getting around 5v usually a little higher, but still only getting around 2v on any of the 5v pins. I've looked for shorts and re-flowed most of the solder joints, that's not to say I didn't miss something. Any suggestions on what I should replace first or where I should look?

    Second question. I would like to use one of the cores on the base pcb to run a different application some of the time. I have an app that does some midi processing for my ESX, and it would be cool if I could use one of the cores to do this when I don't need it as a SID engine. So can I just upload the hex to the core I want to use? I know there is only one optocuplor and one set of midi io, would it be possible to use an IIC module to get a set of midi io to one of the slave cores and still have the main midi io for the other 3 cores?

    Thanks again,

    Luke

  5. Below are the parts that I ordered from Mouser. I built my GM5 last night and it works like a charm. Though these parts should probably be verified, they do for sure work.

    Luke

    
    GM5 USB Module		Mouser Part#		Quantitiy
    Reistors		
    4.7k			291-4.7k-RC		1
    1k			291-1k-RC			3
    220			291-220-RC		4
    27			291-27-RC			2
    
    Capacitors		
    100nF Ceramic		594-K104M15X7RF53H5	2
    1000nF (1uF) Ceramic	810-FK28Y5V1C105Z		1
    22pF Ceramic Cap		21RD722-RC		2
    10uF Polarised Cap		647-UVR1V100MDD1TA		1
    
    Diodes		
    1N4148			78-1N4148			1
    
    Mechanical		
    USB Socket B-Type		534-924			1
    MIDI sockets 		161-0505			2
    
    ICs		
    Crystal 16 MHz  		73-XT49U1600-20		1
    Optocoupler 6N138 		512-6N138			1
    Serial EEPROM 24C04	698-CAT24C04LI-G		1
    
    IC Sockets		
    IC-Socket 		571-1-390261-2		1
    
    
    

  6. Quick update on this. I have gotten this to work quite well. I was able to reduce 8 note on messages to set a row of 8 LEDs to 1 note on message. I will soon release the c code and a small max patch that does the transform. I was going to use NRPNs for this, but that would only reduce the messages being sent from 8 to 4 rather than 8 to 1. Its setup so you can easily choose the type of midi message you would like to use.

    It works by rearranging the bits in a 3 byte midi message. This allows you to take the low bits from the 2nd and 3rd bytes to get the full 8 bit value to set all 8 LED's at once. That leaves the high bits from the 2nd and 3rd byte to set the command type and the row or col number. It's pretty simple and allows for more command types if needed. Comments appreciated! Thanks to everyone that gave advice and TK for the great platform!

    Thanks,

    Luke

    Here is the mapping using note on.

    midi note on message

    9n 7F 7F

    12 34 56

    1: Command Type

    2: Midi Channel

    3: Command

    4: Arg1

    5: Arg2

    6: Arg3

    Command Types

    9: Monome Command

            x: More command types can be added here.

    Commands that emulate the monome commands

    0: LED

    1: ROW

    2: COL

    3: CLEAR

    4: MODE

    ---------------------------

    Command Definitions

    ---------------------------

    LED

    9n 0F 7F

    12 34 56

    1: 9 Matrix Command

    2: Channel

    3: 0 LED

    4: Arg1 Row

    5: Arg2 Value

    6: Arg3 Col

    ---------------------------

    ROW

    9n 1F 7F

    12 34 56

    1: 9 Matrix Command

    2: Channel

    3: 1 ROW

    4: Arg1 High bit

    5: Arg2 Row

    6: Arg3 Low bit

    ---------------------------

    COL

    9n 2F 7F

    12 34 56

    1: 9 Matrix Command

    2: Channel

    3: 1 COL

    4: Arg1 High Bit

    5: Arg2 Col

    6: Arg3 Low Bit

    ---------------------------

    CLEAR

    9n 3F 7F

    12 34 56

    1: 9 Matrix Command

    2: Channel

    3: 3 CLEAR

    4: Arg1 Off/On 0/1

    5: Arg2 0

    6: Arg3 0

    ---------------------------

    MODE

    9n 4F 7F

    12 34 56

    1: 9 Matrix Command

    2: Channel

    3: 3 MODE

    4: Arg1 0

    5: Arg2 0-All On 1-All Off

    6: Arg3 0

  7. 2. When running a (bassline- or drum-) sequence on any other core than core 1 the matrix-leds of the row and column corresponding to the sequences light up all the time. i can't see the sequence running like on the first core. What could that be?

    Not sure about the first problem, but number 2 is just how it works. Leds only trail on the first core.

    Luke

×
×
  • Create New...