It was in response to the specific assertion made that one computer could not have ore than one iTunes library open at a time. You can, I have done it, and I told how. Do what you will with the information. In response to your question or topic about a system for delivery of iTunes. It would be cool. Whether or not it will ever be made is another question.
Ok, cool. Thanks for clarification. I will be trying this soon as I get home!
This is kind of interesting in that it tells us that iOS 6, OS X ML, the Mac, the iPad 2 and 3 have the ability to stream and mirror video over WiFi. Many Apple and 3rd-party apps support video mirroring just fine. Surprises are highlighted in blue.
The new h.265 codec may make it practical to:
stream over a cell connection
reduce bandwidth and/or improve quality over a WiFi connection
Apparently, the means (hardware, software, OS Frameworks, codec) exist, today, to stream and mirror over WiFi -- it is up to the developers, to implement the capability in their apps, to permit mirroring during AirPlay streaming.
These are my encode settings for 720P under HandBrake and they work very well:
Average kbps: 3500 with 2-pass Ref Frames: 5 Max B Frames: 5 CABAC Entropy Encoding: checked 8x8 Transform: checked Weighted P-Frames: checked Pyramidal B-Frames: Strict No DCT Decimation: Unchecked Adaptive B-Frames: Default (fast) Adaptive Direct Mode: Automatic Motion Estimation Method: Uneven Multi-Hexagon Subpixel ME & Mode Decision: 7-RD in all frames Motion Estimation Range: Default (16) Partition Types: (most( Trellis: Encode Only Debllocking: both default
I use this as the template and just adjust the bitrate depending on the frame size. For example, on DVD's I use a 2000 kbps nitrate (I have a 65" HDTV so artifacts and noise are very visible on poor encodes).
EDIT: Ugh..ugly that is collapses your text in this way
These are my encode settings for 720P under HandBrake and they work very well: Average kbps: 3500 with 2-pass Ref Frames: 5 Max B Frames: 5 CABAC Entropy Encoding: checked 8x8 Transform: checked Weighted P-Frames: checked Pyramidal B-Frames: Strict No DCT Decimation: Unchecked Adaptive B-Frames: Default (fast) Adaptive Direct Mode: Automatic Motion Estimation Method: Uneven Multi-Hexagon Subpixel ME & Mode Decision: 7-RD in all frames Motion Estimation Range: Default (16) Partition Types: (most( Trellis: Encode Only Debllocking: both default I use this as the template and just adjust the bitrate depending on the frame size. For example, on DVD's I use a 2000 kbps nitrate (I have a 65" HDTV so artifacts and noise are very visible on poor encodes). EDIT: Ugh..ugly that is collapses your text in this way
Yeah... it shouldn't mess with the text!
Thanks for the settings -- I'll do some experiments later today!
I haven't thought of WebM in months. Whatever became of it? Is it gaining any traction? Do Android phones have WebM hardware acceleration?
MPEG-LA has been somewhat successful in creating questions whether WebM is infringing on existing IP. They haven't actually given any examples of patents that apply to WebM, but I guess repeating often enough that there are some has slowed adoption. I noted MPEG-LA has made enough veiled threats that they did reportedly get the DOJ's attention last year.
MPEG-LA has been somewhat successful in creating questions whether WebM is infringing on existing IP. They haven't actually given any examples of patents that apply to WebM, but I guess repeating often enough that there are some has slowed adoption. I noted MPEG-LA has made enough veiled threats that they did reportedly get the DOJ's attention last year.
It was disappointing to see no user-facing changes to Quicktime in Mountain Lion.
What was there to change?
The only thing about QuickTime in Mountain Lion that I find unacceptable is the RHYTHMIC STUTTERING in the file audio that happens if you rewind anything. You have to quit QuickTime, not just shut that window, and reopen it to fix it.
Comments
Ok, cool. Thanks for clarification. I will be trying this soon as I get home!
Some additional experiments with streaming using:
ML AirPlay Mirroring to AppleTV
Works With Mirroring
Does Not Work With Mirroring
iPad AirPlay Mirroring to AppleTV
Works With Mirroring
Does Not Work With Mirroring
This is kind of interesting in that it tells us that iOS 6, OS X ML, the Mac, the iPad 2 and 3 have the ability to stream and mirror video over WiFi. Many Apple and 3rd-party apps support video mirroring just fine. Surprises are highlighted in blue.
The new h.265 codec may make it practical to:
Apparently, the means (hardware, software, OS Frameworks, codec) exist, today, to stream and mirror over WiFi -- it is up to the developers, to implement the capability in their apps, to permit mirroring during AirPlay streaming.
Average kbps: 3500 with 2-pass
Ref Frames: 5
Max B Frames: 5
CABAC Entropy Encoding: checked
8x8 Transform: checked
Weighted P-Frames: checked
Pyramidal B-Frames: Strict
No DCT Decimation: Unchecked
Adaptive B-Frames: Default (fast)
Adaptive Direct Mode: Automatic
Motion Estimation Method: Uneven Multi-Hexagon
Subpixel ME & Mode Decision: 7-RD in all frames
Motion Estimation Range: Default (16)
Partition Types: (most(
Trellis: Encode Only
Debllocking: both default
I use this as the template and just adjust the bitrate depending on the frame size. For example, on DVD's I use a 2000 kbps nitrate (I have a 65" HDTV so artifacts and noise are very visible on poor encodes).
EDIT: Ugh..ugly that is collapses your text in this way
Quote:
Originally Posted by DJRumpy
These are my encode settings for 720P under HandBrake and they work very well: Average kbps: 3500 with 2-pass Ref Frames: 5 Max B Frames: 5 CABAC Entropy Encoding: checked 8x8 Transform: checked Weighted P-Frames: checked Pyramidal B-Frames: Strict No DCT Decimation: Unchecked Adaptive B-Frames: Default (fast) Adaptive Direct Mode: Automatic Motion Estimation Method: Uneven Multi-Hexagon Subpixel ME & Mode Decision: 7-RD in all frames Motion Estimation Range: Default (16) Partition Types: (most( Trellis: Encode Only Debllocking: both default I use this as the template and just adjust the bitrate depending on the frame size. For example, on DVD's I use a 2000 kbps nitrate (I have a 65" HDTV so artifacts and noise are very visible on poor encodes). EDIT: Ugh..ugly that is collapses your text in this way
Yeah... it shouldn't mess with the text!
Thanks for the settings -- I'll do some experiments later today!
I haven't thought of WebM in months. Whatever became of it? Is it gaining any traction? Do Android phones have WebM hardware acceleration?
To answer your queries:
Nothing.
No.
Who Cares.
Quote:
Originally Posted by Unicron
I haven't thought of WebM in months. Whatever became of it? Is it gaining any traction? Do Android phones have WebM hardware acceleration?
MPEG-LA has been somewhat successful in creating questions whether WebM is infringing on existing IP. They haven't actually given any examples of patents that apply to WebM, but I guess repeating often enough that there are some has slowed adoption. I noted MPEG-LA has made enough veiled threats that they did reportedly get the DOJ's attention last year.
http://arstechnica.com/tech-policy/2011/03/report-doj-looking-into-possible-anti-webm-moves-by-mpeg-la/
Love ya tenacity. I am playing with Android Emulator now! Ha Ha. Despite my bias...
Even though Apple is involved, I bet VLC releases the first public player implementation.
It was disappointing to see no user-facing changes to Quicktime in Mountain Lion.
Originally Posted by Vorsos
It was disappointing to see no user-facing changes to Quicktime in Mountain Lion.
What was there to change?
The only thing about QuickTime in Mountain Lion that I find unacceptable is the RHYTHMIC STUTTERING in the file audio that happens if you rewind anything. You have to quit QuickTime, not just shut that window, and reopen it to fix it.
It's completely inexcusable in a release product.