Xavier,
As always, I supremely appreciate your thoroughness in detail. As I am sure I
have told you in the past, I have an XP box which is on it's last legs. Given
your thorough explanation of the specific state of SONAR 8.5, CT & Win 10, I
will reevaluate and make a decision with respect to how exactly to proceed.
Sent from my iPhone
On Jun 12, 2016, at 12:01 AM, DJX <megamansuperior@xxxxxxxxxxx> wrote:PLEASE READ THIS FOOTER AT LEAST ONCE!
Hi, while the person was able to use the scripts after altering windows 10, I
think the conclusion was that not all things like HSC and color based stuff
worked or would work properly. Furthermore, my point in that whole discussion
was not so much about the scripts working or not working, but that windows
10, especially given all the new updates Microsoft is constantly bringing out
for it, would not run properly with the classic theme from 7, since
(according to Microsoft themselves), the entire classic engine, which is
responsible for the classic theme and made those changes was removed. Even
those on online forums who "discovered the hack" and tried removing the
engine to revert to the classic style (which is what copying an unsupported
theme like windows 7 classic does) reported experiencing random crashes and
new metro apps not working at all and windows 10 being more unstable due to
the new theme engine being disabled. While that might be a compromise that
many are willing to live with and put up with because they have no other
choice, it is by far not a viable or long term solution for a production
environment or a place where time sensitive and projects with deadlines are
done. If you are working on your own stuff, and you are your own client or
just a hobbyist who doesn't mind dealing with crashes or other inherent
issues, this might work well for you, but we can't say that it's a fix or a
working solution, because that would imply that it's been tested and found to
work fine and be a solid platform for anyone to work from, which might not be
the case, especially in a studio for hire or where third party contracts are
involved.
I adamantly share this point of view, because it is from the side of those of
us who work with products and have to release working products to clients and
make sure that all things are working as expected. Imagine if I built a DAW
for someone and didn't test it to be sure that all components were working
fine to spec, or if I told them that the computer will start but might
experience random reboots for no reason whatsoever. They'd be upset. Or what
if I wrote a program for someone and the program was full of bugs when I
released it? Or imagine if Steve or Phil didn't take the time out to test all
their HSC sets as thoroughly as they do and build in all the checks they do
to insure that the sets didn't just randomly click places on screen when
certain windows are not open that should be, or when certain windows are open
that should not be. Nobody would buy or use the stuff because it would be
what we call "buggy" or unreliable!
So all that to say, I'm just not comfortable with suggesting something that
might clearly have other side effects as a viable solution to 1 problem, when
it might create others. Yes it might work for some people, or because one
person only uses certain features and they work fine they consider it
working, but remember we must take into account many different
configurations, setups, and the fact that many people use their systems
differently. While some people don't mind not having access to metro apps,
others might have to make sure that their system would still work with those
alongside the scripts. Some people have to share systems and configurations,
others don't, and yet others just can't take the risk of having windows crash
and risk data lost or corruption in the middle of a project that is not even
their own. Some other people rely heavily on HSC and third party sets or CT
functions that require accurate color detection, so this might not work as
well for them. The only reason I make a big deal about it, is because this is
a public list, where the archives are searchable and even show up on google!
So if somebody a year from now is trying to decide on buying a win 10 machine
and they search this list's archives and find messages where we recommend
this method and they go out and spend their hard earned money on a system
built on windows 10, and they set it all up only to find that it doesn't work
reliably or not everything works 100%, they would be pretty disappointed IMO.
So If we are going to say something like this is a solution, You could say it
somewhat works, and list what works and what doesn't, and list any
workarounds that are known, but mainly list the disclaimers of what will not
work or any side effects the hack will have. Basically, you want to give out
all the information so that the user can make the informed decision on
whether they will try to use the system like that and take the risks and deal
with the consequences for themselves. I just don't think we should say "it
work, all is well" and set up the future reader for those kinds of issues.
Furthermore, let's remember that this is a list to discuss DancingDots
products, and where new users of their products might come to get info and
help, and if they come across info like that, they might completely ignore
the fact that it's not supported by DD, but because they found it on this
list, they would think that's enough, and poor Bill and his team would get
endless support calls and Email complaints about the whole thing not working
or not being accurate. Yes I know, that's the user's falt for not reading or
paying attention to all the stuff as written, but it's the world we live in
lol.
Anyway, don't mean to go on a rant or lecture here, just want to make sure
that all the info is clear ;)
Regards, DJX
-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Efren Chavez
Sent: Saturday, June 11, 2016 3:09 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: Need advice on Mac Pro vs Macbook Pro
Hey Kevin,
The discussion about CT working with windows10 occurred a while back and if
you search you should be able to find that thread.
A guy by the name of Autery Weekes even posted an audio demonstration about
it working with windows10. He copied over the classic theme from
windows7 over to windows10 and he said it worked for him.
Note, it is not recommended nor endorsed by DancingDots and some of the guys
like DJX and Steve who know more about this kind of stuff claime it should
not work if you copy over the classic theme, but like I said they proved
otherwise. It may cause other computer problems, but can't say for sure since
I have not done that myself.
If I find that thread, I'll reply to it so that you can read the thread in
its entirety.
On 6/11/16, Kevin Gibbs <kevjazz@xxxxxx> wrote:
Sean, can you summarize what is and is not possible?
Sent from my iPhone
On Jun 11, 2016, at 7:35 AM, Sean A. Cummins <seanacummins@xxxxxxxxx>PLEASE READ THIS FOOTER AT LEAST ONCE!
wrote:
Kevin,
To my knowledge, no one nor have I had any success getting full
functionality out of Kik talking Scripps in windows 10. Issue is the
original windows seven classic seems that cannot be fully installed
in windows 10.
Take care,
Sean
Sent from my iPhone
So forgive my brevity!
On Jun 11, 2016, at 4:24 AM, Kevin Gibbs <kevjazz@xxxxxx> wrote:
Are you sure CT is a definite no go under Win 10, regardless of JFW
version? Cameron Strife uses SONAR 8.5 with JSONAR under Bootcamp
and Win
10 with JFW 17. I know CT doesn't run under anything higher than JFW 16.
But if JSONAR can work, why not CT? With Bootcamp, Windows 10 & JFW 16?
Sent from my iPhone
On Jun 11, 2016, at 5:28 AM, Sean A. CumminsPLEASE READ THIS FOOTER AT LEAST ONCE!
<seanacummins@xxxxxxxxx>
wrote:
Kevin,
If you are expecting to use the cake talking Scripps with 8.5 on a
mac pro and windows 10, it will not work…
The rule of the jungle with chords, if you are doing soft synths and
native plug-ins, more cores is always better versus speed.
And of course as much ram as you can afford to stuff in the machine
is a great advantage.
Take care,
Sean
Sent from my iPhone
So forgive my brevity!
On Jun 11, 2016, at 2:06 AM, Kevin Gibbs <kevjazz@xxxxxx> wrote:
PLEASE READ THIS FOOTER AT LEAST ONCE!
Guys,
I need advice on whether I can run my studio using a Macbook Pro,
or whether I need a Mac Pro, i gather that it is possible to run
SONAR 8.5 under Bootcamp in Windows 10. Having said that I'm not
interested in the arguments about purpose/built machines.
Tim or Phil,
You guys are using Macbook Pros. Where do you store sample
libraries, or projects? What Audio interface are you using? USB,
Thunderbolt, Firewire? Wha MIDI interface?
When considering a configuration, should I focus on clock speed, or
number of cores?
Thanks for any advice,
Kevin
_______________________________________________
Midimag-ex mailing list
Midimag-ex@xxxxxxxxxxxxxxxxxxxxxx
http://mailman.midimag-xt.org/cgi-bin/mailman/listinfo/midimag-ex
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
If this link doesn't work then send a message to:
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
unsubscribe
For other list commands such as vacation mode, click on the
immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=faq or send a message, to
ddots-l-request@xxxxxxxxxxxxx and in the Subject line type faq
PLEASE READ THIS FOOTER AT LEAST ONCE!
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
If this link doesn't work then send a message to:
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
unsubscribe
For other list commands such as vacation mode, click on the
immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=faq or send a message, to
ddots-l-request@xxxxxxxxxxxxx and in the Subject line type faq
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
If this link doesn't work then send a message to:
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
unsubscribe
For other list commands such as vacation mode, click on the
immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=faq or send a message, to
ddots-l-request@xxxxxxxxxxxxx and in the Subject line type faq
PLEASE READ THIS FOOTER AT LEAST ONCE!
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
If this link doesn't work then send a message to:
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
unsubscribe
For other list commands such as vacation mode, click on the
immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=faq or send a message, to
ddots-l-request@xxxxxxxxxxxxx and in the Subject line type faq
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subjectunsubscribe
If this link doesn't work then send a message to:
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
unsubscribe
For other list commands such as vacation mode, click on the
immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subjectúq or send a message, to
ddots-l-request@xxxxxxxxxxxxx and in the Subject line type faq
--
Efren Chavez
PLEASE READ THIS FOOTER AT LEAST ONCE!
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=subscribe
If this link doesn't work then send a message to:
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
unsubscribe
For other list commands such as vacation mode, click on the immediately
following link:
ddots-l-request@xxxxxxxxxxxxx?subject q or send a message, to
ddots-l-request@xxxxxxxxxxxxx and in the Subject line type faq
PLEASE READ THIS FOOTER AT LEAST ONCE!
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
If this link doesn't work then send a message to:
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
unsubscribe
For other list commands such as vacation mode,
click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=faq or
send a message, to
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
faq
