Rewire: MIDI rescanned when adding instruments in Reason

Hi

I tested it with FL Studio 32 bit and its working very well, without any freezes.

However, Renoise is my main sequencer and I would really like to see it

working better with reason.

Any chance that could be looked into ?

If thats really a bug, I would consider it as a serious one.

Thanks

Hi

Is there any chance that someone can look into it ?

Thanks

Maybe the log file show some stuff for bug hunting. Help -> Show the log file …

OK, here are my findings.

Reason 4.01 slaved to Renoise 3.01 32 bit.

Windows 7 SP1 64bit

While starting up, renoise is displaying a message about enumerating midi devices for quite a while.

Now, I maybe wrong as I dont know it’s internals but it could be that something related to midi is causing it.

After adding rewire in and selecting reason, I can see in the log that midi is enumerated again. And again…

Overall, there are quite a lot of midi related messages in the log.

Every time I add the device in reason and switch back to renoise, its freezing again.

I’m attaching the log from one session where I opened renoise and slaved reason to it, switched few times between the 2 apps.

============================================================
Version : Renoise V3.0.1 (Oct 13 2014)
Date : 2014-11-10
Time : 18:44:22
OS : Windows 7 Service Pack 1 (i386)

CPU: Found 1 enabled unit(s) with 4 core(s) / 4 logical processor(s) per unit. 4 cores, 4 logical processors are enabled in total.

Application: Showing the splash window…
Application: Initializing the API…

IPP: Detected CPU type: 0x22

MIDI: Initializing DirectMusic…
MIDI: Enumerating DirectMusic (WDM) MIDI devices…

MIDI: Skipping emulated WDM device ‘Microsoft MIDI Mapper [Emulated]’
MIDI: Skipping emulated WDM device ‘Microsoft GS Wavetable Synth [Emulated]’
MIDI: Skipping softsynth WDM out-device ‘Microsoft Synthesizer’ (not supported)
MIDI: Enumerating Windows MME MIDI devices…
MIDI: Adding MME out-device ‘Microsoft GS Wavetable Synth’
MIDI: Finished device enumeration

Graphport: Initializing Freeimage…

System: Using ‘C:\Program Files (x86)\Renoise\Resources’ as resource base directory…

GraphPort: Initializing DirectX…
GraphPort: Initializing the Font Engine…

System: Running as 32bit process in a 64bit operating system…

ReWire Slave: ReWire slave engine link (Local Machine) FAILED to install (RegError: 5)
ReWire Slave: ReWire engine link (Current User) is already installed and up to date…
ReWire Slave: ReWire Panel was initialized…
ReWire Slave: ReWire Slave mode failed to init (no master is running)…

ReWire Master: Successfully opened

Timer: Seems safe to use the ‘QueryPerformance’ counters…

Application: Start running…
Application: Loading the preferences…

ScriptingTools: Initializing Scripting Tool: ‘C:\Program Files (x86)\Renoise\Resources\Scripts\Tools\com.renoise.ToolUpdater.xrnx’…
ScriptingTools: Initializing Scripting Tool: ‘C:\Program Files (x86)\Renoise\Resources\Scripts\Tools\com.renoise.UpdateChecker.xrnx’…

Application: Init…

DspDevices: Registering native DSP effects…

DirectSound: Initializing…
DirectSound: Using SampleRate 44100
DirectSound: Primary Buffer Format: FormatTag=1, Channels=2, SamplesPerSec=44100, BitsPerSample=16, BlockAlign=4
DirectSound: CreateObjects … OK
DirectSound: Using MaxProcessingBlockSize: 1536
DirectSound: Output Buffer Format: BufferSize=88200, FormatTag=1, Channels=2, SamplesPerSec=44100, BitsPerSample=16, BlockAlign=4
DirectSound: CreateBuffer … OK
DirectSound: Up and running

Application: Creating a new document…

MIDI: Loading MIDI actions from file ‘C:\Program Files (x86)\Renoise\Resources\Scripts\GlobalMidiActions.lua’…

Osc: Loading OSC actions from file ‘C:\Program Files (x86)\Renoise\Resources\Scripts\GlobalOscActions.lua’…

Player: Constructing…
Player: Creating the slave threads…
Player: Start running…

GUI: Creating the Document GUI…
GUI: Successfully constructed

Application: A new document was created.

GraphPort: Initializing in WindowedMode
GraphPort: Successfully initialized

Application: Init OK
Application: Enter MainLoop…

ReWire Master: Successfully opened ReWire slave ‘Reason’…

MIDI: Rescanning MIDI devices…
MIDI: Enumerating DirectMusic (WDM) MIDI devices…

MIDI: Skipping emulated WDM device ‘Microsoft MIDI Mapper [Emulated]’
MIDI: Skipping emulated WDM device ‘Microsoft GS Wavetable Synth [Emulated]’
MIDI: Skipping softsynth WDM out-device ‘Microsoft Synthesizer’ (not supported)
MIDI: Enumerating Windows MME MIDI devices…
MIDI: Adding MME out-device ‘Microsoft GS Wavetable Synth’
MIDI: Finished device enumeration

MIDI: Rescanning MIDI devices…
MIDI: Enumerating DirectMusic (WDM) MIDI devices…

MIDI: Skipping emulated WDM device ‘Microsoft MIDI Mapper [Emulated]’
MIDI: Skipping emulated WDM device ‘Microsoft GS Wavetable Synth [Emulated]’
MIDI: Skipping softsynth WDM out-device ‘Microsoft Synthesizer’ (not supported)
MIDI: Enumerating Windows MME MIDI devices…
MIDI: Adding MME out-device ‘Microsoft GS Wavetable Synth’
MIDI: Finished device enumeration
MIDI: Rescanning MIDI devices…
MIDI: Enumerating DirectMusic (WDM) MIDI devices…

MIDI: Skipping emulated WDM device ‘Microsoft MIDI Mapper [Emulated]’
MIDI: Skipping emulated WDM device ‘Microsoft GS Wavetable Synth [Emulated]’
MIDI: Skipping softsynth WDM out-device ‘Microsoft Synthesizer’ (not supported)
MIDI: Enumerating Windows MME MIDI devices…
MIDI: Adding MME out-device ‘Microsoft GS Wavetable Synth’
MIDI: Finished device enumeration

MIDI: Rescanning MIDI devices…
MIDI: Enumerating DirectMusic (WDM) MIDI devices…

MIDI: Skipping emulated WDM device ‘Microsoft MIDI Mapper [Emulated]’
MIDI: Skipping emulated WDM device ‘Microsoft GS Wavetable Synth [Emulated]’
MIDI: Skipping softsynth WDM out-device ‘Microsoft Synthesizer’ (not supported)
MIDI: Enumerating Windows MME MIDI devices…
MIDI: Adding MME out-device ‘Microsoft GS Wavetable Synth’
MIDI: Finished device enumeration

Application: Exit…

Shut down: Stopped the Player

MIDI: Shut down: Closing all acquired MIDI devices…
MIDI: Shutting down DirectMusic…

Shut down: Stopped and released all MIDI-Devices

DirectSound: Stop Polling…
DirectSound: Releasing Primary Sound Device…

Shut down: Stopped and released the active Audio-Device
Shut down: Destroyed the Player
Shut down: Destroyed the Window and all Views
Shut down: Destroyed the Document

GraphPort: Releasing DirectX…

Shut down: Destroyed the GraphPort
Shut down: Saving the Preferences
Shut down: Destroyed the Preferences
Shut down: App is down

Application: Exit OK

ReWire Master: Successfully released ReWire slave ‘Reason’…

Application: Finalizing the API…

Closing log file…

[EDIT] OK, I know why Renoise is not starting as a slave. It’s bacause Reason cannot be a rewire master…

I also tried to run renoise as a slave, but when I’m trying it (I simply open reason and after it, renoise), I get this in the log:

ReWire Slave: ReWire slave engine link (Local Machine) FAILED to install (RegError: 5)
ReWire Slave: ReWire engine link (Current User) is already installed and up to date…
ReWire Slave: ReWire Panel was initialized…
ReWire Slave: ReWire Slave mode failed to init (no master is running)…

ReWire Master: Successfully opened

So looks like renoise doesnt know that reason is already opened…

Did you try loading FL as a VSTI with rewired Reason?

No, I didnt and I would like to avoid such ‘frankenstein’ solutions.

However, I rewired Reason to FL Studio, without the issues I have with Renoise which clearly tells me there is

something wrong with Renoise implementation and not my system, software, etc.

yep exactly same problem here ,

Never had it on windows xp …or on my old laptop .

Thing is , renoise even freezes ( for 10 seconds ) when changing the name of a reason device .

Doesn’t happen when reason is slaved to ableton or reaper .

system lenovo thinpad , dual core 2 . 2 gig ram , shitty vista os .

No renoise disk browser is not open .

The only temp.workaround solution I have now is to create a huge reason template with all the instruments all ready loaded .

Hope this will get fixed

some news on this issue ?

I run everything in 32 bit vista , 32 bit renoise and reason .

Like i said, RENOISE is the only program that is rescanning (way to long ) midi inputs of the rewire slave when new reason instruments are added/deleted or renamed (renaming in reason )

Will we ever see anything about this problem ? I posted it more than 2 months ago, followed by other user having the same issue and nothing… Will it be possible to get dev’s attention for this one ?

Some time ago I made a post about my rewire problems:

http://forum.renoise.com/index.php/topic/43248-rewiring-reason-to-renoise-problem/

other user had pretty much the same issue:

https://forum.renoise.com/t/reason-rewired-to-renoise-scanning-midi-inputs-takes-a-long-time/42650

Both posts are left unanswered for 6 months.
I dont have any experience here on Renoise forums, so maybe I didnt ask the question in the right way or didnt provide enough details.
I really dont understand the point of making Renoise a rewire master if it doesnt work with the most important rewire slave - Reason 8.

Can someone look into it, please ? I hope I won’t be ignored this time.

Sorry for the late reply. I’m a bit unsure what the problem now is. Is it that ReWire with Renoise and Reason does not work at all, or is it about the MIDI rescanning?

That Renoise freezes for some time when adding a new instrument in Reason surely is annoying, but this does not happen constantly, or does it for you?

You can easily recreate it with Reason 8 32 bit demo. I tried it in both Reason 4 and 8 (32 bit).

You add Rewire device in Renoise, select Reason, then in reason, create a synth, switch back to Renoise windows and wait… It freezes for like 20-30 seconds which is very annoying.

If I remember correctly, checking renoise logs, looks like everytime you add a synth in Reason, renoise enumerates all the midi devices. Dunno why it doesnt happen in 64 bit.

It also doesnt happen in 32 bit FL Studio.

I’m also pretty sure it’s not just my system - as I stated in my other post, other user has exactly the same issue.

I only have x64 but I don’t have this issue and midi input/output scan is instant for me with reason changes, however if it doesn’t happen for you in x64 renoise, why aren’t you using it instead? There are only a few reasons why you shouldn’t use 64 instead of 32.

I’m using 32bit as I only own Reason 4. I’m using it for thor and I have no plans to upgrade to 8 yet.

And since both latest Reason and Renoise are still offered in 32 bit versions, that configuration should be supported.

I assure you (in my experience) that the devs takenote of every bug report, but if they have trouble replicating it, they probably put it on their check-out-later-again list. And it still may be an issue on your end. Could you try doing the same with a renoise as the master and some other daw as the slave?

Yes, could not replicate the problem here either. The MIDI rescanning actually is OK and should not be the problem. The problem is the freezing. MIDI gets rescanned by Renoise to add or remove MIDI ports in Renoise to control things in Reason. This usually should take a fraction of a second and only happens when adding/removing instruments in Reason.

Double-check this with Reason 4 on Windows 7 - 32bit.

AstroNut: Are you really really sure it’s not the disk-browser or something else. Does this really !only! happens when running Reason rewired to Renoise?
And does it really only happen after you’ve added/removed instruments in Reason?

Hi, sorry for the late update. I have no idea what happened but I cant replicate it today. I will do some more test and I will let you know.

Hello

I decided to bump this topic as unfortunatelly, I still have a problem.

I understand that it maybe related to my PC only but I would be grateful for any suggestions.

When I start Renoise, it takes actually quite a long time to load, and I think the main reason is that it is scanning for available midi devices - at least thats what I can see when it’s loading.

I think my rewire problems are related to it.

Could you recommend any troubleshooting steps ?

Maybe there is a way of disabling midi scanning ?

Thanks very much for any help.

Can you try removing any mid ports (including hardware)you have on your system and see what’s the result of that,

in fact, maybe there’s a virtual midi port that bugs out the entire thing, I had one of those some time ago (that’s all I remember about it)