SWS changes the way my CC lanes are shown (also crashes one project)

[Jeff0S]

From mario.kr...@gmail.com on November 13, 2011 04:31:41

What steps will reproduce the problem? Open the MIDI item on track #2 of this project: http://min.us/m81sFXFPh MIDI editor will try to open and then crash Reaper. Why? Because it seems to want to show ALL CC lanes that have any data within them! This is not the desired behavior at all. It looks like this in a non-crash situation: http://img714.imageshack.us/img714/4760/unusable.png That is definitely unusable. The thing is, if I uninstall SWS, I don't get this behavior at all, I get all the CC lanes remembered correctly for each item as they were. Nobody tries to open all the CC lanes that have some data in them, and crash my project! Serious issue for me... Please look into it! What is the expected output? What do you see instead? I expect not to see so many CC lanes around, please! And definitely no crashes :)

What version of SWS extension are you using? (Extensions -> About SWS...)

v2.1.0 #1 What is your Reaper version number and CPU architecture (e.g. Reaper 3.75 x64)? R4 .11rc4, x86 What operating system are you running? (e.g. Windows XP/7, OSX 10.5.8 etc, 64bit?) Windows XP x86

Original issue: http://code.google.com/p/sws-extension/issues/detail?id=410

[Jeff0S]

From swstim on November 12, 2011 19:37:45

Mario,
First try the latest beta version of SWS 2.1 #17. (In the downloads section.)

[Jeff0S]

From mario.kr...@gmail.com on November 12, 2011 19:42:21

Tried it right after typing up the bug report, at first it acted the same way over here... Then after a few crashes, I tried first opening up other MIDI items in the same project, they opened just fine. Then I decreased the number of CC lanes to acceptable level for each. Then it seemed to open the item on track #2 (which has the most data, actually) without a crash.

It still opens the item a lot slower than I would wish it to be. It must be blinking fast. Currently it takes a few seconds, which is, to me, unacceptable...

I didn't visit this tracker in quite a while, so please excuse me if I wrote about something that's already in here... it's 4 AM over here and I'm pretty beaten and just irked because of this issue. Sorry!

[Jeff0S]

From mario.kr...@gmail.com on November 12, 2011 19:46:13

And here's another annoying behavior - even if I remove the offending CC lanes, upon closing the MIDI item, then reopening it back again, all those lanes are BACK again... Seriously irritating... I'm not sure why this happens at all?

[Jeff0S]

From fingersmcgarnickle on November 13, 2011 02:11:01

I am guessing you have a custom action which runs the action: FNG: Show only used CC lanes after loading the MIDI editor. So if you remove that action from your double click mouse modifier your takes will load quicker. The action was never meant to be used on each load of the MIDI editor as the action will be slow for MIDI takes with a lot of events.

I think I have fixed the crash, which I will submit soon, but fixing the slowness would require a lot more work...

Owner: fingersmcgarnickle

[Jeff0S]

From mario.kr...@gmail.com on November 13, 2011 02:15:24

Wow, Fingers, that's it!

I can't believe that I FORGOT that I set that action up as a mouse modifier! Sorry for bothering, this is user error textbook example! :D

Thanks for fixing the crash anyways! I presume the crash occurs because too many CC lanes open, and overflow happens somewhere when trying to position them in the MIDI editor?

[Jeff0S]

From fingersmcgarnickle on November 13, 2011 02:19:38

Hey Mario, sorry for the crash, which I have fixed now. It is much quicker in the current beta as I sped up the action somewhat. It is still slow on my PC for your second MIDI item.

[Jeff0S]

From mario.kr...@gmail.com on November 13, 2011 02:27:06

It's ok, I'm more like frustrated that I couldn't remember that it was my own Reaper modification turning against me :D :D :D

[Jeff0S]

From fingersmcgarnickle on November 13, 2011 15:22:23

Status: Fixed