Authoring BD5s for playing on the Panasonic DMP-BD35

[rack04]

Does any other owner of the BD35 have issues with fastforward/rewind on BD9 transcodes? I've tried lots of different settings and fast forward/rewind seems to not work correctly. Chapter skip works fine. FF/RW works sometimes on the slowest FF/RW speed, and then sometimes the video just stops fast forwarding, and I have to hit play for the video to start moving at all. Sometimes it even completely stalls the video and I have to eject the disc. Any ideas?

Yep. All the time.

[alc0re]

@MadMonkey7

I've tried all kinds of different settings, and all have the same results playing on my panasonic BD35. Can you possibly post your current x264 encode settings so I can try them?

[laserfan]

Does any other owner of the BD35 have issues with fastforward/rewind on BD9 transcodes? I've tried lots of different settings and fast forward/rewind seems to not work correctly. Chapter skip works fine. FF/RW works sometimes on the slowest FF/RW speed, and then sometimes the video just stops fast forwarding, and I have to hit play for the video to start moving at all. Sometimes it even completely stalls the video and I have to eject the disc. Any ideas?A shot-in-the-dark: Have you tried muxing without the contSPS (tsMuxeR) option?

I've noticed that at least with Cyberlink PowerDVD 7.3 that with contSPS enabled, chapter marks are often early on entry. With contSPS gone from the .meta (or un-checked in the GUI) these are right-on as they should be.

I suspect therefore that contSPS messes with picture timing somehow. Dunno if this might affect your player but worth a try maybe.

[MadMonkey57]

@MadMonkey7

I've tried all kinds of different settings, and all have the same results playing on my panasonic BD35. Can you possibly post your current x264 encode settings so I can try them?

A customized version of Sharktooth's Blu Ray profile for MEGui:

--pass 1 --bitrate "${BITRATE}" --stats "${OUTPUT}.stats" --level "${LEVEL}" --keyint "${KEYINT}" --min-keyint 2 --bframes 3 --b-adapt 2 --weightb --direct auto --deblock -1:-1 --subme 2 --partitions none --ipratio 1.1 --pbratio 1.1 --vbv-bufsize "${VBV_BUFSIZE}" --vbv-maxrate "${VBV_MAXRATE}" --qcomp 0.5 --me dia --threads auto --thread-input --progress --no-psnr --no-ssim --output NUL "${INPUT}" --mvrange 511 --aud --nal-hrd --sar "${SAR}"

--pass 2 --bitrate "${BITRATE}" --stats "${OUTPUT}.stats" --level "${LEVEL}" --keyint "${KEYINT}" --min-keyint 2 --ref 3 --mixed-refs --bframes 3 --b-adapt 2 --weightb --direct auto --deblock -1:-1 --subme 7 --trellis 2 --partitions p8x8,b8x8,i4x4,i8x8 --8x8dct --ipratio 1.1 --pbratio 1.1 --vbv-bufsize "${VBV_BUFSIZE}" --vbv-maxrate "${VBV_MAXRATE}" --qcomp 0.5 --me umh --threads auto --thread-input --progress --no-psnr --no-ssim --output "${OUTPUT}" "${INPUT}" --mvrange 511 --aud --nal-hrd --sar "${SAR}"

typical values for args:

INPUT=blah.avs
OUTPUT=blah.264
BITRATE=nnnn
KEYINT=24
VBV_BUFSIZE=15000
VBV_MAXRATE=15000
SAR=1:1

[MadMonkey57]

Anybody tried firmware dated feb the 9th ?

[alc0re]

@ MadMonkey7

I've tried those settings too...I've tried lots of settings in an attempt to get this to work. Its the very last issue I'm having with my Bluray-to-BD5/9 process. I think it might actually not be an issue with the encode itself, but more of a muxer issue.

What exact steps/settings do you use in tsMuxer?

I'm going to experiment a bit. I need to rip one of my blurays and test it by muxing one of the extras without re-encoding back to a BD5/9 to test my theory that its a muxing issue.

Do you use default txMuxer settings? Do you have the following checked or unchecked on the video stream?

- Add picture timing info.
- Continually insert SPS/PPS.

Do you do anything to the mux after using tsMuxer? (aka fixclpi which from what I gather doesn't work on BD35s, or AVCHD-Me?)

I read in another thread that unchecking "Continually insert SPS/PPS" can help with chapter skipping. What exactly do these two video stream settings do anyways? (Continually insert SPS/PPS and add picture timing info.)

I read in another thread that the user G M C was also having the same issues. He said what he does now is to check "Change FPS" on the video stream option in tsMuxer, even though it "should" read the video FPS fine from the stream. Another user tried that and had luck with it. I haven't gotten around to trying that yet. Is that something you do with your muxing process? I have yet to try any of this with newest firmware. I'd be interested if we could use fixcpli now with the newest firmware also.

[MadMonkey57]

@ MadMonkey7

I've tried those settings too...I've tried lots of settings in an attempt to get this to work. Its the very last issue I'm having with my Bluray-to-BD5/9 process. I think it might actually not be an issue with the encode itself, but more of a muxer issue.

What exact steps/settings do you use in tsMuxer?

I'm going to experiment a bit. I need to rip one of my blurays and test it by muxing one of the extras without re-encoding back to a BD5/9 to test my theory that its a muxing issue.

Do you use default txMuxer settings? Do you have the following checked or unchecked on the video stream?

- Add picture timing info.
- Continually insert SPS/PPS.

Do you do anything to the mux after using tsMuxer? (aka fixclpi which from what I gather doesn't work on BD35s, or AVCHD-Me?)

I read in another thread that unchecking "Continually insert SPS/PPS" can help with chapter skipping. What exactly do these two video stream settings do anyways? (Continually insert SPS/PPS and add picture timing info.)

I read in another thread that the user G M C was also having the same issues. He said what he does now is to check "Change FPS" on the video stream option in tsMuxer, even though it "should" read the video FPS fine from the stream. Another user tried that and had luck with it. I haven't gotten around to trying that yet. Is that something you do with your muxing process? I have yet to try any of this with newest firmware. I'd be interested if we could use fixcpli now with the newest firmware also.

I keep "Add picture timing info" and "Continually insert SPS/PPS" checked and I always check "Change FPS" and "Change level" to force what is detected by tsmuxer. I've done this since the very first day I used tsmuxer as I had read at that moment it "was better that way"... Never took some time to try otherwise.

I never use fixclpi as it breaks playability on the BD35 although I don't know for sure if it is fixclpi or the firmware or x264 settings or tsmuxer settings or any combination of all of this which breaks playability...

Never used AVCHD-Me either.

I also hope the newest firmware will bring improvements but didn't upgrade yet.

[alc0re]

Update :

6-7 dvd+r's later, and still not working with FF/RW. Every thing I tried resulted in BD5 disc that if I use FF on, it would FF for a bit and then stop on a frame for 1-3 seconds, then start playing @ normal speed.

I haven't tried your x264 encode settings, but here's what I have tried.

I took a making of documentary from air force one bluray. It was a short source file...maybe about 6 mins. Processed and burned the m2ts file with Clown-BD....resulting burn did not FF/RW properly.

I took that same clip from air force one and extracted it myself, and muxed it with tsMuxer myself, selecting Change FPS and Change Level in tsMuxer video stream options. Resulting burn did not FF/RW properly.

These are muxes from a .264 video stream direct from studio (not re-encoded by me.) It should RW/FF ok if my FF/RW issues were encode settings related, but it still does not FF/RW correctly (unless it has to do with bitrate settings being too high for dvd-rom speed, but I doubt that. I checked the clip..the video stream is 10 Mbps and the audio stream is 192 Kbps.)

I tried numerous other combinations of things on another video that I transcoded using MeGUI. Here's what I tried on that encode.

1) Tried muxing with Change FPS and Change Level on. Didn't FF/RW correctly.
2) Tried muxing with Change FPS and Change Level on, and deselecting Continually Insert SPS/PPS and Insert Picture Timing Info. Didn't FF/RW correctly.
3) Took both of those muxes and ran a tool called CLIPINF Editor (from author of clown-bd) on them to fix the clipinf and change the structure to identify the mux as AVCHD (instead of tsMuxer's output saying it was bluray...since the panasonic bd35 reads it as avchd.) Both of those after running that tool on them also did not FF/RW correctly.
4) Tried another recommendation found in another thread to take the .m2ts file that tsMuxer outputs and use that is an input file in tsMuxer and remux it again to bluray format (aka mux it to bluray format, take that .m2ts and mux it again with tsMuxer to bluray format.) Still would not FF/RW.

So in conclusion, I have no idea how you are not having FF/RW issues. I think I've exhausted all possible avenues to correct this issue. PS, this was all done on panasonic's newest firmware for the BD35. Any suggestions MadMonkey?

[MadMonkey57]

Well, I don't know what to say... I've never had problems with my BD5s using the procedure I mentioned... It just... works... the exact same way commercial BDs work...
I'm currently upgrading the firmware... I'll let you know if anything is different regarding FFOR/REW.

[MadMonkey57]

Upgrade just done. EU version 1.3.

FFOR/REW are still working fine:5 speeds forward, 5 speeds backward, all work fine. The first speed forward has sound...

[alc0re]

Well,

There are a couple more things I can try...I'll keep you updated if I figure out what the heck is causing the issue in my case.

[alc0re]

Tried a few more things...

I lowered the vbv max bitrate and buffer size down to 15000 like on your encode settings. I also took out --nar-hrd like G M C.

I just did a test clip with new encode settings, muxed with tsMuxer with Change FPS on...used avchd-me like G M C did to apply fixcpli and patch m2ts size.

My results : Fast forward seems to work better, but still not perfect.

I'm starting to wonder if it has to do my either a) my blank media or b) my burning speed.

I'm using either single or dual layer Verbatim DVD+Rs...and I burn them at max speed. When the panasonic BD35 stops FF'ing, I think I can hear the BD35 "struggling" to read the medium.

1) What medium do you use? I thought Verbatim were the best.

2) What speed do you burn at? I think I'm going to try burning at the slowest speed and see if that helps.


UPDATE : Ok, I burned that same clip using my 1x speed in imgburn...I was able to FF the whole clip a 2x the first time...I tried again and it stalled right at the very end, then tried again at both 3x and 4x and I was able to FF the whole clip. So the slower burn speed did seem to help (although still not perfect.) Now I'd like to figure out if that was the only thing messing with my FF, or if it was also related to vbv settings and --nal-hrd settings. Sooo many wasted dvdrs... :(

UPDATE 2 : Changed my vbv settings back up to where they were (22000 buffer/16000 max.) Changed my other settings back to where they were, except I left --nal-hrd out again. Ran it through AVCHD-Me to apply fixcpli and m2ts patch...burned @ slowest speed and worked pretty consistently with FF/RW. Worked just as consistently as with lower vbv settings (I also tend to use more ref and b frames than 3/3, which is still compliant cause I resize to 720p) Here's an interesting thing I learned though. I took that same bluray structure, and followed MadMonkey7's instructions to strip out "extra" stuff and force an audio and subtitle track. That disc did not FF/RW very well at all. It constantly stopped FF'ing/stalled. Here's what else I noticed. On the disc that I didn't follow those instructions, my panasonic bd35 displayed the timecode of the movie during play and during FF/RW. On the one that I followed the directions for using BDEdit to strip out "extra" stuff and force audio/subs on, the timecode neither displayed during the playback or during FF/RW. By display I mean on the front panel of the physical player (the lcd display), not on the tv. I'm going to try leaving in the extra stuff and just adding a line to force audio/subs and see how that goes.

[MadMonkey57]

I'm using different media brands and even unbranded media and all seem to workfine when it comes to FF/RW.
btw I'm burning at the lowest speed my burner allows me to, that is 4x...
And I seem to encounter the kind of problems you're having if I use a DVD+RW disc
... So basically Media type and burning speed might be somehow (partly) responsible for FF/RW issues...

You are right about the LCD not displaying play time... How comes I have missed that !!! Adding the "SetStream" before "PLAY PL" commands and leaving the rest of the structure untouched should do the trick...

The new firmware doesn't help with the fixclpi issue...Still making my AVCHD/BD discs unplayable...
Fixing M2TS length in CLPI file is working fine...

Did you get fixclpi to work ?

[alc0re]

Umm....do I add that setstream command before the play pl command in every movie object? I was going to just add the setstream command right after command 0001 in movie object 000...(after move gpr0,0, before play pl_mk 0, grp10)

Is that correct or do I need to add setstream in more places?

As far as fixclpi...you know I haven't actually used fixclpi directly. after taking out --nal-hrd from my encoding, i've tried both using AVCHDMe and only using the "Fix CLPI files" option (which states it does what fixclpi.exe does, and i've used the utility CLIPINF_Editor from the guy that makes clown-bd and using the "Fix Length" area, which from what I gather it does the same thing that the avchdme program does. So I think yes, indirectly my encodes are working with fixclpi. not sure if the m2ts filesize thing is what gets it working and if that's maybe something fixclpi doesn't do? I really dont know what fixclpi is supposed to do so I'm just shooting in the dark. but yes, my encodes are a lot better now (still not perfect FF/RW...stops sometimes.)

My current process : Rip with eac3to, convert with MeGUI with a profile that is set to autoguess level (my encodes end up at level 3.2..important not to set it to level 4.1. i believe someone posted my finding on that issue with the bd35 earlier in this thread.) I took out --nal-hrd from my encode profile. I mux with tsmuxer, set change fps. I edit with bdedit to setsteam if needed (i only use with when I have a seperate "forced subs" track that I want on by default for foreign language parts of a movie), then I patch it with CLIPINF_Editor. burn now at slowest speed (4x)

I think i've gone trough like a total of 30-40 blank dvd+rs and more than 30 blank dvd+r dls to figure out all this stuff. (first set of 25 dvd+r dls i wasted cause I converted the video at an exact fps of 23.976 instead of 24000/1001 which caused stuttering (based on a tutorial for bluray to bd9)...and also the level 4.1 thing before I figured that issue out)

[MadMonkey57]

...Is that correct or do I need to add setstream in more places?...

Yes. Insert a SetStream BEFORE both PLAY PL commands in tsmuxer's output, that is in movie objects #0 and #1. Those 2 PLAY PL commands refer to the only playlist, which in turn points to the movie.

...I really dont know what fixclpi is supposed to do so I'm just shooting in the dark...

For what I understand, fixclpi fixes an internal table wrongly generated by tsmuxer in clpi files. What is usually referred to as "fix m2ts length" is another issue in clpi files, different than what fixclpi is fixing. As you probably have noticed, there is a bug in fixclpi and jdobbs has updated it. It won't be long until we get plenty of reports regarding Pana SAPs...

...important not to set it to level 4.1...I took out --nal-hrd from my encode profile..

I also tend to use profile 4.0, which is consistent with the VBV-* settings I use in x264 as it seems to *somehow* improve global playability (I used to have stuttering with 1280x720x50p with level 4.1. They's are gone by just switching to level 4.0...)

Regarding --nal-hrd, I have NOT done many tests... So it's hard for me to tell how if affects playability.

[alluringreality]

I've never had problems with my BD5s using the procedure I mentioned... It just... works... the exact same way commercial BDs work...

So if I was to use your encoding settings and author with Encore, does that mean it plays back as 24p on the BD-35? I can always author a test clip sometime, but I just figured it would be easier to ask if the 24p playback had been corrected with what you were discussing.

[MadMonkey57]

Well I should have written that it works ALMOST the same way commercial BDs work... As we have discussed a while ago, I can't get the "24p Playback" feature to work with BD5/9s...

[alc0re]

Where do I find the new version of fixclpi so I can test it?

[rack04]

Where do I find the new version of fixclpi so I can test it?

http://forum.doom9.org/showthread.php?t=145092

[laserfan]

@alc0re do not fail to note that this thread is about testing a version that is less than 24hours old i.e. jdobbs advises against using it for anything but testing atm.

[alc0re]

yah I saw that...thanks for the heads up.

[alc0re]

Yes. Insert a SetStream BEFORE both PLAY PL commands in tsmuxer's output, that is in movie objects #0 and #1. Those 2 PLAY PL commands refer to the only playlist, which in turn points to the movie.


@MadMonkey57....Tried it that way with a SetStream command before both PLAY PL commands in movie objects 0 and 1, and the movie refused to play. Edited that same movie and only had a setstream command before the play pl command in movie object 0 and the movie both plays correctly and set the subtitle on that I specified.

[MadMonkey57]

That's strange... I know I've done this a long time ago (before I started removing almost everything keeping only setstream and play pl...)... But I can't remember if it was on tsmuxer's index.bdmv/MovieObject.bdmv or Adobe Encore CS4... I'll make a few tests and will keep you informed...

[deank]

In multiAVCHD I use only one setstream in the whole compilation and it is before calling title#0 (top menu).

http://multiavchd.deanbg.com/setstream.jpg

[Elesias]

Hi !

I have problems with VC1 video streams (remuxed through TSMuxer) when playing on my Panasonic BD 35. Is there a trick to fix this trouble please ? Thanks !

[laserfan]

Just noticed this on the AnyDVD forum:

Fix (Blu-ray): Playback issues with Panasonic Blu-ray players

This is in the latest version--I have never noticed any comments there about Panny problems, but one wonders if it might have anything to do with problems being discussed here!?

[turbojet]

It has to do with removing region in anydvd.

[MadMonkey57]

Hi !

I have problems with VC1 video streams (remuxed through TSMuxer) when playing on my Panasonic BD 35. Is there a trick to fix this trouble please ? Thanks !

What kind of problems ? Burning BD-25/50 or BD5/9 ?
At least, be aware that VC1 is not AVCHD compliant. So that might be a reason why VC1 streams don't work on BD5/BD9.

[MadMonkey57]

That's strange... I know I've done this a long time ago (before I started removing almost everything keeping only setstream and play pl...)... But I can't remember if it was on tsmuxer's index.bdmv/MovieObject.bdmv or Adobe Encore CS4... I'll make a few tests and will keep you informed...

@alc0re

I still have this on my to do list... lacking time...

[MadMonkey57]

@MadMonkey57....Tried it that way with a SetStream command before both PLAY PL commands in movie objects 0 and 1, and the movie refused to play. Edited that same movie and only had a setstream command before the play pl command in movie object 0 and the movie both plays correctly and set the subtitle on that I specified.

I am not 100% sure I interpret navigation commands correctly, but based on what i see in the outputs from tsmuxer and Adobe Encore CS4, I tried a slightly different scenario to get audio/subs on by default...

The short version:

Use "Play PL_MK 0, 0" instead of "Play PL 0" in my previous procedure


The long version:

Use BDEdit to remove all movie objects but one, keep only 2 nav commands, and update them as follows:
- SetStream 2147598337, 0 [Forcing 1st audio and 1st sub]
- Play PL_MK 0, 0 [Playing Playlist #0 ????]
In addition:
- Assign movie object #0 to "First Playback" and "Top Menu"
- Choose "Movie" as the type of movie object for "First Playback"

Tried this only once so far... works fine... and the LCD displays the play time...

@alc0re, a little feedback would be appreciated

[deank]

Play PL X - Plays playlist file X (i.e. X=1 - 00001.mpls) from first playitem ignoring previous chapter/playitem settings
Play PL PI 0, 1 - Plays second (1) playitem from playlist 0 (00000.mpls)
Play PL MK X, Y - Plays specific chapter from a title.

[MadMonkey57]

Play PL X - Plays playlist file X (i.e. X=1 - 00001.mpls) from first playitem ignoring previous chapter/playitem settings
Play PL PI 0, 1 - Plays second (1) playitem from playlist 0 (00000.mpls)
Play PL MK X, Y - Plays specific chapter from a title.

Thanks for clarifying this.

Any idea why "Play PL 0" indeed plays playlist but doesn't *show* the play time on the LCD of the BD35 ????

[deank]

I guess because your player shows info only when playing a normal title with duration and chapter information set by navigational commands. I think Play PL is not to be used for playing normal titles, but for menu extras like warnings or menu pages (like I use it). Also what is allowed for display and operate is set with other means in playlist files (as you see in middle-upper part of playlist BDedit window).

[MadMonkey57]

OK. I understand the differences between PL and PL_MK and therefore why PL_MK is appropriate here. :thanks:

What I see in the outputs of tsmuxer and Encore is GPR assignments, comparisons, and title jumps. In both cases, if I walk trough the code, I always end up PLAY PL_MK 0, 0

I was assuming this: Nero Vision and Encore insert these GPR assignments and other nav commands within a generic authoring process. In the case of a main movie only, if all we need is starting the disc at the 1st chapter, manipulating those GPRs is useless.

My question is: what manipulating GPRs has to do with the SAP "learning" info from the disc like duration and so on ?? I though this kind of info was stored in PSRs.

EDIT: IMO, PLAY PL_MK nav command triggers the SAP to load some data in the PSRs. I guess it's not the case with PLAY PL.

[deank]

Yes, PSRs hold player status but those cannot be changed - only read, thus menu pages or m2ts files with program codes parse information to movieobject and title#0 (top menu) via GPRs.

For example your player is showing a menu page. The menu page itself contains move/compare... nav commands changing GPRs and then your top menu knows what title/chapter to play, which audio or subtitle stream to enable or disable, etc...

In case of no menu and no need to know what menu page is shown or what user actions are performed you can use Immediate values (of course if the nav command accepts such - as you know some commands require target to be a register).

Also some GPRs get changed by the player itself (while executing playlists), reflecting current chapter/title ie....

GPRs are also mostly used for sort of 'communication' between titles and their program codes (movieobject object IDs).

Also for easy reading one can think of Play commands as:

Play PL X = Play PLaylist X (XXXXX.mpls)
Play PL MK X, Y= Play PLaylist X, starting from playlist MarK (chapter) Y (so this version of the command is time-based)
Play PL PI X, Y = Play PLaylist X, starting from Play Item Y (if your mpls contains references to more than 1 m2ts file - each m2ts is a playitem) - so in other words it means - check playlist xxxxx.mpls and play (Y-1)th m2ts file from it (this version is more like file based) PlayItems are zeropadded so the first is 0, tenth is 9, etc... Of course this is really simplified explanation... but I guess you get the idea.

***

It is not a good idea to have Title#0 (top menu) and Title#1 (main movie) to share the same objectID. While playing a title as TOP menu - navigation is handled differently and information displayed on SAPs LCD or TV is different, too. The best way is to have a simple Jump title #1 for top menu, Play PL MK 0,0 in title#1 (if your mpls file is 00000.mpls), BREAK to quit playback.

***

[x] First playback [Interactive] [2]
[x] Top Menu [1]

Title [1]: HDTV / Permitted / OID #0
---
ObjectID: (all with suspend/enabled/enabled for resume/menucall/titlesearch)

[000]
Play PL_MK 0,0
BREAK

[001]
Jump Title 1

[002]
SetStream $8001C001
Jump Title 0

[MadMonkey57]

...Also some GPRs get changed by the player itself (while executing playlists), reflecting current chapter/title ie...

OK. This is obviously what was troubling me... I would never have thought that the player would alter GPRs... Do you have any info (link ?) on this ? What GPRs can be altered ? What is the trigger ? What is the meaning of the value ?

...Play PL PI X, Y = Play PLaylist X, starting from Play Item Y (if your mpls contains references to more than 1 m2ts file - each m2ts is a playitem)...

Thanks for this explanation.

...It is not a good idea to have Title#0 (top menu) and Title#1 (main movie) to share the same objectID. While playing a title as TOP menu - navigation is handled differently and information displayed on SAPs LCD or TV is different, too...

Could you be a little more specific about that ?

...The best way is to have a simple Jump title #1 for top menu, Play PL MK 0,0 in title#1 (if your mpls file is 00000.mpls), BREAK to quit playback.

***

[x] First playback [Interactive] [2]
[x] Top Menu [1]

Title [1]: HDTV / Permitted / OID #0
---
ObjectID: (all with suspend/enabled/enabled for resume/menucall/titlesearch)

[000]
Play PL_MK 0,0
BREAK

[001]
Jump Title 1

[002]
SetStream $8001C001
Jump Title 0

This minimalistic BD structure / nav commands looks VERY nice, and very close to what tsmuxer and Encore produce (better BD compliancy), stripped out of every unnecessary GPRs manipulations... I definitely will try this for my next backup. Thanks a lot deank.

[deank]

OK. This is obviously what was troubling me... I would never have thought that the player would alter GPRs... Do you have any info (link ?) on this ? What GPRs can be altered ? What is the trigger ? What is the meaning of the value ?

Now again about registers.

It turned out that some PSRs are Player STATUS Registers and some are Player SETTING Registers.

Some STATUS registers can be changed with navigational commands and none of the SETTING registers can be changed (except with some workarounds when using BD-J applications).

And for example changing the value in PSR11 should make the player switch to/display another menu page....

May be not knowing this confused me that the player can alter GPRs, but in fact - depending on player's firmware - it is allowed to set/change GPRs, for example on start-up/disc-loading/changing settings in player's menu, etc...

Let me know if I can be of further assistance.

Dean

[rack04]

Has anyone tried tsMuxer Version 1.8.35(b)? The reason I ask is because I'm finding that it does not work with my BD-35. The player give error "unsupported" disc.

[alc0re]

I have yet to try it, but there's two modes now. According to the release notes, if you're buring to a dvd you need to use avchd mode, not bluray mode. bluray mode is only for burning to actual bluray discs. Not sure if that's the issue you're having or not though.

EDIT : Just tried it. Confirmed that tsMuxer 1.8.35(b) works just fine with a bd-35 as long as you choose avchd mode.

[rack04]

I have yet to try it, but there's two modes now. According to the release notes, if you're buring to a dvd you need to use avchd mode, not bluray mode. bluray mode is only for burning to actual bluray discs. Not sure if that's the issue you're having or not though.

EDIT : Just tried it. Confirmed that tsMuxer 1.8.35(b) works just fine with a bd-35 as long as you choose avchd mode.

Ohh, that's why. I chose blu-ray. Any idea why blu-ray output doesn't work?

[alc0re]

bluray output is meant for when you burn this stuff to an actual recordable bluray disc. I'm not sure if its in this thread or not, but panasonic's bd-35 and a few other players from both panasonic and other companies will only play this content on a recordable dvd if its output in a specific way that makes the player think its an avchd disc. You could see what I mean if you download the clipinf editor tool from the same guy that does the clown bd program. You can actually use that tool to change at least one part of tsMuxer's output that identifies it as an avchd and change it to bluray or vice-versa. I wouldn't suggest you change it though if you want it to work, just a tool that you could use to see what I mean.

[rack04]

bluray output is meant for when you burn this stuff to an actual recordable bluray disc. I'm not sure if its in this thread or not, but panasonic's bd-35 and a few other players from both panasonic and other companies will only play this content on a recordable dvd if its output in a specific way that makes the player think its an avchd disc. You could see what I mean if you download the clipinf editor tool from the same guy that does the clown bd program. You can actually use that tool to change at least one part of tsMuxer's output that identifies it as an avchd and change it to bluray or vice-versa. I wouldn't suggest you change it though if you want it to work, just a tool that you could use to see what I mean.

When/why was this changed? Up until recently blu-ray output worked with my BD-35. Now I must select AVCHD.

[MadMonkey57]

In previous versions of tsmuxer, the "Blu Ray output" was actually an AVCHD/BD output.

Now, tsmuxer is capable of producing 2 outputs:

- "Blu Ray": 100% BD compliant, ment to be burnt on BD media (very few SAP will read the output on DVD media)
- "AVCHD": the usual AVCHD/BD stuff

[MadMonkey57]

...
[x] First playback [Interactive] [2]
[x] Top Menu [1]

Title [1]: HDTV / Permitted / OID #0
---
ObjectID: (all with suspend/enabled/enabled for resume/menucall/titlesearch)

[000]
Play PL_MK 0,0
BREAK

[001]
Jump Title 1

[002]
SetStream $8001C001
Jump Title 0

Hey deank,

Just wanted to let you know that I tried this and it works like a charm. Thanks pal.

[deank]

:) I'm glad.

I don't know if you noticed - there is a FW update (ver 1.4) for BD35/55 on Panasonic's web page:

More... (http://panasonic.jp/support/global/cs/bd/index.html)

[MadMonkey57]

:) I'm glad.

I don't know if you noticed - there is a FW update (ver 1.4) for BD35/55 on Panasonic's web page:

More... (http://panasonic.jp/support/global/cs/bd/index.html)

Thanks for the heads up!

[alc0re]

:) I'm glad.

I don't know if you noticed - there is a FW update (ver 1.4) for BD35/55 on Panasonic's web page:

More... (http://panasonic.jp/support/global/cs/bd/index.html)

Notes state "BD-V Playability"

What is BD-V? (Sorry if that's a stupid question...sounds to me like BD-Video...but I still don't know what the firmware fixes/enhances.)

[deank]

I can see that panasonic uses this way of saying that they addressed some problems with some commercial BD discs.

Previous updates are similar (for BD30):

Improvements
1. AVCHD and BD-V Playability
1. BD-V Playability
1. Playability and Stability
1. BD-V(24p) Playability
1. BD-V(PiP) Playability
2. HDMI Compatibility
3. Audio output level (Low Frequency Effect) improvement
1. BD-V Playability
2. DVD-RW Playability
1. Playability and Stability

[rack04]

I just tried to play a AVCHD that was authored using tsMuxeR 1.10.6. The 1280x720 h.264 stream was encoded using x264 --preset slower. I specified --level 4.1 which made the stream have ref=8. According to the profile this is an acceptable ref frame number. Has anyone has any problems playing 1280x720 with 8 ref frames? As far as I can tell that was the only difference in the encodes. The one with 5 ref frames works fine. Thanks.

[deank]

Try to encode it with --trellis 0, --bframes 4 and may be it is a good idea to explicitly set --keyint to 24 (or 25... depends on your source).
This works just fine in Playstation3 (1280x720@23,976fps)


Encoding settings : cabac=1 / ref=8 / deblock=1:0:0 / analyse=0x3
:0x113 / me=hex / subme=5 / psy=1 / psy_rd=0.0:0.0 / mixed_ref=1 / me_range=12 /
chroma_me=1 / trellis=0 / 8x8dct=1 / cqm=0 / deadzone=21,11 / chroma_qp_offset=
0 / threads=3 / nr=0 / decimate=1 / mbaff=0 / bframes=4 / b_pyramid=0 / b_adapt=
1 / b_bias=0 / direct=1 / wpredb=1 / keyint=24 / keyint_min=1 / scenecut=40 / rc
_lookahead=24 / rc=cbr / mbtree=1 / bitrate=2435 / ratetol=1.0 / qcomp=0.50 / qp
min=10 / qpmax=51 / qpstep=4 / vbv_maxrate=30000 / vbv_bufsize=30000 / ip_ratio=
1.10 / aq=1:1.00