I am on win 64 too and every setting incl. the plugin manager was remembered correctly.rustman wrote:Windows 64 bit.TheoM wrote:Mac or windows?rustman wrote:Looks like 8.5 doesn't remember your plugin manager settings. I spent a long time tweaking the folder structure last night and it's gone today. Still crashes my system when scanning plugins too. I don't use any 32 bit plugins anymore (no wrappers) just to try and reduce this hassle.
i think the best thing right now is to wait a few months for final release.
perhaps if i upgrade to 8.5 when 9 has been announced, i can pay the $50 USD and get into 9 for free.. nothing wrong with using 8.03 for the next few months, nothing at all.
Cubase 8.5 here any day now...and the day has come
-
- KVRAF
- 2048 posts since 13 May, 2004 from Germany
-
- KVRAF
- 2048 posts since 13 May, 2004 from Germany
btw. Cubase own Revelation is a damn fine reverb.
Although I own third party reverbs incl valhalla I often chose Revelation ...
Although I own third party reverbs incl valhalla I often chose Revelation ...
-
- KVRAF
- 5914 posts since 25 Jan, 2007
(last OT diversion I promise - if as you say you will never update the OS, then over time new updates and products won't work with it. I'm not sure when we'll start to see Win 7 deprecation, might only be a year or two though).T-CM11 wrote:Why can't I update anything on it? Or add to it?noiseboyuk wrote:...and that's all good provided you never want to update anything on it, or add anything to it.T-CM11 wrote:It works for other people... my DAW laptop is always offline, and will never be updated from Windows 7.
Not that I'll be adding a lot, I have more than enough music software to do anything I want.
http://www.guyrowland.co.uk
http://www.sound-on-screen.com
W11, Ryzen 7900, 64gb RAM, RME Babyface, 1050ti, PT 2024 Ultimate, Cubase Pro 14
Macbook Air M2 OSX 10.15
http://www.sound-on-screen.com
W11, Ryzen 7900, 64gb RAM, RME Babyface, 1050ti, PT 2024 Ultimate, Cubase Pro 14
Macbook Air M2 OSX 10.15
-
- KVRAF
- Topic Starter
- 7097 posts since 22 Jan, 2005 from Sweden
It might be more complicated.el-bo (formerly ebow) wrote: pure laziness, especially considering the price of their product
Devs of daw don't only rely on what their devs do.
- cross plaform libraries like QT and JUCE
- players like Quicktime
- OS updates
If any of those are not backward compatible, you need to draw a line - what you say is supported.
Currently your are stuck with Quicktime 7.5.5(I think it was) to work on windows 10 - waiting for Apple to fix it.
Last week I looked what PC computer models are on stock on a online retailer.
Windows 10 with downgrades to Windows 7(with/without dual boot) - 2 models
Windows 8.x with downgrades to Windows 7 - 22 models
Windows 7 - 75 models
still today.
So I hope Windows 7 is not dropped by MS or daw vendors in near future.
Bigger institutions like banks are a bit hysterical when it comes to MS updates - and had to change User Agent on my browser not showing I run XP still on my machine usually used for internet.
- what exactly is safer now, doing that?
- how much do banks know about security anyway....not so much, they go by what security companies tell them.
I'm asking myself, what exactly after 15 years of updates on XP is unsafe?
- Microsoft dropped updates - update OS or buy new computer everybody!!!!!
If MS sales techs tell security companies they recommend updating OS, security techs hired by institutions tell institutions the same thing - and the money keep rolling in with updates for new computers and OS and stuff. So any node in the chain of sales is interested in that everybody think new computer/os is needed - even daw and plugin makers live good on that assumption too, making people upgrade daw/plugin.
So very little incentive to put a lot of work into keeping backward compatibility.
Maybe not lazy - just good business dropping support - as long as we choose to play along.
Windows 10.x is out
- I'm on it
- why?
Maybe we should have our heads examined....
- KVRAF
- 2990 posts since 13 Apr, 2008 from Charleston, SC
This is not a revolutionary release, but I doubt we will see that with any software DAW. This is a solid release that addresses many issues and improves on a direction that JUST started last year with Pro 8. They will build and improve on it. To do so means keeping up with current technology, which includes support for current and future OS's. Supporting older OS's can create a weakness in the product and make the need for crutches. Obviously NONE of us want that.
Backward's compatibility has to have a line drawn somewhere or else NOTHING moves forward. We can't have it both ways. It is just impossible.
Remember too, their code is dependent on OS coding which in of itself is buggy (or else we would not see fixes throughout the year). Steinberg worked closely with Microsoft to fix issues that were flawed on MS's end. That is going the distance and is worth my $50 in of itself.
There is much to love about this update. And there is more, always more, to hope for.
If you get it, enjoy it. If you choose not to, enjoy what you have. But I find this a big step forward. I can hardly wait to see what they have in store for us down the road as well.
Backward's compatibility has to have a line drawn somewhere or else NOTHING moves forward. We can't have it both ways. It is just impossible.
Remember too, their code is dependent on OS coding which in of itself is buggy (or else we would not see fixes throughout the year). Steinberg worked closely with Microsoft to fix issues that were flawed on MS's end. That is going the distance and is worth my $50 in of itself.
There is much to love about this update. And there is more, always more, to hope for.
If you get it, enjoy it. If you choose not to, enjoy what you have. But I find this a big step forward. I can hardly wait to see what they have in store for us down the road as well.
-
el-bo (formerly ebow) el-bo (formerly ebow) https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=208007
- KVRAF
- 17994 posts since 24 May, 2009 from A galaxy, far far away
i also understand the rationale, and that it takes time to support each iteration of OS. i would draw the line differently, of course. and yes, "lazy" still stands. i don't have any image of them sitting around playing angry birds, but i do believe they are cutting off support way too early, especially when you consider that these OS upgrades are evolutionary not revolutionary. as such, i think these cut-off points are arbitrary, and way too soon (it's not like i'm arguing for them to support windows xp)noiseboyuk wrote:I get their rationale. Each OS that is supported adds time to every single feature and bug fix. And this really isn't a new problem, not just from DAW manufacturers, but developers in general. People draw the lines differently of course
-
- KVRist
- 335 posts since 20 Jul, 2010
Is there a chart/writeup anywhere of all the new features that have been introduced since version 5 (the one I'm still using
)?
Also, what's the cheapest way to get from Cubase 5 (pro/full/whatever) to 8.5?
Also, what's the cheapest way to get from Cubase 5 (pro/full/whatever) to 8.5?
-
- KVRian
- 555 posts since 10 Nov, 2005 from Scotland
There is one somewhere but it's written in Latinskitchy wrote:Is there a chart/writeup anywhere of all the new features that have been introduced since version 5?
-
- KVRAF
- 5144 posts since 3 Oct, 2013
http://www.macprovideo.com/tutorials/cubase-applicationskitchy wrote:Is there a chart/writeup anywhere of all the new features that have been introduced since version 5 (the one I'm still using)?
Also, what's the cheapest way to get from Cubase 5 (pro/full/whatever) to 8.5?
"Where we're workarounding, we don't NEED features." - powermat
-
- KVRian
- 906 posts since 25 Jan, 2014
I have a small question for those who upgraded ...
About the new feature where we can import track from other project ...for exemple if I have one MIDI track that sends MIDI to 2 instruments track and I import those 3 tracks ....I would like to know if the MIDI routing is still there ...thank you
About the new feature where we can import track from other project ...for exemple if I have one MIDI track that sends MIDI to 2 instruments track and I import those 3 tracks ....I would like to know if the MIDI routing is still there ...thank you
-
- KVRian
- 1125 posts since 29 Sep, 2013
I think my problem was caused by not getting a clean close of Cubase before crashing it. I re-tweezed my plugins and closed the program, and it managed to save the preferences.rasmusklump wrote:I am on win 64 too and every setting incl. the plugin manager was remembered correctly.rustman wrote:Windows 64 bit.TheoM wrote:Mac or windows?rustman wrote:Looks like 8.5 doesn't remember your plugin manager settings. I spent a long time tweaking the folder structure last night and it's gone today. Still crashes my system when scanning plugins too. I don't use any 32 bit plugins anymore (no wrappers) just to try and reduce this hassle.
i think the best thing right now is to wait a few months for final release.
perhaps if i upgrade to 8.5 when 9 has been announced, i can pay the $50 USD and get into 9 for free.. nothing wrong with using 8.03 for the next few months, nothing at all.
I did myself a favor and learned the P and L keyboard shortcuts tonight. I should learn a few more...I'm getting mouse elbow.
In rotation here: Helios- Eingya
-
- KVRAF
- Topic Starter
- 7097 posts since 22 Jan, 2005 from Sweden
I tested a bit, since I was curious too.Jolaff wrote:I have a small question for those who upgraded ...
About the new feature where we can import track from other project ...for exemple if I have one MIDI track that sends MIDI to 2 instruments track and I import those 3 tracks ....I would like to know if the MIDI routing is still there ...thank you
Import from project seems simple, and not so extensive as track archive options.
I did one midi track, and two instrument tracks - routed midi track as output to one, and midi send to another.
Works through track archives, but not picking from project directly(or is buggy).
Midi send became "not connected" from midi track.
Track archives are much more extensive, and also supports busses and routing etc.
So I intend to use archives as track templates for various purposes.
- KVRist
- 198 posts since 30 Sep, 2015 from Germany
Just found this:
http://www.steinberg.net/en/newsandeven ... -3469.html
Makes me quite happy that I went through the process changing everything (OS, Cubase, all plugins) to 64 bit, this way I'll be prepared.
Sad story though, since many people are still using 32 bit plugins - and I made quite some bad experience with not all, but at least a LOT of 32 bit plugins that didn't work for me and crashed Cubase big time. The VSTBridge never worked well for me, that's why I did it all in the first place, also I had to give up on some valuable plugins ...
http://www.steinberg.net/en/newsandeven ... -3469.html
Makes me quite happy that I went through the process changing everything (OS, Cubase, all plugins) to 64 bit, this way I'll be prepared.
Sad story though, since many people are still using 32 bit plugins - and I made quite some bad experience with not all, but at least a LOT of 32 bit plugins that didn't work for me and crashed Cubase big time. The VSTBridge never worked well for me, that's why I did it all in the first place, also I had to give up on some valuable plugins ...
- KVRAF
- 2990 posts since 13 Apr, 2008 from Charleston, SC
Well that is going to cause a lot of heads to spin. I have been using 64 bit products since they were available. I still have some 32 bit plugins that work well with the bridge, but are not really needed. This is that focus I was talking about with Cubase. It should open the door for a more complete stable product with each incarnation.
There are some who are still on Atari ST's that won't like it though,
.
There are some who are still on Atari ST's that won't like it though,