MusicDevelopments

Groundhog #31684 · Post by **Groundhog #31684** » Sat Sep 05, 2015 2:55 pm

Really sorry for the false hope, but I was too fast there... I am having a reproducible crash here with x64 RC and x64 Reaper. It's a cross-thread deadlock in RC which appears to involve any interaction with the RC arrange view or selecting an item in the Scales/Phrases etc windows.

So it works, and plays and you can interact with the transport in local seq mode until you interact with the GUI in the ways described.

Code: Select all

 RapidComposerLE_x64.exe 
   0.0.0.0 
   c74 
   01d0e7e56a6970d9 
   2 
   C:\Program Files\RapidComposer (x64)\RapidComposerLE_x64.exe 
   0a2099f4-53d9-11e5-82bd-1cb72c11905d 
    
    
   430072006F00730073002D00740068007200650061006400000044006500610064006C006F0063006B0000000000 


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 00720043 0073006F 002D0073 00680074 
0010: 00650072 00640061 00440000 00610065 
0020: 006C0064 0063006F 0000006B 0000 


In Bytes

0000: 43 00 72 00 6F 00 73 00   C.r.o.s.
0008: 73 00 2D 00 74 00 68 00   s.-.t.h.
0010: 72 00 65 00 61 00 64 00   r.e.a.d.
0018: 00 00 44 00 65 00 61 00   ..D.e.a.
0020: 64 00 6C 00 6F 00 63 00   d.l.o.c.
0028: 6B 00 00 00 00 00         k.....

I've deleted x86 RC and made sure that the VST/last VST are pointing to x64.

Win 10 x64. If you need me to run or do anything please let me know.

Groundhog #31684 · Post by **Groundhog #31684** » Sun Sep 06, 2015 9:18 am

I have found the cause of the crashes! They only occur when the host tempo is not a whole number. So tempo=110 is fine, tempo=110.1 is not. Good news - I was distracted by it working in an empty project so didn't think of the tempo.

musicdevelopments · Post by **musicdevelopments** » Sun Sep 06, 2015 6:04 pm

Very good observation, and perfect diagnosis! It was a cross-thread deadlock indeed. Fortunately I was able to reproduce it on Win7 and fix it immediately. I also found and fixed another issue. The tempo is stored as a float in RC but as a double in the VST time structure and I did not realize that this could be a problem. A float can store 110.1000 but the VST host provided 110.0999999999 which made the program detect tempo change all the time... Doh!
RC v3.0 will not support Windows XP which means I can use my good old read-write locker class, resulting less (or no) deadlocks.
A v3.0 beta version will be available soon (in about 2 weeks).

Thank you for reporting this issue!!!
Attila

Groundhog #31684 · Post by **Groundhog #31684** » Sun Sep 06, 2015 11:27 pm

No problem, I'm glad my talent/curse of breaking perfectly good things is still alive and kicking! Looking forward to the update!

dbender · Post by **dbender** » Mon Sep 07, 2015 6:03 pm

Will version 3 run on OS X 10.6.8?

Groundhog #31684 · Post by **Groundhog #31684** » Mon Sep 07, 2015 7:26 pm

I just upgraded today and I think I've noticed something that doesn't work as expected - the Default Art(iculation) for tracks doesn't appear to do anything. I can set articulation per phrase and have notes override this with individual articulations, but changing the track setting has no effect - with no articulations on the phrase or notes of course. Am I missing something?

Thanks in advance!

musicdevelopments · Post by **musicdevelopments** » Tue Sep 08, 2015 6:05 am

dbender wrote:Will version 3 run on OS X 10.6.8?

Officially it won't be supported. But the first few 3.x versions will probably run well on 10.6.8 until the development will move to 10.10 from the current 10.7. On 10.10 it is not even possible to build the application for 10.6. I am sure there are hacks to circumvent the situation but I don't want to use those.

Thanks,
Attila

Groundhog #31684 · Post by **Groundhog #31684** » Tue Sep 08, 2015 3:24 pm

I come bearing a gift of a bugissimo.

If you save your project with an RC (VSTi here) track solo'd, it is recalled without that track solo'd, but with the rest of the tracks muted... requiring manual unmuting.

Groundhog #31684 · Post by **Groundhog #31684** » Tue Sep 08, 2015 8:58 pm

Re articulations, the issue with the track setting not affecting/sending out articulations is still there. Hopefully this next issue will shine a light on any articulation gremlins.

I've attached a small RC project file where one of the tracks (Cellos) no longer allows me to change the per-phrase articulation. The only articulation change that works is per note on that track. So that's track + phrase instead of just track that's not working.

Hope this helps, please let me know if you need anything else.

dbender · Post by **dbender** » Wed Sep 09, 2015 6:28 am

musicdevelopments wrote:
dbender wrote:Will version 3 run on OS X 10.6.8?
Officially it won't be supported. But the first few 3.x versions will probably run well on 10.6.8 until the development will move to 10.10 from the current 10.7. On 10.10 it is not even possible to build the application for 10.6. I am sure there are hacks to circumvent the situation but I don't want to use those.

Thanks,
Attila

Thanks, Attila. Good to know I'll be able to use the first few 3.x versions.

When you do move to development on OS 10.10, will Rapid Composer be OS 10.9 compatible?

When I do upgrade from 10.6.8, I plan to go to 10.9, hang on that for a year or so, and then move to El Capitan (10.11). I've heard Yosemite (10.10) has been problematic (especially for audio) but that El Capitan should be more stable (sort of what 10.6 did for 10.5). So I'll skip 10.10 and then go to 10.11 after it has been out for at least close to a year.

Thankns,
David

musicdevelopments · Post by **musicdevelopments** » Wed Sep 09, 2015 3:08 pm

Groundhog #31684 wrote:I just upgraded today and I think I've noticed something that doesn't work as expected - the Default Art(iculation) for tracks doesn't appear to do anything. I can set articulation per phrase and have notes override this with individual articulations, but changing the track setting has no effect - with no articulations on the phrase or notes of course. Am I missing something?

Thanks in advance!

You are right, the default articulation does not do anything. Sorry about that, there will be a fix for that soon.

Thank you for upgrading!
Attila

Groundhog #31684 · Post by **Groundhog #31684** » Wed Sep 09, 2015 6:40 pm

Tee hee, I've done a lot worse myself.

If nothing jumps out at you re the phrase articulation issue I am seeing on a single track in the project I posted above I'll see if I can reproduce it again in a new project.

Glad to upgrade, I hope v3+ is a roaring success!

musicdevelopments · Post by **musicdevelopments** » Wed Sep 09, 2015 7:11 pm

Hi Groundhog,

thank you! I'll check the composition that you uploaded. The track articulation was fixed today. I think only a very few people dare to use the articulations... That is why it may still have issues

Thanks,
Attila

musicdevelopments · Post by **musicdevelopments** » Wed Sep 09, 2015 7:51 pm

dbender wrote: When you do move to development on OS 10.10, will Rapid Composer be OS 10.9 compatible?

Hi David,
Yes, of course it will be compatible with OS X >=10.7 for a long time.

It is beginning to get difficult to do testing on 10.6.8 and a few things worked differently on 10.6, especially with the VST plug-in, with those older DAWs. I am the happiest to retire both my old Mac mini and Windows XP PC.

dbender wrote: When I do upgrade from 10.6.8, I plan to go to 10.9, hang on that for a year or so, and then move to El Capitan (10.11). I've heard Yosemite (10.10) has been problematic (especially for audio) but that El Capitan should be more stable (sort of what 10.6 did for 10.5). So I'll skip 10.10 and then go to 10.11 after it has been out for at least close to a year.

Thankns,
David

Right, this is a good idea.

Thanks,
Attila

dbender · Post by **dbender** » Wed Sep 09, 2015 7:53 pm

Great, thanks Attila!

MusicDevelopments

KVR Audio

Bug reports