|
The 64-bit $h!tlist (pg. 2)
|
View this Thread in Original format
| Normie |
Funny you should mention 64 bit...
Arturia just released the Beta for Jupiter 8V 64. So far so good. Seems to be more efficient in resource management. No monster obvious changes in the beta other than a couple layout tweaks for the better, but they are minor.
No issues "so far", but it looks to be a good thing.
Now the world can burn for all I care. I haZ by 64 bit Jupe and it works ;) Email said they are hoping for a March release of the official version. |
|
|
| Storyteller |
| *Edited away. Apparently I need glasses and perhaps learn how to read again in 1st grade* |
|
|
| Normie |
Part of it is that some figure the coding is $$$ and they are calculating that those costs are 'not yet' worth it since people continue to buy the 32 bit products and suffer the wrapper issues.
Also toss into the mix that XP64/Vista 64 were essentially fringe products that had no 'real' IE widespread support. Now that Win7 64 is growing in installed userbase, it's a more 'profitable' decision to support 64 bit end to end rather than just fudge it.
Then there's the popular "Do we charge for the upgrade and piss off our users or eat the cost?" question.
And of course, no one wants to be first into the pool. They want someone else to test the water first, let the issues crop up and benefit from their experience without the 'brand damage' that doing so incurs.
Not the only reasons I'm sure, but the above factors into it.
| quote: | Originally posted by Storyteller
It is weird though that the switch to 64-bit was already obvious like 5 years ago and still the majority of plugin manufacturers and some major sequencers don't support it. Is it laziness or too expensive for them put time in? |
|
|
|
| Dashka |
To be honest guys, best investment I made once making the switch to 64 bit was picking up jBridge. Pretty inexpensive and means you can properly utilise 32 bit plugs in 64 bits sequencer. (This is a godsend, particularly with vsts like U-He ACE too which are typically very heavy on CPU anyway.)
Sequencers not updating to 64 bit though is just plain lazy. |
|
|
| Looney4Clooney |
| quote: | Originally posted by Normie
Part of it is that some figure the coding is $$$ and they are calculating that those costs are 'not yet' worth it since people continue to buy the 32 bit products and suffer the wrapper issues.
Also toss into the mix that XP64/Vista 64 were essentially fringe products that had no 'real' IE widespread support. Now that Win7 64 is growing in installed userbase, it's a more 'profitable' decision to support 64 bit end to end rather than just fudge it.
Then there's the popular "Do we charge for the upgrade and piss off our users or eat the cost?" question.
And of course, no one wants to be first into the pool. They want someone else to test the water first, let the issues crop up and benefit from their experience without the 'brand damage' that doing so incurs.
Not the only reasons I'm sure, but the above factors into it. |
i think you over emphasize the difficulty. One man operations with products that meet or exceed the big boys manage to do it. The coding is not hard considering other things in other domains. A plugin is pretty ing simple. It is mismanagement , neglect and some stupid game of brinkmanship with other developers that hurt the end user. Every 32 bit only plugin should be cracked and abused so that they get their together and have a reason to update. |
|
|
| cryophonik |
| I have no idea what it takes to bring a plugin to 64-bit, but a few weeks ago, Audio Damage announced that they were going to hunker down and knock out every one of their plugins and they did it over the course of a few weeks. If a small company (2-man operation, I believe) can do it in that short a time, why does it take so long for larger developers? I'm guessing that laziness and greediness plays a role - generally speaking, it's work that is done for free from their perspective, so what's the hurry, right? I can empathize with that to an extent, but I'll give my business to developers who have a record of providing timely updates. |
|
|
| Nightshift |
| quote: | Originally posted by Looney4Clooney
you know what is pathetic is mac and the future of logic. Almost 2 years it seems and no update. And now a new OS in the summer so probably nothing for another year. What a ty company. I really don't understand why anyone would buy a mac for audio these days. |
+5 billion. lol.
p.s. im staying 32 bit till 64 bit is SOFTWARE standard. not just hardware standard. |
|
|
| Raphie |
Now D16 was transitioned I went to Cubase x64
the only stuff i'm running with Jbridge now is my API collection
and that will be sorted this March, I just renewed WUP so i can move out Jbridge when it lands. All my other plugs are already x64 |
|
|
| Ryan0751 |
| quote: | Originally posted by cryophonik
I have no idea what it takes to bring a plugin to 64-bit, but a few weeks ago, Audio Damage announced that they were going to hunker down and knock out every one of their plugins and they did it over the course of a few weeks. If a small company (2-man operation, I believe) can do it in that short a time, why does it take so long for larger developers? I'm guessing that laziness and greediness plays a role - generally speaking, it's work that is done for free from their perspective, so what's the hurry, right? I can empathize with that to an extent, but I'll give my business to developers who have a record of providing timely updates. |
It depends a lot on how the software was written.
It can be quite tedious in some cases to re-write code to be 64-bit friendly. Not to mention, in some cases the 64-bit versions will take a huge performance hit (usually when they are written poorly). |
|
|
| cryophonik |
| Since some of you guys know a bit about this and, while we're on the topic, why is it that the 64-bit versions of plugins usually have a smaller file size than the 32-bit version? |
|
|
| cryophonik |
| quote: | Originally posted by Storyteller
Apart from that I don't think it's a problem with most of the plugins mentioned being 32-bit. As long as the DAW software packages have a 32bit plugin wrapper everything would work as expected anyway.
As far as I know the only plugins that truely benefit from 64bit internals are the ones that need to adress RAM memory above the 3.2GB mark. So basically just romplers need to be 64bit.
|
Well, that's not the only need. One of the problems I'm having is that the sidechaining capability is disabled in some DAWs (e.g., Studio One) when you are using a bridge. For example, I'm trying to process some vocals that I recorded last week with Vocal Rider, but I have to revert to the 32-bit version of my DAW to get VR to work with sidechaining. PITA. |
|
|
| Zombie0729 |
most people were coding 32bit applications prep'ing for a 64 enhancement, especially with memory & data allocation. You can read more on it here:
http://msdn.microsoft.com/en-us/library/ms973190.aspx
It's intensive but not game altering, I think for someone like Waves who has 200+ plugins, worked with OTHER people on their devices, etc, it's more overwhelming then say Sylenth, who's 1 guy :) |
|
|
|
|
