Jump to content

Hawkeye

Administrators
 View Profile  See their activity

  • Posts

    3,632

  • Joined

  • Last visited

  • Days Won

    36

 Content Type 

Posts posted by Hawkeye

  4. LoopA V2 Introduction, Features & Support Thread

    in MIDIbox User Projects

    Posted

    @Elektruck - thanks and cool that you like it, it should bring joy and help with creativity, if it does that, it's a win! :)

    I've added your request to the dev wishlist - technically it would be easiest to implement it as a setting in the config screen - we should be able to add it as a later feature without a problem, but it probably won't be in the upcoming v.208 - but we will be able to get it done! :)

    Best regards and have a good wintertime!
    Peter

  6. LoopA V2 Introduction, Features & Support Thread

    in MIDIbox User Projects

    Posted

    @Karg Thanks a lot! Good idea, and it's already been requested and is on the list! :)

    Regarding the expected time line:

    a) first, there will be a LoopA software update coming relatively soon (before this holiday season), which will add a few new features that have been requested and which will make the LoopA a lot better at recording previously-unknown loop lengths. This is possible on some other MIDI loopers and also on audio loopers, so it should be nice to have it :). This feature also has limited BPM autodetection, so you could just play in a sequence in the new "autoloop" mode, and LoopA will detect its speed and length :).

    b) then there will be the MatriX launch, still hoping for 2020, but it could be still slightly delayed, it's a massive project.

    c) then there will be the LoopA update to support the MatriX - i'd expect it around February or March 2021, the LoopA should get good support by the MatriX, it might take a while, but will be worth it - the MatriX can instantly use the SEQ v4+ by the way.

    ---

    Regarding session naming - yes, that feature is already on the list and is already implemented in the file data structure - every session has already internal "space" for a session name.

    Note that this will not rename the file itself, as more than 8 characters can be stored. So every session file will still have a number, but can also have an optional additional session name, that you can set and see within LoopA. This also makes old "unnamed" sessions compatible with new ones and you can rename the old ones, once the feature is implemented. This feature will not be in the December update, but it's quite high on the list :).

    Have a good day and many greets,
    Peter

  8. SEQV4 (wilba PCB) - SD-Card Error

    in Testing/Troubleshooting

    Posted

    15 hours ago, Phatline said:

    strange is that the mios-studio-ports says that "seqV4+" (its a seq v4 wilba FP without tpd)

    That's all right - for the software it is a SEQ v4+, if it has a STM32F4 with 1MB of flash memory - it just can't use the extended UI features of the midiphy SEQ v4+, primarily the secondary selection row and the TPD/Activity Matrix - using the Wilba hardware config file should work fine.

  11. SEQV4 (wilba PCB) - SD-Card Error

    in Testing/Troubleshooting

    Posted

    No problem, moved to the troubleshooting forum.

    Please make sure the card is formatted with FAT32, that it is no XC (eXtended Capacity Card) and that the card itself is good. I've had damaged SD Cards that formatted well under windows (with the quick format basic windows formatter), but then could not be written on.

    If the SEQ v4 can create directories, i would agree it does not look like a hardware problem -> recommend to exchange the card for another one, e.g. an 8GB or 16GB Sandisk Ultra (SDHC) which are available for 5-8€ or so.

    It's also recommended to use a tool like SDFormatter (Windows) to do a low-level format of the card with FAT32, this tool can also do some extended error checking.

    Best regards,
    Peter

  12. midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    @Eamoex that's very cool - regarding Morphing, it's a transformation function that splits any track into two halves and allows seamless morphing between those two. For example you could record two sequences, one on steps 1..16, one on steps 17-32 - and with the morph function "fade" between them, but it's a real morphing, not like volume fading in a mixer - i.e at a morph value of 50%, you'd get an average note between the first and the second sequence. Cool when e.g. force-to-scale is on. In the big user manual over at ucapps.de: http://ucapps.de/midibox_seq_manual_m.html
    you can find a slightly more in-depth description and two audio demos of morphed tracks. See section "Morph Page"

    Regarding quantization: a step sequencer needs to map all recorded events to discrete steps. In the recording screen you can modify the "Quantize" percentage value, which defines how close to the original step any recording (notes, triggers, CCs) will be placed. But you can also record something that is similar to an unquantized recorder (e.g. LoopA :)) - to simulate this, you can increase the track step length and also change the tempo divider - this allows to record "human" sequences, e.g. of a drumloop that is not perfect with 100% spot-on timing and that could be configured to play back at the same speed as e.g. a 16-step sequence, resulting 16 "substeps" additional resolution per original step of the "slow" 16-step sequence. Hope that makes sense! :)

    Many greets,
    Peter

     

  14. LoopA V2 Introduction, Features & Support Thread

    in MIDIbox User Projects

    Posted

    @Phatline yes, we can do that - currently finalizing the MatriX, but after its launch, the LoopA will get an update anyways to be able to connect to it - we've also collected a few other items on the extension wishlist by other users by now, so there will be a v2.08 after the MatriX launch :).

    Just to make sure i understood it right:

    * add a new config setting in SETUP screen - "transmit PC after load" (on/off, off by default to not break behaviour for existing users)
    * if this setting is enabled and after a session has loaded, transmit program change MIDI messages with the loaded session number to all six tracks.

    -> It's a great idea, i think, thank you! With this function, people could set up their patches to match their LoopA sessions and after loading a new session, all synths can change to the respectively required patch.

    Best regards,
    Peter

  15. MB6582 Fan

    in MIDIbox SID

    Posted

    If you're using 8580 or 6582 SIDs: heatsinks and maybe some passive ventilation holes in the case bottom will be sufficient - using this setup since 10 years now without any problems! :). If you are using 6581 SIDs, that's a different story though, as they run hotter.

    post-7895-007007500%201283479404.jpg

    Many greets and have fun with your MB6582! :)
    Best regards,
    Peter

  16. LoopA V2 Introduction, Features & Support Thread

    in MIDIbox User Projects

    Posted

    @rvooh thanks for the explanation - just thinking about an easy-to-implement solution for this - i'd be interested in it as well, as another LoopA user had reported a similar problem - the MIDI-clock-synced LFOs of a synth would have a bit of "stuttering" when starting or stopping the sequencer engine, as the synth needed a few clock ticks to synchronize itself and went out-of-sync directly after the MIDI stop, leading to problems with any lfo-synced echo effects.

    How about this proposal - i think it might help both of you, while it would not change the workflow for all other LoopA users:

    1) pressing the SELECT encoder and RUN/STOP would activate the sequencer engine in "softstart" mode, without sending a MIDI start (0xFA) command, but the MIDI clock (0xF8) would be sent (LoopA sequencer is running, clips are played back, you'd need to mute those manually or use an empty scene)
    2) when in "softstart" or "softstop" mode and you press RUN/STOP again, the MIDI start command would be sent (the running clock is "untouched" and everything stays in sync)
    3) when the sequencer engine is running and you press SELECT and RUN/STOP again, the MIDI stop (0xFC) command would be sent ("softstop" mode), but the MIDI clock (0xF8) would continue to be sent (LoopA sequencer is still running)
    4) when in "softstop" mode, pressing RUN/STOP again would finally stop sending MIDI clock (then the LoopA sequencer engine is not running anymore)

    Would this approach improve matters with your 303?

    Best regards,
    Peter

  18. LoopA V2 Introduction, Features & Support Thread

    in MIDIbox User Projects

    Posted

    15 minutes ago, rvooh said:

    Just one question: does the device also send midi clock when it is not playing? I prefer it like this, but a lot of devices don't do this and it's quite a dealbreaker for me

    Thanks for your interest in the LoopA, @rvooh!

    Comparable to the SEQ v4/v4+, also for the LoopA the sequencer engine needs to be running to create a proper MIDI clock. But it is very simple to have the sequencer running and not playing back any recorded clips. You could either mute all tracks in the mute screen (6 button presses), or have an empty scene that just contains no clip data - to then perform a "synced" switch to the first scene containing note data you'd just turn the upper-left encoder once to jump to the first scene.

    You can also assign a footswitch pedal for this task, so you would not need to physically sit in front of the LoopA :).

    This can also be stored as a startup-default (as the LoopA automatically recalls the last stored session), so after powering up the LoopA, you'd just need to press Run/Stop once and would have an active MIDI clock and no playback.

    Best regards,
    Peter

  19. LoopA V2 Introduction, Features & Support Thread

    in MIDIbox User Projects

    Posted

    12 hours ago, Karg said:

    Does the LoopA forward/route Program Change messages as well?

    Hi Karg,

    no problem, as you said, there is both a router and a separate live forwarding function built into the LoopA:

    * the MIDI Router should transparently route program changes. These are the 0xC0-0xCF MIDI packets followed by a program number byte, they should be visible in LoopAs MIDI Monitor screen.

    * "live forwarding", as configured on the track page will only forward Note On/Note Off and CC messages, this is basically to avoid confusion, i.e. if you have a main synth as a master keyboard, changing a patch there should not be forwarded to another synth via this "live" facility.

    Best regards,
    Peter

  20. midiphy wirescanner - introducing a graphical cable testing toolkit :)

    in Miscellaneous

    Posted

    @Antichambre no worries, no harm done! A specialized crimp tool is also very good idea - everything that makes cables better! If you don't have a crimp tool with replaceable insets, at least the wirescanner can test the built cables reliably... 

    In the early days of building MB6582 display cables, i tested every pin 1:1 with a digital multimeter and with that time-consuming method probably still missed out shorts to neighboring wires! :)

    Best regards and have a good weekend!
    Peter

  21. midiphy wirescanner - introducing a graphical cable testing toolkit :)

    in Miscellaneous

    Posted

    Hola,

    as cables are quite often problematic, Andy has developed a really cool tool, that allows to visualize the integrity of your cables - not only IDC cables, but also micromatch cables, as used in the upcoming MatriX :). Here's a short introduction video:


    Shop link:
    https://www.midiphy.com/en/shop-details/0/84/midiphy-wirescanner-pcb

    Hope you enjoy! :)

    Many greets and have a nice weekend,
    Peter

  25. The state of SIDs old and young today

    in MIDIbox SID

    Posted

    Just also as a reconfirmation: i've got eight 8580s in the MB6582 - and since 10 years all is good, all the filters are fine and i will never let go of this synth :).

    For those arguing SIDs have a relatively high noise level (in contrast to the clones): that is true, but a perfect extension to your MB6582 is an (inexpensive) external multichannel noisegate. Then you will get the best of all worlds - noise-free recordings when the SIDs are not playing, and the original sound + filter behaviour when turned up. I can recommend e.g. a BSS Audio DPR-504 (around 150€).

    The SIDs in my MB6582 are passively cooled with heatsinks and i would not see a reason why any of them should break soon - I think many of the damaged originals that are now on the second-hand market could have been damaged from not-perfect PSUs. But if you've got a nice (i.e. non original C64) PSU for your MB6582, i think they should be good for another 35 years :).

    So, as a conclusion: I think it still makes sense to track down the originals, but buy them only from good sellers and ask the sellers if they did test the filters and can document that test.

    The advantage of that approach: the price of your MB6582 will always go up from that point on. If you install clones, you could expect that better clones will arrive in a few years, whereas the original will always be the original and will be sought-after :).

    Best regards!
    Peter

×
×
  • Create New...