v1.7 bug reports

KASZ247 wrote:
I think I know your problem I had the same one.You might have to re organize your project programs and tracks..It makes copies which causes the spike...Here this video explains it all.. viewtopic.php?p=1657650#p1657650

Thanks. Looks like a very time consuming process and unnecessary. I would try it, but I don't even have the ability to. Unfortunately the program just crashes when I attempt to load projects. I think I have too many track inserts and sequences so it creates all these programs and it cannot handle it. That is stupid as I rarely would have any lag and CPU bar would always be low in 1.6. Now the program just crashes. Wack.

I pretty much only work on old beats and never start new ones and obviously this update is only targeted at making new beats so I'm out of luck. I'll just have to go back to 1.6. I do not see 1.7.1 fixing this problem. The program just crashes when I try to load projects. This sucks.

Plug In scan causes a crash every time when scanning my main vst plug in folder. Every single time.

Nubian Mindz wrote:Plug In scan causes a crash every time when scanning my main vst plug in folder. Every single time.

In 64 bit mode on win 7

Nubian Mindz wrote:Plug In scan causes a crash every time when scanning my main vst plug in folder. Every single time.

You need to go through your plugs to determine which one is causing the crash.

When you clear a sequence it also clears the programs as well. Which it shouldn't. Strangely though, when you do clear the sequence, the programs are only gone from your hardware but they are still available in the software you just can't access them from the hardware. Pretty wack.

EDIT: You can see the programs in the software but you can't actually access them....

Screenshot. Notice that you can't assign the program to a track anymore even though it exists in the software.



EDIT: I can assign the program to track 2. I can't assign it to track 1...bleh...

pk1 wrote:and i can't delete program 001 if you do it reappears as last track.

ditto...literally just ran into this...

MaZe wrote:When you clear a sequence it also clears the programs as well. Which it shouldn't. Strangely though, when you do clear the sequence, the programs are only gone from your hardware but they are still available in the software you just can't access them from the hardware. Pretty wack.

EDIT: You can see the programs in the software but you can't actually access them....

Was just about to post another issue I ran into about clearing sequences and saw this....for the one you just mentioned if you scroll the Type field you can then select the programs in the list again in both hardware and software--your track 1 type in the screenshot is set to 'plug in' so it won't show Program 001.

I think what is happening is that whatever the Type is set to on the track you are on when you go to clear the seq, it is then set for all tracks after the seq is cleared.

example of what I am seeing:
1. start with a new seq
2. set track 1 to drum
3. set track 2 to plug in (go back to trck 1 check ts type, it should be drum)
4. clear the seq while on track 2
5. track 1 type (and all tracks) will now be plugin
6. set track 1 to drum
7. set track 2 to plugin
8, go back to track 1
9. clear the seq.
10. track 1 will still be drum amd all other tracks will be drum

so probably you may have started the clear while on a track set as plugin, went back to track 1 which was previously set to drum, but is was now set to plugin and now the programs do not appear in the list because the program type selection changed from what you expected it to be.

OTHER SEQ clear bug or maybe not:
when clearing sequences that have tracks with automation, the sequence will be cleared, but the automation will still remain and be active. I cleared a sequence I was just messing around with automation, then started to create new tracks in the cleared sequence and noticed the leds on a few q-links were still increasing and decreasing. Not usre if this ia a bug or as designed since I noticed the programmed automation seemed to stay with the program.....

^In the screenshot it definitely looks that way but I tried that too. For some reason it still didn't want to let me assign it to track 1.

MaZe wrote:^In the screenshot it definitely looks that way but I tried that too. For some reason it still didn't want to let me assign it to track 1.

Oh you're saying you switched the program type in track 1 to drum and it still would not show Program 001 in the drop down and allow you to select? I misunderstood then...yeah that would be a problem....

DaizM wrote:

MaZe wrote:^In the screenshot it definitely looks that way but I tried that too. For some reason it still didn't want to let me assign it to track 1.

Oh you're saying you switched the program type in track 1 to drum and it still would not show Program 001 in the drop down and allow you to select? I misunderstood then...yeah that would be a problem....

Yeah. It was strange but I've noticed a lot of weird behavior when you "clear" or "delete" things so I'm not surprised by the bug that you found. It seems the software, or hardware, or both, get a little confused when you clear/delete. I deleted a program/samples recently from the software and you could still see them on the hardware and then the the screen on the hardware started flipping out a bit when I went into the prog edit screen to the point I had to turn the hardware off. I'm assuming there was some miscommunication between the software and hardware.

Did anyone mentioned a strange behaviour with names of samples dissapearing and apearing from pads in the software?
I'm on mac. Just updated to mavs 10.9.4 a week ago on one computer, the other one is not updated but I don't have it in my possesion now to try, my bro has it,no other problems so far.

Win 8.1, some problems with the mpc software UI - Trying to adjust metronome volume and various other rotary controls by clicking and dragging is extremely erratic or doesn't work at all, often reverting back to 0 as soon as the mouse click is released, if it responds that is. Using the mouse wheel works 100% of the time. Weird.

Also when dragging and dropping audio files from external folders/programs into the mpc software the pads highlight as though i was mousing over them, while my mouse is still hovering over the browser on the left of the window. Incorrectly reading mouse coordinates, or something.

Finally the shortcuts '[' and ']' work for me to scroll between/change focused track, but alt + shift + '{' and '}' do not work at all (should change the current sequence)

fdodds wrote:Win 8.1, some problems with the mpc software UI - Trying to adjust metronome volume and various other rotary controls by clicking and dragging is extremely erratic or doesn't work at all, often reverting back to 0 as soon as the mouse click is released, if it responds that is. Using the mouse wheel works 100% of the time. Weird.

Also when dragging and dropping audio files from external folders/programs into the mpc software the pads highlight as though i was mousing over them, while my mouse is still hovering over the browser on the left of the window. Incorrectly reading mouse coordinates, or something.

Finally the shortcuts '[' and ']' work for me to scroll between/change focused track, but alt + shift + '{' and '}' do not work at all (should change the current sequence)

Can confirm on both Win 7 and 8.1

THE ADVERSARY wrote:

Nubian Mindz wrote:Plug In scan causes a crash every time when scanning my main vst plug in folder. Every single time.

You need to go through your plugs to determine which one is causing the crash.

It's quite tough as I'm not getting any list or details. Once I hit scan on any of my vst folders a couple seconds in it will crash and I have to close the software via task manager.

This is on Win 7.

On Win 8.1 I'm able to get a detailed list and pin point everything that's causing issues.

Nubian Mindz wrote:

THE ADVERSARY wrote:

Nubian Mindz wrote:Plug In scan causes a crash every time when scanning my main vst plug in folder. Every single time.

You need to go through your plugs to determine which one is causing the crash.

It's quite tough as I'm not getting any list or details. Once I hit scan on any of my vst folders a couple seconds in it will crash and I have to close the software via task manager.

This is on Win 7.

On Win 8.1 I'm able to get a detailed list and pin point everything that's causing issues.

You just move them to a different folder then put them back one by one and scan.
The culprit will eventually show.

This is something you always had to do with Pro Tools over the years to find a corrupt or incompatible plug in.