Dubstepforum.com

deadly habit wrote:

rhek wrote:Ello guys.

Just a quick one..

Im using the Virus TI intergrated Cubase 5 (im sure this is relevant to any outboard hardware etc).

Basicly i can't edit the values on any automation on the instrument channel. I can draw in shapes etc but i can't edit the actual values of each point, just the positioning. I can also write in automation with real-time but obviously i can't be exact with that..

Any thoughts?

zoom in on your lane and as you are drawing in the points on the channel it should show the value to the left on the lane you are automating

Sorry I mean i can't actually edit the values. As in if I manualy write the automation using the hardware so i get a rough outline of what i want i can't then move the points up or down if you get what i mean?

So I can't edit the automation. It's like the points are stuck. I thought there might've been something in preferences locking the points to the bars or something like that.

I can see the value and even tried typing the value in which has no effect..

rhek wrote:

deadly habit wrote:

rhek wrote:Ello guys.

Just a quick one..

Im using the Virus TI intergrated Cubase 5 (im sure this is relevant to any outboard hardware etc).

Basicly i can't edit the values on any automation on the instrument channel. I can draw in shapes etc but i can't edit the actual values of each point, just the positioning. I can also write in automation with real-time but obviously i can't be exact with that..

Any thoughts?

zoom in on your lane and as you are drawing in the points on the channel it should show the value to the left on the lane you are automating

Sorry I mean i can't actually edit the values. As in if I manualy write the automation using the hardware so i get a rough outline of what i want i can't then move the points up or down if you get what i mean?

So I can't edit the automation. It's like the points are stuck. I thought there might've been something in preferences locking the points to the bars or something like that.

I can see the value and even tried typing the value in which has no effect..

are you on the main lane or in the sub cat lane for the parameter?

deadly habit wrote: 3.) bring the level on the main bass sound audio output to 0

Of course ... its obvious now :DD

what a plonker

thanks dude!

i moved to cubase 5.1 from reason about 3 months ago or so and am absolutley loving it so far


I was wondering if anyone has updated to 5.1.2. im a little worried after 5.1.1 (which i didnt use after looking at the forums)

I haven't updated my version yet...

I am curious to know also

deadly habit wrote:

rhek wrote:

deadly habit wrote:

rhek wrote:Ello guys.

Just a quick one..

Im using the Virus TI intergrated Cubase 5 (im sure this is relevant to any outboard hardware etc).

Basicly i can't edit the values on any automation on the instrument channel. I can draw in shapes etc but i can't edit the actual values of each point, just the positioning. I can also write in automation with real-time but obviously i can't be exact with that..

Any thoughts?

zoom in on your lane and as you are drawing in the points on the channel it should show the value to the left on the lane you are automating

Sorry I mean i can't actually edit the values. As in if I manualy write the automation using the hardware so i get a rough outline of what i want i can't then move the points up or down if you get what i mean?

So I can't edit the automation. It's like the points are stuck. I thought there might've been something in preferences locking the points to the bars or something like that.

I can see the value and even tried typing the value in which has no effect..

are you on the main lane or in the sub cat lane for the parameter?

Have you tried pressing ctrl and right clicking on the channel to show the automation? is it on write mode? what about the holding down alt and clicking on the automation value above the time bar?

here's a weird problem I'm having:

So I thought I would finally set up my Korg NanoKontrol to use in the studio a bit (I usually just use it for live gigs), and the most useful feature on it for me is the buttons that you can assign to the transport controls of your VST host. I've already done it in Reason 4, and it works fine.


However, with Cubase 5, there's kind of a weird problem. If I push play on the MIDI controller, the play button on the transport will instantly light up and turn green, meaning the MIDI data has been received. However, it always waits about a second and a half before it actually starts playing. It does this with all of them in the transport; stop, record, return to zero, etc. However, if I assign the button to a different function, e.g. Edit VST Instrument, it'll respond instantly. If I use a keyboard shortcut or click on the transport, it responds (nearly) instantly.


Everything appears to be assigned correctly, and it seems that the MIDI data is being received instantly. So I'm guessing this is a preference somewhere or something? Anybody wanna give it a shot with their MIDI controller and see if they have the same problem? I can't figure out what the heck this could be.


Thanks in advance...any help is appreciated.

hmmm mine works fine wanna take a screenshot of your settings and i'll compare it later on tonight?

cloak and dagger wrote:However, it always waits about a second and a half before it actually starts playing. It does this with all of them in the transport; stop, record, return to zero, etc. However, if I assign the button to a different function, e.g. Edit VST Instrument, it'll respond instantly.

I think Cubase just takes the time to buffer your project before it starts playing. If it is a CPU heavy project this might happen. You can check your VST Performance by pressing F12..

Greets,
Vectrex

vectrex wrote:

cloak and dagger wrote:However, it always waits about a second and a half before it actually starts playing. It does this with all of them in the transport; stop, record, return to zero, etc. However, if I assign the button to a different function, e.g. Edit VST Instrument, it'll respond instantly.

I think Cubase just takes the time to buffer your project before it starts playing. If it is a CPU heavy project this might happen. You can check your VST Performance by pressing F12..

Greets,
Vectrex

Nah man, like I said in the post, it plays fine if I click on it or use the PC keyboard...it's just when sending MIDI data to it (even though it receives the data instantly).


Anyway, it got solved! In the Device Setup screen, for transport controls you have to flag those buttons as "Not Automated." I knew it had to be a settings issue and not a computer one

cloak and dagger wrote:

vectrex wrote:

cloak and dagger wrote:However, it always waits about a second and a half before it actually starts playing. It does this with all of them in the transport; stop, record, return to zero, etc. However, if I assign the button to a different function, e.g. Edit VST Instrument, it'll respond instantly.

I think Cubase just takes the time to buffer your project before it starts playing. If it is a CPU heavy project this might happen. You can check your VST Performance by pressing F12..

Greets,
Vectrex

Nah man, like I said in the post, it plays fine if I click on it or use the PC keyboard...it's just when sending MIDI data to it (even though it receives the data instantly).


Anyway, it got solved! In the Device Setup screen, for transport controls you have to flag those buttons as "Not Automated." I knew it had to be a settings issue and not a computer one

ah glad to hear you got it sorted man

yeah me too!


Cubase makes me sometimes

Ok I've got a new one that I think might be easy to solve but can't figure out how.


So I want to use my MIDI controller to do a lot of the work regarding navigation - transport, selecting tracks, muting, soloing, etc. So far so good.


However, some VSTs automatically have CC data set up to certain parameters, and I've noticed that every once in a while, this CC# will be the same as the button assigned to the transport controls or whatever.


Is there a way to make it so that the MIDI controller only affects the assigned parameter in Device Setup and not the VST if that track happens to be selected? I know I can change the CC # on the MIDI controller, but who knows if another VST uses that one. I feel like there's an option somewhere for this but couldn't find anything. Any ideas?

switch the midi channel the plugin is using to like 2 or higher

cloak and dagger wrote:Ok I've got a new one that I think might be easy to solve but can't figure out how.


So I want to use my MIDI controller to do a lot of the work regarding navigation - transport, selecting tracks, muting, soloing, etc. So far so good.


However, some VSTs automatically have CC data set up to certain parameters, and I've noticed that every once in a while, this CC# will be the same as the button assigned to the transport controls or whatever.


Is there a way to make it so that the MIDI controller only affects the assigned parameter in Device Setup and not the VST if that track happens to be selected? I know I can change the CC # on the MIDI controller, but who knows if another VST uses that one. I feel like there's an option somewhere for this but couldn't find anything. Any ideas?

Would like to see how you've set all that up.

deadly habit wrote:switch the midi channel the plugin is using to like 2 or higher

Nah that does nothing...the plugin and MIDI controller are on two separate channels completely. Thanks for trying, though.



I figured out that there's two ways to do it; either use the MIDI filter to filter out the MIDI channel of the controller (didn't try this one out, though), or just remove the controller I'm using for navigation from the "All MIDI Inputs" so that a track has to be assigned to it if I want to use it for recording.


And nowaysj, in Cubase it's relatively easy to assign anything to MIDI through the Device Setup dialogue...you just have to dig around in the menu to find what you want to assign it to (they could learn from Ableton a bit in this regard).

cloak and dagger wrote:

deadly habit wrote:switch the midi channel the plugin is using to like 2 or higher

Nah that does nothing...the plugin and MIDI controller are on two separate channels completely. Thanks for trying, though.



I figured out that there's two ways to do it; either use the MIDI filter to filter out the MIDI channel of the controller (didn't try this one out, though), or just remove the controller I'm using for navigation from the "All MIDI Inputs" so that a track has to be assigned to it if I want to use it for recording.


And nowaysj, in Cubase it's relatively easy to assign anything to MIDI through the Device Setup dialogue...you just have to dig around in the menu to find what you want to assign it to (they could learn from Ableton a bit in this regard).

which midi controller is it?

Korg NanoKontrol

cloak and dagger wrote:Korg NanoKontrol

weird same as me, can i ask if you have any other midi devices setup? cause maybe that's why i have no issues

Pretty new to production, scanned through the forums but didnt see anything really on automation... Cant figure out how to automate my drums. some help please ? (using cubase 5 if thats any help)