Subject:20 Things I wish Sony would fix in SF9.

Posted by: jeffjams

Date:7/9/2007 4:53:06 PM

As someone who make a living putting sounds into games and editing a hundred or more radio/TV spots each year, I think I have now given Sound Forge 9 a pretty fair workout.

But, Sony, I'm having a really tough time warming up to this latest upgrade. And, I feel compelled to say so.

Yes, there are some cool new functions I've been trying to learn and utilize...to give this version a fair shake. But I can't help sensing that you folks have added, tweaked or taken away some things at the expense of many of the program's smaller "nuts-and-bolts" editing functions. Somewhere in another thread on this forum, someone asked, "What were they smoking?" I couldn't agree more.

Bottom line -- in it's current state, I'm finding Sound Forge 9 to be less efficient for my editing needs than previous versions.

Here are 20 reasons why:

1. Curser behavior...for this one, I'll defer to the chorus of complaints in various other threads throughout this forum. Moving right along...

2. Loop editing...it used to be, without fail, I could zoom in on the tail end of a selected area, hit play, then grab and move the end of that selection. In SF9, as soon as I hit play, the file jumps to the
beginning of the selection. This is quite awful!

Once in a blue moon, I get the program to behave the old way. But that's about as reliable as my ex-girlfriend Judy.

3. Loop editing...again in earlier versions of SF, I could grab the front end of a selection, move it and listen to the loop edit point as the file would automatically pre-roll from slightly before the back end of the selection. I have yet to find a way for SF9 to do this -- and it is driving me nuts!! Please fix this!

4. Stereo-to-mono conversion...it used to be, I could right-click on "stereo" down in the lower right, bring up the menu, click on "both" to combine right and left channels and expect the gain to remain at the same level.

However, in SF9, you have apparently changed the default level from 50% to 100% per channel. I now have to go to the "Process" menu or "Swap Channels" toolbar icon, which adds an extra step to the
process. If you continue to promote editing efficiency, then please put this back the way it was.

5. Save preset button...ergonomically, this is now in a really B-A-D place. I've already ruined several old custom presets because I aimed for the pull-down menu arrow and missed, hitting the "save preset" button instead. Then, because I was too busy (like many of us in the trenches) to pay attention to the pop-up prompt, I accidently hit "OK." The way it was in SF7, with the "save as" button further down on the right was far safer.

6. After a decade-and-a-half of having "w" and "e" keys as the default go-to-start and -end functions, Sony, you took away these defaults. Fortunately, after hunting down "customize keyboard," I found I could fix that one. But honestly, Ctrl-Home is at opposite corners on a laptop keyboard, which I don't find to be practical
in a crunch-deadline-edit situation.

Sorry, I'm not a fan of Sound Forge looking and behaving more like Vegas. I have Vegas. I wish it behaved more like the older Sound Forge.

7. Mix/replace...here's one that really slows down my efficiency. The program no longer remembers which levels I used in the previous mix. I find it rather tiresome having to move the destination level from "inf" every time I want to paste something into another file. Please, at least, give this function some memory.

8. Mix/replace...another bugaboo about this function...we used to be able select an option to effect the entire destination file. For instance, I could paste a small piece of audio into a larger file and effect the entire larger file. Unless someone can enlighten me, I have yet to find a way to do that in SF9.

9. Mix/replace...Whatever happend to the ability to drag a mono file onto a stereo file and have the mono file automatically mix across both left and right channels? Or multiple channels, for that matter?

10. Preview looping in process windows...here's another one that went the way of older versions. I keep forgetting I have to hit the "Q" key BEFORE I bring up a process if I want to loop the sound while I make adjustments.

Perhaps a checkbox could be added to allow one to turn on looping AFTER pulling up the process window.

11. Looping during real-time previews...particularly with third-party plug-ins, I sometimes hear serious snaps as the loop restarts. Perhaps it has something to do with ASIO drivers. I don't know. But, this annoyance never happens in SF7, on the same computer using WinXP. Let me add that SF9 is MUCH slower in responding to
adjustments to pitch, pitch bend and volume changes during previews than SF7.

12. Time-stretch...the preview used to play precisely the selected area -- nothing more or less. Now, Sound Forge no longer plays just the selected area. Version 9 plays about 1.5 seconds beyond the selected area of a file, playing a piece of the uneffected area. This never happens in SF7...only a slight pause, which
I find to be far less distracting when trying to make serious editing decisions.

I tried playing with all the selections in the "Preferences/Previews" menu. Also tried deselecting "Real-time." Nothing changed. Please fix this!

13. Acoustic Mirror...same thing as in item 12. Again, during a looped preview (SF7), I find the pause of a second or so to be far more desirable than playing a piece of the uneffected area of a file.

14. Graphic fades...your "[Sys] -6 dB exponential fade out" preset has a point that is quite a bit out of place, compared with the same preset in SF7 and before. Please fix the ugly bump in this curve.

15. The old "play device" window is gone from the toolbar selections...switching sound cards used to take two mouse clicks. Now, you have to right-click, click on "preferences," click on "audio," click to pull down the audio card menu, click to select. Let's see...that's 5 clicks...6 and 7 if I have to switch my
M-Audio FW 410 from ASIO to the Wave driver to finish up 22k game files. Is that more efficient?

In fact, while you're at it, could you add a "play device" window to the Vegas toolbars?

16. Snap to zero-crossing...can't get close to the target crossing and sort of "let it drop" anymore. I now have to drag the curser all the way to the intended edit point. This would be less of an annoyance if you
could just give the snap a bit more "umph!" It's often hard to tell if my curser has snapped in at the right place.

On a positive note, being able to snap to crossings on multiple channels is a good change. Still...more umph, please!

17. Snap to zero-crossing...doesn't find the first zero crossing in a file like it used to, especially if
there's a bit of silence at the start of the file. Please fix this.

18. Pitch shift...this process now tends to stick terrible artifacts at the ends of previews and, ultimately, into newly-processed regions. Some are worse than others. Regardless, each time, it sounds as if the artifact is a small piece of the unprocessed audio from somewhere within the selected area.

19. Batch processor...this is another item that doesn't remember previous settings like it used to. I have click through all the darn buttons each time I bring it up, because the default settings are not what I often use. Efficient? Hm-m! Please give this little Frankenstein better memory.

20. Zoom out to "time normal"...the Ctrl-down key command used to completely zoom out the verticle as well as the horizontal zoom. Now, in SF9, it only zooms out the horizontal. I'm going to wear out my mouse scroll wheel if you don't put this back the way it was.



Oh, did I say 20? Sorry. Here are some more:

21. My graphic fade curve presets (I have many) did not carry over to SF9. An annoyance? Yes. Fortunately, it seems to be the only set of my often-used custom presets blocked by version 9.

22. After saving a new preset in Sound Forge 7 and bringing it up in the version of Preset Manager installed from the SF9 disk, Preset Manager now crashes. I had to revert back to an earlier backup file, then rebuild that particular preset in SF9 to keep the PM from crashing. Looks like a bug somewhere.

23. I agree with another forum member, the phase scope is small. However, I usually refer to my Waves plug-ins for help there.



I know...it's human nature to resist change. But, hey! I finally got the hang of the new "drag selection" behavior. And hopefully, some of the items above are mere bugs that will be fixed in upcoming updates.

But, overall, some things just plain worked better right-off-the-bat in earlier versions. Which makes me wonder, since I skipped from version 7 to 9, can I upgrade back to Sound Forge 8?

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: porkjelly

Date:7/10/2007 6:42:00 AM

I second many of these suggestions. As for Batch Processing, I'm surprised that this feature wasn't revamped (or improved) for SF9. I still have to press the REMOVE button to delete a file (instead of being able to use my delete button). On top of that, there's no way to delete multiple files. Also, clicking the file tab (or any tab) doesn't sort the files accordingly. Then, if I'm working halfway down a long list of files and I delete one, I'm brought back up to the very top of the list and have to scroll my way back down to find the spot I was just at. And finally, saving the batch session does not save the files I have qeued up to process. All this is very frustrating, and I end up using Batch less often than I would like.

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: ForumAdmin

Date:7/10/2007 9:24:08 AM

That's quite a list. Apologies to those who are reading in thread mode, but I'm not going to duplicate all the original items. Here goes:

1) This will be addressed in the next update.

2) Unless I'm misreading you, this behavior hasn't changed since 4.0 (I just tried it). Perhaps you are looking for a way to disable scrolling? Try Options->Scroll Playback (F6).

3) This is a bug. I'll check it out.

4) I agree, I'll look into an extra radio button or restoring the pad.

5) Noted, but not likely to change in 9.0

6) These were actually removed in 8.0, and, as you said, you can easily re-bind them.

7) This will be addressed in the next update.

8) It was called "Apply destination volume to overlapping area only", and has been a source of confusion for new users for as long as I can remember. We are considering restoring it, but I'm curious to know precisely what you use it for.

9) You can still get this behavior this via a clipboard mix or by dragging into an existing selection (Mix Replace). You can also adjust channel selection once the mix dialog is up. It is just no longer directly accessible via drag. With multiple channels there's no obvious way to allow both behaviors based solely on mouse position (as was done in previous versions). The current drag behavior is the most obvious and expected choice, particularly in the multi-channel case.

10) You can toggle loop preview from the dialog's context menu. Right click in the blank area under the "Preview" button.

11) Easily verified if you set your driver prefs to whatever you are using in 7.0. As for the delay, the default non-realtime preview limit is now 10 seconds instead of 4. You can change it in Options->Prefs->Preview.

12) It isn't playing/processing unselected data. The cursor is just traversing the additional length introduced by the stretch, which yields a rough visible indication of how much the adjacent data will be shifted.

13) Ditto.

14) I'll check it out. I assume it is the fourth point?

15) The Play Device toolbar is no longer available because device prefs also include channel routing and, potentially, multiple devices. Note that you can re-route individual channels by clicking on the meter headers. We're considering something like routing presets to solve this issue, but that likely will not appear in 9.0.

16) It is obviously now a soft snap, and we may need to expose a "sensitivity" setting for this one. If you are brave, hold down Ctrl+Shift while selection Options->Preferences, and adjust the entry labeled "Zero Cross Snap Width (pixels)" to something like 100. Alternatively, there are new "snap now" options in the Edit->Selection menu. "Snap to Zero" and "Snap Edge to Zero" snap and do not re-snap if already on a zero crossing. "Extend to Next Zero" and "Extend Edge to Next Zero" is the old behavior that always snaps to the next(previous) crossing(s) regardless of whether you are already on a zero-crossing.

17) Not certain I'm following what you mean here. Can you elaborate a little?

18) Turn off the edge fades. You can save the current edge fade settings for all effects from the context menu in the "More..." section of the dialog.

19) Any reason you aren't saving batch jobs? You can always add or remove files after loading a saved job.

20) This will be addressed in the next update.

21) I'll check it out, but with the new curve types (right click on the envelope segments), you may want to re-formulate your presets anyway.

22) Interesting. I'll install 7.0 and check it out.

23) This will be addressed in the next update.

Thanks for the feedback.
J.

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: porkjelly

Date:7/10/2007 10:41:32 AM

Regarding problem 21, my Graphic Fade presets did not carry over either, even after I re-installed Windows+SF9 twice. I can see them in Preset Manager, but they're not there in SF9. I reported this bug in an earlier SF9 bug thread but no one else seemed to be encountering this problem at the time.

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: jeffjams

Date:7/10/2007 11:05:53 AM

Thank you, J, for the quick response. I really appreciate it.

I'm tied up today with deadlines (spots going out to WGN radio and other stuff). But I will try to clarify several of my points, particularly item #2, in the next day or so.

I also want to go through your suggestions to make sure I haven't overlooked something. It's also heartening to hear that some items
are already being addressed.

Thanks for listening.

Subject:Q

Reply by: rraud

Date:7/10/2007 11:44:48 AM

Good post Jeff.

Regarding:
8) It was called "Apply destination volume to overlapping area only"
I (used to) use this for quickly flying in some applause or other without resorting to Vegas.

24? Loop preview in the plugin chain or a process window did not used to engage the main timeline loop. This has caused me hours of irritation and extra work having to redo or fix recordings back to analog because I forgot to hit "Q" again.
So like many of us, I reverted back to SF-8.

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: TheDingo

Date:7/10/2007 1:26:21 PM

ONE MORE FOR THE LIST

Please improve the accuracy of the Time Stretch effect. I often have to adjust the timing for hour long audio tracks for the videos I shoot. ( digital recorders and camcorders often run at slightly different speeds )

For example, the camcorder's audio track might be 56:23.014, but the same audio source from a digital recorder might be 56:19.342.

Trying to adjust the length of the digital recorder's audio track so that it matches the length of the camcorder's audio track is next to impossible using Sound Forge's Time Stretch effect. It's just not precise enough.

So I end up using the TimeWarp effect in the $50 GoldWave audio editor instead, which works perfectly. If I want the final audio time to be 56:23.014, that's exactly what I get using the GoldWave editor. I just wish Sound Forge could do this too!

...I have the same kind of beef with "Sharpen" effect in Vegas 7.0e. You can set the "Sharpen" effect to 0.000, but it STILL SHARPENS the image. There's obviously something messed up in the code for the "Sharpen" effect, but Sony still hasn't fixed it yet. ( I think I asked for this way back with Vegas 5, and this bug is still around in Vegas 7.0e! )

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: jeffjams

Date:7/11/2007 2:42:49 PM

In response to J, the Forum Administrator, I'll refer back up to my original list. However, for sanity's sake, I'll just clarify one item at a time from here on down.

Also, I'll use the term "classic behavior" to describe anything I'm used to doing in Sound Forge 7 and earlier (I've been on-board with this program since 1995).

With that said, let's jump right to Item #2...loop editing:

Forum Admin, you asked if I might be looking for a way to disable scrolling. Some users love scrolling.

Scrolling drives me crazy...I have always disabled it.

Let me try to describe more clearly what I do. First, I'll take a lengthy file. With the mouse, I'll click and drag to make my rough selection. Using the mouse scroll wheel, I'll zoom in fairly tight to get a good look at the waveform...tight enough that I don't see either end of the selection.

I'll sidebar here: the "classic behavior" would allow you to zoom in on the curser. In other words, in SF7, if I made my selection from left to right, I could scroll and zoom in on the curser position at the right end of the selection. If I selected from right to left, the zoom would take me to the left end of my selected area. To go to the opposite end, just click the "," key to toggle back and forth. For me, it's been a fast and efficient way to start roughing out a crowd or tune loop.

In SF9, the zoom takes me to the middle of my selection. If I'm working on a loop, that's NOT where I want to edit. And, then, when I toggle to go to an end, the default setting takes me to the beginning. I could learn to live with that, but 90% of the time I start working on the back end of a selection. This means two extra clicks I didn't to have to make before. Multiply that over hundreds of files that go into some games and that starts to become an annoyance.

The big problem happens when I get to the back end of a selection (still zoomed in tight, where I don't see the front end). I want to start playing the file, then move the curser to find the right loop point. It's
"Classic behavior" that has worked really well for years.

In SF9, I'll start playback and the curser immediately jumps to the front end of the selection. I have found no way to stop this jump.

Oh, there are two ways I can edit the back end of a loop. One is to zoom out enough to see both ends of the selection (can't see the zero crossings in a long file, though). The other is to start playback, grab the scroll bar at the bottom and slide it until I see the back end, then grab and slide the curser. But stop and re-start playback and the program jumps you right back to the beginning of the selection.

This is a terrible way to edit crowd, music and other sounds that must loop in games. If anyone still has a problem understanding what I am talking about, I'll try pulling up CamStudio and recording a video comparison between SF7 and SF9.

Meanwhile, in the days ahead, I will try to clarify my other lingering issues (perhaps #8 next), a response to my boss as to why I care about this (instead of just dropping back to SF7 or 8), and...of course...I'll have another list!:)

Again, thanks to all for listening.

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: ForumAdmin

Date:7/12/2007 7:06:09 AM

The first zoom issue, where the caret doesn't remain on-screen after a left-to-right selection is a bug that will be addressed in the next update.

The second behavior is also a bug that wasn't clear to me until you said this:

"Scrolling drives me crazy...I have always disabled it."

In 9.0a, when scrolling is disabled (Options->Scroll Playback), it clearly doesn't scroll, but the cursor should not be jumping back to selection start on playback. I'll see that this is fixed in the next update.

Thanks,
J.

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: jeffjams

Date:7/12/2007 3:12:47 PM

Thank you, so much, for looking into item #2 (loop editing).

I did a number of paste/mix functions two days ago for a game, so I was also thankful that item #7 (giving the Mix/Replace function some memory) is being addressed.

In addition, I think we can check off (for now), all the other items on my list up to...

Item #8: "Apply destination volume to overlapping area only"...which appeared in earlier versions of Sound Forge.

Forum Admin, you asked me what I use this function for. In addition to radio/TV spots, I produce audio for a variety of coin-op games -- pinball, redemption and crane games, merchandisers, kiddie rides, along with a couple of well-known coin-op video games. That's music, sound effects and speech for an estimated 12-15 projects this year, alone.

Many of these products have 2-channel sound systems, where only two sounds can play at any one time. To get music, effects AND speech to all play seamlessly and cohesively, you have to pre-mix an awful lot of sound elements in the game. Sometimes, effects get mixed with music, speech calls go into certain effects files...often, smaller files are mixed into larger files, where I'm used to the "classic behavior" that let me effect the entire larger file.

A lot of this is done with great experimentation. Yes, I suppose I could pull up Vegas or another multitrack editor (NOTE: the new multi-channel functions in SF9 do not help me in this area, so far...sadly). But, pulling up another program and searching for the folder and files is just not as efficient for me. If I'm staring at two files right there in Sound Forge, it's so easy to just click on one, drag, adjust gains and voila!

Two side notes: Personally, I'd rather see a multitrack editor instead of the new multichannel function, much like the old Vegas LE that was bundled with SF5. I realize that this might take away some traffic from Vegas. But Vegas has become one those "Swiss Army Knives" with so much video stuff that audio-only users like me don't really need. The last time I looked at Acid, it didn't quite fit my needs either. Perhaps it's nearing time for a "Classic" version of Sound Forge (i.e. Classic Coke) that formulates the best of the old with some of the new great features...along with the audio functions of Vegas.

THAT would get my attention.

Side note 2: I sense that HD video and surround audio has a lot to do with the direction of audio software these days (duh! Jeff). However, here's a reminder from the trenches that we, the public, are being bombarded by an increasing amount of lo-fi audio, as well. Cell phones, blackberries, i-pods, i-phones. Almost everywhere you turn...from gasoline pumps to vending machines...there's now a dizzying array of electro-mechanical devices that spew out processed audio, in all kinds of formats and sample rates.

Just recently, I got a request from a company in Taiwan to send final audio as 10.492kHz .vox files! Anyone who's worked with vox or u-law files knows it's not one "save as" step to get to that point.

The big point here? Sound Forge has always been one of the few editing programs I know of where I can handle most of the really strange stuff that's hitting our shores from overseas lately.

Sony, please don't ever lose sight of the low end of the audio food chain.

I'll try to elaborate more in a day or so on another item on my original list.

Thanks, again!

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: porkjelly

Date:7/13/2007 6:42:24 AM

Regarding my earlier post about the Graphic Fade preset bug: I just checked in Preset Manager for my presets and none of the new ones I created in SF9 are listed in Graphic Fade. Instead, only the older ones that did not get transferred show up. Very odd. Just a heads up. Cheers.

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: jeffjams

Date:7/17/2007 2:32:16 PM

Additional followup to the Forum Admin's response:

Item 9: dragging a mono file onto a stereo one. I'll learn to adapt...though, the new way still feels slower.

Item 10: selecting loop preview. Thanks for educating me.

Item 11: regarding nasty snaps during looped previews. Upon further comparison, as you suggested, I don't seem to hear them as much with the classic Wave Driver.

Regarding the second part of Item 11: I always use "Real-time" for editing (sorry, I didn't make that distinction). Here, again, perhaps Steinberg (ASIO drivers) may the culprit for sometimes erratic behavior in changes to certain edit functions?

Items 12 and 13: preview tails. Again, thanks for pointing me in the right direction. I had forgotten about the various tail data choices, because Sound Forge had always defaulted to "Ignore Tail Data" in the past.

Item 14: (not related to item 4) in the ""[Sys] -6 dB exponential fade out" preset, the 4th graphic node from the left appears out of place, relative to the same preset in earlier versions of SF. Therefore, it
looks as if this is not as smooth a fade curve as it should be.

More to come later.

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: ForumAdmin

Date:7/17/2007 3:11:57 PM

On 11, non-realtime effects are all those that are not DirectX or VST plug-ins. They won't have a "Real time" checkbox on them at all. So these processes (Normalize, Resample, etc.) are still calculated offline for preview and limited to 10 seconds (instead of 4) by default unless you disable that pref or change the value.

On12/13: Technically, it's always defaulted to Mix Tail, but previous versions did not tolerate being able to preview the mix and either ignored or inserted the tail.

J.

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: porkjelly

Date:7/17/2007 10:40:06 PM

Another oddity I've noticed in Graphic Fade: After applying/modifying a preset, the waveform no longer shows in the graph if you select Graphic Fade again. It's just a blank white grid. o-)

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: ForumAdmin

Date:7/18/2007 7:07:18 AM

This one has already been fixed and will be included in the next update.

J.

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: porkjelly

Date:7/18/2007 9:38:09 AM

Good to hear, J. Thanks. o-)

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: jeffjams

Date:7/18/2007 12:50:03 PM

Still more followup to the Forum Admin's response (I think the end of the list is in sight!):

Item 15: Any shortcuts to faster switching of sound devices (and signal routing) gets my vote. Having to go through the "Preferences" menu has always been one of the functions I've disliked about Vegas, as well. Thanks for looking at that.


Item 16: The new soft snapping. I experimented with "100" in the internal settings and found it a bit more to my liking, until I zoomed in. That's when I seem to lose the snapping totally (too many pixels wide?).

I REALLY miss not having the old "Extend Edge to Next Zero" behavior tied in with mouse drags. It's been very useful for quick loop editing...much quicker than using any loop edit window.

I could get used to Shift+Z. The problem? I often want to go back and forth with the active edge. Shift+Z only moves that edge one direction, depending on whether it's at the home or end of a selection.

Would there be any possibility of tying Shift+Z with the mouse to get bi-directional movement?

Or, perhaps it would be easier to program a "single-handed" key command, such as Shift+X, to move the active edge to the right...with Shift+Z moving it to the left.


More to come...

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: jeffjams

Date:7/18/2007 3:05:56 PM

Last of my followup to the Forum Admin's response (whew!):


Item 17: Soft snapping and Shift+Z often don't seem find the first zero crossing. This happens when I open a file I've created in Sonar -- one with only soft synths...no line, amp or room noise at the head of the track.

The "classic behavior" of earlier versions would allow me to drag the active edge of my selection with the mouse -- it would then jump to the start of that waveform.

The new soft snapping doesn't seem to snap until the second visible crossing. It's so "wishy-washy" that I often have to zoom in to the sample level to find the right edit point.

Could it be that the digital silence in this case may not be so silent? If so, then why would the old behavior work seem to work better than the new? Different levels of sensitivity?



I can cross off Items 18 and 20-23. Thanks for addressing all of those.



Item 19: Better memory for little Frankenstein (Batch Processing). Probably 80 percent of the time, I use batch processing to create MP3 files for clients. When I pull up Batch Converter 5.0, it remembers what I used in running the previous job. Example: file folder -- "same as source"; file name -- "same as source"; file format -- convert to MP3 Audio, 128 Kbps. Drag in the files...boom, I'm done.

Yes, I have two custom presets, but that's it. I don't recall ever saving a batch job. And I tend to think that bringing up an old job and clearing out files is a less efficient way of doing things.

If memory is an issue, my vote would then be for "Same as source" as the default for all three save options.

Regardless, we've covered a lot of territory here. I certainly learned a few things. Believe it or not, this is the first time I've posted to any forum since...let me think...Prodigy. So, for me to come out of the
woodwork means I'm pretty committed to helping keep Sound Forge a solidly superior editing program.

Thanks very much for the responses!

Subject:RE: 20 Things I wish Sony would fix in SF9.

Reply by: jeffjams

Date:7/18/2007 6:35:24 PM

Back to Item #11: The snapping that I'm hearing during loop previews? As I write this, I am listening to a timpani hit+roll, previewed in loop mode through the Waves Renaissance Reverberator. The attack of the timp is intermittently being cut off, which, of course, causes a snap.

This is with the Digi002. Is it possible to access the wave drivers for the ProTools hardware (as I believe that's all we could do in SF7) in a future update? I noticed the M-Audio I/O allows either ASIO or wave drivers. Or is this a Digidesign issue?