Hermu
Max Output Level: -90 dBFS
- Total Posts : 23
- Joined: 2015/01/12 03:11:15
- Status: offline
Cakewalk ignores user Bug reports!
it' realy strange that Cakewalk ignore users bug reports!
there are some basic DAW function bugs, which are not working in Cakewalk products about longer time.
for example some other user had reported the same problem already long times ago:
Delete Special and Cut Special is not working with MIDI Events in Track and delete Hole, only the contents will be deleted but the Hole stays unchanged and this is unusable. This disqualifies Cakewalk as a professional DAW, which can not handle basic DAW functions.
Why the hell, need a Cakewalk user 4 different functions to delete a hole and then is not working???
Other DAWs have only one and it works !!!
Also the new feature "Piano Roll View Enhancements" is buggy, because they have not realy tested "Fit Content". This should be automatically for each selected track, and also track content customized.
Cakewalk Sonar Platinum Aspire XC-605, Intel i7 4770K @ 3.4 Ghz, 16 GB Ram, Onboard Sound, ASIO4All Windows 10 Pro x64 NOVATION Impulse 61, M-Audio Oxygen 61 3rd, Roland SD-50, EMU Shortboard 49, iCON iControls, Akai APC mini
|
chuckebaby
Max Output Level: 0 dBFS
- Total Posts : 13146
- Joined: 2011/01/04 14:55:28
- Status: offline
Re: Cakewalk ignores user Bug reports!
2017/03/30 15:28:36
(permalink)
Sorry to hear of your problems. Delete hole will soon be replaced with ripple editing (hopefully in the next couple months). However I often hear users complain and say "other Daw's do this easily". but yet still use sonar for its great features. So Sonar cant be that bad or you wouldn't be here using it..you would have moved on to that other DAW that works flawless  . Where are you reporting your bug reports ?
Windows 8.1 X64 Sonar Platinum x64 Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GBFocusrite Saffire 18I8 - Mackie Control
|
ampfixer
Max Output Level: -20 dBFS
- Total Posts : 5508
- Joined: 2010/12/12 20:11:50
- Location: Ontario
- Status: offline
Re: Cakewalk ignores user Bug reports!
2017/03/30 15:55:58
(permalink)
I'm starting to think flying monkeys will show up before Ripple Editing. It's not even on the coming soon list anymore. Oh wait.... The coming soon list isn't there anymore. But hey, we got wireless Bluetooth midi. 
Regards, John I want to make it clear that I am an Eedjit. I have no direct, or indirect, knowledge of business, the music industry, forum threads or the meaning of life. I know about amps. WIN 10 Pro X64, I7-3770k 16 gigs, ASUS Z77 pro, AMD 7950 3 gig, Steinberg UR44, A-Pro 500, Sonar Platinum, KRK Rokit 6
|
Hermu
Max Output Level: -90 dBFS
- Total Posts : 23
- Joined: 2015/01/12 03:11:15
- Status: offline
Re: Cakewalk ignores user Bug reports!
2017/03/30 15:58:30
(permalink)
i have reported my bugs from my user account and some of theme are always in state "NEW" over years!
and some which are in state "Submitted To Development" are also not fixed.
today CWBRN-73320 for Delete Hole problem goes now to state "Submitted To Development".
Cakewalk should also check other actual DAWs on Market to get equal or better workflow.
All DAWs have atvantages or disadvantages, thats clear, but basic function who are not works or with a inconvenient workflow are not competitive.
Cakewalk Sonar Platinum Aspire XC-605, Intel i7 4770K @ 3.4 Ghz, 16 GB Ram, Onboard Sound, ASIO4All Windows 10 Pro x64 NOVATION Impulse 61, M-Audio Oxygen 61 3rd, Roland SD-50, EMU Shortboard 49, iCON iControls, Akai APC mini
|
Seth Kellogg [Cakewalk]
Administrator
- Total Posts : 814
- Joined: 2009/02/06 15:25:40
- Location: Boston, MA
- Status: offline
Re: Cakewalk ignores user Bug reports!
2017/03/30 16:20:08
(permalink)
☄ Helpfulby BobF 2017/03/31 15:59:51
ampfixer
I'm starting to think flying monkeys will show up before Ripple Editing. It's not even on the coming soon list anymore. Oh wait.... The coming soon list isn't there anymore. But hey, we got wireless Bluetooth midi.
Hi Ampfixer, Lance fielded this concern yesterday. http://forum.cakewalk.com/FindPost/3583423 If you have any more concerns, feel free to send me a PM. Hermu
i have reported my bugs from my user account and some of theme are always in state "NEW" over years!
and some which are in state "Submitted To Development" are also not fixed.
today CWBRN-73320 for Delete Hole problem goes now to state "Submitted To Development".
Hi Hermu, I went through and processed all of your reports that I could find. There's still 2 set to New that we'll need to dig into more. Ripple Editing should be addressing the delete hole issue. A similar case came up with another user last week: http://forum.cakewalk.com/FindPost/3578617
In your specific case, some of the bugs/crashes were from older versions of our products that are currently out of development. I checked ahead though and many were addressed in subsequent versions. If you have any more questions, please feel free to send me a PM and we can dig into this further.
|
Brian Walton
Max Output Level: -79 dBFS
- Total Posts : 584
- Joined: 2014/10/24 22:20:18
- Status: offline
Re: Cakewalk ignores user Bug reports!
2017/03/30 16:23:34
(permalink)
Hermu
i have reported my bugs from my user account and some of theme are always in state "NEW" over years!
and some which are in state "Submitted To Development" are also not fixed.
today CWBRN-73320 for Delete Hole problem goes now to state "Submitted To Development".
Cakewalk should also check other actual DAWs on Market to get equal or better workflow.
All DAWs have atvantages or disadvantages, thats clear, but basic function who are not works or with a inconvenient workflow are not competitive.
All depends on what you do and how you work. For my personal workflow, Sonar is a top tier layout. I do not spend my days deep editing MIDI though.
|
declan
Max Output Level: -81 dBFS
- Total Posts : 463
- Joined: 2003/11/06 17:45:59
- Status: offline
Re: Cakewalk ignores user Bug reports!
2017/03/30 17:01:17
(permalink)
I think Ripple Editing will probably change a lot of people's workflow whether they think so or not. It's not simply about removing headaches.
The implementation will, of course, be the determining factor but it is a creative tool in song composition.
A lot of people recoil at that - cutting & pasting has been around for over 20 years - but now with the synths and various fx we have (and note chase) you can put things together that you haven't thought of.
|
pwalpwal
Max Output Level: -43 dBFS
- Total Posts : 3249
- Joined: 2015/01/17 03:52:50
- Status: offline
Re: Cakewalk ignores user Bug reports!
2017/03/30 17:04:12
(permalink)
declan
The implementation will, of course, be the determining factor
|
chuckebaby
Max Output Level: 0 dBFS
- Total Posts : 13146
- Joined: 2011/01/04 14:55:28
- Status: offline
Re: Cakewalk ignores user Bug reports!
2017/03/30 19:18:13
(permalink)
Im not sure every one is going to happy about ripple editing as some think.
I know I have my own concerns. im used to working in a certain way, for example cut. paste, copy, exc.
The thought of learning a new implementation is not so appealing to me which is why is was hoping for a fix of delete hole vs ripple editing which to be perfectly honest, im not sure what it will bring.
Hence the reason I have never complained about "delete hole", I just split and move data as needed.
Its not a life ending feature (not having delete hole).
Windows 8.1 X64 Sonar Platinum x64 Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GBFocusrite Saffire 18I8 - Mackie Control
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Cakewalk ignores user Bug reports!
2017/03/30 19:51:24
(permalink)
@chuckebaby - I think you'll find ripple editing can be extremely valuable in some situations, and absolutely the wrong tool to use in others. In video editing, where ripple editing is essential, I estimate that I use ripple editing about 15% of the time compared to 85% for cut-and-paste. But when I need ripple editing, I really need it.
@Hermu - Cakewalk does not ignore user bug reports; looking over the list of bug fixes in the eZine provides ample evidence, especially if you follow the forums and keep track of the issues people have reported. However, it is accurate to say Cakewalk either does not, or cannot, act on all user bug reports.
|
declan
Max Output Level: -81 dBFS
- Total Posts : 463
- Joined: 2003/11/06 17:45:59
- Status: offline
Re: Cakewalk ignores user Bug reports!
2017/03/30 20:14:56
(permalink)
chuckebaby
Im not sure every one is going to happy about ripple editing as some think.
I know I have my own concerns. im used to working in a certain way, for example cut. paste, copy, exc.
The thought of learning a new implementation is not so appealing to me which is why is was hoping for a fix of delete hole vs ripple editing which to be perfectly honest, im not sure what it will bring.
Hence the reason I have never complained about "delete hole", I just split and move data as needed.
Its not a life ending feature (not having delete hole).
I was probably wrong to make any predictions, but I do hope that others find inspiration with ripple editing. It does all depends on what you do, but "delete hole vs. ripple editing" is not really a 'thing'. When I started with CWPA.4 you were forced to cut, move & paste out the yazoo considering you only had 32 megabytes of RAM. Essentially "delete hole" is just a welcome shortcut as you pretty much said. I checked out (then bought) Reaper because of a freebie that was recommended in the software forum here. I'd seen the Reaper ripple editing video before in this forum, but I was unaware of how (and how much) I'd actually use it. Even if I still was in a band and just did straight live recording in Sonar I'd still use it.
|
chuckebaby
Max Output Level: 0 dBFS
- Total Posts : 13146
- Joined: 2011/01/04 14:55:28
- Status: offline
Re: Cakewalk ignores user Bug reports!
2017/03/30 22:06:54
(permalink)
declan
chuckebaby
Im not sure every one is going to happy about ripple editing as some think.
I know I have my own concerns. im used to working in a certain way, for example cut. paste, copy, exc.
The thought of learning a new implementation is not so appealing to me which is why is was hoping for a fix of delete hole vs ripple editing which to be perfectly honest, im not sure what it will bring.
Hence the reason I have never complained about "delete hole", I just split and move data as needed.
Its not a life ending feature (not having delete hole).
I was probably wrong to make any predictions, but I do hope that others find inspiration with ripple editing.
It does all depends on what you do, but "delete hole vs. ripple editing" is not really a 'thing'. When I started with CWPA.4 you were forced to cut, move & paste out the yazoo considering you only had 32 megabytes of RAM. Essentially "delete hole" is just a welcome shortcut as you pretty much said.
I checked out (then bought) Reaper because of a freebie that was recommended in the software forum here. I'd seen the Reaper ripple editing video before in this forum, but I was unaware of how (and how much) I'd actually use it. Even if I still was in a band and just did straight live recording in Sonar I'd still use it.
oh man I hope it didn't seem like I was responding to you personally. If it did, my apology's. I was referring to a lot of people out there who are waiting on ripple editing. Myself, I should probably be more open minded and give it a fair share. I tend to jump the gun quite a bit 
Windows 8.1 X64 Sonar Platinum x64 Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GBFocusrite Saffire 18I8 - Mackie Control
|
brconflict
Max Output Level: -56.5 dBFS
- Total Posts : 1891
- Joined: 2012/10/05 21:28:30
- Status: offline
Re: Cakewalk ignores user Bug reports!
2017/03/31 15:01:52
(permalink)
Anderton
@Hermu - Cakewalk does not ignore user bug reports; looking over the list of bug fixes in the eZine provides ample evidence, especially if you follow the forums and keep track of the issues people have reported. However, it is accurate to say Cakewalk either does not, or cannot, act on all user bug reports.
My observation is that the Bug Reports are the first ones addressed. With that said, it seems very obscure bugs one wouldn't even think of or come across daily are fixed, while other problems addressed in the forum (outside the Bug Report Tool) may go ignored, even if they can easily be replicated. The problem I see is that, there's no acknowledgement that the bug is being truly tracked or reviewed. That's frustrating because, users don't have any indication they're being helpful. More, there's issues reported years ago that have still gone untouched and forgotten, even if still replicate-able.
Brian Sonar Platinum, Steinberg Wavelab Pro 9, MOTU 24CoreIO w/ low-slew OP-AMP mods and BLA external clock, True P8, Audient ASP008, API 512c, Chandler Germ500, Summit 2ba-221, GAP Pre-73, Peluso 22251, Peluso 2247LE, Mackie HR824, Polk Audio SRS-SDA 2.3tl w/upgraded Soniccraft crossovers and Goertz cables, powered by Pass-X350. All wiring Star-Quad XLR or Monster Cable. Power by Monster Power Signature AVS2000 voltage stabilizer and Signature Pro Power 5100 PowerCenter on a 20A isolation shielded circuit.
|
ampfixer
Max Output Level: -20 dBFS
- Total Posts : 5508
- Joined: 2010/12/12 20:11:50
- Location: Ontario
- Status: offline
Re: Cakewalk ignores user Bug reports!
2017/03/31 15:54:06
(permalink)
As users, it's hard to say how Cake sets their priority list. Recent threads indicate that the forums are only a small piece of the puzzle. It's obvious that bug reports are another piece and the issues that get discussed here can sometimes lead to quick fixes. But I don't think bug reports are a primary driver.
During the last NAMM, Craig Anderton reported that Noel was showing off Sonar using Bluetooth midi input. I'd never seen that as a feature request, but sure enough, it's a new feature in the most recent Sonar release.
My observation is that feedback from the early release is the most potent input users have. The majority of issues reported get sorted out quickly. It's a form of real-time bug reporting that seems to work for Cake and the user base.
Regards, John I want to make it clear that I am an Eedjit. I have no direct, or indirect, knowledge of business, the music industry, forum threads or the meaning of life. I know about amps. WIN 10 Pro X64, I7-3770k 16 gigs, ASUS Z77 pro, AMD 7950 3 gig, Steinberg UR44, A-Pro 500, Sonar Platinum, KRK Rokit 6
|
ralf
Max Output Level: -86 dBFS
- Total Posts : 205
- Joined: 2010/11/27 05:36:43
- Status: offline
Re: Cakewalk ignores user Bug reports!
2017/03/31 19:44:04
(permalink)
Just two short remarks:
1. Bugs with workarounds obiviously have a very low priority. For "Delete hole", all you have to do is to fill the hole with clips, then it works as it should.
2. No matter how ripple editing will work, I'm pretty sure that "Delete hole" will nonetheless be a valuable alternative - once it is fixed and can be used without a workaround. Selecting a range and then calling "Delete hole" will be faster than ripple editing in some cases. So, I hope it will be fixed and not just replaced by ripple editing.
|
brconflict
Max Output Level: -56.5 dBFS
- Total Posts : 1891
- Joined: 2012/10/05 21:28:30
- Status: offline
Re: Cakewalk ignores user Bug reports!
2017/03/31 19:59:58
(permalink)
ralf
Just two short remarks:
1. Bugs with workarounds obiviously have a very low priority. For "Delete hole", all you have to do is to fill the hole with clips, then it works as it should.
2. No matter how ripple editing will work, I'm pretty sure that "Delete hole" will nonetheless be a valuable alternative - once it is fixed and can be used without a workaround. Selecting a range and then calling "Delete hole" will be faster than ripple editing in some cases. So, I hope it will be fixed and not just replaced by ripple editing.
I'm anxious to see how well the Ripple editing works. I noticed CW removed the Upcoming features from the Sonar page. Not sure what happened, there.
Brian Sonar Platinum, Steinberg Wavelab Pro 9, MOTU 24CoreIO w/ low-slew OP-AMP mods and BLA external clock, True P8, Audient ASP008, API 512c, Chandler Germ500, Summit 2ba-221, GAP Pre-73, Peluso 22251, Peluso 2247LE, Mackie HR824, Polk Audio SRS-SDA 2.3tl w/upgraded Soniccraft crossovers and Goertz cables, powered by Pass-X350. All wiring Star-Quad XLR or Monster Cable. Power by Monster Power Signature AVS2000 voltage stabilizer and Signature Pro Power 5100 PowerCenter on a 20A isolation shielded circuit.
|