Jump to content

vcfool

Members
  • Posts

    55
  • Joined

  • Last visited

Posts posted by vcfool

  1. Hi,

    I am still using the old core STM32 and Wilba's frontpanel and I have a request that would make my workflow faster and easier.

    Would it be possible to have the Datawheel and Up/Down buttons to do different things in Step Edit mode?

    So when holding the Edit button I would like an extra parameter for the Up/Down buttons just like the one for the Datawheel. Then we could for example use the Up/Down buttons for selecting the Parameter Layer and the Datawheel for value, step or any other combination.

    Thank you very much again.

  2. On 2/5/2018 at 4:08 PM, mfk said:
    
    my bpm-led flashes aynchronous to the beat. (v4_095_pre9). Any ideas?
    
    

    This exact same thing happened to me with my STM32 SEQ v4 (first version STM32, not STM32F4). I actually solved it this way: I decided to upload the previous versions to check when the bug was introduced, but I ended uploading backwards to such old versions on which I was sure this didn't happen at the time of release. I think I got back to something like "midibox_seq_v4_074" and the bug was still there! So I gave up.

    Uploading such previous versions and the corresponding old "hwcfg" file made my configuration parameters not valid. So when uploading back to "midibox_seq_v4_094b" I had to manually reset all my MIDI Router parameters and other settings in the "Options" page which got deleted. After doing this, the BPM LED started blinking correctly on the beat again. So I am guessing that something was messed up in the MBSEQ_GC.V4 file or somewhere else.

    Hope I am making myself clear and that this will help.

     

  3. Hi,

     

    I just tried the above v4.075pre1:

     

    The Seq seems to find the IIC outs. No more "*" appears next to them and I can see the the IIC out activity on the MIDI Monitor page.

    But still, there is no actual data coming out of the IIC Ports physical outputs.

     

    Thanks again for the ultra-fast support!

  4. I think I messed up something in my SeqV4 (STM32):

    :sad:

     

    A few days ago I succesfully uploaded from 4.065 to 4.074. I updated both the bootloader and the application and everything seemed fine.

     

    But just tonight I noticed that none of the IIC Out ports were no longer seen by the Core. The "*" symbol appeared next to all 4 of them.

    I thought that before opening the machine to look for a hardware fault, I would check that it wasn't caused by the newly uploaded version 4.074 of the application. So I uploaded 4.065 again and the IIC ports came back to life. So now I have my IIC ports working fine again, but MIOS Studio is reporting an error every time I try to upload the application or the bootloader. No matter which version I try to upload it all seems to start fine, the Seq LCD's show Bootloader mode for some seconds, but then it just reboots and MIOS Studio shows the message: "Upload aborted due to error #14: Invalid SysEx command"

     

    Now I see that I probably did something silly and maybe Bootloader 1.012 + v4.065 is not a good combination.

    This all happened using MIOS 2.4.4 on OS X 10.8.3

     

    So I'd really like to know if there is a way to fix this and get the USB uploads working again or will I get stuck on 4.065 forever?

     

    Thank you all very much!

     

    And someone with 4.074 and IIC Out ports installed should check if they work. :smile:

  5. Hi,

    I upgraded from v041 to v048.

    Something is wrong with my Drum tracks when played from an external MIDI keyboard: The Drum sounds appear repeated several times over the whole keyboard and some MIDI notes don't trigger the right sounds.

    Using the Live Play mode works fine. Sequenced tracks also work nice. Just direct playing/recording from the external keyboard seems to be affected.

    I just tried version 42 which is the last one I downloaded (but never really tried) and the problem is also there.

    Maybe I am doing something wrong. I went back to v041 and all is fine again.

    Thanks again!

  6. Just upgraded from Beta35 to 38.

    I am using Wilba's CS and found that BUTTON_PAR_LAYER_A is not working for me.

    I can confirm that it is not a hardware problem: MIOS Studio detects that the button has been pressed/depressed but says that it's not mapped.

    I went back to Beta35 and the button works fine again.

    Thanks!

    :)

  7. [...]

    Just one more feature idea, which was borrowed from the elektron machines and which is extremely helpful...

    It is called "note cycle". When pressing "cycle left" or "cycle right" (probably bound to a key plus left/right or up/down), the notes are cycled through the track.

    [...]

    Sorry if I am misunderstanding your idea, but are you aware of the "Scroll" function?

    I'm not sure that I do understand the differences between the already implemented "Scroll" and your "Cycle" idea. :)

  8. Nice, thanks again!

    Been quick trying right now and I think there is a problem with the normal Step View Edit Mode:

    The lower line of the LCDs is always displaying the Notes for Steps 1-16, no matter which steps are selected holding the "Step View" button. The upper line of the LCDs and the GP LEDs do show the actual values and edit seems to work, but the lower lines always show the Notes and Lengths of Steps 1-16.

    Also Length Parameter Layer is showing the bars on non-gated steps: Clear the Track and all the steps will show a Length bar indicator. This didn't happen on previous versions.

    Maybe I am just doing something wrong... :)

  9. I have been thinking that such a feature would be useful too.

    Maybe just adding an "Advance Step Parameter" like the one found on most Tracker style sequencers: Set it to "0" not to advance any step when inserting a note, set it to "4" and advance in quarter notes intervals... etc...

  10. I have not had a chance to update to beta 28 yet.

    I was using a midi keyboard controller going to the midi in of the seqv4 and had a question.

    Right now, to pick which midi out port and channel for the seq to respond to the keyboard, you use the midi router correct? Is there a way that we can have another option that would be on/off selectable that can change the midi router to what ever track 1-16 is selected? I was using one keyboard and was using the live record feature and thought it would be very productive to be able to just select the track you want and have the keyboard automatically get routed to that midi out port and channel so you can quickly record to several tracks one after another without having to go into the midi router each time to hear the corresponding track while in live record mode. Is this workable?

    This is already implemented:

    -Go to MIDI -> Transposer and Arp.

    -Select 1 Bus and choose the right Port/Chn/Range.

    -On "Mode" select "Play".

    Also can more than one keyboard controller get connected by way of another midi in on the seqv4? Its limited to 2 ins right now yes? I guess you could always get a midi merge box and merge several keyboards upto 16 for one midi in :santa: I would probably use 2 maybe 3 keyboards at most to do appregiators on one,keys on another and samples on another. 16 would be crazy though and I bet someone will try it. Can the seqv4 and midi router handle this ammount of input on top of a master midi clock at the other midi input?

    regards

    Not sure I completely understand you... There is a 3rd MIDI In/Out on the Core for the BLM now. But you can use it as a normal MIDI port. I have 2 keyboards and 1 sequencer connected to the MIDI INs of the MB-SEQ v4. Using all 3 Core inputs without any problem.

    Hope this helps.

  11. Nice! My 2 cents:

    Would the extra resistors for the LEDs fit on the PCB? Maybe somebody wants to use them, so they may be a good addition. At least adding only a soldering pad next to pins 6 and 10 of each PIC, without resistors, so one can add the resistors and LEDs if needed. Just a thought...

    Then, looking at your PCB vs the schematics, I see you have connected pin 6 of the PICs to J2 (SV6 on your PCB). As far as I see, Pin 6 should be the "Power ON" LED, and pin 7 is the one that should go to J2. Am I wrong?

    :)

  12. Well, so I have the same situation here.

    I have an AOUT_NG inside a MB-SEQ v4. I have been using Unipolar mode without any problems since I finished it some months ago. I have been following this topic and just now I tried the Bipolar mode.

    So far I have only tried CV1: On the Mixer Map I assigned a CC to the AOUT CV1 output and calibrated P9 to have 0V at a CC value of 064. And I have the same problem: the output range is only -2,7V to +2,6V.

  13. I seem to be having trouble getting a drum track to go for more than 16 steps without having to adjust the options page measure function. It tells me that sync to measure is active for 16 steps when I try to make the drum track 64 steps. that means the pattern will change/update at 16 steps for changing to a new pattern or scubbing right? And it still just loops the first 16 steps even though I have pressed the 64 length. I thought this behavior was odd because my non-drum tracks are not doing this. Is this a bug with drum tracks?

    I get the behavior you mention when I got the "Synch to Measure" enabled under the track's "Divider" page. Maybe your drum track has this enabled and your non-drum tacks have not.

    Just a thought because I still don't really fully understand the Synch to Measure feature.

    :)

  14. To your initial request: since each step can only store 128 values (0..127), there is no possibility to disable a CC without reducing the original value range.

    Ah ok, now I get it.

    I was noticing some odd behaviour when trying to use menu-->trigger to set a drum tracks trigger layers. I wanted to to select a different trigger layer for my drum track instead of accent and I was getting stuck. When I hold menu and select trigger GP, I am given the same things as holding trigger layer C. BUT I was able to at some point use menu-->trigger to select the layers such as accent, roll and nofx on the same drum track. Switching through track groups and tracks then switching back produced some results but I am still unsure of what is going on. I haven't dl'd the 21 beta yet.

    So, what should I say to this "issue description"? ;)

    I think I know what Echopraxia means because I have noticed it too. I will try to explain:

    When you enter to the Trigger Assign page, (sometimes) the page will not be displayed correctly. You get the Trigger Layer Select page instead.

    If you then press (and release) Trigger Layer C button the Trigger Assign page will show.

    Pressing the Trigger Layer C button on a Drum track will do nothing. You have to switch to a Note track first. But once the button has been pressed, you can go back to the Drum track and it will also show the Trigger Assign page correctly.

    Hope I made myself clear.

    Thanks again.

  15. This is great. Thank you very much!

    Beta21 is available now:

    
    
    MIDIboxSEQ V4.0beta21
    
    ~~~~~~~~~~~~~~~~~~~~~
    
    
      o If a track is in CC mode, a CC/Pitchbender value will only be sent if
    
        the gate trigger is set.
    
        CCs/Pitchbender events are sent for each step regardless of the gate
    
        as before if the track is in Note or Chord mode.
    
    

    Is there any special reason for the CC events on Note tracks to be sent on every Step?

  16. To start with the classics, I attached 2 .mid files created with ReCycle. The forum didn't allow me to upload .mid files so I added them both to a .zip.

    MIDIbreaks.zip

    AmenBrother.mid -> 4 Bars - 61 Slices (C1/C6) - 138.000 BPM

    ShackUp.mid -----> 4 Bars - 45 Slices (C1/G#4) - 113.325 BPM

    BPM is only relevant when playing the same sliced sample.

    I can attach the .rcy files if needed. I guess at this point these breaks are kind of public domain ;)

    Many thanks again.

  17. Hi TK,

    Just to throw my 2 Euro cents in for this part of MBSeq -

    My main idea with the MIDI file import is to load in simple MIDI files generated with Recycle. Just in case you don't know Recycle, the related MIDI files represent slices of a looped sample (samples being played by a hardware sampler in my case). The MIDI files are monophonic and usually consist of 8- cca. 50 notes, one after another. My dream is to have these imported into a Seq track and then be able to play around with Recycled beats :) not sure if this is doable with Seq4 yet, I am using my Core32 board for other things than MBSeqv4 at the moment....

    David

    Hi,

    I was going to throw exactly the same 2 cents about this. :)

    Importing MIDI files from ReCycle would be great. I have been doing it manually for now. These are simple one-track monophonic files but require quite precise timing (no quantize). I guess this would involve somehow the use of one DELAY Parameter Layer and correct Divider/Length values for the SEQ target Track.

    I am not in need of importing MIDI files containing several polyphonic tracks. Whenever I had to import MIDI files from one machine to another (Cubase created files to an MPC for example) it always involved quite a work on my part. And that was fine for me. Because I really needed to adapt, cut, slice... the "linear" Cubase song, to several tracks/parts to play live. So logically this is a work that can not be done automatically by a program.

    So, for me, it would be more than enough to import one-track MIDI files to a single SEQ V4 track, one at a time.

    Thanks again.

    Sorry to ask the question

    but i think there is a mistake on the Beta 18 release

    I think the record parameter is faulty

    I couldn't record any Note or CC but i saw on the MIDI monitor that event is present on the MIDI IN.

    Maybe it's a mistake or i miss something to do but i don't know what.

    I go to the record Page and i send MIDI event on the Midi IN1 and nothing happend

    Anybody could help me please

    thank you

    We were discussing about the Record function on the chat some days ago, and got to this conclusion:

    The Recording Port is the one selected on Trans/Arpg but then the Channel assigned to the Trans/Arpg is not getting recorded. Use the same Port but a different Channel.

    Hope this helps.

    :)

  18. I have tested these extra buttons. The table in my previous post seems to be correct.

    Now to find the LED.

    :)

    Thanks!

    EDIT:

    I found the extra J3 LED --> SR 17 Pin 0.

    If I am not wrong, I also noticed that there are another 3 free matrix positions: SR 19 Pin 0, SR 20 Pin 3, SR 21 Pin 0. These do not have jumpers on the board and I have not checked how hard it will be to add these LEDs.

  19. A quick question about the PCB: Is there a schematic/diagram showing how the LED/Buttons SR matrix is connected?

    I am trying to find out the SR/Pins of the extra LED and Buttons to assign them on the MBSEQ_HW.V4 file. If I understood correctly:

    -There's one unused LED on J3. What SR/Pin is it using?

    -The extra buttons on U6, out of the matrix:

    I see that the Datawheel button goes to U6 pin 12 and the GP encoder buttons to pin 11. I also noticed that the other side of U6, pins 3-6, are free. That would make 6 extra assignable buttons. Can somebody please confirm that I got this correct:

    U6 Pin 11  is  SR 6 Pin 0  on the HW file (GP encoder Buttons)
    
    U6 Pin 12  is  SR 6 Pin 1  on the HW file (Datawheel Button)
    
    U6 Pin  3  is  SR 6 Pin 4  on the HW file
    
    U6 Pin  4  is  SR 6 Pin 5  on the HW file
    
    U6 Pin  5  is  SR 6 Pin 6  on the HW file
    
    U6 Pin  6  is  SR 6 Pin 7  on the HW file

    Many thanks again.

×
×
  • Create New...