• Content count

  • Joined

  • Last visited

Community Reputation

46 Excellent

1 Follower

About jjonas

  • Rank
    MIDIbox Tweaker

Profile Information

  • Gender Male
  • Location Turku, Finland
  1. MidiBox SID Sound design tips

    MBSID has an absolutely wonderful randomizer function that can be limited to a subsection of all parameters (as opposed to all-or-nothing randomizing everything, like in certain commercially available synthesizers ;-). I strongly recommend you play around with that and then adjust the resulting sounds according to your taste. You get much better and more interesting results this way than if you started from scratch every time, because at least for myself I've noticed that the "patch from scratch" approach too often leads into dialing in the same old stuff. See 'Randomizer Generator Menu' on this page (bottom of page).  
  2. The FPGASID Project

    There was an update about a month ago about the first production lot. At this statege cost is 74,95€ per chip, i.e. not cheap. Also, the installation into a C64 is strictly speaking not what I'd call "drop in replacement" in the sense that several extra wires are needed to make connections to CPU etc. How that will translate into MB6582 use, I can't say. But anyway probably SEQv4+ will be the main priority for some time still, so we'll just have to wait... Some more audio samples are available.
  3. MIDIbox SEQ V4 Release + Feedback

    As to where there exactly, I think the MBSEQv4 documentation page would be the logical place to put the link to a "MBSEQ v4 Workflow" wiki page. A workflow page doesn't exist there yet, you have to make it. And if you are in the business of making a new wiki page with your workflow info there, I guess it could just as well be a general "MBSEQ v4 Workflow" page; even if has only your workflow there, others can add their later. http://www.midibox.org/dokuwiki/doku.php?id=mididocs:midibox_seq_v4 UPDATE: Oh and about the LCD generator, I remember using something that I think was a perl script to generate them, I think I got it from TK when I was making similar shots for the MBSEQv4 Beginner's Guide a couple of years ago. I can't find it right now though, it's been too long, I don't remember anymore.
  4. MBSEQ V4L Mk.ii record and transpose

    Yeah I saw that one when I searched the V4L thread for answers earlier, that wasn't the issue I'm having. The problem is that I'm not able to switch between record/forward and transpose (I can just have one or the other) without changing the settings on the SD card. If someone has their V4L functioning the way I describe (i.e. record and transpose work with the same settings), I'd be interested in the config file (SESSIONS/DEF_V4L/MBSEQ_C.V4).
  5. Hi, I'm unable to get both keyboard transpose and recording working at the same time. I can make only one or the other work, they won't work with the same settings. I'm using the Mk.ii panel, and have tried this with both LPC1769 and STM32F4 cores with firmware version 092pre1 (the newest available on the MIOS32 download page is 086, the newer one was probably available in some forum post in the V4L thread). What I'm trying to do: record some phrase using step (or live) recording stop recording and use the keyboard to transpose the phrase But I haven't managed to get these working like this. It would make sense it would work like this (first record something, then use the keyboard to transpose it every now and then and jam away over it using another keyboard), but I guess the first question is, is this really the case? Is this how it's supposed to work? What I've managed to do is: either record some sequence, which then plays back. I can play over the sequence if I want, but the sequence will be the same, no keyboard transpose is possible (whether or not Transpose is active or not); or, on the Trigger page, turn on some triggers and hear the C-4 notes play the synth. You can transpose the C-4 based rhythm to the key you play on the keyboard, but you cannot record your own sequences that you could then transpose. The Mk.ii panel wiki page says, If the setting is 0x00, I can transpose with the keyboard but not record (or forward notes played on the keyboard even if I->O is on), and if the setting is 0x01, I can record with the keyboard (and notes get forwarded when I->O is on) but not transpose (even if Transpose is on). Apart from this setting, I have not edited other parameters in any other files. What am I not getting?
  6. Seq V4+ news?

    I've understood it like latigid on says, i.e. SEQV4+ will be compatible with the old Wilba front panel, as well as the "standard" setup (there are firmwares for several variants in the latest zip file). And I think we're already in the SEQV4+ era, because that's what the latest firmware is named (if I recall correctly), even if you use it with a Wilba frontpanel. From that point of view to talk about "SEQV4" and "SEQV4+" as if they were separate things makes sense only if we're talking about old firmware versions.
  7. MBSEQ V4L MkII problems

    Ok, I tried the attached firmware on STM32F4 as well as LPC1769 (also the matrix). They both work! Thanks! :-)
  8. Hi, I'm trying to get my MBSEQv4L mkII working. The MkII page says (at the start) that it is for use with both LPC17 and STM32F4 boards. Has it been certified that it works also on an LPC17? I'm asking because while the MkII board works ok with my STM32F4 (firmware 088), it doesn't work ok with the LPC17 (firmware 086) I have. The firmware 088 available on the MkII page (end of page) is only for STM32F4, while the MIOS32 download page offers firmware only for LPC17, and its version is 086. At first I tried to use the MkII board with a STM32F4. Everything was working except for midi in. Midi out was ok, as well as MIDI in via USB. The MkII page says that if there's problems with midi in, make a change in a session file. I did, but it didn't help. What is the midi in problem that requires changing the default session settings? Anyway, because I couldn't get the midi in working, I tried the MkII board with an LPC17 (firmware 086, the latest one available). However, now the MkII board worked only partly. The cursor LEDs (the red ones) were not lit at any point even though the seq was running, nor could I switch gates on. But it seemed like I could select bar, sequence etc., only that I couldn't switch gates on. Whether that was a problem with just the LEDs (so that a gate gets switched on/off, the LED just doesn't incidate it), or with the buttons as well, I couldn't tell because midi in/out were not working.
  9. MIDIbox SEQ V4 Release + Feedback

    I'm not sure, but if you look at the SEQ's CC implementation chart (found e.g. in the Beginner's Guide, search for "loopback"), only Bus1 is marked with "Loopback". However, the user manual section on the loopback function (search for "the loopback ports") seems to imply that any bus, not just bus1, could be selected for loopback.
  10. MIDIbox SEQ V4 Release + Feedback

    My understanding is that what you'd like to do is not possible at the moment, i.e. there's no way to avoid quantized notes from being cut off. Have a look at this message from some years ago when the matter was discussed previously. Apparently it's fixable in principle, but it's all about TK's time. (A kind of workaround is to set quantize to 0% and play very accurately ;-)  
  11. Midi_IO Troubles

    Not sure at all if it's the same problem, but I might have had something similar a while ago. It had to do with Midi Clock master/slave settings.  
  12. MIDIbox SEQ V4 Release + Feedback

    See section 4.2.1. (Copy, paste, duplicate, quick-export/import) of the Beginner's Guide: One or several tracks can also be quick-exported and imported. Multiple tracks within a single group can be selected with the track selection buttons, or any combination of tracks on the Track Selection page (available only as an F1–F4 button or as a saved bookmarks; see Appendices 1 and 2), and then exported with MENU + COPY. This will copy all data in the track(s), including settings, into the PRESETS folder, i.e. they're not session dependent. This means that you can have a maximum of sixteen tracks exported this way at any given time for all your sessions. The file names are of the form COPYx(.V4T), where x is the relative number of the quick-exported track (1–16). Relative means that if, for example, you have selected tracks G2T2, G2T3 and G2T4 and then quick-export them with MENU + COPY, they will be called COPY1, COPY2 and COPY3, even though their “absolute” track numbers are 6, 7 and 8.
  13. Create new session, press play, seq "hangs"

    Thanks for the info! I've now found out what the problem was. I have a keyboard synth with "local control off" that was controlling a number synths via the MIDI router, including itself. It was set to send and receive MIDI clock. With my "basic setup session" the MIDI clock setting was "Master", so this didn't matter, but in a default new session the setting is "Auto", and the combination locked up the seq. Now I don't send MIDI clock anymore from the controlling synth, and all is well.
  14. Hi, I was using MBSEQ (4.94, 4.95pre10) with my MBSID so that I was using the seq's Track Event menu's function to send a Program Change and Bank Change message at start of the pattern. I have two tracks, the first one to MBSID core1 on channel 1, and the second one to MBSID core2 on channel two. It would seem MBSID gets confused with these "simultaneous" PC and bank select messages, as with my other multitimbral synth (Waldorf Blofeld) there's no comparable problem in the same situation. Here's what happens. If I send a PC and Bank Select message on Ch1 but not on Ch2, Ch1 selects program and bank as expected. If I send a PC and Bank Select message on Ch2 but not on Ch1, Ch2 selects program and bank as expected. If I send one PC and Bank Select message on Ch1 and another one Ch2, Ch1 one selects program and bank as expected, but Ch2 switches as expected only when it's on some other program and bank than the one the message orders it to select; if it's on a different program and bank, the selection works. But if it's on the same program and bank, the program/bank selection is as expected on the screen, but the actual sound is the basic "Lead Patch" (I've tested only on the lead engine). If you now turn the MBSID's main encoder to select the next patch, and then turn it back to select the original one, it is the patch that the PC and bank select message was supposed to select. So somehow the messages select the right patch and bank, but MBSID nevertheless plays a "Lead Patch" (or something that sounds very much like it). So, it would seem that receiving two "simultaneous" PC and Bank Select messages works ok for the first target core, but not for the second. At the moment I cannot test whether it is like this for all cores (2-4) after the first. Can someone else replicate this? JL
  15. Hi, it's been years since I created a new session, as normally I've just loaded a "basic setup" session and saved that under a new name. However, today I was about to do some troubleshooting with SEQv4 and MBSID, and thought to create a new session just to make sure that I have a blank slate. But when I created the new session, I found that even though the session itself is created normally, and you can navigate any menus, add notes to steps etc., when you press play, the seq "hangs" in the first step. You can still navigate normally, add notes to steps, but the seq just won't move forward from the first step. MIOS Studio shows a continuing stream of "fa" messages. If you open another session (one of my old sessions, all of which are copies of a basic session I've created many years ago) and press play, playback works normally. So it's not "real hang" or a crash, as you can still navigate normally, open another session etc. But it would appear to be a problem with newly created sessions. I tried different versions of the firmware that I had on my computer (4.90, 4.91pre8, 4.92, 4.93, 4.94pre2, 4.95pre10), but all gave the results described above. Can someone else replicate this? JL