I understand your point on the feature request form, as well.  
 
I guess it depends on the 'read' of the post.  I didn't take it as an insulting comment (and I've been married twice, so I think I have some credibility on being insulted - I am also a programmer).  I read that comment purely as a casual speculation on the possibility of what may have led to a coding issue, were there to in fact be one.  
 
There have been actual cases where multi-million dollar satellites have failed, because one set of the international team did things in American standards, and another set did things in metric.  They were quite bummed about it, since they discovered it when the satellite had already launched and become completely unusable.  And another satellite was lost when somebody forgot to tighten the bolts that secured the satellite to a mounting station, and the 3-foot drop destroyed it. There's even a bridge in Chicago where they started both sides to meet in the middle of the river, and they were a couple of FEET off, so the bridge didn't line up when the two sides met.  DOH!
 
I think a lot of folks in general are a bit bristly these days, as carryover from some pretty trashy/bashy posts of late, and I think anything we can collectively do to keep things supportive and positive is in our collective best interests.
 
I am not even sure Audio Snap will meet the original poster's needs - I just happened to have recently used it for a similar kind of thing, so I tossed it out there for something he could try.
 
We may be a mess, but we're family! :)
 
Bob Bone
 

The Therac 25 was a popular example when I was going through intro programming classes.

Yupper Duppers.  LOTS of examples of 'C' students creating things in the world.  :)
 
Bob Bone
 

You can speed up or slow down the complete mix with this free utility:  http://bestpractice.sourceforge.net/  I've used it on several occasions, works fine for me.

scook
Sure it is possible but it does not rise to the level of insulting the programing/testing staff. It may be how the feature was originally specified and the tool was not intended for the application being discussed. That is why I mentioned the feature request form. Audiosnap may be the more appropriate tool in this case.

Are you sure you weren't the programmer in question scook? 
 
Programmers make careless mistakes quite frequently. It's hardly unreasonable to speculate that this may have been the case. Nor is it unreasonable, by extension, to speculate about what may or may not have been in the specifications. If the design included functionality to shorten or lengthen audio by a percentage amount, what would be a possible justification for restricting that calculation to an int? It wouldn't make any sense at all in the context of a program one of whose primary functions is stretching the time of audio. 

No, that is more pointless speculation on your part.

scook
No, that is more pointless speculation on your part.

No it's not. It's perfectly reasonable speculation. A person is perfectly entitled to speculate. It's just part of daily life. 

The reason audiosnap may be helpful is it should keep the midi and audio lined up. This is one of the easier features of audiosnap so the learning curve is minimal. The longest part is bouncing. On my computer which is a little old, it takes quiet a while.

Probably save project as a different name in case something goes wrong. And bounce to new tracks when done so you can get back to original tracks if you need to.

@WDI, Good plan - nice profile pic - who does your hair?  :)
 
To others: For the second time now, can we PLEASE stop the negative posts?  Maybe for the weekend?  
 
Bob Bone
 
 
 

I've had the same challenge many times.  I simply finish the project at the original tempo (85 in this case), then speed up the stereo mix to the desired tempo using Time/Pitch Stretch.  Works for me.