[Download] UMC V2.0 - Public Beta

[Bjur]

(04-10-2010 03:39 PM)jctcom Wrote:  It's hit and miss but mostly miss. When you talk about the new version are you talking about the previous beta or 1.84? I don't think the playback problems have been any different in any of the new 2.0 betas.

Carl

It was what Jakera wrote a page ago:
And I reported a few posts above that the playback function isn't ready at the moment. Known problem files are MKV, VIDEO_TS, BDMV and maybe ISO.

So if that goes for the newest beta released, I'm gonna use an earlier 2.0 beta?

BTW: Still haven't found a working series xml solution. The one in the wiki only shows bearbeiten, from what I can see..

[DonGyros]

The current version of the frontend will check which firmware is installed an dependent on that will use the correct API calls for playback.
Most playabck issues at the moment have something to do with the differen firmwares installed on your NMT's. Syabas is working on the API and from version to version more features will be included.

[jctcom]

(04-10-2010 03:46 PM)Bjur Wrote:  It was what Jakera wrote a page ago:
And I reported a few posts above that the playback function isn't ready at the moment. Known problem files are MKV, VIDEO_TS, BDMV and maybe ISO.

So if that goes for the newest beta released, I'm gonna use an earlier 2.0 beta?

BTW: Still haven't found a working series xml solution. The one in the wiki only shows bearbeiten, from what I can see..

For Series implementation I have been using file / Folder naming conventions as mentioned at the bottom of that wiki.

Carl.

[JKG]

(04-10-2010 11:34 AM)HTP Wrote:  With the latest beta all my movies have the same director info (in my case Joe Ranft , John Lasseter). Director scraping worked fine in the previous version.

I also have "Joe Ranft, John Lasseter" in director field of every movie.

[Bjur]

(04-10-2010 03:49 PM)jctcom Wrote:  For Series implementation I have been using file / Folder naming conventions as mentioned at the bottom of that wiki.

Carl.

Problem is it ignored - so in The X-Files it looks for The X Files which is not correct. I have gotten to that point where it shows as nfo true, but is still can't find banner etc. and gives the same errors.

[hxall]

(04-10-2010 03:58 PM)JKG Wrote:  I also have "Joe Ranft, John Lasseter" in director field of every movie.

+1, just installed latest (still says build 0001), but when rescanning a single movie folder for Brothers.mkv, it shows the same directors as JKG...

[robinsj]

Here if people want an example of a naming convention that works, I have over 850 movies, and it detected every single one of mine correctly....

[jctcom]

(04-10-2010 03:49 PM)DonGyros Wrote:  The current version of the frontend will check which firmware is installed an dependent on that will use the correct API calls for playback.
Most playabck issues at the moment have something to do with the differen firmwares installed on your NMT's. Syabas is working on the API and from version to version more features will be included.

So you mean something in the way UMC is interacting with the current firmware? Because the problems are far less prevalent if we don't run UMC so it is not just a firmware issue.

Carl

---

I am posting this here mostly so that I can refer to it in my signature since it is too long for me to put it directly into it.

These posts are the best way I have found to get your networked shares up and mounted properly (At least this is what worked for me)

Posts detailing my multiple networked hard drive mounting setup:

First follow this post to set up the start_app.sh

http://www.networkedmediatank.com/showth...art_app.sh Post #2

These are my entries into the start_app.sh which mount my networked shares (Which are predefined in the C200 "Network Shares" configuration)

http://www.networkedmediatank.com/showth...#pid364901 Post #587

Carl

[DonGyros]

The playback functions are all implemented by Syabas and are integrated in the firmware. Syabas is working on that API which you can use from a RobG context and we are using this API.
Dependent o the firmware you have installed the calls to the playback API are not the same. So we just implemented a workaround that at least the playback will work with the current public firmware AND the current beta firmware.

But I'm not sure if the current public version of ReVamp includes this modification.

[hxall]

(04-10-2010 04:31 PM)DonGyros Wrote:  The playback functions are all implemented by Syabas and are integrated in the firmware. Syabas is working on that API which you can use from a RobG context and we are using this API.
Dependent o the firmware you have installed the calls to the playback API are not the same. So we just implemented a workaround that at least the playback will work with the current public firmware AND the current beta firmware.

But I'm not sure if the current public version of ReVamp includes this modification.

I'm on the latest beta firmware, and playback is very poor with consistent lock-ups and reboots necessary. Waiting patiently for Syabas to release next beta firmware with improved RobG...

For the Noob's, this stuff (both RobG and UMC 2.0), is still very beta, don't expect it to run flawlessly for a while, if you want to try it out, then fine, but don't complain when it doesn't scan your library or locks-up your PCH, which will happen...

[jctcom]

(04-10-2010 04:31 PM)DonGyros Wrote:  The playback functions are all implemented by Syabas and are integrated in the firmware. Syabas is working on that API which you can use from a RobG context and we are using this API.
Dependent o the firmware you have installed the calls to the playback API are not the same. So we just implemented a workaround that at least the playback will work with the current public firmware AND the current beta firmware.

But I'm not sure if the current public version of ReVamp includes this modification.

I'm sorry but this is not clear to me if you are stating that there is a problem with playback from within UMC 2.0 or not?

There is definitely a playback issue from within UMC that does not exist (Or at least to a far lesser degree) if we don't run UMC. Are you still saying that this is a C200 Firmware issue? or a UMC 2 issue?

I am running the latest official C200 Firmware so as far as I can see the problem is within UMC.

Carl.

[hxall]

(04-10-2010 04:43 PM)jctcom Wrote:  I'm sorry but this is not clear to me if you are stating that there is a problem with playback from within UMC 2.0 or not?

There is definitely a playback issue from within UMC that does not exist (Or at least to a far lesser degree) if we don't run UMC. Are you still saying that this is a C200 Firmware issue? or a UMC 2 issue?

I am running the latest official C200 Firmware so as far as I can see the problem is within UMC.

Carl, let me see if I can explain this for you:

1) PCH has various built in (firmware) ways to play movies
2) Syabas provides an API (application interfaces) for developers, they are hooks that developers can use to access the internal payback in the PCH
3) The internal playback mechanism is different for different firmware releases, so the interface to the playback (how UMC can access the firmware routines) is also different
4) So what Don is saying is that UMC frontend is now checking to see what firmware is loaded on your PCH before it attempts to "talk to it", to make sure it is using the right interface to send the playback commands
5) Accessing playback directly on your PCH is different than going thru an API (UMC doesn't control access to the internal playback mechanisms)
6) When you tell UMC to play a movie, it sends a "Play" command to the PCH firmware thru the API
7) The PCH firmware and API (interface to it) needs to be improved by Syabas in the next release so that it can better interface with UMC

[jctcom]

(04-10-2010 04:50 PM)hxall Wrote:  Carl, let me see if I can explain this for you:

1) PCH has various built in (firmware) ways to play movies
2) Syabas provides an API (application interfaces) for developers, they are hooks that developers can use to access the internal payback in the PCH

Ok so if we aren't playing back through UMC then we aren't running through that API.

I think I understand now.

Thank you.

Carl

[DonGyros]

This is no UMC problem

The API used to playback movies from within RobG is not the same that is used from the current default NMT interface!

[Mitchlw]

Installed the latest Java and got everyhing working now...looks so sexy...

But now when i click "play", nothing happens?