Jump to content

Rio

Members
 View Profile  See their activity

  • Posts

    712

  • Joined

  • Last visited

  • Days Won

    9

 Content Type 

Posts posted by Rio

  2. [B] Curtis CEM3387

    in Fleamarket

    Posted · Edited by Rio

    Are you looking for CEM 3387 or CEM 3378? Both differ in certain functionality. 

    Yes, it is rare, but not impossible to get. Wait and watch on ebay or second hand sellers, etc. the price should be double (or even higher) what it was 20 years ago. e.g. the cem3378 were rare even then.

    I got mine (3378) around ~2006 for 20 euros each. But those were already the last in stock. 

    Greetings,

    rio

  3. Midiphy seq V4+ Remote control improovement

    in MIDIbox SEQ

    Posted · Edited by Rio

    Do you have experience in programming? The reason I ask is because it requires that. And your approach of changing the args of a core function is definitely not the right way.

    Btw: I think this is pretty custom for your needs, since the mute works in a different way in the midi implementation (regarding tracks).

    Otherwise, if you absolutely need it and above all if you are confident that you can do it, then you can hack the seqv4 source and define and include your own external control as a CC and specify & transmit the channel there as a value, which is used in your own loop through the tracks and mutes or unmutes the corresponding tracks if (value == track's channel).

    e.g.

    seq_midi_in.h -->
      

    #define SEQ_MIDI_IN_EXT_CTRL_MUTE_BY_CHANNEL 16

#define SEQ_MIDI_IN_EXT_CTRL_NUM_IX_CC     17

    <-- (make sure to increase the NUM_IX_CC)

     

    seq_midi_in.c --> 

    seq_midi_in_ext_ctrl_asg[SEQ_MIDI_IN_EXT_CTRL_MUTE_BY_CHANNEL] = 122; // your cc for that control


      

    const char* ext_ctrl_str[SEQ_MIDI_IN_EXT_CTRL_NUM] = {

..

"Mute by channel", // your name for that control

}

    <-- (index 16 must be noted here)

     

    append your external control handling inside:

    static s32 SEQ_MIDI_IN_Receive_ExtCtrlCC(u8 cc, u8 value) 

    if (cc == seq_midi_in_ext_ctrl_asg[SEQ_MIDI_IN_EXT_CTRL_MUTE_BY_CHANNEL]) { ... }

     

    but i think if you want to change something in the code, you have to get familiar with the structure of the entire source anyway.

     

    Greetings,rio

  6. midiphy SEQ v4+

    in MIDIbox SEQ

    Posted · Edited by Rio

    this fix refers to the following issue (midibox seq v4 release feedback):

    The quantized recording loses its sustain (GLD) due to the offset of the next step, since the note of the step to be played is not passed and the recording loses the (note/sustain) information in the next step.

     

    seq_core.c:

    1. replace this line:

    https://github.com/midibox/mios32/blob/master/apps/sequencers/midibox_seq_v4/core/seq_core.c#L1053

    with:

      
    	    if (SEQ_RECORD_NewStep(track, prev_step, t->step, bpm_tick))
                mute_this_step = 1;

    mute or not to mute? thats the question!

     

    seq_record.c:

    2. insert this code: 

      if (t->state.REC_DONT_OVERWRITE_NEXT_STEP) {
    int next_step = new_step + 1; // tmp. variable used for u8 -> u32 conversion to handle 256 steps properly
    if( next_step > tcc->length )
      next_step = tcc->loop;

    new_step = next_step;
  }

    before:

    https://github.com/midibox/mios32/blob/master/apps/sequencers/midibox_seq_v4/core/seq_record.c#L727

     

    3. replace this line:

    https://github.com/midibox/mios32/blob/master/apps/sequencers/midibox_seq_v4/core/seq_record.c#L735

    with: 

    if( any_note_played ) {

    which also passes flagged REC_DONT_OVERWRITE_NEXT_STEP.

     

    4. replace this line:

    https://github.com/midibox/mios32/blob/master/apps/sequencers/midibox_seq_v4/core/seq_record.c#L843

    with: 

    return any_note_played; // no error

    instead of no error code, but it is enough that it is returned positive.

     

    Note: It is more of a hack than a concrete fix (it only works for tracks that are played forward), but for my purposes it works - if you actually like to use the quantization feature for live recording.

    But your desire to get an "undelayed, unquantized recording" has nothing to do with this solution.

    This hack is suitable for a working quantization during live recording of tracks that already contain & process midi data. Maybe quantization can give better results when recording notes, except that it does not conflict anymore with existing (already recorded) data in my modification.

     

  7. midiphy SEQ v4+

    in MIDIbox SEQ

    Posted · Edited by Rio

    Hello steve,

    Is it possible for you to make your own binary from the sources? I have written a fix for quantized live recording in the past...  you could try the code changes/snippets which it affects. Let me know if you would like to try it out.

    Oh, you mean a possibility of an exact "unquantised recording". Of course, my suggestion doesn't fit there. 

    greetings,

    rio

  10. Help...Ive Screwed up my Midibox Seq V4

    in MIDIbox SEQ

    Posted · Edited by Rio

    Quote

    5. This finally showed up the bootloaders details vrsion, board etc in theLEFT hand box below the input dropdown..

    fine

    Quote

     

    13. I powered off the midibox once completed and changed to powering it via the wall plug rather than my laptop  and lo

    my new session (named "apple") was now the active session upon startup and it SOULD be read to / saved to etc.

     

    If you end up uploading the Midibox SEQ app via midi, you should be able to manage sessions from the midibox options menu. You do not need to make sessions via the terminal - but it is possible.

    If you have the feeling that something in your 'old' session is stored incorrectly or is corrupt, then you can also try to load this session and copy certain things (patterns etc.) into your new (cleanly created) session - all this directly on the unit. And maybe in future just make a backup of the SD more often. no corrupt files have happened to me in all that time, but I always make chronological backups on the PC.

    Quote

    12. I then created a brang new Session via the MIOS terminal ..this took quite an unexpected long while....all the time I had two progress bars on the screen of my midi box, it may have taken around five minutes to complete...I just let it run

    That's tooo long! So my suggestion: please test a new SD Card <= 4GB! I also had problems in the past with SD cards of different types.

    Maybe my old thread helps out (but note, I use a LPC17 core - but the conclusion is to use a smaller SD card, which I have already mentioned):

    Perhaps as a tip for the future: I can't say anything about the hardware problems, but you should also check all the connections to the SD card - in case you soldered together your own SD card board (or the previous owner). Otherwise, test another SD card).

     

  11. Help...Ive Screwed up my Midibox Seq V4

    in MIDIbox SEQ

    Posted · Edited by Rio

    5 hours ago, phillwilson said:

    it may also be worth adding that my SD card contains all the following files... these are currently not accessible from within the midibox itself, but i cen eject the micro sd card. put it in my reader on the laptop and ge the following files.

    Screenshot (13).png

    You should backup these files as long as they can be read on the PC.

  14. Help...Ive Screwed up my Midibox Seq V4

    in MIDIbox SEQ

    Posted · Edited by Rio

    On 3/6/2022 at 2:52 AM, phillwilson said:

    What I WANTED to do  was update my firmware within MIOS Studio ( I had done this before so I thougth I knew what i was doing...however, it not looks like I have uploaded the latest BOOTLOADER rather than the firmware update that I THOUGHT i was doing... now my whole MIDIBOX seems ot be stuck on a screen that reads Bootloader is up-to-date! ;-)  and LCD#2.1 READY.

    This is a standard message when the bootloader/mios32 is on. It is good that it is running. After that, you can safely upload the MBSEQ, but for the right core! - which is not quite clear here yet (probably STM32 core).. but MIOS Studio should already give you the info back with the USB midi connection.

     

    more infos here:

    http://www.ucapps.de/mios32_bootstrap_newbies.html

    and here:

    http://www.ucapps.de/index.html?page=mios32_bootstrap_newbies.html

    Mios Studio 2:

    http://www.ucapps.de/index.html?page=mios32_bootstrap_newbies.html

  17. LPCXpresso ide

    in MIDIbox NG

    Posted · Edited by Rio

    On 8/11/2021 at 9:52 AM, Number 6 said:

    Hi Guys,

    It's been a while, I've had health issues, spent time in hospital and so on, but I'm back, just trying the same thing again, I did manage to find a short cable but not thick, same result, also tried to lower the speed, same result.

    Could someone provide a link to buy a cable that works for you on amazon?

    Otherwise, could I ship my unit to someone who could try to flash it for me(I'm in France BTW)?

    Thx!!!

    Hi,

    there might be something wrong with your board. I tried it several times with my different 1769 board revisions - a,b, d - all with success. 
    So you can check your board for bad solder points and/or the debugger/link interconnection.. maybe you missed something.

  18. Replacement for PIC18F4685 on sammichSID

    in MIDIbox SID

    Posted · Edited by Rio

    On 1/12/2022 at 6:47 PM, ###OCT### said:

    I have recently revisited my old sammichSID, the PIC is caput.

     

    how can it break? as long as you haven't trotted up, it should still work.. probably the mios firmware/app on that device is corrupted, isn't it? as long as the bootloader is still there, which is in a protected area, you can fix it. And yes, you can not take a PIC18f4620 - different features, different storage area.

  19. Possible mods for Seq4/4+ accessibility?

    in MIDIbox SEQ

    Posted · Edited by Rio

    Hi,

    you could create a simple program, also with a PIC core board with the help of a bare skeleton available here on ucapps. the k2 speakjet project is a good example for a serial communication (max232), but for your needs IIC would be more comfortable (as long as it is supported by your speakboard). you may get faster results with an Arduino board too.

    With all this knowledge you can surely also hack the SEQ for your needs, but that takes quite a lot of time to understand everything that is already there.
     

    you could still allow a control via midi on your own board too.

    greetings

  25. SID "Clones" List/Sources/Experiences

    in MIDIbox SID

    Posted · Edited by Rio

     

    On 4/23/2021 at 6:19 PM, dwestbury said:

    To the best of my knowledge, the only relevant analog aspect of the SID is its filter.

    BTW: Is the armsid filter section purely emulated or analog? and are the filters just as sensitive as the original (regarding electrical damage)?

×
×
  • Create New...