yeaaa willy. you go girl.

"Given the time available only a percentage of all issues logged get addressed."

 "We do the best we can do but its impossible to address every known issue in a given release."

And herein lies the downfall of the yearly release cycle.
 
Instead of fixing things like the envelope issues, it's time to start working on the next new version. 
Which would be fine except that these things get put by the wayside never to be looked at again.
 
So I might not have functional automation but I do get a new GUI with session drummer.

Mike 

Installed 8.5.1.
When I open previous projects the program tells me it can't find all of my instances of Dimension Pro plug ins. I've re-run the VST scan to no avail. The error message tells me to reinstall the plug-ins and run Sonar again.

However, when I open projects up with 8.3 all the Dijmension plug-ins are there so I'm not sure if reinstalling Dimension will have any affect at all on the problem.

One thing I noticed is that Dimension PRo is listed as both a Dxi and a VST. Is this correct and if so is there a difference between the DXi and VST versions?

Running 64-bit Vista.

Willy - that might be your perspective, but from my viewpoint that is "nearly one out of every six issues reported was not fixed".

My intention was to simply remind folks that if you want us to know about the issues you are seeing please use the form, if you would like to continue this discussion, I'd suggest a PM so we can keep this thread on topic.

RE: the 1/6 "un-fixed" issues you're making the assumption that all of the issues we did not address we're real issues and not user errors, config related or simply a case of not reading the documentation.

This thread has drifted too far off-topic, IMO. The OP did not intend for it to be a general **** session, but a place to gather bug reports in one place.

But as long as we're already out here in off-topic land, lemme add a few OT comments of my own:

1. For every bug you're aware of, a software developer will have fixed 40 bugs you never knew anything about, because they got knocked down during development, beta and QA testing. If you think the majority of bugs are ignored, that's just frustration talking and just ain't so.

2. Well over half the "bugs" reported on this forum (not this thread, but on the forum in general) are NOT SONAR bugs. They are user error, third-party plugins, hardware problems, Windows configuration issues, driver issues and user error. Yes, I said that last one twice.

3. Posting a complaint on this forum does not constitute a problem report. CW has a system in place for logging, prioritizing and tracking problems, and for allocating internal resources to address them. If you want your concern looked at, you must use the formal reporting mechanism. Willy, Brandon, Noel et al cruise the forum only when they have time, it's not in their job descriptions.

4. CW could be more forthcoming with these issues. There is no searchable database to find out if a given problem has already been reported and/or fixed. There is no convenient way to check progress on a problem report (although the CW staff are pretty good about emailing updates - still, only the report filer gets that information).

5. CW needs to re-evaluate the beta program. I don't know if there aren't enough testers, not enough quality testers, not a stringent-enough standard for qualifying testers, or what the problem is. But when something like the Toontrack 64-bit issue makes it through beta without someone noticing, that's got to make you wonder how effective the beta program is. I don't think a public beta is necessarily the solution, though.

Sorry for contributing to the off-topicness.

bitflipper

4. CW could be more forthcoming with these issues. There is no searchable database to find out if a given problem has already been reported and/or fixed. There is no convenient way to check progress on a problem report (although the CW staff are pretty good about emailing updates - still, only the report filer gets that information).

I agree almost 100% with you, except the part that I highlighted. I got zero feedback from Cakewalk, which is why I'm so frustrated with this. After all the time I spent on this making sure Cakewalk has as much info as I can possibly provide, I have heard nothing back. I don't know whether they tried to reproduce it, whether they successfully reproduced it, whether they triaged it - nothing.  So my feeling is that I just won't bother next time. Yes they don't owe me anything, but they can at least acknowledge it when I go out of my way trying to help them.

I got zero feedback from Cakewalk

Hi Steven,

I personally replied to your report on 3/5/09 as did Noel when you originally posted about the issue: http://forum.cakewalk.com/tm.aspx?m=1643436

I've selected a bunch of tracks and going to archive them. I've pressed "A" button, it lights up, but tracks still play.

There're also problems with displaying waveforms. In some cases waveforms doesn't display.

wo1


I've selected a bunch of tracks and going to archive them. I've pressed "A" button, it lights up, but tracks still play.

There're also problems with displaying waveforms. In some cases waveforms doesn't display.

Not sure about the Archiving issue, but try deleting the contents of your 'Picture Cache' folder. 
 
This should take care of the wave drawing problems.
 
HTH

the developers of that product have had access to every build of SONAR 8.5 through our 3'rd party beta program. The whole purpose of our 3'rd party beta is to get early warning about compatibility issues. Yet we heard nothing about that problem until now.

Now THAT'S distressing.

From the Toontrack forum:

Sonar include technology to provide support for 32 bits plugins to operate in the 64 bit version of the host. We however do not test nor can make any guarantee of proper operation...we do NOT test this environment and therefore can make no guarantee of proper operations. That said there are no known issue ...but again it depends how mission critical your set up has to be .

Interestingly, the above quote was copied and pasted into more than one thread reply. Must be the official company position.

I don't want to rush to judgment, but I'm wondering if Superior Drummer users' wrath is misdirected, and maybe Toontrack should be getting some heat from this.

've selected a bunch of tracks and going to archive them. I've pressed "A" button, it lights up, but tracks still play. There're also problems with displaying waveforms. In some cases waveforms doesn't display.

You're going to need to supply a lot more detail on these, so they can be confirmed. In particular, Archive has been around since the stone-age, and for me the button seems to work just like the hot-key I've had assigned to that function since shortly after the stone-age. I still prefer my hotkey, because I can archive all selected tracks at once, instead of having to press the A button on each one.

seriousfun

Jose7822

seriousfun

 
Jose7822

@ Seriousfun,

There's two easy ways of opening the Audio Snap palette:

1- Select a clip (or groups of clips) and press F12.

2- Click the new Transient Tool and then click on any audio clip.


Remember, Audio Snap won't open on MIDI clips (though you can right-click a MIDI clip and open it that way).


HTH

Thanks, but that doesn't work. I've uninstalled and reinstalled. Everything else seems to work as-expected. I have reported this.

I believe that the issue is at your end though, cause it works exactly as I've described (at least on my end).  Try to give Cakewalk's TS a call this week to see if they can help you with that.  Hope they help you sort this out soon.
 
 
Take care!

Thanks for trying! I agree, it's probably on my end, but my system is usually stable, upgrades ususally go well, and I have tried everything I could think of. I have submitted a report, and I'll let everyone know what the fix is.

quoting myself...
 
The response from tech support didn't seem to work - they suggested I delete a few X and Y registry keys for Audiosnap. The first time I opened SONAR after that, the Palette showed for a second but then disappeared.
 
So I called Tech Support. The helpful guy (didn't get a name) tried a bunch of things with me. I told him I have three monitors, the third on an EVGA USB+12 usb adaptor. Turned off the third monitor and the AudioSnap Palette shows. I like my third monitor but now I have a workaround. This wasn't pilot error, but it was system-specific. The Tech Support guy found that USB adaptor in their database and added a note - we'll see if Cakewalk can come up with something.
 
 

I don't want to rush to judgment, but I'm wondering if Superior Drummer users' wrath is misdirected, and maybe Toontrack should be getting some heat from this.

I don't see why TT should get any heat.  Superior and EZdrummer are doing their job in the environment they were designed for.  Those two programs are designed for a 32 bit operating system.   They are advertised to work in a number of 32 bit Windows hosts as well as Mac applications.  To say that they are responsible to obtain 64 bit computer systems and testers to test a beta version of a host for a non supported environment is a bit of a stretch.

I can say that to the best of my knowledge, Cakewalk is getting no different treatment as any other software host.   Can you imagine if all the DAW hosts were in beta for 64 bit apps at the same time?  It's difficult enough to shoot at stationary targets much less moving ones.   It's not like TT is sitting doing nothing waiting for the hosts to release a new update so we can check the code for bugs.  Keep your eye on the TT track site for some nice releases and further news. 

 As far as I know, 8.5 32bit is reported as working fine.  The 64 bit deal is on Cakewalk.  And like I said before, just because a beta tester reports a bug doesn't mean a stop shipment order is going to be made so I don't blame the beta testers at all.

Hey SongCraft,

I didn't mean to ignore your post.  For some reason yours just slipped by, but it wasn't intentional, I promise.

I've read about the metronome problems for as long as I can remember but I haven't had any with it personally.  Maybe if you could provide a step by step on how to reproduce this bug, or point to a thread where this is explained in more detail I could try it on my setup.  Your help is appreciated :-)

Jose7822


Hey SongCraft,

I didn't mean to ignore your post.  For some reason yours just slipped by, but it wasn't intentional, I promise.

I've read about the metronome problems for as long as I can remember but I haven't had any with it personally.  Maybe if you could provide a step by step on how to reproduce this bug, or point to a thread where this is explained in more detail I could try it on my setup.  Your help is appreciated :-)

Apology to you Jose,

My posted was directed at Willy or whoever else (CW), also because I'm upset since I've been having issues accessing my eStore account since Sept 16, I also sent several Emails and still no reply from CW (and I don't have anti-spam filters, no blocking on my Email accounts) I should have gotten a reply from CW by now.

About the metronome:
In older versions of SONAR (for example dating back to ver. 6.2) when using multiple instances of vsti plugins the metronome count-in would be way off time.  Question: I am wondering if this annoyance has been fixed in later versions of SONAR?

If you do a search: 'Metronome' you will find a lot of topics/posts in regards to metronome issues. If the metronome was working perfectly and is simple to use then why so many issues with it's timing? Often replies such as; use punch in/out and/or create our own click track using a drum softsynth for example.  Also, when setting metronome properties from default (midi) to audio it does not entirely resolve the timing issue such as when using multiple instances of vsti plugins and/or in multitimbral mode.