Adobe Community: What we love, (and don't), about CS6

Currently Being Moderated

What we love, (and don't), about CS6

May 30, 2012 6:56 AM

I am thrilled with the progress that Adobe developers have made with CS6. The control surface support and metronome were my "deal breakers" for CS5.5, but in CS6, there is alot more to love. It has crashed on me once in the last three days... when I was adjusting an effects plugin on the fly.... but other than that, it seems very stable on my AMD 6 core system running 32 bit Windows 7 with 4G ram. I must say that the improvements over and above Audition 3.0 were significant enough for me to pay for the upgrade, even through full MIDI support is still on the horizon. It would be nice to have it, but it is not a big deal right now for the way that I prefer to work. I look forward to next editions, that are a bit more processor effecient (Audition 3 seems to play a large-scale multitrack configuration that CS6 will not. In fact, CS6 seems to handle fewer plugins at a time than its predecessor. No clue why this is.

I have even learned to live with the inability to change the tint of the user interface from various shades of sick brown to an almost metalic grey to death pallor, I have opted for the closest to flat metalic grey that I can get.... 3.0's ability to change UI color alowed me to make my visual display more appealing (at least to my admittedly quirky tastes).

All said, I am very happy with this software. The control surface support is leagues ahead of the legacy cool edit support that was in 3.0. Multiple control surfaces with android and ios devices working harmoniously together. This is the way that the control surface universe should be for bargain-seeking kludgers like me.

Keep up the good work. I was pleasantly surprised with the progress you are making on this. I'm sure that many others must feel the same. Perhaps they too will express their gratitude to the Adobe Audition development team for their impressive work, and encouraging them to keep moving forward to an even more impressive CS7.

JPK

hmmm.. it says mark my discussion as a question. Perhaps the question is, "Why do you love about the new CS6, and what would make you love it even more?"

4495 Views 44 Replies Latest reply: Kost7, Jul 3, 2012 1:31 AM

Replies 1 2 Previous Next

Currently Being Moderated

1. SuiteSpot,

Jun 1, 2012 4:35 AM in reply to klinejp

Report

Metronome is fantastic - for simple things like setting up a count in for a band
I don't know how many times I forgot to turn on the click or turn it off, blah, blah
With an envelope - its done and forgotten about

Simple but sure saves some embarrasment

Colours suck that is for sure - no I'm no fanboy of skins (what is that all about?) but give me a little dash of colour to tell the vocal track from the drum tracks - and you get the picture

Crash?
Not once - never - and CS6 has been bashed unmercifully ever since it arrived.

Performance?
Puts both Vegas and Reaper to shame and they both fly!

Give me a reference track in the manual pitch correction screen, option to lock takes on record and better highlighting of the currently selected track and what else could a poor boy ask for ?

I could go on but there is work to be done

|
Mark as:
Currently Being Moderated

2. Charles VW,

Jun 1, 2012 5:00 AM in reply to klinejp

Report

You may want to send us one of those sessions that did work in Au 3, but doesn't work in Au CS6. Also, are you using third-party effects, or only the built-in ones?

|
Mark as:
Currently Being Moderated

3. therealdobro,

Jun 1, 2012 8:07 AM in reply to klinejp

Report

I love it because it's pretty much everything AA3 was, but faster. The Parametric EQ alone makes my day - it's way better than the parametric in AA3.

What I don't like about it is temporary - I'm having to learn some new tricks - poor me (and poor Steve, who has to put up with me). When I've learned those tricks, however, it'll be mama come to papa time.

Suite Spot - it's got colors, and they're attractive. And go into Preferences>Appearance and turn the lamp way down low - set the brightness to zero or ten. Instant chic. Now, when they get around to putting colors in the Mixer View, now that will be sexy. (And very useful.)

|
Mark as:
Currently Being Moderated

4. SuiteSpot,

Jun 1, 2012 8:28 AM in reply to therealdobro

Report

Mixer view for sure but what I would like is a little strip of colour in each track so I can quickly identify say a vocal track among 20 or 30 other tracks across several screens
And if we could have this in both the mixer and MT screens that would be excellent!
As in this PT example

|
Mark as:
Currently Being Moderated

5. klinejp,

Jun 1, 2012 9:04 AM in reply to Charles VW

Report

Thanks for the response. Before I send you a large multitrack file of around 1 GB (recorded in 32 bit, 96Khz), I am doing some trouble shooting on my end. So far, I have noticed that if I have multiple iZotope plugins going at once (Spectron, Ozone, Nectar), they seem to load in the same processing core... I use native plugins, but there are others as well. So, my 6 core system starts to stutter, because one of the cores is maxed and the others are barely loaded (yes, I looked to see if there were any other CPU hungry programs running, and there were not..   This may not be consistent, however, because awhile ago the load was distributed evenly across cores. One thing that Audition 3 does flawlessly is distribute the work load across all six cores.

The other thing I am checking into is disk fragmentation.   I try to avoid this by storing all data on drives separate from the OS driver... The optimization routines I use for the system drive (file alignment etc) differ from the more straightforward approach I use on the data drives (iolo system mechanic seems to be laid out like this). I've gotten a couple more crashes, typically having to do with initializing control surfaces and on-the-fly editing of VST plugin parameters.

As for the colors: You can change the waveform colors on a per channel or group basis, which I do in order to break things up visually.   The User interface is easy to read and follow, so I'll take that over being able get away from Adobe gray. I love the fact that my control surface now lists the names of the tracks, and the VU meters work too! And, with all due deference to the clever minds who decided to make the background of the UI "Adobe Gray," (the word play is not lost on me), my impression is that the old color changing scheme wouldn't work in Mac.... but is that a reason for not letting windows users have this feature?   I'm getting used to the brownish / greenish / greyish just-got-drafted-into-the army colors.

I can't help to wonder, though, if there is a switch that could be installed that gave Windoze users more flexibility with background colors.   It would be a nice consolation prize for those of use who haven't been able to make the mac transition yet.

I'll let you know if I have more information about the plugin allocation thing. Might just be a quirk of my AMD Thuban processor.

|
Mark as:
Currently Being Moderated

6. Claude King,

Jun 19, 2012 1:07 PM in reply to klinejp

Report

Why is it that Audition CS 5.5 developers did not see, or know that the loop function is totally loopy??? This may sound a small deal, but when you work as extensively with this function as I have to, to earn my living, I find it unforgivable that it was not discovered before the damn system was launched as for sale. Further, I mentioned this months ago in one of these forums, and no corrective update has been provided? Under the circumstances, I am scared to upgrade to CS 6.

|
Mark as:
4,753 posts
Oct 26, 2006

Currently Being Moderated

7. SteveG(AudioMasters),

Jun 19, 2012 3:24 PM in reply to Claude King

Report

Claude King wrote:

Why is it that Audition CS 5.5 developers did not see, or know that the loop function is totally loopy???
I think you'll find that they know exactly what state it's in - and, as we've said before in so many words, Rome wasn't built in a day. IOW, you can't have it all at once, especially with enforced external time constraints.

So, the developers concentrated on what they knew they could fix in the time they had available. What this generally means is that if a facility isn't touched, it's because something else is planned for it, and there's no point in compromising this. A typical example of this is what happened with Groups; everybody moaned about this in Audition CS5.5, but in Audition CS6, where they've come back, they are enhanced to a state well beyond which they were previously.

Audition is a work in progress. It's not yet perfect, but it's coming on just fine.

|
Mark as:
Currently Being Moderated

8. klinejp,

Jun 21, 2012 9:22 AM in reply to klinejp

Report

I've switched to the 64 Bit version of Windows 7, and noticed that Audition CS6 only installs as x86. Does this mean that performance will be impacted by the extra translation layer that Windows 7 uses to emulate 32 bit programs on the 64 bit architecture?   I haven't noticed a performace decrement, even with Audition 3.01, although I have to run 3.01 in XP compatibility mode or it simply neglects to include effects plugins during mixdowns.    That is an odd glitch that I can't explain.   CS6 seems to run very well on the 64 bit platform, and the more I use it, the more I appreciate how well designed it is, and yes, the CS6 production team has addressed most of my CS5.5 concerns. I still want to barf at the hideous UI colors, and would really like to change the color of the user interface.   iZotope also moved to hideous colors in Ozone 5... Makes my computer screen remind me of a high tech military tank, which is far from my first choice of aesthetics, and aesthetics are important during the creative process.

I think I know a piece of the puzzle of why the program was glitching and multithreading poorly. It had to do with the fact that Audition does not change MOTU's native cuemix system when it changes sample rates. So, if you been running a 44.1 Khz session, then load up a 96 Khz session, it will try convert the 96 kHZ session to 44.1 Khz on the fly.   I've found that if I simply leave it set to 96Khz, I can generally load up 44.1 Khz files, but I don't think that allowing Audition to take control of the iso driver capitalizes on all of the formidable DSP capabilities of the 424 card., So, if I need to change sampling rates, I need to exit audition, exit cuemix, wait until all traces of them are gone from memory, reset the sample rate in cuemix, start cuemix, restart audition, and then load the sesx file with the sample rate that matches the rample rate that is displayed on my 24i/o hardware.    A bit of a hassle, but workable with some workflow planning. Throwing more speed at it didn't hurt either, as I've overclocked my AMD Thuban 1066t to 3.39 ghz and turned off the turbo mode. AMDs turbo mode was probably forcing all processes onto a smaller number of cores when the CPU load reached a certain load.   Turning it off seems to have helped.

Is Audition going to jump on the x64 bandwagon with the rest of the CS6 collection?   Seems like this would make for something of a performance increase..

|
Mark as:
Currently Being Moderated

9. ryclark,

Jun 21, 2012 9:27 AM in reply to klinejp

Report

It probably woudn't make much difference to processing speeds but would have the advantage of allowing you to use more memory. This might speed up some processes and help with large track counts and real time effects plugins.

|
Mark as:
Currently Being Moderated

10. _durin_,

Jun 21, 2012 10:05 AM in reply to ryclark

Report

We'll have some more information about our plans and concerns with moving to a 64-bit release later this year. There's several issues that have previously prevented Audition from moving 64-bit, primarily the dearth of 64-bit plug-in availability and the fact that one of our larger customer segments tends to run older 32-bit hardware and accompanying software that will likely never be updated. However, with Waves and other large plug-in vendors finally making the move to 64-bit, there's less and less to hold us back.

However, doing so would prevent you from using any legacy 32-bit VST effects you currently own. We've explored bit-bridge wrappers that allow 32-bit effects to operate in a 64-bit application, but our experience with the existing solutions has been horrible. If anyone has different opinions or examples of bit-bridge wrappers, please share them as I'm willing to be open-minded.

|
Mark as:
Currently Being Moderated

11. Claude King,

Jun 21, 2012 12:48 PM in reply to SteveG(AudioMasters)

Report

Steve, your contribution was not very helpful to my problem. I think it's clients like you who contribute to software vendors providing us with unnecessary, entirely avoidable, inferiority, while charging us an arm and a leg. Rome may not have been built in a day, but what was there, WORKED.

Do you feel it is fair that you spend by no means small money on a (supposedly) superior system, and then it cannot perform a simple task like looping function, although it has been designed to do it? To boot, the malfunction is so bad, that you cannot use it to earn your living, and then you find a free wave editor that peforms this function FLAWLESSLY... FOR FREE? If you don't find that wacky, then I don't know.

To Durin, how deeply in the code is this screwed function buried, that you cannot fix it? How difficult, and ethical, can it be to deliver something you claim your system does??? This is an entirely unacceptable situation. System designers should remember a very important edict: Users will notice the stuff that does'nt work, more profoundly than the good stuff... the good stuff is expected... THAT"S WHAT WE PAY FOR!!!

Adobe Audition team should fix this malfunction in Audition CS 5.5 asap and provide the update. The problem displays itself exactly in the same way on both 32bit and 64bit systems, so it has nothing to do with OS.

|
Mark as:
4,753 posts
Oct 26, 2006

Currently Being Moderated

12. SteveG(AudioMasters),

Jun 21, 2012 1:12 PM in reply to Claude King

Report

Claude King wrote:

Steve, your contribution was not very helpful to my problem. I think it's clients like you who contribute to software vendors providing us with unnecessary, entirely avoidable, inferiority, while charging us an arm and a leg.
Firstly, I don't set the pricing, secondly it's only an 'inferior' product according to you - which doesn't count for a lot, quite frankly. I use this software professionally, and it works fine for me. So do a lot of the world's broadcasters - who purchase multiple seats of it, and wouldn't continue to do so unless it worked for them too. These are the people who ultimately determine where the developers' priorities lie - not me, although I do tend to agree with them.

Do you feel it is fair that you spend by no means small money on a (supposedly) superior system, and then it cannot perform a simple task like looping function, although it has been designed to do it?
Adobe provide you with an unrestricted trial of Audition with every version released, so that you can try it for yourself to find out whether any particular usage you desire is possible before you purchase. They are giving you a very fair way of avoiding the caveat emptor traps you might have otherwise fallen into, so I think that your objection holds no water at all. And which specific claim made by Adobe in relation to this release do you think is not met?

|
Mark as:
Currently Being Moderated

13. _durin_,

Jun 21, 2012 1:38 PM in reply to Claude King

Report

Hi Claude,

I'm not entirely clear on what is flawed about the existing Loop functionality? Can you elaborate on the exact nature of the problem that you are experiencing? While the loop functionality in CS5.5 and CS6 is not yet at the point it was in Audition 3.0, I'm not aware of any major flaws or malfunctions in the current implementation.

Any file may be looped in Multitrack by enabling Loop mode for the clip in the Properties panel. Once enabled, these clips may be dragged to loop the contents as needed. With CS6, real-time stretch allows you to first stretch a clip to the desired tempo, then loop it continuously at that tempo. By setting the Multitrack ruler to "Bars and Beats", you can stretch a clip to an exact number of beats at the session tempo.

Obviously, there are some features from previous versions that have not been ported yet, chiefly bpm detection, key matching, and auto-stretch to match session tempo. There are other advanced looping features that have never been available in Audition but that I'd personally like to see implemented such as making arbitrary regions of a file into unique loops, and marking intro, loop, and release regions. I have no desire to implement advanced looping features haphazardly, and want to focus on this functionality when we have time and resources to build it as good as, and preferably better than, what we offered in Audition 3.

Can you be clear on what specific functionality you require that Audition doesn't currently satisfy? This will help the discussion here, as well as help me prioritize the various features in our backlog that comprise the Advanced Looping workflows.

Thanks,
Durin

|
Mark as:
Currently Being Moderated

14. Claude King,

Jun 21, 2012 4:33 PM in reply to _durin_

Report

Hi Durin... thanks for the reply. I don't use Audition in multi-tracking mode, it's not yet at where it would suffice for the work I do... I apply it to mastering, audio analysis and transcribing. CS 5.5 Audition has a loop function, as I'm sure you know. This is a very important aspect for our transcribers. So you should take a wave file and run a test to see what I mean; when you engage loop, it works maybe for a while, but sooner or later, although loop is engaged, it stops looping, then the sound file stops playing (although continueing to run). I then have to go through a whole range of clicks and unclickings (play, pause, loop buttons, etc,) re-engage loop, then it works again, untill I get a repeat of the whole mess again, on and on. So truly speaking, as the loop function is in this version, you may just as well remove it, it is so useless... I had to stop using it for a job I am currently trying to deliver on, because, instead of facilitating me an efficient work-flow, it has put me so far back that I will now have to deliver late. That's just not on... I hope you can understand my frustration, especially since I broached the subject with one of your people months ago. Accept that then I did'nt hammer on it, figuring I may be at fault, maybe just not knowing the sytem well enough. Well, I have now used the system extensively, and yep, it is a malfunction, for sure.

BTW: the files I work with vary from the average 50 mb stereo song, to 4 gb conference files, and so far it does it with all sound files and all formats... file-size/type does not matter.

|
Mark as:
Currently Being Moderated

15. Bob Howes,

Jun 21, 2012 11:38 PM in reply to Claude King

Report

With respect, Claude, I think this just goes to show the huge differences in the way people use software like Audition--and the different priorities they have. I can't comment on whether I have the same issues as you with "looping" because I can't see any use--in MY workflow--for the procedure you describe.

Mention "looping" to the majority of people using Audition as an audio production tool and they'll assume you mean making a loop in multitrack mode--for example a bar or two of a drum beat--and using that to create a backing drum track. Or, for me (doing a lot of sound effects work) I do a similar thing but with it being the sound of wind or waves or similar. For that sort of looping, Audition works exactly as I'd expect it to--and reliably.

This is not meant to say your use is in any way less valid than others--to to try and explain why the problems you're having might not have been spotted by other users.

|
Mark as:
Currently Being Moderated

16. ryclark,

Jun 22, 2012 5:19 AM in reply to Bob Howes

Report

Claude have you tried the trial of CS6 yet? There are quite a few improvements in the playback engine and memory usage which may have sorted the problems that you are seeing in CS5.5 with loop playback ( not "looping" per se as explained by Bob).

|
Mark as:
Currently Being Moderated

17. Claude King,

Jun 22, 2012 5:59 AM in reply to ryclark

Report

Hi Ry... thanks for your time. No I have'nt tried CS 6 yet, too scared to spend the money, too weary about things that will not have been updated. Don't get me wrong, I am not bashing CS... I've been doing video productions on Premierre for nearly 10 years now, and got turned on to it because I thought it was so hot... still think so. It's just that when I upgraded to 5.5, I bought the Prod Prem package, and Audition came with it, so I thought I'd make the move from my previous audio mastering software systems, to it. And yes, it has basically all the functions of Wavelab and Soundforge, much good stuff... but I got nuts when I find the standard loop function, it does'nt work, and Audition Team did not respond, pertaining to whatever they intend to do about it... something (and if so, what) or nothing.

It bothers me that Audition Team appears not to be aware of this problem, so why would they fix it in Cs6? Afterall, we cannot fix any problem unless we are aware of it. I must say again with total amazement, that I don't understand how come they were not aware of it... it makes good sense to test your stuff thoroghly before rushing it to market.

Anyway Ry, thanks once again for your contrib.

|
Mark as:
Currently Being Moderated

18. SuiteSpot,

Jun 22, 2012 6:34 AM in reply to Claude King

Report

Hi Claude,

I don't know if this 'looping' issue is a bug or not as I don't either use loops or do any looping at all but I'm sure that once it is established that it is a bug (if it hasn't been already) you can be certain that someone in the dev team will get to look at it.

As far as being 'bothered that the Audition Team appears not to be aware of the problem' I guess that is understandable but they rely not only on their own extensive in-house testing but also a wide range of diverse beta users (I don't know how many but I'm guessing a lot) to also test Audition. Even so things can be missed and no software development is immune from that unfortunately.
You are right they can't fix something unless they know about it.

Anyway you are in the right place to not only voice your opinion but to get as much feedback as the devs are permitted.

I hope it gets sorted out for you.

|
Mark as:
Currently Being Moderated

19. Bob Howes,

Jun 22, 2012 7:19 AM in reply to SuiteSpot

Report

One last thought is that Claude can see if the looped playback in CS6 works the way he wants by downloading the 28 day trial. If nothing else, it would be a quick way to generate a bug report if it DOESN'T work any better than CS5.5.....

|
Mark as:
Currently Being Moderated

20. Claude King,

Jun 22, 2012 7:55 AM in reply to Bob Howes

Report

Hi Bob, and also Suitespot... thanks very much for input. One thing ywhich a few people mentioned is trying CS6 to see if the problem is in there too... one of the two things that's prevented me from doing that was the download siza. But thank you Bob, because you triggered another thought in me, and that is that I could try the download of Audition only, and not the whole 5-plus gigs of the package. thank you very much, both of you, and all the other caring guys here.

|
Mark as:
Currently Being Moderated

21. klinejp,

Jun 22, 2012 8:43 AM in reply to Claude King

Report

Claude,

One of the things that I love most about Adobe in general is the fact that they allow you to download fully functional, albeit time-limited, trial versions so that you don't have to have such fears. Simply download the trial version and follow the instructions.   They give you plenty of time to play with the software and decide if it is worth the investment.   If after the trial period you decide that the upgrade is not for you, e.g. because it won't loop, poop, or whatever bell or whistle you desire, you can choose to invest in another product that suits your needs. I doubt that the Adobe engineers will put up with bugs in their software, and I have faith that they will eventually address all of the functionality concerns, and perhaps even get to minor issues like being able to change the icky user interface color. It looks ok with earthy wallpapers, but it still makes me feel like I am sitting at the controls of a high-tech tank. Why, just awhile ago, I was mixing with Audition 6 and driving my tank through Stonehenge.

I knew for sure when I tried CS5.5 that it wasn't a viable upgrade for me after trying it.   It only took me a few days after I tried CS6 to make the decision to purchase an upgrade for one of my Audition licenses, mainly because the iPad and Android control surface app support was outstanding (i.e. multiple surfaces so no more bank switching, vu meters on the individual channels work, and the channel labels are no longer all screwy). Since I use Audition mainly to record and produce my own music and don't sequence or loop, the loss of MIDI functionality from 3.01 to 6.0 wasn't a big deal.   Since they do have the control surface support, and the control surface support operates via midi, I can't help but to think that such functionality will appear in subsequent versions of Audition.

I started out with Cool Edit Pro back in the '90s,   I stayed with it because when Adobe came out with Audition 1, they kept the overall layout of the user interface and made the pricing structure affordable, just as they have with version 5 in CS6.   The upgrade price from CS5.5 to CS6 is really reasonable, and if you already own CS5.5, I can't see a downside to going to CS6 (I was a beta tester for CS5.5, and ran it on a home-made hackintosh / windows dual boot system, with the goal in mind of getting away from Windows and eventually moving to Mac. I was impressed with the fact that the software was exactly the same in 32 bit OSX 10.5.9 as it was in 32 bit Windows, but the lack of control surface support made it not viable for me at that time). Now that I am running a stable and responsive 64 bit system with an overclocked processor, I have no need to move in the Mac direction at this time and dismantled the Hackintosh..   I have a feeling that the next version of Audition will have native 64 bit support, which should speed things up quite a bit. As it is, CS6 loads much faster than 3.01, and in my opinion, is much more stable than its predecessor.

Their engineers often respond directly and quickly to concerns raised in these forums.   No software is perfect. Audition is a fine product built by audio Software engineers in .a mostly visual work environment, and their relatively small development team has produced impressive results. Adobe could have dropped Audition altogether, and I believe almost did, because it is by far not its cash cow.   I for one am glad that they chose to hang in, and am grateful for the continued efforts of the developers, because I really didn't want to have to learn a new software package.

When I started this forum, I deliberately made it about what we loved first, and what we didn't second.   People derive more creative solutions when motivated by carrot rather than stick, so I encourage users to try the free trial download and give the engineers a fair and honest appraisal, beginning with feedback about the many things that these high;y capable engineers have gotten right. I am concerned that if there is too much customer dissatisfaction expressed, Adobe might abandon Audition altogether, or change its functionality so it is no longer that useful for people like me who use it as a complete music production solution.   Engineers have to answer to bottom-line oriented executives. We as customers ultimately decide the software's fate.   I for one hope that Adobe continues to move forward in its development.

|
Mark as:
Currently Being Moderated

22. _durin_,

Jun 22, 2012 9:09 AM in reply to Claude King

Report

Hi Claude,

So what you're discussing is not a problem with creating loops for multitrack production, but looped playback in the waveform editor. Very different discussion! Sorry for the confusion earlier.

Still, I'm not aware of other reports of problems with this functionality and certainly haven't seen any myself. Can you give me a step-by-step process with which I might be able to reproduce the issue that you experience? As an example, here's what I've done this morning trying to uncover any issues you might be seeing:

1. Launched Audition and opened a file that's 4:54 in duration.
2. In the Waveform editor, I made a short selection of about 2 seconds in length, toggled Loop in the player controls, and started playback.
3. After looping this section continuously for about a minute, I began resizing the selection shorter and longer, making new selections, removing selections, dragging the playhead around to scrub, making selections again, etc.. All without stopping playback.
4. I continued to zoom in, make selections of different lengths (from a few seconds to a few samples.) I used the JKL keys to play reverse and at different speeds. I created Marker ranges from my selections during playback, then jumped between these by double clicking their entries in the Markers panel.

At no time did I experience what you've described. Playback continued, and selections all looped as expected.

If my attempts were similar to what you do, I have several questions that might help narrow down the issue:

1. What OS, Sound device, and buffer size/sample rate settings are you using?
2. If you are using Windows, are you using an ASIO or an MME driver?
3. Is the device you are using to edit the same device your operating system uses to play sounds, such as new mail or error beeps?
4. Does this occur almost immediately in your editing process, or do you find it only happens after an extended editing session.
5. Does this occur every time you edit a project, or does it seem to be random?
6. When playback goes silent, does it return if you stop and restart playback?

Thanks,
Durin

|
Mark as:
Currently Being Moderated

23. therealdobro,

Jun 23, 2012 8:51 PM in reply to klinejp

Report

The metronome isn't working for me. It has hiccups, and I can't trust it. Just this evening, I was tracking a guitar part and it jerked me around and I screwed up the part. I'm disappointed, because I was looking forward to being able to use the metronome in CS6, but now I have to go back to laboriously constructing click tracks in FL Studio and importing them into CS6.

|
Mark as:
Currently Being Moderated

24. Kost7,

Jun 24, 2012 3:08 AM in reply to therealdobro

Report

Therealdobro, sorry to hear that. But make Audition templates. I only made 80 bpm, 120 bpm and 160 bpm templates with one bar. I stretch these for whatever bpm I need then loop it. I also use Mobile Metronome on my Android phone to tap and find the needed tempo sometimes and then I set it for multitrack. Template implementation and multitrack stretch are just great in Audition CS6. Awesome! Speaking of what we like about CS6

|
Mark as:
Currently Being Moderated

25. klinejp,

Jun 24, 2012 8:55 AM in reply to therealdobro

Report

What hardware are you running? I have found that cs6 plays catchup, ie it speeds up the tempo after you've maxed one or more of your processor cores for a time. It is also possible that you have another process eating clock cycles..

Sent from my iPhone

|
Mark as:
Currently Being Moderated

26. therealdobro,

Jun 24, 2012 9:30 AM in reply to Kost7

Report

I haven't got into templates yet, but that sounds like a very useful workaround - thanks.

|
Mark as:
Currently Being Moderated

27. therealdobro,

Jun 24, 2012 9:37 AM in reply to klinejp

Report

klinejp wrote:

What hardware are you running? I have found that cs6 plays catchup, ie it speeds up the tempo after you've maxed one or more of your processor cores for a time. It is also possible that you have another process eating clock cycles..

Intel i3.

What were you doing in Audition when the tempo changed?

|
Mark as:
Currently Being Moderated

28. klinejp,

Jun 24, 2012 9:53 AM in reply to therealdobro

Report

I was mixing a 24 track session with multiple plugins on several channels without regard for auditions sample rate matching that of my motu system. Once I figured out that making these match reduces my processor load, it didn't happen again. More importantly: is your system powerful enough to run audition 5? My metronome works fine while recording or playing back, as long as I am not pushing my system too hard. I suggest monitoring processing load during the error to see if it could be responsible. You might also try changing your hpet setting... My current system seems to function better with it on, but previous systems functioned better with it off.

|
Mark as:
Currently Being Moderated

29. therealdobro,

Jun 24, 2012 10:39 AM in reply to klinejp

Report

klinejp wrote:

I was mixing a 24 track session with multiple plugins on several channels without regard for auditions sample rate matching that of my motu system. Once I figured out that making these match reduces my processor load, it didn't happen again. More importantly: is your system powerful enough to run audition 5?
I think so, yeah. I measure the capacity of my system according to how many tracks I can run with how many plugins before it starts stuttering. With the Intel i3 processor on this machine (I've had it for two years - it's relatively new), I can run a lot of tracks with a lot of plugins before it starts stuttering, and I can then squeeze a bit more out of it by adjusting the buffer size on my interface. However, the problem with the metronome happens when I'm recording a completely new session, even if I'm recording only one track. It makes no sense to me. But the metronome hiccup has screwed up about four different recordings on four different occasions for me, so I either have to figure it out and solve it, or abandon it - it's unacceptable as it is.

|
Mark as:
Currently Being Moderated

30. klinejp,

Jun 24, 2012 12:51 PM in reply to therealdobro

Report

Did you try adjusting HPET settings? If they are on, turn them off, and vice versa. My experience has been that HPET can enhance, degrade, or make no difference in the performance of a DAW.

|
Mark as:
Currently Being Moderated

31. R3333W,

Jun 24, 2012 11:54 PM in reply to klinejp

Report

I'm also very pleased. More or less every complaint I had with CS5.5 was addressed (and improved upon, even!). I am exceedingly happy with the VST3 support and all of the native plugins I missed from AA3 seem to be back and in even better form. Manual Pitch correction is awesome, it was a pleasant surprise to not only get that tool back but to have it improved upon. Kudos to the dev guys, high-fives all around. Great to have clip stretching back in Multitrack as well.

Media Browser is a great and long overdue addition. And hey, side-chaining! Nice. I was already sold on the upgrade based on VST3 support and the return of all the old-but-new native plugins, these were cool surprises on top of that. Stability seems to have improved on 5.5 as well.

If I had to pick one thing I'd like in the future it would be to also get MIDI support back, then I would be a very satisfied customer indeed.

Thanks for listening to our whinges about CS5.5 and making it all better again, the wait was worth it!

|
Mark as:
Currently Being Moderated

32. therealdobro,

Jun 25, 2012 1:12 AM in reply to klinejp

Report

klinejp wrote:

Did you try adjusting HPET settings? If they are on, turn them off, and vice versa. My experience has been that HPET can enhance, degrade, or make no difference in the performance of a DAW.
I've been through the BIOS a couple of times, but I can't find HPET settings. Where's it supposed to be?

|
Mark as:
4,753 posts
Oct 26, 2006

Currently Being Moderated

33. SteveG(AudioMasters),

Jun 25, 2012 2:28 AM in reply to therealdobro

Report

therealdobro wrote:

I've been through the BIOS a couple of times, but I can't find HPET settings. Where's it supposed to be?
Read this.

|
Mark as:
Currently Being Moderated

34. Claude King,

Jun 25, 2012 2:41 AM in reply to Claude King

Report

To Bob Ry, JP, Durin:, first, thanks for your input, especially the one on trying CS 6 AU. I download and installed, gave it one more try to complete my job, and the loop problem I complained about is not present in it ... it works exactly like expected.

This brings me back to CS 5.5 AU (Durin). I ran 5.5 and 6 on two laptops (Win 732 and 764) CS 6, no prob on both. But 5.5, same looping prob on both. I read the details of your test. When I do some of that stuff in one or more or all variations, invariably I pick up a prob. So it t brings me back to what I said before; 5.5 wa designed with a looping function, and it should work. I think you guys should do an investigation, find out how come it is problematic (and especially, how come it works in 6 and not in 5.5) and put out a corrective update for 5.5.

Thanks again.

|
Mark as:
Currently Being Moderated

35. ryclark,

Jun 25, 2012 4:17 AM in reply to Claude King

Report

Claude King wrote:

So it t brings me back to what I said before; 5.5 wa designed with a looping function, and it should work. I think you guys should do an investigation, find out how come it is problematic (and especially, how come it works in 6 and not in 5.5) and put out a corrective update for 5.5.

Thanks again.
They have investigated the problem and the answer is available in the update which is Audition CS6. I don't think that you will get an update to CS5.5 now CS6 is released, I'm afraid.

|
Mark as:
Currently Being Moderated

36. klinejp,

Jun 25, 2012 6:53 AM in reply to SteveG(AudioMasters)

Report

That depends on your bios. Have you looked in your power management settings? Perhaps you can give more detailed information about your machine, i.e. motherboard, processor, memory, and OS?

|
Mark as:
Currently Being Moderated

37. therealdobro,

Jun 25, 2012 10:50 AM in reply to klinejp

Report

I think maybe I'm just a little bit hooped here. In the power management tab of BIOS, the ACPI 2.0 Support was disabled, but enabling it made no difference. The reason I think this might be significant is because of things I've read online about how, as it says in the Wikipedia article on HPET, "If the ACPI is not set up correctly the OS cannot list the HPET," and as I read on another website, the only way you can change the ACPI mode is if you reinstall Windows. This seems like an awful lot to go through just so that I might be able to use the metronome in CS6. I'm going to try the workaround that Kost7 suggested, and report back. (Otherwise, I'll continue with the imported click track maneuver.)

Thanks for your help, jp.

Sorry to sort of hijack this thread with my problem, everyone.

|
Mark as:
Currently Being Moderated

38. therealdobro,

Jun 26, 2012 10:39 PM in reply to therealdobro

Report

Okay, I tried Kost7's suggestion about looping a bar or two of click track, and it worked like a charm. I love the way I can extend the looped clip to *exactly* the length of the tune.

Question: Assuming that I've got computer latency happening, why would that not affect the looped track the way it affects the metronome? Is that a question only a developer can answer? Or God, maybe?

|
Mark as:
Currently Being Moderated

39. ryclark,

Jun 27, 2012 2:40 AM in reply to therealdobro

Report

therealdobro wrote:

Question: Assuming that I've got computer latency happening, why would that not affect the looped track the way it affects the metronome? Is that a question only a developer can answer? Or God, maybe?
I would hazard a guess that maybe it is due to the fact that the metronome has to be generated in the background then played whilst you looped audio is just having to play the file.

|
Mark as: