|
Subject:SF7... do I need it?
Posted by: SteveM
Date:11/28/2003 10:35:51 AM
I've been using SF5 for quite some time & was wondering if there is any reason why I should upgrade to SF7. I thought SF6 was less than impressive (actually slower than SF5) and I haven't seen anything that makes me want to spend the $$ to upgrade. Any comments, suggestions, etc will be appreciated... thanks! Steve |
|
Subject:RE: SF7... do I need it?
Reply by: Iacobus
Date:11/28/2003 11:47:13 AM
6.0 was slower than 5.0 for you? For me, the selling point was the fact that, in version 7.0, you can work with files like you would a project in ACID or Vegas, which means you can make changes even after you close the file and come back to it later on. You're no longer committed to changes in 7.0. (Must save in the FRG file format, which is Sound Forge's project file format.) Be aware 7.0 is Windows XP/2000 only. Apparently, some users were not aware of this fact when upgrading, only to find out that 7.0 wouldn't work on their 9x/Me system. HTH, Iacobus ------- RodelWorks - Original Music for the Unafraid mD's ACIDplanet Page |
|
Subject:RE: SF7... do I need it?
Reply by: seeker
Date:11/28/2003 8:51:49 PM
Iacobus, Do you think there is any chance the special upgrade offer of $99 that ended October 31 will be repeated? That came at a bad time for me. And I don't have Windows XP yet. -- Seeker -- |
|
Subject:RE: SF7... do I need it?
Reply by: Spheris
Date:11/29/2003 5:06:03 AM
In a word - no no showstopper features and funny enough alot of the newer features are just renamed versions of less obvious ones in 6.0 Stay with 6.0e and be much much saner until sony works out their issues with rebranding and licensing problems with 7.0 if you need wm9 and 24p dv support buy the mainconcept dv codec for 49 6 handles media 9 video and audio just fine as is if you have the wmv9 codec installed |
|
Subject:RE: SF7... do I need it?
Reply by: drbam
Date:11/29/2003 6:51:32 AM
Seeker: Contact Sony and tell them your story. I did that some time ago regarding the SF6 w/ Noise Reduction offer. I orginally didn't get NR and a few months later regretted it. I wrote to SoFo and they sent me a link for the download at the discounted price. That kind of service definitely reinforced my "loyal customer" position. drbam |
|
Subject:RE: SF7... do I need it?
Reply by: drbam
Date:11/29/2003 7:01:47 AM
>>In a word - no no showstopper features. . .<< I disagree. I personally think that non-destructive editing and especially the addition of envelopes are worth the upgrade. Of course this is subjective and anyone asking this question should watch the new features video and/or download the demo and decide for themselves. Nobody here can really say anything about how valuable a product can be for someone else they don't even know. ;-) drbam |
|
Subject:RE: SF7... do I need it?
Reply by: Rednroll
Date:11/29/2003 8:47:37 AM
"no showstopper features and funny enough alot of the newer features are just renamed versions of less obvious ones in 6.0" Spheris, You keep mentioning "showstoppers". Could you let the rest of us who are happilly using v7.0 without any problems what you are referring too, so that we can be made aware of them? |
|
Subject:RE: SF7... do I need it?
Reply by: Rednroll
Date:11/29/2003 8:54:37 AM
If you have no need for these features, which are the ones I use the most, then yes I agree you should stay with v6.0. I find these features priceless and have been asking for many of them since v4.5. v7.0 to v6.0 feature additions:: 1. A Vu meter, which more accurately represents how your hearing detects loudness, allowing you to do more precise mastering leveling of different songs. 2. A sweep Generator, which allows you to generate any frequency sweep duration so you can use these waveforms for audio system analysis. 3. Noise generators, which will allow you to accurately tune an acoustical environment and also do analysis on other audio hardware. 4. Undo past save, which allows you to make a save, then hear your changes in your multi-track program like Vegas and if you decide you don't like what you did within the project you can freely UNDO and make tweaks. 5. Total undo history saved within the new Sound Forge project. Allowing you to do an entiring mastering session and recalling and undoing every process you did if you decide later you didn't like something. 6. Enhanced Spectral Analysis tools, allowing you to compare one files spectrum to the one you're working on. Another great mastering tool, when you are trying to get your sound to match what's currently available and has been professionally mastered. Which gives you great control of making precise eq adjustments. 7. Automatible effects/envelopes, allowing you to change effect parameters and, volume and pan envelope adjustments. Tons of use for this one. 8. Vinyl Restoration plugin, allowing you to remove clicks and pops within a recording. 9. Automated recording options. Allowing you to set a time for SF to start and stop recording...just like a VCR, when you're not around and want to record something. Also, a threshold start/stop recording. Want to record something and not sit there all day and listen for it. Let Sound Forge do it for you. 10. Drag and drop CD extraction from multiple CDrom devices. Have a CD burning tower and a bunch of CD's you need to extract the songs from. Put all the CD's into the seperate drives, select the tracks you want and walk away while Sound Forge handles all the work for you, instead of having to sit there, open the extract window...extract one song, wait.....remove CD, insert next, open extract window..extract...wash rinse repeat. 11. New explorer window, allowing you to manage and preview your audio files all within sound forge. |
|
Subject:RE: SF7... do I need it?
Reply by: Spheris
Date:11/29/2003 10:31:17 AM
Okay red, I can answer you. Because bam has not a clue what I was referring to. 1. The metering in the 7.0 version is not a step forward and probably should have been left out because of its lack of corresponding compatibility with broadcast standards (ie previous threads discussing the rms discrepancies and various inventive ways to get it back on track which have not been addressed as of 7a unless they just left it out of the readme - doubtful) 2. wm9 support is almost fully functional in 6, quicktime support is parallel with 6 as there is still no direct aac/mp4 export options as yet from any of the foundry products as several posts on this forum and my own experience with it have demonstrated. 3. non destructive editing is built into 6. that answers itself. if you truly needed the ability to roll back after a save. go have a cigarette and think about it before you save - it presents the connotation that the editor is an idiot and somehow. I'm sure some are but I find the connotation offensive. end of topic for that one. 4. it makes a bloody mess if you have any other foundry products installed and you are not some sort of zen master of patience and flipping through rings in order to traverse the many strange angels that it seems to offer the unwary. multiple plugin versions, blown plugins and export incompatibilities, reg errors and etc all well discussed in these forums. Worse, that the unicode nonsense was offered as an explanation/defense of it. see http://cgm.cs.mcgill.ca/~luc/standards.html for further explanation and details of what unicode is and how it means absolutely nothing to program structure or compatibility in the case of this nonsense they made of the 7.0 install. 5. 24p support in 6 is entirely possible with the mainconcept dv codec - which is the only feature of it that is partially new. considering the spectrum analysis only got a visual overhaul to pretty in pink/blue what have you - with no functional upgrade in its functionality as a comparitive much less editing tool over what 6's offers. end of story there. I can take a screen shot just fine and its just as useful for edging out a bad spectrum. I'll use the ionizer for that and skip the nonsense and time waste, thanks. :) We're entitled to our opinions Red. you are a fan. for your own reasons. I am not - for my own reasons. Neither are more valid than the other. But both are valid pro and con for the app. I remain with my intitial post. No show stopping reason to upgrade to it as yet. |
|
Subject:RE: SF7... do I need it?
Reply by: RiRo
Date:11/29/2003 1:32:29 PM
you said... "many strange angels" Hmmm... could be interesting. RiRo |
|
Subject:RE: SF7... do I need it?
Reply by: pwppch
Date:11/29/2003 7:13:50 PM
Spheris: Explain to me what this site you reference http://cgm.cs.mcgill.ca/~luc/standards.html has anything to do with UNICODE support in our apps or your contention "it means absolutely nothing to program structure or compatibility" is even remotely accurate? While there are some interesting links on the site you posted, I found little if anything to do with UNICODE developement. I found absolutley nothing to support your contention about our UNICODE support. Please, clarify yourself here. Peter |
|
Subject:RE: SF7... do I need it?
Reply by: Spheris
Date:11/29/2003 9:48:44 PM
Peter, You missed the point. Here's the clarity, THERE IS NO CONTENTION ABOUT THE UNICODE SUPPORT -unicode has no bearing on the arcane explanation of this nonsense in the change of sf7 structure or cross compat with the existing ACID or VEGAS structures that has been rolling through the threads for a few weeks - not particularly by Sonys doing I will add. Apple and MS development in their current form require unicode. True, unicode is not supported in any 9x product or any apple OS from 9.1 backwards (and upto 9.6, it's a sad sad thing anyway by my own admission). That much is true. But the rest of what is being offered in explanation for it is getting a bit OT and rediculous. It is a character set standard. Not a code level compatibility issue in the win32 environment because name space (read file system type and character translations) issues are handled at the OS level not user level and therefore transparent. Not an allmighty hammer explanation such as WMD's which is about on the same par for accuracy if we've read the papers lately ;) I'm not claiming the foundry is responsible for that as much as people have grabbed the idea and ran with it to explain a raft of initial problems that are being sorted one fix at a time as program errata, not character set issues. The rest of the explanations given for the various strangeness in the new build as well as the separation of the dir structures etc, however is not applicable - unicode has no bearing on it. Market considerations and restructuring woes do -ie mainconcept and other affiliations and their renegotiations. But that's another thing altogether and part of being in business. At best you could break OS support, not support within your own application group. True, you owe your customer base no particular explanations. But then again, when problems occur - they would like a workable answer and address of the issues. Which looking back (and not very far) are more than a varied few. The unicode explanation should have been squashed at the start. Not left to turn into the blanket answer to all. The rest is immaterial as explanation or excuse. Not that I am calling you on the carpet particularly. But the unicode explanation has spiralled a bit out of context. It is an ISO standardised character set. For cross platform and unity in developement. Which means Sony is planning a foray into the macintosh realm sometime soon. Which is good. But at the cost of some real iritation to their current client base. Which in an unstable and faltering market is very,very bad. Just ask any win32/darwin developer. oh, you have one here. It's very very bad. Nothing against the foundry. I love what you make - upto this 7.0. I bought a PC specifically to use acid and came upon forge by virtue of that and truth to tell have not touched Peak in nearly 7 months since forge was purchased and no apologies to BIAS for that. You made a superior product, and mean that - THERE IS NOTHING COMPARABLE to it for the MAC world as yet. And while we're here. Any chance of a proper rebranding of 6.0. it would make my ACID so much happier ;) and allow me not to do this arcane shuffle of two folders of the same plugins from seemingly two separate companies sony/sonic foundry that makes me nearly insane just to look at. It's kind of like unified character sets, you just get used to a little order. Know what I'm saying? By the way, I was looking for promotional lit on vegas to get it bought in at the organisation I'm at but found since sony restructured the page. its just the little on the front page. Is it still around as specs etc? or is that pulled till the new version? Help is appreciated on that and nothing personal Peter, just clarifying a little misinformation on unicode and what it has to do with some of the perceived problems - which is nothing at all. The rest of the problems I pointed out still stand and in that you did not speak to those. I will assume they are still to be addressed which I'm sure will help the person who started this thread immensely in his buying decision. With no apologies for providing the best answer I could based on the information available and some time looking over the 7.0 trial product versus the 6.0e product. And some very real disdain for the hokie blanket "answer" that has proliferated to 7's idiosyncratic behaviour for some time now and stops (hopefully) here. ALL products ship with errata, ALL of them. You and I have to accept that and hope our clients can to as they are either worked around or redeveloped into workable structures for their use. I credit you and the entire foundry developer team for doing that with the last generation of products. I truly do. It's on a par with Appleworks for cohesive design and part of what attracted me to begin with (waits for the MAC users to stone me to death ;) Yours sincerely, a very happy and loyal 6.0e user and WIN32/DARWIN developer And Peter, if I seem a bit iritated with you and Sony in general, why don't you look back two topic pages and try giving me an answer to my question posted about the side effects of if and when cda and batch will be rebranded updated et al. Since a valid purchase question can go ignored but an honest answer to someone else seems to draw you calling me on the carpet to a losing debate about the pros and cons of character set support and file system level translation logistics? Thanks Peter, I'll be looking forward to the answer to the two questions posed to you now. get back to me on the cda thing before my wife charges me out of house and home for christmas season, would you? |
|
Subject:RE: SF7... do I need it?
Reply by: drbam
Date:11/30/2003 9:13:38 AM
>>Okay red, I can answer you. Because bam has not a clue what I was referring to.<< I was simply offering a subjective opinion directly related to the SteveM's original question. My response to SF7 is different than yours and was intended for SteveM and anyone else who might be interested in a wider range of opinions and was not directed to you. Period! Unless you're psychic (and obviously your not), you do not, nor cannot, have any idea whether I have "not a clue" what you were referring to. drbam |
|
Subject:RE: SF7... do I need it?
Reply by: Rednroll
Date:11/30/2003 9:20:26 AM
Speris, I'ld let to address some of your points: 1. The metering in SF7 is definately a step forward with the inclusion of a VU meter. I was included in the development stages to assist with this meter and it's functionality, because I had explained a VU is a necessity for mastering to better represent how the ear perceives loudness. You can achieve what you are asking for by adjusting the metering settings within the preferences. I was not so familiar with the balistics of an actual VU meter, so I recommended to Sony that they included an Engineer who was my instructor when I first started engineering. He happens to be a Motown mastering engineer and had used a VU meter extensively for Motown in their hayday and what became known as the "Motown Sound" of that era. The final VU meter according to him was the best he has ever seen for a software representation of an actual VU meter with the ballistics correlation. The only further recommendation that we included was a trim control on the user interface for the VU meter. This may or may not happen for future releases, but is already possible with the adjustment settings within the Meter settings on the preferences. So it's basically a UI issue at this point. 2. I have never had any need for any of these functionalities, and therefore can not give any feedback of what is lacking 3. You are absolutely wrong on this statement. This does not say the engineer is an idiot. If anything it shows that the engineer works in a safe manor. This feature was implemented so users would have this functionality when working with a mult-track editor like Vegas. Therefore, you can open a file within a mixing project in Sound Forge. Do processing in Sound Forge, then SAVE, then go back to Vegas and hear your changes within your mixing project. If at that point you decide you don't like the changes within your mixing project you can go back to Sound Forge and UNDO and you are back where you started. 4. Sony has no control over whether a plugin functions properly within their apps. If a plugin is developed so that it abides by the DX functionality specs, then it will work properly within Sound Forge. If a plugin was not developed properly, the only thing Sony can do is try to work around that plugin and it's improper functionality. NOT A PROBLEM OF THE APP, IT'S A PROBLEM WITH THE PLUGIN DEVELOPMENT. 5. The Sound Forge SA definately has feature enhancements, by the user being able to do a screen capture of an existing file or REAL-TIME INPUT, then being able to have that screen capture on the SA while looking at your current file you are working on and comparing it. This is a great feature for mastering engineers like myself that compare EQ spectral curves and then have to make EQ adjustments to make your songs sound spectrally similar, so all the songs sound like they belong together on the same CD. This can also be used in tuning acoustical environments, which I also use for tuning studios and vehicles. Obviously you are not familiar with this functionality, therefore you have no need to comment like I have in response #2. The only functionality which I think is missing is an "averaging" adjustment, so you can have the SA react in the same manor that a VU meter does. This is on Sony's feature requests list already. It's obvious by your statements that a lot of the features in SF7 are not within your working environment needs. They are within mine, and I'm sure quite a few other users. When I was referring to, "show stoppers", this is referring to bugs within the app itself. Not features which you think are missing and obviously have not even bothered to open the "preference" folder to adjust them to work with your working environment. The defaults are setup to work how the majority of users would use them, but are able to be changed for other user requirements. What else can you ask for? I am not familiar enough with "Unicode", because I am not a Software Engineer/Developer. But it seems that most audio apps are going to the Unicode format and only supporting Win2K and WinXP. So according to you, Steinberg, Aobe Audition, Cakewalk, and now Sony don't know what they're talking about when it comes to Unicode. I'll place my vote with those folks who do this development on a daily basis, instead of yourself who seems to be not so informed at this point like myself about the functionality of Unicode based software. I'll let Peter have this further discussion with you, I am sure Peter has the expertise with this information. red |
|
Subject:RE: SF7... do I need it?
Reply by: Spheris
Date:11/30/2003 11:31:43 AM
Actually Red, none of the above companies are being called on the carpet about whether they are aware or even familiar with unicode. I'm speaking to the fact that it has been overused (mostly by rumour speculation) to describe program eratta and changes to licensing structures within internal components. That comes with the territory of change. Nothing more really. And again, it'll work out as Sony rolls their line completely over to their new structure. Unicode or not. As far as SF7's viability. We have our differences of opinion on it. Nothing personal as you use it in likely a different way than most here (myself included) its an addon editor for me with ACID. And an impressive one at that and appreciate its simplicity and function every day. It's true, there are some interesting ideas developing as it advances. But I'm not here to advocate or not advocate one way or the other. It's that simple. The lead of the topic was opinions and advice on whether to make the jump. You gave yours, I gave mine. Neither is any less or more valid. Only the lead poster knows for sure if those features or lack thereof are in their best interests to justify the expense. And I'd love a dialogue with Peter, openly or otherwise about the ins and outs of unicode. On a real world use basis. Which is not the case with the speculation ongoing on the forum to explain some of the errata. But so we're clear on this and everyone can be satisfied - I'll clarify one step further. The errata in question has to do with the various hive migration errors. some idosyncratic and others - user errors The license issues of export plugins etc, some again user error and others unexplained The plugins themselves suffering the same at random. None of these things are directly related or even tied to the unicode element of the app itself - THAT is the heart of my point. Peter and the development team do not deserve to take heat or Sony to take on the "steinberg" perception that their apps are becoming less compliant with one another - rather than moreso. Place blame on user error or application errata, or better yet on licensing/branding issues involved in corporate buyouts (which is where the majority of it is) - where it belongs, not on an unrelated and non-issue like character set translation and developer environment optioning. Peter is aware of that as well as I am. But it is a moot point as Peter has his day job as a developer and I have mine. We can talk shop endlessly and somewhere between our combined knowledge are all the answers to all the ins and out of it from both perspectives but I doubt either of us have the time for all that. My point was to put a brake between perception versus reality of function in the case of what it would have to do with various things its being blamed for. It's not fair to the devlopment team to take that kind of heat for what is not their doing. And makes for a poor perception in the users as some are still contemplating the ramifications of updating not only their apps but OS structures to accomodate those apps. The means to remove market fear is to either allay or give the reality of the pro and con of the changes. I'm not an MBA, but around 40'ish. I hope I've gained a little business common sense. Fair enough? |
|
Subject:RE: SF7... do I need it?
Reply by: Spheris
Date:12/1/2003 4:33:11 AM
Red, I gave it some thought and have a few things to redress to you. "It's obvious by your statements that a lot of the features in SF7 are not within your working environment needs. They are within mine, and I'm sure quite a few other users. When I was referring to, "show stoppers", this is referring to bugs within the app itself. Not features which you think are missing and obviously have not even bothered to open the "preference" folder to adjust them to work with your working environment. The defaults are setup to work how the majority of users would use them, but are able to be changed for other user requirements. What else can you ask for?" As a beta tester, it should have been obvious to you that certain things would not be so familiar much less if working in the previous version. It would not seem to have done much beyond disappearance. The RMS inaccuracies are a bit more than noodling with the preferences as previous threads have pointed out. I agree. Some features are outside of my interests or day to day uses. Others are simply not "quite there: yet. Some are questionable in value at all. 24p support being primary as it should have been in the 6.d update to correspond with the acid and vegas updates adding corresponding support themselves. That much is indisputable from a common sense standpoint. Thankfully mainconcept does sell a very servicable dv codec of their own that plugs into and fills that oversight very well. What to ask for. Only one thing - unity and one less plug in folder. That's really it for right now. I'm sure I'll think of something else later. "3. You are absolutely wrong on this statement. This does not say the engineer is an idiot. If anything it shows that the engineer works in a safe manor. This feature was implemented so users would have this functionality when working with a mult-track editor like Vegas. Therefore, you can open a file within a mixing project in Sound Forge. Do processing in Sound Forge, then SAVE, then go back to Vegas and hear your changes within your mixing project. If at that point you decide you don't like the changes within your mixing project you can go back to Sound Forge and UNDO and you are back where you started." Actually Red, that was a subject statement of my personal observation and perception of the non destructive marketing material. Not anything else see top of the thread - he was asking for opinions and perception on the cost effectiveness and functionality of the upgrade. 4. Sony has no control over whether a plugin functions properly within their apps. If a plugin is developed so that it abides by the DX functionality specs, then it will work properly within Sound Forge. If a plugin was not developed properly, the only thing Sony can do is try to work around that plugin and it's improper functionality. NOT A PROBLEM OF THE APP, IT'S A PROBLEM WITH THE PLUGIN DEVELOPMENT. Non sequitor, never mentioned - has nothing to do with anything that was said in any context to any reply i have made thus far, the only plugins mentioned are the sony/sonic foundry split that continues to be a burden and iritation to some. Again a subjective thing, not altogether the end of the world. But an iritation and notable for that. Upto the individual to assign its priority. "I am not familiar enough with "Unicode", because I am not a Software Engineer/Developer. But it seems that most audio apps are going to the Unicode format and only supporting Win2K and WinXP. So according to you, Steinberg, Aobe Audition, Cakewalk, and now Sony don't know what they're talking about when it comes to Unicode. I'll place my vote with those folks who do this development on a daily basis, instead of yourself who seems to be not so informed at this point like myself about the functionality of Unicode based software. I'll let Peter have this further discussion with you, I am sure Peter has the expertise with this information." This point has no purpose or relevance to the post or subsequent reply to Peters query about unicode and its relation to the errata in 7.0 or its changes in structure relational to the existing foundry applications. Except to make you sound like a schill. Keep the ass kissing to your correspondence with the beta test lab. Too many here get too iritated with your "company poster boy" promotion for it to profit you much. Leading anything said here to a false conclusion about unrelated companies and their doing (accidents or otherwise) with updating to the momentarily current application programming protocols or any judgements being made upon them had little to do with this as much as to remove the "bogey man" perception that unicode has become here lately. Nor to call Peter or the development team to task for anything other than the standard errata that comes with any (ANY) commerical application and some additional nonsensical marketing decisions made by Sony that are really out of their control to do much about. Poor Red, very poor. You are absolutely right, you should leave programming discussions to those who know a little about it. Stay with research into closed space acoustics design and mastering, where we are familiar with your talents and formidable insight/knowledge of the subjects. On any given day, I will concede your knowledge of those subjects far exceeds anything I would pretend to know or likely will ever have the free time to learn in those particular things. For the help and advice you have offered me in the past on those subjects I have been and continue to be grateful. The last word on unicode -It is an ISO standardised set of characters,symbols and glyphs. Nothing more and nothing less. And to the naked eye of the end user, transparent to you and your use of the applications and OS's supporting them as your common alphabet - if done correctly at the integration level and that IS about it. The exorcism is over and the "bogey man' has left the building. Now we can get back to lives already in progress. |
|
Subject:RE: SF7... do I need it?
Reply by: Rednroll
Date:12/1/2003 6:14:20 AM
Spheris, Most of what you said went in one ear and out the other. That's not because I was trying to ignore your statements, I just get the feeling you're trying to get poetic in nature with your sentences and your statements are very vague without a focal point. Or maybe I need to reread your statements 10 more times before they will start to absorb? A primary example is in your your statement "5". You start off talking about 24p support then somehow wander into criticism about the spectral analyzer. Are these 2 things related? Spheris said: As a beta tester, it should have been obvious to you that certain things would not be so familiar much less if working in the previous version. Uhhhhhhhh????? If a train is leaving at 2:00 traveling at 75MPH, then Who's on first? Speris said: "This point has no purpose or relevance to the post or subsequent reply to Peters query about unicode and its relation to the errata in 7.0 or its changes in structure relational to the existing foundry applications." Is this really one sentence?? Let's talk about "errata" and could you put it in a sentence form to give other users a visual representation.....oh wait, you just did. Come on now. How can we have a constructive discussion when you reference other posts which, may or may not be factual in the first place? How can you make a solid statement using words like "Certain"? I'm an degreed engineer, and if I was presenting information which is vague, non factual, and without supporting information, I would be out looking for a new carreer right now. Or do you believe everything you read without checking the facts for yourself? Or are you just the spokes person for all these other burdened users? Spheris said: "The last word on unicode -It is an ISO standardised set of characters,symbols and glyphs. Nothing more and nothing less. And to the naked eye of the end user, transparent to you and your use of the applications and OS's supporting them as your common alphabet - if done correctly at the integration level and that IS about it. The exorcism is over and the "bogey man' has left the building. Now we can get back to lives already in progress. " Thank you, Now this makes sense to me and helps clear the air. |
|
Subject:RE: SF7... do I need it?
Reply by: Spheris
Date:12/1/2003 7:24:01 AM
Nice try Red, Very poor again, that you could not come up with better than that. You may be able to cow some of the people in the forum. I am not one of them. Your status as a beta tester only makes you a willing guinea pig. Yet another machine to inject code into and stand back and click the stopwatch to see pass or fail. Nothing particularly special and rather plentiful to people like Peter and myself - a necessary evil to development purposes. So best to use that razor charm on someone else, you get more mileage from the ones that will oooh and ahh that position. However, jotting out a reply at that hour of the morning, without coffee or much in the way of sleep. I can forgive myself a bit for academic english (i.e.: mouth runneth over). I can depricate myself much more ably than you and it's actually a bit funnier to hear it from myself. But, I'll try to put it into a haiku form next time for your benefit, if I can remember the verse/line order and tempo. The idea got across, however, to you - as your reply so aptly shows. Yes, I'm a smart ass with an arcane sense of humour, and well aware of it. Keeps assistants and guinea pigs in their jobs here where I work. Probably keeps you in your status as well if their DP runs like any other one. take good care Red Better sport sparring with the other natives Discussion is closed |
|
Subject:RE: SF7... do I need it?
Reply by: Rednroll
Date:12/1/2003 9:46:11 AM
Spheris, I pointed out 3 wrong assumptions that you have of the programs functionality. Why would I further consider any information presented by you to be legit that I'm unfamiliar with? Call me a guinee pig if you like. Obviously, I'm a guinee pig because I've used the software for a long time along with the rest of Sony's software product line being a recording and mastering engineer. I develope audio products for one of the largest audio companies in the world and work with Software Engineers during development on a daily basis. They rely on my feedback from an audio and user interface perspective because I have expertise in these areas with real world applications. I rely on the Software engineers to do the right thing in doing the programming. If their coding doesn't do the right thing, I can explain to them why their interpretation was incorrect. Similar to what I do being a beta tester for Sony. So in other words one side can't exist without the other. I can see in your opinion that you think you're at a higher level of the food chain and therefore refer to me as a "guinee pig". So King Software programmer, tell us what knowledge you have on Fletcher Munson equal loudness curves, speaker intermodulation, differences between tube distortion and transistor distortion, how was the decibel first used, how the ear percieves volume as a mathematical representation, audio imaging within an acoustical environment, Petroff filter techniques to improve imaging, how to mic a kick drum to get the best isolation and acoustical enjoyable sound(ie placement, mic type, isolation techniques), how to use multiple micing techniques and reduce phase cancellation, how to link multiple studios together via 3D-2. Please, get back to me on these things, and then refer too me as a guinee pig once again. |