33

(12 replies, posted in Nintendo Handhelds)

idk what options there are in software.
But my other suggestion is to swap In and Out on one end of your cable. You know how Rx goes to Tx and vice versa.

34

(12 replies, posted in Nintendo Handhelds)

Have you tried connecting the ground pin? It is the third pin that is shaded in on the link port drawing, but not labelled.
Connect that to the center pin of your midi cable.

35

(6 replies, posted in Nintendo Consoles)

Make your own. Looks like you can get cheap USB DIY receptacles like this:
https://www.hawkusa.com/manufacturers/p … pwQAvD_BwE

and then salvage the cable from a used GBC/MGB charger.
Try to use a wall charger rather than a computer port to charge it though. Computers will introduce noise.

36

(89 replies, posted in Sega)

Keep up the good work!

37

(2 replies, posted in Nintendo Handhelds)

Sounds more nes to me, but that could be virtually anything...

38

(15 replies, posted in Nintendo Handhelds)

Those are line-level audio outputs. The small one is for connecting a stereo 3.5mm (1/8in) TRS and the second is for connecting a 6.65mm (1/4in) TRS. The familiar "name" of those jacks is pro-sound.
If you have no idea what you are buying, start with a non-modified gameboy. In fact, why don't you just get the LSDj licence and use an emulator on your computer.

39

(15 replies, posted in Nintendo Handhelds)

yes

40

(15 replies, posted in Nintendo Handhelds)

Excellent. Here is a list of CC values for mgb if you want to get started adding them to the N&V code:
https://github.com/trash80/mGB

41

(15 replies, posted in Nintendo Handhelds)

Ok, since that one has DIN MIDI, I suggest making a separate midi controller with a secondary Arduino. You can make it far more interesting than just 8 keys. In fact, you can break out every mGB cc control to a knob as well as your keys. AND you can use an example code to start with! All you do is fill in the blanks. Besides, isn't an octave 12 keys...? I think the currently available TeensyBoyPro only has 8 extra GPIO and man, 8 keys would be so boring.

Watch part 1 and 2, then get back with us if you like the idea.
https://www.youtube.com/watch?v=DXhxdsGREsU

42

(15 replies, posted in Nintendo Handhelds)

Well, given an Arduinoboy made with an Atmega168 has 9 remaining GPIO, it would be feasible to add 8 buttons.
To add these into code though, we'll need to know exactly what you want to do with them and which mode you'll be using on the arduinoboy.

EDIT: Also, what arduinoyboy will you be soldering these buttons to? I only assumed it was running on an Atmega168.

That does seem scary. Do you have another gambeoy to test the cart on?
Graphical glitches first make me think VRAM, but the glitches are incorrect sprites, not corrupted data. And besides, the VRAM has to be perfect or else the ROM won't boot. (the logo is loaded into vram, then read back to check)
So maybe there is a problem with the cart or cart RAM. I would be worried for your songs too. Can you find someone who can back up your SRAM to PC for you? What cart do you have?

44

(3 replies, posted in General Discussion)

I look forward to hearing from PJRC on what they have to say as far as arduino IDE integration. I have to assume that the Teensy 2.x, LC, 3.x and 4 can support MIDI 2.0 over USB. It is more likely than other authors will create MIDI2.0 function libraries first but it has to be coming.

45

(3 replies, posted in General Discussion)

I assume that for unidirectional MIDI messages, 2.0 supports DIN5.
MIDI 2.0 is backwards compatible in that the devices perform a handshake and agree on what functions are supported, defaulting to 1.0 functions in the case of no response from the slave. MIDI can be streamed over DIN5, USB and TRS connections commercially as we well know. So I have to assume that yes, MIDI 2.0 bitstreams can be sent over DIN5, granted the MIDI slave can respond and confirm the supported capabilities.

A more detailed explanation of the handshake is that the MIDI master sends a capability request in MIDI 1.0, then waits for the response. If the slave device supports MIDI 2.0, then it can return the MIDI 1.0 message. For MIDI 1.0 devices, there is nothing to be excited or worried about. MIDI 2.0's highest priorities is backwards compatibility. One of the few MIDI 2.0 devices available (or soon to be) is the Roland A-88MKII MIDI Keyboard Controller. It supports MIDI 2.0 over the USB-C on the back, but also has DIN5 IN and OUT jacks. So I have to assume that if MIDI 2.0 is supported over DIN5, then both the master and slave need MIDI IN and OUT connected.

46

(3 replies, posted in General Discussion)

Bidirectional
Backwards Compatible
256 MIDI Channels
32 bits of resolution
more+

What are you most excited about?

Thanks Oliver. Would you suggest a voltage divider to bring it down to Line level?

What steps in this mod are you hoping to take? Are you just adding a wire between the VIN pin and an RCA jack? Even though the audio isn't going thru the CPU, it is still going to have the same ground floor and DC offset associated with the VIN pin.
I think what you want to do is cut the VIN pin at the cart connector and solder a wire to an AC coupling capacitor, then to your RCA jack. There should be some improvement since he audio doesn't go thu the CPU and the noisy amp IC, but it will probably be subtle at best.