2018.3 & 4 Running Well Here.

[TOM@METRO]

Who else?

[grayter1]

I'm good here...

tg

[jeam25]

Perfect !

[amagras]

Thanks.

[s.d. finley]

its running fine over here but I still have MASSIVE cpu spikes that should not be happening :confused:

[TNM]

its running fine over here but I still have MASSIVE cpu spikes that should not be happening :confused:

what buffer and sample rate? Pro tools can not cope under certain buffers with core audio or HD Native

[DAVE24]

When pitch shifting a track on elastic time the pitch change seems to have no effect on clip while on real-time processing unless you switch to rendered processing. Is there a way to report this to avid. Man, every time a new update comes out, they fix some bugs but then reintroduce new ones that worked fine before. :mad:

[albee1952]

When pitch shifting a track on elastic time the pitch change seems to have no effect on clip while on real-time processing unless you switch to rendered processing. Is there a way to report this to avid. Man, every time a new update comes out, they fix some bugs but then reintroduce new ones that worked fine before. :mad:
Odd, its working fine here^^^. In any case, I am also having some -9093 errors, but its better now than with 12.8.x(and based on others with a very similar computer build, I don;t blame Pro Tools. The errors are solved by about 90% as soon as I disconnect from the internet:o

[john1192]

When pitch shifting a track on elastic time the pitch change seems to have no effect on clip while on real-time processing unless you switch to rendered processing. Is there a way to report this to avid. Man, every time a new update comes out, they fix some bugs but then reintroduce new ones that worked fine before. :mad:

open a support case ...

[amagras]

I uninstalled Pro Tools only, installed the new version, restarted the computer and it was the smoother transition ever, not a single error, not a single warning, my preferences were intact and my sessions open the same as before. I had to check the version number to be sure it was 2018.3.

BTW, the name Jeffro has been trademarked in the PT credits! Also a lot of familiar names from the DUC there!

[maltastudio]

Working fine here so far,seems more stable,less spikes,will see.
Peace

[Emi]

Running great here. Stable as a rock.

[s.d. finley]

what buffer and sample rate? Pro tools can not cope under certain buffers with core audio or HD Native

24bit or 32 bit @48k. 64 buffer with 3 audio tracks and zero plug ins and the cpu meter is spiking like crazy, even with transport not engaged/PT not playing.
128 is better but I get the occasional AAE-9093 error. I looked up the error and its not a clocking error. When I use just one Lynx 16 with LTHD, both with up to date firmware, I still get the error. Normally its 2 Aurora 16s with a Mytek DSD DA for monitoring. If use the Mac Pro built in as the interface no spikes. MacPro is 5.1 dual hex core 3.33ghz 64 gb RAM with an SSD for the OS which is El Capitan X.11.6. I had adjusted my buffer to 256 in a 20 track session with maybe 15 or so plug in, no reverb or multi band, linear eq so nothing piggish, and still got an error.

[CHRIS AIKEN]

I would update to Sierra. Going from El Capitan to Sierra made my cpu issues way better. I run a Lynx aurora 16 connected by thunderbolt.


Sent from my iPhone using Tapatalk

[TOM@METRO]

Odd, its working fine here^^^. In any case, I am also having some -9093 errors, but its better now than with 12.8.x(and based on others with a very similar computer build, I don;t blame Pro Tools. The errors are solved by about 90% as soon as I disconnect from the internet:o

Similar here, performance is further improved with Internet disconnected. But it's always been that way for me. But in fairness, even with the Internet connected, 2018.3 is a very strong version here.

[abc1mce2]

Similar here, performance is further improved with Internet disconnected. But it's always been that way for me. But in fairness, even with the Internet connected, 2018.3 is a very strong version here.

Are you guys disconnecting the internet for device manager or somewhere else?

[xylie6]

Disconnecting and disabling WIFI are part of the recommended setup. I can tell you that WIFI in particular will slow down your computer for sure.

With all the spyware/malware and whatever else programmers do for the money, your computer is constantly reporting to someone what you do.

I like the idea of having a Pro Tools drive that does nothing else at all. No internet, no other programs, nothing. Anyway, that's what it is.

[Sardi]

Disabling WiFi is a ridiculous optimisation now that they offer iLok cloud.

Sure, there’s Ethernet, but if you’re on a laptop and have to plug a dongle in to get an Ethernet socket, then you might as well just use the damn iLok dongle.


Sent from my iPhone using Tapatalk

[john1192]

and you cannot use PT Control without Wi-Fi .. can be LAN only yes .. but how many have this only

[albee1952]

I have a wifi router connected to handle an Artist Mix and iPad running the Control app. I simply unplug the cable that brings the internet in the control room(from the office ethernet switch).

[migueldgoncalves]

I must have missed 2018.2...
What's new in version 2018.3? On the website it only shows info on 2018.1

[Sardi]

There was no 2018.2.

PT expert has the full list of bug fixes if you can’t find them on AVID’s site.


Sent from my iPhone using Tapatalk

[JoelG]

I must have missed 2018.2...
What's new in version 2018.3? On the website it only shows info on 2018.1

To further Sardi's post.. Versions are year.month - so 2018.March basically. There was no release in February.

Joel

[s.d. finley]

I would update to Sierra. Going from El Capitan to Sierra made my cpu issues way better. I run a Lynx aurora 16 connected by thunderbolt.


Sent from my iPhone using Tapatalk


Hi thanks for the info, just regular Sierra? I might have to try that

[Drew Mazurek]

Bookmark this page.

http://avid.force.com/pkb/articles/en_US/ReadMe/Pro-Tools-Release-Notes

[TrackerLe]

Strange... I thought the bug with BX_Digital and Eq Curve track view was fixed with 2018.3...
Brainworx Digital v3 no longer crashes Pro Tools when Mix Window EQ curve is shown (PT-237575)

It seems to be on Mac...but on Windows 10... BX_Digital still crashes Protools 2018.3 when EQ Curve in the Mix Window is activated...

[gives]

I would update to Sierra. Going from El Capitan to Sierra made my cpu issues way better. I run a Lynx aurora 16 connected by thunderbolt.


Sent from my iPhone using Tapatalk

Agreed El Capitan is a mess..

[gives]

Disconnecting and disabling WIFI are part of the recommended setup. I can tell you that WIFI in particular will slow down your computer for sure.

With all the spyware/malware and whatever else programmers do for the money, your computer is constantly reporting to someone what you do.

I like the idea of having a Pro Tools drive that does nothing else at all. No internet, no other programs, nothing. Anyway, that's what it is.

I never run Wifi always Ethernet connection to may control room studio. I have to have that with all the work going out the door, however never a problem with slowing here and have had not issues for years. Always a good idea to make sure that you don't have any spyware or crap in some prefs folder. I found some stuff that was giving me problems on one of my laptops on my mac. I was not really installed, but with some IT work got ride of anything using the System Profileer extensions and found some thing there were not from an identified developer and looked up what it was. Just some junk that somehow got on there. Fixed my problems and never came up a gain. G

[Downtown_BE]

I noticed that some backup software (even time machine) does slow down my system too (sierra and protools 12.8.3)

[TNM]

24bit or 32 bit @48k. 64 buffer with 3 audio tracks and zero plug ins and the cpu meter is spiking like crazy, even with transport not engaged/PT not playing.
128 is better but I get the occasional AAE-9093 error. I looked up the error and its not a clocking error. When I use just one Lynx 16 with LTHD, both with up to date firmware, I still get the error. Normally its 2 Aurora 16s with a Mytek DSD DA for monitoring. If use the Mac Pro built in as the interface no spikes. MacPro is 5.1 dual hex core 3.33ghz 64 gb RAM with an SSD for the OS which is El Capitan X.11.6. I had adjusted my buffer to 256 in a 20 track session with maybe 15 or so plug in, no reverb or multi band, linear eq so nothing piggish, and still got an error.

there is no way it can do 64 buffer sorry.. no matter if your mac is a super yet to be released one. No issues at 128 here though with apollo thunderbolt.

but yet you say you can use the built in audio no spikes? I don't experience that.. It depends i believe on how tracks are armed for monitoring with fx...

and if you have vi tracks armed so you can play them live..

128 seems the best compromise here over all, very rarely i have issues.

[CHRIS AIKEN]

Hi thanks for the info, just regular Sierra? I might have to try that



Yup regular Sierra. Not sure how High Sierra works, I’ll do that eventually


Sent from my iPhone using Tapatalk

[CHRIS AIKEN]

there is no way it can do 64 buffer sorry.. no matter if your mac is a super yet to be released one. No issues at 128 here though with apollo thunderbolt.



but yet you say you can use the built in audio no spikes? I don't experience that.. It depends i believe on how tracks are armed for monitoring with fx...



and if you have vi tracks armed so you can play them live..



128 seems the best compromise here over all, very rarely i have issues.



I run at a 64 buffer. I get the occasional spike but for the most part it’s really good now. I can even do 32 but the spikes are a bit more often so I don’t bother with it.


Sent from my iPhone using Tapatalk

[TNM]

I run at a 64 buffer. I get the occasional spike but for the most part it’s really good now. I can even do 32 but the spikes are a bit more often so I don’t bother with it.


Sent from my iPhone using Tapatalk

well it would be really good to know your actual mac model, and OS.. and audio interface...

as well as how many tracks you have armed at 64 in "live" mode at any one time.

[loud neighbor]

Wish I could report better operation. 2018.1 was fine but so far 2018.3 has been really unstable for me. A lot of random crashes. For example, it crashed when I moved an instrument track after stopping playback. Crashed after changing buffer sizes. Crashed when drag and dropping audio in. This is in a very small 48k session with less than 20 tracks and hardly any plugins.

Perhaps it's an El Capitan issue? WiFi is off. I'm running 10.11.6 on a trashcan Mac Pro with 32GB of RAM and separate SSD's for sounds and sessions. S3 with PT Control (latest version) on an iPad (no Dock). Eucon (18.3) may be interfering because that is crashing along with PT from time to time.

[CHRIS AIKEN]

well it would be really good to know your actual mac model, and OS.. and audio interface...

as well as how many tracks you have armed at 64 in "live" mode at any one time.

I added my system specs to my signature but I'm running...

Hackintosh 10.12.6 -16 gigs Ram - Lynx Aurora 16 Thunderbolt - Protools 2018.1 HD

If it's helpful for anyone to know...I can record 12 tracks of drums with Slate VMR on every track at a 64 Buffer.

[Sardi]

I run at a 64 buffer. I get the occasional spike but for the most part it’s really good now. I can even do 32 but the spikes are a bit more often so I don’t bother with it.


Sent from my iPhone using Tapatalk



Same.

Tracked a VO session at 32 sample buffer last week. 2 tracks recorded for 50 mins straight. No plugins, but some people are saying they can’t do that either.

Oddly enough, earlier today I had 4 tracks playing back with no plugins at 1024 buffer and got the CPU error message 3 times.

Bizzarre.


Sent from my iPhone using Tapatalk

[TNM]

can definitely do 12 tracks on my macbook pro with 12 VMrs as they are so light at 64 buffer..

and can actually do 64 tracks here at 32 buffer with no plugins at all.

So that all sounds normal. But it's VI's and when you start adding delay based effects like reverb that 32 and 64 buffer become an issue if "live".

Hackintosh doesn't say much about the chip but your performance sounds about right.

Now try 64(or 32) buffer with a couple diva's armed.. but then try it on another daw and see the difference, literally like 1/5th the usage.

PS just to add, the lynx drivers are very good, which of course helps. :)

[grayter1]

I run at a 64 buffer. I get the occasional spike but for the most part it’s really good now. I can even do 32 but the spikes are a bit more often so I don’t bother with it.

Same here. Running at 64 buffer while composing. I've had to bump to 128 if the mix is gets really dense, but overall I sit at 64.

tg

[gives]

Try enabling Dynamic Plug-In Processing in the Playback Engine if you have not done so to the person that mentioned the -9093 errors. I have not had the problems ever on my Native HD system except for a few years ago on V 11 when it first came out. Offline bouncing can be a solution if you are in the box for bounces. The internet thing I have never had an issue with wither. I connect via ethernet with no problems all day long.
g

[CHRIS AIKEN]

can definitely do 12 tracks on my macbook pro with 12 VMrs as they are so light at 64 buffer..

and can actually do 64 tracks here at 32 buffer with no plugins at all.

So that all sounds normal. But it's VI's and when you start adding delay based effects like reverb that 32 and 64 buffer become an issue if "live".

Hackintosh doesn't say much about the chip but your performance sounds about right.

Now try 64(or 32) buffer with a couple diva's armed.. but then try it on another daw and see the difference, literally like 1/5th the usage.

PS just to add, the lynx drivers are very good, which of course helps. :)

I updated my specs... 3.5 GHz Intel Core i7. I was mostly commenting for the guy who had a problem running 3 tracks, no plugins, at a 64 buffer. Live VI's at a low buffer is another issue for sure...I tend to stay at 128 for that.

[TNM]

I updated my specs... 3.5 GHz Intel Core i7. I was mostly commenting for the guy who had a problem running 3 tracks, no plugins, at a 64 buffer. Live VI's at a low buffer is another issue for sure...I tend to stay at 128 for that.

Ok yeah.. that's where I stay, 128 to play live Vi's..

It's interesting the hackintosh has that issue as well (as i presume unlike on a real mac you were able to disabled intel cpu throttling)..

I believe it's quite simply a pro tools specific issue.

Yeah the guy having an issue recording 3 tracks at 64 buffer, that's not right.. my 7 year old imac does that even at 32 buffer without issue.. A lot of it comes down to audio interface drivers, the OS of course and if on windows, any dpc latency issues

[climber]

I updated from 2018.1 yesterday morning. Just installed over existing version. Then spent the afternoon and evening doing some mixing and MIDI drum editing and programming on an original tune I’ve been working on. Loaded another tune with about 30 tracks including Keyscape and RMX. No errors and it ran fine at 512. Then I laid down some background vocals for a friend. 10 audio tracks, no VI’s, at 32 using my VMS with several Slate plugins in the VMR. Again, no stutter, no errors, it just worked. Today I spent much of the day editing and mixing on a couple of my tunes. Probably an average of 30 tracks on each, some Keyscape, some RMX, one with Kontakt. Worked just fine. No errors and no crashes.

Of course none of this really stressed my system, but I’m happy with how it went. Of course YMMV.

[Jazzbass56]

I’m running 2018.3 on a Win 10 Pro workstation and a New Mac Pro 12 core beast Both workstations have 64 gb of ram and 2018 is the best version I have ever had on my Windows workstation, the Mac is always stable but I’m really happy to report the Windows version is getting there, I also forgot to mention I’m running High Sierra on the Mac 10.13.3 one thing I found out for me was don’t use iCloud Drive to sync your documents folder on your workstation if that is where you store your track presets etc, that caused me some grief but now I’m not doing that it’s much better, and Windows now shuts down without hanging
So the new PT was worth the upgrade for me


Sent from my iPhone using Tapatalk

[abc1mce2]

Strange... I thought the bug with BX_Digital and Eq Curve track view was fixed with 2018.3...
Brainworx Digital v3 no longer crashes Pro Tools when Mix Window EQ curve is shown (PT-237575)

It seems to be on Mac...but on Windows 10... BX_Digital still crashes Protools 2018.3 when EQ Curve in the Mix Window is activated...

Can confirm the bug. If the EQ curve in the Mix Window is closed no crash. If the window is opened and you try to adjust and the EQ...crash. If you just open BX v.3 plugin no crash, just don't try to EQ anything until you close the EQ curve view.

[LDS]

24bit or 32 bit @48k. 64 buffer with 3 audio tracks and zero plug ins and the cpu meter is spiking like crazy, even with transport not engaged/PT not playing.
128 is better but I get the occasional AAE-9093 error. I looked up the error and its not a clocking error. When I use just one Lynx 16 with LTHD, both with up to date firmware, I still get the error. Normally its 2 Aurora 16s with a Mytek DSD DA for monitoring. If use the Mac Pro built in as the interface no spikes. MacPro is 5.1 dual hex core 3.33ghz 64 gb RAM with an SSD for the OS which is El Capitan X.11.6. I had adjusted my buffer to 256 in a 20 track session with maybe 15 or so plug in, no reverb or multi band, linear eq so nothing piggish, and still got an error.


We have almost the same spec Mac Pro. I am running a dual hex 3.33ghz 5.1, but with only 16gig of ram. I can playback 20+ tracks of audio through 5 groups and about 30 plugins... all while recording 10 new tracks, each monitoring through an additional plugin PLUS 6 stereo headphone mixes. All at 64 sample buffers, 32 bit floating & 48kHz sample rate. I am running Sierra on my system...

Here are some screenshots to give you an idea of what is possible:

https://www.dropbox.com/s/2i6ranj6v2io40w/28424478_10156339693844073_4913146938345227622_o.j pg
https://www.dropbox.com/s/txi4iv5ihbc4wtk/28514461_10156339694934073_8372053540999791991_o.j pg

https://photos-4.dropbox.com/t/2/AAD1ss0hIS_m0I3tetrL0DZbbNNl13nt6EGmm6Os-9XEzg/12/83605231/jpeg/32x32/3/1520784000/0/2/28424478_10156339693844073_4913146938345227622_o.j pg/EIKHjEEYsfw9IAIoAg/cI5M49lLiCLBatOOKbsu5JTXBh2XSRATFAl9a7K31Yw?dl=0&size=32x32&size_mode=5
https://photos-4.dropbox.com/t/2/AACqL4pE6-IDKrA6N4BgFQDwMoE9ow7pMBT4dN_nV5QFLg/12/83605231/jpeg/32x32/3/1520784000/0/2/28514461_10156339694934073_8372053540999791991_o.j pg/EIKHjEEYsfw9IAIoAg/53QShqpzJSsL47BGOyLhPPtJ45msrTP-1UqMPJv7euU?dl=0&size=1280x960&size_mode=3

Are you using your Aurora's via a HD Native card? Or some other protocol? From my experience, not all audio interfaces are created the same. The session above was running an Antelope Zen Studio which runs pretty ok... but it does seem to chew up considerably more system resources than an RME PCIe or SSL Madixtreme card does. I do get spikes... but they seem to bounce around 20-30% on top of whatever Pro Tools is using.

[BScout]

Can confirm the bug. If the EQ curve in the Mix Window is closed no crash. If the window is opened and you try to adjust and the EQ...crash. If you just open BX v.3 plugin no crash, just don't try to EQ anything until you close the EQ curve view.
Yeah, no crash on Mac. Haven't checked Windows yet. (and strangely, since we are talking about the EQ view, the Brainworx digital v3 doesn't have any effect on that eq view in the first place with the latest version of the plugin and 2018.3)

[s.d. finley]

I found a couple bugs on 2018.3 today. I had several audio tracks record enabled and when I tried to drag a hardware output send from one record enabled audio track to another I could not. If I had the audio track not record enabled, I could drag and drop its send to an audio track that was record enabled.
Also dragging and dropping multiple files at once from the regions bin into the edit window caused the scribble strips on my C/24 to FREAK out during the process. Yes I am still having CPU spikes too. Another one happened during recording today.

[s.d. finley]

We have almost the same spec Mac Pro. I am running a dual hex 3.33ghz 5.1, but with only 16gig of ram. I can playback 20+ tracks of audio through 5 groups and about 30 plugins... all while recording 10 new tracks, each monitoring through an additional plugin PLUS 6 stereo headphone mixes. All at 64 sample buffers, 32 bit floating & 48kHz sample rate. I am running Sierra on my system...

Here are some screenshots to give you an idea of what is possible:

https://www.dropbox.com/s/2i6ranj6v2io40w/28424478_10156339693844073_4913146938345227622_o.j pg
https://www.dropbox.com/s/txi4iv5ihbc4wtk/28514461_10156339694934073_8372053540999791991_o.j pg

https://photos-4.dropbox.com/t/2/AAD1ss0hIS_m0I3tetrL0DZbbNNl13nt6EGmm6Os-9XEzg/12/83605231/jpeg/32x32/3/1520784000/0/2/28424478_10156339693844073_4913146938345227622_o.j pg/EIKHjEEYsfw9IAIoAg/cI5M49lLiCLBatOOKbsu5JTXBh2XSRATFAl9a7K31Yw?dl=0&size=32x32&size_mode=5
https://photos-4.dropbox.com/t/2/AACqL4pE6-IDKrA6N4BgFQDwMoE9ow7pMBT4dN_nV5QFLg/12/83605231/jpeg/32x32/3/1520784000/0/2/28514461_10156339694934073_8372053540999791991_o.j pg/EIKHjEEYsfw9IAIoAg/53QShqpzJSsL47BGOyLhPPtJ45msrTP-1UqMPJv7euU?dl=0&size=1280x960&size_mode=3

Are you using your Aurora's via a HD Native card? Or some other protocol? From my experience, not all audio interfaces are created the same. The session above was running an Antelope Zen Studio which runs pretty ok... but it does seem to chew up considerably more system resources than an RME PCIe or SSL Madixtreme card does. I do get spikes... but they seem to bounce around 20-30% on top of whatever Pro Tools is using.

Yes I am using HDN with 2 Lynx Aurora 16s with the LTHD cards all with updated firmware. Thats great with your system. Too bad my system sucks. This is really absurd. I have an HD Omni at my other studio I am going to bring it in and see if that makes any difference. If it does not then its the stupid HDN card which is also absurd!! I NEED 64 I/O.

[s.d. finley]

Yes. Happened with 2018.1 as well. I'm on 10.12.6

Yes, but the actual area where the tool changes seems to have moved little bit further south if you know what I mean. For me the selector for the trim tool seems to need to be lower in the region for it to change.

[dankin]

Yes, but the actual area where the tool changes seems to have moved little bit further south if you know what I mean. For me the selector for the trim tool seems to need to be lower in the region for it to change.

I haven't noticed that yet. What I've been seeing is after working for a while, sometimes the tool won't change from the hand tool, but it still works. It's just a little weird seeing a hand tool while yo trim a region, or add a fade. If I quit PT and reopen it will be fine for a while, then it will happen again.

[s.d. finley]

I haven't noticed that yet. What I've been seeing is after working for a while, sometimes the tool won't change from the hand tool, but it still works. It's just a little weird seeing a hand tool while yo trim a region, or add a fade. If I quit PT and reopen it will be fine for a while, then it will happen again.

yes that is odd, I have not noticed that yet.

[TOM@METRO]

I haven't seen this here, but I'm on Windows.

[jeam25]

So far since I bought into Pro Tools in Dec 2015, this is the best version I have ever used. I haven't had a single crash and performance seems even slightly improved (still no where near cubase/Logic levels at 32 or 64 buffer, but better).
performance at 128 buffer is outstanding, including absolute full utilisation of my 8 logical cores.



Hi TNM !

Maybe is an audio interface problem :-/ ?

I must say that with my old 003 i had to record at 128 and mix at 1024 . I've tried ever possible trick/tweak on the internet and it didn't change this a bit . But i've upgraded my Audio Card , now im using a clarett 8 pre X and not talking about the quality improvement , now i can track at 32 and mix at 64 . I use a lot of VI without freezing them and UAD plugins mainly on my mixing sessions . Not a single error since that , my cores never pass 15% on the PT meter on most complex mixes and not a single CPU spike neither .
Also i have a TC Poco wich i use because of the TC master X3 . I use it for mastering almost everytime . If i didnt have my buffer at 1024 while using it my system crashed almost 99% of the time . Now some times i forgot that i leave the buffer at 64 when do mastering and using the TC Master X3 because it stays so solid even with it .
It makes me smile when i remember and dicover that i just did the master at 64 buffer size :-) .

[LDS]

Yes I am using HDN with 2 Lynx Aurora 16s with the LTHD cards all with updated firmware. Thats great with your system. Too bad my system sucks. This is really absurd. I have an HD Omni at my other studio I am going to bring it in and see if that makes any difference. If it does not then its the stupid HDN card which is also absurd!! I NEED 64 I/O.


It does seem ridiculous if you are only recording three tracks at once and still getting drop outs, etc at 64 samples. I too noticed the difference in performance when using just the in-built sound card in my Mac Pro. It runs very efficiently! Out of curiosity, have you tried a different slot in your Mac Pro? I think the closest slot to the graphics card is a 4x PCIe... while the two towards the top are 1x each.

2018.3 doesn't seem as efficient as 2018.1 to me. I have had to untick dynamic plugin allocation in the hardware settings to get it to run near the smoothness of 2018.1.

[MixerGuy]

I hear that with 2018.3. There may be an ILOK - PT issue?

supposedly on the ILOK side?

Anyone else getting this ?

Thanks.

[abomeerza]

Perfect in 2018.1 and 2018.3

[climber]

I hear that with 2018.3. There may be an ILOK - PT issue?

supposedly on the ILOK side?

Anyone else getting this ?

Thanks.

not here. you don't say what system or OS you're on...:confused:

[TOM@METRO]

No ilok issues here.

[MixerGuy]

not here. you don't say what system or OS you're on...:confused:

It isn’t me.

It is a pal.

Don’t know his OS.

I suspect Mac.

Don’t know.

[64GTOBOY]

So far running fine on Win 7 even though unsupported. I had some weird GUI mouse pointer issues with 12.8 but not now.

[TOM@METRO]

So far running fine on Win 7 even though unsupported. I had some weird GUI mouse pointer issues with 12.8 but not now.

It's good to hear there's still some life left in W7. :cool:

[TNM]

Hi TNM !

Maybe is an audio interface problem :-/ ?

I must say that with my old 003 i had to record at 128 and mix at 1024 . I've tried ever possible trick/tweak on the internet and it didn't change this a bit . But i've upgraded my Audio Card , now im using a clarett 8 pre X and not talking about the quality improvement , now i can track at 32 and mix at 64 . I use a lot of VI without freezing them and UAD plugins mainly on my mixing sessions . Not a single error since that , my cores never pass 15% on the PT meter on most complex mixes and not a single CPU spike neither .
Also i have a TC Poco wich i use because of the TC master X3 . I use it for mastering almost everytime . If i didnt have my buffer at 1024 while using it my system crashed almost 99% of the time . Now some times i forgot that i leave the buffer at 64 when do mastering and using the TC Master X3 because it stays so solid even with it .
It makes me smile when i remember and dicover that i just did the master at 64 buffer size :-) .

Hi there:), drivers don't get much better than the blackface thunderbolt apollos.. not on mac anyway.
You are on windows which makes a difference cause you can stop your processor from throttling in bios, heck or even in the OS itself, which we can not do on mac unfortunately. This definitely has something to do with it, as even on my old 2012 2.3ghz ivy bridge windows 7 laptop, even though low buffer was not amazing on pro tools and still instigated multiple cores in cases only one core should be used (eg a single VI), it still had a much better dropout threshold than my newer and supposedly much faster macbook pro.



One thing to note: Pro tools uses a 1024 internal buffer for all VI's once you have recorded them. So it doesn't matter what your main buffer is at..

If you are telling me, you can have a busy project, and then ARM and play a heavy VI, something like Diva for example, at 32 or 64 buffer alongside the rest of the project playing back, other VI's, audio tracks with effects etc.. then YES, that is a HUGE difference to anything I have ever experienced on mac, nor anyone else I know that uses Pro tools on mac.

I really would have to attribute it to windows' possibility to have a dead steady frequency clock for the processor.

It's also unusual in your case, as dawbench has the clarett on windows marked very low for driver quality vs other thunderbolt interfaces (RME and UAD).

But, no matter what, i am very happy for you that you can work at such low buffer!

Over here on the macbook i can track many tracks at 32 buffer, and i can put any avid effect including d verb on, but if i start putting even one heavy 3rd party delay based effect, it's game over. 64 buffer is a bit better. 128 buffer I can do anything, i can have every single core hammered and every track being monitored with effects, without issue.

[s.d. finley]

It does seem ridiculous if you are only recording three tracks at once and still getting drop outs, etc at 64 samples. I too noticed the difference in performance when using just the in-built sound card in my Mac Pro. It runs very efficiently! Out of curiosity, have you tried a different slot in your Mac Pro? I think the closest slot to the graphics card is a 4x PCIe... while the two towards the top are 1x each.

2018.3 doesn't seem as efficient as 2018.1 to me. I have had to untick dynamic plugin allocation in the hardware settings to get it to run near the smoothness of 2018.1.

yes I originally had the HDN card in slot 4, but then moved it to slot 2 which is right next to the graphics card. I will try slot 3 but my hopes are very low but I am literally willing to try just about anything to get this system to work properly.

[TOM@METRO]

yes I originally had the HDN card in slot 4, but then moved it to slot 2 which is right next to the graphics card. I will try slot 3 but my hopes are very low but I am literally willing to try just about anything to get this system to work properly.

Let us know if you see any progress on this.

[TNM]

yes I originally had the HDN card in slot 4, but then moved it to slot 2 which is right next to the graphics card. I will try slot 3 but my hopes are very low but I am literally willing to try just about anything to get this system to work properly.

all dynamic plugin option does is release cpu on transport stop and when there is gaps in the audio during playback so the effect doesn't have to process..

I am finding it really bizarre that 2018.3 has worsened efficiency for you.. i think you should start a support ticket.. over here it's the opposite, everything is running a bit tighter and not only that, way less overload messages...

[CHRIS AIKEN]

yes I originally had the HDN card in slot 4, but then moved it to slot 2 which is right next to the graphics card. I will try slot 3 but my hopes are very low but I am literally willing to try just about anything to get this system to work properly.



Did you try Sierra yet? Still not better with it?


Sent from my iPhone using Tapatalk

[s.d. finley]

Did you try Sierra yet? Still not better with it?


Sent from my iPhone using Tapatalk

I am installing it right now on a fresh disk. Fingers crossed!!:cool:

[s.d. finley]

all dynamic plugin option does is release cpu on transport stop and when there is gaps in the audio during playback so the effect doesn't have to process..

I am finding it really bizarre that 2018.3 has worsened efficiency for you.. i think you should start a support ticket.. over here it's the opposite, everything is running a bit tighter and not only that, way less overload messages...

I have started a support ticket and the Avid tech has been very helpful. They are going to give me a call later so they can see whats going on

[noiseboyuk]

I've had an irritating thing with PT 2018.1 and .3 in Windows. If I click the PT icon on the Windows Taskbar and it's already open somewhere, PT is lost. There's no way of getting back to it, though it looks like it's still active in the background somewhere but Alt Tab doesn't help and I can't access it via task manager. I have to wait for an auto-save, kill it and re-open from scratch. Anyone else have this?

[amagras]

I've had an irritating thing with PT 2018.1 and .3 in Windows. If I click the PT icon on the Windows Taskbar and it's already open somewhere, PT is lost. There's no way of getting back to it, though it looks like it's still active in the background somewhere but Alt Tab doesn't help and I can't access it via task manager. I have to wait for an auto-save, kill it and re-open from scratch. Anyone else have this?Sounds like there's a disc on your dvd drive.

[dabiochemist]

Soundbase Favorite list is gone, The heart in right corner use to list all the sounds that I favorited nothing there now

[noiseboyuk]

Sounds like there's a disc on your dvd drive.

Spooky - yes there is. How is this a thing?

Now I'm really conflicted, since (you'll just have to believe me on this) Kontakt
loads faster with a disc in the drive. This, mind you, is the same disc drive that in Windows 7 couldn't do ASIO audio at all unless there was a disc in the drive, which I really do understand sounds made up, but I can assure you was absolutely true.

The good news is I get a new rig and new disc drive next week, and hopefully will put all this nonsense behind me. Curious to know why it makes PT misbehave though....

[TOM@METRO]

It's just best to keep the optical drive free when running Pro Tools.

[TOM@METRO]

If there's anyone having any reproducible issues, please post here along with the steps reproduce, and I'll report it. Pleas include all system info.

For me, this is still one the best releases ever. I haven't had a single error or crash since installing it.

[s.d. finley]

Did you try Sierra yet? Still not better with it?


Sent from my iPhone using Tapatalk

Sierra actually works much better than El Crap. Still get some spiking but its not as nearly as bad and so far, fingers crossed, no show stoppers. :cool:

[TOM@METRO]

Sierra actually works much better than El Crap. Still get some spiking but its not as nearly as bad and so far, fingers crossed, no show stoppers. :cool:

Thanks, SDF. ;)

[JFreak]

I can double that, Sierra has been very well built OS and it makes me think about Snow Leopard which left PPC code burden behind. But in this case Sierra is the last OS before Apple's new filesystem. It seems they have put more effort than usual to iron out bugs and even had time to tweak their code for perfromance.

With that said, all of my computers are running High Sierra but that is because I want to gather as mucb first hand experience from the filesystem than possible. I have accepted the fact that this approach will let me face some kinks here and there, but those have been fewer than I expected.

...and the next OS is likely released soon :P

[CHRIS AIKEN]

Sierra actually works much better than El Crap. Still get some spiking but its not as nearly as bad and so far, fingers crossed, no show stoppers. :cool:



Good to hear. If you’re trying to just record audio (not sure about with VI’s) at a low buffer. I’ve found using an app called Cpu Setter to disable hyper threading works well.

I recently did a drum tracking (14 tracks) session at a 32 buffer....not one spike. That’s with Slate VMR plug-ins on every track as well as Valhalla Room on an aux.

I’ll try to test it with some cpu intensive VI’s and see if it helps.

Chris


Sent from my iPhone using Tapatalk

[TNM]

Good to hear. If you’re trying to just record audio (not sure about with VI’s) at a low buffer. I’ve found using an app called Cpu Setter to disable hyper threading works well.

I recently did a drum tracking (14 tracks) session at a 32 buffer....not one spike. That’s with Slate VMR plug-ins on every track as well as Valhalla Room on an aux.

I’ll try to test it with some cpu intensive VI’s and see if it helps.

Chris


Sent from my iPhone using Tapatalk

thanks for the tip, if works will uninstall xcode and reclaim 5gig of precious ssd space :D

but what we really need on mac is something that can disable certain cores per app.. in windows this is easy and built right in.

People are solving their windows PT cpu spikes by simply disabling one core only for PT.. i bet you it would work on mac too, it makes sense..

Why did avid remove the setting, sigh. Studio one has removed it too...

The only daw on mac to still let you choose (but only in divisions of 2) is Logic. But Logic doesn't have any spiking issue anyway so it doesn't matter, even at 32 buffer with 32 tracks armed.

I wonder if there is a way on mac, any way to tell PT to only use 6 or 7 threads (in the case of an 8 logic processor system, i.e a quad core with HT).

[s.d. finley]

Good to hear. If you’re trying to just record audio (not sure about with VI’s) at a low buffer. I’ve found using an app called Cpu Setter to disable hyper threading works well.

I recently did a drum tracking (14 tracks) session at a 32 buffer....not one spike. That’s with Slate VMR plug-ins on every track as well as Valhalla Room on an aux.

I’ll try to test it with some cpu intensive VI’s and see if it helps.

Chris


Sent from my iPhone using Tapatalk

damn, at 32 buffer? I cannot run any session at 32. I had downloaded the cpu setter when I was having issues with el cap which that app worked ok, but I would still get a buffer error even though I would not see the cpu buffer actually spike. That didn't happen often. I have an extra SSD that I will probably install High Sierra on just to see if that OS works any better.

[YYR123]

Yeah I never had sessions that ran at a 32 buffer.

Must be nice.

[Southsidemusic]

Yeah I never had sessions that ran at a 32 buffer.

Must be nice.

Neither have we but running a session at 32 buffersize or 64 buffer doesn't do squat for any session, no one will be able to hear that hence the big studios don't care to complain about that.

We produce and record a-list artists for major labels all the time and never had a whiff of mentioning regarding tracking at 32 or 64 so why chase this for no good reason?

[YYR123]

Yeah for HDX it won’t matter anyway but even at HD Native I wasn’t able to...

But yes you are right

[LDS]

Neither have we but running a session at 32 buffersize or 64 buffer doesn't do squat for any session, no one will be able to hear that hence the big studios don't care to complain about that.

We produce and record a-list artists for major labels all the time and never had a whiff of mentioning regarding tracking at 32 or 64 so why chase this for no good reason?

It is system dependant though. If you are running an interface with inherently low latency (HDX, HDn, Lynx AES16e, RME HDSPe, etc), then the improvement in overall system latency when flicking between32, 64 or 128 samples won't be so catastrophic. On my system, with a Zen Studio the difference between 32 sample and 128 sample buffers at 48kHz is ~5ms of latency or ~11ms of latency. The latter is a nice flam in the ear of a vocalist trying to record. Sure, the Zen Studio has a nice FPGA based mixer to avoid it... but being able to run at 32 or 64 samples means I can create headphone mixes and monitor through plugins directly in Pro Tools.

Low sample buffers may do squat for you... but they are the difference between a happy and unhappy performer for me.

[CHRIS AIKEN]

Neither have we but running a session at 32 buffersize or 64 buffer doesn't do squat for any session, no one will be able to hear that hence the big studios don't care to complain about that.

We produce and record a-list artists for major labels all the time and never had a whiff of mentioning regarding tracking at 32 or 64 so why chase this for no good reason?



I’m a drummer, recording at 32 or 64 is VERY different than 128. I’ve done it a bunch.

Also if a vocalist is tracking at 128 and there’s vocal bleed from headphones back to the mic the comb effect is way more noticeable.

If it works for you that’s cool though.

Chris


Sent from my iPhone using Tapatalk

[musicman691]

I’m a drummer, recording at 32 or 64 is VERY different than 128. I’ve done it a bunch.

Also if a vocalist is tracking at 128 and there’s vocal bleed from headphones back to the mic the comb effect is way more noticeable.

If it works for you that’s cool though.

Chris


Sent from my iPhone using Tapatalk
Drummer here as well (amongst other instruments) and tracking at 128 ain't a problem. I just think Charlie Watts and have at it.

[CHRIS AIKEN]

Drummer here as well (amongst other instruments) and tracking at 128 ain't a problem. I just think Charlie Watts and have at it.



Like I said, if it works for you at 128 all good! It is noticeable to some people though.


Sent from my iPhone using Tapatalk

[strangeLoop]

My outdated, small ram, system is running very well with Pro Tools 2018.3.

MIDI combined with audio, lots of editing.

CPU at 12%

We are getting back to the stability of Pro Tools 9.

John Clavin

[noiseboyuk]

I'm still getting a long-standing issue where bouncing to Quicktime offline causes a hang. I'd say it only happens one time in 20 or 30 so it's pretty rare, and there's no rhyme nor reason as to what causes a hang. When I restart and do it again, it always works fine. I have to keep remembering to save every time before I bounce, just in case.

I have similar issues with dragging a midi track to an audio track to commit. Most of the time no problem, once in a while it causes a permanent hang. Anyone else have either of these?

(Win 10 Pro)

[Stephen Bond]

We are getting back to the stability of Pro Tools 9.


Hopefully not but rather the stability of PT 5.3 :D

Stephen

[64GTOBOY]

^^^+1
The only thing I ever had any problems with 5.3 was when I had too many sampletank instances. Of course the feature sets don't really compare

[mrguitarguy]

Constant crashes using Melodyne here on OSX 10.12.6 on HD Native.

Celemony or Avid need to get this one fixed right away.

[TOM@METRO]

Melodyne is okay here, but this is on Windows 10, HDX.

[zion]

Melodyne is okay here, but this is on Windows 10, HDX.

Same here on Sierra 10.12.6. Its working just fine.

[TNM]

Same here on Sierra 10.12.6. Its working just fine.

same here

I think we are going to have to start saying what sample rate and buffer we are at when we get crashes with plugins. especially the sample rate could make all the difference.
Melodyne AAX works fine here at 44 and 48K

[TOM@METRO]

44.1 and 48, 32 float, 128 buffer.

[zion]

24/48 32/48 Buffer 128

[TOM@METRO]

Anyone running this at higher sample rates?

[grayter1]

I haven't read the entire thread, but how is it running in Windows 10?

I'm growing tired of issues created by minor Apple updates with my Hackintosh, and I'm thinking about going all in on Windows? Yesterday Apple pushed what appeared to be a minor security update, along with Safari and iTines, and my display drivers went bye bye.

Does anyone have Thunderbolt working under Win 10, and if so, which motherboard?

Thanks,

tg

[jjnssn]

I haven't read the entire thread, but how is it running in Windows 10?



I'm growing tired of issues created by minor Apple updates with my Hackintosh, and I'm thinking about going all in on Windows? Yesterday Apple pushed what appeared to be a minor security update, along with Safari and iTines, and my display drivers went bye bye.



Does anyone have Thunderbolt working under Win 10, and if so, which motherboard?



Thanks,



tg



Yes. Info in my profile X99-E WS/3.1. UAD forum has a lot of info on working TB systems. Windows 10 pro w/ TB3 AIC working excellent for my system configuration.


Sent from my iPhone using Tapatalk Pro

[YYR123]

I have a X99 Asus board but I do not use TB with my setup


All good here works a charm

Came from a 2012 MP 6-core and a Hackintosh before that.

Don’t miss it

[JFreak]

Anyone running this at higher sample rates?

I run at 96k all the time, no prob

[musicman691]

I haven't read the entire thread, but how is it running in Windows 10?

I'm growing tired of issues created by minor Apple updates with my Hackintosh, and I'm thinking about going all in on Windows? Yesterday Apple pushed what appeared to be a minor security update, along with Safari and iTines, and my display drivers went bye bye.

Does anyone have Thunderbolt working under Win 10, and if so, which motherboard?

Thanks,

tgOT but I have to ask - why did you allow the update? You don't have to take an update if you don't want.

[grayter1]

OT but I have to ask - why did you allow the update? You don't have to take an update if you don't want.

I got lazy and let my guard down. It’s that simple. I’m sure an updated driver will be available in a few days, but in the meantime, my system doesn’t “see” my card correctly and my screen looks like it’s running at an 800x600 resolution.

As much as I love my hack, I’m tired of worrying that every potential patch and OS update can brick my system. I’ll keep this system going, of course, but I’ll build a new Win 10 box to run along side and ease into it.

Thanks all for the suggestions.

tg

[musicman691]

I got lazy and let my guard down. It’s that simple. I’m sure an updated driver will be available in a few days, but in the meantime, my system doesn’t “see” my card correctly and my screen looks like it’s running at an 800x600 resolution.

As much as I love my hack, I’m tired of worrying that every potential patch and OS update can brick my system. I’ll keep this system going, of course, but I’ll build a new Win 10 box to run along side and ease into it.

Thanks all for the suggestions.

tg
Solution if you don't do it already - regular system clones. They've saved my bacon more than once from rogue updates I thought were safe. Which they were but not for everything I do on my daw computer. Basic system stuff was no problem but caused all kinds of havoc in PT. One time was a security update in OSX 10.9.5 that hosed PT usage.

[grayter1]

Solution if you don't do it already - regular system clones. They've saved my bacon more than once from rogue updates I thought were safe. Which they were but not for everything I do on my daw computer. Basic system stuff was no problem but caused all kinds of havoc in PT. One time was a security update in OSX 10.9.5 that hosed PT usage.

I’ve never done system backups. What’s the best software to use?

tg

[JFreak]

I’ve never done system backups. What’s the best software to use?

tg

Carbon Copy Cloner -- just clone your system drive in working condition and you have a copy available to boot from if you're too busy to clone it back to your system drive.

[Ray Lyon]

. The errors are solved by about 90% as soon as I disconnect from the internet:o

Is this wifi or ethernet or both?

[jjnssn]

Is this wifi or ethernet or both?



I never use WiFi. Have Ethernet hooked up all the time on my MBPr with TB dongle.


Sent from my iPhone using Tapatalk Pro

[jjnssn]

A couple of upgrade questions...

When I upgrade from 12.8.1 to 2018.3 can I rename the older PT app icon to 12.8.1 to preserve it in case there is a problem? Will the older version launch as is with no problem even though the new updated HD Driver is installed?

If I have two or more older versions on my Mac can I go back to any of the earlier versions by launching the older version directly from the Applications folder?

Thanks for your help!



That’s my understanding. I have never done that however.


Sent from my iPhone using Tapatalk Pro

[grayter1]

Carbon Copy Cloner -- just clone your system drive in working condition and you have a copy available to boot from if you're too busy to clone it back to your system drive.

NVIDIA updated the display driver this morning and I'm back up running. Now I'm off to purchase Carbon Copy Cloner...

tg

[Emi]

Anyone running this at higher sample rates?

Running at 96 and 192 here with good results.

[musicman691]

NVIDIA updated the display driver this morning and I'm back up running. Now I'm off to purchase Carbon Copy Cloner...

tg
And make sure the drive you backup to is not connected or at least turned on all the time. Less of a chance on it getting mucked up. Neat thing with CCC is you can set it to work on a schedule as well as manually. CCC can also do what they call a 'safety net' which if you're backing up to a drive you've backed up to in the past it will put the files that have been replaced by new versions in the safety net so you can go back if you so choose.

[TOM@METRO]

Running at 96 and 192 here with good results.

Thanks, Emi.

[climber]

A couple of upgrade questions...

When I upgrade from 12.8.1 to 2018.3 can I rename the older PT app icon to 12.8.1 to preserve it in case there is a problem? Will the older version launch as is with no problem even though the new updated HD Driver is installed?

If I have two or more older versions on my Mac can I go back to any of the earlier versions by launching the older version directly from the Applications folder?

Thanks for your help!

Yes and yes, Mac only...

[Ray Lyon]

Thank you Al!

[StillHollow]

And for us Windows 10 users, what is the best AND easiest Carbon Copy Cloner alternative to use ?

[The Weed]

And for us Windows 10 users, what is the best AND easiest Carbon Copy Cloner alternative to use ?

Macrium Reflect works very well for me and has great options. Others like Paragon.

[LightWing]

Only using it half a day so far...not bad.

See my possible PT 12.8.3 and/or Xpand!2 BUG thread I just started.

[profdraper]

And for us Windows 10 users, what is the best AND easiest Carbon Copy Cloner alternative to use ?

In my experience, there is *nothing* like CCC for Win10, unfortunately. If you are familiar with CCC then I suggest you have a scan of the relevant Win10 manuals for backup software before purchase and that will be immediately clear. eg:

In a scenario here using both system disk back up, plus several data SSDs and a RAID - variously for video, audio, sound libraries, other documents etc.


CCC is very fast to make back-ups, especially once beyond the initial full. The Win equivalent is usually not by comparison.
CCC can check all backups very quickly and then make updates to each image *simultaneously*; Win10 equivalents are much slower and can only update one image at at time, one after the other.
Biggest issue for me: Win10 software assumes some kind of office model and insists on setting up scheduled times for backup, like at 5pm when you 'go home' 'from work'. Yeah, right ....This is also quite laborious /boring to set up because each and every backup plan has to be manually fiddled with, timed disk schedules to avoid each other etc.
With CCC: for data disk backup 'schedule' I use 'when source or destination is reconnected'. This means that when I simply turn on my external JBOD array, CCC sees that and does quick, simultaneous backups at a time of my choosing, or in combination with regular scheduled backups. Some Win10 software provides for what appears to be similar as 'on event' commands but in my experience this is both poorly documented and unreliable.


FWIW, the two most consistently, highly rated Win10 backup solutions are 'Acronis True Image' and StorageCraft's 'Shadow Protect'. But they work as per the above comparison.

[jjnssn]

Macrium Reflect works very well for me and has great options. Others like Paragon.



I use Macrium Reflect Free. Works excellent for me on my PC.


Sent from my iPhone using Tapatalk Pro

[Songster]

Perfect !

good to know. I've been holding off going to 2018 and windows 10 because I have a 003 console, and a "formerly approved" HP Z400 workstation with a quad core ... still a little leary

[StillHollow]

Agree that CCC is the ultimate backup solution but looks like Macrium should work ok for me. Thanks profdraper and jjnssn

[TOM@METRO]

I've never tried Macrium, but i'll try to give it a shot tomorrow.

[The Weed]

The things I really like about Macrium: the ability to add Macrium to the Boot Menu so you don't always have to use a Rescue CD for certain functions. The ability to create Backup Definitions - all the parameters you want for an image say - and then have an Icon on your Desktop or Taskbar to run that Backup. Another is how fast Macrium loads a virtual drive of an image and how fast it unmounts it.

For example, on my audio computer I have two Backup Icons. One runs the backup image for my audio drive to a folder on my Storage Drive, the other runs the backup image for my OS to a different folder on my Storage Drive.

I keep the last 3 images of the audio and OS drives so this is the backup definition for each:

Audio: Keep 3 images, so delete the oldest, create a new image (makes 3 again) and verify the image.

OS: Keep 3 images, so delete the oldest, create a new image (makes 3 again) and verify the image, then shut the computer down.

You can pause and resume image backups and change whether the computer shuts down or not.

When I've installed new hard drives or SSDs, Macrium has seen the new drives without requiring any formatting and successfully restored images to them.

With the paid version of Macrium Reflect you can Restore to Dissimilar Hardware and also setup emails for success or failure of a backup.

HTH

[64GTOBOY]

I used Macrium when I updated the hard drives on my laptops. Worked without a hitch.

[TOM@METRO]

The things I really like about Macrium: the ability to add Macrium to the Boot Menu so you don't always have to use a Rescue CD for certain functions. The ability to create Backup Definitions - all the parameters you want for an image say - and then have an Icon on your Desktop or Taskbar to run that Backup. Another is how fast Macrium loads a virtual drive of an image and how fast it unmounts it.

For example, on my audio computer I have two Backup Icons. One runs the backup image for my audio drive to a folder on my Storage Drive, the other runs the backup image for my OS to a different folder on my Storage Drive.

I keep the last 3 images of the audio and OS drives so this is the backup definition for each:

Audio: Keep 3 images, so delete the oldest, create a new image (makes 3 again) and verify the image.

OS: Keep 3 images, so delete the oldest, create a new image (makes 3 again) and verify the image, then shut the computer down.

You can pause and resume image backups and change whether the computer shuts down or not.

When I've installed new hard drives or SSDs, Macrium has seen the new drives without requiring any formatting and successfully restored images to them.

With the paid version of Macrium Reflect you can Restore to Dissimilar Hardware and also setup emails for success or failure of a backup.

HTH

I used Macrium when I updated the hard drives on my laptops. Worked without a hitch.

Thanks Guys.

[moogboy100]

Yes I see that too, it's intermittent...and annoying! Sometimes if I have Safari or Mail open in the background, quitting it/them solves the problem, and sometimes my smart tool gets smart again if I move the cursor rapidly! :confused: But it's not just 2018.3, I noticed this in 2018.1 and 12.8.3 as well. Can't remember if 12.8.1 had this problem.

When 2018.3 was released I thought they fixed it but after a while the bug came back.

Confirmed here. Switching to other apps and then returning to Pro Tools, the smart tool no longer correctly switches the cursor between the various hand/insert/pointer images. The tool still works, it's just not showing the right cursor. Switching back out of pro tools to another app, and then back to Pro Tools again usually makes the smart tool snap return back to normal operation. But this is VERY annoying.

[TOM@METRO]

Confirmed here. Switching to other apps and then returning to Pro Tools, the smart tool no longer correctly switches the cursor between the various hand/insert/pointer images. The tool still works, it's just not showing the right cursor. Switching back out of pro tools to another app, and then back to Pro Tools again usually makes the smart tool snap return back to normal operation. But this is VERY annoying.

You're seeing this on 2018.3 right? Mac or Windows? What OS version?

[moogboy100]

You're seeing this on 2018.3 right? Mac or Windows? What OS version?

Mac Pro and Macbook Pro, both Sierra, both 2018.4.

[TOM@METRO]

I'm not seeing this on Windows. Perhaps some other Mac users could chime in.

[H-man]

yep, I'm seeing this too on my MBP running Sierra 2018.4.1

[Guy McDude]

2018.3 and .4 are solid here except for the offline bouncing/ committing issues outlined here:

http://duc.avid.com/showthread.php?t=398504

hope Avid adresses the problem.

[innesireinar]

As someone has already pointed out I am experiencing hysteric cpu peaks when running at 128 samples (45%) with a session with only 32 stereo audio tracks with no plugins inserted and with no addictional plugins in the folder (deleted the pref, removed all plugins and makes pt to reinstall its core plugins), but by switching to the internal mac out the cpu goes down to 5% (9 times less). Yesterday after further tests I discover that by closing or hiding the edit window while pt is playing the cpu goes down as when running through the internal mac out. Same thing happens if hiding tracks and maintaing the edit w open. Very weird. A couple of days ago i tried to reinstall yosemite on another disk and pthd 11.3.2 and all works fine and i was able to run the session at 64 samples with no cpu spikes

[TOM@METRO]

Interesting. And this is all with HDX, right?

[YYR123]

A couple of days ago i tried to reinstall yosemite on another disk and pthd 11.3.2 and all works fine and i was able to run the session at 64 samples with no cpu spikes


That is the stake through the heart

Sometimes newer is not better.

[innesireinar]

Interesting. And this is all with HDX, right?

Yes, sure my mac is very old (2010) and maybe its graphic performance could conflict with the pt processing, btw I don' t understand why it works flawless by switching to internal out

[innesireinar]

That is the stake through the heart

Sometimes newer is not better.

Once found a stable rig we should stop upgrading and updating. At least for a while

[Emi]

Once found a stable rig we should stop upgrading and updating. At least for a while

This is so true, but everytime there is an update I just have to hit that button. It's like the "don't push the red button"....:o

[innesireinar]

I found that having two separate partitions is the right way to go. One for working, the other for testing new releases

[musicman691]

I found that having two separate partitions is the right way to go. One for working, the other for testing new releases
Add to that having an external non-connected backup. All this also helps recovering from pilot error :o

[innesireinar]

Add to that having an external non-connected backup. All this also helps recovering from pilot error :o

Sure. But now pilots do ILS approaching

[TOM@METRO]

I always keep at least one offline backup of everything. I thought everybody did.

[TOM@METRO]

I found that having two separate partitions is the right way to go. One for working, the other for testing new releases

I do this as well. It makes it easy to compare when questions arise.