Avid Pro Tools HD v10.3.0-VR

Pro Tools is by far the best and ive used every other daw there is, its really just a personal preference but i dont understand how u can like the othe daws that look shitty, editing is shitty and not as easy as pro tools. pro tools has everything there at a click of a button making workflow a lot smoother and faster for me. too bad i cant have pro tools cause i cant afford a mac or good enough pc, caused i would def buy the real pt if i had a pc or mac to run it. with that being said just using this for a few days even tho it keeps crashing really lets me see how much better it is than cubase which is my 2nd favorite. i dl samplitude 12, its ok. studio one meh, reaper is cool but eh, and cubase is 2nd to pt. thanks for the crack wish i could get rid of mf error tho. thanks

this is reaper in action. do we need more ?

13 tracks playing, 4 recording at the same time. cpu usage : 1%. disk load : 3%. mega stable.

screenshot

Yes, it's a good DAW....but she's very temperamental........! A little Princess, believe me!

random MF error, left up pro tools for near 5 hrs then it happened. ehhhhh.....we need a fix

pro tools hd v10.03 is not compatible with waves 9r6????

I Followed instructions but i get this error every time I close any waves plugin interface:
Access violation occured, unable to write location:0x00000140

what i should to do?

use waves v8 by AiR works perfect,

navid811,
thnx

MF error

EVERITHING WORKS PERFECT ONLY MF ERROR ANYBODY CAN HELP
THX

Every Time I start PT it scanns the Plugins and Freeze when it Comes to DAE.. sometimes on DAE sometimes on the files after DAE (for example "DAE 2674320") sometimes on another number... Sometimes PT opens up and tell me no enough memory... Any advise? WIN 7 Acer Aspire, 4gb Ram, i5 m480 2,67ghz
thx

Problemereignisname: APPCRASH
Anwendungsname: ProTools.exe
Anwendungsversion: 10.3.0.28
Anwendungszeitstempel: 504efe47
Fehlermodulname: CFnd.dll
Fehlermodulversion: 10.3.0.28
Fehlermodulzeitstempel: 504ef2f7
Ausnahmecode: 40000015
Ausnahmeoffset: 00036cfb
Betriebsystemversion: 6.1.7601.2.1.0.768.3
Gebietsschema-ID: 1031
Zusatzinformation 1: 5afc
Zusatzinformation 2: 5afc49c9cb43e2e9f5f044da2e9c2499
Zusatzinformation 3: c3e7
Zusatzinformation 4: c3e7387e9863a46dc92ba2e06a7cc402

wait for usable crack i guess

http://i49.tinypic.com/8vt6rd.jpg

Hi.....

dbelazy: APPCRASH uninstall cubase or nuendo first and reboot thn open protools ...i had same prob but got rid with this ....pls do it n tell me.

Hey Hindustani,
thx for your reply. Ok i will try it and report it to you! But it would be important to me, to run both sequencers.

dbelazy,

hi i have the same problem.
do this :
hold 'n' on keyboard when it's starting then change your soundcard to ASIO4ALL or other soundcard that you have (something other than Asio Directx Full Duplex).
it should help.
if not change other setting on that window !

HAVE Fun.

Yeah MLocomotive,
thank you very much!!! now its running! Now i can reinstall cubase ;)

Different digital audio workstation applications sounding better than one another :facepalm:
Those whom have mentioned 'x' sounding better than 'y' - You all were joking right? The only few I know definately sound different are Ardour with the Harrison Mixbus front-end as it has alot of non-linear processing going on, Same with Pro Tools so long as HEAT is active as again it is a non-linear algo to 'warm' up the "perfect" sound, Cranesong's Phoenix is great also for that purpose in tandem with heat, Add Slate Digital's VCC and VTM or Waves NLS and any DAW becomes non-linear and 'warmer' or whichever 3rd party plug-ins of choice with non-lineararities on tap you like. Otherwise it is all just the built-in/bundled processing and effects plug-ins with the DAW that your ears like as your regular arsenal of goto plug-ins are doing the exact same thing. Pan law could be another reason but if you are hearing a 'better' sound in one application against the other then I'd highly recommend you calibrate/optimize gain staging then run a null test *If things are still sounding different'

You have a difference, but this results out of the standard Pan law in the daw!

*edit* sometimes i should read the complete post :D sry overread the part with the pan law!

GivePeaksNoChance,

Look in the gearslutz forum there is an thread with a poll. This poll was made with professional engineers from the music industry. The result is 50% of the engineers voted for difference in the DAWs. So you think these guys have problems calibrating gainstaging?

mf error ...........what the hel this is?

guys have u solved this prob or not.....if yes, tell me the final way....pls and if not ...first we should talk abt mf error ....m i right or not ? evry trick has gon failiour ...

so pls talk about this error

suchenderxxx
Can you give a link to this "gearslitz" poll, please!

if 50% said there r differences,it means the other 50% said there aren t

Where is beta 8 patch?

its still not released man ............wait til cow comes at the home

mf error is a very pro-toolz 10 hd feature.
to get rid of it you have to buy the pro tools hd no mf version for 25 grand .

mf = mothafucka error

here is the link: http://www.gearslutz.com/board/music-computers/759871-poll-do-some-daws-have-sup
erior-sound-you-programmer-engineer.html

pro tools 10,

do you guys dont trust your ears or do the most of you have such bad studio monitors? i opened a thread a while ago in the audiosex forum, but a wana be guru Lordgaga trolled against me that i have no idea and all daw sound the same bla bla bla. i said this 1-2 years before but no one believed me. there is so much code so much things that can affect the sound of an daw. why no one does the test for his self like i did with the most daws? it is so easy to do and this shows that i am not the only one who had same results.

i did the test recently. this pro tools, sequoia, reaper, studio one pro 2, live8.
they all sounded the same. faders at 0, pans at 0. wav renders. all the same. the rest is hype and marketing ollox what suckerz like suckerderks eat happily.

popeye :hahaha

pro tools 10,


read this if you can understand it then maybe you will be enlighted. But as i see your intelectual selection of words i dont know if this will happen (This is from an programmer of MAGIX):

This was posted on the Samplitude forum some time ago. It's the only comment on this subject by anyone who actually writes this stuff that I've personally ever seen.
________________________________________________________________________________

______

I can try to give some comments here, bit I won't claim to end this debate once and for all time. This is my personal point of view, so don't take this for an official MAGIX statement:

-As programmer (and scientist) I tend to the deterministical point of view: just adding two numbers should give the same in all circumstances, and hence the basic mixing task should be the same for all 32 bit floating point DAW's - if you take the simple adding process as a common method for mixing: we know there may be other methods here.

-I also know that due to the number representation in the computer, there just is not only a limited precision but also a certain "random factor" in calculations with floating point numbers. This is basicallly caused by the representation of the compiled code in the system (initialisation of floating point registers with more than 32 bit processing, usage of registers versus usage of computer memory,...) and the execution of the code in the real system (e.g influence of other tasks, e.g. with multitasking). Both is partially depending on the used compilers, but of course also from the programmming code the application is written with. A recent example could be a problem with the master gain in the first v8 beta versions, where it changed the bit depth even when just initialized with exactly 0dB (= factor 1.0 in floating point).

-An obvious step after summing before going to the output is reducing the bit depth again to 24 or 16 bit. This consists of at least 3 steps: clipping, scaling and dithering. Every step can be implemented in various ways. *Clipping can be done straight forward or more sophisticated, both with possible hazards for the audio signal - but of course hopefully or at least commonly only present to loud parts of the audio. *Scaling can be done before or after summing (both is e.g. possible to be influenced by the user in Samplitude with the input gain options or the master fader). Since scaling also applies to the input, there's again a lot of things that can be done differently. Even the discussions about panning law settings may be put here. Since integer based engines require scaling before summing I can easily imagine different appproaches in other DAW's. *Dithering: nothing much to say here: there are more algorithms than we can think of here. A major "ditherence" may be its application for intermediate steps when necessary.

So here I see many possible reasons for different behaviour and even mis-behaviour. And often I have seen or heard the results - not only in other DAWs, but partially also in our (some still may remember a dithering problem in version 5.1x).

-An often uncommented problem seems the timeline representation of audio material. There sure is a difference between sample based or PPQ based approaches. The first gives perfect audio reproduction but possible problems with loops and BPM values while the latter more easily may sacrifice the first in favour of the BPM.

So to sum it up: yes, the simple adding of numbers should basically give the same results, but even there may be a bit of voodoo here - although it might be hard to realize the differences. The more obvious reason for sound differences are decisions about the processing at input and output stage, with a lot of different ways to go - and I neither mentioned the connection with audio drivers and other parts of the system.

Regards, Volker

imagine if this product was called " Basic Tools ". everything the same. features/gui/etc.

i'm sure it wouldnt be the industry shampoo. psychology man.

sonar is great but its name reminds people to some military equipment/submarines.
studio one PRO : pro is there - its a hit or its going to be, worldwide.
reaper - bad name. jack the ripper? death? ouch. its the best but will never will be big. bedroom stuff. awesome for us, broken amateaurs. we know its the best but its secret.
nuendo/cubase : very german, kraftwerk stuff/precision.
fl studio : a fucking joke.
live : deadly. not only for live. horrible timeline/gui.

peace

pro tools 10,

im still searching what you wanted me to tell with this post? there is no information or an argument at all. only some funny plays with some words. come one if debatting then with niveau. i posted something that can prove that there is so much in an pc and an daw that affects the sound and this was all from you?

as i mentioned the previous post was not from me its from an magix programmer.