![d16 phoscyon vs abl2 d16 phoscyon vs abl2](https://www.pluginboutique.com/system/resources/srcs/000/000/010/main/phoscyon-gui-original.jpg)
all other RE's seem like purpose programmed RE's so far imo. Alot of devs won't be interested in spending time making a special RE version.īesides KHS one and the korg stuff, bitspeek. Theo.M wrote:Ochen, they are talking about just taking a plugin and making an identical RE, 1:1, when they discuss limitations. Some of those limitations are intentional because they have big upsides like stability and portability. But those limitations aren't nearly as restrictive as many developers seem to believe (or seem to perpetuate as an excuse for not considering the platform.) Some of those limitations are simply because the RE SDK is still young in its development and haven't been addressed yet. The UI format in the RE SDK absolutely has limitations. They could probably just shrink everything down by 4% without losing any usability or legibility. And even that might not need to actually be changed. Phoscyon is 785px wide. That's just how they laid out the UI to begin with. If D16 is saying that the layout might have to be changed because REs have to be a certain width and height, that might be true, but that's not a limitation of the SDK. They even have the 3D models to work from. There's nothing in the Phoscyon UI that couldn't have been done in SDK1. I love how "the SDK's UI limitations" has become the stock answer whenever a developer isn't interested in developing REs, whether it actually applies or not. Roland TB 303 Clones: ABL2 (vst) vs Phoscyon Maybe they are unaware of it or maybe it still is to restrictive for there products! Maybe someone else with more knowledge with what's new with the REASON SDK,might give them a shout out One thing I didn't mention to him is, how the RE format had been updated to a new SDK.
![d16 phoscyon vs abl2 d16 phoscyon vs abl2](https://appledrumloops.com/wp-content/uploads/2014/05/Bass_Line_Sequel.jpg)
Therefore, in case we succeed in creating the ReRacks devices, the outcome machines will only be inspired by our existing drum machines as opposed to 1:1 conversions. There is just a bit more to be written about it: As for the the plugins being adapted to Reason: as the ReRack's SDK format puts strong constraints when it comes to GUI (and this strongly influences the functionality), we have no certainty that we will be able to move them 1:1. Then the issue-ticket closes automatically in 2 days. In case you find my answer helpful, you might ignore replying. We are a small team (+ the graphic designer) and can not start such endeavour just immediately. Provided we start our attempts to the ReRack format, we must decide whether the devices would be 1 to 1 with original plugins, or should they respect the specific ReRack GUI that ties our hands significantly.
D16 phoscyon vs abl2 mac#
Still though we can't specify the exact date as there are too many current works to catch up with (as for instance chasing the endlessly newer and newer Mac OSes, or primarily - the creative work). Has D16 group considered porting Phoscyon to the propellerhead REASON format ?