Forge 6 rebranding -ACID Product Family - MAGIX Community Forums Archive

Subject:Forge 6 rebranding Posted by: Spheris Date:11/22/2003 9:18:24 AM Okay, I think we can all take a joke. But one of the things that most irked me about the forge 7 trial and one of the main reasons i'm deferring on it till later (bugs aside) was the fact it screws up the plugin setup. one of the things I liked most about foundry was a seemingly unified architecture end to end. unlike steinbergs hodgepodge nonsense. Now we have it here with a handy dandy new sony folder of plugins etc et al..minor but important in and of itself. and iritating as hell for the fact i have to reach into two sets of folders now for the same plugins as well as reassign presets and the like (no the migration utility is not working or the preset manager with the new plug assigns. at least not consistently. so when does 6 get the rebrand treatment or do we have to roll back to the previous e version in order to feel all is well with the worid? and yes, I'm well aware this is the acid forum. using 4.0 with forge and the sony acid 4f update is the culprit at issue
Subject:RE: Forge 6 rebranding Reply by: Iacobus Date:11/22/2003 12:00:27 PM The reason for there being separate folders is a rather simple one: The Sony plug-ins were built (re-built?) using UNICODE, a completely different programming language from the ones built in the Sonic Foundry folder. (It had a name but I can't remember offhand.) I highly doubt Sound Forge 6 will get a rebranding, being as it is Sound Forge 7 is the latest. I would imagine it's just a matter of time before everything points to just one folder again. (That is, if one upgrades to the latest.) Iacobus ------- RodelWorks - Original Music for the Unafraid mD's ACIDplanet Page
Subject:RE: Forge 6 rebranding Reply by: Spheris Date:11/22/2003 12:24:06 PM egads, back to 4e then. Hopefully I'll not find a reason to use the rear channel busses :) On the unicode subject, doubt that's in any part true. All 2000/XP apps (certified or logo) must be unicode compliant in order to attain logo. As a technology partner with MS. There'd be little chance the switch would have only occured now - but stranger things do happen I guess.

Subject:Forge 6 rebranding

Posted by: Spheris

Date:11/22/2003 9:18:24 AM

Okay, I think we can all take a joke. But one of the things that most irked me about the forge 7 trial and one of the main reasons i'm deferring on it till later (bugs aside) was the fact it screws up the plugin setup. one of the things I liked most about foundry was a seemingly unified architecture end to end. unlike steinbergs hodgepodge nonsense.

Now we have it here with a handy dandy new sony folder of plugins etc et al..minor but important in and of itself. and iritating as hell for the fact i have to reach into two sets of folders now for the same plugins as well as reassign presets and the like (no the migration utility is not working or the preset manager with the new plug assigns. at least not consistently.

so when does 6 get the rebrand treatment or do we have to roll back to the previous e version in order to feel all is well with the worid?

and yes, I'm well aware this is the acid forum. using 4.0 with forge and the sony acid 4f update is the culprit at issue

Subject:RE: Forge 6 rebranding

Reply by: Iacobus

Date:11/22/2003 12:00:27 PM

The reason for there being separate folders is a rather simple one: The Sony plug-ins were built (re-built?) using UNICODE, a completely different programming language from the ones built in the Sonic Foundry folder. (It had a name but I can't remember offhand.)

I highly doubt Sound Forge 6 will get a rebranding, being as it is Sound Forge 7 is the latest.

I would imagine it's just a matter of time before everything points to just one folder again. (That is, if one upgrades to the latest.)

Iacobus
-------
RodelWorks - Original Music for the Unafraid
mD's ACIDplanet Page

Subject:RE: Forge 6 rebranding

Reply by: Spheris

Date:11/22/2003 12:24:06 PM

egads, back to 4e then. Hopefully I'll not find a reason to use the rear channel busses :)

On the unicode subject, doubt that's in any part true. All 2000/XP apps (certified or logo) must be unicode compliant in order to attain logo. As a technology partner with MS. There'd be little chance the switch would have only occured now - but stranger things do happen I guess.