anonyme-x22

Hello, I agree, and i'm sorry if you feel wrong again. I understand that time today is limited for everyone, and the time are difficult, however i don't expect you to do all the thing as fast as possible. But we've agreed that for all function, avoiding this behavior is a good point. So please when you get time, take a look at this issue to really finish the thing we started. As i said we can work as small increment when you get some time. As for the mode of discussion, i'm sorry again but i'm muted. Of course, if you help me for the most having a way to test the software without need to upload it on the seq 4 v+, i will manage the build environment to make the things! Rgds,

Hello, I you want you can add a - or a ., or whatever you want to fill the space, C-+1, C.+1. Frankly i don't care if it's beautiful, but C-+1, C--1, is far much speaking than C-1, c-1!!! As for cpu power everything consume, that's perhaps not a huge gain, but i never look at this meter, and it don't deserve any purpose just filling a space, the velocity, i look at the top row number where this meter is also shown, but sorry i don't set a velocity according a meter, so as any daw, and again if even i wanted to, i will use the one displayed at the top row! It could be an option, so both will be available if some prefer c-1, instead of C?-1. Rgds,

I looked again to the step edit view. It seems you have 4 Char available. Top row display there is sufficient space to do C--1. Bottom row the third char is a meter? Unless you see a worth to behavior here, it could be removed, and will also allow C--1. So no more upper and lower case, again more consistant and less cpu intensive, so we gain power! You can also use Daw notation C1; C-1, which involve two or three char. if you want something centered into the 4 char: C +1; C -1; C#+1;C#-1; Whatever the less understandable without a specific manual is the actual one. The vumeter after note, is also something cpu consuming for absolute zero to value. There is no blaming involved again but objective criticism!

Again, you're wrong, i don't blame you! I understood special condition as option! So as option menu is only one level, i think you understood i don't want to surcharge it! That just it. I will never blame, you , just put it like the user point of view and the dev point of view! My only goal is to advance, not to blame anyone, perhaps i wrote it the wrong way, But sorry , it has never come into my mind to blame you, it's useless, and as i said respect for you're already work, but improving involve arguing , to reach common commitment, and yes sometimes we can have wrong feeling, like he blame me or what, etc, don't fall here, that's a negative process! Take it as a dev which handle a user, and we do not speak the same language, so sometimes before thinking the wrong way, most of the time, that's because we did not understood each other! We have the same goal, making this software better every day! Also take into account that we do this activity (UI Design) behind a screen with differed time, the most efficient way would have been us in the same room physically! It's common practice, and already validated, but unfortunately du to several reason, we can't do it like this!

As it involve two page, user can choose if he want it hang or toggle. This said you're right the question is does this page should really be there. I think we need two button with a single page where it separate the edit part, involving pattern, and the song/jam mode. I think we both agree that edit and song are the best candidate for that. So where to put the generator page, which is in fact pattern FX, like there is step FX caller trigger. Therefor it became logic that pattern FX (Generator) should be under the pattern button or if you have better one in mind?, which could be a triggered or hang button. Rgds,

Hello, Hold down, If you think i blame you you're totally wrong! I just want to involve you in the full thinking i got for improving the ui/making actually a consistent, most user happy, behavior to value workflow! I'm sorry you see it like this, but you know it's like this when you arguing about thing, as i've manufactured a lot of business ui, i was arguing which a lot of different people, most over the developers where always thinking they were blamed because they took a way alone, and this way is arguable as soon as other notified it, and as no use case prior the dev, it ended like this! This project involved only yourself at the beginning, but now we are about 100 user, so you're no more alone. You're always been the most one to respect, but i think it's time to open more widely your development to user point of view without thinking, that every request is in order to blame you, and that the criticism which insn't blame is the key point in order to advance in ui improvement or any domain. If everything is good, you never improve like one of my managers was saying, so he did never put over 95% of goal achievement, even if everything was perfect and you did not get any criticism on them! Frankly, i would love that someone just blame me for the two album i put on share, even get a ton of criticism, you should be honored, that people look at your work, instead of having the felling of being blamed! Ignorance of someone work by people is perhaps the worst thing you can get! The way i work is easy, i take a picture, see what is wrong, write idea in how to remove/improve the issue. Now as i said whatever it is for after muting or unmuting, or both, this isn't a worth to value behavior against the track+mute option, however it can't stay like this because it doesn't accommodate all user! As i said the most easier, flexible with 100% of user accommodation is to add the three option: option auto select unmuted track option auto select muted track option auto select un/muted track Also, take into account that a professional UI designer, when he do something, he want it the best for all, not only for himself. Frankly i don't use track+mute page as well as i already set the option to disable auto select. However and again I want it to benefit for most user. Rgds, Ps: if you asked me about a use case it's simple: The tx81z use one channel for voice edit. The pattern use ch1-8. So the first thing i need is to mute then select the channel i want to edit Set the channel of the track to the corresponding voice channel of the tx81z. Edit the voice on the tx81z. Unmute the channel on the seq4v+ in order to get the sound. Another use case: Let's say i want to edit the channel but before i want to mute all others, The last muted channel should be selected prior to voice edit. Another use case: I want to edit something muted before unmut it. It valid the option of un/mute with selection. Another one, i want to mute track 2-8 and select the last track. Of course i want to mute unmute channel 2 and 8 and select the last muted for edit! Use case i can find you so much...

Hello, I see now! Effectively to show -1-2 octave we're in trouble! I think when we speak about ui it's important to separate technical and user interface. i understand you took the way of how midi monitor do it and in order to feat 3 letters. I think that we haven't any other option here even if C--1 would have been better than c-1 so the use case is valid! - Turn it full left to disable the step. Turn one to right and it will re-start at C-3 (this was a special request by a user who wanted to re-start at the middle octave) Again Turn it full left to disable the step what the use case? so as Turn it full right to disable the step? It's so much faster to switch the top button under the note to disable them. Again does this is useful, consistent, accommodate all user? For me Turn it full left/right to disable the step isn't consistent and does not accommodate myself! So it should be at least an option if you really want to keep this! - re-start at C-3 (this was a special request by a user who wanted to re-start at the middle octave) Yes that's truly demonstrate the need of a default in the layer configuration page for each layer, and also is un consistent which what you said to me about default configuration, why did he not done a template??? Rgds,

Hello, I understand that's was a need! Question don't you think that this need is covered with: Mute+Track button where you exactly have a quick selection of mute/track select! Furthermore i could have requested wanted a quick selection of the EDIT track after unmuting/muting it? However yes what's % of people using this use case? For me the use case requested is making all nonsense! So consistency to keep everything good would be: option auto select unmuted track option auto select muted track option auto select un/muted track Again the question is does all those behavior are not covered with mute+track select button! The goal is to ensure not too much redundancy in a behavior and if really needed that all user could set according their need! So again i you want to keep this you need: option auto select unmuted track option auto select muted track option auto select un/muted track to accommodate everyone needs! Again the % of people using this instead of using mute+track button should be so low that it's better the remove the case! But i asked people it's time for them to raise their uses case, if not the easiest is always took as default meaning here not auto select at all on this page! Rgds,

Hello, That's the issue " regardless if ALL is selected or not, whenever somebody turns a GP encoder the corresponding step will be activated." what use case you put under if all button is activated: Lets say C3 C3 C3 Four step - Push all button - Move encoder 3 : i get C-1, whatever i set the layer to! So you get the pattern mess with a note you don't want! As you can see no valid use case for this so it's called a bug! This said if all button off why not, even if it's not consistent, yes effectively encoder under none could raise the step on! I don't think it's an option. The goal of the option "Ramp...." is to avoiding concentrate onto the cursor or encoder when all is pushed, or actually that option, work in half as you steel need to concentrate to which encoder i need to turn = set the cursor under a note in other way! Rgds,

Hello, I'm perhaps wrong but edit button contains, the step edit view and/or Pattern Fx view? So the toggle is justified when there is two page on a single button! However does the edit button should not only do edit, and fx should page should belong somewhere else, like pattern button toggle/hang with pattern selection/fx? Rgds,

Hello, there should be a clear separation between EDIT and SONG mode Absolutely, edit page mostly what you did by making all page in step edit view, and graphical view as soon as song button is press. This will ensure where you re are via the graphical display (song mode) or step edit display (pattern). what about PATTERN and PHRASE mode? I think we should work in incremental step because there is so much to do and it's more easy to advance by small step. So actually Pattern belong to step to edit step views, phrase belong to song so song views! Don't read """"" as Next incremental step. """""This said: Pattern button: If you press pattern button, you are in pattern selection, therefore no button except bookmark should work! Then you switch back in edit mode or song mode. Phrase button: Actually here we're facing a name issue, phrase is more when you have a block of pattern whose are linked but not corresponding to exactly the song mode! But phrase mode is blocking pattern chaining! So what's the use case of phrase mode in step edit? - You switch the bottom row to select one of the 16 slot and it display the first pattern of each slot in current edit! Also Phrase mode and song mode option in the phrase/song page, what's the point? If pattern or edit button, phrase mode is selected automatically, if song mode is press, automatically you're in song mode. So the phrase / song mode param in phrase/song page is useless and confusing! I know that if a pattern change and not saved it's lost, but that's another subject, and using phrase mode/song mode option in phrase mode page isn't the good way, it's even more confusing: - edit pattern - switch to song mode - edit A1-2 configuration - nothing change - i need to switch to phrase option to song mode , but phrase mode is song mode, meaning pattern chaining setting! You see so much to do! """" Step/Track/Parameter/Trigger/Instrument/Mute buttons should optionally switch to corresponding overview page, but only in SONG mode same behavior in PATTERN and PHRASE mode? Or all optional: optional in EDIT, optional in PATTERN, optional in SONG, optional in PHRASE mode? Pattern belong to step so edit step views, phrase belong to song so song views! Step/Track/Parameter/Trigger/Instrument/Mute buttons should permanently and not temporary switch to the corresponding overview page another option? which means overall 8 new options - for EDIT/PATTERN/SONG/PHRASE mode switch or don't switch to overview page, permanently or temporary What, No that's where small incremental step is much better: As well as you have simplified mode in the config file (which i think is really not the good way, because not available on the fly), let's say Full simplified mode (allowing page to change according step edit or song button) SONG and PHRASE are closely coupled, PHRASE is just a song of multiple pieces - are there ideas to differentiate PHRASE from SONG further? (I'm asking because this might affect the UI handling as well...) Yes we definitively should work on those two button! Anyway let's make small incremental step! Song and phrase graphical display with song button, and actual one on edit button Rgds,

Hello, I would like to set the edit button in toggle mode, however i don't see it in the list? ################################################## # Button behaviour # 0: active mode as long as button pressed # 1: pressing button toggles the mode ################################################## BUTTON_BEH_FAST 1 BUTTON_BEH_FAST2 0 BUTTON_BEH_ALL 1 BUTTON_BEH_SOLO 1 BUTTON_BEH_METRONOME 1 BUTTON_BEH_LOOP 1 BUTTON_BEH_FOLLOW 1 BUTTON_BEH_SCRUB 0 BUTTON_BEH_MENU 1 BUTTON_BEH_MUTE 0 BUTTON_BEH_BOOKMARK 0 BUTTON_BEH_STEP_VIEW 0 BUTTON_BEH_TRG_LAYER 0 BUTTON_BEH_PAR_LAYER 0 BUTTON_BEH_INS_SEL 0 BUTTON_BEH_TRACK_SEL 0 BUTTON_BEH_TEMPO_PRESET 0 Thanks in advance, Rgds,

Hello, In some case which i cannot determinate, the note is displayed in lower case. This can happen on both display row. The workaround is to unlit, relit the step to make it appears in upper case. Thanks in advance, Have a good day, Rgds,

Hello, Yes it works consistently now with option disabled and my preferred choice. Many thanks. However as i said and it is mentioned in the option auto select unmuted track. Why only at unmute time? Does it is not more consistent when enabled that it select muted/unmuted track? So the option name would be auto select track in track mute page? Moreover if you select mute button then track now it lite the track and the mute button much better behavior by the way, where you can mute top row and select track by bottom row. So does this option auto select unmuted track in mute page is still relevant for the enabled one? Whatever you live the option i think it's important in that case for other user to have auto select track in track mute page instead Rgds, Ps: Users if you read this please tell us: Does the - if you select mute button then track it lite the track and the mute button, where you can mute top row and select track by bottom row. is sufficient for you? Does the ability to select and mute track in the mute page (button) make any sense to you? If yes: Would it be more consistent to select at mute or unmute time, than just at unmute time? Thanks for you greatly requested thought.

Hello, I still think that adding the default value in the layer page configuration would have been a better value to behavior. Rgds,

Hello, Many Thanks. Will try it. However i think the mute+select behavior is buggy, you should consider mute+select as soon as you mute and no the weird way it does it actually! Rgds,

Wrong post reply!

Hello, Many thanks, that will really make the device way more fun, and easy to use, as the all will work whatever the cursor is positioned for the current pattern track. So actually it works but: There is also another issue with all button which is not related to the ramp, the fact is that if you turn all encoder under a blank step, it will add the step while, whatever the ramp mode is activated or not! i think it's a bug, all should only affect already existing step because you still have to concentrate yourself in order to do the knob turning on a note! Futhermore, you can't disable the step once you have rotated the wrong encoder meaning: - Exit All button - Remove the unwanted step! - Select again All button - Concentrate to be under/find an already set step. - Update Rgds,

Hello, Many thanks, it comes in handy, i just left the machine because was to annoyed by the page flipping of all those button. It's just day and night for me, again many thanks just so more usable. Meanwhile i remixed the issue in my head several day, but perhaps the main problem is that there are page more adapted to pattern edit and some page that are more adapted to song playing, like graphical pattern display, or graphical track mute, graphical layer mute , graphical track select etc! So i thought that perhaps the best way will be that as soon as the edit button is lite, the workflow i mentioned before is applied, and when song mode is lite the graphical page are applied, this will remove forever those hang button behavior, and will make everything more consistent keeping all the page and bringing them as the best moment for their use. However in whatever your're in song mode or edit mode, bookmark and phrase button, should have always the same page, with no hang as shift can switch the phrase mode page, but most over song button is exactly the same behavior as phrase mode. I think that for those two button, the song mode should get to the menu (copy...phrase mode...takeover) whereas the phrase button should engage what is in fact the song configuration layout! "As the graphical page for step, track select, mute track make all senses, does the param/layer/ins one are really making sense?" However, I think is the most optimized workflow remaining everything in place while removing hang action on most of buttons! But if you absolutely think that the default behavior (hang) has any meaning/necessary for compatibility: In the simplified mode an option so when you lite song button the around dial button show their graphical page (hang one) instead of the the edit one, and the edit button will show the actual behavior. And why an option, because while it brings all the page back without hang, perhaps some won't need them! Rgds,

The two other ins and layer i haven't used them yet but it is also valid for them. For bookmark, there is only one view, so i suppose the config file should do the job. Phrase/song mode has two view, so it would require same mode as other. Here there is a big issue, because phrase=song button + shift = hold view for the two!

Of course accessing an sd card is just time killer but it's an option you'll be warned,furthermore it has never cut with actual speed sd card from my side! At edit time it would not be annoying, and more useful, storing the session, is something we have to do so many times! Of course for performances, you remove it, like there is a live button, which is still confusing for me as i don't really know what it does, but it could disable the option when enabled, of course with an option to select this behavior! Regarding the performances, i'm around 20% of use, saving a session add 17% on 20%, meaning less than 6% at 80% of course on the stfm4.

That way it is complicated because: - You make it compatible for both but you loose a lot of friendly using mode! - You make it for the actual (I don't think the first version is still made, the benefit of two row are just an incredible step forward), and it is not compatible with the older mode! - You make both and of course you add a configuration switch like in the file to set everything which is on the sd card, or an option! This said: What you are suggesting: with the Copy button the upper GP row shows steps which are going to be copied, and GP buttons allow to set the start/end within the current step view Ok, showing the step to copy withing the 16 step range could be interesting but if you have to copy more like 32-48-96, you will have to handle a different lightening for the upper row other wise useless! i think that the use case is: - Push copy button - do not depress it - Look the step range on the screen more speaking, as step = number, but if you manage it correctly, why not doing everything with top/bottom group, and confirm good range by the screen. A +, but not mandatory users who don't have a lower GP row could change the step view with a GP encoder like before the lower GP row could be used to change the step view Change eventually this one with the encoder, like actually or the bottom group, exactly on phase but: I was suggesting that the bottom group button would have set by 16step start end range: For a 256step (easier because all button correspond to 16 step) pattern bottom button group act as start point and end point so: i want t copy step 48-80: - Hold copy button: - One push in bottom group button at button 3 set start point at 48. - Two push of button 5 set the end at 80. You mistake: - Still holding copy button: - One push redo start point - Two push redo end point - Release copy to copy the range. Of course the dial don't change allow a full compatibility and avoiding two mode and option for this one! An extended and efficient way of copying step! The top of the cake is when you hold paste you could do the same thing!

Well it actually don't work logically, you have to select one, and the other after are selected, it's more a bug! The consistent behavior would have been mute+select all the time! Frankly what's the point, you should select track by track button Yes at least an option please! I know we can adapte to many bug or inconsistent workflow, but do you think it's the right way! It remember my work, how that do not work as expected, open a bug, but for the moment use the weird path!

The issue with the toggle setup is that it does not resolve issue with not used page! For example, step button toggle, will switch between a graphical step view, and the step edit! Frankly the graphical view is useless for me, i don't any interest of seing graphically the steps, because bottom row show already where you are in the pattern by 16 step, plus the upper row the actual step reading! So actually it flash graphical view and after step view which is very annoying! So if use only toggle setting, it will be a mess, because i will have to toggle many time to select step! Furthermore, the thing has to be edited into a file etc, for that type of option, i think it isn't the right place! An option to say : For Step button two view mode On/Off, Two view mode type (toggle/hang), and Single page view type would make configuration a way more flexible and on the fly! Of course if two view mode off, two view mode type will not be effective, just the single page view type! It's the same thing with track, where the view choice is more arguable, but i think the most usable for me is the one switching bottom row from step part select to track select, then i just push back step to switch bottom row back to step part select! Same for param the one with note vue meter and so on, just annoying, so i would prefer it like this: Step button, i edit Param, i change the layer from bottom button etc.. Track button, i change the track from bottom button Step button, i edit all with just a push so each one would show only one view with no flashing or toggle of the not wanted one! An incredible speed up in pattern making, also a way more less flashing screen, and far less complex button management!