crazy time

i was using maschine 2 vst in ableton. i deleted a pattern. the maschine time went crazy and now i can't get the maschine sequencer to run. it appears to be stuck. i tried saving the maschine project to disk and reloading it in a new ableton project but the crazy time gets loaded with the project. oh well. i didn't have too much time invested in the project. i just figured that i would post a pic because i have not seen this before.

 

Have you tried loading it into standalone Maschine?

 

yep. it loads into stand alone just fine in standalone maschine. i saved the project into a new project file but the new project file had the same problem when i loaded it into a maschine vst. very strange. anyways the project only had one pattern so i was able to recreate it within a few minutes.

after that i spent some time trying to make the problem happen again but i was unable to do so.

 

Very weird.

 

So it works in Maschine standalone.
Does Ableton eventually crash? If so what does the windows event viewer say about the crash?

Have you tried it in another DAW such as Reaper?
Do the projects that crash contain any specific third party plugins?
Can you get any projects to crash that have been created with the latest version of Maschine?
I have Sonar X3, if you can create a simple pattern that crashes (or tell me how to do it) you could email the Maschine project to me and I could test it.

 

Well that's me told. Have a nice day.

 

jpeg, if you are getting crashes please send logs to tech report and try to narrow down what you are doing when it crashes. See if it is related to a specific plug-in you are running and list your system specs. You can create a topic about it in the tech area but this thread was not about crashes so I deleted a few post.

 

Standalone won't load for me ever since I updated

 

Oh forget it.
If stand alone will not load, try going into the Library folder and double clicking a project to launch Maschine. You can also do this with one of your own projects that you know is good. Usually if it won't launch it is due to a curupt default project or a plug-in crashing on scan. If you get it up then remove the default project in preferences.

@Spazoo, did you happen to drag on the time sig or time display while Ableton was in play? I think I saw this before and that is what caused it but I can't be sure.

@jpeg, could it be that you are running out of RAM resources? Try saving your projects more often to free kits and instruments from memory. M2 seems to not be flushing previously loaded stuff from memory until you save or restart. If you are getting frequent crashes I would suspect that or a plug-in that you are using not playing well with Maschine. Beyond that it should not be crashing very often at all if you are on 2.06

 

no, i was in the group's pattern browser and i clicked on the 'x' glyph to delete a pattern that i no longer wanted. i'm not sure if the pattern that i deleted was currently being used by any scenes.

i don't remember if the ableton sequencer was running.

i will do some more experimenting and try to reproduce the problem.

 

ok i found another way to reproduce the problem.

by the way... i am not at home so i am not using the maschine controller. i am doing all of this with the maschine application UI.

1) create an instance of the maschine vst inside ableton
2) create a pattern that is 4 bars long and adjust the loop range so bars 3 and 4 of the pattern are looping
3) click the mouse on the pattern length (4:0:0) and drag down in order to change the pattern length to 1:0:0

wait a few seconds and you should see the error.

 

Not reproducible in Sonar/Windows 7 64 bit/Maschine 2.0.6 over to an Ableton user.

 

Works fine for me in Live 9.1 (PC, Win 7, 64 bit). No matter how much I try to confuse it the time stays good.

However, when testing I did discover another thing I don't like about 2.0. When duplicating a scene you can have blank pads but these are not reflected in the software. So if you have 8 scenes on pads 1 to 8 and duplicate scene 1 to pad 12, in the arrange view you will see 9 consecutive scenes (no blank scenes representing pads 9,10 and 11).

 

thought it said "crazy train" at first..

... i had effects not work when saved in a project hosted in live.. the only way i could fix it was to save the groups and effects presets and delete the project and built it again in standalone...

 

here is a link to a video that demonstrates the problem:

https://vimeo.com/87319904

additional info...

i am using os x 10.9.1 and maschine 2.0.6 and ableton live 9.1.1 32-bit.

after the time gets all crazy the maschine sequencer will not run.

i am able to reproduce the problem when using the maschine 2 vst however i have not been able to reproduce the problem using maschine in stand-alone mode.

after the problem occurs... if i save the maschine project to a file, then restart ableton live, then load a maschine vst and then reload the maschine project file, the problem will be also be loaded and the maschine sequencer will not run.

although i am causing the problem by changing a pattern length, i originally experienced this problem when i deleted a pattern by clicking on the 'x' glyph in one of the pattern slots within the pattern manager.

 

The steps in the video are different to the steps stated earlier, still cannot reproduce in Sonar X3D and Maschine 2.0.6.

 

Does it still happen if you disable the loop in Live?

 

I think we get that you cant replicate it in sonar lol

Shame the daw feels like running through mud

 

yes it still happens. i tried it just now with the ableton looping disabled and i got the bug.

 

I just confirmed two different steps given to us I don't think there's anything wrong or overboard with that,
If another ableton user can confirm it then it would appear to be ableton issue wouldn't it? That would be useful information right? You really want to see how this works with as many different DAW's as possible.
I know you guys really want a mud slinging match for some reason but please give us a break, don't you want to get down to the bottom of this issue?

I'm doing my best to ignore the mud being slung considering I'm the one who seems to have resurrected this thread from the grave and kicked in the nuts for doing so.. So let's just be polite... (which will be a lot easier if what Spazoo says is indeed true, I don't believe him though people always want to know what is being said about them... ).