I have a couple burgers lined up right now. I also have some sliced ham. I may put the ham on the burgers. Then they will literally be HAM burgers. That's right... I just blew your mind.

Never eat hamburger!
This is a humanistic and moralistic question !
No compromise..........

double post

Be QUIEEET"!!! I'm stuck at work and really hungry!!!!!!!!




(Perhaps I should just finish what I'm doing and go to the nearest place that sells burgers ASAP - it's a blood sugar thing now!)

Carry on and stay healthy!!




Now what was this thread about? I'll have a coffee as well.

Keeping with the hamburger theme that seems to have developed, there is something about Pro Tools that reminds me of my experience working at MacDonalds when I was a teenager.  It is standardization and I've mentioned it in the past.

At MacDonalds we were trained on the grill to have a certain procedure to assemble a hamburger that for the most part only had a few components.  Six standard ingredients may be used but there was an order to the process even though order didn't make a hill of beans difference in the final results.   As an employee, I could be dropped into any restaurant in any state and I would immediately know the procedure and could work as a part of a three man grill crew and never miss a beat.

From my limited experience with the demo, Pro Tools reminded me of that kind of standardization.  After you got past the "goesintos" and "goesouttas" (I/O), I didn't see where you could customize much other that the color of your track info.  SONAR X1 has brought quite a bit more standardization to my DAW of choice and I have accepted it kicking and screaming as many old timers have.  You can't customize as much as you could with 8.5 and someone coming into my SONAR X1 box who has a knowledge of the program would find most everything exactly where they would expect it.  On the other hand, Reaper is so customizeable, that my setup would be totally foreign to a lot of users because, I've removed a lot of menu choices for features I don't use.  And I use a custom theme that looks nothing like the default theme.

Whether standardization is good or bad, it's up for the studio owner to decide.

Well if you insist on talking about competing products, I read on Gearslutz that apparantly a lot of Pro Fools users are switching over to Weeper.

I'll stick with Sonar X1,  thank you !!

djwayne


Well if you insist on talking about competing products, I read on Gearslutz that apparantly a lot of Pro Fools users are switching over to Weeper.

I'll stick with Sonar X1,  thank you !!

Yeah, I'm reading the same threads as well.  At least the activity has a certain amount of entertainment value.  Sort of like Jersey Shore for DAW geeks.  

Mod Bod


Keeping with the hamburger theme that seems to have developed, there is something about Pro Tools that reminds me of my experience working at MacDonalds when I was a teenager.  It is standardization and I've mentioned it in the past.

At MacDonalds we were trained on the grill to have a certain procedure to assemble a hamburger that for the most part only had a few components.  Six standard ingredients may be used but there was an order to the process even though order didn't make a hill of beans difference in the final results.   As an employee, I could be dropped into any restaurant in any state and I would immediately know the procedure and could work as a part of a three man grill crew and never miss a beat.

From my limited experience with the demo, Pro Tools reminded me of that kind of standardization.  After you got past the "goesintos" and "goesouttas" (I/O), I didn't see where you could customize much other that the color of your track info.  SONAR X1 has brought quite a bit more standardization to my DAW of choice and I have accepted it kicking and screaming as many old timers have.  You can't customize as much as you could with 8.5 and someone coming into my SONAR X1 box who has a knowledge of the program would find most everything exactly where they would expect it.  On the other hand, Reaper is so customizeable, that my setup would be totally foreign to a lot of users because, I've removed a lot of menu choices for features I don't use.  And I use a custom theme that looks nothing like the default theme.

Whether standardization is good or bad, it's up for the studio owner to decide.

Yes sure Pro Tools is like MC Donalds hamburger alright.  
Non eatable grey hamburger that arn't grilled at all. The cheese that are on them going to be found intact in any grave 1000 years after the body are gone.  The cheese and the meat are made and produced and taken directly from the cows inside Tjernobyl reaktor 4...  
 
 
 
 

U know, I think this thread have been...   I think coffee house next

that third banana needs some alone time methinks......

 
He's an exhibitionist...
 

(...)

rst, it never crashed in all the time I used it over the whole month. It never even crackled or buzzed or did anything other than what it was meant to do. I recorded track counts of about 30 tracks full of plugins, on my Q6600 quad pentium system. This is about a normal "song" for most musicians. It didn't falter once. Sadly I can't say the same for Sonar X1d, but in saying that, most of the problems which caused crashes were associated with 3rd party plugins. I think this is generally where most problems occur. In defense of Sonar, it is made to be as compatible with a wide range of 3rd party plugins, and you are always going to get something which doesn't work properly. PT has the advantage that the plugins tend to be more tightly controlled because they are RTAS (at the moment, for the native version) which means they only have to work with PT. So I guess this makes PT less likely to crash because of plugin problems. Basically: both DAWS were totally stable without plugins, but once plugins were added to tracks Sonar misbehaved sometimes whereas PT10 remained rock stable.

When you're talking about rock-solid stability with plugins, one major factor that you're not taking into account:
ProTools 10 is *still* a 32Bit application.  It's limited to addressing 4GB of RAM (major limitation).
Sonar x64 is a 64Bit application.  Thus, any 32Bit plugins have to be bridged to operate.
Some 32Bit plugins cope well with being bridged... others don't cope well at all.
To make the comparison equal, you need to compare the 32Bit version of Sonar vs ProTools 10.

Jim Roseberry


To make the comparison equal, you need to compare the 32Bit version of Sonar vs ProTools 10.

so the best way to compare anything is to ignore the differences?... that makes no sense whatsoever...
 
The world has moved to 64bit os and Avid never noticed... so going back in time is not an option.

Yeah, there's been quite a few stories like that - and they are very true. Latest now was that they've sold M-Audio. I guess that kills the Pro Tools M-Powered series. But I worry what will happen with the good products Avid owns, like Sibelius. Apparently they're closing down the original Sibelius development team in the UK or something.

true. They'll keep the development office in the States but there will be some lay off's in the UK office as they're only moving key personell from developement across the pond. But the UK office is definitely closing down as in; they're not going to have employees in the UK to continue developing Sibelius. So it will be a smaller Sibelius developement team and probably some grumpy family members who have to move with their spouses to another country. Sibelius remains but there are some serious concerns in the composer communities over what the future of Sibelius is.


It's scary what happens at Avid. It's like they diminish their product developement while loosing money. Imagine if Avid suddenly seized to excist! They own pretty much "everything" and if they're going bankrupt without being able to sell off their products to be developed under different companies, imagine the uproar in the industry when there's no more Pro Tools, Media Composer or Sibelius.