Project
Cubase selected channel by PS
Started by Phil999 on .
Sign in or create an account to join the conversation.
instructions and details inside the archive. It's very close to 512 kB, therefore not entirely finished.
CubaseChannel.zip
CubaseChannel.zip
Hi
Congratulations Phil, mighty fine effort, nicely packaged with good info . . .
I don't run Cubase myself so can't really trial it properly, but it look s good . . .
Some nice features there with the SignalScopes for feedback . ..
A few bits in the code could be tidied up and more features added/expanded when we get the larger filesize soon
Weel done mate
Cheers
MM
Congratulations Phil, mighty fine effort, nicely packaged with good info . . .
I don't run Cubase myself so can't really trial it properly, but it look s good . . .
Some nice features there with the SignalScopes for feedback . ..
A few bits in the code could be tidied up and more features added/expanded when we get the larger filesize soon
Weel done mate
Cheers
MM
I want to thank you for your kind words, coming from an old 'veteran' like you. They mean much to me.
Lemur is what I've been dreaming of. It seemed unavailable to me, like Paulo Egidio Silva's Dragon controller, or SmithsonMartin's Emulator. I didn't even know Lemur was ported to the iPad, I bought mine in January for TouchOSC, actually.
All the better, all the better, I can now start to really move my software and CV-controlled hardware without the need for lots of preparation. Spontaneous, instant access to lots of parameters without walls of heavy controllers. One or more iPads makes it affordable, and portable.
this morning I've spent some time re-reading the manual, and I think I know now how to use Multipads instead of dozens of Custom Buttons. I want to try that out soon. The Scopes I will probably use for every physics object in all my templates, I like them.Macciza wrote: A few bits in the code could be tidied up
Lemur is what I've been dreaming of. It seemed unavailable to me, like Paulo Egidio Silva's Dragon controller, or SmithsonMartin's Emulator. I didn't even know Lemur was ported to the iPad, I bought mine in January for TouchOSC, actually.
All the better, all the better, I can now start to really move my software and CV-controlled hardware without the need for lots of preparation. Spontaneous, instant access to lots of parameters without walls of heavy controllers. One or more iPads makes it affordable, and portable.
That is a seriously well thought out DAW environment integration. Very cool!
I also don't use Cubase currently, but I imagine something like this would be great for Logic control with the right modifications.
Regarding your included notes about NRPN handling, over the past 3 weeks I've been working on code for easy handling of this.
Have it working very well with DSI Mopho synth test subject send and receive!
I'm tiding up and will release the template today and the code for everyone to utilize.
cheers~
J
I also don't use Cubase currently, but I imagine something like this would be great for Logic control with the right modifications.
Regarding your included notes about NRPN handling, over the past 3 weeks I've been working on code for easy handling of this.
Have it working very well with DSI Mopho synth test subject send and receive!
I'm tiding up and will release the template today and the code for everyone to utilize.
cheers~
J
great. I just had replied to your thread there, good work.
With such useful templates that come out every week, the learning curve for Lemur becomes much less steep.
For Logic, I see much more possibilities than with Cubase at the moment. There is a TouchOSC template or surface where you have timecode and plugin parameter name feedback from Logic. And when you select the instrument tab, the plugin GUI opens, when you select the EQ, the EQ GUI opens, etc. Hmm, this gives me an idea, I could do this with my Cubase template as well. Anyway, Logic is much better for controlling I think. If I wanted timecode and plugin parameter name feedback with Cubase, I would need to create another device there.
With such useful templates that come out every week, the learning curve for Lemur becomes much less steep.
For Logic, I see much more possibilities than with Cubase at the moment. There is a TouchOSC template or surface where you have timecode and plugin parameter name feedback from Logic. And when you select the instrument tab, the plugin GUI opens, when you select the EQ, the EQ GUI opens, etc. Hmm, this gives me an idea, I could do this with my Cubase template as well. Anyway, Logic is much better for controlling I think. If I wanted timecode and plugin parameter name feedback with Cubase, I would need to create another device there.
And the learning curve is also smoothed out quite a bit after reading the manual a few times. 
)
After buying iPad Lemur and trying unsuccessfully in getting it to work in Mackie emulation mode I then tried TouchOSC template (also a multi day undertaking with OSCulator tie in), it is very useful... but it's not Lemur. : ) The day after I had it all working, I came back to find only one way comm and I haven't had it working again in 2 months. )
I was obsessed with having fully emulate Mackie emulation control over OSC in order to switch between audio interface mixer (Metric Halo) with the same template as Logic.
So I ended up working on it a week trying to get that sweet bidirectional communication. The frustration factor was at 100% for days.
The problem was distraction mostly was in me trying to make it work with OSCulator because I thought that I had to map stuff there, but it turns out not at all. I did get it working and ended up with a slightly customized MCU template along with a new working principals for Lemur application dev.
-J
)After buying iPad Lemur and trying unsuccessfully in getting it to work in Mackie emulation mode I then tried TouchOSC template (also a multi day undertaking with OSCulator tie in), it is very useful... but it's not Lemur. : ) The day after I had it all working, I came back to find only one way comm and I haven't had it working again in 2 months. )
I was obsessed with having fully emulate Mackie emulation control over OSC in order to switch between audio interface mixer (Metric Halo) with the same template as Logic.
So I ended up working on it a week trying to get that sweet bidirectional communication. The frustration factor was at 100% for days.
The problem was distraction mostly was in me trying to make it work with OSCulator because I thought that I had to map stuff there, but it turns out not at all. I did get it working and ended up with a slightly customized MCU template along with a new working principals for Lemur application dev.
-J
Phil999 wrote:great. I just had replied to your thread there, good work.
With such useful templates that come out every week, the learning curve for Lemur becomes much less steep.
For Logic, I see much more possibilities than with Cubase at the moment. There is a TouchOSC template or surface where you have timecode and plugin parameter name feedback from Logic. And when you select the instrument tab, the plugin GUI opens, when you select the EQ, the EQ GUI opens, etc. Hmm, this gives me an idea, I could do this with my Cubase template as well. Anyway, Logic is much better for controlling I think. If I wanted timecode and plugin parameter name feedback with Cubase, I would need to create another device there.
now with more available memory space, the selected-channel-template has become a full Cubase surface, with Mackie Control and meter bridge. It is intended for mobile use. At home I find it almost a waste to use Lemur for such profane tasks like pushing buttons. There are other controllers that can do that, even a normal keyboard with some shortcuts.
Actually this update is a good example for what you should avoid (if possible). Hundreds of duplicated elements without proper hierarchy. If I had to start from scratch, I'd probably tried a different approach. But it is working, that's the important thing for now.
I want to thank all the people who have posted their templates, a lot of things I have learned and copied from them.
Cubase.zip
Actually this update is a good example for what you should avoid (if possible). Hundreds of duplicated elements without proper hierarchy. If I had to start from scratch, I'd probably tried a different approach. But it is working, that's the important thing for now.
I want to thank all the people who have posted their templates, a lot of things I have learned and copied from them.
Cubase.zip
added range objects to the dynamically controllable EQ bands. This I wanted to do from the very beginning, but didn't know how. Thanks to the user dbk for his example. Link:
http://liine.net/forum/viewtopic.php?f=25&t=683&p=4125#p4125
channel12b.zip
http://liine.net/forum/viewtopic.php?f=25&t=683&p=4125#p4125
channel12b.zip
Hi
Did you post the right version?
I can't find the Range control - should it be in the SSL Oxford? Am I missing something?
Also heres a suggestion for TG panel -
Rather then list the option above the knobs, have them display the selection
For the Shape control which has the same text . . .
Define the text options with an expression in the container like - shape_text={'LOW','BL',etcetc} to be shared by all 4 knobs
Then add an action() script execute on x to the knob
decl i=x;
i=range(i,0,4);
setattribute(Text60,'content',shape_text);
For the Freqs, because of differing values just use a local var, like this
decl i=x;
decl loc_text={'181','256','362','512','724'};
i=range(x,0,4);
setattribute(ContainerPlugins2.Text55,'content',loc_text);
// For some reason I need to name this explicitly or it referenced the global Text55 even though the others didn't . . .?
Adjust the Textnn refs as needed
End result should be that the Text boxs will show your options when first opened and then current selection when changed
If you only want current selection then delete the defaults from the text boxs.
Cheers
MM
Did you post the right version?
I can't find the Range control - should it be in the SSL Oxford? Am I missing something?
Also heres a suggestion for TG panel -
Rather then list the option above the knobs, have them display the selection
For the Shape control which has the same text . . .
Define the text options with an expression in the container like - shape_text={'LOW','BL',etcetc} to be shared by all 4 knobs
Then add an action() script execute on x to the knob
decl i=x;
i=range(i,0,4);
setattribute(Text60,'content',shape_text);
For the Freqs, because of differing values just use a local var, like this
decl i=x;
decl loc_text={'181','256','362','512','724'};
i=range(x,0,4);
setattribute(ContainerPlugins2.Text55,'content',loc_text);
// For some reason I need to name this explicitly or it referenced the global Text55 even though the others didn't . . .?
Adjust the Textnn refs as needed
End result should be that the Text boxs will show your options when first opened and then current selection when changed
If you only want current selection then delete the defaults from the text boxs.
Cheers
MM
the range objects are in the modulation tab, where also are two aliases of the two EQ bands. Actually I want to have drop-down menus to select various objects, but for now it is fixed to the two EQ frequencies. Being able to instantly define the range of the influence was a very necessary addition. Full range filter sweeps are nice, but in many cases a limited, more subtle sweep is better. Even though most information is there in the manual, it is sometimes a bit hard to use a new object for the first time in your life.
Many thanks Macciza for the suggestions about value display of the TB12412. That is one more thing that was missing, and I can't wait to implement it tonight. I'm very grateful for such good help. This way I (and other beginners) can learn much quicker.
Many thanks Macciza for the suggestions about value display of the TB12412. That is one more thing that was missing, and I can't wait to implement it tonight. I'm very grateful for such good help. This way I (and other beginners) can learn much quicker.
it works great, and gives a much better overview over the current frequencies.
What I've learned is not only to use text objects as monitors, but also that you can define variables in two ways: with an expression, and inside a script. I'm sure this can be found in the manual, and for programmers it must be the simplest thing; for me it is completely new.
channel12c.zip
What I've learned is not only to use text objects as monitors, but also that you can define variables in two ways: with an expression, and inside a script. I'm sure this can be found in the manual, and for programmers it must be the simplest thing; for me it is completely new.
channel12c.zip
Hi
No worries. There are a few more tweaks I can think of that I will look into and a few modules that you may be interested in as well as some other projects to look at . Will send something soon. It would be good to tweak the LMF Freq monitor to better display what is going on.
Unfortunately or best optimisation and on going tweaking I think you should embark on a major rewrite to fix up names, it will make things easier to work out, particularly in 6 months time.
I was going to say I preferred the labelling above the knobs in the TG but really it is about the sound and your ears should be the guide most of the time not some number . . .
Cheers
MM
No worries. There are a few more tweaks I can think of that I will look into and a few modules that you may be interested in as well as some other projects to look at . Will send something soon. It would be good to tweak the LMF Freq monitor to better display what is going on.
Unfortunately or best optimisation and on going tweaking I think you should embark on a major rewrite to fix up names, it will make things easier to work out, particularly in 6 months time.
I was going to say I preferred the labelling above the knobs in the TG but really it is about the sound and your ears should be the guide most of the time not some number . . .
Cheers
MM
the value display can be a problem, and this SSL emulation is one of them. The compressor ratio value is probably the worst approximation. Frequency, decibel, and ratio are very important values to see on a device, but as you say, it's the ear that decides in the end. The knob angles are similar, and if I need to know the exact value, I must mouse over the plugin GUI.
I can rename things or even start from new. It would be clever to replace a bunch of buttons with few multipads. And yes, I would like to know a labeling and hierarchical system that will be recognisable and reusable in 6 months.
You're right, I'll put the labels of the TG12412 on top again. Better to see when the finger is on it.
Looking forward for the modules you spoke of. Tonight I have downloaded a couple of interfaces from the user library that I have missed. This keeps me busy.
I can rename things or even start from new. It would be clever to replace a bunch of buttons with few multipads. And yes, I would like to know a labeling and hierarchical system that will be recognisable and reusable in 6 months.
You're right, I'll put the labels of the TG12412 on top again. Better to see when the finger is on it.
Looking forward for the modules you spoke of. Tonight I have downloaded a couple of interfaces from the user library that I have missed. This keeps me busy.
Hi
We can have a look at those things and see what might be possible.
Renaming would really help, but sometimes it's easier to start anew and copy and paste segments and test functionality as you go.
Otherwise it is possible to get quite lost and spend too much time and headaches on issues that would not be there if rewriting.
If you start off with a well thought out namespace it is far better, time spent thinking it out is better than time spent fixing it . .
Then after a night of extreme editing it is good to go back over what you did and see if you can tidy it up whilst it is fresh in your mind.
There are many marvellous examples floating around with some real gems, and some quite deep programming as well, great resource.
We should do some PMs off-forum and work on some stuff before another release, I can beta test
You're doing really well, a bit more C knowledge will certainly help. Get the K&R book or the C Book, for starters.
For Lemur purposes it is quite a subset of C and different syntax in place but there are a lot of basic principals that are the same.
There are then of course many different ways to do the same thing but certain 'recipes' are very common an good to learn.
I am certainly no expert, I have just done a bit, and learnt by hacking, solving problems & remembering solutions, and thinking . . .
Cheers
MM
We can have a look at those things and see what might be possible.
Renaming would really help, but sometimes it's easier to start anew and copy and paste segments and test functionality as you go.
Otherwise it is possible to get quite lost and spend too much time and headaches on issues that would not be there if rewriting.
If you start off with a well thought out namespace it is far better, time spent thinking it out is better than time spent fixing it . .
Then after a night of extreme editing it is good to go back over what you did and see if you can tidy it up whilst it is fresh in your mind.
There are many marvellous examples floating around with some real gems, and some quite deep programming as well, great resource.
We should do some PMs off-forum and work on some stuff before another release, I can beta test
You're doing really well, a bit more C knowledge will certainly help. Get the K&R book or the C Book, for starters.
For Lemur purposes it is quite a subset of C and different syntax in place but there are a lot of basic principals that are the same.
There are then of course many different ways to do the same thing but certain 'recipes' are very common an good to learn.
I am certainly no expert, I have just done a bit, and learnt by hacking, solving problems & remembering solutions, and thinking . . .
Cheers
MM
that is great, Macciza. I am hesitating to rewrite the entire template to decrease the file size and make it more elegant. Because I fear it will become more difficult to make changes, e.g. changing a button's destination. And also because the current version performs well and with 16GB there's plenty of room. The 32-channel interface (included in a previous attachment) however is way too big, it uses much too much CPU and/or RAM. The iPad2 gets real slow. But as long as I don't have a good (elegant) solution for the meters (http://liine.net/forum/viewtopic.php?f=26&t=971&p=3926&hilit=led+meter#p3926), I can't make it slim. I rarely use this 32-channel interface.
I'm also not sure about my standard channel inserts. I may need controls for 6 insert slots instead of 4, and also make the buttons bigger (also the send buttons). I'll have to rethink the whole design. To squeeze every desired command into one interface is what I want, but it gets narrow.
In the last two months I was able to use this template in live and studio situations, and it has proven to work well. I added my VSTi-interfaces to it, even during a live session, and had all needed controls in one template. The big amount of work I have put into this has definitely paid off. In the attachment is a new version of the Cubase channel template.
Changes:
- tempo control. That's a big one for me, I thought it was only possible with MTC.
- changed the Pool button to Sync Setup.
- changed the REVerence reverb to Waves IR. REVerence crackles when using surround IR's, it's unusable in quadro projects (Cubase 5.5.3, FastTrack Ultra, 512 buffer).
- no distracting bright colours for the physics faders anymore.
channel13grey4.zip
I'm also not sure about my standard channel inserts. I may need controls for 6 insert slots instead of 4, and also make the buttons bigger (also the send buttons). I'll have to rethink the whole design. To squeeze every desired command into one interface is what I want, but it gets narrow.
In the last two months I was able to use this template in live and studio situations, and it has proven to work well. I added my VSTi-interfaces to it, even during a live session, and had all needed controls in one template. The big amount of work I have put into this has definitely paid off. In the attachment is a new version of the Cubase channel template.
Changes:
- tempo control. That's a big one for me, I thought it was only possible with MTC.
- changed the Pool button to Sync Setup.
- changed the REVerence reverb to Waves IR. REVerence crackles when using surround IR's, it's unusable in quadro projects (Cubase 5.5.3, FastTrack Ultra, 512 buffer).
- no distracting bright colours for the physics faders anymore.
channel13grey4.zip
rec enable was missing in the Generic Remote xml. Replace with the one in the attachment.
channelplus.zip
channelplus.zip
changes:
- text objects rearranged
- signal scopes hide if there's no activity
- replaced some faders with sliders
- colour changes
- multiball quad panner now changes colour when moved
- bugfix
- new Generic Remote xml
EDIT: forgot the labels of the TG12412 again. I'll do it in the next update.
channel15.zip
- text objects rearranged
- signal scopes hide if there's no activity
- replaced some faders with sliders
- colour changes
- multiball quad panner now changes colour when moved
- bugfix
- new Generic Remote xml
EDIT: forgot the labels of the TG12412 again. I'll do it in the next update.
channel15.zip
changes:
- TG12412 labels on top
- SSL channel modulation location moved
- bigger panner
- level fader
- bug fixes, new xml
channel20.zip
- TG12412 labels on top
- SSL channel modulation location moved
- bigger panner
- level fader
- bug fixes, new xml
channel20.zip
only a small update. The same Cubase xml can be used.
changes:
- back to one LED per segment in the level tab. I tried two and four LED's per segment because I thought they're not bright enough, but it can be misleading for a mono level meter.
- reset buttons for pan and level. They're not accurate because of the 7-bit MIDI resolution, but for the moment I'll leave it like that. I will use 14-bit resolution later.
- minor rearrangement of elements
channel22.zip
changes:
- back to one LED per segment in the level tab. I tried two and four LED's per segment because I thought they're not bright enough, but it can be misleading for a mono level meter.
- reset buttons for pan and level. They're not accurate because of the 7-bit MIDI resolution, but for the moment I'll leave it like that. I will use 14-bit resolution later.
- minor rearrangement of elements
channel22.zip