kennywtelejazz
I'm wondering aloud over here ...What brick walls are folks here hitting while using P 5 ?
 

I would like to be able to load Addictive Drums and Scarbee Rick Bass and one of the Scarbee Electric Pianos into a project.  I get memory issues when I do that in P5.

Magic Russ

kennywtelejazz
I'm wondering aloud over here ...What brick walls are folks here hitting while using P 5 ?
 

I would like to be able to load Addictive Drums and Scarbee Rick Bass and one of the Scarbee Electric Pianos into a project.  I get memory issues when I do that in P5.

Project 5 is a 32-bit application, subject to user-mode virtual address space for each 32-bit process of 2GB.
 
https://social.technet.microsoft.com/Forums/en-US/e029e271-2c53-4e23-8da4-ac48e2092a76/memory-limits-of-32bit-application-running-on-64bit-os-windows-2008-server-64bit?forum=winservergen
 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa366778(v=vs.85).aspx#memory_limits

abacab

Magic Russ

kennywtelejazz
I'm wondering aloud over here ...What brick walls are folks here hitting while using P 5 ?
 

I would like to be able to load Addictive Drums and Scarbee Rick Bass and one of the Scarbee Electric Pianos into a project.  I get memory issues when I do that in P5.

Project 5 is a 32-bit application, subject to user-mode virtual address space for each 32-bit process of 2GB.
 

Yes, and to make matters worse, jBridge was not helpful.  It is capable of allowing you to run 64-bit plugins in 32-bit applications, each with its own memory space, but I had run into enough issues and annoyances to rule it out as  a solution for me..
 
The original question was "what brick walls are you hitting?", and for me, the 2GB limitation is very much a brick wall.
 
 

abacab

BobF
 
I had X3 x32 installed for awhile too, and P5 was able to use those x32 synths.  ASIO was still a problem.
 
For reference, it was 8.1x64 with Platx64, X3(e)x32 and P5 ... along with other stuff.  Everything worked OK except for my interface (16x08).  IIRC, P5 only saw the first 2 of 16 inputs.
 

 
Ah, well my M-Audio Firewire 410 is actually only 2 in, 8 out as far as the 1/4" TS plugs go.  So unless I use S/PDIF, which I don't, no problemo -- maybe? 
 
Two ins works OK for me, because I mostly always use soft synths now anyway.
 

 
My thinking is that if I have zero x32 stuff, I'll never have to worry if a problem is related to x32/x64 bridging

I get that!

My problem with inputs isn't that I need more for concurrent recording.  I have different stuff connected to different inputs, with each input's gain set accordingly.  The INST ins are 9/19, with 9 set up for guitar and 10 for bass or A/E.
 
Two ins (XLR) for mics, another has the direct out for an amp, another is set up for a Red Box 5, a set of lines for a GT-001, etc.
 
Only seeing 1/2 in my case makes it more trouble to use than it's worth.
 
 

Magic Russ
 
The original question was "what brick walls are you hitting?", and for me, the 2GB limitation is very much a brick wall.
 

The real solution to that is for Cakewalk to provide us with a 64-bit version of Project5. 

BobF
 
My problem with inputs isn't that I need more for concurrent recording.  I have different stuff connected to different inputs, with each input's gain set accordingly.  The INST ins are 9/19, with 9 set up for guitar and 10 for bass or A/E.
 
Two ins (XLR) for mics, another has the direct out for an amp, another is set up for a Red Box 5, a set of lines for a GT-001, etc.
 
Only seeing 1/2 in my case makes it more trouble to use than it's worth.

So it sounds like the real brick walls are using external inputs and the 32-bit limitations.  Cakewalk, are you listening?

abacab

Magic Russ
 
The original question was "what brick walls are you hitting?", and for me, the 2GB limitation is very much a brick wall.
 

The real solution to that is for Cakewalk to provide us with a 64-bit version of Project5. 

I joke about a P5V3x64, but I don't really think we'll ever see it.
 
My purely speculative opinion is that Cake either lost the rights, the code or the expertise.  Maybe even all 3.

The speculation was there was one programmer and he left after P5 came out.  Its main point was playing soft synths, but SONAR could soon do that.  I think the real idea behind P5 was Dimension - cakewalks first real sample playback unit.  So P5 v1 was a synth player for the older synths and P5 v2 added Dimension with a nice library that became Dimension Pro and then Rapture. Then they tacked on audio recording and suddenly they had competing products and decided to stick with SONAR.  They stuck a lot of P5 into SONAR, but it has never been as simple and clean. But a lot of the clean look of P5 got transferred over to SONAR X.

using reason with sonar vs other daw's I use, wasn't implemented so great I felt personally, in previous version. It wasn't as transparent as it needed to be , like other things I use. maybe thats changed, dunno
 
 

AT
So P5 v1 was a synth player for the older synths and P5 v2 added Dimension with a nice library that became Dimension Pro and then Rapture. Then they tacked on audio recording and suddenly they had competing products and decided to stick with SONAR.  They stuck a lot of P5 into SONAR, but it has never been as simple and clean. But a lot of the clean look of P5 got transferred over to SONAR X.

V1 was pretty limited.  I think their original goal was to have something that could compete with Reason.  V2 seemed more like a new host together than an update.  It looked a lot cleaner, they added the matrix, Dimension Pro, a clip browser, etc.  Dimension was a big additional selling point, but I would have never gotten into P5 if it didn't make the improvements it did between versions 1 and 2.