OS v1.01

Well, but it seems that OS 1.01 was released almost a year ago.

Artemiy wrote: "Well, but it seems that OS 1.01 was released almost a year ago"

Ya it was on the Japanese site. However they quite literally just got it posted on rolandus. (6-30-09)
I know there were some people waiting for that to happen, including myself.

They still don't tell you what it does and it doesn't seem to be anything major.
There are poor Japanese translations out there and it seems to fix audio phrase drifting.

Peace

Know1

Are you sure that "audio phrase drifting" is not a feature? Because it sounds kinda cool

Only 3 meg?

Either it just patches part of the OS, or the MV OS really is that small.

Cubase 3.0 on the Atari ST was less than 1 Meg, so I guess it's possible.

When I worked as a Linux administrator, I could use several tricks to squeeze a stripped-down kernel, shell and some tools onto about 950 KB of space. So 3 MB is actually quite a lot, especially if it's just the operating system itself, not containing any samples, demo songs or wallpapers.

Yup.
As I indicated, 3meg would have been a really big aplication on an Atari ST, and you could do a lot on an Atari ST. And when the MV starts up it appears to go through a process of "extracting" the OS, which suggests that it is stored a compressed file.

But they got the update instructions wrong. They tell you to reboot while holding the Disk/USB and Sequence buttons. The MV8800 doesn't have a Sequence button. The 8000 has, but not the 8800. If you hold the Song button instead, it works.

Oh they definitely got the instructions wrong. I tried to let them know and they couldn't figure out what was wrong with them.

They got some smart ones werkin fer em. The fancy book readin type.


Peace

Know1

I was so incensed at the illiteracy of the tech support for the MV-8800 at one point (I don't remember the details now) that I actually went to the trouble of finding the Japanese site and contacting some people high up in Roland Japan about the terrible tech support their hire in the US was providing.

This doesn't surprise me. Could it take what, 3 seconds to actually try out the instructions ONCE before shipping this off to the web? How hard is that?

I think Mike programs some great drumbeats, but he's got to learn something else than a "whatever, man" attitude towards this stuff -- if it's him. Or maybe he just does drum programming for the MV series, who knows, and they have some HS intern at $2/hr doing the actual tech support for 'em.

Sigh.

Mike Acosta is not working for Roland anymore, is he? There has been a message about that on the mv-nation forums

edit: here it is
http://mvnation.com/phpBB/viewtopic.php?f=22&t=13027
now find someone else to blame :-p

L56 Wrote: "Mike Acosta is not working for Roland anymore, is he? There has been a message about that on the mv-nation forums."


I think there was a post on here about it too. I'm not sure where it is at though.
Also I'm fairly sure that he wouldn't be answering tech support questions.


Peace

Know1

Aww, that's too bad -- Mike was one of the few guys there who took the chance of reaching out to the user community; and yeah, I'd be surprised if it were him responsible for any tech support issues (my other one had nothing to do with the actual tech support, just a refusal of the LA team to recognize an absolutely glaring file bug in the MV-8800 awhile ago, one that would risk less astute users trashing their HD -- fortunately I caught it before it became an issue for me. I eagerly brought it to their attention but got absolutely no acknowledgment of the existence of the issue; would've understood if it was a no-fix, can't-fix, will-fix later, but to completely refuse to see something totally obvious, that was what irked me at the time, as I vaguely recall. So, since I really like the MV-8800, I made it my mission to try to bring it to _someone's_ attention in Roland, if it had to be in Japan.... so be it!).

Enough on all that tho.

Did the bug have to do with previewing patches and hitting quick edit?

Nope, searched my email for you and here it is:

"MV-8800 freezes when using Mastering-Audio File Utility-Delete in an area where there is no WAV or AIFF file (example: CDIMAGE folder).
Cannot use. Cannot shutdown. Cannot park hard disk head."

I had just gotten my MV-8800 and gone thru basically testing making a CD to check on the reliability of a particular type of CD I'd planned to use with the MV-8800, then blithely thought I could delete the contents and then CDIMAGE folder when I was done.

It was a minor annoyance, but something I figured could easily be resolved in an update, or at least confirmed by Roland, even with just a "Can't Execute" warning (as it should do, based on the file management principles outlined in the manual) in the OS applied to attempting this action.

Here are more specifics from another email:

a) Go to Mastering/Audio File Utility
b) Use Audio File Utility/Delete inside the CDIMAGE folder, to attempt to delete one of the two .BIN files in there (my original error, that I was reporting).
c) The MV-8800 will lock up hard when you use Mastering/Audio File Utility/Delete on the, I believe it's called, CDDATA.BIN file inside the CDIMAGE folder. No other controls, including shutdown, will work at this
point, and the MV-8800 has to be turned off and restarted to get it unfrozen.
d) Once turned off and turned back on, everything is fine -- I haven't had any problems with corrupt files that are evident in any way yet.
e) If I try to use DISK/USB/File Utility to delete the same file, I get the proper "System folder cannot be deleted" error message.
f) So at least as far as I can tell, the issue is that inadvertently using Mastering/Audio File Utility to try to delete the CDDA.BIN file inside the CDIMAGE folder will cause a lockup.

My OCD annoyance was that CDDA.BIN was sitting there on the hard drive taking up space after I was done with it, with no way of getting rid of it.

After a few rounds of email, they did finally acknowledge the problem. Actually, they were very polite on their end; it was just frustrating trying to report this as accurately as possible and at first, just getting a part of the manual quoted back to me in response.

Oh well, old news I hope and maybe fixed with the OS update? The exchange about this above was over two years ago, in any event. Generally, unlike the internet FOO on this issue, I've found Roland support very professional and responsive, which is why it was a bit of a shock not to get a more explicit response to this attempt on my part to help.

Tempest in a teapot, really, but you asked.

Haven't checked to see if this is fixed in the update; I've just learned "not to do that" since then.