Had to switch computers, now my setup isn't working

[ebasler]

Hi everybody, new here and I must admit I'm not as educated in how to work my gear as I should be considering how long I've been using it. I got it to work about 10 years ago and never paid much more attention to the details, so my apologies for laziness. I would sure appreciate any help you all could give me.

I had been running Cubase Studio 4 through a Line 6 Toneport kb37.

My new computer is a Dell XPS Tower with Intel i7 processor and 16 GB of RAM, this is significantly better than the computer I had been using and I understood this system to be one of the better options for recording.

I did manage to get Cubase 4 Studio up and running, but had to use compatibility mode to install it.

The kb37 needed to find a specific usb port that it liked, once that was found it has been totally consistent at running the audio for windows (Youtube, my music library through Music Bee, etc.) but Cubase has given me an error a couple of times now during projects, something like ASIO not found Open ASIO error, sorry I didn't write it down specifically. Basically it was like the kb37 disconnected from Cubase and crashed the project.

On top of that, while the output has been more or less reliable, the midi input function is more often not working. For example if I open EZdrummer first I can get signal from the keys to activate the drum sounds, but if I open something else, like Kontact or Reaktor, I frequently (but not always) get no signal from the keys, and if I open those VST instruments first and then open EZdrummer, I can't get signal to EZdrummer either. At that point I have to disconnect the kb37 at the usb port, or restart Cubase and start all over again.

The kb37 has the most recent drivers available. I'm not sure what else to try.

Maybe some or all of what I'm trying to use is just too old now, but the new computer broke the bank already, so I can't really afford much upgrading if I can at all help it.

One other possible clue, projects that ran no problem on my old, less powerful computer, were snapping, popping and crashing until I cranked the buffer size way up. I didn't expect that with the new, more powerful computer. I'm sure I must have had the buffer adjusted differently on the old one too, so maybe that isn't surprising? I was sure hoping for better, though.

Really appreciate any help or just advice on this.

[Drew Stephenson]

What operating system are you on? And is your version of cubase 32 or 64 bit?

[ebasler]

Windows 10 and 64 bit. FWIW I had installed it on a Windows 7 machine previously, and that machine upgraded to 10. Under that format it had been working. But a fresh install to this machine running 10 required compatibility mode at install.

[BJG145]

So you've already got the latest Windows 10 driver for the KB37, and the latest 64bit version of Cubase Studio 4 with update...

https://www.steinberg.net/index.php?id= ... ds_cs4&L=1

Can we not persuade you to try something more current though...? Sonar is now free after all, and Reaper's only £45.

https://www.bandlab.com/products/cakewalk
http://reaper.fm/

Dell are usually great with drivers for their systems, so I'd also find the serial or service tag, look it up on their website, and download the latest versions. It sounds like there might be something amiss with your USB drivers, as I'd have thought any port should work. (There's likely a mix of port types, USB 2, USB 3, etc., identified by small graphics beside the USB symbol. Perhaps you don't have USB 3 drivers.)

[CS70]

Yes, Cubase 4 is from 1998? Using it for routine recording is a bit like wanting to go to work in a Model T. Or maybe too much, maybe a BMW from 1959. Using it on a powerful modern PC is like putting the engine of said BMW in a Ferrari chassis.

Sonar is free and has a similar track/mixer approach as Cubase and you can reuse all your VSTs, so worth a shot. Reaper is also as powerful and you can learn it for free and buy it for a few bucks when you decide you like it.

Or a light version of Cubase, guess it's a bit late for an upgrade path, but may be worth asking Steinberg.

[OneWorld]

There is a possibility that your version of Cubase is too old for Win10. There have been some softwares I have used and they simply would not run on Win10/64, even using compatibility mode, in a way I was sort of glad, forced me to update to a more modern and slick version. Back in the day, Cubase was never even coded from the ground up for Windows anyway, it has always, up till about Cubase 6 or thereabouts a bit of a compromised code when running on Windows

[ebasler]

Ok, that's what I was afraid of, but it makes sense. So if I upgrade will the kb37 likely work with any newer DAWs? Or do I need an update in that area as well?

[CS70]

Never tried one but th interface is much more recent and should work just fine.

[ebasler]

Ok, thanks everybody. I bit the bullet and got a copy of Cubase Artist 9.5.

Didn't solve my issues. Same things are happening. I do have a more detailed description of the failure now.

I was working with my first project in the new Cubase, still using the toneport kb37 as midi controller and ASIO soundcard. I initially couldn't get signal from the keys until I shut everything down, unplugged the kb37, then powered down the computer and reconnected the kb37. Then I had signal from the keys, which I used to trigger one of the included synths. I had bad latency so I adjusted the buffer size to 128, the smallest option figuring I should have the power for that now.

I then added one track of ezdrummer samples. It didn't make it through one play-through before it crashed Cubase, by which I mean playback stopped, and a buzzing noise started. None of the buttons or other controls did anything. In the ezdrummer interface, in red letters, was the message "Audio Engine Inactive Check Your Audio Device". That would be the kb37, right?

When I went to Task Manager, Cubase was not responding. Before shutting anything down I went to Youtube and could hear the audio through the continued buzzing sound, so the kb37 was still playing audio from the computer in general, but was buzzing and had crashed Cubase. I shut down Cubase and the buzzing persisted until I disconnected the kb37.

So I am assuming that I need a new midi controller. Would you all agree? Or is there some setting I'm missing? I know I could adjust the buffer some, but since these are the same problems I was having with the ancient version of Cubase, I think the common link is the kb37.

I'll take any advice, especially recommendations for the best midi controller and or interface. I have a bunch of stuff that didn't work so well with my last setup that I'm going to try to use tonight yet (M-Audio Fast Track, Lexicon Omega SV, Mackie Onyx Satelite, with M-Audio Axiom 25 keyboard and a Roland Edirol PCR-1 keyboard.) Really, though, I'm tired of fighting to make obsolete crap work. I would love some ideas for the most "plug and play" options for Cubase 9.5.

Really appreciate the help.

[ebasler]

Update: I got the Lexicon Omega/Axiom 25 combo to work. So far, so good anyway. Hopefully not jinxing myself by writing this. I would still be interested in advice for upgrades.

[ef37a]

Some years ago, son and I found that Cubase was very twitchy on XP then W7 in that it seemed to want the computer 'all to itself'? One big no-no was to never tick "Release drivers in other Applications" (may not be an exact quote) .

I recently read that unlike Reaper, Samplitude and most other DAWs, Cubase was never fully "optimized" for Windows?

Dave.

[ebasler]

Interesting. I'll make sure I don't have that ticked. I'm hoping to get some real time in on a project in the near future, but I have some tutorials to watch in the meantime. Want to get it right this time.

[CS70]

Some years ago, son and I found that Cubase was very twitchy on XP then W7 in that it seemed to want the computer 'all to itself'? One big no-no was to never tick "Release drivers in other Applications" (may not be an exact quote) .

I recently read that unlike Reaper, Samplitude and most other DAWs, Cubase was never fully "optimized" for Windows?

Dave.

Not sure honestly what that would be. There's no particular optimization to do for Windows, especially for something so relatively simple as ASIO streams.

[ef37a]

Some years ago, son and I found that Cubase was very twitchy on XP then W7 in that it seemed to want the computer 'all to itself'? One big no-no was to never tick "Release drivers in other Applications" (may not be an exact quote) .

I recently read that unlike Reaper, Samplitude and most other DAWs, Cubase was never fully "optimized" for Windows?

Dave.

Not sure honestly what that would be. There's no particular optimization to do for Windows, especially for something so relatively simple as ASIO streams.

Don't know. It was just something I read in another forum and it sort of made sense? I understand Cubase was mac oriented for a long time? But then, 'sall Greek to me!

Dave.

[ebasler]

So I thought I would update, and hopefully provide a conclusion for anyone searching with a similar problem.

I've determined that I was just trying to make obsolete equipment work to a level it couldn't achieve. I bought an Audient ID4 interface and things seem to be working well now. Hopefully that will be the solution. 2 weeks in, so far, so good.

Thank you everybody for the help.

[zenguitar]

Glad you found a solution. And thanks for making the effort to come back and let us know how things worked out.



Andy

[Matt Houghton]

Sorry to be so late to the thread... it sounded as I read through like an audio interface issue... probably old drivers not working consistently. Glad you got it sorted.

If you ever find yourself in that situation again, try running the same hardware with different DAW software... Not a generic Windows app but something that can use the ASIO drivers. The free Reaper trial is good for this. If you have the same problem there, it's a hardware/driver issue; if not it's a Cubase one...

On the plus side, you now have an excellent modern system!

Not sure where Dave's getting his intelligence on Cubase... its been available for Windows amd Mac for aeons, and its a touch more efficient on Win than Mac. Steinberg invented ASIO because Windows audio handling was awful back in the day. Maybe this is what he meant by it not being optimised for Windows?!

[ef37a]

WISH! I could remember Matt! (don't get old!)

Almost certainly a throwaway remark on HR forum, maybe someone with a beef against Steinberg AND Msoft?

Whatever, the small amount of experience I have had with Cubase was not as intuitive as say Samplitude? All those "busses" you have to setup and exporting audio was always a bit of a pain IIRC? In Sam you just go>"export audio". Select .wav or MP3 or other. You can change the quality level and destination if you want but otherwise it defaults to your last setting. 16bit/44.1kHz and Desktop in my case.

Been a long time but I think you have to finagle with "markers" or some such in Cubase?

But, don't mind me!

Dave.