SOLVED | New Cubase Install - Monitors But Will Not Record | SOLVED

[velorush]

I had Cubase AI 6.0 installed on my old PC but hadn't had a chance to put it on the new machine. Finally loaded it up this weekend and I had nothing. I am using the Yamaha THR10 as the interface, which worked perfectly with the old PC. After about an hour I finally got it to where I could get a signal in monitoring. I enabled the Guitar Audio channel for recording, set up my click track, pressed record and began to play. Absolutely nothing!

I've worked on it a couple of hours tonight, changed some settings and still nothing.

Yes, the input of the channel matches the VST input. Yes, I have the channel enabled for recording. I even have a fairly tasty amp sim going. I've checked drivers, too.

I've searched the Steinberg knowledge base and discussion groups. I am sure it's some simple little switch that needs to be in the opposite position.

Any ideas before I uninstall and forget the whole thing?

[jettster]

Not familiar with Cuebase but the audio portion was a major pain in the ass when I originally configured my DAW. (And I work on and build computers)

I know in my DAW there is a record button as well as a monitor button for each respective channel, oddly enough I don't use the monitor button only the record is active on the channel being recorded. Doing a search it appears that many others are having audio issues, not only is there basic audio configuration, it also looks like there are connection settings associated with VST routing. Stick with it, you will eventually get it figured out and won't have to mess with it after that.

Good luck!!

[velorush]

There've been several "ah-ha" moments where I've found something that was not set (such as the channel input not being matched to the ISO input), but nothing seems to get me there.

Last night, after posting this, I found the ASIO Direct Sound Full Duplex Setup and was sure I'd found the problem (as nothing to do with Yamaha was checked as an input) - that, too, did nothing - or at least, didn't fix the problem. The only significant difference with this PC (other than being a hoss of a processor!) and the old one is it has a touch-screen monitor and the PC sound is coming out of the monitor (connected to the PC by HDMI). Maybe I'll give it a whirl coming out of the sound card - just a wild guess as the PC sound is not in the loop. All monitoring is done through the THR10.

I find this interesting as I've grown so used to manufacturers finally delivering on the plug-n-play environment that was promised back in the 90's (I've been at this since the 8080 processor). I've too many hobbies and can easily find something else to do. I'll give it some more time. Maybe someone else has encountered this sort of thing and has a hint.

[velorush]

Another Ah-ha!

With the THR10 turned off, I just opened the ASIO Direct Sound Full Duplex Setup and was greeted with a dialog box: "The currently installed soundcard driver does not support Direct Sound Input. Recording audio is not possible. Going looking for a recording-capable driver for the Dell ss2240t...

Or it could just be that the THR10 isn't connected and the PC is freaking out. I think it's that the HDMI monitor is processing sound. I'm going to try to revert back to the sound card in the machine.

ETA: this makes perfect sense as the monitor, while having a sound output jack, has no provision for input. The sound card, however, does (multiple, actually)!

[tomteriffic]

I gave up on Cubase after 4. I eventually got half-ass competent with it but it was a bear. And it took almost as long to register the damn thing as it did to figure out how to actually use it. Andonandonandon Oh and the interface crapped out with zero manufacturer support (that was the last straw for me and PreSonus). Once it got working, Cubase was pretty good but an absolute PITA to get that way.

I junked it, and the big-ass rackmount machine it was running on, got a fairly hotshot refurb laptop with dual monitor capability and put Reaper on it. I'm feeling my way along, but it seems to work as advertised. Right now the dual monitor capability has the app up on the big monitor and the manual on the other. That has made things much easier. The Tascam interface is adequate to my needs, particularly with some decent outboard preamps.

After 20 years and countless thousands of bucks, with maybe a dozen tunes to show for it, I may finally be getting somewhere. Just in time for my ears to crap out and the arthritis to set in.

[velorush]

[TT, I like the post, not that it's time for your ears to crap out and arthritis is set in]

I may have some progress. I switched over to the PC soundcard rather than the HDMI interface through the monitor and cranked up Cubase. I again got the "your sound card doesn't support recording" message. Ah! The THR10 isn't connected or on! Killed Cubase and connected/powered the THR10, then reloaded Cubase - no message. Grabbing a guitar to give it a try, now.

ETA: still nothing. As an experiment I loaded up an included virtual instrument. Monitored fine, just nothing on the recorded track. This is a clue as the virtual synth is coming directly from the software. I've got some setting jacked up - why, oh why would it have some such setting? I would think the intent of the software is to record sound and MIDI instructions - why would it be defaulted to do neither?

Ridiculous!

[jettster]

I have ran into a similar problem, also have an HDMI monitor connection and it has built in speakers. (If you could call it that, they sound like shit) I use a Presonus Audiobox 44VSL USB audio interface and my monitors are plugged into that, it's my audio source for everything. (Inputs as well) Hope you can get it sorted out, would love to hear more music, guitar solos or whatever from people on the board.

[velorush]

Got it figured out:

1. I loaded my midi controller before Cubase and I was able to record and listen to keyboard sounds. Progress!
2. I hooked up and powered the THR10 (interface) before Cubase, ensured I had the correct input selected for the track and I was able to see the waveform as I recorded the track. Still no playback.
3. I DE-selected the "monitor" button and suddenly I could hear playback. So, the "monitor" button must be off in order to monitor playback on the track. I am sure there is some logic to this, but I'll just take the discovery and move on. The Senior sounded spectacular on the scratch test track using a preset called "Jimi's Rhythm."

Off to bed, but at least I've got it sorted out. Thanks to those who had suggestions.

[tomteriffic]

I missed that bit about the "Monitor" button. Hunt around in the menus, there may be a way to automate that button depending on whether or not you're in the record or record-ready mode.

[Feynman]

Well, let's hear it.

[gorch]

The monitor button should be set on when the recording button is on too. You actually monitor a running recording. That's the logic.

[velorush]

Well, let's hear it.

Consider the juxtaposition: a perfectionist with guitar skills only fractionally greater than the non-existent ability to use the recording software.

Consider me Eric Johnson or Tom Scholz in my expectations, but with the abilities of neither.

The monitor button should be set on when the recording button is on too. You actually monitor a running recording. That's the logic.

Understood and agree with that logic, but why would the Monitor button need to be in the "off" position to monitor playback (it's a rhetorical question)?

[jettster]

Sometimes this stuff doesn't work in a logical fashion. If I enable the monitor button on my DAW record channel, it re-routes the signal through an application and introduces a little bit of latency. I always leave the monitor button disabled (record enabled) because I want the raw signal coming from the audio interface input, going straight out straight to the monitors without anything done to the signal. My inputs and outputs are all on the audio interface which has it own volume for the monitors along levels, etc.

Glad you got it working, now get to recording so we can hear some music.

[velorush]

When I'm working in the software, I picture myself sitting (naked) inside the software box, and I think of the various other parts and their inputs/outputs from that perspective.

Are you hitting a bong and pissing in the pool, too?

[gorch]

...

The monitor button should be set on when the recording button is on too. You actually monitor a running recording. That's the logic.

Understood and agree with that logic, but why would the Monitor button need to be in the "off" position to monitor playback (it's a rhetorical question)?

You could argue that playback is not being monitored.