FW 2.11.9 released

B-Wise wrote:The SE thinks it's too good for an update

Collector's item. Keep it stock.

But for real, OP, we're just messing around.

I always do the updates with a USB drive. Sometimes it takes more than one try. Any other method always makes my Live go crazy.

Avasopht wrote:I'll put my money on streaming coming when it's ready.

But the MPC is pretty slow at loading from SD and SSD, so maybe it's just not appropriate for real-time streaming for instrument patches.

Or maybe this is all just a minor config issue and they just need their Linux distro to load the right driver or something.

It thrashes disks. google "disk thrashing" also sdd has a limited amount of writes like usb or ssd then they start to bit rot. i assume knowing that everyone uses ssd is a factor on whether or not they add it or not but i've been known to be wrong.

Ultros wrote:It thrashes disks. google "disk thrashing" also sdd has a limited amount of writes like usb or ssd then they start to bit rot. i assume knowing that everyone uses ssd is a factor on whether or not they add it or not but i've been known to be wrong.

Is everybody playing like 5 minute long files? Or are you using a bunch of short as shit one shots like drum hits? Those tiny ass 100k files are exactly what needs to be loaded into RAM. The reason things like Gigasampler and Kontakt 'invented' disk streaming was to load HUGE multilayered libraries. Not a bunch of chopped up drum breaks and bass notes.

Constantly reading a 16 piece drum kit every time a note triggers it, is going to not only trash your SSD a lot quicker, you might even slow the MPC down to the point where 'disk streaming' makes it worse than before.

And there are slices, which are kind of like files inside files. Every slice is played like it was its own WAV file. But the number of files seems to slow down loading more than the number of slices. Tutor has utilized this by packing many samples as slices in the same WAV file, speeding up loading. The same can be found in at least some of Ableton's sound libraries, where a whole category, instrument or articulation sample set has been concatenated together in a single file. Though I don't know the rationale behind that in Ableton's case.

Adding disk streaming for all cases is not trivial by any means, but it should be possible to automatically classify samples as suitable or unsuitable for streaming. A lot can be figured our by looking at what kind of a program is using the sample. At least samples used by audio tracks/clips could be streamed by default. For other kinds of programs, it depends. Keygroups? Probably yes. Drum programs? Probably not.

Naturally disk streaming needs a preload buffer setting. How much of the beginning is preloaded to RAM. Now I don't see any such setting in the Force software, it's just either yes or no for each sample.

Ultros wrote:

Avasopht wrote:I'll put my money on streaming coming when it's ready.

But the MPC is pretty slow at loading from SD and SSD, so maybe it's just not appropriate for real-time streaming for instrument patches.

Or maybe this is all just a minor config issue and they just need their Linux distro to load the right driver or something.

It thrashes disks. google "disk thrashing" also sdd has a limited amount of writes like usb or ssd then they start to bit rot. i assume knowing that everyone uses ssd is a factor on whether or not they add it or not but i've been known to be wrong.

SSD streaming is fine. It doesn't involve writing (and SSDs are recommended for sample library streaming).

As for thrashing, this all comes down to the memory management policies. If all of your samples do fit into RAM, the caching policy would ensure they're not loaded again (eliminating the thrashing issue).

Is anyone else having an issue with 2.11.9 FW update ? It’s making my MPC One super buggy

GSTizzle wrote:Is anyone else having an issue with 2.11.9 FW update ? It’s making my MPC One super buggy

Mine works fine after the update, but I must be using it at 10% capacity (drums, a bass track and sometimes a synth)...

GSTizzle wrote:Is anyone else having an issue with 2.11.9 FW update ? It’s making my MPC One super buggy

Having a lot of freezes, most noticeably at power up once in the main screen. Buttons not responding for a 5 to 10 seconds, then back to normal. Had this with some of the previous versions, went away with others, now it's back whit this one.

GSTizzle wrote:Is anyone else having an issue with 2.11.9 FW update ? It’s making my MPC One super buggy

HanHuman wrote:Having a lot of freezes, most noticeably at power up once in the main screen. Buttons not responding for a 5 to 10 seconds, then back to normal. Had this with some of the previous versions, went away with others, now it's back whit this one.

Rock solid on my Live II. Maybe a silly question, but did the both of you do a system preferences reset after updating your firmware?

EnochLight wrote:Rock solid on my Live II. Maybe a silly question, but did the both of you do a system preferences reset after updating your firmware?

No, is it something that should be done with every update? I'd rather not have to do that and set everything up again each time but if this is required…

@Lampdog Makes sense, never did a preset reset even once I think, so that won't hurt. Thx!

EnochLight wrote:

GSTizzle wrote:Is anyone else having an issue with 2.11.9 FW update ? It’s making my MPC One super buggy

HanHuman wrote:Having a lot of freezes, most noticeably at power up once in the main screen. Buttons not responding for a 5 to 10 seconds, then back to normal. Had this with some of the previous versions, went away with others, now it's back whit this one.

Rock solid on my Live II. Maybe a silly question, but did the both of you do a system preferences reset after updating your firmware?

Wow I’ve never done that. Weird that tech support never suggested that . He suggested I downgraded to 2.11.8 and let them know if it’s still buggy. Which technically it isn’t but my Q-link feature seems to be off.

B-Wise wrote:

HouseWithoutMouse wrote:If it doesn't have any meaning to you, you can ignore it. No, actually it was for EnochLight, but your post seemed to about the same thing, so I thought it's continuing the line of thought. I wanted to show details about how the Force's disk streaming works, because I think most MPC users don't know about selecting memory/streaming one-by-one for every sample.

I know I can ignore it but this is a public forum/thread so use the quote function or provide context to your post like you did in the post that I'm quoting, then I wouldn't have had to asks, who are you replying to. You do know people can't read your mind or know your intentions?

Ignoring something I don't understand is not my nature. A wise thing to do when you don't know is to ask questions. Thanks for the clarification. Before you catch an attitude see the role you played in what & or how you say something could be misunderstood by non-mind readers.

But to your point about selecting each sample 1by1, doesn't that suck. like wouldn't it be better to be able to pick the destination in the sample menu first or after you sample something?
Or even set a file size min so if a sample is that size or over it automatically gets streamed from disk?
Or have a way to batch select samples, then pick stream to disk or RAM.
Do you have any suggestions on how it could implemented better?

I have a suggestion- get off your high horse because dude- you're a nobody.
Your reply was assholish, making you an a-s-s-hole
And I'll bet my studio that your music is wack as fcuk!

Has anyone made beats this weekend i have not because of family engagements.. that being said why are we fighting who cares .. to be honest I have not powered up my X after updating but with the bugs I just move on because what we have is better than I have had in the last 30 years ..