Cubase.net = locked threads GALORE!!!

[pavvel]

Maybe I should start an unofficial cubase sx forum

[CorrosiveGod]

I’m sure you could too. The issue’s not so much the bugs (although really dbLaw and BUS summing in SX2 was awesomely shocking) – it’s what Steinberg does about them bugs, how Steinberg doesn’t conduct even baseline QA on it’s dot-zero releases, and how Steinberg reneges upon the promises it makes when selling new versions – these features are unique to Steinberg, and Steinberg alone. No other company in audio software has such a proven, established and long running reputation for clucking defiance.

Not a single version of Cubase since VST 3 (for Cubase users who can’t add that’s nine years running) has been finished. Every Major release of every Cubase-named audio product has been discontinued before closing its outstanding bug sheet. The nearest contender (Cubase SX 2.2 dot something or another, after an avalanche of complaint from its user base) wasn’t actually released as fixed – just unsupported hot patches released in a cupboard marked beware of the leopard.

So it’s no good waiting for Cubase SX 3.1, even it actually fixes the bugs in Cubase 3.0 (and please don’t make me publish the version history here, it’s sooo boring), the new ‘features’ leveraged into it will be so buggy as to require you to pay for yet another major number release. You won’t ever have a copy of Cubase that doesn’t have open and known bugs – Steinberg has never released one, and never will as long people keep parting with money for it.

Try that on Samplitude 7.22 users or Sonar 4 users. At least those bugs actually got fixed. With Bullshitberg, the bugs get features. Sorry if you don’t like it old matey, it usually takes two or three $400’s worth before most people start seeing what the game actually is. Assuming you can count that is.

You hit the problem right on the nose and the reason why I don't buy Bullshitberg's software any more.

[pavvel]

I’m sure you could too. The issue’s not so much the bugs (although really dbLaw and BUS summing in SX2 was awesomely shocking) – it’s what Steinberg does about them bugs, how Steinberg doesn’t conduct even baseline QA on it’s dot-zero releases, and how Steinberg reneges upon the promises it makes when selling new versions – these features are unique to Steinberg, and Steinberg alone. No other company in audio software has such a proven, established and long running reputation for clucking defiance.

Not a single version of Cubase since VST 3 (for Cubase users who can’t add that’s nine years running) has been finished. Every Major release of every Cubase-named audio product has been discontinued before closing its outstanding bug sheet. The nearest contender (Cubase SX 2.2 dot something or another, after an avalanche of complaint from its user base) wasn’t actually released as fixed – just unsupported hot patches released in a cupboard marked beware of the leopard.

So it’s no good waiting for Cubase SX 3.1, even it actually fixes the bugs in Cubase 3.0 (and please don’t make me publish the version history here, it’s sooo boring), the new ‘features’ leveraged into it will be so buggy as to require you to pay for yet another major number release. You won’t ever have a copy of Cubase that doesn’t have open and known bugs – Steinberg has never released one, and never will as long people keep parting with money for it.

Try that on Samplitude 7.22 users or Sonar 4 users. At least those bugs actually got fixed. With Bullshitberg, the bugs get features. Sorry if you don’t like it old matey, it usually takes two or three $400’s worth before most people start seeing what the game actually is. Assuming you can count that is.

You hit the problem right on the nose and the reason why I don't buy Bullshitberg's software any more.

Yep I agree totally as well. Could have said it better myself.

Bullshitberg....lmao

[drinelli]

Cubase SX 3, on my system, no bugs, Maybe I need glasses, Or maybe a new system, to get them. Or maybe I work around them therefore not noticing them. Or maybe todays PCs are so different from each other, some code is good on some, bad on some other. Maybe the situation is simply an attitude problem between Costummers and Steinberg, and maybe all it needs is a call, to getting the problems solved. Conflicts never solve problems, they make them. So can we have world peace please...... eh wrong forum , well it was worth the try

[Sascha Franck]

Cubase SX 3, on my system, no bugs

Read my recent rant about the solo functionality.
If that doesn't qualify for a program being buggy, whatelse will?

[Muzik 4 Machines]

i think this is it, i'm selling my cubase SX2, i can't continue to deal with a bunch of liars and FUD at yamaha/steinborg. They don't even respect their legit users like us, they treat everybody like pirates, it's not good marketting

[GypsyJazz]

For me it is simply the fact that I don't like Cubases interface or work flow...I find SONAR much easier to understand and operate.......

And no DONGLE! That is a major difference.

Cubase just seems really clunky and obtuse compared to SONAR.

I can't understand why anyone uses it ...........

[peejunk]

Without any dongle jokes this thread was as dry and uninspiring as Cubase itself.

[HanafiH]

[img]http://www.championship_606.ursatech.com/images/comical_ali.jpg[/img]

What do you say to a Cubase user with two back eyes? Nothing, you told him twice already!

[james0tucson]

It’s an argument that you can’t win. Steinberg has an inalienable right to require proof of purchase before supplying support.

Thats exactly what I'm talking about, users who Steinberg already knows to be legit, who purchased their licenses and registered their products with them.
If they want only users with registered products to post - they could do that without bothering users and treating them like criminals.

They have a right to refuse service to anyone, unless you've got a contract that states otherwise. Proof of purchase is a Red Herring here.

Why did you jump in bed with these people, only to complain later about getting crabs?

[HanafiH]

It’s an argument that you can’t win. Steinberg has an inalienable right to require proof of purchase before supplying support.

Thats exactly what I'm talking about, users who Steinberg already knows to be legit, who purchased their licenses and registered their products with them.
If they want only users with registered products to post - they could do that without bothering users and treating them like criminals.

They have a right to refuse service to anyone, unless you've got a contract that states otherwise. Proof of purchase is a Red Herring here.

Why did you jump in bed with these people, only to complain later about getting crabs?

That depends upon where you live, the physical delivery media is covered in Europe by statutory rights.

Whatever we can all rejoice that this immaculate and flawlessly lovely problem, sorry product, has had the following problems fixed:

The following problems have been fixed in Cubase SX/SL version 3.1
• "Open Default Project" on startup from Preferences\General has no function.
• "Can Hide" as well as narrow/wide status of channels are not correctly
recalled after opening a project (this has been fixed for projects made with
version 3.x).
• "Enable Auto Select" setting was not saved for Mackie Control device setup.
• If the function Pool/"Remove unused Media" is involved in a Macro, it may
work unreliably.
• "Keep Notes in Range" option was broken in Transpose dialogue.
• OMF: The handle-length for events is not stored into OMF-File when "Export
All to one File" and "consolidate events" option is enabled in the OMF-Export
menu.
• Using "Control-Click" for the Insert-Bypass-Button of Track- Controls to list
the used plug-ins will lead to crash when two projects are open and you
toggle between the two projects.
• Input VU meter doesn't work on mono tracks when more than one track
records from the same input bus.
• ASIO-Delay-Compensation doesn’t work with some Audio Interfaces.
Concerned are as far as we know ECHO Layla and Soundscape Mixtreme.
Side effect: MIDI and Audio run out of Sync.
• Assigning and recording more than one input bus to several audio tracks
does not work. Signal will only be recorded to one track.
• Insert a new key sig or new clef somewhere in the middle of a page. 2) Add
another new key sig/clef at the beginning of the next page. = doesn't work as
it should.
• A crash could happen in Score Editor after inserting Key Signatures.
• An issue was fixed when modifying plug-in settings in Offline Process.
Cubase SX 3.1 – Version History 5 of 11 Last Update: August 2005
• Arpache SX can produce hanging notes, when a recorded session is played
back.
• Audio part editor: The mute tool does not work if the range tool has been
used before.
• Building N-Tuplets in Score Editor could led to crash.
• Bypass status for Insert-FX in the Mixer was sometimes not recalled as
saved.
• Clef changes in Score Editor sometimes to applied to the desired Voices.
• Copied tracks showed wrong lyrics in Score Editor.
• Crash when dragging a MIDI-Event into the Input Transformer.
• Crash when importing certain Cubase 5.x Songs.
• Crash when pressing multiple transport buttons at the same time.
• Application may crash if you create automation tracks for FX tracks and then
un-/reload a plug-in on that FX track.
• Different velocity values in midi parts are not recognized during playback. All
events are played using the same velocity value.
• DirectX plug-ins are not disabled in the offline process menu after being
deactivated in plug-in Information window.
• Display Length in Score Editor was not working.
• Dots in a dotted notes chord are not aligned.
• Drawing a ramp in Tempo Track and starting playback may lead to crash if
audio warp is active.
• Drum Map settings in Score Editor sometimes not remembered.
• Each Time you close the Score-Editor, MIDI and audio drops out for a
moment.
• Editing of audio events can be slow, especially if many events are
warped/musical/transposed/crossfaded.
• Export Tracks / import archive ignores start times.
• Folder Track problem with copy and paste of events inside folder: Pasted
events location is shifted.
• Folder tracks don't stay selected after duplicating.
• Group of events/parts could get dissolved when "Duplicate" command was
used.
• Groups within folder tracks could break the signal path (no sound).
• It was not possible to expand / collapse multiple Folders in project window.
• It was not possible to change shape of note heads in Score Editor.
• Latency shifts when using MPEX with pitch-envelope -> these shifts should
be compensated by time-stretching simultaneously.
• Moved notes to lower staff sometimes not aligned in Score Editor.
• MPEX Algorithm produces wrong results on events with offset (event start not
at 0). E.g. cut an audio event and process the rear part.
• Multi track recording can result in freeze depending on Zoom Factor).
• Display mismatch of MIDI Insert-FX with Mackie Control display.
• Application doesn't completely quit if Hyperthreading is enabled with Dual
CPU computers. Also possible crashes on loading projects.
• Application crashes after loading a project that contains a frozen VSTi Track.
• Application may crash after closing project without saving, followed by option
"delete created files" = yes".
• Application may crash when changing clef on the second staff.
• Page Mode in Score Editor had problems with MIDI Step Input.
• Pool: Convert Stereo file Mono may cause crash
• Pool: Tempo information not always stored immediately with audio file.
• MIDI Pre-record does not work after beat 4 of count in.
• Pressing "Escape"-key to cancel dialogues sometimes led to undesired
behavior
• Application may freeze if you remove Groups from the VST Connections
window while playback is running.
• Program Changes have not been exported to MIDI file when a Patch Name
list was used.
• Random crashes after project load.
• Recalling Workspaces could change Solo states of tracks.
• Score - Step Input fails if multiple parts are used.
• Score - Application may crash after undoing "Delete" of massive number of
notes.
• Score: nudge a group of notes sideways changes the stem length.
• Score: Select status of notes (highlighted) is sometimes incorrect if you select
notes using arrow keys.
• Several fixes for Page Layout problems in Score-Editor.
• Shuttling across video clip edits can cause lockups.
• Stems sometimes wrong after moving events form one staff to another in
Score Editor.
• Symbols in Score Editor were gone after copying a part.
• Tempo symbol in Score Editor showed wrong value.
• Hide function in Score Editor sometimes did not work as expected.
• Turning monitor switch on without having physical input selected in VST
connection panel could lead into instable application.
• Under certain conditions you were able to move/resize files to a negative filelength.
Intermittently this even may result in crash.
• Using Game Joystick for Surround Panning can lead to freeze.
• Video (PC-only): Thumbnails are not displayed while winding, scrolling, etc.
This only occurs with QuickTime video player on windows based system.
• In Cubase/Nuendo 3.x the Record Latency could vary. The greater the buffer
size, the higher the latency (negative value).
• Writing automation with Key Editor open could not be undone.

[flex42]

come on...it only took 'em a year to fix that

[drinelli]

maybe i have come across one or two of them, but not anymore, most of the mentioned functions i never used, i just make music with cubase, nothing else. But i can understand those who need this must be frustrated.