Audiosnap Bug: Manually moved transients don't bounce correctly

Page: < 12 Showing page 2 of 2
Author
Ryan Munnis [Cakewalk]
Administrator
  • Total Posts : 1067
  • Joined: 2009/11/01 10:28:44
  • Status: offline
Re:Audiosnap: Urge to Kill... RISING!! 2011/10/21 10:10:15 (permalink)
Hi Qwerty69, 

I just want to clarify. The report is confirmation that we submitted the details of your report to our testers & developers for review. It's not confirmation of anything other then that. Sorry if the auto-reply from the system was misleading. 

If the report comes back as an issue that gets resolved/fixed/deferred/closed/marked as intended/elaborated upon/etc., I'll make sure you're notified with further information.

(EDIT: need to remember to not use FF when I post)

Ryan Munnis
Cakewalk
#31
Qwerty69
Max Output Level: -62 dBFS
  • Total Posts : 1435
  • Joined: 2004/02/19 17:44:10
  • Status: offline
Re:Audiosnap: Urge to Kill... RISING!! 2011/10/21 10:12:07 (permalink)
Lol!! Good to see the auto-responder is as accurate as the transient detection 
#32
Ryan Munnis [Cakewalk]
Administrator
  • Total Posts : 1067
  • Joined: 2009/11/01 10:28:44
  • Status: offline
Re:Audiosnap: Urge to Kill... RISING!! 2011/10/21 10:17:31 (permalink)
Qwerty69


Lol!! Good to see the auto-responder is as accurate as the transient detection 


:)

It's lose/lose. When we didn't have auto-notifications, people thought we were throwing the reports into a black hole. Now that we do have notifications, they get taken out of context and/or misinterpreted occasionally (sorry!)

Anyhow, that's why we also employ a few humans in support. For clarification purposes of course.

Ryan Munnis
Cakewalk
#33
brundlefly
Max Output Level: 0 dBFS
  • Total Posts : 14250
  • Joined: 2007/09/14 14:57:59
  • Location: Manitou Spgs, Colorado
  • Status: offline
Re:Audiosnap: Urge to Kill... RISING!! 2011/10/21 10:51:07 (permalink)
Qwerty69


brundlefly


But to say it's all "crap", and "never" bounces down correctly is not accurate.
Umm... No. That's exactly what the confirmed bug report says. Smeared transients, regardless of how good the tone of the algorithm, are still inaccurate - AND reproducible according to the bakers...
Note the key word "never" in my post. One confirmed case (presuming it is, in fact, eventually confirmed) does not constitute "never" working. All I'm saying is that the problem you are encountering in this one instance is not par for the course in my experience, and I can't reproduce it.


SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
#34
Page: < 12 Showing page 2 of 2
Jump to:
© 2024 APG vNext Commercial Version 5.1