-
ACID Product Familyon 2/12/2020
ACID Pro 8/9/Next/MusicStudio - updated public beta Nov 12, 2019
Any update releases?
-
ACID Product Familyon 1/21/2020
Audio sample is added automatically--annoying
You spending even more time continuing to tell me how "professionals" work and with which tools? That right there spells out that you are truly not a professional. Have a good day.
-
ACID Product Familyon 1/21/2020
Audio sample is added automatically--annoying
You seem to wander and talk a lot. I already outlined I know the different fortes of the different programs and you ramble on about that while ignoring I've been describing the similar functions between them all along. These apps maintaining similarities does not stop them from expanding. I'm pretty certain common functioning explorer window views, sound card setups, plugin setups, and preference settings has not stopped them from moving forward. You talk about how "professionals" work and the tools they use. I don't care, I've witnessed those my penis is bigger than yours conversations many times over the years, they don't impress me and I'm really not interested in those type of conversations and your associated speculation assumptions. For me it's simple, I've worked in "professional" studios and it isn't about the tools you use or the workflow you choose. It never has been. I'm at a point in my life that I'm tired of jumping ships to learn a new way to work only to further discover their short-comings along the way. I don't care if there's a hammer available that has led lights on it, chromium finish and made of a new light weight rare earth allow metals and I definitely don't give a damn if Steven Spielsberg is producing the next Star Wars movie and associated music score with it. Those new tools don't make me a better or more "professional" carpenter if I'm not able to work more efficiently with them and with less frustrations along the way than I am with a good ole fashion, no frills hammer and build a house just as well as the other guy with the new frills hammer. I work with Acid and Vegas because I can go to work and not have to spend an additional 30 minutes each time I fire them up digging through different menu layouts and scratching my head trying to do a simple task for something I already know how to accomplish in Acid or Vegas and I don't care to change that so Acid can start looking like the star ship enterprise. You don't have to tell me the history of Vegas, Acid and Sound Forge from Sonic Foundry to Sony, to Magix and act like the rest of us are clueless about that history. I've been using them since their initial releases. You can go find my username on the Sony/Sonic Foundry forums going back to the 1990s if you're really insterested. I'm glad you seem to have everything all figured out and know how "professionals" work and the future roadmap Magix has chosen with these apps. However, most of it just sounds like a bunch of speculative assumptions, aka bullsh*t and it seems you really enjoy talking bullsh*t.
-
ACID Product Familyon 1/20/2020
Broken Beatmapper Wizard and More
P.S. The Stem Separator in ACID Pro Next is Terrible. That was the only new feature I was interested in for APN, but haven't personally tried it yet. I've been spending weeks configuring APN to look, feel, and function the way I'm used to working in past Acid versions, and becoming frustrated along the way when I find preference settings taken out and when I do get things setup to work with my MCU controller, only to find out it doesn't work very well or at all. All this is becoming very discouraging towards the revival of the products where I was finally very excited to see a 64bit version released with some new life breathed into them.
-
ACID Product Familyon 1/20/2020
Audio sample is added automatically--annoying
Acid, Vegas, and Sound Forge are different applications for different purposes - not a "Suite" of applications. They each need a UI/UX tailored to the markets they target. So it's actually encouraging that MAGIX is willing to start breaking that mold, and unshackle these applications so that they can develop well for their target user bases. They were always intended as a suite of products where they are different applications with different fortes in the different areas of multimedia creation. That's the reason they all share common functions which had originally been implemented to be common, so the users which use all 3 applications in their different areas of multimedia creation wouldn't be faced with learning different paradigms, while using apps which have common functions between them. There's a reason that both Acid and Vegas will automatically recognize if Sound Forge is installed on your system and both will then have an "Open in Sound Forge" menu item where audio can be exported, manipulated in SF and imported back into Acid or Vegas easily. If Acid didn't have a similar paradigm and workflow as Vegas, then I would have fully moved to Reaper for music creation a long time ago and if Acid continues down this path of moving away from that commonality between them, then I no longer have a good reason to stick with using Acid Pro if I'm going to be forced into learning new and different paradigms. Reaper is the better music creation app at this time over Acid aside from Acid having a similar GUI and workflow as Vegas and Sound Forge. Reaper costs less, is better supported in fixing problems with much more frequent updates which includes additional features and fixes. So yeah, go ahead and break the mold if the goal is to push away customers who use that suite of apps for the commonality between them. Acid is no longer a leader in any area of being a music creation DAW tool and they would only be pushing users towards the other apps which are. The OP has been pushed towards Albeton Live while preferring to work with Acid, where I feel like I am being pushed towards Reaper with these changes which have provided nothing other than working differently than what we have grown accustom. Jump the shark and get eaten by the other sharks. This would also be the dumbest thing to do in regards to development resource management where if you have 3 apps with common functions between them, that you wouldn't be sharing code between them to reduce your overall development efforts but instead having similar apps and having different developers working on them and recreating the same functions in different manners.
-
ACID Product Familyon 1/17/2020
Audio sample is added automatically--annoying
Now, back to the issue, I meant by Auto Load was this, when you double click a sound from the explorer, it loads a new track onto the arrangement ready to be painted (greatest feature which no other DAW has to date), but now, when you double click a sound, it loads that very sound onto the track's beginning (a 4 bar loop or one shot). Please try this and you will know what I mean. Acid was the only DAW that had auto track creating when double clicking on a sound but guys at Magix sort of ruined that, too. Thanks, I see what you mean now. I'm currently just setting up my system with AP Next and am not quite at the level of seeing what Magix has done. Now that I look at it and tried it out, I noticed the double click to load in chopper in the preference settings is no longer there as well. The drag from explorer onto the track fader section which is the way I typically add loop works the same as you described, where it auto loads the loop onto the track timeline as well, so that isn't a work around either. It seems like someone who didn't quite understand the original Acid paradigm, created this new behavior with the thought they were saving us a step but in doing so, they actually created more steps since the most often use case is that you add a loop to a track and then start painting that loop into your song arrangement at different sections other than the beginning, such as the verse/chorus/bridge....which are not in the intro beginning section of the song...LOL! So now if you actually intended to have a loop come in at the chorus, etc you 1st need to scroll back to the beginning of the song to delete the loop that was auto loaded onto the track at the beginning of the song. Good grief! Thanks for the heads up, that would have frustrated me as well. No longer seeing the double click to load in chopper is annoying also.
-
ACID Product Familyon 1/16/2020
Audio sample is added automatically--annoying
Hi You can run the GUI with Acid Pro 7 in the settings Options>Preferences>Display= Dark or Light choice thanks for replying. but as I mentioned originally "....new version and dark to extremely lit GUI", where you suggested, its still not the same as version 7. Its almost as if the dark GUI was inverted. Not sure if that makes any sense. But more than that, that "auto load" of samples is way more annoying at the moment among other things. I wish there was an option to turn that off. I'm totally onboard with you with the GUI color selection. They went from extremely dark to an almost too bright color selection option. I do however appreciate the light, it is much better for my eyes than the dark. One of the things I'm majorly disappointed with since Magix has taken over the development of Vegas Pro, Acid Pro and Sound Forge Pro is the lack of commonality that has been lost as they started creating revised versions of these apps. This is something that Sonic Foundry and Sony made a very conscience effort to ensure commonality between these apps. So for instance in regards to color themes, current Magix versions of Vegas Pro and Sound Forge each have 4 different level options from dark to light of their themes to choose from, yet with the new versions of Acid Pro they initially provided a dark only theme and later added the extremely light option where my eyes prefer the options that are typically in between. So when I fire up Sound Forge or Vegas, the look and feel is very similar and now Acid looks like it has jumped the shark and has been kicked out of the family. Sound Forge, Vegas and Acid also have common functionalities such as their explorer window views, plugin manager views, yet ever since Magix has taken over development, I have noticed these once common views that functioned and looked very similar, are becoming very different from each other. Assigning plugin locations are different in Acid than in Vegas and Sound Forge. There are many things I am seeing becoming different about each of these apps and not in a good way. This all tells me that Magix needs a project lead that oversees the suite of the acquired Sony products to ensure things are implemented in a common direction, but it's becoming obvious that their different development teams assigned to each of the products, the right hand is not talking to the left. I'm uncertain of what you're describing with the "auto load" when double clicking on a sample. Are you talking about the double clicking behavior when viewing audio files through the explorer window? If so there is a double click option under the preferences to have it load into the chopper window instead of the track view and that is a common preference setting in Vegas and Acid, except in Vegas it's the trimmer window and in Acid it's the Chopper.
-
Sound Forge PCon 7/26/2019
Incompatibility between all my MAGIX audio programs and Yamaha AG06?
It's likely a Yamaha ASIO driver problem. They're not exactly known for being one of the more commonly used audio interfaces. You may want to try the ASIO4ALL driver with the Yamaha interface and see how that works.
-
ACID Product Familyon 5/27/2019
A critical discussion: What went wrong with ACID Pro 8 ?
Having someone to complain to and something to complain about and seeing someone actually respond is progress for Acid Pro that we haven't seen in 10 years. Oh, and seeing a 64bit version on my Win10 x64 bit system that I can use without jumping through hoops is very welcome as well. I've been using Acid since v1.0 (no pun intended). :D I've tried to stop using Acid and move onto all those other great DAW programs and to be honest, they all are great in their own regards one way or another. What keeps bringing me back to using Acid and Vegas for that matter? Familiarity. It's as simple as that. I've reached a stage in my life, where I just no longer feel like working through the frustrations of learning another DAW. So while those other DAWs now do those 5 to 10 things better, it's the other 100 things that I use more often and I know exactly where to look for them is why I continue using Acid Pro. I'm sure many of us including the OP is in that same camp. I'm also happy that Acid evolved into a full DAW. That way I didn't need to learn another program to do the other things I use a DAW for and I didn't have to be messing around syncing and rewiring multiple programs together. There's a lot of things I don't like in the newer versions of Acid, but I just blame that on human nature. As humans we are creatures of habit and anytime someone changes something that we've grown accustomed to, it always makes us feel uncomfortable but that's just progress being made and it's up to us to adapt, try to focus on the positive and stop complaining. I see the same kind of bitching and moaning everytime there's a new version of Windows released. "Oh my gosh! Windows 7 was so awesome, Windows 10 is so awful! Microsoft are complete idiots! They cannibalized it!" Sound familiar to the 1st post? Shut-up already, stop being lazy and move out of your comfort zone and start enjoying progress being made and jump into the fun zone.
-
ACID Product Familyon 5/27/2019
EQ !!!
Regarding jbridge. I can't say I've encountered any plugin that doesn't work, at least in AP8. Obviously though I've not tried every plugin in existence. Have you tried rescanning your plugins. Have you added the 32bit installation folders to the folders to scan? I've been unsuccessful using Jbridge with the Sound Toys v4 Native plugins. Sound Toys just released v5.3 plugins with 64bit support, so maybe I need to look into those. https://www.soundtoys.com/product/soundtoys-5/
-
ACID Product Familyon 5/27/2019
External Control surface Automation (MCU)
I figured this out. I had to go into the X-Touch ONE configuration settings and map a button to the MCU "READOFF" defined command. It looks like I need to either reverse engineer ACID and VEGAS MCU command mappings to determine which function in each they map to in the DAW. In case anyone else has this problem, here's what I found. The MCU "READOFF" command when mapped to a button on the controller, will toggle the controller to either control/read the Acid/Vegas non automation faders/controls or the automation fader/controls. I was able to do this by changing the X-Touch ONE to the "MCU user" configuration, which then allows you to map pre-defined MCU commands to specific buttons.
-
ACID Product Familyon 3/21/2019
[Feedback] How do you like version 8.0.8.29 ?
the current build DOES show the architecture, if the VST is a different architecture from the version of Acid you're using. e.g. if you're using 64bit version, it will label the 32bit plugins accordingly. If the VST is the same architect as the version of Acid you're running it doesn't display it. Did you actually add in your 32bit Plugins? I think I know where my confusion is with all this. Yes, Acid does show you if you're using the 64bit or 32bit version and the names of plugins makes sense from what you described. It shows "(32bit)" next to their names when I'm using the 64bit version of Acid. What it doesn't show you is if it's a VST3 or VST2 host. Acid added VST3 plugin support in the latest update. So based off of what you described and what I'm currently seeing with my plugin names is that the problem seems to be that although the latest update has VST3 host support, Acid still thinks it is a VST2 host since I it displays "(VST3)" labels next to my plugin names, thus causing confusion since Acid is not behaving consistently with its plugin naming convention to what you described. So don't expect any type of consistency between Magix apps is the theme I'm starting to witness. Don't expect consistency for it's VST plugin support naming within an app and don't expect consistency between Magix apps from the same family of products such as Sound Forge Pro 12, Acid Pro 8, and Vegas Pro 16. Expect the unexpected. Good to know.
-
ACID Product Familyon 3/19/2019
[Feedback] How do you like version 8.0.8.29 ?
OK, I just confirmed my VST scanned folders between Sound Forge and Acid Pro Sound Forge VST folders *C:\Program Files\VSTplugins\*C:\Program Files\Common Files\VST3\*C:\Program Files (x86)\VstPlugins\ Acid Pro VST folders *C:\Program Files\VSTPlugins\*C:\Program Files\Common Files\VST3\*C:\Program Files (x86)\VstPlugins\C:\Program Files (x86)\Common Files\VST3\C:\ProgramData\ACID\ACID Pro\8.0\MAGIX Plugins\C:\ProgramData\ACID\ACID Pro\8.0\MxSynth\ So now the problem, in Acid I have no waves VST3 plugins showing up, but they are clearly showing up in SF12. In the Izotope plugin folder, it shows "(VST3) next to the plugin's name. So therefore that must mean that Acid must think it's a VST2/64bit program.
-
ACID Product Familyon 3/19/2019
[Feedback] How do you like version 8.0.8.29 ?
One thing I really wish is that the Plug-In manager showed more details like it does in SF12. In SF 12 the Plug-in manager displays if it's a VST2 or VST3 plugin as well as tells you if it's 32bit or 64bit plugin. AP8 seems to only tell you if it's a VST3 plugin or not which is better than Vegas Pro which doesn't seem to tell you anything in regards to the plugin properties and lets you know which version of the plugin you are using in your project. the current build DOES show the architecture, if the VST is a different architecture from the version of Acid you're using. e.g. if you're using 64bit version, it will label the 32bit plugins accordingly. If the VST is the same architect as the version of Acid you're running it doesn't display it. Did you actually add in your 32bit Plugins? Anyway to get AP8 and Vegas Pro 16 to display plugin details like SF12? There's a little thing of consistency across apps that I really like and it seems SF12 has the best implementation. When you enable "Details" in the AP8 plug-in manager view there is a column of "version" but nothing is displayed. I'm guessing that column should display VST version? Yeah, you're right there. Looking at the properties info of a plugin does show the version, but it's not being populated in the details view. One thing I really wish is that the Plug-In manager showed more details like it does in SF12. In SF 12 the Plug-in manager displays if it's a VST2 or VST3 plugin as well as tells you if it's 32bit or 64bit plugin. AP8 seems to only tell you if it's a VST3 plugin or not which is better than Vegas Pro which doesn't seem to tell you anything in regards to the plugin properties and lets you know which version of the plugin you are using in your project. the current build DOES show the architecture, if the VST is a different architecture from the version of Acid you're using. e.g. if you're using 64bit version, it will label the 32bit plugins accordingly. If the VST is the same architect as the version of Acid you're running it doesn't display it. Did you actually add in your 32bit Plugins? Anyway to get AP8 and Vegas Pro 16 to display plugin details like SF12? There's a little thing of consistency across apps that I really like and it seems SF12 has the best implementation. When you enable "Details" in the AP8 plug-in manager view there is a column of "version" but nothing is displayed. I'm guessing that column should display VST version? Yeah, you're right there. Looking at the properties info of a plugin does show the version, but it's not being populated in the details view. I'm pretty sure I have SF and Acid scanning the same folders and my 32bit plugins have been added. What's odd to me is that SF shows all my VST3 plugins as being 64bit but in Acid as you have shown they're labeled VST3 "32bit". I'm really confused, so if there's no label next to the plugin name, and I'm using the 64bit version of Acid, then I should assume that it is a VST2 64bit plugin or a VST3 64bit plugin? It seems to be the latest Acid update is "VST2" according to what I'm seeing with my plugin names, yet they added VST3 support in the latest update. If you could help me out here, because I'm really struggling to understand the methodology in Acid and it's definitely much clearer in SF. These are my iZotope plugins. Starting from the top. "Neutron 2"= ???/??? "Neutron 2 (VST3)"= VST3/64bit?? "Neutron 2 (VST3) (32 Bit)"= VST3/32bit Now I go to my Waves folder "Abbey Road Plates Mono"= ???/??? "Abbey Road Plates Mono (32bit)"= ???/32bit What a mess to try and figure out.
-
Sound Forge PCon 3/16/2019
Noise Reduction Plug-In
I ended up just installing the Sony version. I couldn't find the "soundforgepro12_dlm.exe". So I thought I would just try to reinstall SF12, since I must have just quickly clicked through the install and missed checking NR. It's telling me I need to uninstall before I can re-install. I would have gone through and done that, but I just finished spending a ton of time organizing my plugins in the Plugin manager and it seems I would have had to do all that organizing over. Anyone know of a way to save and recall your plugin manager folders and plugin groups?
-
Sound Forge PCon 3/13/2019
Noise Reduction Plug-In
Thanks Rick, I'll give that a try. My PC recently got corrupted when I was installing some Waves plugins. I'm pretty anal about keeping HDD image backups and for some reason I couldn't even get my PC to boot into windows after restoring a known working HDD image. So long story short, I had to do a complete factory restore and start installing everything fresh. Therefore, I'm just starting with the latest versions of SF, Vegas, Acid, etc and have just let everything install with default settings. Took me an entire week to get 90% of everything re-installed and reconfigured. The NR 2.0 Magix version built into SF12 isn't a VST? Just Dir-X?
-
ACID Product Familyon 3/9/2019
[Feedback] How do you like version 8.0.8.29 ?
The lighter skin was definitely a welcome addition. I had just installed AP 8 last week and from being a AP user since v1.0 the 1st thing I looked for changing was a lighter skin. I really couldn't stand the black, it really made me feel uncomfortable and became frustrated to find there was no adjustment but 1 week later that was solved with the update. I'm in setup stages for now with AP8. One thing I really wish is that the Plug-In manager showed more details like it does in SF12. In SF 12 the Plug-in manager displays if it's a VST2 or VST3 plugin as well as tells you if it's 32bit or 64bit plugin. AP8 seems to only tell you if it's a VST3 plugin or not which is better than Vegas Pro which doesn't seem to tell you anything in regards to the plugin properties and lets you know which version of the plugin you are using in your project. Anyway to get AP8 and Vegas Pro 16 to display plugin details like SF12? There's a little thing of consistency across apps that I really like and it seems SF12 has the best implementation. When you enable "Details" in the AP8 plug-in manager view there is a column of "version" but nothing is displayed. I'm guessing that column should display VST version? SF Pro 12 plugin manager view AP8 plugin manager view
-
Sound Forge PCon 3/8/2019
Noise Reduction Plug-In
Hi rraud, I've been out of the loop and am currently setting up my PC. Wow...32bit, 64bit, VST2, VST3 versions of plugins...what a mess. Anyways, I installed SF Pro 12 and am not finding NR-2.0. Where are they hiding it these days? Was going to install my Sony NR-2.0 version but if it's in SF12...no need right....if I could just find it.
-
Sound Forge PCon 1/18/2018
SOUND FORGE – What features do you want us to develop?
I'm sure I'm late to the party and SF 12 is well on it's way already but here's some more..... The File Browser could use some updating to support viewing audio file metadata fields, as well as include a search filter. If you're not familiar, try out MediaMonkey for a great onboard file browser. http://www.mediamonkey.com/ MediaMonkey has a great "ALL" selection, where it then displays all the supported media files in the current browse window folder AND all the sub folder contents that are under that root folder. For example: Note the "ALL" selection on the left. Then notice the "Search" field filter to the upper right. I type in a word in this example "jump", and it displays all the files that match that search filter view criteria which are under the folder I have selected. Hmmm??? I need to find a "Tight Snare drum" sample in a whole mess of drum sound samples. Type in "Tight Snare Drum" and all metafields that match that description are displayed. That could be useful and make work pretty efficient huh? Then here's the view if I select just a single folder. Now let's compare that to what the curret Sound Forge's File Window Browser provides while selecting the same folder. Looking kind of outdated by not supporting displaying any metadata fields which the majority of modern audio file formats now have with a waste of a bunch of screen space not filling any useful information.
-
Sound Forge PCon 1/18/2018
Drag and drop into SF 11
I tried to go through the regedit stuff, and it wasn't as described and didn't work for me. I found 3 paths in my registry that all looked similar to the path described but none of them matched as described. Here's the paths I found in my registry \HKEY_CURRENT_USER\Software\Sony Creative Software\Sound Forge Pro\11.0\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Sony Creative Software\Sound Forge Pro\11.0\HKEY_USERS\S-1-5-21-2822192545-2847659882-2700481763-1001\Software\Sony Creative Software\Sound Forge Pro\11.0 I deleted the 11.0 folder in the last one and still had errors. I ended up restoring my system from a HDD image backup which I had prior to the SF 11.0 Build 345 install and then followed the method below which went much smoother and didn't require any regedit monkey business. The joys of installing the Sony stuff in making sure you have all those proper ".NET" packages installed prior. 1. Go to the search point next to the Start menu and type 'Windows Features'.2. 'Turn Windows Features on or off' will appear.3. Click on this. You may be asked for your Administrator password, so enter it.4. At the top of the list, you will see '.NET framework 3.5 (includes .Net 2.0 and 3.0)'. Expand this item and check the check boxes next to the two items that drop down and ensure that the main item is also checked. Press OK.5. You will be asked to confirm the download of some additional components. Do so and let the system do its stuff.6. You'll be prompted when the process has completed.7. Close the panel. I can see wherever Magix touched this release. Someone must like to program with the CAPS LOCK on. Found a new "MAGIX" folder and my shared plugin folder after install was in a folder named "VEGAS", and I hadn't even installed Vegas on this system yet.
-
Sound Forge PCon 1/18/2018
Win95 Sound Forge Noise Reduction Wanted
I have NR v1.0b. It's a full 900KB in size. It's a DX version that I ran with SF v4.5 ;)
-
Sound Forge PCon 1/17/2018
Hello Again, I'm Back!!! (Sonic Foundry Forum User check-in Club)
Thanks for the Welcome back Rick!!! Good to see you still hanging around. I'm glad someone stuck around to captain the ship and keep up the good fight while the rest of us dispersed and abandoned it. Well, I kind of got thrown overboard at the end 😆....but that's all good. I'm glad to see the Magix team breathing some life back into these great tools. I really thought I was witnessing yet another long and drawn out Opcode Studio Vision death with all the Sonic Foundry products. Hopefully, there's some long term vision with these products going on behind the scenes and we can get this forum back to hoping again and get back to arguing about what are the most important features we all need. 👍 Have you been working with any of the developers that transitioned over from SF/Sony with the beta testing? Peter still around?
-
Sound Forge PCon 1/17/2018
SOUND FORGE – What features do you want us to develop?
User requested Feature requests. I love it!!! Overall, I think Sound Forge needs to come up to speed with the rest of the apps/programs out there and become "Connected". As in connected to the cloud. This would give SF a closer integration with the OS eco system that the other audio apps have not jumped onboard with yet. We should have a "share" button, so that SF is not on an island but instead I can save and open audio on cloud based storage systems like Google Drive, OneDrive, DropBox, iCloud, Sharepoint, Email, This of course means that SF should have the ability to add your account credentials to access those cloud storage systems, and be able to Browse audio files directly from within SF which are stored in the cloud. And let's not stop there, there's more to this. We should be able to have SF with us wherever we go and not tied to our Audio DAWs. There should be a Sound Forge "Express" app available for iOS, Android, and Windows Metro devices. Think along the lines of Adobe's Photoshop "Express" app. A reduced feature set of SF available in the app store market places that provides the basics when you're on the go. Nobody travels without a smart device these days, so SF is always with us and is a familiar app we're comfortable working with wherever we go. Try to imagine some of the scenarios that can happen and would expand SF into markets where it doesn't currently exist. Let's say for example I'm a news media reporter, or an in the field audio technician, etc and I'm out in the field and I need to record something. I fire up my SF Express app on my smartphone, I press record and start recording. I get done recording, I do some basic trim clean-up editing on that audio within SF Express, maybe some noise reduction, normalization, and other volume adjustments with it. I save that audio to whatever format I need, I then select "share" on the SF Express app and I upload it to the cloud storage service, email it, or heck even send a text message with that audio file. The persons colleagues, or that individual fires up SF Pro back at the ranch on our desktops, access that audio that's now already in the cloud, where we're all sharing that same cloud service access and collaborating on a project in almost real-time using multiple devices which make more sense to the locations/situation we're currently at. Maybe they add some music to that audio back at the ranch. They save it to the cloud and now the person in the field opens it back up in the SF Express app on their smartphone or tablet. It doesn't even have to be a collaboration scenario. I could record some audio on my smartphone out in the field and when I get back to my DAW with SF Pro, Vegas, or Acid on it, that audio is waiting for me, where I'm not there and trying to figure out how I'm going to transfer that audio from my phone/tablet to my desktop....it's already there when I arrive. We live in a connected world. I would have to think, it's time for Sound Forge to start becoming connected. Thanks for asking, Red
-
Sound Forge PCon 1/17/2018
SOUND FORGE – What features do you want us to develop?
Hi Mathias, I sent you a PM about beta testing, I wonder if you got it. I was a beta tester for SCS on SFP-11 and SL. Did someone say there was a new Sound Forge in the works? ;)
Rednroll
Offline, Last login 6/30/2020, Member since 1/17/2018