Home › Forums › General › Using Ctrlr › Waldorf MicroQ
Tagged: Micro Q CTRLR
- This topic has 39 replies, 13 voices, and was last updated 7 years, 5 months ago by macmickey.
-
AuthorPosts
-
December 4, 2013 at 6:45 am #16184
Were I can download panel for mQ ?
December 5, 2013 at 7:26 pm #16253Hi
I’ve done a single sound panel ( it lacks some steps of the arp and globalfx2 ) but it can get sound from microQ dump alreadyBut i do a new panel based on the microQ hw ( a kind of replica ) with 16 parts , drum edit ,all factory banks and 3 user banks integrated.
If i’m correct it will be possible to edit drum sounds individually wich are not editable
with the hardware
I think doing macros as vst parameters : 4 per sound = 64 + 128 (drum sounds) params automatable
I must add my first panel as editor : that way , i have a full microQ
Lot of work !- This reply was modified 10 years, 4 months ago by zeoka.
December 5, 2013 at 11:29 pm #16256This looks like it will be really great. Since I own only a Q, I hope when you are done you make that panel as well!
July 30, 2014 at 9:40 am #26832I also dream with a mircroQ panel. I have a stand alone editor, but a ctrlr panel will be perfect.
August 31, 2014 at 7:58 pm #28248Hi i would to display the alt1&2 waveforms
I Wonder if someone knows using Audio Term softwareI would convert the 2 wavetables in 256 SYX or WAV files
Possible ??
Attachments:
You must be logged in to view attached files.October 20, 2014 at 10:57 pm #30991any progress on the micro Q panel? I would love to test it!
October 22, 2014 at 12:42 pm #31053I too am interested in this panel. How about sharing the panel if it already has something working? As a word of advice if you hold the panel to your self and release it when it is 100% perfect then the risk of it ending up on some dark corner of your hdd forever. The community might help you do the things that are still missing. This is just my personal thought and I do the same thing. I am working on v-amp2 panel, but only have one MIDI cable at home so I haven’t been able to continue it although it is able to communicate with the device. Maybe I will share it soon unfinished, the functionality is the most important part of the panel the layout comes in second. Having functional panel with a layout that doesn’t satisfy everybody is better than having no panel at all. And because this application is flexible people that has issues with the layouts can change them to their liking.
Sorry for the outburst, but it seems that I have those when the issue is even loosely related to some other issues =)Ramblings about things related to the studio:
http://studio.therobotinitiative.comOctober 22, 2014 at 1:51 pm #31055Hello
Sorry about this panel i give up for now
i must reconsider it
if I want full vst integration for it , I need to break it and reduce very strongly my mods number near 380 for sound ,same for multi data and drum set data plus single params
Since I masterize way better uiCustomComponent I can reduce strongly mod number
, evitate a lot of brainer and add “macro” modulators
customcomp does a lot of cool things
-multiple params in one (like step arps ) using BigInteger +hidden mods (valueMapped)
-multistage interrupts (evitate using several buttons&radiogroup)
-listboxes&tabs&modulators&graphic elements in same time
-customized listboxesI’ve created for another synth a global data custom comp that works
with sliders & buttons
my system doesn’t work with “snapshot” feature but could work with “progam” feature
using “createProgramFromData”
I will start a new panel this week and post news very soonEdit :
Also I’ve 3 options :
-The panel works like micro Q (buffers must be saved before quit like micro q)
simplier method for me-The buffers (37+50) are kept in the ctrlr when I JUST save project in the DAW
– Implement the two with possibility of chosing one
What do you think about it ?
- This reply was modified 9 years, 6 months ago by zeoka.
October 23, 2014 at 2:07 pm #31099Nice to hear that you are planning to start doing a new one. This is something from the book The Mythical Man-Month it states that when doing software you should plan for a throw away version, the first version that you ever do which is kind of what you are doing and what I have come across in my personal plug-in project for Reaper. But for all of those throw aways and unfinished panels how about if there were some dumpster for them? Place where you could leave them and people should be aware by the context where they are available that they are what they are, no guarantees, only there to some one to pick a project up or to learn from.
From those choices the third one sounds best. The first one is good if you want to save the patch for later access, good for playing around with sounds.
The second choice is also very good because for some the workflow would contain the patches in the project file. You know when you are working on a track you can just open it and you get all the sounds from that.
So giving the option to choose from one from the other would be eventually most ideal in my opinion. But starting out with the first option, to get something saved, is better than not really working version of the two.
I think this idea taken from API design also applies here: It is easier to add something later than to remove something.
So do one version first and forget about the other options. Add other options when you have the time.Ramblings about things related to the studio:
http://studio.therobotinitiative.comOctober 24, 2014 at 12:49 am #31125ok
I upload something soon then you and others could test and participateFebruary 23, 2015 at 6:36 pm #38686Hi 🙂
any news?
xx
July 14, 2015 at 1:16 pm #52651…. i Wait it long..
Do You stop work on this panel? Not waiting it?July 15, 2015 at 4:14 pm #52779Hi
I’m on something but it’s long . It will be not free but sold cheap
it does not have a beautiful design with nice knobs but all sound params is in one page , all modulation sources&targets set by drag&drop from fixed lists,graphic envelopes, graphic arp with random step timing &lenght represented by timer. Panel Color choice of your device .drumset will quasi work in real time . sounds of drumset could be set (not possible with the device). my philosophia is someone turn on a microQ, play with it, modify sounds ,create multi or not ,save all in the DAW preset file and turn off microQ. Tomorrow he turn on the microQ,open the DAW project , restitute all the microQ state and continue the project
no program bank is planned but all factory sounds could be loaded (part not done yet ) .sounds could be saved in SYX to store them as well the microQ state in own format .A Q/Q+ version is on the go with the step seq editor (no way it works in realtime but could be useful )July 15, 2015 at 4:20 pm #52780When? 😛
July 15, 2015 at 4:31 pm #52781I give to myself one month two max
it’s cool to see you motivated
But I think in two week it will be mainly finished (I abandoned it two weeks , I made home working and other works)
I’m on it everyday now 🙂July 15, 2015 at 5:39 pm #52786any pict about it? 🙂
July 16, 2015 at 11:11 pm #52858Hi
this is a little pic
hope design is not so bad ,it can change but limited spaceAttachments:
You must be logged in to view attached files.September 2, 2015 at 10:06 am #56864Hi. Any news? =)
July 28, 2016 at 3:31 am #69661Any updates / place I can try an interim version ? 😮 🙂
Thanks
October 25, 2016 at 8:00 am #70182No way eh?!
-
AuthorPosts
- The forum ‘Using Ctrlr’ is closed to new topics and replies.