creatorlars

Hi TK! This feature is AWESOME and I have been using it a lot the past week. It works great for shorter counts but for some reason it gets stuck when patterns of more than 16 steps and doesn't progress.

Thank you SO much!!! :) Just in time for a weekend of songwriting too.

No worries. :) Thanks for putting some thought into it -- this is driving me crazy. I'm ready to "finalize" the work-in-progress SEQ4 that I've had around for ages, as it is the core component of my new musical rig.

No, I just meant the bootloader. I thought with MIOS32, the OS was integrated with the program upload.

I did try that (uploading to the most recent bootloader, and then the latest seq4 program again.)

I'm very sorry to keep spamming this thread, but I want to make sure you have all the info I can find about this issue. I found an old copy of MBSEQ4 beta 12 on my hard drive from way back. After restoring that, the AOUT works perfectly fine. So this definitely seems like a firmware issue of some kind.

Okay, further investigation reveals that I am getting SOME response from the outputs, but not at all as desired. AOUT Ch. 2 is changing my AOUT board's CV output 1 from ~5.25V to ~10.8V (max & min values from calibration menu). AOUT Ch. 4 is changing my AOUT board's CV output 2 from ~5.25V to ~10.8V. CV output 3 is stuck at maximum voltage and will not change (~10.8V) CV output 4 is stuck at minimum voltage and will not change (~5.25V) CV output 5 is stuck at -0.6V and will note change (??) AOUT Ch. 8 is changing my AOUT board's CV output 6 from ~5.25V to ~10.8V. CV output 7 is stuck at maximum voltage and will not change (~10.8V) CV output 8 is stuck at minimum voltage and will not change (~5.25V) So it looks like something scrambled here! Again, I confirmed proper logic 0 and 1 levels at the DAC/IC1 pins 8, 9 and 10 directly. I've searched the site and can't find any earlier firmware version compiled .hex files to download and test with. Any help letting me know what I should try next would be greatly appreciated!

Okay, I investigated this further. Using the testaoutpin function in MIOS terminal, the cs, si, and sc connections all test OK switching from logic 1 to logic 0 with the meter, at the input pins on the DAC chips. Logic 0 appears to be something like 0.1V rather than 0.4V and the sc signal is 5V rather than 4V. Those still seem like valid logic signals, but maybe there's something I don't know. Testing resistance with the meter, R32 is 1K values and connected the right way around, so no problems there. I'm going to revert to some older versions of the firmware and see if my AOUT starts working again and will report back. Thanks! Lars

How difficult would it be to hard code this behavior into my MBSEQ as a custom job? The code seems all very well commented and in C, so I am not intimidated, but I am wondering about any pitfalls I may encounter. I would not be concerned about any glitchy side effects with MIDI slave or master devices, since MBSEQ is the core sequencing component in my rig.

Thanks for the reply TK! I will run the tests and see what I find out. The last time I updated my SEQ4 firmware was probably around October or November of 2009, if that helps diagnose anything that may have happened between now and then. A few weeks ago, I finally installed the AOUT board and everything has been working great, until right before the update. I'll let you know what I find out after running the tests.

Note: I did not update my hardware config file at all. Could this be causing any issues?

I would second the option for a feature like this! I often write songs in strange time signatures that change time signatures multiple times in a song. Having one track set as the master references would be perfect. Even if it were a simple on/off options, taking track 1 as the reference.

Hi Midibox community! It has been a couple of years since I have been actively using my SEQ4, life has been busy. I was really pleasantly surprised to return and find all the awesome new features that have been added! I upgraded my SEQ4 today (STM32 core), but now my AOUT board is not putting out CV at all. All the 8x gate outputs are working fine. I have the correct board (AOUT) selected from the CV configuration page. I haven't looked inside, but I was using the CV outs immediately before the upgrade, so I suspect it's not a hardware issue. Any help is appreciated, thanks!! Lars

I am using a 2GB SD Card of the SanDisk brand... it was brand new from RadioShack. So it should be fine, right?

Will do. The SEQ4 just got a new friend the other day... Yamaha TX816 with six modules... my mind is getting blown this week... :frantics:

Hi everyone -- Been really enjoying getting to know my SEQ4 the past couple weeks. Can't express my appreciation enough to TK & company. I've noticed a small glitch when loading patterns. Sometimes when using the pattern or song screens to change the pattern, gatelength and/or velocity get "locked". So for example, a pattern plays a note on every step whether or not its supposed to. Or all velocity levels get fixed at a certain spot. In both cases I can't change it, but if I switch to another pattern, then switch back, sometimes a couple times, it will load the correct gate/velocity parameters. Could this be an issue with my SD card or a problem with my build? Or is it a potential glitch in the software? It's not a huge deal to me, but I wanted to report it. Thanks, Lars

Amazing, can't thank you enough! Coincidentally I just finished assembling everything in my case and am ready to jam!

I did not realize this -- thanks!

Yes!!! Awesome!! Thanks again, can't wait. :)

I have a simple suggestion for Song Mode -- Could, for a given song position, a track group be given an option of "no change"? This would mean that whatever pattern was playing from the previous song position would continue playing without the need to specifically define it again. This is a minor thing, but it would be very beneficial to me while composing/structuring a track and eliminate some grunt work, especially in workflows where I am using mute events on the same tracks over and over, or in phrase mode if I want to effectively change a core beat pattern but leave everything else the same regardless of whatever else that is. Thanks, Lars

This sounds absolutely perfect to me. It will cut the time it takes for me to hammer out tracks with my rig in half, easily. Thanks again, Lars

Hi Thorsten -- thanks for your reply and your attention to my request! I completely agree -- Your suggestion of "preset patterns" or "pattern templates" is absolutely perfect, at least for me. I would have no real need/desire to have additional drum/instrument maps or presets if this is the case. Here are a couple suggestions that would fit my personal needs: 1) Instead of saving pattern to bankstick, you have the option to save it to a new "pattern template"... it would not save any of the sequence data, just category/track/drum labels and track mode configuration. The name/label of the track would become a new option when scrolling through track event modes in the "track event" page. 2) Or alternately, a special track event mode could be set up to inherit track event properties/labels from another pattern. Then any saved pattern could be used as the "template". As far as number of allowed templates, 16-32 would be more than enough for me. I will post on the SEQ forum as you've suggested, I just wanted to share my feedback here first. Thanks!

Thanks for all the info! Well I wasn't sure what step to omit, so I ended up going thru the whole tutorial process -- learned a few things along the way, hah! But I've got it all set up and successfully compiling now. Sure, no problem! On the subject of labels, it would be nice to be able to create specific label/preset maps for separate instruments/instrument setups, and access them easily from the track event page. Even better, if I can just dump them as an easily editable text file into the root of the SD card. For example in the drum case, I have a modular drum machine and a couple others (Drumulator, Ensoniq Mirage) that respond to MIDI. It would be nice to have a preset map with labels and midi notes for each of these instruments, so that I can quickly just select the instrument I want and start programming. If I could set up preset label/note maps for each of my instruments, my workflow would speed up 200%. Is something like that possible to achieve?

I sincerely apologize if this question has already been answered. I dug around but couldn't find out if I'm missing something. What tools/toolchain is needed to recompile MIOS32 source for development on a Windows machine? I find plenty of information on the wiki for MIOS toolchain, but not MIOS32. Any point in the right direction would be most appreciated... I just got my SEQ4 built and want to change some of the preset labels. :) Thanks, Lars

Awesome, thanks for the code TK! The UI is a secondary concern... preconfigured clock outs would be fine if I can't find another way to do it. :)