Cubase SX3/Reason 4 Rewire Problem

2010-01-29 19:27:10

If this is the wrong forum, I apologise. Feel free to move it.

Alright, so I've had Reason 4 working through Cubase SX3 via Rewire before, around two or three months ago. Now though, it won't work. I open Cubase first, like I'm meant to, and then open Reason. Just before Reason opens I get a message saying-

"MIDI input problem.
One or several of the MIDI inputs could not be opened. They might be in use by another application. Open the Preferences dialogue and check your MIDI settings."

Once I click okay, Reason opens, but there is no sound when I play the keyboard. It will play sound that's already been recorded, but it won't recognise the keyboard. I've looked in the preferences and all the soundcard options are set to "No MIDI input" and when I try to change one to my soundcard- Line6 TopePort UX1, it won't let me because it's being used by another application. Presumably Cubase. But wouldn't this have been the same the first time I rewired it? I don't understand.

Am I even meant to change that setting in Reason to the soundcard, or is it supposed to be the keyboard?

I didn't have to do this the first time. Between the last time I tried rewiring and now I've had to reinstall the ASIO drivers on my computer because for some reason Cubase changed the original ASIO TonePort UX1 one I was using to the default ASIO Multimedia Driver and wouldn't let me change back. Maybe the problem is in that somewhere. The ASIO TonePort UX1 is the only one that works though, and it was set to that one before. ASIO4all always crashes my computer.

Thanks to anybody that can help.

Cubase SX3/Reason 4 Rewire Problem

Reply #1 – 2010-01-29 20:15:04

I guess that your other ReWire clients are working properly?
If that's true ask Propellerhead support for solution

Cubase SX3/Reason 4 Rewire Problem

Reply #2 – 2010-01-30 00:31:58

By Rewire clients do you mean other programs I use it with? If you do mean that, then I only run it through Cubase. But if you don't, then I don't know what you mean. I'll try using it with Audition and get back to you.

Cubase SX3/Reason 4 Rewire Problem

Reply #3 – 2010-01-30 00:55:19

It seems to work in Audition, I don't get that error message at all. Although there is a noticeable increase in latency when compared to Cubase, even though I'm using the same audio driver.

Cubase SX3/Reason 4 Rewire Problem

Reply #4 – 2010-01-30 00:57:38

I meant can you ReWire (through Cubase): Live, FL, Acid... any ReWire capable DAW?

So, if problem is Reason (which I think it is), than ask their support

[edit] How did you get Reason to work with Audition?

[edit2] nevermind, I found it - it's in multitrack

Cubase SX3/Reason 4 Rewire Problem

Reply #5 – 2010-01-30 02:39:54

I don't have any others installed. I might have Fruity Loops somewhere though. I'll install it and try that through Cubase, via Rewire.

Cubase SX3/Reason 4 Rewire Problem

Reply #6 – 2010-01-30 17:26:08

I haven't tried it with FL yet, but I reinstalled Reason and it gives me the same message. I don't understand. It's the same copy of Reason it actually worked with the first time around. My copy of Reason was downloaded so will Propellerhead even talk to me without proof I've purchased their product?

Cubase SX3/Reason 4 Rewire Problem

Reply #7 – 2010-01-30 17:35:22

I thought it's like that
I'm FL fan and similar was reported on FL Forums, but without replies from admins/devs, and users solutions IIRC were confusing and not working

Try reinstalling and deleting all registry values related to Propellerhead
If you can, buy the product, it's one of the programs you should pay for if you can IMO

[edit] I don't use Cubase so can't tell you how to do it, but Reason has 2 inputs, try connecting to the second input (regardless dialog box about MIDI input problems)

Cubase SX3/Reason 4 Rewire Problem

Reply #8 – 2010-01-30 18:46:56

Haha, yeah. I was a bit apprehensive of saying because I've seen some replies to problems like this just being unhelpful "that's what you get" comments. If I could afford to buy it I would. I will one day though. I'm sick of problems like this. I just checked on the Propellerhead website and it says I have to register my copy of Reason before they'll talk to me. So that's out of the question.

I did reinstall Reason, and reboot etc. How would I delete all the corresponding registry values? I'll try again but do that this time.

Cubase SX3/Reason 4 Rewire Problem

Reply #9 – 2010-01-30 19:33:44

PROGRESS. I have no idea what happened, but I now get audio output in Cubase, from Reason, via Rewire. I don't know what this forum's stance is on linking to other forums, but I found this thread looking for similar problems- http://duc.digidesign.com/showthread.php?t=244957

I was doing what the dude in there said and it seemed not to be working, but then I tried a few more combinations and now I get audio through Cubase from Reason.

However, I can't figure out how to record what is coming from Reason, in Cubase. I can record it in Reason, alongside the stuff I've already recorded in Cubase. That's a work around I can live with for now. I'll look up some tutorials or something.

Thanks for your help.

Cubase SX3/Reason 4 Rewire Problem

Reply #10 – 2010-01-30 20:27:42

Well, if that did solve the problem, then you should hear the sound even without disabling MIDI inputs in Reason AFAIK

As I said I didn't find Cubase interface to my preferences so can't tell you what to do, but check this:

- if there is option for releasing audio driver, deselect it (don't release the driver)
- you can easily see what's going on if you run Plogue Bidule as VST in your Cubase and then ReWire Reason through Bidule:

[a href="http://img716.imageshack.us/img716/5532/sshot2a.png" target="_blank"]
I haven't tried this, but just heard that it works for someone

Cubase SX3/Reason 4 Rewire Problem

Reply #11 – 2010-01-30 20:37:00

Yeah, I'd already unchecked that 'release drivers in background' box. I'll download that VST though, it looks useful.

Once again this forum keeps its clean sheet. I posted something in the past and whoever replied was really helpful too. So thanks to all of you