Muse Research

richwhite9 · Post by **richwhite9** » Wed Nov 04, 2009 8:44 pm

projektio wrote:Bump

The bumps are getting annoying and accomplish nothing.

SurfacePatterns · Post by **SurfacePatterns** » Wed Nov 04, 2009 9:10 pm

richwhite9 wrote:The bumps are getting annoying and accomplish nothing.

A bump does two things:

1.) It moves a topic up to the top of the topic list. This brings attention to the topic.
2.) It reminds Muse Research that we haven't forgotten about the topic in question, and that we expect answers to the question(s) we've asked in that particular topic.

You might find the bumps annoying, but I guarantee that there are many of us that are much more annoyed with Muse Research at this point.

johnrule · Post by **johnrule** » Thu Nov 05, 2009 2:10 pm

'wine' is not an emulated or interpreted environment. It's a compatibility layer that takes care of system calls, loading DLLs, etc.

The compatibility layer is the interpretive software system that allows you to run a native Windows widget in a native manner within Linux. It is not an emulator in a literal sense like running a Commodore 64 within your current OS, but the abstraction means a software process that is required for functionality.

Still, we're not supposed to use that dirty word since 'WINE' stands for "Wine is NOT an Emulator".

'wine' takes care of loading the data from DLLs and .exe files, and loads compatible libraries for the code. So, in the case where Windows code being run under 'wine' isn't actually making calls to external libraries, it runs just the same (and just as fast!) as it does under Windows.

Hence the "interpretation"...and overhead in my opinion. Still, it works very well. I run many things at almost the same comparable responsiveness on Windows. The Real-time kernel for Linux is absolutely required though, and this is all 32 bit I am referring to.

EnergyXT does run natively under Linux; however, last I checked, it only loads VSTs that are also Linux-native.

I run the Windows version of Energy XT using Wine under Linux in order to use the VST capabilities, but Energy XT does come in a native Linux flavor that can be used with Jack to 'wire' yourself into whatever you like.

Back to the topic of this thread however...

*Bump*

A statement from Muse would be appreciated. Just because Receptor 1 owners do not have current hardware does not mean we are not customers. And I would suggest that if you want us to remain potential customers at all you should say something.

JR

projektio · Post by **projektio** » Thu Nov 05, 2009 8:13 pm

richwhite9 wrote:The bumps are getting annoying and accomplish nothing.

What's annoying is being left in the dark about a product you believed in enough to purchase. What's annoying is getting the impression there are more Receptor 1 users than Receptor 2, but feeling like even though you went out of your way to upgrade from Rev C to Pro Jr, that the product will no longer be supported, so spending the extra $1,000 was a waste.

If Muse cannot be made aware of potentially alienating more than half of their existing "fan base" by keeping a relevant topic toward the top of the list, then why bother having a Receptor Discussion and Support forum??

projektio

gregh1 · Post by **gregh1** » Thu Nov 05, 2009 8:45 pm

I've talked about this with Chris Halaby, and the folks at Muse are quite concerned about providing the right solution (or solutions, maybe?) for their user base. Yes, it does seem that they tend to stay a bit quiet until they have the "perfect answer", but (in this case, I think) the perfect answer seems to be tougher to arrive at. But they really want to sort this out. My understanding is that Chris is deciding on a strategy, which he'll shortly talk about. I'll let him know that I have posted this here.

projektio · Post by **projektio** » Thu Nov 05, 2009 10:41 pm

gregh1 wrote:I've talked about this with Chris Halaby, and the folks at Muse are quite concerned about providing the right solution (or solutions, maybe?) for their user base. Yes, it does seem that they tend to stay a bit quiet until they have the "perfect answer", but (in this case, I think) the perfect answer seems to be tougher to arrive at. But they really want to sort this out. My understanding is that Chris is deciding on a strategy, which he'll shortly talk about. I'll let him know that I have posted this here.

Thank you!

projektio

gregh1 · Post by **gregh1** » Fri Nov 06, 2009 12:40 am

You're welcome - and, by the way, I'm one of those Receptor 1 users, too...

SurfacePatterns · Post by **SurfacePatterns** » Fri Nov 06, 2009 2:32 am

johnrule wrote:
'wine' is not an emulated or interpreted environment. It's a compatibility layer that takes care of system calls, loading DLLs, etc.
The compatibility layer is the interpretive software system that allows you to run a native Windows widget in a native manner within Linux. It is not an emulator in a literal sense like running a Commodore 64 within your current OS, but the abstraction means a software process that is required for functionality.

Still, we're not supposed to use that dirty word since 'WINE' stands for "Wine is NOT an Emulator".

I think we have the same view on what 'wine' does, while the language we're using is being interpreted differently by each of us. I have (overly?) strict ideas about what "interpreters" and "emulators" are, probably due to my experience with emulation (bits and pieces of my old Motorola 6802 emulation code have been borrowed and used in game emulators).

'wine' takes care of loading the data from DLLs and .exe files, and loads compatible libraries for the code. So, in the case where Windows code being run under 'wine' isn't actually making calls to external libraries, it runs just the same (and just as fast!) as it does under Windows.
Hence the "interpretation"...and overhead in my opinion. Still, it works very well. I run many things at almost the same comparable responsiveness on Windows. The Real-time kernel for Linux is absolutely required though, and this is all 32 bit I am referring to.

Yes, there's definitely overhead, but it's my understanding that there is also overhead in Microsoft's own OS compatibility layers (running an application under WinXP in Win98 compatibility mode, for instance). I have no experience with this myself, so I could be wrong.

EnergyXT does run natively under Linux; however, last I checked, it only loads VSTs that are also Linux-native.
I run the Windows version of Energy XT using Wine under Linux in order to use the VST capabilities, but Energy XT does come in a native Linux flavor that can be used with Jack to 'wire' yourself into whatever you like.

I haven't tried running the Windows version of Energy XT under 'wine'. It's probably way too OT to ask you about your experience with it.

A statement from Muse would be appreciated. Just because Receptor 1 owners do not have current hardware does not mean we are not customers. And I would suggest that if you want us to remain potential customers at all you should say something.

+1.

SurfacePatterns · Post by **SurfacePatterns** » Mon Nov 09, 2009 10:30 pm

*Bump*

gregh1 · Post by **gregh1** » Mon Nov 09, 2009 10:49 pm

I believe that Muse is working on one of the upgrade options - it's a technical solution, and they are trying to determine if it will work properly before they sign off on it.

SurfacePatterns · Post by **SurfacePatterns** » Mon Nov 09, 2009 10:55 pm

gregh1 wrote:I believe that Muse is working on one of the upgrade options - it's a technical solution, and they are trying to determine if it will work properly before they sign off on it.

How do you know this? Can you be more specific?

I'm glad to hear they're working on it.

gregh1 · Post by **gregh1** » Mon Nov 09, 2009 11:21 pm

It was from conversation with Chris Halaby. I'm a Canadian Receptor dealer, not a representative of Muse, so it's not my place to give specifics. But they are, indeed, working on the upgrade options.

SurfacePatterns · Post by **SurfacePatterns** » Tue Dec 01, 2009 8:31 pm

gregh1 wrote:My understanding is that Chris is deciding on a strategy, which he'll shortly talk about.

Any month now ...

gregh1 · Post by **gregh1** » Tue Dec 01, 2009 9:07 pm

Yes... I believe that Chris is meeting with his team about this.

SurfacePatterns · Post by **SurfacePatterns** » Fri Dec 11, 2009 10:33 pm

gregh1 wrote:Yes... I believe that Chris is meeting with his team about this.

You know, Greg, you've been making excuses for Muse Research for a while now, and I still see no sign that Muse Research intends to fulfill its promise to make the 1.8 OS available to Rev. C Receptor users. I'm not going to listen to you any more. No offense.

I want Muse Research to stop pussyfooting around and to tell us what's going on with this issue. The technical folks that post on the Receptor forum have offered Muse one or more solutions to each problem that Muse has brought up regarding getting the 1.8 OS on Rev. C Receptors; yet, AFAICT, there has been no progress on this issue.

I'm tired of waiting for Muse Research to get its act together. Muse Research has had more than enough time to take care of this issue.

Muse Research

KVR Audio

Version 1.8 System Software Update for Receptor 1 users ?