0.9.5 Encodes Lock up Classic Apple TV

General questions or discussion about HandBrake, Video and/or audio transcoding, trends etc.
dad2ways
Posts: 13
Joined: Mon Dec 28, 2009 8:16 pm

0.9.5 Encodes Lock up Classic Apple TV

Post by dad2ways »

I will post an activity log when I get a chance to get back to my Desktop Mac where all of my encoding is done.

Here is the problem:

Videos encoded with Handbrake 0.9.5 cause Classic Apple TVs to lock up and reset. The scenario goes like this:

1. Select video to watch
2. The screen goes black and audio starts (no video is ever displayed on screen)
3. Audio plays for a few seconds and then everything stops.
4. After a few seconds the Apple TV resets and restarts in Recovery Mode.
5. Apple TV built-in diagnostics indicate there are no hardware or software defects.
6. After rebooting the Apple TV the problem persists.
7. Videos perform as expected on computers and new Apple devices with an A4 processor.

Note: all other video content performs as expected (ITMS purchases and video encoded with previous versions of Handbrake). Re-encoding the video does not affect any change. Many other users have reported the same errors.
mduell
Veteran User
Posts: 7329
Joined: Sat Apr 21, 2007 8:54 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by mduell »

Forum rules
Activity Log
is required for support requests. See Must Read: How To Get Questions Answered on These Forums for details.

Rodeo even told you to post one in the other thread that prompted you to start this one. There's no point in posting a stub thread without one. It's not like forum posts are being rationed and may run out.
dad2ways wrote:Many other users have reported the same errors.
Any funny enough, it's almost always due to a custom preset that the user failed to update.
User avatar
Rodeo
HandBrake Team
Posts: 12679
Joined: Tue Mar 03, 2009 8:55 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by Rodeo »

dad2ways wrote:Many other users have reported the same errors.
That is correct. Why do you think we need an additional topic about this? Couldn't you have posted this in an existing topic? Have you bothered to check the suggestions in the other topics? Where is your Activity Log?
dad2ways
Posts: 13
Joined: Mon Dec 28, 2009 8:16 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by dad2ways »

Yes I read the other thread and Someone from the tech support team had requested that the discussion be started on a new topic, not in the general 0.9.5 discussion thread, so I did as they requested.
dad2ways
Posts: 13
Joined: Mon Dec 28, 2009 8:16 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by dad2ways »

dad2ways wrote:I will post an activity log when I get a chance to get back to my Desktop Mac where all of my encoding is done.

Here is the problem:

Videos encoded with Handbrake 0.9.5 cause Classic Apple TVs to lock up and reset. The scenario goes like this:

1. Select video to watch
2. The screen goes black and audio starts (no video is ever displayed on screen)
3. Audio plays for a few seconds and then everything stops.
4. After a few seconds the Apple TV resets and restarts in Recovery Mode.
5. Apple TV built-in diagnostics indicate there are no hardware or software defects.
6. After rebooting the Apple TV the problem persists.
7. Videos perform as expected on computers and new Apple devices with an A4 processor.

Note: all other video content performs as expected (ITMS purchases and video encoded with previous versions of Handbrake). Re-encoding the video does not affect any change. Many other users have reported the same errors.
mduell wrote:Forum rules
Activity Log is required for support requests. See Must Read: How To Get Questions Answered on These Forums for details.

Rodeo even told you to post one in the other thread that prompted you to start this one. There's no point in posting a stub thread without one. It's not like forum posts are being rationed and may run out.
Rodeo wrote:That is correct. Why do you think we need an additional topic about this? Couldn't you have posted this in an existing topic? Have you bothered to check the suggestions in the other topics? Where is your Activity Log?.
dad2ways wrote:Yes I read the other thread and Someone from the tech support team had requested that the discussion be started on a new topic, not in the general 0.9.5 discussion thread, so I did as they requested.
As I stated I was away from my desktop computer where all of my encoding is done. I also stated that I would add the missing log ASAP. Here is the activity log, which I don't think will be of much good, since Handbrake did not encounter an error. The error only occurs on Classic Apple TV boxes, which do not have any such logs. I have also included the encode log which will probably be of more use.

Activity Log:

[14:21:11] hb_init: checking cpu count
[14:21:11] hb_init: starting libhb thread
[14:21:11] macgui: Handbrake Version: 0.9.5 i386 (2011010300)
[14:21:11] hb_init: checking cpu count
[14:21:11] hb_init: starting libhb thread
[14:21:11] hb_init: checking cpu count
[14:21:11] hb_init: starting libhb thread
[14:21:14] macgui: hbInstances path to this instance: /Applications/HandBrake-0.9.4-MacOSX.5_GUI_i386/HandBrake.app
[14:21:14] macgui: hbInstance found instance pidnum:2192 at path: /Applications/HandBrake-0.9.4-MacOSX.5_GUI_i386/HandBrake.app
[14:21:14] macgui: hbInstance MATCH FOUND, our pidnum is:2192
[14:21:14] macgui: Pid for this instance:2192
[14:21:14] macgui: HBQueueController : My Pidnum is 2192


Encode Log:

HandBrake Activity Log for /Volumes/Media 2TB/Movies/Action/The A-Team.m4v: 2011-01-14 23:41:30 -0700
Handbrake Version: 0.9.5 i386 (2011010300)

[23:41:30] macgui: Rip: Pending queue count is 1
[23:41:30] macgui: getNextPendingQueueIndex next pending encode index is:1
[23:41:30] macgui: scanning specifically for title: 1
[23:41:30] hb_scan: path=/Volumes/Projects/RIPS/MPEG RIP/The A-Team, title_index=1
libbluray/bdnav/index_parse.c:157: indx_parse(): error opening /Volumes/Projects/RIPS/MPEG RIP/The A-Team/BDMV/index.bdmv
libbluray/bluray.c:960: nav_get_title_list(/Volumes/Projects/RIPS/MPEG RIP/The A-Team) failed (0x2952400)
[23:41:30] bd: not a bd - trying as a stream/file instead
libdvdnav: Using dvdnav version 4.1.3
libdvdread: Using libdvdcss version 1.2.10 for DVD access
libdvdread: Couldn't find device name.
libdvdnav: Can't read name block. Probably not a DVD-ROM device.
libdvdnav: Unable to find map file '/Users/John/.dvdnav/.map'
libdvdnav: DVD disk reports itself with Region mask 0x00fe0000. Regions: 1
libdvdread: Using libdvdcss version 1.2.10 for DVD access
libdvdread: Couldn't find device name.
libdvdread: *C_ADT nr_of_vobs > avaiable info entries

*** libdvdread: CHECK_VALUE failed in ifo_read.c:1594 ***
*** for c_adt->cell_adr_table.vob_id <= c_adt->nr_of_vobs ***


*** libdvdread: CHECK_VALUE failed in ifo_read.c:1594 ***
*** for c_adt->cell_adr_table.vob_id <= c_adt->nr_of_vobs ***

[23:41:31] scan: DVD has 10 title(s)
[23:41:31] scan: scanning title 1
[23:41:31] scan: opening IFO for VTS 6
[23:41:31] scan: duration is 01:58:40 (7120043 ms)
[23:41:31] pgc_id: 1, pgn: 1: pgc: 0x20c77880
[23:41:31] scan: vts=6, ttn=1, cells=0->48, blocks=0->2550431, 2550432 blocks
[23:41:31] scan: checking audio 1
[23:41:31] scan: id=80bd, lang=English (AC3), 3cc=eng ext=1
[23:41:31] scan: checking audio 2
[23:41:31] scan: id=81bd, lang=Espanol (AC3), 3cc=spa ext=1
[23:41:31] scan: checking audio 3
[23:41:31] scan: id=82bd, lang=Francais (AC3), 3cc=fra ext=1
[23:41:31] scan: checking subtitle 1
[23:41:31] scan: id=21bd, lang=English (Closed Caption), 3cc=eng
[23:41:31] scan: checking subtitle 2
[23:41:31] scan: id=23bd, lang=Espanol, 3cc=spa
[23:41:31] scan: checking subtitle 3
[23:41:31] scan: id=25bd, lang=Espanol, 3cc=spa
[23:41:31] scan: checking subtitle 4
[23:41:31] scan: id=27bd, lang=Francais, 3cc=fra
[23:41:31] scan: title 1 has 21 chapters
[23:41:31] scan: chap 1 c=0->0, b=0->125348 (125349), 317917 ms
[23:41:31] scan: chap 2 c=1->4, b=125349->284202 (158854), 415564 ms
[23:41:31] scan: chap 3 c=5->6, b=284203->443543 (159341), 427349 ms
[23:41:31] scan: chap 4 c=7->8, b=443544->563392 (119849), 321279 ms
[23:41:31] scan: chap 5 c=9->12, b=563393->698721 (135329), 386337 ms
[23:41:31] scan: chap 6 c=13->15, b=698722->849199 (150478), 432528 ms
[23:41:31] scan: chap 7 c=16->17, b=849200->934895 (85696), 232902 ms
[23:41:31] scan: chap 8 c=18->19, b=934896->1054388 (119493), 338175 ms
[23:41:31] scan: chap 9 c=20->22, b=1054389->1144922 (90534), 263952 ms
[23:41:31] scan: chap 10 c=23->25, b=1144923->1245483 (100561), 280368 ms
[23:41:31] scan: chap 11 c=26->26, b=1245484->1364876 (119393), 336996 ms
[23:41:31] scan: chap 12 c=27->28, b=1364877->1525188 (160312), 466431 ms
[23:41:31] scan: chap 13 c=29->32, b=1525189->1653921 (128733), 342224 ms
[23:41:31] scan: chap 14 c=33->33, b=1653922->1757280 (103359), 292992 ms
[23:41:31] scan: chap 15 c=34->35, b=1757281->1807515 (50235), 146398 ms
[23:41:31] scan: chap 16 c=36->37, b=1807516->1905372 (97857), 276954 ms
[23:41:31] scan: chap 17 c=38->39, b=1905373->2038814 (133442), 378895 ms
[23:41:31] scan: chap 18 c=40->41, b=2038815->2200218 (161404), 456440 ms
[23:41:31] scan: chap 19 c=42->44, b=2200219->2401153 (200935), 572579 ms
[23:41:31] scan: chap 20 c=45->47, b=2401154->2550426 (149273), 433577 ms
[23:41:31] scan: chap 21 c=48->48, b=2550427->2550431 (5), 176 ms
[23:41:31] scan: aspect = 0
[23:41:31] scan: decoding previews for title 1
libdvdnav: DVD disk reports itself with Region mask 0x00fe0000. Regions: 1
libdvdnav: Suspected RCE Region Protection!!!
libdvdnav: Suspected RCE Region Protection!!!
[23:41:31] scan: title angle(s) 1
[23:41:31] scan: audio 0x81bd: AC-3, rate=48000Hz, bitrate=192000 Espanol (AC3) (Dolby Surround)
[23:41:31] scan: audio 0x82bd: AC-3, rate=48000Hz, bitrate=192000 Francais (AC3) (Dolby Surround)
[23:41:31] scan: audio 0x80bd: AC-3, rate=48000Hz, bitrate=448000 English (AC3) (5.1 ch)
[23:41:31] scan: 10 previews, 720x480, 23.976 fps, autocrop = 54/58/0/2, aspect 16:9, PAR 32:27
[23:41:31] scan: title (0) job->width:720, job->height:304
[23:41:31] libhb: scan thread found 1 valid title(s)
[23:41:31] macgui: ScanDone state received from fQueueEncodeLibhb
[23:41:31] macgui: Preset: Default
[23:41:31] macgui: processNewQueueEncode number of passes expected is: 1
[23:41:31] macgui: Start / Stop set to chapters
[23:41:31] macgui: prepareJob exiting
[23:41:31] 1 job(s) to process
[23:41:31] starting job
[23:41:31] sync: expecting 170734 video frames
[ac3 @ 0x1ac3a00] No channel layout specified. The encoder will guess the layout, but it might be incorrect.
[23:41:31] job configuration:
[23:41:31] * source
[23:41:31] + /Volumes/Projects/RIPS/MPEG RIP/The A-Team
[23:41:31] + title 1, chapter(s) 1 to 21
[23:41:31] * destination
[23:41:31] + /Volumes/Media 2TB/Movies/Action/The A-Team.m4v
[23:41:31] + container: MPEG-4 (.mp4 and .m4v)
[23:41:31] + compatibility atom for iPod 5G
[23:41:31] + 64-bit formatting
[23:41:31] + chapter markers
[23:41:31] * video track
[23:41:31] + decoder: mpeg2
[23:41:31] + bitrate 9800 kbps
[23:41:31] + frame rate: same as source (around 23.976 fps)
[23:41:31] + loose anamorphic
[23:41:31] + storage dimensions: 720 * 480 -> 720 * 368, crop 54/58/0/2, mod 16
[23:41:31] + pixel aspect ratio: 1436 / 1215
[23:41:31] + display dimensions: 850 * 368
[23:41:31] + filter
[23:41:31] + Detelecine (pullup) (default settings)
[23:41:31] + encoder: x264
[23:41:31] + options: cabac=0:ref=2:me=umh:b-adapt=2:weightb=0:trellis=0:weightp=0
[23:41:31] + quality: 20.00 (RF)
[23:41:31] * audio track 0
[23:41:31] + decoder: English (AC3) (5.1 ch) (track 1, id 80bd)
[23:41:31] + bitrate: 448 kbps, samplerate: 48000 Hz
[23:41:31] + mixdown: Dolby Pro Logic II
[23:41:31] + dynamic range compression: 3.750000
[23:41:31] + encoder: ca_aac
[23:41:31] + bitrate: 256 kbps, samplerate: 48000 Hz
[23:41:31] * audio track 1
[23:41:31] + decoder: English (AC3) (5.1 ch) (track 1, id 80bd)
[23:41:31] + bitrate: 448 kbps, samplerate: 48000 Hz
[23:41:31] + AC3 passthrough
libdvdnav: Using dvdnav version 4.1.3
libdvdread: Using libdvdcss version 1.2.10 for DVD access
libdvdread: Couldn't find device name.
libdvdnav: Can't read name block. Probably not a DVD-ROM device.
libdvdnav: Unable to find map file '/Users/John/.dvdnav/.map'
libdvdnav: DVD disk reports itself with Region mask 0x00fe0000. Regions: 1
libdvdread: Using libdvdcss version 1.2.10 for DVD access
libdvdread: Couldn't find device name.
libdvdread: *C_ADT nr_of_vobs > avaiable info entries

*** libdvdread: CHECK_VALUE failed in ifo_read.c:1594 ***
*** for c_adt->cell_adr_table.vob_id <= c_adt->nr_of_vobs ***


*** libdvdread: CHECK_VALUE failed in ifo_read.c:1594 ***
*** for c_adt->cell_adr_table.vob_id <= c_adt->nr_of_vobs ***

libdvdnav: DVD disk reports itself with Region mask 0x00fe0000. Regions: 1
libdvdnav: Suspected RCE Region Protection!!!
libdvdnav: Suspected RCE Region Protection!!!
[23:41:31] encx264: min-keyint: auto (23), keyint: 240
[23:41:31] encx264: encoding with stored aspect 1436/1215
[23:41:31] encx264: Encoding at constant RF 20.000000
x264 [info]: using SAR=1436/1215
x264 [info]: using cpu capabilities: MMX2 Cache64
[23:41:31] reader: first SCR 146 id 224 DTS 14629
x264 [info]: profile High, level 3.0
No accelerated IMDCT transform found
[23:41:31] mpeg2: "Chapter 1" (1) at frame 0 time 3003
No accelerated IMDCT transform found
[23:51:18] mpeg2: "Chapter 2" (2) at frame 7612 time 28576548
[23:57:55] 522.755554s: Film -> Video
[23:57:56] 523.222717s: Video -> Film
[00:06:02] mpeg2: "Chapter 3" (3) at frame 17604 time 66072006
[00:07:24] 770.970215s: Film -> Video
[00:07:25] 771.437317s: Video -> Film
[00:22:51] mpeg2: "Chapter 4" (4) at frame 27870 time 104597493
[00:36:13] mpeg2: "Chapter 5" (5) at frame 35578 time 133531398
[00:45:45] 1730.462036s: Film -> Video
[00:45:46] 1730.929199s: Video -> Film
[00:50:43] mpeg2: "Chapter 6" (6) at frame 44878 time 168429261
[00:51:02] 1881.579712s: Film -> Video
[00:51:03] 1882.046753s: Video -> Film
[01:05:55] mpeg2: "Chapter 7" (7) at frame 55268 time 207420213
[01:10:59] 2438.669434s: Film -> Video
[01:11:01] 2439.136719s: Video -> Film
[01:14:18] mpeg2: "Chapter 8" (8) at frame 60863 time 228411183
[01:25:39] mpeg2: "Chapter 9" (9) at frame 68968 time 258834576
[01:27:54] 2946.176514s: Film -> Video
[01:27:55] 2946.643799s: Video -> Film
[01:34:31] mpeg2: "Chapter 10" (10) at frame 75314 time 282645363
[01:37:17] 3214.477783s: Film -> Video
[01:37:19] 3214.961670s: Video -> Film
[01:44:23] mpeg2: "Chapter 11" (11) at frame 82061 time 307962309
[01:57:25] mpeg2: "Chapter 12" (12) at frame 90130 time 338250567
[02:11:28] mpeg2: "Chapter 13" (13) at frame 101321 time 380259534
[02:20:26] 4465.846191s: Film -> Video
[02:20:27] 4466.313477s: Video -> Film
[02:24:15] mpeg2: "Chapter 14" (14) at frame 109557 time 411163407
[02:32:34] mpeg2: "Chapter 15" (15) at frame 116572 time 437496714
[02:33:43] 4902.182617s: Film -> Video
[02:33:44] 4902.666504s: Video -> Film
[02:36:54] mpeg2: "Chapter 16" (16) at frame 120096 time 450712917
[02:46:12] mpeg2: "Chapter 17" (17) at frame 126727 time 475604784
[02:57:38] mpeg2: "Chapter 18" (18) at frame 135799 time 509658804
[02:58:13] 5682.761719s: Film -> Video
[02:58:15] 5683.229004s: Video -> Film
[03:12:45] mpeg2: "Chapter 19" (19) at frame 146754 time 550769874
[03:22:28] 6456.501953s: Film -> Video
[03:22:30] 6456.969238s: Video -> Film
[03:30:22] mpeg2: "Chapter 20" (20) at frame 160513 time 602406459
[03:38:24] 7125.036133s: Film -> Video
[03:38:25] reader: done. 2 scr changes
[03:38:25] 7125.520508s: Video -> Film
[03:38:25] mpeg2: "Chapter 21" (21) at frame 170912 time 641430444
[03:38:27] work: average encoding speed for job is 12.022612 fps
[03:38:27] sync: got 170914 frames, 170734 expected
[03:38:27] mpeg2 done: 170914 frames
[03:38:27] render: lost time: 135135 (45 frames)
[03:38:27] render: gained time: 135135 (176 frames) (0 not accounted for)
[03:38:27] render: average dropped frame duration: 3003
x264 [info]: frame I:2553 Avg QP:17.16 size: 32177 PSNR Mean Y:46.10 U:49.78 V:50.04 Avg:46.93 Global:46.55
x264 [info]: frame P:52672 Avg QP:20.97 size: 9342 PSNR Mean Y:44.31 U:49.41 V:49.12 Avg:45.19 Global:44.29
x264 [info]: frame B:115644 Avg QP:24.11 size: 2873 PSNR Mean Y:42.82 U:48.85 V:48.46 Avg:43.82 Global:43.23
x264 [info]: consecutive B-frames: 3.1% 7.4% 26.0% 63.6%
x264 [info]: mb I I16..4: 9.3% 57.0% 33.8%
x264 [info]: mb P I16..4: 4.0% 9.1% 4.3% P16..4: 38.0% 19.7% 7.5% 0.0% 0.0% skip:17.3%
x264 [info]: mb B I16..4: 0.4% 1.2% 0.6% B16..8: 41.0% 8.9% 1.4% direct: 3.7% skip:42.8% L0:38.2% L1:51.3% BI:10.5%
x264 [info]: 8x8 transform intra:53.4% inter:54.2%
x264 [info]: coded y,uvDC,uvAC intra: 69.5% 73.6% 42.9% inter: 13.5% 13.8% 1.4%
x264 [info]: i16 v,h,dc,p: 38% 24% 6% 32%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 19% 15% 17% 6% 8% 10% 8% 9% 8%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 25% 18% 13% 6% 9% 9% 7% 7% 5%
x264 [info]: i8c dc,h,v,p: 48% 19% 24% 9%
x264 [info]: ref P L0: 71.7% 28.3%
x264 [info]: ref B L0: 87.0% 13.0%
x264 [info]: ref B L1: 93.4% 6.6%
x264 [info]: SSIM Mean Y:0.9805398 (17.109db)
x264 [info]: PSNR Mean Y:43.326 U:49.038 V:48.689 Avg:44.288 Global:43.567 kb/s:1017.54
[03:38:28] mux: track 0, 170869 frames, 906398833 bytes, 1017.41 kbps, fifo 8
[03:38:28] mux: track 1, 334079 frames, 234422692 bytes, 263.13 kbps, fifo 512
[03:38:28] mux: track 2, 222719 frames, 399112448 bytes, 448.00 kbps, fifo 256
[03:38:28] libhb: work result = 0
Last edited by dad2ways on Sat Jan 15, 2011 9:22 pm, edited 3 times in total.
User avatar
Rodeo
HandBrake Team
Posts: 12679
Joined: Tue Mar 03, 2009 8:55 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by Rodeo »

dad2ways wrote:Yes I read the other thread and Someone from the tech support team had requested that the discussion be started on a new topic, not in the general 0.9.5 discussion thread, so I did as they requested.
That's still no reason for not providing a log.

Edit: OK now there is a log. Thanks :-)
dad2ways
Posts: 13
Joined: Mon Dec 28, 2009 8:16 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by dad2ways »

Rodeo wrote:
dad2ways wrote:Yes I read the other thread and Someone from the tech support team had requested that the discussion be started on a new topic, not in the general 0.9.5 discussion thread, so I did as they requested.
That's still no reason for not providing a log.
How could there be any possible way to provide a log that exists on a computer that I did not have access to at that moment. I stated that I did not have a log to submit but would provide it as soon as possible. Besides, the activity log indicates that everything processed without error, so how would that do any good. The Apple TV does not provide such a log to be included. I gave enough information to provide guidance to what was going wrong. A little patience is all that was needed. I didn't need to harassed about not providing a log. Is this that unforgiving of a place? You have designed a product that is simple for the naive end user to utilize. While I am not one of those, you shouldn't be such a dilettante about following your rules to the 'T' before qualifying a error report.

Besides, I was not asking for technical support. I was only reporting an error I experienced and I was the only one to do as you requested and start a new topic. Guess I won't make that mistake again. :|
thompson
Bright Spark User
Posts: 356
Joined: Sat Dec 12, 2009 8:04 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by thompson »

dad2ways wrote:How could there be any possible way to provide a log that exists on a computer that I did not have access to at that moment. I stated that I did not have a log to submit but would provide it as soon as possible.
Then don't start a thread until you have access to it, because nothing can be done until you provide one.
dad2ways wrote:Besides, the activity log indicates that everything processed without error, so how would that do any good.
Your settings are likely causing the crash. The encode log tells us what settings you used.
dad2ways wrote:I gave enough information to provide guidance to what was going wrong. A little patience is all that was needed.
No, you didn't. Without an encode log we have no idea what you are doing wrong.
dad2ways wrote:I didn't need to harassed about not providing a log. Is this that unforgiving of a place? You have designed a product that is simple for the naive end user to utilize. While I am not one of those, you shouldn't be such a dilettante about following your rules to the 'T' before qualifying a error report.
Apparently you did need to be reminded, because your initial post failed to include a log as required by the forum rules. Without a log we cannot diagnose what is going wrong, so there is simply NO POINT in posting a question before you can provide the log.

Code: Select all

options: cabac=0:ref=2:me=umh:b-adapt=2:weightb=0:trellis=0:weightp=0
Where did you get that options string? It's not the Apple TV preset and, for example, failed to disable b-pyramid. If this was a custom preset that you had before 0.9.5 it must be recreated from scratch as default options change version to version. You're better off just using the built-in Apple TV preset which IS updated from version to version.
User avatar
Rodeo
HandBrake Team
Posts: 12679
Joined: Tue Mar 03, 2009 8:55 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by Rodeo »

dad2ways wrote:
Rodeo wrote:
dad2ways wrote:Yes I read the other thread and Someone from the tech support team had requested that the discussion be started on a new topic, not in the general 0.9.5 discussion thread, so I did as they requested.
That's still no reason for not providing a log.

Edit: OK now there is a log. Thanks :-)
How could there be any possible way to provide a log that exists on a computer that I did not have access to at that moment. I stated that I did not have a log to submit but would provide it as soon as possible.
My post was a reply to your post from today (which still didn't include a log), not the original post. It just turns out you provided the log in a following post.
dad2ways wrote:Besides, the activity log indicates that everything processed without error, so how would that do any good. The Apple TV does not provide such a log to be included. I gave enough information to provide guidance to what was going wrong.
No, you did not! Unbelievable. How can you expect us to determine what's causing the issue when you don't even tell us what settings you're using? For all we know you were encoding Theora video and Vorbis audio to an MKV container.
dad2ways wrote:You have designed a product that is simple for the naive end user to utilize. While I am not one of those
I beg to differ. You don't even realize that different settings can affect device compatibility.
Besides, I was not asking for technical support. I was only reporting an error I experienced and I was the only one to do as you requested and start a new topic. Guess I won't make that mistake again.
No, there is at least one other topic about it. It contains the solution to your problem. Which thompson just provided (I wish he hadn't, then you could have experimented with forum search).

Your advanced options are that of HandBrake 0.9.4's built-in AppleTV preset. The built-in presets get updated automatically. Updating your own custom presets is your responsibility. All you need to do is to use the current AppleTV preset's advanced options in your preset.
User avatar
s55
HandBrake Team
Posts: 9900
Joined: Sun Dec 24, 2006 1:05 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by s55 »

Are these AppleTV's running the latest Take2 Software Updates?

Also, to be safe, can you do "Presets Menu" -> "Update built-in presets" to make sure those presets are not somehow broken.
tlindgren
Bright Spark User
Posts: 245
Joined: Sun May 03, 2009 2:14 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by tlindgren »

dad2ways wrote:Videos encoded with Handbrake 0.9.5 cause Classic Apple TVs to lock up and reset.

Code: Select all

cabac=0:ref=2:me=umh:b-adapt=2:weightb=0:trellis=0:weightp=0
That's not the AppleTV preset! It's similar but missing three very specific options required for making it compatible with the AppleTV (Classic)...

If you want to create your own preset for AppleTV you need to know what you're doing, don't blame Handbrake for following your specific instructions and creating something that doesn't work on an AppleTV.
mduell
Veteran User
Posts: 7329
Joined: Sat Apr 21, 2007 8:54 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by mduell »

dad2ways wrote:Yes I read the other thread and Someone from the tech support team had requested that the discussion be started on a new topic, not in the general 0.9.5 discussion thread, so I did as they requested.
No, he didn't tell you to start a new thread. He just told you not to post in the 0.9.5 discussion thread. One of the first things pointed out in the "Must Read: How To Get Questions Answered on These Forums" document is to search before posting.

Stop lying and start reading.
dad2ways wrote:Here is the activity log, which I don't think will be of much good, since Handbrake did not encounter an error. The error only occurs on Classic Apple TV boxes, which do not have any such logs. I have also included the encode log which will probably be of more use.
The problem is usually the user, not HandBrake, so lack of errors in the HB log is not indicative of anything.
dad2ways wrote:How could there be any possible way to provide a log that exists on a computer that I did not have access to at that moment.
Why was it so urgent to start a new thread instead of searching the forum for your issue (as recommended) or at least waiting until you could provide all of the relevant information?
dad2ways wrote:I stated that I did not have a log to submit but would provide it as soon as possible. Besides, the activity log indicates that everything processed without error, so how would that do any good. The Apple TV does not provide such a log to be included. I gave enough information to provide guidance to what was going wrong. A little patience is all that was needed. I didn't need to harassed about not providing a log. Is this that unforgiving of a place? You have designed a product that is simple for the naive end user to utilize. While I am not one of those, you shouldn't be such a dilettante about following your rules to the 'T' before qualifying a error report.
You don't read the directions, you don't follow the rules, and you didn't provide enough information.
dad2ways wrote:Besides, I was not asking for technical support. I was only reporting an error I experienced and I was the only one to do as you requested and start a new topic. Guess I won't make that mistake again. :|
What were you looking for, someone to hold your hand and sing kumbaya?
thompson wrote:

Code: Select all

options: cabac=0:ref=2:me=umh:b-adapt=2:weightb=0:trellis=0:weightp=0
Where did you get that options string? It's not the Apple TV preset and, for example, failed to disable b-pyramid. If this was a custom preset that you had before 0.9.5 it must be recreated from scratch as default options change version to version. You're better off just using the built-in Apple TV preset which IS updated from version to version.
I'm shocked. Oh, nope, wait, someone predicted that a half dozen posts ago...
mduell wrote:Any funny enough, it's almost always due to a custom preset that the user failed to update.
Last edited by mduell on Sat Jan 15, 2011 10:05 pm, edited 2 times in total.
thompson
Bright Spark User
Posts: 356
Joined: Sat Dec 12, 2009 8:04 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by thompson »

Rodeo wrote:Which thompson just provided (I wish he hadn't, then you could have experimented with forum search).
The long weekend must bring out the kindness in me... ;)
User avatar
Rodeo
HandBrake Team
Posts: 12679
Joined: Tue Mar 03, 2009 8:55 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by Rodeo »

tlindgren wrote:
dad2ways wrote:Videos encoded with Handbrake 0.9.5 cause Classic Apple TVs to lock up and reset.

Code: Select all

cabac=0:ref=2:me=umh:b-adapt=2:weightb=0:trellis=0:weightp=0
That's not the AppleTV preset! It's similar but missing three very specific options required for making it compatible with the AppleTV (Classic)...

If you want to create your own preset for AppleTV you need to know what you're doing, don't blame Handbrake for following your specific instructions and creating something that doesn't work on an AppleTV.
To be fair, this used to be the AppleTV preset's advanced options (in 0.9.4). He just needs to update his custom presets every year or so.
dad2ways
Posts: 13
Joined: Mon Dec 28, 2009 8:16 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by dad2ways »

s55 wrote:Are these AppleTV's running the latest Take2 Software Updates?

Also, to be safe, can you do "Presets Menu" -> "Update built-in presets" to make sure those presets are not somehow broken.
No. They have not had a software update in over a year. The Take2 software updates are only available to the new Apple TV with an A4 processor.
mduell
Veteran User
Posts: 7329
Joined: Sat Apr 21, 2007 8:54 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by mduell »

dad2ways, you'd probably receive a lot nicer response if you weren't so rude coming in and [censored] all over the forum without reading up on the issue first or even how to get help.
dad2ways wrote:
s55 wrote:Are these AppleTV's running the latest Take2 Software Updates?

Also, to be safe, can you do "Presets Menu" -> "Update built-in presets" to make sure those presets are not somehow broken.
No. They have not had a software update in over a year. The Take2 software updates are only available to the new Apple TV with an A4 processor.
I don't even know what you're drooling about here. Take Two was a software update to the original Apple TV with an Intel processor.
Last edited by mduell on Sat Jan 15, 2011 10:09 pm, edited 1 time in total.
dad2ways
Posts: 13
Joined: Mon Dec 28, 2009 8:16 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by dad2ways »

Rodeo wrote:
tlindgren wrote:
dad2ways wrote:Videos encoded with Handbrake 0.9.5 cause Classic Apple TVs to lock up and reset.

Code: Select all

cabac=0:ref=2:me=umh:b-adapt=2:weightb=0:trellis=0:weightp=0
That's not the AppleTV preset! It's similar but missing three very specific options required for making it compatible with the AppleTV (Classic)...

If you want to create your own preset for AppleTV you need to know what you're doing, don't blame Handbrake for following your specific instructions and creating something that doesn't work on an AppleTV.
To be fair, this used to be the AppleTV preset's advanced options (in 0.9.4). He just needs to update his custom presets every year or so.
No, those settings work fine with videos encoded with 0.9.4. The Apple TV preset does not provide the quality encode I need. That preset was producing very flat and sometimes blurry output.
dad2ways
Posts: 13
Joined: Mon Dec 28, 2009 8:16 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by dad2ways »

mduell wrote:dad2ways, you'd probably receive a lot nicer response if you weren't so rude.
I didn't start the rudeness. What you perceive as rudeness was a reflection in kind to the replies that were received. Just as I am sure you probably didn't perceive rudeness in your replies, I was careful to tone down my responses. I even edited them multiple times.
mduell
Veteran User
Posts: 7329
Joined: Sat Apr 21, 2007 8:54 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by mduell »

Your very first post was rude because it reflected a lack of respect for the forum: starting yet another thread on an already covered issue, failing to provide all necessary information (which is clearly spelled out at the top of every forum page), etc.

In the end it's the usual story. Clueless user picking options they don't understand and then complaining it doesn't work instead of using the provided presets. :roll:
User avatar
Rodeo
HandBrake Team
Posts: 12679
Joined: Tue Mar 03, 2009 8:55 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by Rodeo »

dad2ways wrote:No. They have not had a software update in over a year. The Take2 software updates are only available to the new Apple TV with an A4 processor.
The "AppleTV Take 2" is the version 2.x software for the original, 1st generation AppleTV (or anything more recent, like version 3.x of the AppleTV 1 software).
dad2ways wrote:
Rodeo wrote:
tlindgren wrote:
dad2ways wrote:Videos encoded with Handbrake 0.9.5 cause Classic Apple TVs to lock up and reset.

Code: Select all

cabac=0:ref=2:me=umh:b-adapt=2:weightb=0:trellis=0:weightp=0
That's not the AppleTV preset! It's similar but missing three very specific options required for making it compatible with the AppleTV (Classic)...

If you want to create your own preset for AppleTV you need to know what you're doing, don't blame Handbrake for following your specific instructions and creating something that doesn't work on an AppleTV.
To be fair, this used to be the AppleTV preset's advanced options (in 0.9.4). He just needs to update his custom presets every year or so.
No, those settings work fine with videos encoded with 0.9.4. The Apple TV preset does not provide the quality encode I need. That preset was producing very flat and sometimes blurry output.
Yes, they work fine with 0.9.4, not 0.9.5. You need to update your advanced options for 0.9.5.

Also, they are the same advanced x264 options as HandBrake 0.9.4's AppleTV preset:

http://trac.handbrake.fr/browser/tags/0 ... BPresets.m (line 185)
dad2ways
Posts: 13
Joined: Mon Dec 28, 2009 8:16 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by dad2ways »

dad2ways wrote:I will post an activity log when I get a chance to get back to my Desktop Mac where all of my encoding is done.

Here is the problem:

Videos encoded with Handbrake 0.9.5 cause Classic Apple TVs to lock up and reset. The scenario goes like this:

1. Select video to watch
2. The screen goes black and audio starts (no video is ever displayed on screen)
3. Audio plays for a few seconds and then everything stops.
4. After a few seconds the Apple TV resets and restarts in Recovery Mode.
5. Apple TV built-in diagnostics indicate there are no hardware or software defects.
6. After rebooting the Apple TV the problem persists.
7. Videos perform as expected on computers and new Apple devices with an A4 processor.

Note: all other video content performs as expected (ITMS purchases and video encoded with previous versions of Handbrake). Re-encoding the video does not affect any change. Many other users have reported the same errors.
mduell wrote:Your very first post was rude because it reflected a lack of respect for the forum: starting yet another thread on an already covered issue, failing to provide all necessary information (which is clearly spelled out at the top of every forum page), etc.

In the end it's the usual story. Clueless user picking options they don't understand and then complaining it doesn't work instead of using the provided presets.  :roll:
Obviously, you are so stuck on the necessity of a log inclusion on anything other than a praise letter that you cannot read completely anything that does not include it.

I was not rude in that first post and I completely respected the forum rules. The following is a quote that is from that post:

"I will post an activity log when I get a chance to get back to my Desktop Mac where all of my encoding is done."

I most certainly did explain why I did not include the log to begin with and I did absolutely promise to post one as soon as possible and did as I promised.

And as far as starting a new thread on a subject already covered, one of the last posts I read on the general discussion forum included a request to start a new topic with this subject. I did not find that thread to add my voice to, so I started a new topic. For that I have experienced consistent rudeness, arrogance and condescension, quite a bit of it coming from you. How would you respond if you had done what was requested, respected the rules of the forum to the best of your ability, and then were rewarded with attack after attack when you came back to fully add your respect to the forum by adding log records, even though I was not making a support request?

As far as the comments about my settings you would do yourself a big favor if you check your attitude before you decide to correct someone else about theirs. Those settings have worked without error for a year using 0.9.4. I would understand your comment, sans the arrogance and condescension, if I were a first time user reporting a problem. Why such a stickler about log reports. I wasn't making a support request and I made sure and made it clear that it was missing and promised to provide ASAP. No matter what, even the fact that I was not with the computer that encoded the videos in question was not good enough. More than once I was told that this was not still a good enough reason for not including a log I didn't have access to. Was I supposed to fake one? I couldn't even pull one up from the device I was using, since there is not a version available for the iPad.

As for all of the comments concerning parameter strings, I don't access Handbrake from the Terminal, so why does anyone expect me to know what any of that cryptic info relates to. As far as not using the correct settings, the only deviation from the Apple TV preset I make are to select iPod 5G support, I change the audio bitrate from 160 to 256, I change the DRC from 0 to 3.75, and I change Detelecine from Off to Default. Everything else is the standard Apple TV preset settings. I created my own preset by first selecting the Apple TV preset and made the afore mentioned changes.

It is not a case of a user doing things they have no idea about and then blaming the software when things don't work. Did a lot of research before selecting those settings, both from the official user's manual and extensive outside research about what all of the settings mean and how they affect the resulting video output. As I already stated, the error did not occur the first time I used these settings. I have used these settings for at least a year with previous versions of Handbrake without incident.

If you don't want to receive "rudeness" in replies you should not be arrogant and condescending in yours.
thompson
Bright Spark User
Posts: 356
Joined: Sat Dec 12, 2009 8:04 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by thompson »

dad2ways wrote:I was not rude in that first post and I completely respected the forum rules. The following is a quote that is from that post:

"I will post an activity log when I get a chance to get back to my Desktop Mac where all of my encoding is done."

I most certainly did explain why I did not include the log to begin with and I did absolutely promise to post one as soon as possible and did as I promised.
Forum rules require an activity log, so the correct course of action would be to have waited until you had access to one before posting.
dad2ways wrote:How would you respond if you had done what was requested, respected the rules of the forum to the best of your ability, and then were rewarded with attack after attack when you came back to fully add your respect to the forum by adding log records, even though I was not making a support request?
You didn't follow the rules, see above. You then got defensive about it for no good reason. Look, we simply cannot help you unless you provide an activity log because we have no idea what is happening. Even if you didn't want help, your post was of no help to the developers without the log for the same reasons.
dad2ways wrote:As far as the comments about my settings you would do yourself a big favor if you check your attitude before you decide to correct someone else about theirs. Those settings have worked without error for a year using 0.9.4.
Emphasis added. As we have said earlier, doesn't mean that it will work in 0.9.5. The defaults have changed, which means that your presets must change in order to remain compatible with the Apple TV.
dad2ways wrote:I would understand your comment, sans the arrogance and condescension, if I were a first time user reporting a problem. Why such a stickler about log reports.
Because we can see exactly what you did wrong, which in this case was using an outdated preset that failed to disable Pyramidal B-Frames.
dad2ways wrote:As for all of the comments concerning parameter strings, I don't access Handbrake from the Terminal, so why does anyone expect me to know what any of that cryptic info relates to. As far as not using the correct settings, the only deviation from the Apple TV preset I make are to select iPod 5G support, I change the audio bitrate from 160 to 256, I change the DRC from 0 to 3.75, and I change Detelecine from Off to Default. Everything else is the standard Apple TV preset settings. I created my own preset by first selecting the Apple TV preset and made the afore mentioned changes.
Those settings are visible under the "Current x264 Advanced Options String:" box in the GUI, this has nothing to do with the terminal. For redundancy's sake, the problem is that your preset was created by modifying the OLD AppleTV preset from 0.9.4. That means that it is incompatible with 0.9.5. The things you changed are fine, they won't affect compatabiility, but you also must turn "Pyramidal B-Frames" to "Off". The better option though is to start with the AppleTV preset included with 0.9.5. You will be able to tell that you're working with the correct preset if, when you select it, that advanced options box looks like this:

Code: Select all

cabac=0:ref=2:me=umh:b-pyramid=none:b-adapt=2:weightb=0:trellis=0:weightp=0:vbv-maxrate=9500:vbv-bufsize=9500
Then you can turn off detelecine, change your audio bitrate, and modify the DRC. But you must start with that preset first in order to maintain the proper settings.
dad2ways wrote:It is not a case of a user doing things they have no idea about and then blaming the software when things don't work. Did a lot of research before selecting those settings, both from the official user's manual and extensive outside research about what all of the settings mean and how they affect the resulting video output. As I already stated, the error did not occur the first time I used these settings. I have used these settings for at least a year with previous versions of Handbrake without incident.
Because defaults have changed. As we've told you, and as we've told the countless others reporting problems with ATV encodes. You MUST start fresh from the AppleTV preset included with 0.9.5.
User avatar
Rodeo
HandBrake Team
Posts: 12679
Joined: Tue Mar 03, 2009 8:55 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by Rodeo »

dad2ways wrote:As far as the comments about my settings you would do yourself a big favor if you check your attitude before you decide to correct someone else about theirs. Those settings have worked without error for a year using 0.9.4. I would understand your comment, sans the arrogance and condescension, if I were a first time user reporting a problem. Why such a stickler about log reports. I wasn't making a support request and I made sure and made it clear that it was missing and promised to provide ASAP. No matter what, even the fact that I was not with the computer that encoded the videos in question was not good enough. More than once I was told that this was not still a good enough reason for not including a log I didn't have access to. Was I supposed to fake one? I couldn't even pull one up from the device I was using, since there is not a version available for the iPad.
You could have waited until you had the log before posting.

But more importantly, the only hint you gave us about what you were doing is that you were doing the same as in 0.9.4. Did you expect us to go through to 770 changes that were made to HandBrake since 0.9.4? Even what you posted just below would have helped a lot:
dad2ways wrote:As far as not using the correct settings, the only deviation from the Apple TV preset I make are to select iPod 5G support, I change the audio bitrate from 160 to 256, I change the DRC from 0 to 3.75, and I change Detelecine from Off to Default. Everything else is the standard Apple TV preset settings. I created my own preset by first selecting the Apple TV preset and made the afore mentioned changes.
You did this in 0.9.4. You need to update your custom preset for 0.9.5 (e.g. by going through the same procedure in 0.9.5 and creating a new custom preset). Settings change from version to version.

Also, the "iPod 5G support" checkbox adds an atom which is required for iPod 5G compatibility. It's only one part of the settings needed to achieve compatibility with the iPod 5G. Your encodes (even the 0.9.4 ones) will not work on your iPod, so you might as well not check it.
mduell
Veteran User
Posts: 7329
Joined: Sat Apr 21, 2007 8:54 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by mduell »

dad2ways wrote:Obviously, you are so stuck on the necessity of a log inclusion on anything other than a praise letter that you cannot read completely anything that does not include it.
When you're requesting support ("here is the problem") you need to provide an activity log so we can see what you're doing. Users claims about what they're doing can never be taken at face value.
Flame all you want without logs. Personally I think the GUIs are dog [Censored].
dad2ways wrote:And as far as starting a new thread on a subject already covered, one of the last posts I read on the general discussion forum included a request to start a new topic with this subject.
No, it didn't:
Rodeo wrote:This topic is not for support requests; also, you didn't provide an Activity Log.
dad2ways wrote:How would you respond if you had done what was requested, respected the rules of the forum to the best of your ability
That's a bizzare choice of hypotheticals, since you did no such thing.
dad2ways wrote:Those settings have worked without error for a year using 0.9.4.
And their compatibility with a year+ old release is relevant how?
dad2ways wrote:Why such a stickler about log reports.
Users cannot be believed to provide an accurate and complete reflection of the settings they chose.
dad2ways wrote:No matter what, even the fact that I was not with the computer that encoded the videos in question was not good enough. More than once I was told that this was not still a good enough reason for not including a log I didn't have access to. Was I supposed to fake one? I couldn't even pull one up from the device I was using, since there is not a version available for the iPad.
Why was it so urgent to get a post up (which was requested by no one) that you couldn't wait until you had all required information available?
dad2ways wrote:As for all of the comments concerning parameter strings, I don't access Handbrake from the Terminal, so why does anyone expect me to know what any of that cryptic info relates to.
"That cryptic info" is the result of the changes you made in the advanced tab.
dad2ways wrote:As far as not using the correct settings, the only deviation from the Apple TV preset I make are to select iPod 5G support, I change the audio bitrate from 160 to 256, I change the DRC from 0 to 3.75, and I change Detelecine from Off to Default. Everything else is the standard Apple TV preset settings. I created my own preset by first selecting the Apple TV preset and made the afore mentioned changes.
This is what I say about being unable to rely on users to provide accurate and complete information. You conveniently omit you're using presets from an old release.
dad2ways wrote:It is not a case of a user doing things they have no idea about and then blaming the software when things don't work. Did a lot of research before selecting those settings, both from the official user's manual and extensive outside research about what all of the settings mean and how they affect the resulting video output.
Guess you didn't do enough.
dad2ways
Posts: 13
Joined: Mon Dec 28, 2009 8:16 pm

Re: 0.9.5 Encodes Lock up Classic Apple TV

Post by dad2ways »

mduell wrote:
dad2ways wrote:Obviously, you are so stuck on the necessity of a log inclusion on anything other than a praise letter that you cannot read completely anything that does not include it.
When you're requesting support ("here is the problem") you need to provide an activity log so we can see what you're doing. Users claims about what they're doing can never be taken at face value.
Flame all you want without logs. Personally I think the GUIs are dog [Censored].
dad2ways wrote:And as far as starting a new thread on a subject already covered, one of the last posts I read on the general discussion forum included a request to start a new topic with this subject.
No, it didn't:
Rodeo wrote:This topic is not for support requests; also, you didn't provide an Activity Log.
dad2ways wrote:How would you respond if you had done what was requested, respected the rules of the forum to the best of your ability
That's a bizzare choice of hypotheticals, since you did no such thing.
dad2ways wrote:Those settings have worked without error for a year using 0.9.4.
And their compatibility with a year+ old release is relevant how?
dad2ways wrote:Why such a stickler about log reports.
Users cannot be believed to provide an accurate and complete reflection of the settings they chose.
dad2ways wrote:No matter what, even the fact that I was not with the computer that encoded the videos in question was not good enough. More than once I was told that this was not still a good enough reason for not including a log I didn't have access to. Was I supposed to fake one? I couldn't even pull one up from the device I was using, since there is not a version available for the iPad.
Why was it so urgent to get a post up (which was requested by no one) that you couldn't wait until you had all required information available?
dad2ways wrote:As for all of the comments concerning parameter strings, I don't access Handbrake from the Terminal, so why does anyone expect me to know what any of that cryptic info relates to.
"That cryptic info" is the result of the changes you made in the advanced tab.
dad2ways wrote:As far as not using the correct settings, the only deviation from the Apple TV preset I make are to select iPod 5G support, I change the audio bitrate from 160 to 256, I change the DRC from 0 to 3.75, and I change Detelecine from Off to Default. Everything else is the standard Apple TV preset settings. I created my own preset by first selecting the Apple TV preset and made the afore mentioned changes.
This is what I say about being unable to rely on users to provide accurate and complete information. You conveniently omit you're using presets from an old release.
dad2ways wrote:It is not a case of a user doing things they have no idea about and then blaming the software when things don't work. Did a lot of research before selecting those settings, both from the official user's manual and extensive outside research about what all of the settings mean and how they affect the resulting video output.
Guess you didn't do enough.
I was correct in my assessment of you. You cannot read a post completely before you begin firing off responses. I have never once requested support. I have been very clear to repeatedly make it clear that I was NOT requesting support. If you are going to do customer/user support, you need to make sure you understand what is being stated before you fire off solutions, corrections, or reprimands. I am not seeking support. I don't need your support. I was merely experiencing a problem and adding my voice and experience to the discussion. I find it odd that I have been repeatedly harassed over the exclusion of an activity log that cannot tell you anything about what is happening in an Apple TV box when others reporting the same issue and not including the same log have not been singled out.

You sir need to get over yourself and pay attention to what is going on before you spout out things in response to people that are not related to what was presented to you.
Locked