Gearslutz.com - View Single Post

Thomas@TC · 23rd June 2009

Hey guys,

Sorry for this lengthy message, I hope this will answer some of your questions.

1)
The S6K plug-ins for PowerCore are 1:1 portings from System 6000. As said earlier in this thread, the two products use the same Freescale (formerly known as Motorola) DSPs.

In theory, a phase inverse comparison should do the trick. However, since the infrastructure on System 6000 and a DAW with plug-ins differs, there might be latency differences between the two, and therefore it might be difficult to get the two to cancel each other out.

When we do portings between products, for instance moving an algorithm from System6000 to PowerCore - or to Reverb 4000, we do all kinds of measurements to make sure they sound exactly the same. So, a VSS3 for System 6000 is 1:1 with VSS3 for PowerCore - or VSS3 for any other TC product.

In other words, we make sure that the naming of the algorithm is true to its content - sound wise. With some implementations, it does make sense to make adjustments to the UI.

For instance, with NonLin2 Poco, we graphically show the envelope, rather than working with numbers only.

If the algorithm is the same but the UI differs too much from the original, we might decide change the naming.
For example, TapFactory is a direct port of the System 6000 algorithm named Reflector, but since TapFactory has a very different UI, we decided to not name it Reflector.

There are also examples that we add algo stuff to the plug-in version.
For instance with UnWrap (stereo to 5.1 upconversion), we decided to do a dedicated DownMix page. The DownMix page lets the user check how the upconverted 5.1 signal sounds when played back in stereo.
System 6000 users would normally use the ToolBox to do this, but since we don't have the ToolBox available as a Poco plug-in, we thought that we had to add this feature to the plug-in itself.

Bottom line is, though, that the algo always remains the same - parameter- and sound wise, and therefore you also find that the System 6000 plug-ins are preset compatible with System 6000 plug-ins for Poco (you can take any System 6000 preset and use it with the equivalent Poco plug-in).

2)
You are correct that PowerCore 6000 includes the System 6000 plug-ins, meaning the algorithms from System 6000 that is currently available for PowerCore. PowerCore 6000 does not include _all_ algorithms from System 6000, e.g. it does not contain the VSS4 or the multichannel algorithms - (except UnWrap).

Since TapFactory is based on the System 6000 Reflector algorithm, we dicided to make TapFactory part of PowerCore 6000, too.

23rd June 2009	#60
Thomas@TC Gear interested Joined: Jun 2009 Location: Denmark Posts: 2	Hey guys, Sorry for this lengthy message, I hope this will answer some of your questions. 1) The S6K plug-ins for PowerCore are 1:1 portings from System 6000. As said earlier in this thread, the two products use the same Freescale (formerly known as Motorola) DSPs. In theory, a phase inverse comparison should do the trick. However, since the infrastructure on System 6000 and a DAW with plug-ins differs, there might be latency differences between the two, and therefore it might be difficult to get the two to cancel each other out. When we do portings between products, for instance moving an algorithm from System6000 to PowerCore - or to Reverb 4000, we do all kinds of measurements to make sure they sound exactly the same. So, a VSS3 for System 6000 is 1:1 with VSS3 for PowerCore - or VSS3 for any other TC product. In other words, we make sure that the naming of the algorithm is true to its content - sound wise. With some implementations, it does make sense to make adjustments to the UI. For instance, with NonLin2 Poco, we graphically show the envelope, rather than working with numbers only. If the algorithm is the same but the UI differs too much from the original, we might decide change the naming. For example, TapFactory is a direct port of the System 6000 algorithm named Reflector, but since TapFactory has a very different UI, we decided to not name it Reflector. There are also examples that we add algo stuff to the plug-in version. For instance with UnWrap (stereo to 5.1 upconversion), we decided to do a dedicated DownMix page. The DownMix page lets the user check how the upconverted 5.1 signal sounds when played back in stereo. System 6000 users would normally use the ToolBox to do this, but since we don't have the ToolBox available as a Poco plug-in, we thought that we had to add this feature to the plug-in itself. Bottom line is, though, that the algo always remains the same - parameter- and sound wise, and therefore you also find that the System 6000 plug-ins are preset compatible with System 6000 plug-ins for Poco (you can take any System 6000 preset and use it with the equivalent Poco plug-in). 2) You are correct that PowerCore 6000 includes the System 6000 plug-ins, meaning the algorithms from System 6000 that is currently available for PowerCore. PowerCore 6000 does not include _all_ algorithms from System 6000, e.g. it does not contain the VSS4 or the multichannel algorithms - (except UnWrap). Since TapFactory is based on the System 6000 Reflector algorithm, we dicided to make TapFactory part of PowerCore 6000, too.