Go Back   Cockos Incorporated Forums > Projects > Deprecated REAPER issue tracker > Closed Issue

Reaper 3.5 doesn't play all midi notes Issue Tools
issueid=2225 03-22-2010 07:17 PM
Human being with feelings
Reaper 3.5 doesn't play all midi notes

if you open this project in Reaper 3.3 all the notes will be heard

the same won't happen in Reaper 3.35

http://forum.cockos.com/attachment.p...1&d=1269310370

this is a very high priority bug fix because my songs don't sound right in newer versions, so i won't be able to upgrade meanwhile.
Issue Details
Issue Type Closed Issue
Project Deprecated REAPER issue tracker
Category MIDI recording and playback
Status Fixed
Priority 1 - Highest
Affected Version 3.35
Closed Version 3.67
Yes votes 0
No votes 0
Assigned Users (none)
Tags (none)

03-22-2010 07:48 PM
Super Moderator (no feelings)
 
- plays correctly in 3.3, breaks in 3.31
- switch the ME to standard mode -> all notes are 100% legato
- select one note -> all notes being played

- recreating the scenario in a new item in 3.36pre doesn't show this behavior

Old item:

HASDATA 1 960 QN
E 0 99 3c 7f
E 480 89 3c 7f
E 0 99 3c 7f
E 480 99 3c 7f
E 480 89 3c 7f
E 0 99 3c 7f
E 480 99 3c 7f
E 480 89 3c 7f
E 0 99 3c 7f
E 480 99 3c 7f
E 480 89 3c 7f
[...]

New item:

HASDATA 1 960 QN
E 0 90 3c 7f
E 480 80 3c 00
E 0 90 3c 7f
E 480 80 3c 00
E 0 90 3c 7f
E 480 80 3c 00
E 0 90 3c 7f
E 480 80 3c 00
E 0 90 3c 7f
E 480 80 3c 00
E 0 90 3c 7f

[...]

Looks like a corrupted item to me.

Edit: Tried to recreate that in 3.3, item turns out ok (like in the example above). That brings up the questions:

- how did you create the item?
- in which Reaper version were the affected projects created?
Reply
03-22-2010 10:03 PM
Human being with feelings
 
Quote:
Originally Posted by Steindork

- how did you create the item?
- in which Reaper version were the affected projects created?
i created it playing in realtime with my midi keyboard, then quantized all midi notes in Reaper's midi editor

the projects were created in Reaper 3.3 and earlier
Reply
03-22-2010 10:34 PM
Super Moderator (no feelings)
 
I see...

... however, I can reproduce the behavior you described with your example project but I can't reproduce a complete bug scenario for now, it looks like it got corrupted somehow at some point. Determining if that's a common bug or something that happened only on your system is quite hard without knowing how it happened in first place. All I can see is:

- creating a 100% legato item in 3.3, the item does not have this problem in later versions

- touching anything in your example item "sorts" it in memory and writes an intact item to the .RPP on save in 3.3 and later versions (which is probably also how you could repair the affected projects)

Besides that, the fact that it plays ok in 3.3. and not in 3.35 might give the devs an idea.
Reply
03-23-2010 05:33 AM
Administrator
 
The old item has various corruptions including double note-on messages that were probably generated by buggy quantizing or humanizing. There have been some bug fixes related to this problem since 3.3, fixes to quantize/humanize that prevent the corruption from happening in the first place, and fixes to playback to ignore double note-ons.

We will add the same corruption-cleaning at load time, which should fix things so corrupted MIDI will get fixed when loaded, rather than (as Steindork pointed out) getting fixed the first time the MIDI item is touched.

I don't know if we'll be able to get this change into the next release, it might need to be the one after. As a workaround, you can touch the items in the latest release to fix them.
Reply
03-23-2010 07:24 AM
Administrator
 
Where is the attached project by the way?
Reply
03-23-2010 12:34 PM
Human being with feelings
 
Quote:
Originally Posted by schwa
Where is the attached project by the way?
i'll make a new one and post here as soon as i can because i'm afraid this happens in projects created in 3.35 as well
Reply
03-24-2010 09:18 AM
Human being with feelings
 
i couldn't make this happen with 3.35. i was wrong (what is is a good thing in this case)

to make the old itens to sound right in 3.35 i tried to requantize them and it worked.

thank you both!
Reply
05-03-2010 08:01 AM
Human being with feelings
 
why is this closed? Reaper 3.51 doesn't play all the notes of the attached project yet.

for some reason the old link is broken, so here it is again:
www.estudionitro.com.br/roger/midi.zip

thanks!
Reply
07-13-2010 12:31 PM
Administrator
 
This issue isn't closed. Automatically correcting overlaps on loading the project causes a whole new set of problems, so we've decided not to do that. Hopefully it does fix your specific MIDI items to run the MIDI editor action "correct overlapping notes."
Reply
07-14-2010 07:48 AM
Human being with feelings
 
yes, it works with this action! a very better way than re-quantize!
thank you :]
Reply
08-10-2010 07:17 PM
Administrator
 
3.67 will have some new behavior, to set the MIDI option "automatically correct overlapping notes" disabled by default when loading a project that was saved prior to version 3.4.
Reply
08-16-2010 02:38 AM
Human being with feelings
 
great, thanks a lot!!
Reply
Reply

Issue Tools
Subscribe to this issue

All times are GMT -7. The time now is 11:15 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.