Zebra2 and Receptor
-
- KVRist
- 309 posts since 11 Sep, 2005 from Virginia
Are they any near future plans for Zebra2!?
-
- KVRian
- 1116 posts since 22 Apr, 2005 from Nashville, TN USA
PhilMuller wrote:Are they any near future plans for Zebra2!?
email from Urs dated 1/17/2007 wrote: Roadmap for Receptor compatibility
Yes, we know that some of you are awaiting this - and we ask to be a bit more
patient. We have worked out a nice concept to workaround our problems with
Receptor's Linux underpinnings, but we couldn't make a stable 100% reliable
version of our engine in time before the holidays.
However, we're confident that Triple Cheese, MFM2 and Zebra will be spotted on
Receptors during Musikmesse, that is end of March.
-
- KVRist
- Topic Starter
- 309 posts since 11 Sep, 2005 from Virginia
Tim, It is now the end of April and I haven't heard anything from anybody on Zebra2?Hybernation wrote:PhilMuller wrote:Are they any near future plans for Zebra2!?email from Urs dated 1/17/2007 wrote: Roadmap for Receptor compatibility
Yes, we know that some of you are awaiting this - and we ask to be a bit more
patient. We have worked out a nice concept to workaround our problems with
Receptor's Linux underpinnings, but we couldn't make a stable 100% reliable
version of our engine in time before the holidays.
However, we're confident that Triple Cheese, MFM2 and Zebra will be spotted on
Receptors during Musikmesse, that is end of March.
-
- KVRist
- 120 posts since 21 Jan, 2005
I heard Urs (before Musik Messe)talking about he knows the way to receptorize Zebra 2.1 and hadn't time to develope it due to Frankfurt fair schedule.
Hoping to see Zebra 2 receptorized soon, i'll be watching all related posts and forward them as possible.
Ciao. P
Hoping to see Zebra 2 receptorized soon, i'll be watching all related posts and forward them as possible.
Ciao. P
-
- u-he
- 30192 posts since 8 Aug, 2002 from Berlin
Hi,
I'm testing my Receptor compatibility with Triple Cheese now:
http://www.kvraudio.com/forum/viewtopic.php?t=175716
If that works out, Zebra2 will be Receptorized pretty soon!
Please have a look and check it out!
Thanks,
Urs
I'm testing my Receptor compatibility with Triple Cheese now:
http://www.kvraudio.com/forum/viewtopic.php?t=175716
If that works out, Zebra2 will be Receptorized pretty soon!
Please have a look and check it out!
Thanks,
Urs-
- KVRist
- 120 posts since 21 Jan, 2005
Thanks Urs,
I'm really grateful for your caring away for us/yours customers!
...are you interested in becoming our new City Mayor here in my town by the sea of Rome?
Waiting for good news.
Thanks and have a "good time" working with Receptor related.
PGi
I'm really grateful for your caring away for us/yours customers!
...are you interested in becoming our new City Mayor here in my town by the sea of Rome?
Waiting for good news.
Thanks and have a "good time" working with Receptor related.
PGi
-
- u-he
- 30192 posts since 8 Aug, 2002 from Berlin
-
- KVRist
- Topic Starter
- 309 posts since 11 Sep, 2005 from Virginia
Any more news about the Receptorized version of Zebra2? I love this synth.Urs wrote:So, hehe, does it work?!?
-
- u-he
- 30192 posts since 8 Aug, 2002 from Berlin
Not yet.
Still trying to get my head around why presets don't load while graphics do... it's a bit strange, and not having a Receptor around isn't too helpfull as well
Still trying to get my head around why presets don't load while graphics do... it's a bit strange, and not having a Receptor around isn't too helpfull as well
-
- KVRian
- 524 posts since 25 Aug, 2005
Urs, I'm not sure if this is related - can you create and save a simple preset into the Receptor library? And does it recall OK>
If so, have you dropped the preset lib into the Drop Installers Here folder?
OP=X had/has some similar issues, runs and plays great, but could not find its presets...
If so, have you dropped the preset lib into the Drop Installers Here folder?
OP=X had/has some similar issues, runs and plays great, but could not find its presets...
-
- u-he
- 30192 posts since 8 Aug, 2002 from Berlin
The problem is, I have *no idea* what that obscure "Drop Installers Here folder" is and what it does. Everything would be relatively easy if I knew...thesoundsmith wrote:Urs, I'm not sure if this is related - can you create and save a simple preset into the Receptor library? And does it recall OK>
If so, have you dropped the preset lib into the Drop Installers Here folder?
OP=X had/has some similar issues, runs and plays great, but could not find its presets...
Actually, as far as I am told, .fxp from Triple Cheese load fine from Receptor's interface. But like you mentioned, it doesn't see any presets within its own browser.
Cheers,
Urs-
- KVRian
- 524 posts since 25 Aug, 2005
I don't thnk I can give you a clear answer as to exactly what happpens when you put something in the Drop Installers Here folder, but if yoju search this form, there have been some good explanatory posts.
-
- KVRist
- 197 posts since 23 Jan, 2006 from Ontario, Canada
The manual describes the Drop Installers Here folder as "your gateway to Receptor". It is the place to put system updates, new plugin installers, or folders of banks and patches.
My understanding is that the OS constantly monitors the folder, looking for new things. When they appear, they will be listed as available for installation on the Setup page.
Banks and patches are scanned for the unique VST ID to which they apply, then Receptor organizes them into the appropriate bank folder, and updates it's database of MIDI
bank select and program changes (as discussed in Chapter 14, "Patch Management").
My understanding is that the OS constantly monitors the folder, looking for new things. When they appear, they will be listed as available for installation on the Setup page.
Banks and patches are scanned for the unique VST ID to which they apply, then Receptor organizes them into the appropriate bank folder, and updates it's database of MIDI
bank select and program changes (as discussed in Chapter 14, "Patch Management").
Greg Holmes
Retailer: Acoustic Image, BassLab, Muse Receptor, MIDIjet, Rayzoon Jamstix, and more...
http://www.ghservices.com/
http://www.gregholmes.com/
Retailer: Acoustic Image, BassLab, Muse Receptor, MIDIjet, Rayzoon Jamstix, and more...
http://www.ghservices.com/
http://www.gregholmes.com/
-
- u-he
- 30192 posts since 8 Aug, 2002 from Berlin
Thanks, that makes it a bit more clear to me!gregh1 wrote:The manual describes the Drop Installers Here folder as "your gateway to Receptor". It is the place to put system updates, new plugin installers, or folders of banks and patches.
My understanding is that the OS constantly monitors the folder, looking for new things. When they appear, they will be listed as available for installation on the Setup page.
Banks and patches are scanned for the unique VST ID to which they apply, then Receptor organizes them into the appropriate bank folder, and updates it's database of MIDI
bank select and program changes (as discussed in Chapter 14, "Patch Management").
Do you also know *where* Receptor puts the patches? If I knew the path, I could make my gui look into that location...
Urs-
- KVRian
- 691 posts since 13 May, 2004 from Silicon Valley
Hi Urs,
Receptor manages "Its' own" patches in the "Banks and Patches" folder (top-level). As Greg explained, these are typically organized by product, and bank Name (MIDI bank IDs also show up in the names of these folders). There is also an XML file (under the "Reports" top level folder), and I think that also has the name "Banks and Patches" (not sure). This is a single XML file with a hierarchy of ProductName and Bank/Patch names.
Typically users (and VSTis) do not access these (Banks and Patches) dirs or files, since the Receptor software tries to manage these.
Here is a scenario of how one might "make receptor aware" of a program's patches (fxps/fxbs):
1.) User installs vsti on receptor
2.) User gathers fxps/fxbs and places them in the 'Drop Installers Here' folder
3.) User goes to the System tab and hits install (where the label next to the button should report the total number of fxps/fxbs placed in the installers folder)
4.) Receptor creates entries in the BanksAndPrograms.xml file
5.) Receptor creates folders under the BanksAndPrograms folder, assigns BankIDs for banks
6.)Receptor copies fxps into the folders
(I'm not sure, but I think Receptor might extract fxp info and generate individual fxps from an fxb).
7.) if a user modifies a plug, and saves a patch (via Receptor's save), fxps are also generated and placed under this folder.
This is generally how this works. Hope this helps.
Regards,
Kevin L
Receptor manages "Its' own" patches in the "Banks and Patches" folder (top-level). As Greg explained, these are typically organized by product, and bank Name (MIDI bank IDs also show up in the names of these folders). There is also an XML file (under the "Reports" top level folder), and I think that also has the name "Banks and Patches" (not sure). This is a single XML file with a hierarchy of ProductName and Bank/Patch names.
Typically users (and VSTis) do not access these (Banks and Patches) dirs or files, since the Receptor software tries to manage these.
Here is a scenario of how one might "make receptor aware" of a program's patches (fxps/fxbs):
1.) User installs vsti on receptor
2.) User gathers fxps/fxbs and places them in the 'Drop Installers Here' folder
3.) User goes to the System tab and hits install (where the label next to the button should report the total number of fxps/fxbs placed in the installers folder)
4.) Receptor creates entries in the BanksAndPrograms.xml file
5.) Receptor creates folders under the BanksAndPrograms folder, assigns BankIDs for banks
6.)Receptor copies fxps into the folders
(I'm not sure, but I think Receptor might extract fxp info and generate individual fxps from an fxb).
7.) if a user modifies a plug, and saves a patch (via Receptor's save), fxps are also generated and placed under this folder.
This is generally how this works. Hope this helps.
Regards,
Kevin L