Jump to content

Rio

Members
  • Posts

    712
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by Rio

  1. Rio

    CEM3378 schematic

    @sasha and seppoman: nothing of your posts answered my questions! So please discuss only about relevant information in this thread. i know also there is a AOUT_NG in development, but i got at home 2 AOUT_LC. I don't want to throw them away and i'm interessted in a MBSIDV2 + AOUT_LC solution too! And i don't know yet, whether and how a MBSIDV2 will support seperated CEM3378 with AOUT_NG? Maybe if there is no way to use AOUT_LC i've to change to AOUT_NG.
  2. Rio

    CEM3378 schematic

    Hi Thorsten, thanks for that huge information. Ok, everything is now a bit more clearly. You mean trimpots for filter and resonance? Do you adjust Gain or Balance on CEM3378 in any way? If i understand it right, every SID Audio Output Channel should be Filtered through 1 CEM3378 seperatly to keep it stereo. So i connect SID Output only at CH.A and CH.B wouldn't be used, because CEM 3378 provides at least only 1 Output? or i'm wrong? If every CEM3378 needs 1 AOUT_LC, how can i connect 2 AOUT_LC on 1 CORE Module to have a stereo effect for CEM3378 on a MBSID2? Does MBSID2-Application supports 2 AOUT_LCs to use them together with 2 SID on 1 Core? Best Greets, Rio
  3. Hello, if i understand it right: TK will take a look about SEQ Remotefunctions too in future, if he have time... Greets Rio.
  4. Rio

    CEM3378 schematic

    first i'll build up now a PSU for that, like in description of TK's AOUT_LC (bipolar) +12V -12V and i'll get -5V with a 7905 too. So that the power supply should be allready. But i still need a info about necessary parts for that schematic for a right connection from AOUT_LC to CEM3378. I found that:http://www.synthtech.com/cem/c3378pdf.pdf So i'll ask my questions more detailed now: 1. Which OPAmp should be choosen in that schematic ? (Did someone has written down a complete partlist e.g. Shopping basket at Reichelt) I think i will first begin with 2x CEM3378. 2. Should CV#1 and CV#2 from AOUT_LC connected to CH.A and CH.B INPUT? 3. Should Freq, Resonanz, Gain, Balance controlled by Potentiometer or can MBSID handle this? 4. Does every CEM3378 needs an own AOUT_LC. Are 2x AOUT_LC + CEM3378 needed, to get start for Stereo-Filtering? Greets, Rio. PS: Please discuss build up's for SSM2044 further in a new thread.
  5. Rio

    CEM3378 schematic

    thx for info, but i've got 4x CEM3378.. so i needed detailed informations to use them with AOUT_LC ;) Greets Rio.
  6. hi ris8_allo_zen0, Jambonbill used that keyboard as little sequencer: http://www.midibox.org/dokuwiki/doku.php?id=midiboxkb_-_using_a_c64_keyboard_as_input (scroll down to the bottom) he has developed the C64 Keyboard connection to Core. At time i build up another project yet: "K64". It's finished to 95%. It can be used to controll a Speakjet (together with K-II) but also works as MIDI Controller with the external MIDI-OUT Port. The "K64" isn't a Sequenzer! but it's more a controller. There are two boards in it: 1.Core for C64 scan matrix (code from bill) and application code for midicontroller and midi keyboard functions, for TextToSpeech or Synthoptions etc... 2.Core for K-II Yes i want to add a Recording function for SEQV3, but at time the Remote support of SEQV3, registered every incoming "remotekey" as recorded note.. so it's at time not possible, to activate Record Mode and step through Tracks of SEQV3. I'm waiting til TK have time to check the current source code of SEQV3. so that remotekeys will not recorded. Another little problem is that every remotekey will be routed through other device - that should be deactivated too.. That are some little things they need to changed before i can try add this.. I've to document the project if i'm finished.. I hope i get it everything under $7FFF ;)
  7. 1.Is there any CEM3378 schematic/connection diagramm for use with AOUT_LC, yet? I only found this: http://www.midibox.org/forum/index.php?topic=5538.0 I want control CEM3378's (max.4) with my upgraded MBSID2 in future. 2.Does every CEM3378 needs an own AOUT_LC (i have 2 AOUT_LCs yet)? 3.Does i need an external supply for the CEM3378? I've readen that +12V and -5V are needed for CEM3378 (Are they available from Reichelt or Conrad?) 4.What are the parts i need additional? EDIT: I changed my questions in more detail in further posts below Best Greets, Rio
  8. i believe the R4 is the only one, which works correct..
  9. and yes, there are differences in 6581 too... which revision is yours?
  10. a little annotation: 6581 can not double or triple filtering. That means that the 8580 can used for AND-Command between channels. The missing function is a bug by developing 6581 chip. The correct solution is included in 8580. Another thing: Have someone ever tried to play Triangle + Saw or Pulse + Triangle, Pulse + Saw or all together ($31, $51, $61, $71) on C64 I with 6581 chip in it. It's sound very quiet, low and nasal.... that was corrected in 8580.
  11. That Cloning feature sounds interessting... Great! I'll check it out next time, if i've build up the MBNET connection. Ooh.. I don't find any description about connection of the second SID Board on J14 in ChangeLog. Best Regards, Rio.
  12. Only for comprehension: 1.if i wanna update my old 4xSID for a new stereo MBSIDV2 i can remove 2 of my 4 Coreboards out of that box and connect each second SID board on J14, right? 2.MIDI-Connection: i have to connect MIDI LINK like in description of changelog? 3.CAN-BUS: i have to connect D0, D1, D2, D3 of LCD to VSS? Is this LCD correct working without D0-D3 connection from Core? Is there really only 1 single line for CanBUS (so i have to connect D2+1N4148 and D3 together on 1 line)?
  13. So the difference between the 32K und 64K is the available address range: $7FFF and $FFFF. If understand it right: best should be to proof 2 specific values in $0000 and $0001 and if them are wrong the whole range should be initilise maybe with $00 and then the specific values should be written to $0000 and $0001 again. But why i have to proof 2 values... because one could be randomly the same before on that adress? Best Greets, Rio.
  14. 1. Are there some things that i've to mention if i want to implement an bankstick support (readpage/writepage) for 32k and 64k type. What is the difference for programming? I've only a 32k EEPROM for testing... 2. Is the read and save code for 32K usable for 64k EEPROMs too? 3. Are they formated automatically by MIOS if they are never used before and then connected? 4. How can i format them in C?
  15. kein problem... nö hab mich nur am SEQ Anzeige orientiert :) ;D ok, hast recht, das sollte man dann nochmal überlegen.. oder man macht das so, dass die Note an diesem der Step richtig wieder gelöscht wird (für korrektur beim record oder step-weisen einspielen ohne das man extra in den Edit-Modus oder in die UtitlityPage wechseln muss) Beste Grüße, Rio.
  16. Rio

    Seq V3.2

    hi, scheint doch so, dass ich ähnliche Probleme mit der Version 3.2 habe. nach erneutem Upload sind zwar die beschriebenen Routervalues #55 weg (siehe engl. Thread), aber nach einem neustart werden die Werte auf 0 zurückgesetzt. Dann viel mir auf, dass der SEQ auf CC 111 reagiert und dadurch alles mögliche in den Settings verstellt... ??? EDIT: Sorry ich mein CC 112 bei geöffneten Router @tk: wie du ja meintest ist das eventuell auf einen korrupten Flashspeicher zurückzuführen - ich werde ebenfalls mal einen Auszug machen und dir die tage zusenden. Grüße Rio.
  17. Hallo Thorsten, ich hab mich gestern mit der Remoteansteuerung beschäftigt. Funktioniert fein. Was mir dabei augefallen ist, dass die Beschreibung in mbseqv3_remote_functions.txt in versetzter Oktave dokumentiert war. die Belegung beginnen bei 1.Oktave: Key | Hex# | Function =====+======+========================================================== C-1 | 0x24 | GP Button #1 C#1 | 0x25 | Track 1 D-1 | 0x26 | GP Button #2 D#1 | 0x27 | Track 2 usw... ich hab das mal im Anhang geändert. Jedoch gibt es ein Problem bei der Remotefunktion bzgl. der Recordfunktionen: 1. Nämlich dass im Recordmenü alle externen MIDI Signale als Remote auch als Noten behandelt und in die Sequenz erfasst werden. Das macht sich schlecht, wenn ich die Recordmenü-Funktionen auch über meinen externen Controller nutzen möchte. Es wäre günstig, sobald die Aktivierungstaste: C-6 NOTE-ON (0x60) vom SEQ erfasst wird, diese und alle folgenden Remotekeys im Recordmenü bis einschließlich C-6 NOTE-OFF nicht als Notenaufnahmen behandelt werden. Also ich mein damit, alles was einschließlich und innerhalb der gedrückten Aktivierungs-RemoteKey passiert, soll vom SEQ Recorder ignoriert werden. Auch der Router sollte die RemoteKeys nicht auf dem Midi-Kanal durchschleifen. Das sollte meineserachtens beides durch ein Flags im Code prüfbar sein. 2. Ist eine Änderung der SelectButton-Routine im Recordmenü möglich? Zurzeit ist sie für das Wechseln der Menüpunkte im Menu hinterlegt. Macht IMHO nicht viel Sinn, da ich die Menüpunkte ja explizit auswählen kann und das wesentlich schneller geht. Für eine praktische Arbeit wäre es sinnvoll, dass man über diese SelectRoutine die Note, wo sich der Step befindet, aktivieren oder deaktivieren kann. Im Recordmodus ist es ja sonst nicht möglich (z.B. für schnelle Korrekturen) die aktuelle Notenposition ein- oder auszustellen. Ich hoffe ich hab mich nicht zu kompliziert ausgedrückt und eventuell können die 2 Features technisch nicht all zu aufwändig umgesetzt werden. Die Funktionalität würde dagegen enorm gesteigert werden.. Beste Grüße, Rio. mbseqv3_remote_functions.txt mbseqv3_remote_functions.txt
  18. sorry TK, i found the problem out.. It must be an upload error or something else. i've uploaded the whole application again and now all works fine. Pattern A1 is then set to C-3...C-3...C-3...C-3 Router works fine... Greets, Rio.
  19. it's for both IN-Ports. no, but my old settings / tracks wasn't overwritten on EEPROM after uploading... upload-versions before were clearing the A1 bank everytime. That this A1 isn't cleared in 3.2 upload is an advantage... but maybe this is the reason for that problem... i don't know. I'll format all EEPROMs and check it out. i don't know... what should i do? if there is shown a #55 then i don't know which channel is choosen for dest-channel in router... that would be a disadvantage. In future i'll build up the IIC1 MIDI-IN. At time i work with only Int.MIDI IN-Port. Cool, i wish all best for further support... I'm really pleased about that SEQ Project all in all... Great work..! I'll format the EEPROMs and post you the result.. Greets, Rio.
  20. After uploading from 3.1 to 3.2, SEQ3.2 application shows me a value: #55 for Dest-Channel for all Ports in Router.. (maybe it's a value 255). Only if i rotate it up then channel #16 will be shown and i can scroll down to #1. But everytime i switched the SEQ on & opened the router menu, that "55" is shown again. Everything works fine in 3.1 before.
  21. thx, i'll check it out.
  22. ohh.. i send it by my own application as MIDI-IN Device.. at 176. Only SRC->All or SRC->None works for routing CCs to another external device from SEQ (i use MBSEQv3.1 at time) in Router. if i set up other SRC Channels, CC will be blocked. How do you mean this? i thought i send it independent through 176. Best Greets, Rio.
  23. I've checked out that CC will only be sended if the Router is set up to Channel->ALL, so i can't filter any MIDI Source-channels without disabling all CC messages (thats is a bit inconvenient) It is possible to get the CCs for every SRC-Channel in Router too?
  24. ach...immer geduldig bleiben.. ;D Grüße Rio.
×
×
  • Create New...