FJ Lamela
Max Output Level: -90 dBFS
- Total Posts : 11
- Joined: 2015/10/21 05:56:15
- Location: Spain
- Status: offline
The Rapture Pro 2.0.3 new possible bug??
Open The Rapture Pro 2.0.3 instrument in sonar x3.
Load a dimensión pro preset: bass synth /Producer1 preset or Producer2 preset ..etc (legacy or not legacy).
Play some notes ,all is ok.
Save the Project.
Reopen the Project: the sample is not loaded (saw z3a+.flac) and the sound is the default tone.
Can anyone confirm/test this?.
Thanks.
PD:Windows 10 64 bits/Rapture vst3.
The bug is the same in vst2.
|
bmcclure
Max Output Level: -90 dBFS
- Total Posts : 5
- Joined: 2015/05/09 23:54:27
- Status: offline
Re: The Rapture Pro 2.0.3 new possible bug??
2016/01/13 22:39:58
(permalink)
I have what seems to be the exact same problem, but in REAPER instead of Sonar. For a little while after starting to use Rapture Pro, it worked fine for me. But now, no matter what session I am in, any Rapture Pro instance I add always loads with the default sound when I close and re-open the session, even though the UI indicates that the correct preset is active.
|
ChazEd
Max Output Level: -88 dBFS
- Total Posts : 121
- Joined: 2014/12/01 05:17:09
- Status: offline
Re: The Rapture Pro 2.0.3 new possible bug??
2016/01/14 09:08:55
(permalink)
I had the same issue, and found that my projects saved with the VST2 version opens with the default preset with the VST3 version (I recently changed to the VST3 version). Rolled back to the VST2 version, and now everything works fine, so try using the VST2 version. This worked for me. Maybe there's a bug when changing the VST2 to the VST3 version, just like Z3ta+ 2 had. Don't know exactly. Hope this helps! EDIT: oooops, you already said the issue is with both versions, sorry!
post edited by ChazEd - 2016/01/14 09:29:09
Ableton Live 10 Suite x64 Korg Legacy Collection, FXpansion Tremor, Z3ta+ 2 & Rapture Pro Win 10 x64 (Still knocking on wood...) i7 4770, GA-H97-D3H, 16 GB, 7200 1TB + 2TB, RX 580, CX600V2 UA-101 (Thank you, Roland, for the Windows 10 driver!), SM57, MG10/2, MicroKey 37
|
ChazEd
Max Output Level: -88 dBFS
- Total Posts : 121
- Joined: 2014/12/01 05:17:09
- Status: offline
Re: The Rapture Pro 2.0.3 new possible bug??
2016/01/14 10:47:37
(permalink)
Did some more testing and found something weird with Rapture Pro.
Using Producer's 01 Preset (D-Pro Factory Library/Bass Synth), recorded some notes. The sound have some filter envelope applied.
Save and close project & Sonar.
Open Sonar and load same project. Play it.
No filter envelope is heard, only saw with low pass, which means the preset will not sound as it should.
Close and open project again. Go to Element 1, click "CUTOFF 1", "ENV GEN" and just click "VEL->INT" rotary button.
BAM! Filter envelope is working again!
Is that a bug? Can anyone reproduce?
Ableton Live 10 Suite x64 Korg Legacy Collection, FXpansion Tremor, Z3ta+ 2 & Rapture Pro Win 10 x64 (Still knocking on wood...) i7 4770, GA-H97-D3H, 16 GB, 7200 1TB + 2TB, RX 580, CX600V2 UA-101 (Thank you, Roland, for the Windows 10 driver!), SM57, MG10/2, MicroKey 37
|
FJ Lamela
Max Output Level: -90 dBFS
- Total Posts : 11
- Joined: 2015/10/21 05:56:15
- Location: Spain
- Status: offline
Re: The Rapture Pro 2.0.3 new possible bug??
2016/01/14 12:00:15
(permalink)
ChazEd
Did some more testing and found something weird with Rapture Pro.
Using Producer's 01 Preset (D-Pro Factory Library/Bass Synth), recorded some notes. The sound have some filter envelope applied.
Save and close project & Sonar.
Open Sonar and load same project. Play it.
No filter envelope is heard, only saw with low pass, which means the preset will not sound as it should.
Close and open project again. Go to Element 1, click "CUTOFF 1", "ENV GEN" and just click "VEL->INT" rotary button.
BAM! Filter envelope is working again!
Is that a bug? Can anyone reproduce?
This is the origin of this thread ChazEd
I had the same issue, and found that my projects saved with the VST2 version opens with the default preset with the VST3 version (I recently changed to the VST3 version).
Rolled back to the VST2 version, and now everything works fine, so try using the VST2 version.
This worked for me.
Maybe there's a bug when changing the VST2 to the VST3 version, just like Z3ta+ 2 had. Don't know exactly.
Hope this helps!
EDIT: oooops, you already said the issue is with both versions, sorry!
in my case, the bug happened in vst2 and vst3 versions Thanks for your help ¡¡¡¡¡¡Cakewalk !!!!!!! we are waiting your official answer,but for the moment is silence.
post edited by FJ Lamela - 2016/01/14 12:13:32
|
ChazEd
Max Output Level: -88 dBFS
- Total Posts : 121
- Joined: 2014/12/01 05:17:09
- Status: offline
Re: The Rapture Pro 2.0.3 new possible bug??
2016/01/14 12:22:17
(permalink)
I think there's 3 issues here:
1- You said rapture pro don't load the sample(s). If it doesn't load some samples, it will sound different. In my case, Rapture Pro loads samples just fine.
2- I said the envelope generator doesn't remember it's settings (or something like that) when saving and opening a project. Did you test this issue?
3- When I changed to the VST3 version, all my projects saved with VST2 versions didn't remember what sounds/presets I have saved.
Anyway I will open another thread regarding this envelope generator issue & VST3 saved settings.
And other thing: Cakewalk will do nothing if the issue is not reproducible. So if more people chime in, maybe Cakewalk will look at the issue. If not, then we're alone on this.
Ableton Live 10 Suite x64 Korg Legacy Collection, FXpansion Tremor, Z3ta+ 2 & Rapture Pro Win 10 x64 (Still knocking on wood...) i7 4770, GA-H97-D3H, 16 GB, 7200 1TB + 2TB, RX 580, CX600V2 UA-101 (Thank you, Roland, for the Windows 10 driver!), SM57, MG10/2, MicroKey 37
|
ChazEd
Max Output Level: -88 dBFS
- Total Posts : 121
- Joined: 2014/12/01 05:17:09
- Status: offline
Re: The Rapture Pro 2.0.3 new possible bug??
2016/01/14 13:11:35
(permalink)
I did again some more tests and Rapture Pro remembers Rapture Pro presets (tested 3 presets, load samples / env gen just fine), but doesn't remember some D-Pro legacy env gen presets (tested 2 presets: Producer's 1 & 2, Bass Synth).
Well, I'm not going to test every preset, so that's all I can do.
Let's hope more people try to reproduce the issue.
And while I was testing, I recorded some nice bass lines with that problematic but inspiring preset, so thanks for that!
Ableton Live 10 Suite x64 Korg Legacy Collection, FXpansion Tremor, Z3ta+ 2 & Rapture Pro Win 10 x64 (Still knocking on wood...) i7 4770, GA-H97-D3H, 16 GB, 7200 1TB + 2TB, RX 580, CX600V2 UA-101 (Thank you, Roland, for the Windows 10 driver!), SM57, MG10/2, MicroKey 37
|
bmcclure
Max Output Level: -90 dBFS
- Total Posts : 5
- Joined: 2015/05/09 23:54:27
- Status: offline
Re: The Rapture Pro 2.0.3 new possible bug??
2016/01/14 15:13:49
(permalink)
In my case this happens with both the VST2 and VST3 version of the plugin. On a new session, it doesn't matter which version I use, I consistently experience the bug.
|
FJ Lamela
Max Output Level: -90 dBFS
- Total Posts : 11
- Joined: 2015/10/21 05:56:15
- Location: Spain
- Status: offline
Re: The Rapture Pro 2.0.3 new possible bug??
2016/01/15 05:19:25
(permalink)
bmcclure
In my case this happens with both the VST2 and VST3 version of the plugin. On a new session, it doesn't matter which version I use, I consistently experience the bug.
Yes my case is the same,i can reproduce always the bug
|
ChazEd
Max Output Level: -88 dBFS
- Total Posts : 121
- Joined: 2014/12/01 05:17:09
- Status: offline
Re: The Rapture Pro 2.0.3 new possible bug??
2016/01/27 20:38:51
(permalink)
Ableton Live 10 Suite x64 Korg Legacy Collection, FXpansion Tremor, Z3ta+ 2 & Rapture Pro Win 10 x64 (Still knocking on wood...) i7 4770, GA-H97-D3H, 16 GB, 7200 1TB + 2TB, RX 580, CX600V2 UA-101 (Thank you, Roland, for the Windows 10 driver!), SM57, MG10/2, MicroKey 37
|