What editor do you recommend for Windows 10 64bit?

[Steve Bolivar]

But I would like to mention Acoustica, from Acon Audio. It's cheaper than the big ones, yest very professional, and they are in the process of making a new version with some very interesting features, that should be out soon. Besides, it follows closely the Sound Forge paradigm, which has been my favourite in Windows since ever.

This looks really nice. I'll probably be switching from Sound Forge to this with my Win10 build later this year. Acoustica 7 should be out by then.

[thecontrolcentre]

I keep hoping for an update to Sound Forge so it supports 64 bit plugins ...

[jabe]

Wavosaur's out, being from NCH. Once bitten, and all that.

Old Steinberg progs don't work on newer Windows, so I shan't be putting any more cash their way.

Acoustica looks nice. I'll try the basic edition. Otherwise it's either Wavelab 4 on a machine from the dawn of time (I've kept several for such an eventuality), or Audacity.

[fmr]

... or Audacity.

I tried Audacity several times, but somehow, I can't help disliking it. The way it handles plug-ins, especially, is very convoluted and outdated. Seems like they don't want us to use other plug-ins besides their own.

[bustedfist]

Old Steinberg progs don't work on newer Windows, so I shan't be putting any more cash their way.

I multi-boot with hidden partitions. I have XP through W10 plus a couple of flavors of Linux all on the same machine and all versions of Cubase since SX3, spread about. I love LE1.0.7 best, no copy protection and for firing up and capturing an idea it's lightning quick.

[QuantumMusicality]

quality of process benefits from a true 64bit digital audio process

Just a heads-up, that wasn't what was being argued above. It was 32 vs 64-bit Operating System and consequently applications.

The big reason for x64 here will be, a lot of plugins aren't made in 32-bit anymore.
I'm not sure why one would need more than a couple gigs RAM for audio editing...

Man, I am disheartened to say the least. I had a sincere posted reply to your reply that I pretty much carefully worded, and finished apart from proof reading, that had taken me just about all day today to write. I am at work and just get little bits of free time here and there when I can concentrate on posting. Hit the submit button and lost everything I wrote to you. I guess the system logged me out, and when O logged back in my post was no where to be found.

My reply pretty much centered around the fact that I didn't understand what you meant.

I have never been as computer science steeped as I'd like to be, but I have found that in my own DAW world, according to my own experience and how I specifically use the DAW for creating, a 64bit OS is critically important to my own audio big picture. My question with respect to an audio editor that was 64bit in nature was posed in direct relation to the fact that the editor that I end up using will be implemented on my current DAW machine which is W10 64bit. I wanted to determine how important it would be for me specifically running the machine I am running to use a 64bit editor. I know know that it's (64bit) pretty much industry standard, industry wide.

What did you mean about the 32bit vs.64bit debating? Are you stating that the debate centered on a 32bit plugin sounding as good as 64bit plugin according to each's internal process no matter whether the OS is 32 or 64bit? Or...?

Could you explain what it is that was being argued, and what relevance that had to my initial post's question?

[bustedfist]

Could you explain what it is that was being argued, and what relevance that had to my initial post's question?

Don't worry about it, it was a very small unimportant factor as to whether 32bit apps could use the 3GB switch in a 32 bit OS to take advantage of any RAM not used by the OS for other processes/ programs. Then it devolved into an arguement, most likely from those not able to upgrade and stuck in their mire, the amount of RAM needed for audio processing, failing to take VSTs or any other workflow than theirs. Sorry that distracted you.

You did the perfect thing, IMHO. The integration of Cubase and Wavelab is killer. When you see how powerful it is and the tools at your fingertips you'll be happy.

Re; long posts, write them in notepad and copy/ paste to posts or use Ctrl/A and Ctrl/S a lot.

[jancivil]

People went back and forth about 32-bit vs 64-bit operating systems and the consequent 32-bit and 64-bit hosts and the consequent 32-bit/64-bit plugins. This was not about a 64-bit audio engine.

32-bit OS/DAW Hosts can only access so much memory. My experience of Cubase was around 2 GB and it starts to become unstable. This '3 GB switch' was brought in, which afaik is a property of Windows OS.
Just applying effects plugins to audio, I didn't so much find Cubase 32-bit a problem except in extreme cases, a hundred tracks or something. I would run into the RAM ceiling with only one sample-based instrument, however.
I ran Vienna Ensemble Pro since ca. 2010, which can run a 32-bit and a 64-bit 'server' plugin host simultaneously.

I'm using plugins today that are strictly from 64-bit; & I have almost nothing that requires to be hosted 32-bit.
64-bit addresses more RAM than anybody has. So that whole limitation was superseded. And for a few years now, development for x64 OS and Hosts has more or less superseded 32-bit (aka x86).

The audio engine 'bit' is a whole 'nother matter.
viewtopic.php?f=259&t=407794

[kb420]

I just bought Cubase 9 Pro back in December, and I just got Wavelab Pro 9 a few weeks ago when they had the 40% off deal. I must say that so far I am very happy with these two Steinberg products. I think that once you really get a handle on both, you will really appreciate them.

[UltimateOutsider]

I am yet another Cubase/Wavelab user. (Currently at Cubase Pro 9/Wavelab Pro 8.5.)

When I was working with Ableton Live as my main DAW I actually had Wavelab set up as the external audio editor (requires a little extra work to make that happen with Wavelab, at least on Windows), but I ended up moving back to Cubase as primary DAW anyway. Cubase has much more extensive audio editing/processing capabilities than Ableton Live (there is some functional overlap with Wavelab), but Wavelab is very fast and powerful for audio editing, rendering, analyzing, etc.

Also, I'm glad 64-bit has finally become the industry norm. I've definitely needed the extra per-process RAM it allows in several DAW projects, and I'm happy to be free of the many headaches involved with managing multiple platform versions of plugins and apps on 64-bit Windows.

[nIGhT-SoN]

Right now for file editing I use Wavosaur, VST support (vst 3 you have to add your plugins manually and some don't work), is 64bit and the most important thing, it's free.

[inkwarp]

+1 wavosaur.
hardly any footprint and does most things just as well as soundforge.
not saying i don't like SF, i love it, but it's nice to have a really fast and light editor in tandem with various DAWs.

[inkwarp]

Wavosaur's out, being from NCH. Once bitten, and all that.

what are you on about?
wavosaur has nothing to do with NCH.