|
|
|
01-10-2011 05:03 AM | |||
|
|||
Discussion thread:
http://forum.cockos.com/showthread.php?t=72220 |
02-07-2011 10:00 AM | |||
|
|||
This problem applies to both vers. 3 and vers. 4 alpha. I know the devs. have tried to fix it earlier on, but as it seems with no luck :-)....
|
02-07-2011 10:21 AM | ||
|
||
Same for me - all the way to Raper4alpha38.
Mac OSX 10.6.6 with M-Audio Fastrack Pro but I had same problem with previous Yamaha UX96 midi interface. |
02-08-2011 04:24 AM | |||
|
|||
Happened to me too some time ago (3.x & 4alpha). [edit]Win XP 32[/edit]. You have re-define your MIDI setup each time you start REAPER.
I fixed it this way: - Quit REAPER - Delete "reaper-midihw.ini" - Start REAPER and (re-)define your MIDI setup (i.e. enabled IOs, controls IOs, aliases) once for all - Quit REPAER (a new file will be created, this one will be ok) Remark: i think it's due to a conflict between 3.x and v4alpha. I reported several issues like that in the v4alpha bug thread. It definitly occurs in 3.x if you didn't do a v4 *portable* install or if you remove your v4 portable reaper.ini file (=> v3.x get corrupted) |
02-08-2011 04:52 AM | ||
|
||
It happens here, on XP64 - didn't get it with XP32, but then again I didn't have R4 Alpha on that install either. I thought it was an XP64 thing.
Interestingly, it only loses my Axiom ports, which are connected via USB. It doesn't lose my FF400 (firewire, obviously) ports OR my Alphatrack, which is also USB. One of the difference(s) between the Alphatrack and Axiom is that the Alphatrack has drivers, whereas the Axiom is Plug n Play. Dunno if that has anything to do with anything, but it's worth mentioning. |
02-09-2011 03:48 AM | ||
|
||
Newbie here. Win7 32bit AOK. On x64 'cannot open the midi port' message appears when using Mackie Control and HUI and hitting 'play'. Same result on both Midisport 4x4 and RME Hammerfall. Other controls seem OK.
x64 Reaper flys. |
03-04-2011 02:34 AM | ||
|
||
Hey guys, I had the same issue when trying to use rtpMIDI as a MIDI interface in REAPER for control via the AC-7 app from an iPod Touch.
I found in a post somewhere that if you're using a control surface then the MIDI interface(s) you set under Control Surfaces must be not be enabled in the MIDI devices section. It seems that the control surface needs to have complete access to the device and when Reaper tries to open a connection to the MIDI interface it can't. Sucks if you a control surface and and other midi device on the same midi interface. It didn't matter to me because I was using a virtual MIDI interface set up just for the controller. Is having a control surface configured the common thread here? |
05-13-2011 01:13 AM | |||
|
|||
update: it is 100% fixed in v4, we are just waiting for them to follow through on the v3 fix:
see here: http://forum.cockos.com/showpost.php...7&postcount=15 |
01-04-2012 10:11 AM | ||
|
||
*edit* Solved. Now on I'll read the whole thread before posting...
|
05-03-2012 08:33 PM | |||
|
|||
Windows XP sp3 M-Audio Oxygen 49 Reaper 4
Always get the error Have to keep the Keyboards' Power off Once Reaper is running I power up the Oxygen go to the preferences midi devices double click the Oxygen then hit apply It then shows up ready to work! |
05-04-2012 07:27 AM | |||
|
|||
Sorry for the trouble! Please post bugs/help requests in the appropriate forums first, not here in the issue tracker (a database for confirmed REAPER bugs). If you still have the issue (which may be completely different from this actually fixed ticket), can you repost this in the forums for further investigation, please? Thanks!
|
Issue Tools |
---|
Subscribe to this issue |