Jump to content

dj3nk

Members
  • Posts

    758
  • Joined

  • Last visited

    Never

Posts posted by dj3nk

  1. kann ich auch die jetzigen pics zum testen aller leds und buttons nutzen?

    Leider nicht, da die SID V2 gar nich auf den 18f452 passt. U.A. wegen des höheren Speicherbedarfs wurde dann auf den grösseren 18f4685 gewechselt.

  2. Könnte man den Topic endlich mal umbenennen ? Ich weiss nicht was diese ganze diskussion noch mit dem usb-pic modul zu tun hat? Ich meine es gibt genug newbs die sich den kopf zerbrechen müssen weil man manche sachen so durcheinander bringt. Klar wir die schon länger hier sind verstehen das, aber denkt auch mal an andere. Wie soll man denn die ForumsSuche schön und sauber benutzen unter solchen Umständen ?

  3. Good idea, but I think its better just to add motorfader (aout) function to the mb mixer application. I don't think a "merge" of the projects is so easily possible.

    With aouts you could even add more real controls like eqs to your mixer. Midifying analog gear is an actual discussion here. Go and look at the wiki. There are some hints about the possibilities. But this wasnt worker out deeper by anyone as far as I know.

    greetz

  4. thank for your explanation !!

    I want to replace the 14 encoders with analog pots. As far as you explained, I understand everything. My only problem is that I dont know if it is possible to access a value of an encoder directly. So that I turn a pot and the right value in the chosen layer (!) is changed.

    ...or...

    can I just change one CERTAIN parameter? That way I would have to manage these layer functions in my controller and not in my sid. But that would be a lot more to do I suppose. :/

    If everything works fine we could melt our projects to one ?!

  5. nice to hear that you solved this. I'll have to check that MBLink and perhaps MBNet stuff for my purposes too soon.

    Can MBNET access and change the actual values of the encoders in the chosen layer? Or can it only handle a parameter "inside the sidapp", meaning I cant access parameters "of the control surface"? (sry for that bad english ;D)

    I  havent read into that stuff very deeply yet, but it were nice to know if you could give me a good starting point for that.

    greetz

  6. Da der Thread jetzt doch komplett gehijackt wurde wäre es denke ich für den Urheber des Threades (und für zukünftige ForenSuchAktionen) nett, wenn man die GM5 Abteilung in nem gesonderten Topic verschiebt ?!

    greetz

  7. The only really reason is that I want to build my SID with analog controls and one MidiIN/Out in one case (without USB). So that it looks and runs like the original just with pots. And I want to leave and use the midi connectors on my SID, so I am not limitated to leave the SID running over a usb port.

    The switch would work, but I don't like switches ;) I do more like solutions without "workarounds" if it is possible somehow.

    The costs wouldnt matter since I have some core and 74hc00's lying around here.

  8. In addition i have to tell the exact meaning of my previous post. The "no sysex forwarding" function should only filter the incoming messages from mbStudio. So it would be possible to add a mb64 (or anything else) before the mbSid and record this events in the host sequencer via the midimerger. No need for doing anything then. You wont get a feedback loop when updating the firmware and all events from other devices are passing through the merger.

    Perfect for adding real analog controls to the SID :D not yet

    greetz

    EDIT: I've added a small sketch. outdated

    Problem: When the recorded events are played from the Host they get through the merger again, what means that sended events are received again by the host (=> loop possibility)

    EDIT2: I've added another sketch

    Due to the above written problems I searched for a new solution. As this seemly doesnt need any modification on the firmware this could be the last post on this prob in this topic.

    The yellow rectangles are showing 2 areas where we need to merge 2 signals into 1. The MidiMerger of the SID is turned off in this case. So there's my probably last question ... is it possible to add a 2nd MidiIN to the SID with an IIC module or do I need to build a seperate Core with the merger software?

    EDIT3: Perhaps it's the easiest way to integrate a MBrouter with 2 iic's into the case.

    mergingold.JPG

    mergernew.JPG

×
×
  • Create New...