Jump to content

Gridracer

Members
  • Posts

    142
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Gridracer

  1. Better idea: Similar to Actions like Jump Position/Song/Select Mixer map, a "Mute" Action could be provided which allows you to enter a mute pattern into a song step.

    What I really like on this proposal is that it uses the already given features so menu structure stays lean.

    (Just a new action type) Scenes could be fast and easily recalled with the GP buttons in phrase mode.

    It would work perfect in combination with your second idear:

    How about following solution: a special GP button function in SONG page which copies the current pattern set and mutes into a "phrase slot" of a song

    I think holding the select button in SONG page depressed and pushing a GP button to save the current pattern set and mutes to the corresponding phrase slot (A1,B1,C1.....P1) should work nicely.

    (The action parameter could be set automatically to "MUTE" or an error mesage could be displayed if the

    action parameter is unequal "MUTE")

    In addition, you could hold the select button in SONG page depressed and push the MUTE button to save (the current pattern set) and mutes to the actual song Position-> This could make the need of an extra "Mute Action" obsolete and provides recordabel mute changes for all 128 song positions. While the fast save and recall option is maintaind by saving to one of the 16 phrase slots by the use of the GP buttons.

    I reall think that this could be nice.

    Best regards

    Gridracer

  2. Hello Thorsten,

    I now realize that you think of the mute scenes as an much more sophisticated tool than I had ever in mind.

    Which honours you as an perfectionist!

    My basic idea was to make max. 1-5 snapshots of current mute situations during live performance to be

    able to quickly jump between them. (like on the Yamaha RM1X or RS7000 e.g.)

    The number of 16 seemed just too obvious,  but only useful for song mode to recall the scenes automatically.

    You are absolutely right that a feature that adds more complexity than usage makes no sense at all.

    If I will have a flash of inspiration how to handle a SIMPLE mute snapshot function I will

    let you know, perhaps it will be worth to implement.

    Thanks for all your effort! Greetings,

    Gridracer

  3. Mute scenes are feasible, but the described handling conflicts with the multi-mute selection, as you already noticed.

    I thought a bit more about the handling: What do you think about using the forward and rewind button

    to switch between the current mute page and a new mute scene page?

    This would solve the conflict with the multi mute + multi track selection.

    A ">"  sign in the upper right of the display could indicate that there is one more page forward,

    a "<" sign in the left corner displays that there is a page backward.

    Saving a mute scene could be done by pushing a GP button while depressing the select button.

    I also find it confusing, if settings for a song have to be done in another page.

    Where do you see a cause of confusion?

    My idea was, that each song provides storage for 16 mute scenes that are

    represented by the 16 GP buttons on a second (new) mute scene menu page.

    Those mute scenes should only belong to the song they were created in

    and should not be exchanged between songs.

    So i think there is no need to define anything in the song screen.

    My personal preference would be to use the mute scenes in phrase mode to create different breaks that would take me to much time to perform with the multi mute selection method.

    But I think there is the option to blow up the usage of the mute scenes for song mode:

    You could define in the song screen at what song position which mute scene (1-16) should be recalled.

    (just like a pattern)

    probably yes

    Will do my very best to handle it ;)

    Best regards

    Gridracer

  4. MUTE SCENES would be a nice thing to have I guess:

    If feasible, a set of 16 mute scenes could be stored within a song, by the following use of the controlsurface:

    The mute button could be used to toggle between the already implemented "track mute page" and a new "mute scene page".

    With the 16 GP buttons you could recall 16 mute scenes.

    To save a current mute pattern, hold the select button depressed and push the GP button you want it to be stored to.

    (A note to do so could be displayed like on the pattern save page)

    The multiple track selection feature by depressing the mute button could be maintained, but the mute screen would toggle when the

    button is released. I must admit that I  have no idea yet how to overcome this,  but perhaps somebody else has.

    Finally just a cosmetic issue, (not really worth to mention):

    I wonder if I am the only person who is a little confused by the behavior of the the LEDs on the mute page, because I

    would expect the LED to be on when a track is active and to be off when it is muted and not vice versa.

    Gretteings,

    Gridracer

  5. I think the search for the perfect button is like the search for the holy grail.

    If money doesn't matter at all:

    CONRAD part# 701880 (could not manage to get a working link at least her is a pic.):

    http://media.conrad.de/m/7000_7999/7000/7010/7018/701880_BB_00_FB.EPS.jpg

    But 7,70€ is the best price I found for such an full metal eyecandy.

    But something stopped me from ordering 120 of those beauties for my SEQ  ;)

    ______

    Here a link to many, nice illuminated buttons on ten pages, can not say anything about it as I had bookmarked this link form a thread here in the forum some time ago:

    http://www.rjselectronics.com/cms/html/modules.php?set_albumName=album16&op=modload&name=gallery&file=index&include=view_album.php&page=1

    ______

    Also an interesting thread about soft tact switches that is worth reading:

    http://www.midibox.org/forum/index.php/topic,12283.15.html

    EDIT: chaned link, hope it works better

  6. I think I noticed a bug in SEQ V3.4  :-[:

    It affects stepview 17-32 of trigger layer B and C if the tracklength is 32.

    Problem: The GP led's always display trigger layer A regardless if trigger layer B or C is selected.

    The display's and the led's on the led matrix work correct and display the selected trigger layer,

    also the GP buttons and the matrix butons work correct.

    (The effect only shows when tracklength is 32 on stepview 17-32, all other tracklengths and stepview 1-16

    work right)

    Could someone test this on his box to see if it is really a bug in the application?

  7. I guess you could use the "general purpose connector" that is included in Wilbas design to connect

    a self made breakout box containing the AIN's and AOUT's:

    481496473_e495a4b824.jpg?v=0

    You would have to wire the connector pins to the required pins on the PCB

    But get confirmation from the pros here first I am not familiar with this box.

  8. Here some ideas that do not add really new functions but could ease the workflow:

    (Would be also great to have them on V3)

    1. Behaviour of the SELECT button in EDIT mode:

    I think it would be great if you could select several steps (or a single step) with the GP buttons

    (or the buttonmatrix), by holding the select button depressed.

    Then the values of the selected steps could be changed relatively with the datawheel.(similar to ALL function)

    Any second hit on the select button or any GP or matrix button should lead back to single selection mode

    Think of live composing: e.g. have a track, bassdrum on every fourth step

    -> Select every 8th step ->increase note number so you instantly get from kick, kick, kick.. to e.g. kick, tsch, Kick,tsch... ;)

    2. "preloading steps": Possibility to change the note number of a step without actually setting it.

    Also think of live composing here: I have a track playing, several steps are not set, I know what notes

    I want there. How to get there without hearing my scrolling thru the notenumbers?

    My suggestion: Layer A is already active-> I press it again-> LED goes off or starts blinking

    I change the note numbers of the steps without setting them, (audience hears nothing) ->

    I push Layer A again->  LED is On again. Now I can set the new steps which will now play the intended

    notes right from the beginning.

    3. Could be helpful if the all button would also work on the mute screen

    THANK YOU for all the great work! Have my SEQ up since only a week and cant,t imagine how I came along without it.

  9. I think you have to focus on the voltage, not the current.

    As you supply your core with only 5V the power controler has no  "reserve"  to keep 5V stable

    when load (current) increases. It stays cool as there is nothing to regulate for him, Inlet=outlet what it

    shouldn't be. See the link to the WIKI.

    On the other hand I can not imagine that 4.97v is already a problem but I don't know for sure.

    Is this what you have on the pin of the Pic?

    Perhaps the lag of your voltag meter is to big to show the voltage drop that makes the pic reset.

  10. Hello Godzisz,

    I  had to get myself read into this BLM stuff just some weeks ago.

    Perhaps it helps to think about the basic concept of a scan or display matrix first:

    "Matrix" here has nothing to do with the position of the buttons and led's on your panel!

    It is a concept to handle a large amount of buttons and led's with a smaller amount of

    in and outputs of shiftregisters:

    Think of 100 buttons e.g. without a matrix you will need 100 DIN pin's so each button is

    connected to one pin.

    By using a e.g. 10x10 scanmatrix you will only need 10 output pins and 10 input pins, while the outputs

    are connected to the rows of your matrix and the inputs are connected to the columns of your matrix.

    But you will have to use a technique called multiplexing, that means, only one output and therefore

    row will be active at one time and  current will "flow" thru the matrix so that the inputs can read the information from this active row. Then the next row is activated by next output and scanned by the inputs, then the third.... this switching is done faster than anyone can push a button and has to be realized by your software. Basically the same with a LED display matrix, but here you use outputs for columns and rows, switching is faster than your eye can realize.

    Two problems come along with a BLM matrix, on the scan matrix you could have some undetermined states where the input could not "know from which button the current came from" this can be avoided

    by adding a diode to each button which restricts current flow to only one direction.

    On the display matrix you have the problem that output connected to one row has to "take" the current of all LED's in one row (if all are on) there is a workaround by using low current led's but the propper way to do it is to use a special IC thru which the curent will flow and which can take it. The shiftregister output will only drive this so called sink driver. Also as a Row is only active when scanned the LED gets less current

    in average compared to a permanent on one, so to get the same brightnes you have to drive it with higher current.

    So this is what i have sorted out, if i wrote something wrong, please anyone correct me.

  11. Can;t stop smiling since I finished my box last weekend :D

    First of all, thank's a million, million times to all midibox members for developing and SHARING this

    incredible piece of gear, very special thanks to TK of course!

    Since I got my first MIDI gear in 1995 I always dreamed of "the ultimate hardware sequencer"

    Over the years boxes have come and gone and I spend sometimes more or sometimes less time in my studio. I was pretty happy with my RS7000 but always had an eye on other SEQ's. I had the Manikin Schrittmacher and the Genoqs Nemo on my wanna try list, and I had on the very back of my mind that there was a site about a remarkable DIY SEQ on the net.

    As I work in the automotive industry it became that since the end of 2008 I have more time to spend for

    my hobby then the years before due to shortend working times. :( ??? :)

    So the wish for THE sequencer became stronger than ever before and I was close to get a nemo.

    BUT... then i recalled this DIY SEQ found it on the web again, started reading, reading, reading

    and things developed.........

    http://www.midibox.org/forum/index.php/topic,12903.0.html

    so since last weekend I have a grin on my face and this BOX on my desk:

    3316468944_7c39c685ca.jpg?v=0

    3316466942_94cbffb956.jpg?v=0

    INSIDE:

    3315638913_452e08d790.jpg?v=0

    MORE:

    http://www.flickr.com/photos/gridracer/sets/72157613814527297/

    Here some Info:

    My "want to have it all" frontpanel as well as the rearpanel is from Schaeffer

    The wooden box is made by a friend and carpenter out of ALDER wood which is oiled with FLAXOIL

    My singlecolour BLM is a slight variation of the duocolour version, I only added a darlington array as sinkdrivers.

    These are the buttons I use (more about them, read below):

    http://www.sci.com.tw/PRODUCTS/switch/(R13)%20PUSH%20SWITCH/R13-529.htm

    All modules came as kits from MIKE

    What i learned:

    -reading is the key, if I had read more for example I could have avoided building my own bankstick e.g. ;)

    I just overlooked that there is a PCB available, only no kit ...silly me.

    -Switching polarity on the MIDI sockets is easy.... but also easy to sort out, just compare by using an LED

    with some commercial gear.

    -Optocouplers are lousy little bastards! >:( I became just anothert victim.. mine passed all tests, but messed up SW upload! My bugy opto even works fine on the thru port of the IIC module as the signal gets amplified, but messes up the midi in -> note numbers and Velocity values get randomly changed!

    -The "melt isolation" wire i used on the matrix is tricky, it takes lots of heat to get a propper connection

    so there is the danger to overheat the components. I fried 5 buttons, 1LED, 1Diode and had lots of non

    conducting connections, whereas I had not a single problem on the PCBs.

    -The buttons I use seem to have problems with production tolerances, I guess I was lucky to have only 2 or 3 "sticky / rough" blue ones while I had to repalace almost half of the yellow ones due to the bad feel.

    If the buttons show up to be a cause of trouble I might disassemble them and use them as luxury cap system for tact swiches.

    -ALPS encoder STEC16B04 743420 unequal VOITI + SOUNDWELL encoder ?

    I got my encoders from www.distrelec.de and had to discover that they only decrease values when

    connected as described. I got mine to work by switching ground and highest din pin.

    -Watch the spec's of the displays, I had to use additional resistors and a different potentiometer e.g.

    Finally, I hope I can give at least a little of all that I recieved back:

    4664_CONTENT_jpg4b6adfc2e47eff0ede512b65

    CHAINREACTOR-SHARE.zip

    EDIT: fixed attachment tag

    • Like 1
  12. Hello loziniak2

    nice to see another SEQ arise!  :D

    I guess you were as happy as I was when reading "ready" on the display for the first time. ;)

    Looking forward to see new pictures from your project.

    Good Luck, and Greetings!

    By the way, did you etch those PCB;s yourself? They look great!

×
×
  • Create New...