2018.7 So Far...

[krabbencutter]

Originally Posted by Philthy

Well there's terrible news for a company shedding market share

You can expect many more companies to start dropping official Win7 support within the next 16 months. The extended support for Win7 ends in January 2020 and there will be no more security or bugfix updates by then. That doesn't mean Windows 7 or any software will stop working and many people will decide to keep running Win7 on an offline machine. But from a business perspective it will not be feasible to support an operating system that has officially reached EOL.

See https://support.microsoft.com/en-us/...cle-fact-sheet

[xmission]

Originally Posted by B.J.

Win7 is not supported at 2018.7

Regards
B.J.

Yep. I found out the hard way Friday, when I tried to clear the problems by doing a fresh install. It wouldn't let me install 2018.*

I had to go back and incrementally install from 12.1 to get running again.

It would have been better for me to have had the window pop up when installing over an older version, and I wouldn't have been in a jam.

[64GTOBOY]

I have three machines running 18.7 on Win7 with no issues. It's not "supported" basically means they wont test it. Doesn't mean it doesn't work.

[TNM]

Originally Posted by Emi

I repeat, @ 192 kHz sample rate. I could run at 128 (min. @ 192 kHz) but was unstable. 256 is stable @ 192 kHz, but for safety I left it at 512. Did I say @ 192 khz?!?

Divide to 4 the buffer size for 48khz behavior.

I repeat, that is completely normal and expected.

yes, i can read. 192.

256 is what's stable at 192 on my old crappy macs in sierra.

But I do my tests with 64 channels armed, each with effects.

[xrekcor]

hmmmm have to say I am still getting the buffer error, it seems to only happen after starting up PT and after loading a session I might get it just after the first run through, prolly about 2-3 times over the last week of several hours per day running PT. I have.... A) don't do anything - it hasn't appeared again even after hours of continuous working B) did try a testing lowering buffer after receiving the error prompt - still couldn't make the error reappear.

so don't know if its a biggy but hasn't seemed to have caused any grief here so not for me.

another weirder thing is and sorry this is slightly off topic..... a lil story I got hold an old Roland GP8 brought from the US a month or so back what a great lil unit btw, so once it got here I had it changed to Aussie power using a power board from another Aussie version. well the dang thing has been rebooting itself every few minutes to an hour or so (pain in da *ss dang thing) I have been going over it checking for dry solder joints (mine mostly) nothing seems to have fully fixed it until..... now I know us audio types can be very interesting individuals but I'm not too loopy to believe there is a connection. But!!!! ever since I updated to 2018.7 the ol GP8 has been running like a well oiled 1980's machine..... so just incase thanks for the fix Avid!!!!

ok back to the real world...

[amagras]

Originally Posted by xrekcor

hmmmm have to say I am still getting the buffer error, it seems to only happen after starting up PT and after loading a session I might get it just after the first run through, prolly about 2-3 times over the last week of several hours per day running PT. I have.... A) don't do anything - it hasn't appeared again even after hours of continuous working B) did try a testing lowering buffer after receiving the error prompt - still couldn't make the error reappear.

That happens to me when I try to run playback too quickly after the session has finished opening. Wait a few seconds before pressing space bar and see if that helps.

[xrekcor]

Originally Posted by amagras

That happens to me when I try to run playback too quickly after the session has finished opening. Wait a few seconds before pressing space bar and see if that helps.

could be, ill take note of that when loading a session and see if there is any difference. for me PT throws the prompt a few seconds into the second play through and then doesn't throw it again even try to force it a lil. do you get it straight off or during the next play through?

thanks for your input. ill test over the next week and post a reply.

[amagras]

Maybe is one library that's still loading, that happened to me with MiniGrand, try deactivating one plugin at the time.

[xrekcor]

Originally Posted by amagras

Maybe is one library that's still loading, that happened to me with MiniGrand, try deactivating one plugin at the time.

the reality is its only happened 2-3 times since the update to 2018.7 and certainly over perhaps hundreds of cycles of a session(s) its not really an issue for me just that it popped up 2-3 times and thought I would mention it.

[daeron80]

I'm encountering several bugs when working with MIDI tracks. The worst one is when a track is set to Clips, the Trim tool causes clips to shift down and to the right, making it impossible to see where you're trimming it to. Workaround is to select the point you want to trim to and use the keyboard shortcuts. Not a complete workflow killer. There are some other oddities that similarly have more-or-less acceptable workarounds. Overall, though, I'm loving the speed and stability. Retroactive is a godsend.