This problem happened after the 1.30 upgrade. Buffalo included Twonkymedia 4.4.18 and that version did not stream .mt2s files as delivered by Buffalo. I figured this issue would be fixed with the latest firmware release. Sadly NO!!! 1.32 comes with Twonky 4.4.19e2 and .m2ts files still can not be streamed. All I need is telnet and root access to the machine and I could fix it myself!!!!
I had to downgrade to firmware 1.20 which included Twonky 4.4.8 which streams all media format with no problems but still has many bugs including ones for replication.
Can a Buffalo representative tell me why I should continue with a product line that states that it can stream media but clearly can not stream files shoot with my home video camera.?
This has become very fustrating. I am being forced to use another companies products because Buffalo in not concerned in delivering features that it's customers need.
Someone from Buffalo please respond because I need to know if this issue will be addressed. If not I will move on to a product line that does meet my needs.
Thanks
Chris
bump
bump!!!
Not all formats are supported by the unit through DLNA, but since it worked on the previous firmware ill forward it to the engineers and see what we can do. Sorry about the inconvenience.
Also, after the upgrade, try to reset your unit through system then restore/format. Then set up the unit again and configure the media server function and see if this fixes the issue.
Sir, I did get an answer from our engineers. If you could provide your phone number I can give you a call tomorrow between 8-4 to discuss this issue.
Sorry for the late reply. I have been traveling. call me cell at any time 917-803-8316
bump
Thank you for you mesage today. I have followed your directions completetly and .mt2s files still can not be played on my popcorn hour c-200 on TS-XL firmware 1.32 / Twonky 4.4.19_e2.
Again i downgraded to version Firmware 1.20 Twonky 4.4.8 and all AVHCD (.m2ts files) play perfectly.
as a side note My Terrastation Pro II with Twonky 5.0.68 streams .mt2s files just file.
Any more sugestions?
I also renamed a .m2ts file as a .mkv on firmware 1.32 / Twonky 4.4.19_e2 and the files stream fine to my PCH C-200. Seems that .m2ts files are not being recognized as a valid media format.
or........
The PCH-200 is being recognized as a Generic DLNA 1.0 client. Has the info in the client.db changed so that it no longer supports .m2ts??
I am at a complete loss without looking at the twonky files myself :-(
bump
There is the possibility that the extension may be causing Twonky to bug out. I haven't even heard of that media extension before.
Edit: Upon further investigation, according to the DLNA certificate and Media Format and Transport Model the extension of .mt2s is not supported via DLNA.
FIrst of all saying the format is not supported by twonky is not true. AVHCD is a container based on MPEG-2. The file can be streamed from my PS3 and Samsung 58 Plasma TV with firmware 1.20 - 1.40 with no issues. The issues is how the popcorn hour is recognized by the version of twonky you offer on this device. Every device in the UPNP devices list is recognized and there is a file that states what format that device can stream. If I rename the .m2ts file to .mkv, the file plays correctly so twonky stream the file. All someone has to do is look it up on the twonky forums. It is a simple procedure to add the extension of the supplied database for popcorn hour type devices in 4.4.19. In 5.x and 6.x RC.x of twonlky it works fine. I can stream it with firmware 1.20 that has 4.4.8 of twonky. I can stream it with Playon or other stand alone dlna streaming products. I can stream it with twonky that is installed on a Qnap T-559 Pro device. The only one is can stream it on is the Terrastation III.
With respect if you knew all of this before then why not elaborate on it? Oh, nevermind I'll let someone else answer.
If you read the entire thread you will see that I mentioned it a few posts in.
I am also unable to play mt2s files from my LS-WXL. Called Buffalo Support today, who recommended me to upgrade firmware (to 1.37 through the "force method" found at http://forums.buffalotech.com/t5/Storage/FAQ-2-of-5-Force-Firmware-update-procedure-please-read-this/td-p/11011) and also reset config to defaults. Did both and still doesn't play.
The manual states on page 94 that .m2ts is supported for DLNA, but it isn't working on any of my player clients.
So, I guess my question is....does Buffalo recognize this as a bug and have plans to address or do I need to return this product that doesn't behave as documented in the manual?
Check out http://cdn.cloudfiles.mosso.com/c85091/linkstation_1.40_version_history.txt (linked to from the downloads page for my duo).
I can't really tell is this means firmware 1.40 is coming out for the LinkStation or if this is simply the DTCP-IP version update, which mine already shows as 1.40-20101129.
Thats not a firmware, thats a media server version.
The Media Server Version and config is included with the firmware.
Are the other NAS drives out there (like Seagate BlackArmor, WD, Iomega, Lacie, etc) any better at handling mt2s files? I don't want to switch out vendors only to have the same problem.
QNAP
LS-WX2.0TL/R1
Firmware 1.37
DTCP-IP:1.40-20101129
the ps3 plays .m2ts perfectly from this model. the only issue is that if i try to transfer a file to / from the nas it sometime crashes the media server!
I would advise updating the unit to the 1.50 firmware and setting the media server back up to see if it is an issue with the current firmware you are running on the unit now.
Still does not work.
I have found that Buffalo products simply don't work as advertised. The router I bought went back to the store 1 week after purchasing, and so did my Linkstation Pro. I'm instead running Mezzmo on XP and having absolutely no problems playing M2TS files to my Sony Blu Ray player. Buffalo needs to get their act together and actually understand these problems instead of wasting consumer's time doing random firmware upgrades and downgrades. How about a response like, "I did X and that fixed it" instead of just simply "well, try this and let me know if that fixes it." No, that's what Buffalo's QA team is for...trying things and seeing if they work.