A while back there was a bit of talk about an issue with exporting midi files from reason into sonar due to Reason's higher ppqn or something similar... was there ever a fix? I am trying to export several files into Sonar and they are playing back not quite right... I'm hoping I don't have to replay all of this stuff....Thanks for any help...

there are a couple of things you should check out.  first thing, obviously, is that the tempo in sonar is the same as in reason.  next thing would be checking the regroove mixer to see if there is anything going on there.  you can do this in the control area or by pressing fn8 and selecting the regroove tab.  if you do have regroove settings you need to commit them to the clip before you export midi.  this one is pretty common.  the last thing you should do to check is rewire reason into sonar, mute all the midi clips in the reason project, import the midi into sonar and assign the midi tracks output to the corresponding instruments in reason.  that should help narrow down what's going on.  
what version of reason are you using?

Swamp, 
 
thanks for your reply I'm using Reason 7 as well... I'm referring to the large difference that was mentioned a while back in relation to the ppqn as reason's is extremely different. The issues with re-groove doesn't really apply as I'm talking about simple lines from synth and chord progressions no quantise or anything... I will try the rewire thing but it seems that this was never solved as I see the highest you can set the tpqn or whatever it's called isn't even close to what reason's is.... 
 
Thanks again, 

the reason manual has some info on this - from pg 117:
"About subticks in the Song Position display
When editing notes and automation events in the sequencer you have a resolution of 240 ticks per 1/16th note,
which allows for very accurate positioning. But for the Song Position Pointer, the internal resolution is even higher
(15360 ppq) which means that the position can end up on a fraction of a tick, a so called subtick.
If the Song Position Pointer value is on a fraction of a tick, this is displayed with an asterisk (*) in the Tick section of
the Song Position display."
pg120:
"About subticks in the Position and Length displays
When editing notes and automation events in the sequencer you have a resolution of 960 ppq (240 ticks per 1/16th
note), which allows for very accurate positioning. But when you record , the internal resolution is even higher (15360
ppq) which means that notes and automation events can end up on a fraction of a tick, a so called subtick.
If the value is a fraction of a tick, this is displayed with an asterisk (*) in the Tick section of the Position or Length display."
 
That made me wonder what reason exports at 960 or 15360, so I exported a reason file as midi and looked at the file header with a hex utility and sure enough it exports at the higher resolution.  d'oh.  i'm wondering if you could quantize to 64th notes in reason and then export?

hey frank, 
 
i've been mulling this one over and have a couple of options for you...
the first is to quantize the reason tracks to 128th or 256th notes.  this is a bit hard to do the first time but here's the gist of it.
create an instrument track and set snap to 64th notes and draw one 64th note to the track.   the header should now show position, length, note and vel.  in length it should read 0.0.0.60.  change that to 0.0.0.30 for 128th notes or 0.0.0.15 for 256th notes.  turn snap off.  select the note and copy ctrl+c and paste ctrl+v for one full bar.  close the prv.  right-click the new clip and select "get groove from clip".  this loads the pattern into regroove.  select all your tracks with recordings and select groove a1 from the regroove selector. this will quantize to 128th or 256th notes. you then have to click the groove selector and choose commit to groove.  this will save the quantize.  export the file as midi and import to sonar.  
the other solution would be to get a midi loopback device like tobias erichsen's loopmidi.  set up virtual loopback ports equal to your reason tracks.  launch sonar and enable the virtual midi inputs.  rewire reason into sonar and set up  an equal number of external midi instruments for each loopback port.  copy each midi track to a different external midi instrument.  
in sonar, you would create midi tracks with inputs from the corresponding loopback port.  
i'm sure it sounds pretty complicated, but it's easy to do when you've done it a couple of times. 
the advantage of the quantize method is you can save those grooves for future reference and use. 
 
i'd like to know if that helps at all!  love sonar, love reason!  good fun!

Well, this appears a bit odd. I may think that even though Reason processes midi data at a higher resolution for its 'better engine' performance. It should have an option to export midi which adheres to the General Midi protocol.  If it is audio, then that too should be to the standard wav formula.

Audio does export very well. With reason 7+ you can slice audio and export as rex files. I think there should be an option to export midi at a lower ppqn but it's not available. One could also make the case that sonar should be able to import midi files higher than 960 ppqn.