If you did not make any changes to the audio then of course it is going to take less time to "render" it because there is nothing for the computer to do. Also the fact changing Preferences causes such delays makes this MORE likely to be a system/config issue. Audiosnap has its problems and yes they could be construed as "buggy" but the things you are describing are not "bugs". You are describing what happens when your computer is processing info. From your description here everything did work... it just took a while. When a software program performs the function it is intended to you cannot in any way call it a bug.
 
As far as this forum is concerned it is one of the friendliest, most helpful and forgiving places on the internet. If you are experiencing consistent problems with forum members it is quite possible the problem may lay with you.
 
BTW... I may like Sonar and you might call me a "fan" of the program but I am by no means a "fanbois" as the kiddies like to say nor would I dismiss a new user's problems or questions. In this very thread I have acknowledged potential limitations of the feature you are using as well as offered possible culprits and suggestions in regards to the original question. You have dismissed all of that instead opting to blame Cakewalk and insinuating that I, and anyone else on the forum who has tried to help you, are simply ignorant toadies.
 
You can continue down this path if you so choose but you are only damaging your own chances at a positive experience with the program and this forum.
 
I anxiously await your next thread.

AS corrupting projects is definitely a bug, give the guy some slack

lawp
AS corrupting projects is definitely a bug, give the guy some slack

Check #28, I began to write out steps. If there is an actual bug here I'm all ears... Ta
 
(Ah #28 has just been quoted by Beep, if anybody can repro it in X3E please let me know.. I'm going down the pub).

200bpm
 
Having read some older posts, there appears to have been a problem with bugs for X3a-d, so I attribute the resistance I'm getting to the loyalists being gun shy; they would rather dismiss a new user's problem than entertain that there is a bug that will impact his use of the product.

 
I believe the resistance you're getting is due to not following community protocols that were established long before you or I joined. There have been posts where what you identified as a potential bug was not a bug, like when you tried to create an instrument by dragging it into a track that had already been created. It's like the story about crying wolf. Do it enough times, and people will stop taking you seriously.
 
The protocol is this: If you find a "bug," give steps to reproduce it so others can help determine whether it is a bug, your lack of understanding of the program, or something that might be system-specific. If a bug is confirmed and can be reproduced, submit a bug report to Cakewalk so it can be added to the list of remaining bugs and prioritized.
 
Note that saying "I loaded a file and it took a long time to render at 24/96" is not sufficient to qualify as steps required to reproduce. In the past, when people have wanted others to check results regarding a particularly problematic file, they post it in dropbox or use a service like hightail.com to provide a link. It may just be that AudioSnap is doing lots of calculations. Or maybe "multiprocessing engine" was turned off somehow under preferences.
 
Some people have reported huge render times where the problem ended up being the floppy disk port enabled on the motherboard in a system with no floppy drive. Someone had huge render times for Kontakt instruments that no one else experienced, and IIRC it turned out to be due to having a blank disk in the computer's optical drive. These issues were found only because no one else experienced them, so instead of being distracted trying to find "bugs" in Sonar that didn't exist, the community (which with all due respect, has a lot of people who are much more savvy about these things than you or I) was able to localize and fix the problem. I doubt anyone will be able to provide a definitive answer to solving your issue based on the information you've provided. If you want a problem solved and cannot figure out how to solve it yourself, you will need to provide sufficient data so that others can solve it.
 
That said, AudioSnap is complex and not trouble-free. I find it far more predictable if I work on individual sections of a file instead of really long files. 
 
People who have been using Sonar for a long time generally agree that X3 is stable by any reasonable standards. This is due in large part to this forum, which is not based on adversary relationships. It is a partnership between the user base and Cakewalk, who both seek to have Sonar be the finest software possible. By the community providing important data, and sometimes even sending projects, Cakewalk's engineers can not only find and track down bugs within Sonar, but compatibility issues with third party software and system-specific issues that would be very hard to find without Sonar getting into the world onto a huge variety of systems running a huge variety of software.
 
Finally, it's amazing how many intractable problems are solved by a clean Windows install. The more programs you install, particularly if they're of the same type (e.g., a bunch of different DAWs), the more likely there will be conflicts with unpredictable results.
 
P.S. It would be helpful if you could give some clues as to what's not in the documentation so others could benefit from your experience with tech support.
 

Beepster
 I have not experienced that one though and I don't see many complaints about it so it's not one of those bugs that can be consistently reproduced. Not sure if there is a different term for that. "Bug Lite"? "Ghost Bug"? "Borg"?
 
I usually just call those intermittent ones gremlins.

 
My favorite "bug" of all time happened with a Mac. Strange, rare, and unexplained crashes would happen. They were totally unpredictable and so infrequent I couldn't find a common thread. I figured they related to the operating system since the problems occurred with more than one program.
 
I re-installed the OS (very easy on a Mac) and thought the problem was solved, but it came back. Someone suggested I check my RAM, so I did that but the test program gave my RAM a clean bill of health. I swapped out some other hardware components and still, the occasional crash would come back eventually.
 
The person who suggested the RAM test asked if that had solved the problem. I said no. But he said I was using the wrong kind of RAM test, because it needed to occupy some of the RAM and that couldn't be tested. He turned me on to a program you had to load on a USB stick and run from the Mac's Command Line Interface. Sure enough, there was a RAM stick with a defect. I replaced it and the crashes never came back.
 
The other hardware problem I really hate is when a hard drive starts losing sectors...

lol... I'm well versed in the way of the internet jerk due to my other cyber haunts. I'm just extremely well behaved here because it's a nice place and I don't want to stink it up too much. Funny thing though is I spend more time here than anywhere else now. It's more relaxing. ;-)

Paul P

Anderton
 
The other hardware problem I really hate is when a hard drive starts losing sectors...

Hard disks have got to be the most reliable things on the planet.  I think you're being a bit nostalgic there, Craig
 

I don't mean to imply it's a common occurrence by any means, but about two years ago I did have a hard drive lose sectors after being in service for about 90 days. First one in years. The hard drive that failed prior to that had a failure of the circuit board, not the drive. Fortunately I had an identical driver, swapped the boards, saved the data, and moved on. Not that this has anything to do with AudioSnap...

Riiight...
 
There is a big difference between 24 hours and having to abandon the function and waiting ten minutes resulting in the desired result. It worked. It was just processing it. That is not a bug. It is your computer being slow(ish) for some reason or another.
 
As far as demand for an apology... luuuuulz. Might as well block me my friend... but you are gonna have to do it every time you create a new account... the first of which I'm assuming will be created tomorrow.
 
Peace.

Paul P

200bpm
 
If any of the people who have dumped on me would like to apologize, I would accept that and continue to respond to your posts, otherwise I don't have time for the petty bs and will put you on block list, if possible.

For what it's worth, I understand your situation.  Every time I get around to actually doing something useful with Sonar/etc, I encounter bugs that take me hours to figure out.  Z3ta is my current point of reference.
 
Part of using Sonar is learning all that doesn't work as it should and working around.  The documentation is way behind and doesn't address bugs.  I'm sure that eventually I'll know all the workarounds and the program will be useful.  In the meantime, it's painful.
 

Samplitude isn't sexy, and it can be obtuse (there is little documentation and the user community is all pro so none of them are using tools like Maschine),  but I've been doing this kind of audio manipulation, tempo mapping, tempo/signature changes, transient mapping and applying to clips, and general clip manipulation for 5+ years and the program has not crashed once.
 
I'm still hopeful I can get SONAR going, but the big surprise for me was that Samp's midi editor is ahead of Sonar's. Another important feature to me is the ability to loop record midi (a la Maschine), and Samp does this beautifully.  Can record and edit in real time, draw notes, etc so midi can be composed in a very organic way.
 
If I want to change project tempo, all I have to do is change the metronome and everything conforms, no funny menus, substeps or whatever.
 
Sonar has ARA integration and a better UI, but at least I can load Melodyne plug, AD2 and Z3ta+2 into Samp so this won't be a complete loss if I give up on Sonar.

If any of the people who have dumped on me would like to apologize, I would accept that and continue to respond to your posts, otherwise I don't have time for the petty bs and will put you on block list, if possible.


Also, just because YOU can't reproduce something does not mean it isn't a bug.  Logic.  Patience.  Acceptance.  Professionalism. Progress. Peace.
 
Please add me too to the block list to both your user accounts, you will probably be hiding behind yet another user account very soon anyway Teal.
 
Again performance issues are not a bug, and yes most of us agree that that audiosnap can be painful.

And in regards to your statement I quoted above I have documented around 70 bugs with the help of the community so far and have been involved in all of the threads, so please I don't need a lesson or a lecture from you thankyou...
 
I'll check Beepsters steps later....

The steps-to-reproduce protocol was only introduced for x series by Alex, so not so long ago... And there were many calls for Cakewalk to document known issues, which they never did, and so that was also introduced by Alex... Both very useful imho

Yeah blocking won't help anyone xoxo