v5.26pre3 - September 23 2016

[mustgroove]

v5.26pre3 - September 23 2016
+ MIDI export: fix time selection export of tempo changes and project markers [p=1733871]
+ MIDI: improve importing type 1 MIDI files that contain one track
+ MusicXML: fix import when default MIDI ppq has been customized
+ Undo: preserve selected envelope on undo/redo
# MIDI editor: do not automatically activate filter on "show all channels" action [p=1734098]
# MIDI export: adjust SMPTE offset for project start time

[EvilDragon]

Originally Posted by mustgroove

+ Undo: preserve selected envelope on undo/redo

YAAAAAAAAY!!!!

Originally Posted by mustgroove

# MIDI editor: do not automatically activate filter on "show all channels" action [p=1734098]

Also extremely useful! One annoyance less!

[daxliniere]

Originally Posted by mustgroove

+ Undo: preserve selected envelope on undo/redo

Sorry Justin, but this has broken something else. Check this LICEcap. First added points are using action _BR_ENV_POINT_MOUSE_CURSOR (I use this almost exclusively for inserting points as it's fast and has no minimum distance between points unlike the native action). Second set of added points are via double-clicking on the envelope.
You'll notice 2 problems:

1) Env pts inserted with _BR_ENV_POINT_MOUSE_CURSOR are not undone when undo is pressed.
2) Env pts inserted with _BR_ENV_POINT_MOUSE_CURSOR are incorrectly removed when undoing the points added by double-click.




Regarding the all-important 'responsiveness during undo' I just tested pre3 and it's MUCH better with big projects (thankyou!!!), but still not as fast as when there is no audio interface connected. Even Dummy Audio is slower than no interface. What's happening behind the scenes?

The difference from reducing the thread count by 25% is negligible. Reducing by 75% is more noticeable, but still not as fast as no audio interface.

[Mercado_Negro]

That's very interesting indeed, Dax. I just tried it and effectively it is much faster when Dummy Audio is used. Why is that, Justin? Never thought that could've had something to do with it.

Pre3 is much better as Dax says. I didn't install pre2 so maybe most changes happened between these two pres. This is shaping up nicely, Justin. Thanks for putting some love in it.

[daxliniere]

Originally Posted by Mercado_Negro

I just tried it and effectively it is much faster when Dummy Audio is used.

Hey David, just to clarify, are you saying that Dummy Audio is faster than no interface at all?
That prompted me to do some more tests and this is what I found:

1) switch interface off (REAPER already set to ASIO)
2) load REAPER
3) load project
<undo is lightning fast>
4) switch to Dummy Audio
<undo is lightning fast)
5) Turn on interface and set back to ASIO
<undo is slow*>
6) switch to Dummy Audio
<undo is slow*>


*still much faster than 5.26pre1

[daxliniere]

Originally Posted by daxliniere

6) switch to Dummy Audio
<undo is slow*>

Ahaa! I just noticed something that explains the difference between the outcome of steps 4 and 6, which should be the same.
After step 4, the top right corner shows "audio device closed", but after step 6, it shows "[a bunch of specs] Dummy Audio"

[Mercado_Negro]

Originally Posted by daxliniere

Hey David, just to clarify, are you saying that Dummy Audio is faster than no interface at all?

Yes, exactly.

[daxliniere]

Originally Posted by Mercado_Negro

Yes, exactly.

Ahh, this is not the case for me.
What interface are you using?

[Mercado_Negro]

Originally Posted by daxliniere

Ahh, this is not the case for me.
What interface are you using?

I have a Focusrite LS56 here atm.

[Justin]

Sorry Justin, but this has broken something else. Check this LICEcap. First added points are using action _BR_ENV_POINT_MOUSE_CURSOR (I use this almost exclusively for inserting points as it's fast and has no minimum distance between points unlike the native action). Second set of added points are via double-clicking on the envelope.

99% sure this was caused by the changes in pre1-- confirm that and i'll look at fixing!

[Justin]

Originally Posted by daxliniere

Ahaa! I just noticed something that explains the difference between the outcome of steps 4 and 6, which should be the same.
After step 4, the top right corner shows "audio device closed", but after step 6, it shows "[a bunch of specs] Dummy Audio"

Try disabling prefs/playback/run fx when stopped and it should probably get quite snappy!

I think the main issue is that the FX used in the project are competing with the main UI thread for CPU time...

[Klangfarben]

Originally Posted by mustgroove

# MIDI export: adjust SMPTE offset for project start time

Everything working great here for type 1 when exporting entire project. However, when I export a time selection on OSX 10.9.5 5.26pre3 x64 I'm getting a hanging crash and have to force quit. Can anyone else replicate? Haven't tried on Windows yet but will try next.

Also, if SMPTE offset could be included for type 0 export as well that would be really great.

Thanks so much for the great work.

[Klangfarben]

So, hanging crash on exporting Time Selection Only seems to depend on the selection itself. In the attached RPP, if I make a selection from measures 7-18 and choose Time Selection only and export SMF, Reaper hangs. If I make a selection from measures 2-18 and choose Time Selection only and export SMF, it exports fine. Can't seem to figure out why.

http://s3.amazonaws.com/TLMusic/TJL/...26pre3.RPP.zip

[ELP]

"+ MIDI export: fix time selection export of tempo changes and project markers [p=1733871]"

The bug are the Tempo/Signature marker in between T=0 and the time selection at project timeline together with Time Selection exports.

If in between T=0 and the time selection for export are tempo/sig Marker,
REAPER hang!
Maybe this refers to the fact that REAPER want export,
together with time selection -at the moment-
redundant tempo/sig markers (multi tempo marker|same position within exported file).

This is the bug within the above fix which caused a REAPER hang, Schwa!
[<Provider Name="Application Hang" />
..
<Data>reaper.exe</Data>
<Data>5.2.5.13</Data>
..
]
Marker/Cues works fine without redundant events; Tempo/Sig Marker not.

[Klangfarben]

Originally Posted by ELP

If in between T=0 and the time selection for export are tempo/sig Marker, REAPER hung!

ELP, you are truly a man among men...

[schwa]

Originally Posted by Klangfarben

ELP, you are truly a man among men...

You can never really assume that on the Internet.

Fixing the bug, thanks!

[xpander]

It seems undo doesn't work with Master track tempo envelope points. This changed already in v5.26pre1. After adding few tempo envelope points, clicking undo doesn't seem to do anything until undo has (apparently) cleared every point and the envelope disappears. And the tempo markers will still be visible after this in the marker area above the timeline.

Original report by vanhaze:
http://forum.cockos.com/showthread.php?t=181796

[jmorel33]

So, any research about what I posted on in the final 5.25 release thread?

Reaper did scrap my RPP project and I have to repopulate my tracks in order to work since it's now giving me this super laggy playback in MIDI pianoroll and also that involuntary playback of *all* midi devices again in midi edit.

[Mercado_Negro]

Is it just me or now the master track suddenly floats when you open a new project?

[xpander]

Originally Posted by Mercado_Negro

Is it just me or now the master track suddenly floats when you open a new project?

Haven't noticed that here with new or old projects?

---

Originally Posted by jmorel33

So, any research about what I posted on in the final 5.25 release thread?

Not really a new issue belonging into this pre-thread but rather a separate topic if you'd like to create one. Would also help to know what are you referring to. Probably the following?
http://forum.cockos.com/showthread.p...79#post1732479

Like suggested in there, you have pretty heavy PDC going on in your example project, 45056 samples on Master track. Untick JS:Zero Crossing Maximizer and you'll get much more immediate playback during your edits.

[Mercado_Negro]

Originally Posted by xpander

Haven't noticed that here with new or old projects?

Just fixed it. Edited the .ini. Thanks for checking.

[sinkmusic]

Hi
I hope this is the right place to ask : Would it be possible, in the Region/Marker manager, to add another "lenght" column, in order to display both the lenght in hours/minutes /seconds and in Beat/mesures ?

It seems like a small thing to add, but it can come handy (at the moment, the "lenght" column use the same time unit than the one sest in the timeline).


Thank you

[jmorel33]

Originally Posted by xpander

Haven't noticed that here with new or old projects?

---



Not really a new issue belonging into this pre-thread but rather a separate topic if you'd like to create one. Would also help to know what are you referring to. Probably the following?
http://forum.cockos.com/showthread.p...79#post1732479

Like suggested in there, you have pretty heavy PDC going on in your example project, 45056 samples on Master track. Untick JS:Zero Crossing Maximizer and you'll get much more immediate playback during your edits.

Correct. Removing Zero Crossing Maximizer fixes it! But I've never had to worry about lag in the editor before :/

Thanks a bunch for the tip! PDC to me is still some obscure term, but I'm keeping this one noted. Now the MIDI notes playing everywhere from the EDIT ghappens on that RPP project on the VX90 track. Think there's something I should do about that or it's the project that's got some bad mapping? I haven't tricked the channels around really.

Thanks Xpander!

[jmorel33]

Just noticed the Edit delays when using the piano roll or placing notes is exactly the time that is set in the Zero Crossing Maximizer ! Never had that before from what I can recall. Also this only happens because of the Master Track, I can use Zero Crossing Maximizer on all other tracks and it doesn't delay my edits.

[tack]

Every time I see "undo" at the beginning of a bullet in the change log I get a twinge of excitement that maybe it's fixed undo of step-inputted notes. Some day!

[Justin]

Originally Posted by xpander

It seems undo doesn't work with Master track tempo envelope points. This changed already in v5.26pre1. After adding few tempo envelope points, clicking undo doesn't seem to do anything until undo has (apparently) cleared every point and the envelope disappears. And the tempo markers will still be visible after this in the marker area above the timeline.

Original report by vanhaze:
http://forum.cockos.com/showthread.php?t=181796

Thanks for pointing this out, fixing for pre4

[daxliniere]

Originally Posted by Justin

99% sure this was caused by the changes in pre1-- confirm that and i'll look at fixing!

Yes, 5.25 is perfect, 5.26pre1 shows the problem.

Originally Posted by Justin

Try disabling prefs/playback/run fx when stopped and it should probably get quite snappy!

Oh yeah, 5.25, undo is much faster with this disabled. The difference between on and off with v5.26pre3 is that it's a little bit snappier again.

What kinds of things will this affect? Weird sounds on playstart with some delay plugins, I guess. Anything else?

[Justin]

Originally Posted by daxliniere

Yes, 5.25 is perfect, 5.26pre1 shows the problem.


Oh yeah, 5.25, undo is much faster with this disabled. The difference between on and off with v5.26pre3 is that it's a little bit snappier again.

What kinds of things will this affect? Weird sounds on playstart with some delay plugins, I guess. Anything else?

plugins that produce sound when stopped, and reverb tails, i guess (though for the latter there's an option to run fx for a certain time after stopping). other than that, should be good!

[vanhaze]

Originally Posted by Justin

Thanks for pointing this out, fixing for pre4

Hooray, many thanks Justin !!

[daxliniere]

Originally Posted by Justin

plugins that produce sound when stopped, and reverb tails, i guess (though for the latter there's an option to run fx for a certain time after stopping). other than that, should be good!

Reverb/delay tails are fine, I did see that option (well thought-out, BTW)
No problems with starting and stopping plugins? What exactly is meant by starting/stopping? Obviously they're not unloaded (that would obviously be a session-stopper), but how does it work?

[airon]

After a stop I do get the occasional huge reverb tail as the reverb is fed the parametrer values of where the cursor is placed for the next PLAY.

Valhalla Room, or any other plugin where this might be noticable and the parametrer are automated.

In my case I might start playback just before parameters change, with nothing being fed in to the reverb.

When I stop in the middle of something being fed in to the reverb, those parametrers values from where I started payback magically come in to play.

Perhaps I am missing a setting that prevents that ?

[amagalma]

Sorry for being so late in the game!.. There were some fixes regarding peaks in versions 5.11, 5.15, 5.18, 5.20-5.22

Could something be done with this bug (incosistent peak drawing in various zoom levels when there is an active volume envelope) that has existed forever?

Thank you!