MusicDevelopments

musicdevelopments · Post by **musicdevelopments** » Mon Nov 03, 2014 4:20 pm

lulukom wrote:Yes, Attila another unpleasant surprise with the new beta ...
In MAC OSX Yosemite is loaded, but any action with transport ( start/stop /etc ) - Crash !!!
With the Mavericks the same!
But on a MacBook with 10.7.5 Lion works fine!

Hello lulukom,
it seems to work well on OS X Yosemite. I tried the standalone application with both MIDI-only and SF2 tracks. Can you send me more details? Do you mean the VST plug-in crashes? With which host? How can I reproduce it?

Thank you in advance!
Attila

musicdevelopments · Post by **musicdevelopments** » Mon Nov 03, 2014 4:41 pm

Atonal wrote:re: MIDI playback random drop-outs

ver 2.8b4
WIN X/P

--> Loading MIDI files results in occasional note drop-outs when playing back

Dear Atonal,

when you press the PLAY button, does it become yellow or green?
I am asking this strange question because when you have MIDI tracks only (no SF2 or VSTi), a different sequencer is used which may not work as precisely on Windows XP, especially on slower machines.
If that is the case, please add an empty track with a soundfont instrument and see if playback improves (it should).
This is still a beta version, so more testing will be necessary on Windows XP. Probably the timers are very imprecise, so only the old sequencer will be available on XP.

Thanks,
Attila

Atonal · Post by **Atonal** » Mon Nov 03, 2014 9:32 pm

The play button, when pressed, results in yellow .

I only began having this issue a couple of betas ago ...

regards,

-- atonal

Atonal · Post by **Atonal** » Mon Nov 03, 2014 10:34 pm

Also, switching to soundfonts did make a difference. Full and complete playback.

Still, the MIDI needs some attention

-- atonal

lulukom · Post by **lulukom** » Tue Nov 04, 2014 1:26 pm

Hi Attila!
I was wrong, the latest beta works fine with Yosemite !
Those were my problems with adjustment OSX
Sincerely lulukom

musicdevelopments · Post by **musicdevelopments** » Tue Nov 04, 2014 2:38 pm

Hi Atonal,

this behavior on Windows XP is fixed in the next update. Thank you for reporting it!
Please note that using RapidComposer on Windows XP will not be supported for too long.
It does not mean that it won't run on XP - it may, but I had so many issues with XP and since Microsoft stopped supporting Windows XP.... The same with Mac OS X 10.6.8.

Thanks,
Attila

BlackWinny · Post by **BlackWinny** » Tue Nov 04, 2014 5:17 pm

musicdevelopments wrote:Please note that using RapidComposer on Windows XP will not be supported for too long.
It does not mean that it won't run on XP - it may, but I had so many issues with XP and since Microsoft stopped supporting Windows XP.... The same with Mac OS X 10.6.8.

Thanks,
Attila

Hmmm... I think that it is a mention very, very important to add as soon as possible on the purchase page, even before the end of the XP support, so that current XP (and OS X 10.6.8 ) users being potential purchasers can't legally complain when the end of the support occurs in the next weeks.

musicdevelopments · Post by **musicdevelopments** » Tue Nov 04, 2014 6:29 pm

Yes, good point, BlackWinny.
The support will not end in the next few weeks, but with the release of v3.0, probably next summer.
I have checked a few music software, and most of them (e.g. StudioOne, Sonar, Cubase, DP8) support only Windows 7 and 8. Not even Vista.

The problem with XP is not that it is old. Lots of things do not work on it reliably (timers, synchronization) or work differently (e.g. font rendering) and this means lots of trouble and extra time spent.

Attila

BlackWinny · Post by **BlackWinny** » Tue Nov 04, 2014 6:38 pm

musicdevelopments wrote:Yes, good point, BlackWinny.
The support will not end in the next few weeks, but with the release of v3.0, probably next summer.
I have checked a few music software, and most of them (e.g. StudioOne, Sonar, Cubase, DP8) support only Windows 7 and 8. Not even Vista.

The problem with XP is not that it is old. Lots of things do not work on it reliably (timers, synchronization) or work differently (e.g. font rendering) and this means lots of trouble and extra time spent.

Attila

Yes, and it's normal... the most important change was even the memory management which had been totally rewritten for the developments of Windows 7, leading to many issues on the compatibility with the past. There is a trick (the "compatibility mode" in the settings of each executable) but many people don't know it, those who know it don't always know how to use it correctly... and in addition it doesn't assure a guaranty at 100% with the past.

dsan@mail.com · Post by **dsan@mail.com** » Sat Nov 15, 2014 2:41 pm

Hi Attila,
Sorry to report, I just got a crash (reproducable here). Using Beta 2.8b4 x64, VISTA HP Service Pack 2, Intel Core 2 Quad Q9300, 2.5 GHz, 6 GB RAM.

Steps to reproduce:
1.) Open RC (success)
2.) Click to create a new composition (success)
3.) Change Master track key to Em (success)
4.) Select Generate Chords (4) Default Minor Scale Rules (success)
5.) Add Melody Generator (success)
6.) Right click Melody Phrase to open properties dialog (success)
7.) Change Division to 8 beats (fail and)
8.) Crash Dialog

Let me know if I can provide additonal information.

Thanks!

Best regards and Happy Musiking!
dsan

EDIT: Upon further tests it doesn't seem to matter how many beats the phrase gets changed to (step 7 above). It crashes every time the beats are changed. Using "Probilistic Rhythm" algorythm.

BlackWinny · Post by **BlackWinny** » Sat Nov 15, 2014 3:03 pm

Curious, I have tried in VST mode to reproduce exactly the procedure as you described, Denis... and it has not crashed.

You were in standalone executable or in VST mode?

And my system is exactly the same as yours: an Acer Aspire V3 (i5 with 8Gb) with Win7-64bits.

dsan@mail.com · Post by **dsan@mail.com** » Sat Nov 15, 2014 3:12 pm

I should have expressed that part, sorry for the omission - stand alone version.

Thanks for bringing that up BlackWinny

Additionally, I send the MIDI data to a third computer utilizing VEP5 for the instruments.

Note the computer with RC is a VISTA machine. My DAW is on the W7 machine (in my sig) and VEP5 is on a W8 slave unit.

Happy Musiking!
dsan

musicdevelopments · Post by **musicdevelopments** » Sat Nov 15, 2014 3:20 pm

Thank you, dsan and BlackWinny!
I could reproduce this bug, and it is fixed now.

Thank you!!!

Attila

BlackWinny · Post by **BlackWinny** » Sat Nov 15, 2014 3:29 pm

dsan@mail.com wrote:I should have expressed that part, sorry for the omission - stand alone version.

Thanks for bringing that up BlackWinny

Additionally, I send the MIDI data to a third computer utilizing VEP5 for the instruments.

Note the computer with RC is a VISTA machine. My DAW is on the W7 machine (in my sig) and VEP5 is on a W8 slave unit.

Happy Musiking!
dsan

Got it!

Confirmed in standalone.

And another way to crash too:

At the step 6, open the properties of the Master Track, then click "Generate progression from 1.1.00".
And...

dsan@mail.com · Post by **dsan@mail.com** » Sat Nov 15, 2014 3:33 pm

Thank you Attila

Great response as always

Let us know when the revised BETA is ready for us to dl.

Thanks again! You are the best

Happy Musiking!
dsan

MusicDevelopments

KVR Audio

Bug reports