|
|
Post by sct on Jul 23, 2014 7:34:21 GMT -5
The suggestion to offer a Dirac-less model is pure genius! And, when you think about it, had they done so to begin with, we could have had this unit in our homes a year ago. Think of the cashflow that would have generated for Emo, maybe even making silliness like The Millionaire's Club completely unnecessary.
|
|
|
|
Post by andrecop on Jul 23, 2014 7:38:22 GMT -5
CMS
Well, i'm very interested about this thread.
My idea, and even a question to owners or to Emotiva, is to make the XMC-1 able to
manage a CMS for screen and projector, only via HDMI.
Many users have a valid projector without a CMS and, for a perfect calibration, the unique
solution is buy an external processor, like Lumagen Radiance and so on.
I don't know if now the XMC-1 is able to do this, with a firmware upgrade, thas is
the hardware on-board can manage this, or this will be the next step for the future XMC-2.
The CMS that i speak is without the add-on of a Radiance, but only the availibilty to work
with a Calman or X-rite via USB to manage the CMS.
Sorry for my english, i hope someone understand what i mean..
|
|
|
|
Post by indyscammer on Jul 23, 2014 7:49:45 GMT -5
Streaming of audio, including multi-channel audio, (FLAC, PCM, WAV) via the ethernet connection. (It's probably in the works, but since it's not here yet it still counts as a feature request)  +1, but don't forget Gapless, without it I consider it uselessly incomplete player. The best would be to implement DLNA renderer, so it can be controlled from any DLNA controller from smartphone or tablet. Considering ReplayGain if set in the file metadata would also be very nice to have, so fletcher munson loudness curves would be offsetted correctly according to the normalization level of the recording, and also there would be no volume jumps between files. Kept it all in one post as everything here is closely related. +1 for DLNA Renderer. |
|
bootman
Emo VIPs 
Typing useless posts on internet forums....
Posts: 9,358
|
Post by bootman on Jul 23, 2014 7:52:24 GMT -5
The suggestion to offer a Dirac-less model is pure genius! And, when you think about it, had they done so to begin with, we could have had this unit in our homes a year ago. Think of the cashflow that would have generated for Emo, maybe even making silliness like The Millionaire's Club completely unnecessary. I guess you didn't read the guidelines in the first post.  |
|
|
|
Post by sct on Jul 23, 2014 7:53:58 GMT -5
User settable timeouts for OSD menu display and info. screen displays. One of the things that really bugs me about the UMC-1 is the amount of time the little info screens are displayed, they obscure the picture for far too long.
Also, an "Apply to all channels" feature that would allow for quicker setup of the user configurable parameters. Once you have setup a given channel, you'd click a button that would push those settings to all channels. For those with speakers that are somewhat equidistant from the seating position and/or are of the same size and type, this would be of great benefit.
|
|
|
|
Post by ÈlTwo on Jul 23, 2014 8:18:30 GMT -5
I'd like to see a menu time out after a few minutes and let the info screen stay on screen a little longer... As sct said above, I'd modify this by making the timeouts user selectable. |
|
|
|
Post by geebo on Jul 23, 2014 8:20:32 GMT -5
I'd like to see a menu time out after a few minutes and let the info screen stay on screen a little longer... As sct said above, I'd modify this by making the timeouts user selectable. That would be nice. |
|
|
|
Post by merlinwerks on Jul 23, 2014 8:45:23 GMT -5
++1 for DLNA Renderer functionality...
|
|
Lonnie
Emo Staff 
admin
Pay no attention to the man behind the curtain
Posts: 6,999
|
Post by Lonnie on Jul 23, 2014 11:41:18 GMT -5
Add an open web service (API) on the XMC-1 in such a way that an external application can control the parameters of the XMC-1. Probably a REST style interface is the easiest way. A simple interface can open up the same functions as covered by the remote control. But it’ll be more interesting if it is also possible to read and set the parameters of the detailed configuration. An application that implements this interface can then offer to the user a screen with much more information than what is possible to show on the OSD. Changing parameters using the menu structures on the XMC-1 is doable, but imagine a screen with all relevant parameters, where it is easily to make changes using a normal keyboard and mouse: an overview of all settings on one single screen; or have the opportunity to switch between two or more different configurations by a single click. With a little bit more imagination you can see a kind of graphical representation of all the PEQ settings for all speakers. Anyway, all that is possible, but the first step is to have the ability to access the XMC-1 settings by an API. Instead of providing an interface to developers, Emotiva can also create their own application. But why not make it possible for the open source community to develop an application to interface with the XMC-1? The XMC-1 is based on Linux, it should be possible to implement such an interface. Also, the XMC-1 has already a network connector so no hardware change is necessary. I don’t know how the internal software structure is, so I can’t estimate the costs for implementing this web service. I’m not sure if and how much people are willing to pay, maybe $25 to enable this interface? This is a great suggestion and one that has been in the original design scope. The hardest part right now is fire walling specific areas and only allowing access to certain things like PEQs, System set up functions, etc. There are things that we can't allow access to due to licensing agreements and or the potential of a novice doing damage to other aspects of their system (i.e. blowing up their speakers). But we are working on this for the future. |
|
|
|
Post by petew on Jul 23, 2014 11:52:05 GMT -5
Add an open web service (API) on the XMC-1 in such a way that an external application can control the parameters of the XMC-1. Probably a REST style interface is the easiest way.... This is a great suggestion and one that has been in the original design scope. The hardest part right now is fire walling specific areas and only allowing access to certain things like PEQs, System set up functions, etc. There are things that we can't allow access to due to licensing agreements and or the potential of a novice doing damage to other aspects of their system (i.e. blowing up their speakers). But we are working on this for the future. Would it be possible to allow open source room correction to run on DSP 2? If I understand correctly, the DTS and Dolby code and other decoder code lives in DSP 1, then the data goes through the asynchronous sample rate converters to DSP2 for further processing (room correction). (Is PEQ implemented in DSP2 also?) I think it would be appropriate to unload Dirac code if a user wanted to load open source room correction code into DSP2. I also think it would be appropriate for Emotiva to have a heavy hand in the open source code since the potential for harm is great. |
|
|
|
Post by urwi on Jul 23, 2014 12:13:40 GMT -5
1) Dolby Atmos 2) RMS level-calibrated, band-limited periodic pink noise generator (40-80Hz for subwoofer, 500-2000Hz for mains) 3) Independent settings for level, delay and EQ for subwoofer output 1 and 2 when the subwoofer is set to mono. 4) Independent cutoff and slopes of speaker and subwoofer splice. An example would be setting front left to 80Hz and 12dB whereas the signal going to the subwoofer could be 90Hz and 36dB. 5) Upload of PEQ filter settings from REW. 6) Upload of user generated FIR filters for every speaker channel. I would like to keep this thread specifically for requests for new features - and requests for changes in how the XMC-1 works. We really do want to hear your suggestions, and we will keep them in mind when deciding what we're going to change - and setting the priorities for planned changes. |
|
|
|
Post by ludi on Jul 23, 2014 12:17:06 GMT -5
Add an open web service (API) on the XMC-1 in such a way that an external application can control the parameters of the XMC-1. Probably a REST style interface is the easiest way. A simple interface can open up the same functions as covered by the remote control. But it’ll be more interesting if it is also possible to read and set the parameters of the detailed configuration. An application that implements this interface can then offer to the user a screen with much more information than what is possible to show on the OSD. Changing parameters using the menu structures on the XMC-1 is doable, but imagine a screen with all relevant parameters, where it is easily to make changes using a normal keyboard and mouse: an overview of all settings on one single screen; or have the opportunity to switch between two or more different configurations by a single click. With a little bit more imagination you can see a kind of graphical representation of all the PEQ settings for all speakers. Anyway, all that is possible, but the first step is to have the ability to access the XMC-1 settings by an API. Instead of providing an interface to developers, Emotiva can also create their own application. But why not make it possible for the open source community to develop an application to interface with the XMC-1? The XMC-1 is based on Linux, it should be possible to implement such an interface. Also, the XMC-1 has already a network connector so no hardware change is necessary. I don’t know how the internal software structure is, so I can’t estimate the costs for implementing this web service. I’m not sure if and how much people are willing to pay, maybe $25 to enable this interface? This is a great suggestion and one that has been in the original design scope. The hardest part right now is fire walling specific areas and only allowing access to certain things like PEQs, System set up functions, etc. There are things that we can't allow access to due to licensing agreements and or the potential of a novice doing damage to other aspects of their system (i.e. blowing up their speakers). But we are working on this for the future. I fully understand the need for controlled access, and as you mentioned there are good reasons. One of the solutions is to use an API implementation that includes validation and error checking and not just blindly copy data from the outside into the system and vice versa. Good news such interface was already considered during early design stages, often that means implementation can be done without a complete rewrite of the system. |
|
Lonnie
Emo Staff
admin
Pay no attention to the man behind the curtain
Posts: 6,999
|
Post by Lonnie on Jul 23, 2014 12:20:51 GMT -5
This is a great suggestion and one that has been in the original design scope. The hardest part right now is fire walling specific areas and only allowing access to certain things like PEQs, System set up functions, etc. There are things that we can't allow access to due to licensing agreements and or the potential of a novice doing damage to other aspects of their system (i.e. blowing up their speakers). But we are working on this for the future. Would it be possible to allow open source room correction to run on DSP 2? If I understand correctly, the DTS and Dolby code and other decoder code lives in DSP 1, then the data goes through the asynchronous sample rate converters to DSP2 for further processing (room correction). (Is PEQ implemented in DSP2 also?) I think it would be appropriate to unload Dirac code if a user wanted to load open source room correction code into DSP2. I also think it would be appropriate for Emotiva to have a heavy hand in the open source code since the potential for harm is great. We can't open up the use of DSP 2 to the public. You are correct in that DSP 2 does the post processing after DSP 1 has done the decoding. However, there are post processing functions in both Dolby and DTS that are required and DSP 2 also handles bass management. All of which must be retained are some really bad things will happen. Depending on how things play out, we may open up access to some of the embedded stuff, but that is as far as we could allow. Lonnie |
|
|
|
Post by Priapulus on Jul 23, 2014 12:28:55 GMT -5
Streaming of audio, including multi-channel audio, (FLAC, PCM, WAV) via the ethernet connection. (It's probably in the works, but since it's not here yet it still counts as a feature request) +1, but don't forget Gapless, without it I consider it uselessly incomplete player. The best would be to implement DLNA renderer, so it can be controlled from any DLNA controller from smartphone or tablet. Considering ReplayGain if set in the file metadata would also be very nice to have, so fletcher munson loudness curves would be offsetted correctly according to the normalization level of the recording, and also there would be no volume jumps between files. Kept it all in one post as everything here is closely related. Wouldn't a Google Chromecast ($35) plugged into a HDMI port do this, better? /blair
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jul 23, 2014 12:31:54 GMT -5
Center Channel Fill Mode: L/C/R Only Tends to extend the sweet spot with the center more anchored for stereo. Normally the center is run L-3dB + R-3dB, but adjustable would be nice.
+1
|
|
|
|
Post by BassThatHz on Jul 23, 2014 13:13:49 GMT -5
+1 on the 2Hz increments of a 10-20hz HPF
+1 on the dual mono-subs option with independent XO/Delay/variable phase.
1) Adding X.2 inputs. $0
2) Adding XLR inputs. $100
3) Via FW update, add a DEQ Compressor/Expander for the sub outs. $0
4) External processor board for Atmos support. $300
5) Creating a UMC-500 that sells for $1000 and is dirac-less, but that has all the rest of the features of the XMC-1, but just 1 HDMI output and a few less inputs, no zones, no record.
6) Adding rev2 of XSP-1 with X.2 HT inputs. $0
7) Adding the 2.2 defeatable analog XO's in the XSP-1 to the RMC-1 for Ref-mode,
13.2 XLR & RCA inputs and outputs,
have the RMC-1 be a modular design (and unlike Rotel, actually build and sell the modules... not empty promises.)
Dirac could be a separate module, the stock 11-band PEQ is fine. Atmos could be a separate module.
Add a generic channel mapper and matrixer and push DataSat out of the market place with a lower price tag.
I'd pay $3000-4000 for that beast!!
-My 2 Cents.
|
|
|
|
Post by ÈlTwo on Jul 23, 2014 13:18:53 GMT -5
+1, but don't forget Gapless, without it I consider it uselessly incomplete player. The best would be to implement DLNA renderer, so it can be controlled from any DLNA controller from smartphone or tablet. Considering ReplayGain if set in the file metadata would also be very nice to have, so fletcher munson loudness curves would be offsetted correctly according to the normalization level of the recording, and also there would be no volume jumps between files. Kept it all in one post as everything here is closely related. Wouldn't a Google Chromecast ($35) plugged into a HDMI port do this, better? /blair
No, I'm looking at a wired connection, not a wireless one, and I don't want to eat another HDMI input. I'm also talking about pulling the material from a NAS, not casting it via Chrome. If I cast it via Chrome, I have to use something like Plex. I'd rather just pull the material via the ethernet connector to the XMC-1 and play it. A DLNA renderer would accomplish this, and one could use a tablet or smartphone as a Digital Media Controller. |
|
|
|
Post by millst on Jul 23, 2014 13:32:31 GMT -5
More functionality for the HDMI outputs
1) Output video from one HDMI input with audio from a different input
2) Output the [non-downmixed] audio being decoded in the main zone
3) Output different sources to the outputs
|
|
|
|
Post by igorzep on Jul 23, 2014 14:42:02 GMT -5
More functionality for the HDMI outputs 1) Output video from one HDMI input with audio from a different input +1 2) Output the [non-downmixed] audio being decoded in the main zone 3) Output different sources to the outputs What do you mean here? |
|
edrummereasye
Sensei
"This aggression will not stand, man!"
Posts: 438
|
Post by edrummereasye on Jul 23, 2014 18:11:01 GMT -5
Add an open web service (API) on the XMC-1 in such a way that an external application can control the parameters of the XMC-1. Probably a REST style interface is the easiest way. A simple interface can open up the same functions as covered by the remote control. But it’ll be more interesting if it is also possible to read and set the parameters of the detailed configuration. An application that implements this interface can then offer to the user a screen with much more information than what is possible to show on the OSD. Changing parameters using the menu structures on the XMC-1 is doable, but imagine a screen with all relevant parameters, where it is easily to make changes using a normal keyboard and mouse: an overview of all settings on one single screen; or have the opportunity to switch between two or more different configurations by a single click. With a little bit more imagination you can see a kind of graphical representation of all the PEQ settings for all speakers. Anyway, all that is possible, but the first step is to have the ability to access the XMC-1 settings by an API. Instead of providing an interface to developers, Emotiva can also create their own application. But why not make it possible for the open source community to develop an application to interface with the XMC-1? The XMC-1 is based on Linux, it should be possible to implement such an interface. Also, the XMC-1 has already a network connector so no hardware change is necessary. I don’t know how the internal software structure is, so I can’t estimate the costs for implementing this web service. I’m not sure if and how much people are willing to pay, maybe $25 to enable this interface? +1000 I'll even go $50 (but it should be free!) |
|
