DAWs suck and Cubase by Steinberg is no exception. It's another PIECE OF SHIT!
From the Mouths of Cubase Users
Since installing 7.0.5 on both my MacBook Pro
and my Windows 7 desktop. Cubase is crashing often, like irregularly
about every half hour or so.
On the Mac side, I'm getting a crash report (see attached).
On the Windows side, I'm gettting the "Serious Problem" dialog.
This is happening in both 32 and 64 bit versions of the program.
It happens randomly, sometimes when I open a Waves plugin on an insert
point of a channel and sometimes when I do something like close the Mix
Console.
I did not encounter these crashes with 7.0.4
Will 7.0.6 be out soon containing a fix or do I need to go through uninstall and reinstall on both machines (ugh!).
Cubase 7 has really slowed down my workflow with all of this instability. Not a happy camper...
You do not have the required permissions to view the files attached to this post.
Desktop:
Cubase 7.0.5 Wavelab 8.0.2, Halion 4.5.4, Presonus StudioLive 24.4.2,
CPU Intel Core 2 Quad Q9550 2.83gHz, Motherboard Asus P5Q Pro, RAM
Corsair 8gb (2x4gb), Video Card MSI R5450 (no fan), PSU Zalman ZM600 HP,
Zalman Reserator 1 liquid cooled system, Windows 7 x64 Home Premium,
Pro Tools 9.0.6, Waves Mercury Native 9.2.6
Laptop: MacBook Pro (15 in), 2.4 gHz Intel Core i7, 8 gb RAM, OSX
Mountain Lion 10.8.4, Focusrite Saffire Pro 14 (Driver v 3.2), Presonus
StudioLive 24.4.2, Philips DVD+-RW SDVD 8820 SATA drive, Wavelab
8.0.2, Cubase 7.0.5, Halion 4.5.4, Pro Tools 9.0.6, Waves Mercury Native
9.2.6
-
timmyboylad
- Junior Member
-
- Posts: 179
- Joined: Thu Dec 16, 2010 8:25 pm
by
Sonik » Thu Jul 18, 2013 2:31 am
+1 ...
MacPro 8 core 12gb HD 5770 10.7.5|Cubase 7.05|Wavelab 7.2.1|Wavelab 8.01|Protools 10|Logic 9|Logic X|3xUAD-2|
Thermionic Phoenix Mastering Plus|API 2500|Avalon 737sp|API
512c|Avedis MA5|Summit TLA-100A|Distressor EL8-X|Neumann M147|Apogee
Symphony|Apogee Rosetta 200|RME Fireface 800|Euphonix McMix x2|
Halion Sonic|Komplete8|Korg Legacy|Stylus RMX|VSL Strings|EW|ReFx
Nexus 2|Autotune 7|Waves 9|Vocalign
3|Melodyne|Soundtoys|Softube|Brainworx|SPL
i7 3,40ghz|Asus P8P67|16GB GSkill 12800|GTS450 1gb|Win7 64|Cubase 6.5.4|UAD-1|UA-25|
-
Sonik
- Member
-
- Posts: 646
- Joined: Wed Dec 15, 2010 10:34 pm
by
Chew » Thu Jul 18, 2013 7:59 am
Its happening the same thing here
-
Chew
- New Member
-
- Posts: 10
- Joined: Fri Dec 17, 2010 12:16 am
crashing & unstable...happens to me tooI have not seen any way to resolve this issue yet, only uninstalling and reinstalling...
Cubase 7
Akai MPK 25 MIDI Keyboard
Focusrite Scarlett 8i6 USB soundcard
Yamaha HS80M Monitors
Macbook Pro, 15" Mid 2012, 2,3Ghz Quad-core Intel i7
Turbo boost 3.3GHz
4G Ram
500G harddrive
OSX 10.8.4
-
Audionic
- New Member
-
- Posts: 12
- Joined: Sat Jul 13, 2013 2:51 pm
+1 same here guys. V7.0.5. Is absolutely useless
!!!! Crashing, unable to open project in 64bit under mac os x. I have
to use 32bit version, but the performance is horrible + so much spikes. I
hope that its gonna be fixed very soon. i can not work on projects Ive
got scheduled !!!!
-
Ronny K.
- New Member
-
- Posts: 3
- Joined: Wed Apr 24, 2013 5:26 pm
by
Danimal » Fri Jul 19, 2013 4:07 am
Crashing on me too. Most notably when i have a
project open and i try to add another VST instrument. To be specific,
one time it was Halion Sonic SE, and today i cannot load the
AmpSimulator plugin into my project without it crashing.. even with a
system reboot... gave up.
Danimal
Cubase 5LE
Cubase 7
2011 Macbook Pro 13"
Tascam US-1800 midi interface
OWC 2TB Ext. Drive
-
Danimal
- New Member
-
- Posts: 35
- Joined: Fri Sep 23, 2011 12:29 am
Finally figured out what's causing this. Found it in this forum:
https://www.steinberg.net/forum/viewtopic.php?f=184&t=44301On
my system, when an insert slot is selected (outlined in red) or maybe
when the insert section has focus AND you close the Mix Console with F3
it crashes. If anything else is the focus (the faders, etc), no crash.
There
is a fix somewhere in that thread from a German forum. I have not
tried it yet. It involves uninstalling Cubase, Reinstalling 7.0.0, then
7.0.2 then going straight to 7.0.5 then saying the magic word then
initiating the secret handshake, saying a prayer,
doing countless MORE
hours of beta testing...
Desktop: Cubase 7.0.5 Wavelab
8.0.2, Halion 4.5.4, Presonus StudioLive 24.4.2, CPU Intel Core 2 Quad
Q9550 2.83gHz, Motherboard Asus P5Q Pro, RAM Corsair 8gb (2x4gb), Video
Card MSI R5450 (no fan), PSU Zalman ZM600 HP, Zalman Reserator 1 liquid
cooled system, Windows 7 x64 Home Premium, Pro Tools 9.0.6, Waves
Mercury Native 9.2.6
Laptop: MacBook Pro (15 in), 2.4 gHz Intel Core i7, 8 gb RAM, OSX
Mountain Lion 10.8.4, Focusrite Saffire Pro 14 (Driver v 3.2), Presonus
StudioLive 24.4.2, Philips DVD+-RW SDVD 8820 SATA drive, Wavelab
8.0.2, Cubase 7.0.5, Halion 4.5.4, Pro Tools 9.0.6, Waves Mercury Native
9.2.6
-
timmyboylad
- Junior Member
-
- Posts: 179
- Joined: Thu Dec 16, 2010 8:25 pm
Update...
On my Windows machine, I
uninstalled Cubase and reinstalled up to 7.0.4 and no more crashes when
F3ing the Mix Console when an insert slot is selected.
...
Desktop: Cubase 7.0.5 Wavelab
8.0.2, Halion 4.5.4, Presonus StudioLive 24.4.2, CPU Intel Core 2 Quad
Q9550 2.83gHz, Motherboard Asus P5Q Pro, RAM Corsair 8gb (2x4gb), Video
Card MSI R5450 (no fan), PSU Zalman ZM600 HP, Zalman Reserator 1 liquid
cooled system, Windows 7 x64 Home Premium, Pro Tools 9.0.6, Waves
Mercury Native 9.2.6
Laptop: MacBook Pro (15 in), 2.4 gHz Intel Core i7, 8 gb RAM, OSX
Mountain Lion 10.8.4, Focusrite Saffire Pro 14 (Driver v 3.2), Presonus
StudioLive 24.4.2, Philips DVD+-RW SDVD 8820 SATA drive, Wavelab
8.0.2, Cubase 7.0.5, Halion 4.5.4, Pro Tools 9.0.6, Waves Mercury Native
9.2.6
-
timmyboylad
- Junior Member
-
- Posts: 179
- Joined: Thu Dec 16, 2010 8:25 pm
Yep, Count me in fellas. 7.05 creates a virtual paperweight...
Projects don't load, sometimes Cubase gets "Stuck" on opening and freezes...
Now, thanx to this I have waste my time on uninstalling, reinstalling and fixing.
I was a supporter and on the positive site of C7 but now I'm a little disappointed 
Custom Built WS:
i7 3930k @ 4.2Ghz | Corsair H100 | 32GB GEIL Evo Corsa DDR3 @ 1600 |
Sapphire HD7950 Dual X | MSI BigBang XPower II | Enermax Platimax 1200w
80+ Platinum |
2x SanDiskSSDX12 + 2x WD2500 HDD+ WD4001 HDD | Coolermaster Cosmos II
Cubits : | Cubase 7.01 b-2078 64bit | CMC-TP | CMC-CH
Sound Gear: Access Virus Ti ,Virus C | Korg Triton pro 76 | Roland XV-5080, JV-2080 | Yamaha AW4416 | MOTU 2408mk3, MidiXT | Mackie HR824
-
theRoyal1
- Junior Member
-
- Posts: 169
- Joined: Fri Nov 04, 2011 5:08 pm
-
Even worse
now... seems like uninstalling, reinstalling and updating back to 7.04
has made some other software installation that worked fine before
totally unstable and Cubase now crashes Every time it shuts down...
This is now becoming an *&#@ headache...
Custom Built WS:
i7 3930k @ 4.2Ghz | Corsair H100 | 32GB GEIL Evo Corsa DDR3 @ 1600 |
Sapphire HD7950 Dual X | MSI BigBang XPower II | Enermax Platimax 1200w
80+ Platinum |
2x SanDiskSSDX12 + 2x WD2500 HDD+ WD4001 HDD | Coolermaster Cosmos II
Cubits : | Cubase 7.01 b-2078 64bit | CMC-TP | CMC-CH
Sound Gear: Access Virus Ti ,Virus C | Korg Triton pro 76 | Roland XV-5080, JV-2080 | Yamaha AW4416 | MOTU 2408mk3, MidiXT | Mackie HR824
-
theRoyal1
- Junior Member
-
- Posts: 169
- Joined: Fri Nov 04, 2011 5:08 pm
-
So I decided to
live on the edge and re-install 7.05 after reverting to 7.04. Started
messing with some of the problems I had and it turned out that my midi
configuration got "Wonky" which was locking up my controller and not
allowing the loading to complete.
I figured this out when I physically pulled my Midi cable out and it then continued with the load...
I'm
not about to start tryin to figure this one out because one thing we
should all know by know is to leave well enough alone!! 
That
said, if your install is crashing, double check your drivers and midi
configs... seems to have worked for me after going through will all the
troubleshooting.
Custom Built WS:
i7 3930k @ 4.2Ghz | Corsair H100 | 32GB GEIL Evo Corsa DDR3 @ 1600 |
Sapphire HD7950 Dual X | MSI BigBang XPower II | Enermax Platimax 1200w
80+ Platinum |
2x SanDiskSSDX12 + 2x WD2500 HDD+ WD4001 HDD | Coolermaster Cosmos II
Cubits : | Cubase 7.01 b-2078 64bit | CMC-TP | CMC-CH
Sound Gear: Access Virus Ti ,Virus C | Korg Triton pro 76 | Roland XV-5080, JV-2080 | Yamaha AW4416 | MOTU 2408mk3, MidiXT | Mackie HR824
-
theRoyal1
- Junior Member
-
- Posts: 169
- Joined: Fri Nov 04, 2011 5:08 pm
-
Hi,
since I've encountered a bad unstability into my Cubase 7.0.5, I'll write here what happens to me:
Each
time (I say each time!) I open the mixer console and press the E button
(over the volume cursor) to adjust the input gain of a channel, Cubase
stops working and a Windows message says the application (Cubase) will
be closed.
All the new data of the project are, of course, lost
forever. Once Cubase is open again, it doesn't even remember the project
that was open before crashing.
In some other cases, Cubase stops
itself without an apparent reason (this always appens while I'm setting
some other parameter within the mixer console. I've never encountered a
problem while I'm recording or rehearsing), but when it happens the
Windows message and the effects on the project are the same as above.
Increasing the buffer (with more latency) has no effect. The problem is, in my opinion, inside Cubase.
It
can't go on this way. Cubase has never been that unstable (I've passed
through all the versions from Cubase 4 to 7.0.5). People at Steinberg
should really fix this bad bug as soon as possible.
Hope to listen to some good news soon.
Maurizio - Italy
PC Intel I7 CPU - windows 7 64 bit - 16 Gb RAM - 128 Gb SSD System HD;
MOTU 24 I/O;
The entire system has been setup to work as a 96 KHz - 24 Bit audio recorder (no other unuseful programs are installed inside).
-
maurigati
- New Member
-
- Posts: 3
- Joined: Sun Jul 28, 2013 1:26 pm
Hi Maurizio,
I think your crash is
different than mine (though no less troubling). Version 7.0.5 seems to
be the most unstable yet. Since the release of 7.0.5 I have seen many
posts about this instability but not much response from Steinberg.
Hopefully they are quietly listening and preparing fixes in the next
release.
In the mean time, I'm wondering about your loss of work
when a crash occurs. Do you have auto save turned on in Cubase's
preferences? I have it turned on and set to back up every ten minutes.
For auto save to work easily, you'll need to create the project and
save it as something right away. Even if the program crashes before you
save the first time, the program SHOULD auto save to the chosen
directory as "Untitled" or something like that.
That should help you be able to get back at least ten minutes into your work.
Good Luck!
Desktop: Cubase 7.0.5 Wavelab
8.0.2, Halion 4.5.4, Presonus StudioLive 24.4.2, CPU Intel Core 2 Quad
Q9550 2.83gHz, Motherboard Asus P5Q Pro, RAM Corsair 8gb (2x4gb), Video
Card MSI R5450 (no fan), PSU Zalman ZM600 HP, Zalman Reserator 1 liquid
cooled system, Windows 7 x64 Home Premium, Pro Tools 9.0.6, Waves
Mercury Native 9.2.6
Laptop: MacBook Pro (15 in), 2.4 gHz Intel Core i7, 8 gb RAM, OSX
Mountain Lion 10.8.4, Focusrite Saffire Pro 14 (Driver v 3.2), Presonus
StudioLive 24.4.2, Philips DVD+-RW SDVD 8820 SATA drive, Wavelab
8.0.2, Cubase 7.0.5, Halion 4.5.4, Pro Tools 9.0.6, Waves Mercury Native
9.2.6
-
timmyboylad
- Junior Member
-
- Posts: 179
- Joined: Thu Dec 16, 2010 8:25 pm
+1
What is wrong with you programmers at Cubase? This really sucks!
Weird stuff is happening, even on 7.04, which is what I had to re-install.
You're making it so hard to work. You had some good ideas and you're just screwing them up.
Keep it simple and Get it Together, Please !!!!
-
rchaisse
- New Member
-
- Posts: 14
- Joined: Tue Mar 20, 2012 6:50 pm
timmyboylad wrote:Hi Maurizio,
I
think your crash is different than mine (though no less troubling).
Version 7.0.5 seems to be the most unstable yet. Since the release of
7.0.5 I have seen many posts about this instability but not much
response from Steinberg. Hopefully they are quietly listening and
preparing fixes in the next release.
In the mean time, I'm
wondering about your loss of work when a crash occurs. Do you have auto
save turned on in Cubase's preferences? I have it turned on and set to
back up every ten minutes. For auto save to work easily, you'll need
to create the project and save it as something right away. Even if the
program crashes before you save the first time, the program SHOULD auto
save to the chosen directory as "Untitled" or something like that.
That should help you be able to get back at least ten minutes into your work.
Good Luck!
Thanks Timmyboylad for your kind replay!
Waiting for some good news by the Steinberg Team, I think I'll go back to the 7.0.4 version of my Cubase.
I
do have the automatic save turned on, but fine tuning the input
settings is one of the very first things I do before pressing the REC
button, so very often the crashing occours before any "normal" auto save
procedure.
As said, what sounds strange to me is that, after the
crash occours, the last opened project is not even included into the
index that Cubase creates each time you simply open (not saving) a
project.
An example: open an existing project and close it without
saving. Then go to the option "recently open projects" in the lower part
of the "file" tab: you should see that project name at the top of the
list (as the last open project). Well: after a crash I dont' see that
project name into the index.
Of course, after having saved the
project (manually, and before the crash), I can find it in its own
location and the title is included into the index of the last opened
projects.
Best Regards
Maurizio
-
maurigati
- New Member
-
- Posts: 3
- Joined: Sun Jul 28, 2013 1:26 pm
Hello,
let me quote what I wrote in another thread, as it applies here also:
Fabio Bartolini wrote:
[...]
About fixing:
Cubase
7 is not broken. But we are indeed aware that some of you are having
problems and are interested in knowing why and find out what can be
improved and made more reliable on as many machines as possible or help
the users with solving the problem, where local.
As Support, we are committed to this, and some cases have been carried on for weeks.
Cubase
7 is working fine on most machines and we found the performance being
pretty much the same of Cubase 6.5 (even better on some Windows 8
machines). Therefore, it is important that those having performance or
crashes contact Support, as your issues cannot be solved by checking on a
trouble-free setup and developers cannot fix what isn’t reproducible on
our side.
We will look into the system, examine crash logs, study
the configuration, talk to the users, do remote sessions and collaborate
with Development to spot system specific issues wherever necessary.
Support does this on a case-by-case basis.
Some of those who are
complaining have not contacted Support – for example, I offered to
contact us in order to help those receiving the "Video Engine" error in
that very thread, but have been contacted only by one user.
This is not going to help the users and slows down Steinberg in its effort to constantly improve.
We
are collecting data to see on which systems Cubase 7 is not working
100%, so if you contacted support and didn't receive an answer yet,
please send me a PM and I will add your reports to the collected ones.
Thank you, wish you all a nice week.
Kind regards,
Fabio Bartolini, Steinberg Tech Support
Steinberg Media Technologies GmbH
Hamburg, Germany
Check out Steinberg on YouTube, Twitter and Facebook!
-
Fabio Bartolini
- Moderator
-
- Posts: 44
- Joined: Tue Oct 02, 2012 11:55 am
Hi Fabio,
Thank you for your response,
however, when people are using a 7.0.4 and it is not crashing, then they
upgrade to 7.0.5 and it crashes and they lose there work.. it's broken.
No matter how you want to deny it.
I have also experienced this
same problem. I am a computer tech as well as a programmer. I did not
make any changes between 7.0.4 & 7.0.5. Did YOU? Did you change
something we aren't aware of? Should you have included some special
instructions that appear as the upgrade starts it's process.
Because
you have had so many updates that have problems, it seems to me that
your foundation is not as stable as you might think. Instead of adding
all these 'features', I would prefer to have a program that works
smoothly. then the features could be tested on a stable foundation and
shouldn't cause the types of complaints that I'm reading about.
Most of us don't have the time or patience to put up with your experimenting.
I'm not going to blame the programmers anymore.. This is clearly a management issue.
Someone needs to fix this..
-
rchaisse
- New Member
-
- Posts: 14
- Joined: Tue Mar 20, 2012 6:50 pm
by
dr4kan » Mon Jul 29, 2013 7:10 pm
rchaisse wrote:Hi Fabio,
Thank
you for your response, however, when people are using a 7.0.4 and it is
not crashing, then they upgrade to 7.0.5 and it crashes and they lose
there work.. it's broken. No matter how you want to deny it.
I
have also experienced this same problem. I am a computer tech as well
as a programmer. I did not make any changes between 7.0.4 & 7.0.5.
Did YOU? Did you change something we aren't aware of? Should you have
included some special instructions that appear as the upgrade starts
it's process.
Because you have had so many updates that have
problems, it seems to me that your foundation is not as stable as you
might think. Instead of adding all these 'features', I would prefer to
have a program that works smoothly. then the features could be tested on
a stable foundation and shouldn't cause the types of complaints that
I'm reading about.
Most of us don't have the time or patience to put up with your experimenting.
I'm not going to blame the programmers anymore.. This is clearly a management issue.
Someone needs to fix this..
+1
As
written in another thread, never experienced a single crash since
upgrading (?) to 7.0.5.. Since then, I deal with crashes every day...
Mac i7 16 GB ram, OSX 10.8.3
MOTU 828mk3, MOTU Ultralite, MCU Pro, CC121, ...
-
dr4kan
- Member
-
- Posts: 253
- Joined: Tue Dec 18, 2012 10:30 pm
Fabio Bartolini wrote:Hello,
let me quote what I wrote in another thread, as it applies here also:
Fabio Bartolini tells a huge lie....
[...]
About fixing:
Cubase
7 is not broken. But we are indeed aware that some of you are having
problems and are interested in knowing why and find out what can be
improved and made more reliable on as many machines as possible or help
the users with solving the problem, where local.
As Support, we are committed to this, and some cases have been carried on for weeks.
Cubase
7 is working fine on most machines and we found the performance being
pretty much the same of Cubase 6.5 (even better on some Windows 8
machines). Therefore, it is important that those having performance or
crashes contact Support, as your issues cannot be solved by checking on a
trouble-free setup and developers cannot fix what isn’t reproducible on
our side.
We will look into the system, examine crash logs, study
the configuration, talk to the users, do remote sessions and collaborate
with Development to spot system specific issues wherever necessary.
Support does this on a case-by-case basis.
Some of those who are
complaining have not contacted Support – for example, I offered to
contact us in order to help those receiving the "Video Engine" error in
that very thread, but have been contacted only by one user.
This is not going to help the users and slows down Steinberg in its effort to constantly improve.
We
are collecting data to see on which systems Cubase 7 is not working
100%, so if you contacted support and didn't receive an answer yet,
please send me a PM and I will add your reports to the collected ones.
Thank you, wish you all a nice week.
Kind regards,
One thing that the DAW makers do when they know their DAWs are shitty Beta-ware is blame the computer when their DAWS fuck up. Steinberg is also another lying DAW developer and vendor. Cubase is crashing on Windows and Mac so for Fabio Bartolini to lie and say it is a computer problem is fucking laughable and shameful all at the same time.
Hi Fabio,
I
am still having CPU spikes and some unstable issues, beforehand I did
upgrade from 7.0.0 straight to 7.0.5, and when running 7.0.5 I had many
crashes and unstable problems could not even carry on with my
production, so I went back to 7.0.0 and now I only get spikes and
sometimes cubase runs slow at certain moments, no crashes yet though.
I
have a brand new Macbook pro, my specs are attached, I am still not
happy with these issues and I expected more from C7, I love my Cubase
but these issues must get sorted out, I paid a lot of money for this
upgrade and expect it to run smoothly, I was running cubase 4 before
this on my old PC and had no issues like this.
How do I contact support?
Thank you
Cubase 7
Akai MPK 25 MIDI Keyboard
Focusrite Scarlett 8i6 USB soundcard
Yamaha HS80M Monitors
Macbook Pro, 15" Mid 2012, 2,3Ghz Quad-core Intel i7
Turbo boost 3.3GHz
4G Ram
500G harddrive
OSX 10.8.4
-
Audionic
- New Member
-
- Posts: 12
- Joined: Sat Jul 13, 2013 2:51 pm
Had a bit of a 7.0.5 scare last night. Last
night I completed a song I'd been working on for the past month, and
rendered out to WAV. When that was done I did a save-on-exit, but Cubase
crashed in the process. I didn't think too much of it until an hour
later when I launched Cubase again and opened my project, only to be
alerted that Cubase couldn't find like 20 of my plugins anymore. All the
plugins were still showing up in the Plugin Manager; the project just
couldn't load 'em.
After about an hour of troubleshooting, I was
able to get the project to load again by deleting the Cubase preferences
folder, re-updating my plugin paths, and then opening the project. If
this happens again I will definitely file a report; just wanted to
mention the workaround here in case it happens to anyone else.
One
other thing that happened during the production of this project (all
done on 7.0.5 64-bit) is that two of my plugins, Waldorf Lector and
FXpansion Tremor behaved very erratically... several times I had to
exit/restart Cubase to get them to produce audio or otherwise behave
normally. Actually I had to completely remove Lector and replace it with
a less flexible plugin because it was too unreliable. I don't know if
the real fault was with Cubase or the plugins though. Very frustrating.
(Will def submit a support request if I encounter similar behavior in
future projects.)
-
UltimateOutsider
- Junior Member
-
- Posts: 119
- Joined: Tue Apr 10, 2012 6:18 am
by
Danimal » Tue Jul 30, 2013 3:46 am
I was using Cubase in 32 bit mode, switching to 64bit mode fixed all my previous crashes i posted about for 7.0.5.
Give it a try and see if it helps.
Danimal
Cubase 5LE
Cubase 7
2011 Macbook Pro 13"
Tascam US-1800 midi interface
OWC 2TB Ext. Drive
-
Danimal
- New Member
-
- Posts: 35
- Joined: Fri Sep 23, 2011 12:29 am
@Audionic: replied to your PM.
@rchaisse:
if you are a programmer, you most probably have a clean system with not
so many applications which could trigger the issues, you are welcome to
send a support request (if you live outside EU, please PM me and I will
send you instructions on how to send it) - should be easier to spot
issues on a clean system.
We have made several performance and
compatibility tests with 7.0.5 on many machines, so we are looking
forward to see why this is not consitent for all of the users.
I
think the foundation is stable - but you perfectly know how fixing
something for a given number of systems might trigger something weird on
other systems, especially with such a huge and complex application.
I'm looking forward for your report, if you are willing to collaborate.
@
dr4kan and UltimateOutsider: same as above - if you are willing to
collaborate and have us looking into your issue, please contact support
(same means as for rchaisse).
Thanks everyone.
Fabio Bartolini, Steinberg Tech Support
Steinberg Media Technologies GmbH
Hamburg, Germany
Check out Steinberg on YouTube, Twitter and Facebook!
-
Fabio Bartolini
- Moderator
-
- Posts: 44
- Joined: Tue Oct 02, 2012 11:55 am
If you want my assistance I will be glad to help but we need to talk on the phone.
I provide tech support to many people and to try to do that via e-mail is ludicrous.
I need to work in real time. Questions and comments need to be exchanged in moments, not days.
Let's work together and get past this nightmare.
I am located in the U.S. How may we communicate? Evenings (GMT-8) are best for me.
-
rchaisse
- New Member
-
- Posts: 14
- Joined: Tue Mar 20, 2012 6:50 pm
I upgraded to Cubase 7.05 from 7.02 tonight using this path:
1) 7.03
2) 7.05
I make a living using Cubase and I can't afford for it to be broken. I am not a happy camper!
That's all I have to say about that!
-
nathanieldiazrua
- New Member
-
- Posts: 1
- Joined: Wed Jul 31, 2013 1:13 am
-
rchaisse wrote:Instead
of adding all these 'features', I would prefer to have a program that
works smoothly. then the features could be tested on a stable foundation
and shouldn't cause the types of complaints that I'm reading about.
Most of us don't have the time or patience to put up with your experimenting.
Someone needs to fix this..
rchaisse wrote:
I'm not going to blame the programmers anymore.. This is clearly a management issue.
Agreed 110% with you.
I
should also mention one thing about SB's support: emails take very long
to be replied. If I want phone support, I have to make a paid long
distance call in order to get support for my products....and worst, it
is BAD quality support with people who are poorly informed.
It makes me wanna sell all my Steinberg products and go somewhere else.
DAW: Cubase 7 + Many Plugins @ Win7x64 | Intel i5-2500 | 16GB Corsair DDR3 RAM | 2TB Seagate Sata 3 HDD | 24' Acer FullHD Display Hardware: Steinberg UR28M | Yamaha HS-80
-
diogo_cme
- Junior Member
-
- Posts: 111
- Joined: Thu Apr 26, 2012 12:23 am
diogo_cme wrote:I should also mention one thing about SB's support: emails take very long to be replied.
This
pretty much depends on the amount of incoming requests and how complex
the requests are. We are sorry that we cannot always reply in a few
hours, but we do our best. Moreover, some cases get priority - as you
might guess a Studio that lost the license needs to be sorted out before
an e-mail containing only Feature Requests.
diogo_cme wrote:If I want phone support, I have to make a paid long distance call in order to get support for my products
You actually can, if you send a support request and need direct support, the US Team will call you.
diogo_cme wrote:....and worst, it is BAD quality support with people who are poorly informed.
You
are entitled to have your opinion. But Support members all have a
pretty in-depth general knowledge and some specialities - so, although
the person that replies to you is not the most prepared in the field you
need support with, he / she can ask to the specialist.
If the issue cannot be solved by the local Team, it gets forwarded to the HQ for further investigation.
For
sure, a support case is started in a general way, addressing the most
common issues, especially if the report is not detailed - but in case of
need we do remote support, collaborate with other Teams to solve the
problem, which we do in the vast majority of cases. So I don't see how
this is bad. YMMV.
Do you have any current issues you need to be solved?
Kind regards,
Fabio is clearly a corporate scumbag shill. He got an offer from a computer tech and software engineer to fix this awful DAW and now he is back peddling! Typical corporate crook!
Click here to read more... It gets really ugly as more lying Steinberg socks and shills come on board to trash the Cubase user/victims.
Even more...
HERE!
