Bub


You can unfreeze a track to work on it so again I call BS.

" ... it's nobody's preference." - Again, BS.

You said, "I've got projects that I can't play in 32 bit because the sample sets I'm using are too large. But I can play them in 64 bit."


Until you prove to me you have a situation where your only option is to use 64 bit .... then I stand by what I said.


So far you given me excuses as to why you want to work in a 64 bit environment, but you haven't shown anything based in fact as to why you are forced to work in a 64 bit environment.


I still call bull***t.

You are a very strange, angry and stupid man. I don't think I'm going to bother pursuing this any further.

John T

You are a very strange, angry and stupid man. I don't think I'm going to bother pursuing this any further.

I should hope not. There's not really anywhere else to go once you start acting like a 6 year old.

"I don't think I'm going to bother pursuing this any further."


BTW - Reported. This kind of behavior really needs to stop.

What kind of behaviour? I think there's a worthwhile discussion to be had about the the detail of real uses of 64 bit; it's certainly a topic others are interested in. But it's kind of hard to have with someone going "I CALL BS! I CALL BS!" all the time.

How you can possibly think you've been a model of polite behaviour in this thread, and I've somehow been out of order after putting up with your nonsense for really much longer than anything you've posted has deserved, I can't begin to imagine. You've been acting like a complete jack-ass.

All I asked for were some facts to back up your claim that you can not use 32 bit for some projects and so far you haven't been able to produce any. You've skirted in every direction and made excuses why you prefer to work in x64 but haven't been able to backup your claim.

You got called out and took it to heart and lost your cool. That's on you partner ... not me.

Bub you are coming at this backwards. It would normally be one is "forced" to work in a 32 bit environment because of legacy gear.  Not unlike it was back in the 16 bit era. If you need to know the real benefits of a 64 bit environment do a little research on it.

Overall performance is better in a 64 bit OS. More importantly though is the fact that most high end audio and video apps have migrated over to 64 bits not because of marketing but for the advantages 64 bits offers.

Anyone that has a system that can handle 64 bits and has the options of dual booting to a 32 bit OS and a 64 bit OS on the same machine will notice a performance gain with the 64 bit OS.

This is not pie in the sky but real world experiences from nearly all that have taken the plunge. 

Read the threads I have posted on this in the past and then make your view known here. Better yet try it yourself.

If you don't have the same experience that most have I will be surprised. But you must have the right gear first. Yes it will mean some things will need to be left behind but that in the end will allow suitable new things to will come along and more than make up the loss.


Where is Freddy  when you need him?

To pour fuel on the fire, I've been using x64 all round since I installed Windows 7, I think that's about 2 years now but I'll stand corrected if that time frame is wrong.

I don't even have an x32 version of Sonar installed on my main DAW, although I do use it on my x32 OS'd laptop. I'm also wasting my time because I currently only have 4GB RAM but do plan to add more.

I've had very few problems, if any, other than the well documented bugs (most of which I had work rounds for) and so far crashes are few and far between. Only one sticks in my mind and that was bought on when experimenting in a thread cutting & pasting buss envelopes, with ba_midi IIRC.

My point is that whatever problems may exist for some with X1 they aren't simply x64 related. Unless having x32 installed as well causes the issues because it ain't happening here on a x64 only system which co-incidentally is below Cakewalk's minimum recommended spec.

John

Bub you are coming at this backwards. It would normally be one is "forced" to work in a 32 bit environment because of legacy gear.  Not unlike it was back in the 16 bit era. If you need to know the real benefits of a 64 bit environment do a little research on it.

I have. There's very little improvement when running Sonar when going from 32 to 64 other than being able to access more ram.

Overall performance is better in a 64 bit OS. More importantly though is the fact that most high end audio and video apps have migrated over to 64 bits not because of marketing but for the advantages 64 bits offers.

Everyone except one of the largest ones ... Apple Quicktime.

Anyone that has a system that can handle 64 bits and has the options of dual booting to a 32 bit OS and a 64 bit OS on the same machine will notice a performance gain with the 64 bit OS.

Are you talking about system speed or Sonar? I've been running 64 bit Sonar since Windows 7 came out on a dual boot XP/Win7 setup. There was no improvement whatsoever that was noticeable in Sonar. Windows 7 boots up faster than XP, the GUI is smoother, but that's the only improvement I saw.

This is not pie in the sky but real world experiences from nearly all that have taken the plunge.

Again, are you talking about the OS or Sonar? Sonar, I see no improvement except for being able to access more ram, which technically is not a show stopper if you don't have it because you can freeze to free up CPU/RAM.

Read the threads I have posted on this in the past and then make your view known here. Better yet try it yourself.

I have tried it. I've been running 64bit since Windows 7 (and M-audio released 64 bit drivers.). It has only caused problems because of Bitbridge. That's why I recently switched back to 32 bit.

If you don't have the same experience that most have I will be surprised. But you must have the right gear first. Yes it will mean some things will need to be left behind but that in the end will allow suitable new things to will come along and more than make up the loss.

Where is Freddy  when you need him?

On my system, an i5 Quad Core 750 Win7 x64, 4GB RAM (I had 8GB but saw no improvement and ended up swapping it out for a lesser quantity of better quality RAM) running 8.5 and X1 both in 64 and 32 bit ... I see no difference whatsoever for the projects I do when switching between 32 and 64 bit. I only see improvements because I don't have to deal with Bitbridge crashing.

The discussion between John T and myself is ... he said he has projects that will not run at all in 32. All I'm asking is, prove it which he has been unable to do. You always have the option to freeze to take the load of your CPU/RAM if things bog down.

FastBikerBoy

To pour fuel on the fire ...

To clarify, all I'm saying is I haven't seen anything to prove that you are forced to use 64 bit in large projects like John T has claimed.

All I asked for was some facts and instead I get called stupid, angry, strange.

Thank God he didn't call me untalented.

Bub

aleef

i would have thought by now we would be through with bitbridge/jbridge.. and freezing tracks.

Can't tell by your statement if you're pro or con on bitbridge and freezing. There's two ways to read it.


All I can say is bitbridge has been buggy ever since it was introduced so I just completely avoid it which means ... no more x64. It's just not worth the aggravation on top of everything else.

 
ohh noo!!  im against bitbridge and that whole wrap rendering thing..most of the time it works, but on any given day it doesnt. and having to pay for jbridge which may or may not work any better doesnt sit well with me.  i dont know why, but i was under the impression that bitbridge was behind us..it hasnt been talked about for awhile..

Bub, ol pal, while there is much truth to what your saying regarding "performance" there is just no question whatsoever that 64bit gives you more "headroom" when building projects with RAM hungry VSTs.  And when you say (I'm paraphrasing) "well, you can always just freeze and unfreeze" you are 100% correct...but who the heck wants to do that??  I don't.  If you've ever watched a fully loaded multitrack setup of SD2 or BFD2 "freeze" it's like watching paint dry.  People complain on the forum all the time and occasionally in very bellicose fashion about having to make ONE extra click with their mouse to do something now.  Yet you're advocating (I think) that freezing and unfreezing all the dang time is just a triviality.  It's not.  At least to me.  I'd never go back to 32 bit.  I've been freed by the constraints of 32 bit.  Free at last, free at last thank gawd almighty I'm free at last!  Of course, YMMV:-)