Just a quick one. My DAW: Cubase 5 (latest update).
During making a project I updated A3.0.1 to A.3.1. Project loads up with no problems, sounds/patches play as originally set, however Albino has lost patch name filepath.
In other words A3.1 loads up the parameters of the patch but it does not refer to the patch file itself. It shows "[-------]" instead of a patch name.
I've tried to "force" Albino to refer to the patch folder via registry. No luck.
Also I can't see all automation parameters. Well I see pan, volume etc but can't find cut off, wet/dry etc.
The last one is that I didn't manage to connect an external audio to A3.
I've followed all necessary steps to do so but routing cahnnel into A3 does not appear.
What I did while installation was that I didn't uninstall 3.0.1 hoping that 3.1 will overwrite it. It didn't happen. So I unistalled both and installed 3.1 once again.
Any suggestions will be greatly appreciated.
Cheers
Mike
Latest News: LinPlug updates Spectral to v1.3
Albino 3.0.1, Albino 3.1 and Cubase 5
-
- KVRAF
- 1676 posts since 17 Dec, 2002 from Yorkshire
-
- KVRian
- 511 posts since 19 Jul, 2008
Are you on a 64bit system and installed both versions of Albino (32bit and 64bit) ? Try reversing the order of installing the updates, since the latter of both will set the presets path.
Re automation: did you choose 'more' from the automation track menu ?
Re external audio: there is no FX-version for Albino available, so you can't route audio into Albino inside Cubase (as far as I know).
Re automation: did you choose 'more' from the automation track menu ?
Re external audio: there is no FX-version for Albino available, so you can't route audio into Albino inside Cubase (as far as I know).
-
- KVRAF
- Topic Starter
- 1676 posts since 17 Dec, 2002 from Yorkshire
"Are you on a 64bit system and installed both versions of Albino (32bit and 64bit) ? Try reversing the order of installing the updates, since the latter of both will set the presets path."
I forgot to matntion the OS. Thanks for picking this. I'm on 32bit XP SP3.
Reversing the install sounds like an idea. Cheers.
"Re automation: did you choose 'more' from the automation track menu ?"
Yes I did. I see only standard automation controls related to the MIDI track.
"Re external audio: there is no FX-version for Albino available, so you can't route audio into Albino inside Cubase (as far as I know)."
There's no FX version of A3 but there is an audio input capability within the plug itself. Refer to the manual p.22. Linplug site also describes how to "achieve" this in other major DAWs but Cubase. By the way ProSound Diversity sound bank provides set of patches based on this feature.
I forgot to matntion the OS. Thanks for picking this. I'm on 32bit XP SP3.
Reversing the install sounds like an idea. Cheers.
"Re automation: did you choose 'more' from the automation track menu ?"
Yes I did. I see only standard automation controls related to the MIDI track.
"Re external audio: there is no FX-version for Albino available, so you can't route audio into Albino inside Cubase (as far as I know)."
There's no FX version of A3 but there is an audio input capability within the plug itself. Refer to the manual p.22. Linplug site also describes how to "achieve" this in other major DAWs but Cubase. By the way ProSound Diversity sound bank provides set of patches based on this feature.
-
- KVRAF
- Topic Starter
- 1676 posts since 17 Dec, 2002 from Yorkshire
Just an update. I've managed to control/automate parameters via ECS. Not a perfect solution per se but defenitely a problem solver.
-
- KVRAF
- Topic Starter
- 1676 posts since 17 Dec, 2002 from Yorkshire
-
Peter from LinPlug Peter from LinPlug https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=24 - KVRian
- 1258 posts since 25 Oct, 2000
The patch name might show ---- if the presets location changed. However, this does not affect accurate playback of the used sound. Regarding Automation we could not reproduce the problem, it seems all pretty perfect.
-
- KVRAF
- Topic Starter
- 1676 posts since 17 Dec, 2002 from Yorkshire
Peter thanks for dropping a line.
"The patch name might show ---- if the presets location changed. "
- Any chance to restablish the path? (As I said previously registry changes don't make the trick) Or it is relatevely depended in physical terms (folder structure) where the dll is and the fxb are located. Funny enough even after fresh install of A3.1 it still does not show the names. And nothing has been changed in terms of files location.
"Regarding Automation we could not reproduce the problem, it seems all pretty perfect."
As far as I can understand that reproducing the problem maight be difficult the point is that I can't access direct automation controls. What I can find in "More" menu (Automation track) is CC controllers. I can't see anything Albino related. I can make a parameter working via ECS but no in a direct way.
Does it sound any clearer?
"The patch name might show ---- if the presets location changed. "
- Any chance to restablish the path? (As I said previously registry changes don't make the trick) Or it is relatevely depended in physical terms (folder structure) where the dll is and the fxb are located. Funny enough even after fresh install of A3.1 it still does not show the names. And nothing has been changed in terms of files location.
"Regarding Automation we could not reproduce the problem, it seems all pretty perfect."
As far as I can understand that reproducing the problem maight be difficult the point is that I can't access direct automation controls. What I can find in "More" menu (Automation track) is CC controllers. I can't see anything Albino related. I can make a parameter working via ECS but no in a direct way.
Does it sound any clearer?
-
Peter from LinPlug Peter from LinPlug https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=24
- KVRian
- 1258 posts since 25 Oct, 2000
About the preset location, i will try to explain it better:
Albino's preset browser shows you the existing, installed presets. That is, everything inside the Albino Banks folder next to the Albino.dll. If you load a song with a preset that was located at a different physical path, then ---- is shown. So when the path to Albino is different to what i was when you made the song, you see ----. To "repair" this the path to the lib should be the same as when you made the song (but usually one has a reason to have a new location so I think this is no option).
About automation, I get this when I insert Albino in a Cubase track, two automations, the lower one is for Albinos parameters.
Albino's preset browser shows you the existing, installed presets. That is, everything inside the Albino Banks folder next to the Albino.dll. If you load a song with a preset that was located at a different physical path, then ---- is shown. So when the path to Albino is different to what i was when you made the song, you see ----. To "repair" this the path to the lib should be the same as when you made the song (but usually one has a reason to have a new location so I think this is no option).
About automation, I get this when I insert Albino in a Cubase track, two automations, the lower one is for Albinos parameters.
-
- KVRAF
- Topic Starter
- 1676 posts since 17 Dec, 2002 from Yorkshire
Hi Peter. Thanks for confirming how patches work. The scenario you describe assumes that the plugin itself is not changed I guess. And it makes sense. In my case I only reinstalled the plugin. I haven't changed sound banks location/s. Ok there's no point to dig it any further 
Thanks for the screenshot. It shows exectly what I was expecting. But unfortunately it does not. Hence this post. Any ideas why it does note appear?
Thanks for the screenshot. It shows exectly what I was expecting. But unfortunately it does not. Hence this post. Any ideas why it does note appear?
-
Peter from LinPlug Peter from LinPlug https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=24
- KVRian
- 1258 posts since 25 Oct, 2000
No idea. In theory thats impossible 
No seriously, I have not the slightest clue, its such a basic function, if not Cubase for some reason suppresses this (I'm no Cubase expert) ... sorry
No seriously, I have not the slightest clue, its such a basic function, if not Cubase for some reason suppresses this (I'm no Cubase expert) ... sorry-
- KVRAF
- Topic Starter
- 1676 posts since 17 Dec, 2002 from Yorkshire
no probs mate. i'm sure it will work at some point
Basically I did all that update thing because I wanted to run an exteranl audio through A3 (couldn't do it in A3.0.1 so thought 3.1 will help). On your website you show how to do it in other DAWs. I can't make it C5 despite I understand the idea how to connect it. Any ideas on that one?
Basically I did all that update thing because I wanted to run an exteranl audio through A3 (couldn't do it in A3.0.1 so thought 3.1 will help). On your website you show how to do it in other DAWs. I can't make it C5 despite I understand the idea how to connect it. Any ideas on that one?
-
Peter from LinPlug Peter from LinPlug https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=24
- KVRian
- 1258 posts since 25 Oct, 2000
Thats the bad joke, its not possible in DAW's of the inventor of VST, all Steinberg hosts do not support it ... dont ask me why. The only workaround for us would be to make an "effect" (opposed to make a instrument plugin).
-
- KVRAF
- Topic Starter
- 1676 posts since 17 Dec, 2002 from Yorkshire
Peter I do appreciate what you say. But this is exactly the reason I have started this thread. Anyway, I will try reinstalling the thing again. At some point I'm sure I will have to reinstall the OS so there's still a chance
Anyway thanks for trying to help me. Do you think it would be worth asking Steiny about that?
Anyway thanks for trying to help me. Do you think it would be worth asking Steiny about that?