Another semi-success story

[Big Dummy]

I've got a semi-working pushpin.

Made In China C/CGB-JPN-2

R1 and R2 are 1k

R3 is 330

Didn't use the buffer

Getting same issue when any channel outside of 1-4 (+ offset) is sent.

Tested with FL Studio 6 thru Tascam US-224 and also MIDI equipped bass
guitar thru Roland GR-30.

Notes:
The results with FL Studio were kinda bleh: arpeggios won't work
(plays 1st note then clicks) and I can't get cc's working right. I
don't have my MIDINES on hand so I can't test to see if the issue is
with my pushpin interface or not. I'll get on that in the next few
days. Now that I think of it, I had a similar issue with cc's while
messing around with the windows version of piggytracker and MIDINES.
Hmmm. Oh and pitch bend worked.

The tracking with the bass and GR-30 is pretty nice. The only problem
is that the GR-30 only shoots out certain cc's so I can't really do a
complete test. However, when I step on the "WAH" footswitch, the unit
sends information out on cc#1 but this noticeably affected the
waveform of channel 3, the note length of channel 2 and channel 1 went
unchanged.

I'm gonna keep messing around and report back in the next few days so
if there's anything specific you want me to try out, let me know!

[Big Dummy]

OK, I can verify that no cc's are working. Any suggestions?

[Patrick Leonard]

The CC's should work right out of the box. Make sure that you are
sending the right CC's on the tight channels. Are you sending them
from the computer or another midi device.

[Big Dummy]

I tried both a PC and a korg padKontrol.

Um, when you say "tight channels" you mean 1-4 or the offset
equivalent? If so, yep. I tried sending them on 1 then 2 and so on.

Could the fact that I'm using alternate resistor values be the
problem? I'll try to get my hands on the correct ones.

On Apr 8, 2:51 pm, "Patrick Leonard" <dreamt...@gmail.com> wrote:
> The CC's should work right out of the box. Make sure that you are
> sending the right CC's on the tight channels. Are you sending them
> from the computer or another midi device.
>

[Alden]

tight channels = typo of "right channels"
as in, "are you sure you are sending cc's on the correct channel?"

[Big Dummy]

I tried sending cc's 0-4 on channel 1 with no luck. I also tried some
other cc's on other channels.

One thing that is of some interest is that when I sent some note data
outside of the channel 1-4 range, not only did I get the note hang and
garbled sound issue but also it some of the parameters changed like
the pulse envelopes and the texture of the wave channel.

On Apr 8, 7:58 pm, Alden <n3l...@gmail.com> wrote:
> tight channels = typo of "right channels"
> as in, "are you sure you are sending cc's on the correct channel?"
>

[Patrick Leonard]

this is what has been happening. I think that the code isn't
filtering out the other channels totally. I haven't had a chance yet
to take a look at it.

[Big Dummy]

OK, got it. My handle is "Big Dummy" for a reason. I missed this
important note:

IMPORTANT NOTE

The Range value below is just to show what the dynamics of the
hardware can handle. You should *always* send full-bit MIDI CC ranges
(0-127) -- the SMM automatically puts your value in range to the
hardware. For example, to set the Sound1 wave duty at 75%, we could
send a CC#3 of anything over 95. To set it at 12.5%, we send a CC#3 at
anything under 32. Accordingly, the 0-1 values (such as sound on-off)
are turned 'on' by any controller value over 63.

Now we're in business!

On Apr 9, 2:12 am, "Patrick Leonard" <dreamt...@gmail.com> wrote:
> this is what has been happening. I think that the code isn't
> filtering out the other channels totally. I haven't had a chance yet
> to take a look at it.
>

[Brian Whitman]

yeah, pretty confusing wording on my part. Glad you got it going.

Can anyone who has successfully built an interface post a schematic, parts list and detailed instructions? It would really be helpful to have that on the site.

--
http://variogr.am/