Bug reports

Official support for: musicdevelopments.com
Post Reply New Topic
RELATED
PRODUCTS Fyler RapidComposer

Post

Hello BlackWinny,

I will investigate this in the following days. I wonder if I can reproduce it with Reaper, or it happens with MuLab only.

Thanks,
Attila
Top

Post

musicdevelopments wrote:Hello BlackWinny,

I will investigate this in the following days. I wonder if I can reproduce it with Reaper, or it happens with MuLab only.

Thanks,
Attila
I'm going to try too. For the moment I have tried only in Mulab, this one being my go-to DAW. I'm going to try with Reaper too.
:)
Build your life everyday as if you would live for a thousand years. Marvel at the Life everyday as if you would die tomorrow.
I'm now severely diseased since September 2018.
Top

Post

Hem... Reaper 4.71 (32-bit) doesn't find the new RapidComposer 2.7 (32-bit) within the VST's.

And what looks strange is that it doesn't want either to import it by a simple drag-drop of the dll.
Image
Build your life everyday as if you would live for a thousand years. Marvel at the Life everyday as if you would die tomorrow.
I'm now severely diseased since September 2018.
Top

Post

And I've just reinstalled the 2.7b9 in replacement of the 2.7 released... I'm going to see if it disappears again in Reaper...

EDIT: not even! Reaper 4.71 still crashes at the scan of the VSTs when it arrives at RapidComposer 2.7b9.
Last edited by BlackWinny on Tue Aug 12, 2014 9:31 pm, edited 2 times in total.
Build your life everyday as if you would live for a thousand years. Marvel at the Life everyday as if you would die tomorrow.
I'm now severely diseased since September 2018.
Top

Post

Hum...

DAW used: Reaper 4.71 (the current version available) in 32-bit.

I install the old RapidComposer 2.6 released version (from April) in 32-bit.

I launch Reaper and do a "Clear Cache / Rescan" of the VSTs.

Result: RapidComposer is correctly added. And i can effectively see it in the list of the VSTs.

I close Reaper.

I install the new RapidComposer 2.7 released version (from today) in 32-bit.

I launch Reaper and do a "Clear Cache / Rescan" of the VSTs.

Result: Reaper crashes.

I relaunch Repear. It opens.

I can see that RapidComposer is anymore in the list of VSTs. Curious...

I do a new "Clear Cache / Rescan" of the VSTs. Reaper crashes once again at the moment when it finds RapidComposer (I recall: at this step I am now with the new 2.7 of today).
Build your life everyday as if you would live for a thousand years. Marvel at the Life everyday as if you would die tomorrow.
I'm now severely diseased since September 2018.
Top

Post

Having kept all (I think) the beta versions of the 2.7, I'm going to come back in the time little by little to try to detect starting at which beta version the problem began.
Build your life everyday as if you would live for a thousand years. Marvel at the Life everyday as if you would die tomorrow.
I'm now severely diseased since September 2018.
Top

Post

Is 2.7 release today identical to RapidComposer2.7b9-x64 beta?

What is latest beta name/version number?
Top

Post

Here are the results of my tests:


DAW used: Reaper 4.71 (the current version available) in 32-bit.

Procedure:
    1. I install the old RapidComposer 2.6 released version (from April) in 32-bit.
    2. I launch Reaper and do a "Clear Cache / Rescan" of the VSTs.
    3. Result: RapidComposer 2.6 is correctly added. And i can effectively see it in the list of the VSTs.
    4. I close Reaper.
    1. I install the old RapidComposer 2.7b1 in 32-bit.
    2. I launch Reaper and do a "Clear Cache / Rescan" of the VSTs.
    3. Result: RapidComposer 2.7b1 is correctly added. And i can effectively see it in the list of the VSTs.
    4. I close Reaper.
    1. I install the old RapidComposer 2.7b2 in 32-bit.
    2. I launch Reaper and do a "Clear Cache / Rescan" of the VSTs.
    3. Result: RapidComposer 2.7b2 is correctly added. And i can effectively see it in the list of the VSTs.
    4. I close Reaper.
    1. I install the old RapidComposer 2.7b3 in 32-bit.
    2. I launch Reaper and do a "Clear Cache / Rescan" of the VSTs.
    3. Result: RapidComposer 2.7b3 is correctly added. And i can effectively see it in the list of the VSTs.
    4. I close Reaper.
    1. I install the old RapidComposer 2.7b4 in 32-bit.
    2. I launch Reaper and do a "Clear Cache / Rescan" of the VSTs.
    3. Result: RapidComposer 2.7b4 is correctly added. And i can effectively see it in the list of the VSTs.
    4. I close Reaper.
    1. I install the old RapidComposer 2.7b5 in 32-bit.
    2. Result: Reaper crashes.
    3. I relaunch Repear. It opens.
    4. I can see that RapidComposer isn't anymore in the list of VSTs.
    5. I do a new "Clear Cache / Rescan" of the VSTs. Reaper crashes once again at the moment when it finds RapidComposer (I recall: at this step I am now with the 2.7b5).
    6. I reinstall the old RapidComposer 2.7b4 in 32-bit.
    7. I launch Reaper and do a "Clear Cache / Rescan" of the VSTs.
    8. Result: RapidComposer 2.7b4 is correctly added. And i can effectively see it in the list of the VSTs.
    9. I close Reaper.
    1. I install the old RapidComposer 2.7b6 in 32-bit.
    2. Result: Reaper crashes.
    3. I relaunch Repear. It opens.
    4. I can see that RapidComposer isn't anymore in the list of VSTs.
    5. I do a new "Clear Cache / Rescan" of the VSTs. Reaper crashes once again at the moment when it finds RapidComposer (I recall: at this step I am now with the 2.7b6).
    6. I reinstall the old RapidComposer 2.7b4 in 32-bit.
    7. I launch Reaper and do a "Clear Cache / Rescan" of the VSTs.
    8. Result: RapidComposer 2.7b4 is correctly added. And i can effectively see it in the list of the VSTs.
    9. I close Reaper.
    1. I install the old RapidComposer 2.7b7 in 32-bit.
    2. I launch Reaper and do a "Clear Cache / Rescan" of the VSTs.
    3. Result: RapidComposer 2.7b7 is correctly added. And i can effectively see it in the list of the VSTs.
    4. I close Reaper.
    1. I install the old RapidComposer 2.7b8 in 32-bit.
    2. I launch Reaper and do a "Clear Cache / Rescan" of the VSTs.
    3. Result: RapidComposer 2.7b8 is correctly added. And i can effectively see it in the list of the VSTs.
    4. I close Reaper.
    1. I install the old RapidComposer 2.7b9 in 32-bit.
    2. Result: Reaper crashes.
    3. I relaunch Repear. It opens.
    4. I can see that RapidComposer isn't anymore in the list of VSTs.
    5. I do a new "Clear Cache / Rescan" of the VSTs. Reaper crashes once again at the moment when it finds RapidComposer (I recall: at this step I am now with the 2.7b9).
    6. I reinstall the old RapidComposer 2.7b8 in 32-bit.
    7. I launch Reaper and do a "Clear Cache / Rescan" of the VSTs.
    8. Result: RapidComposer 2.7b8 is correctly added. And i can effectively see it in the list of the VSTs.
    9. I close Reaper.
    1. I install the new RapidComposer 2.7 released version (from today) in 32-bit.
    2. Result: Reaper crashes.
    3. I relaunch Repear. It opens.
    4. I can see that RapidComposer is anymore in the list of VSTs.
    5. I do a new "Clear Cache / Rescan" of the VSTs. Reaper crashes once again at the moment when it finds RapidComposer (I recall: at this step I am now with the new 2.7 of today).
    6. I reinstall the old RapidComposer 2.7b8 in 32-bit.
    7. I launch Reaper and do a "Clear Cache / Rescan" of the VSTs.
    8. Result: RapidComposer 2.7b8 is correctly added. And i can effectively see it in the list of the VSTs.
    9. I close Reaper.
Conclusions:
  1. Version 2.6: OK
  2. Version 2.7b1: OK
  3. Version 2.7b2: OK
  4. Version 2.7b3: OK
  5. Version 2.7b4: OK
  6. Version 2.7b5: Crash
  7. Back to version 2.7b4: OK
  8. Version 2.7b6: Crash
  9. Back to version 2.7b4: OK
  10. Version 2.7b7: OK
  11. Version 2.7b8: OK
  12. Version 2.7b9: Crash
  13. Back to version 2.7b8: OK
  14. Version 2.7 released: Crash
  15. Back to version 2.7b8: OK
Last edited by BlackWinny on Mon Aug 11, 2014 10:13 pm, edited 6 times in total.
Build your life everyday as if you would live for a thousand years. Marvel at the Life everyday as if you would die tomorrow.
I'm now severely diseased since September 2018.
Top

Post

Musical Gym wrote:Is 2.7 release today identical to RapidComposer2.7b9-x64 beta?

What is latest beta name/version number?
The latest beta number was 2.7b9.

And the latest beta number to install correctly in the current Reaper 4.71 32-bit was 2.7b8.
Build your life everyday as if you would live for a thousand years. Marvel at the Life everyday as if you would die tomorrow.
I'm now severely diseased since September 2018.
Top

Post

thanks
Is 2.7b9 the same as 2.7 that was released today?
Top

Post

Musical Gym wrote:thanks
Is 2.7b9 the same as 2.7 that was released today?
Only Attila can answer this second question. Some internal changes can have been made between the 2.7b9 and the 2.7 publicly released, only the person having the source code will be able to say if a line of C++ code has been modified between the two compilations.
:D
He will tell us.
Build your life everyday as if you would live for a thousand years. Marvel at the Life everyday as if you would die tomorrow.
I'm now severely diseased since September 2018.
Top

Post

ok, thanks
Top

Post

Musical Gym wrote:thanks
Is 2.7b9 the same as 2.7 that was released today?
Yes, there were no changes between 2.7b9 and 2.7.
Top

Post

BlackWinny wrote:Here are the results of my tests:
Amazing, BlackWinny, this was a huge help, thank you!!! :tu:

There is no software release without issues :(

I am investigating the problem with the VST plug-in.
Top

Post

Thanks for information on release compared to beta.

Does RC have guitar/bass articulations capability, or is it planned?

Slide up, slide down, hammer-on, pull-off, string bend, etc.?

This also could be achieved using the Kontakt/vst/other instrument, so it may not really be necessary. Just curious about it..
Top
Post Reply

Return to “MusicDevelopments”