Jump to content

slo

Members
  • Content Count

    169
  • Joined

  • Last visited

  • Days Won

    10

slo last won the day on December 10 2020

slo had the most liked content!

Community Reputation

22 Excellent

About slo

  • Rank
    MIDIbox Addict

Profile Information

  • Gender
    Male
  • Location
    Victoria, Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. What worked for me was because I’m using a powered hub to power the seq I had to remove the data pins from the port that powers the seq. I’m suspecting the hub was generating some interference on these lines and corrupting the OTG input. Hope that helps
  2. I had trouble with OTG. The fix may or may not apply to your problem but it’s worth a look. http://midibox.org/forums/topic/20993-troubleshooting-midiphy-seq-v4/page/20/
  3. On the Jam page under Live recording there is this from the manual. http://ucapps.de/midibox_seq_manual_m.html Have not tried it yet but it looks like what you want.
  4. There seems to be a bug in drum tracks when selecting "Ctrl" in LayB All the details are here http://midibox.org/forums/topic/21545-bug-when-changing-layer-assignment-in-drum-track/?tab=comments#comment-187731
  5. I notice if you set LayB to Ctrl while you are setting up the track and then INIT, LayB reverts back to Roll. This is from the changelog: It seems like it is buggy, I got the same result as OP but I usually set up a drum track and never touch it again, changing the number of parameters/steps will result in loosing the track because it needs to be INIT again to be setup for the new values resulting in all input being lost.
  6. Ok, got it working, ignore above, I went another route. I installed Ubuntu onto my Windows 10 from the Microsoft store and got it working under WSL1. It was quite a few steps involving an X11 server, the GUI works and looks great, its helpful to see what the V4+ does under the hood! Thanks for this.
  7. INFO: controller : Command do "show_editor (('tracks_editor',), {})" INFO: mbs4edit.py: show_editor tracks_editor 1 Exception in Tkinter callback Traceback (most recent call last): File "C:\Users\xxxx\AppData\Local\Programs\Python\Python39\lib\tkinter\__init__.py", line 1885, in __call__ return self.func(*args) File "C:\Users\xxxx\PycharmProjects\MBSeq_Ed\view_tk\menus.py", line 41, in open_sdcard name = filedialog.askdirectory() NameError: name 'filedialog' is not defined I tried running this and got this error. I know nothing about Python but thought it would be interesti
  8. slo

    MIDIbox SEQ V4Lite

    I've been trying to use the SEQV4L for playback of files produced by a SEQV4+ but it's not happening. Are the files from SEQV4+ compatible? Any hints on which tracks I should put my notes?
  9. Looks like it should work, all leds are behaving correctly. Did you try to reflash the firmware? And maybe look at the monitor windows in MIOS for incoming and outgoing notes. The messages about remote access might be a clue, but I don’t know if the V4L has remote access like the SeqV4+ has.
  10. Did you set the midi channel for seq1 to match what the keyboard is set for?
  11. #attempt to make a small synth switcher RESET_HW LCD "%C@(1:1:1)vo.B vo.K iPad syn4" #setup encoder ENC n= 1 sr= 1 pins=7:6 type=detented3 #disable router nodes ROUTER n= 1 src_port=IN1 src_chn=0 dst_port=OUT1 dst_chn=0 ROUTER n= 2 src_port=IN1 src_chn=0 dst_port=OUT3 dst_chn=0 ROUTER n= 3 src_port=IN1 src_chn=0 dst_port=OUT4 dst_chn=0 ROUTER n= 4 src_port=IN2 src_chn=0 dst_port=OUT3 dst_chn=0 ROUTER n= 5 src_port=IN2 src_chn=0 dst_port=OUT4 dst_chn=0 ROUTER n=10 src_port=SPI4 src_chn=0 dst_port=OUT1 dst_chn=0 ROUTER n=11 src_port=SPI4 src_
  12. I'm trying to code a simple switcher in NG and find myself stuck. 4 buttons just select a synth on a channel, but I can't find the Event_Sender setting that will allow all midi events to pass through as stated in the .NGC document.
  13. There is no computer connected, with just a hub under power, that's enough to stop OTG, maybe the hub is sending some current sensing data...just speculating also..
  14. Fixed my OTG problem by using a "charge only" USB cable to power the V4+ from a USB hub. I can only speculate that computers, hubs etc. have some transmissions going on that corrupts the OTG operations.
  15. Ok Thanks Andy, I'll dig into it later this week and report back
×
×
  • Create New...