Antichambre

In fact it's already the case, the legacy SOLO follows the Track Selection. So you've got it already now with my modifications. If you are talking about the SOLO which is on the BLM, it overrules the Legacy SOLO, then it will be complicated for the user to understand there's two solo system on the same machine. I think it's good like that. But tell me when you have tested it. Another idea is to disable the legacy SOLO for Midiphy version only and implement the second SOLO layer(BLM) by using the SOLO button. Then on a SeqV4+, Track Selection and SOLO will be unlinked. Best regards Bruno

This has to be reported to the Waveshare team for their QC.

lol, c'est toujours les cordonniers les plus mal chaussés ;) This can be done and optional too... Let me try it tomorrow evening... Don't worry I didn't touch to the master version, it's an alternative branch, if Thorsten validates it, he just has to merge those changes to the master. And for the precompiled files I shared here I clearly mentioned that it's not an official version, in red with exclamation marks!!! ;) @lp1977 Yep like Andy I filed the stem a few before inserting it the first time.

@lp1977 I forgot to apply the option#28(Invert Mute Leds) to the 2nd line when it indicates Tracks Mute in Layers Mute Page. I corrected it and refreshed branch and precompiled another time.

Thx! :) Yep! If you ask yourself why... I'm also unable to give you an answer, I tried both and finally let it like that ;)

Obviously ;) Anyway, this problem is fascinating to follow, what a suspense, we can not wait to discover the outcome ;) I hope it's not too much frustrating for you!

Maybe stupid but... A faulty usb cable? The one you use with LoopA is necessarily different from the one you use directly with the waveshare, so... On sait jamais ;)

@Rio The mute button behaviours is now an option. Old fashion(default), hold mute button to access Layer page or click alternates between the Tracks an Layers Mute pages. It's Option#34. @latigid on The second row behaviour is improved for both mute pages access(Option#34). Second row indicates tracks selection for both pages by default and can be changed by option#35 for Layers Mute page , Rows are no more redundant. The branch and release above in the thread had been refreshed. Best regards Bruno

The advantage is to keep one hand free for something else during drum parts muting too. Question of taste and Live Act workflow habits, no worry.

It should change the behaviour of the mute for your version too. Test it and tell me what happens. the 2nd row(Direct tracks selection buttons) workflow is not an issue for your version cause they don't exist on the wilba CS. There's no change for the 1st row(GP buttons) they show exactly the same thing as before.

Full description is above in the thread ;) I didn't test it with a non Midiphy SeqV4! Here the whole release. !!! This is not official release !!!

Corrected! thx seqV4+_mute_pages_impoved_project.hex.zip Here the precomplied hex file. !!! This is not official release !!!

Here a new github branch for the MUTE PAGES improvement, what i explained above, this is better than words, you can test it directly. https://github.com/midibox/mios32/tree/feature/seqv4+_mute_pages_improvement It remains me to add the option: For LAYERs MUTE page, second row is TRACK SEL or TRACK MUTE... For the moment it's TRACK SEL ;) Done! Best regards Bruno

My best idea is to use the MUTE button to alternate between TRACKS MUTE and LAYERS MUTE pages. When you click MUTE for first time(when previous page is something else than a MUTE page) you will enter in TRACKs MUTE page: OLEDs and 1st row show the TRACKs MUTE, 2nd row shows the TRACK SELection directly, instead of the redundant TRACKs MUTE, TRACK Sel and MUTE leds lit to indicates MUTE for TRACKs Clicking a second time the MUTE button switches to the LAYERs MUTE page: OLEDs and 1st row show the LAYERs MUTE, Instruments for a drum track, parameters for all others, 2nd row still shows the TRACK SELection, or the TRACKs MUTE. in live it's interesting to have the mutes for the 16 tracks and 16 percussions at the same time, this can be an option to choose. MUTE led still lit, but now INSTruments or PARAMeters led lit depending on the Selected Track type(Drum or other), it indicates we are in the LAYERs MUTE and which type of layer it is. Option34/34: For Layers Mute Page Direct tracks butt are: Track Selection for a non drum track, layer button lit: for a drum track, instrument button lit: Option34/34: For Layers Mute Page Direct tracks butt are: Track Mute Now second row indicates the Track mute instead of the Track Selection: Clicking another time on MUTE button switches back to TRACKs MUTE page etc... Clicking other button than MUTE leave the MUTE pages. And EXIT button can be used to come back to previous page if this last was memorized on first MUTE click. Best regards Bruno

What you expect, leave the MUTE page on MUTE button release and come back to previous page is not possible cause Layers mute will not be accessible any more. I had a look on the code @TK. clearly mention it and disabled it. static s32 SEQ_UI_Button_Mute(s32 depressed) { static seq_ui_sel_view_t prev_sel_view = SEQ_UI_SEL_VIEW_NONE; if( !depressed ) { prev_sel_view = seq_ui_sel_view; seq_ui_sel_view = SEQ_UI_SEL_VIEW_MUTE; seq_ui_button_state.TAKE_OVER_SEL_VIEW = 1; } else { if( !seq_ui_button_state.TAKE_OVER_SEL_VIEW ) seq_ui_sel_view = prev_sel_view; } seq_ui_button_state.MUTE_PRESSED = depressed ? 0 : 1; #if 0 // doesn't really work since MUTE button also selects layer mutes when pressed // if( seq_hwcfg_button_beh.mute ) { if( depressed ) return -1; // ignore when button depressed ui_mute_prev_page = ui_page; SEQ_UI_PageSet(SEQ_UI_PAGE_MUTE); } else { if( seq_ui_button_state.MUTE_PRESSED ) { ui_mute_prev_page = ui_page; SEQ_UI_PageSet(SEQ_UI_PAGE_MUTE); } else { if( ui_page == SEQ_UI_PAGE_MUTE ) SEQ_UI_PageSet(ui_mute_prev_page); } } #else if( depressed ) return -1; // ignore when button depressed SEQ_UI_PageSet(SEQ_UI_PAGE_MUTE); #endif return 0; // no error }

Not exactly ;) for now the tracks mute is a constant page(appears and stays), the layers mute page is temporary(by holding mute button). I wish the layers mute page to be a constant page too, shown on oleds + first row and keep the tracks mute on 2nd row. By using SHIFT + MUTE for example. Maybe just for the Drum tracks type. Note: for Drum Tracks it's the Instruments mute page in fact.

If you're already in track mode(only track button lit) and you press(short or long is the same) the mute button, both rows will shows the tracks mute(redundant), if you want to get back the track sel on the second row you must press track another time then track and mute buttons are lit, first row and oleds indicate the mutes, second row indicates the selection. I have to admit that i don't understand this option :/

On my side, for the mute button, click and hold temporary switch to layers mute, then switch to tracks mute on button release. Always whatever the previous function(menu) was. And the others behaves pretty the same. If you are talking about something like short and long press difference when you said "click&release" and "click&hold", it's not the case, there's no diff. I just upgraded to the last firm version to be sure, same... Best regards Bruno

Hi All, On the SeqV4+, is there a way to constantly show the layers muting and avoid to let the finger on the mute button to access it? If not, something like SHIFT+MUTE or a second MUTE press to alternate between tracks/layers should be great. And if we can keep the track muting on the 2nd row, this would be perfect. Can be very useful in live for drum tracks. Feel free to tell me I'm an idiot if I just didn't find it ;) Thx!

Great! :) Congratulations for number #30! Best regards Bruno

Just an idea, even if the team doesn't reply, maybe a user can reply you using forum messenger, send your message to some builder box users, maybe they have the softwares in their computer. Also try facebook, tweeter maybe... About hacking it, can you find the diagram?

I can access some and others are err.404 Best is to open a thread in their forum or contact them directly. http://forum.lividinstruments.com/

It seems the C4 must be unlocked by a compatible software to work. The only way is to sniff it when connected to the compatible software(e.g. Commander) and do the reverse engineering, an heavy work...

Where are you from?... Maybe using a VPN is a durable solution for you ;) Best regards Bruno

Tell me if I'm wrong, the subject is very interesting for me too... It seems to me that microtuning is only possible if the synth allows it, MIDI note mapping is generally done on the synth side, there is nothing to do on the controller side than to send a note. The problem with the @gatesphere's method (Note + pitchbend) is that it will not allow polyphony, only mono, because each note will require its own pitchbend value, a synth voice can receive several notes but only one single pitchbend . This trick only works if you send one note at a time and if they don't overlap, so no chord is possible on the same voice. It already makes this feature less attractive, no? Best regards Bruno