VBR or not?

I will be importing my whole cd library in AAC format. After reading lots of posts, i'm still undecided in what I should do about VBR. Should i check that box or not? When checked, the extra space it seems to take up is not an issue but is the supposed better quality worth the bit of extra space? Please advice:)

I was doing VBR but decided after speaking to a friend that runs a club using mp3's that it is better to keep a steady bit rate. His feeling is that the quality is superior but I suppose it is up to your ears. There are other opinions of course. You can have a read at http://service.real.com/help/faq/rjbvbrfaq.html or http://www.codinghorror.com/blog/archives/000470.html
These came from a google search of "variable bit rate".
Some programs used to edit mp3/4 will not work with VBR files or may not perform the job as well as a file that is CBR.
MJ

Similar Messages

ITunes Plus - VBR or not?

Hello,
My question is simple:
When choosing iTunes Plus as the import format for CDs, iTunes Plus files are being described as VBR, and show up as VBR in the iTunes library. However, imported iTunes Plus files are supposed to be the same quality as purchased iTunes Plus files from the iTunes Store.
Yet purchased iTunes Plus files from the iTunes Store are not showing up as VBR.
Somebody can help me out on this one?
Thanks,
Thomas

I'm sorry, but I don't have any experience with variable bit rate. All of my songs are 128 kbps aac, including my iTunes Store songs. Well, actually, I just checked songs from my latest iTunes Purchase (5/10/2008), and a handful of them are 256 kbps -- I guess those were iTunes Plus. How do you make them appear VBR or not? I see one purchased song, from 4/1/2007, that's 303 kbps (perhaps that's why it sounds rather crappy!) and it says it was encoded with FAAC 1.24+, while the vast majority of my purchased songs don't tell me what encoded them. Hey, there's another one: 267 kbps, encoded with FAAC 1.24+, purchased 8/31/2005. I don't recall for certain, but I think it also sounds of questionable quality. Both of these come from +Rare Requests, Vol. 3+. I don't think these are "iTunes Plus."

Problems with VBR why not....

So if I am getting dissolve artifacts from VBR 2 pass should I just use CBR @ 6.2
Would that be better quality anyway?

Hi,
I'm looking at Flip4Mac to convert my .mov files into WMV and compress them for my website. I'm lost with all the technical details and hope you can you give me some advice so I don't waste my money on the wrong product.
Flip4Mac have 3 versions of a converter in the 'WMV Studio' range, the major difference being that the top-end one offers 2-pass encoding, while the middle and low-end versions offer 1-pass.
I have to keep the converted file size under 1MB. The trial version I used on the 1-pass setting came in at about 1MB (from a 100MB original) but the quality was not great.
Does 2-pass encoding makes the file size larger or would it be around the same as 1-pass? And is there a distinct improvement in the quality?
Thanks and regards,
Andrew
[email protected]
PowerMac G5 dual 1.8 Mac OS X (10.4.6) 1.5G of RAM

GBB-VBR at the time of GI with M.type 201

Dear all
When i trying to do GI with MB1A system is asking account determinationfor entry 1000 GBB--VBR 7001 not possible, can i maintained the account determination in OBYC. is it the correct entry at the time of GI.
Regards
venu gopal

Hi all,
I have defined GBB - VBR in OBYC trx, but at the time of GI with movement 201, the system does not automatically define any account. Is there any other configuration required for automatic account assignement for MIGO 201?
Regards,
Victoria

Encoding question acc vbr

Hello I import my music at acc 256 auto on both sample and channels and VBR
should I be using vbr?
Is it helping or not?
I am not sure what it does.
Also I use "error correct when reading cds" Is this good or not really?

Imagine a section of music with silence in it. To represent that digitally takes far less information than a busy section with all frequencies and lots of dynamic variation. VBR (Variable Bit Rate) works smartly to reduce just how much data is needed. CBR (Constant Bit Rate), however would, in a silent section, keep sending out information saying "all quiet, all quiet, all quiet".
It's normally said that some older MP3 players can't cope with VBR but, to be honest, I don't know of any. VBR is perfectly acceptable and should make a difference to the file size, although encoding may take a little longer.
Expect to save space with VBR but not massive amounts. 25% if you're lucky but, if you listen to lots of high octane music, you may find no saving at all.
You could consider stepping from from 320kbps to 256 or even 192. I use 320 VBR but buy a lot of storage and, if you can do that, I suggest you do the same. in a few years, our video libraries will dwarf our audio and you'll regret then compressing at lower rates. Disks are so cheap that you might as well just buy another. Archive what you don't want online and hope that iTunes is improved in the near future to support multiple volumes.
Pete

Why can't I write ID3 tags?

Hi gang. Odd problem. Just very recently noticed it.
With some files, but not all, when I go to bounce them, it won't let me write ID3 tags.
I click the Bounce icon. The bounce box comes up.
I overtype the file name at the top.
I select destination MP3. Stereo mode is joint stereo. Write ID3 tags is ticked, so are use best encoding, filter frequencies below 10Hz , mode offline and include audio tail. Bit rate mono is 80kbps. Bit rate stereo is 160kps. Bit rate VBR is not ticked.
I click ID3 settings. The Bounce box goes out and then after a very short moment comes back set back to the PCM destination with the file name missing.
I go through the whole routine again. This time the bounce box goes out and stays out.
The only way it will bounce is without changing the ID3 tags. It flatly refused to edit them. Just no way, I can't get at them, that's it.
Version is 9.1.5 (1 7 0 0.9) 32 bit. Yes I have tried saving the file, shutting the program down and restarting it, it still does it. Once a file starts doing this, that's it, it always does it.
The only thing that's changed recently is DwellClick. Every file created after that seems to have the problem. Every one before it is still OK, even with DwellClick running. However, if I create a new project now, the problem doesn't happen, it's fine. Something must be happening during the project that stops the ID3 tag dialogue box being accessible.
Is this a software incompatibility? a software bug? suggestions??

Hi
Erm, excuse me asking a really stupid question, but how would I do that?
and why is it affecting some files but not others? The latest file here does not seem affected. If it was a global preferences issue would it not affect all files? is it not more likely that it is the project itself that has the issue?
I notice that the project file can be examined as a package which apparently contains a folder LgDoc, which itself contains
displayState, which appears to contain coding instructions and data
documentData, which is mostly unintelligible coding with odd bits in clear text
windowImage.jpg, which is just the graphic for the icon.
This for example is a displayState file from a project that does not allow access to the ID3 tags:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>displayDataVersion</key>
    <integer>1</integer>
    <key>docPreferences</key>
    <dict>
        <key>EXSEditorGlobalPersistency</key>
        <dict/>
    </dict>
    <key>screenVisibleFrames</key>
    <array>
        <string>{{0, 97}, {1440, 781}}</string>
    </array>
    <key>screensetCurrSlot</key>
    <integer>1</integer>
    <key>screensetDictArray</key>
    <array>
        <dict>
            <key>layoutDictArray</key>
            <array>
                <dict>
                    <key>docwWindowState</key>
                    <dict>
                        <key>currentDocwListID</key>
                        <integer>1</integer>
                        <key>docwEditorTabIndex</key>
                        <integer>-1</integer>
                        <key>docwListTabIndex_events</key>
                        <integer>0</integer>
                        <key>docwListTabIndex_media</key>
                        <integer>1</integer>
                        <key>docwListTabIndex_notes</key>
                        <integer>0</integer>
                        <key>focusedElement</key>
                        <integer>0</integer>
                        <key>inspectorIsVisible</key>
                        <true/>
                        <key>listsAreVisible</key>
                        <false/>
                        <key>markerTextIsExpanded</key>
                        <true/>
                        <key>markerTextSplitPosition</key>
                        <real>33.333000183105469</real>
                        <key>mediaListIsCurrent</key>
                        <true/>
                        <key>screenSpaceRect</key>
                        <string>0 97 1440 781/0 0 1440 900 0 97 1440 781</string>
                        <key>tabViewPercentMixer</key>
                        <real>100</real>
                        <key>tabViewPercentOther</key>
                        <real>76.597442626953125</real>
                        <key>toolbarIsVisible</key>
                        <true/>
                        <key>transportBarIsVisible</key>
                        <true/>
                        <key>transportLayoutDict</key>
                        <dict>
                            <key>CLgTransportBtnsDisplay</key>
                            <array>
                                <integer>18</integer>
                                <integer>19</integer>
                                <integer>21</integer>
                                <integer>22</integer>
                                <integer>23</integer>
                                <integer>24</integer>
                            </array>
                            <key>CLgTransportBtnsModus</key>
                            <array>
                                <integer>29</integer>
                                <integer>38</integer>
                                <integer>39</integer>
                                <integer>42</integer>
                                <integer>43</integer>
                                <integer>45</integer>
                                <integer>30</integer>
                            </array>
                            <key>CLgTransportBtnsTransport</key>
                            <array>
                                <integer>6</integer>
                                <integer>5</integer>
                                <integer>11</integer>
                                <integer>12</integer>
                                <integer>13</integer>
                                <integer>14</integer>
                                <integer>15</integer>
                                <integer>16</integer>
                            </array>
                        </dict>
                        <key>udataArrange</key>
                        <data>
                        HAFJcASnAgA4AQAAAADdBEUCAAAA
                        AAAAAAAAAAAAAAAAAAAAAADbACcA
                        SXAAAAAABACAAAAAAAAAAIARAAAA
                        AQoAIADbAI+IAAAAAAAAgAAAAAAB
                        AQAAAABAAAAAAAAAAADkAAAAAAAA
                        AMaYAAAAAAAAAAB43/+/8HwAAAAA
                        tACAAQAAAAAAAAMAAAACAAAADA5/
                        cQBjFgBXADAAQAAWABYAGwAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AQQDBgUCAAAAAAAAAAAAAAAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        ACBCAAC4QQAAAAA=
                        </data>
                        <key>udataBin</key>
                        <data>
                        HAEVEABAAgCdAQAAAABlARUCAAAA
                        AAAAAAAAAAAAAAAAAAAAAACZABEA
                        FRAAAAAAAAAAAAAAAAAAAAACEgAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AAAAAABAAAAAAAAAAAAAAAAAAAAA
                        AMaYAAAAAAAAAADY7f+/8HwAAAAA
                        9AGAAAAAAAAAAAAAAAAAAAAADAD/
                        AABjFgAbABYAFgAWABYAGwAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AQQDBgUCAAAAAAAAAAAAAAAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AJBBAAAAAAAAAAA=
                        </data>
                        <key>udataMixer</key>
                        <data>
                        HAEhIFjyAgCMAQAAAADdBOEBAAAA
                        ACMAAAAAAAAAAAAAAAAAAAAfAAAA
                        ISAAAAAABAAAAAAAAAAAAAATAAAA
                        AAAAAAAAAPCvEBgAAAAAABgAAAAS
                        EgAAAABAAAAAAAAAAAAAAAAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        0QGAAAAAAAAAAAAAAAAAAAAADAD/
                        AABjFgAbABYAFgAWABYAGwAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AQQDBgUCAAAAAAAAAAAAAAAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AABAAACAPwAAAAA=
                        </data>
                        <key>udataPianoRoll</key>
                        <data>
                        HAFCcFjyAgDpAQAAAABxA5wB4i4A
                        ADYBAAAAAAAAAAAAAAAAAABCACcA
                        QnAAAAAABAAAAA4A//2AAAQVAAAA
                        AAoAIAAAAPz/UAAAAAAAuAAAAA4p
                        KQAAAABAAAAAAAAAAABRAQAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAQAAAAAA
                        ZQGAAQAAAAAAAAMAAAACAAAADAD/
                        AABjFgAbABYAFgAWABYAGwAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AQQDBgUCAAAAAAAAAAAAAAAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAABI
                        4RJCAAAgQQAAAAA=
                        </data>
                        <key>udataTransport</key>
                        <data>
                        HAEKAAAAAgACAQAAAAAlAigAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        CgAAAAAABAAAAAAAAAAiAAAAAAAA
                        AAAAAAAAAAAAAAAqAJgADQAAAAAA
                        AAAAAABAAAAAAAAAAAAAAAAAAAAA
                        AMaYAAAAAAAAAADo3/+/8HwAAAAA
                        GACAAAAAAAAAAAAAAAAAAAAADAD/
                        AABjFgAbABYAFgAWABYAGwAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AQQDBgUCAAAAAAAAAAAAAAAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AAAAAAAAAAAAAAAAAAAAAAAAAAAA
                        AABBAAAAAAAAAAA=
                        </data>
                        <key>windowFrame</key>
                        <string>0 143 1440 735 0 0 1440 878 </string>
                        <key>windowIsZoomed</key>
                        <true/>
                    </dict>
                    <key>docwWindowType</key>
                    <integer>1</integer>
                </dict>
            </array>
            <key>screensetLocked</key>
            <false/>
            <key>screensetName</key>
            <string></string>
            <key>screensetSlot</key>
            <integer>1</integer>
        </dict>
    </array>
</dict>
</plist>
Question - is this corrupt, or is the other (mostly unintelligible one) corrupt?

Unable to create iPod-playable h.264 files using Compressor

I've been running some video compression work for iPod, and have been able to do "quick & dirty" exports to iPod via QuickTime Pro (standalone & from within FCP).
To get more of a handle on the compression parameters than the default "Export to iPod" setting allows, I have had success using 3'rd party tools, and using customized settings in QuickTime Pro (most excellently discussed in Ken Stone's page here: http://www.kenstone.net/fcphomepage/video_to_ipodstone.html)
So far so good: successfully creating iPod-friendly files that meet the requirements: http://www.apple.com/ipod/specs.html
What I really want to do, though, is create a saved Compressor setting for setting up batches of iPod conversions, and so I don't have to hand-tweak each export in QT Pro.
I am running current version of QT and Compressor, but CANNOT create MPEG 4/h.264 files that will load onto an iPod for the life of me.
Here's how it goes down for some different Compressor settings, with their results:
1.)
File format: QT
File extension: .mov
Video: 320x240 15 fps MPEG-4 Video (note for those playing along at home that there is **no way** to specify h.264 nor "Baseline Low Complexity" in the Compressor dialog)
Audio: AAC
Result: a quick to encode, plain old MPEG4 file with only so-so quality that will load and play on an iPod
2.)
File format: QT
File extension: .mov
Video: 320x240 15fps h.264 (again: no way to select "Baseline Low Complexity" within Compressor)
Audio: AAC
Result: Slower to encode, higher quality and smaller file that will NOT load onto an iPod. Error in iTunes states that the file "cannot be played on this iPod"
3.)
File format MPEG4
Extension: mp4
Video: 320x240 15fps Basic (0) ISMA profile, Medium VBR. Note that there is no way to specify h.264
Audio: 44.1/128 kbps
Results: Same as in #1 above
What I feel I have it boiled down to is that there is some weirdness in Compressor that doesn't connect to the QuickTime compression settings properly. Where you SHOULD be able to specifiy h.264 and Low complexity settings (as you can when using QT Pro) for an MPEG4 file, you cannot in Compressor. Similarly, when specifying h.264 in Compressor, there is no way to specifiy Baseline Low Complexity.
Long post- sorry! I have tried many more iterations than are listed here. I'll spare everyone those, as the examples above I think illustrate my predicament.
Anyone have any thoughts?
Thanks-
John

OK.. first, thanks for the reply. Sort have had given up on finding an answer here and just checked back here yesterday. Lo and behold I do see the iPod setting on a newer machine- and started to look into why exactly it isn't on the main workstation here.
Turns out that you don't get updates unless the software is registered. Maybe it's just me, but I never bother with product registations (until today I guess).
So a word up to anyone else who does the same. You won't get FCP automatically updated unless you register.
I assume after I update everything I should be AOK
Also- I should have marked your reply as SOLVING my problem- but my first instinct was to say to myself "Of course I'm using current versions- what kind of jamoke does this guy think I am, anyway?" So, feeling very charitable, I marked your reply as merely helpful.
And now I have to eat my words! Sorry about that. Guess you'll get good karma points somehow. Maybe I'll look into that some more while I'm downloading updates this AM.
Thanks again!
-John

Account determination for movement type 251

Hi!
While checking account determination for logistic movements, I find that according to standard customizing, movement type 251 is related to account modification VBR. You can easily see this: OMJJ --> Check movement type --> type "251" --> Select "Account Grouping".
Now my question: what I don't understand is why VBR and not VAX. GBB-VBR is the transaction key + account modification for internal goods issues (such as consumptions of material) and it's accordingly associated to movements types 201, 261, etc. which seems logical to me since these are internal GI's.
Now, 251 is IS-Retail movement type to reflect a POS sale, "GI for sales" as the short text indicates, so it is not an internal goods issue but rather an external one, not different from movement type 601, which is a normal sale and is associated to GBB-VAX. GBB-VAX is the transaction key + account modification for sales goods issue.
I know I could easily copy 251 to create another movement type and assign any account modification to it, that's not the issue. The only problem is that I must explain to my client how account assignments work, and I cannot find a single reason why in standard SAP IS-R an external goods issue (251) is associated with an internal goods issue account modification (GBB-VBR).
Any ideas? Thanks in advance.

hi
for inventory use
gbb>inv
umbfor inventory and material val
prv for prise diffrence
in 702 prv and inv is the postings
for 309 vbr and pru is transaction in gbb
1) one more thing u can do is go to OMWb then go to simulation there u can find gl accounts and grouping keys note down that GL nos
2) then come one step back
and clik on gl accounts there u will find many gl accounts
find gl accont no which u have noted in step 1
there u can find transaction keys
by doing this u can find which are transaction keys for a perticular movement type
reward if helpful
regards
kunal

FI Account modification from MM via T030

Hy Expert,
I need help about integration from MM to FI when I make a stock variation. My question is where Sap store the account modification when creating an Fi document via stock modification in MM?
I explaine:
I make an MM Logistic movement on the stock. Sap decrease/increase the quantity in the stock and following makes an FI document to update the stock value on FI account.
Example:
Movement type 201 use the procedure BSX to decrease the stock value in the specific FI account.
The corresponding Sap procedure to balance the stock value in FI document is GBB + account modification VBR.
The procedures BSX and GBB, used by Sap, to determine FI account is visible in BSEG.
Where i can see the account modification VBR used by Sap ?
BSX is visible in bseg or via transaction FB03 on FI document
GBB is visible in bseg or via transaction FB03 on FI document
VBR is not visible.
In which table I can see the account modification VBR?
Thanks.

Hi,
If you want the link between MM mov and FI document, use the function module AC_DOCUMENTS_RECORD, for instance
call function 'AC_DOCUMENT_RECORD'
    exporting
      i_awtyp      = 'MKPF'
      i_awref      = awref
      i_aworg      = aworg
      i_awsys      = awsys
      i_awtyp_incl = 'BKPF'
      i_valutyp    = '0'
      x_dialog     = ' '
    tables
      t_documents = docs_fi
    exceptions
      no_reference = 1
      no_document = 2
      others       = 3.
where
data: awref like acchd-awref,
        aworg like acchd-aworg,
        awsys like acchd-awsys.
and data: docs_fi like acc_doc occurs 10 with header line.
Regards,
Eduardo

Error while issue goods

Hi Frnds,
I have created a new material type -- consumables and also i assigned G/L account to that using OMWB Tcode. Now while issuing the goods to cost centre againt 201 moment type i am getting the following error:
Account determination for entry 1000 GBB ____ VBR 3004 not possible.
Diagnosis
The system did not find an account for this transaction. This means that the account determination for key 1000 GBB ____ VBR 3004 is not maintained in MM Customizing (Valuation). The key is made up of:
This is the error , wat more setting should i do over come this.
Regards
Rakesh

Hi,
1) Goto OBYC
2) Enter Chart of Accounts = 1000
3) Double click GBB
4) Search for VBR
5) With VBR and 3004 Valuation class maintain a G/L account ( The G/L account can be demanded from the FI team or you can make use of the G/L account which had already been configured in your system say for eg :G/L account of VBR 3000 valuation class can be used if you are just doing a testing for your own academic learning )
Regards,

Error - Consignment - MB1A

Dear All,
I am posting goods issue in T.Code MB1A, initially i got an error as Acct. Det. for entry INT GBB RHII VBR IIII not possible in OBYC T.code i cleared it & saved the changes.
Now in T.Code MB1A i have given the details & iam getting the below error when saving it:
"Document Number 0IIL 101 2008 was already assigned"
How to clear this error?
Vineeth.

what is the movement type u r using in MB1A?
regards,
indranil

Variable bit rate is good

hello everyone,
I've been compressing dvd using compressor at 7.8CBR for my pass projects & it looks great. However on my current project I can't pull a good compression due to the large LCD screen in the background so I have to try vairalbe bit rate with min 6.5 & max 8.0 two passes & it looks great.
Does anyone has any similar experience?
I heard that compressor's VBR is not good so I 've never tried but to my understanding, it's better to do 2passes since the software would analyze the movie better.
just some note.
JP
ps: can't wait to upgrade to fcp studio2

It's said the Compressor 2.3 has solved all problems related with VBR in past versions.
Alberto

Differences between 2 pass and 1 pass compressing in compressor 2.0

Is there a noticeable difference between 2 pass and 1 pass compression? It seems to me that sometimes 1 pass looks better than 2 passes. Strange...
Thanks,

Hey Girshon
this is more of a compressor forum question, but i can answer it here
theoritically, a 2 pass VBR encode is a MUCH better option if you are limited to space with VERY complex scenes. a cbr encode is optimal for short encodes, or encodes where you have NO space limitation. of course this is how most encoders work.
in compressors case, for SOME reason (unbeknown to me) a 2 pass vbr does not encode to a quality that where i can call acceptable, especially with accepatable bit-rates.
this problem has seemed to come in compressor v2. a lot of people that use this version of compressor seem to recommend a CBR in compressor or a 2 pass vbr IN DVD SP.
compressor v1 seems not to have this problem however. as a matter of fact, a lot of other DVD encoder, software or hardware dont seem to have this problem.
if you do a search for 2 pass vbr in the compressor forums, you will see all the quality problems associated with compressor 2.
Mikey m.

Optimizing dvd playback quality (macroblocking problems)- HELP!

Nothing is quite so frustrating as spending countless hours editing, encoding, and authoring a DVD and then discovering that the video has playback issues (macroblocking, digital artifacting, sometimes so serious it halts playback altogether) at some point in the stream.
I feel sure others must have some idea what I'm talking about, and yet I haven't found a thread on this forum or any other that addresses what is really the root cause here. As I figure it, there are a number of factors (variables) at work:
1. the media itself
2. the software used to create the disc (in my case DVDSP 4.0/Compressor usually at the "Best" quality encoding)
3. the hardware used to burn the disc (in my case the MATSHITA DVD-R UJ-815 superdrive in my powerbook)
4. the DVD player used for playback
In my experience, a disc might do fine on one player but then have significant playback issues on another. On one occasion I even saw playback perfectly through an hour of video, and then the next day on the same player and the same DVD I got significant macroblocking through parts of it.
What gives!? Are there some DVD-R media that are way better than others? Or do I need to invest in a better drive to burn them? Or is this just the growing pains of emerging technology? Is there some other thread anywhere in cyberspace that addresses this issue?

Hi John
So you're saying that your mpegs are clean and clear of any macro blocking, and this is only introducted once you burn to DVD, and then only on some players, but also a disc that played fine one day on a deck, plays back bad the next day on the same deck.
Man, you've got some serious gremlins at work in your office. Before you pull your system apart, chack you mpegs again. If you're using Compressor 2 with any of the VBR presets you're going to get macro blocking because C2's VBR is not very good - I've not had one successful mpeg out of it. If your project is under 1hr try CBR at 7.5Mbps, that's been working fine for me.
Now, are you encoding your audio to .ac3, or .aiff. If you're using .aiff you might be hitting wall with your bitrate. Your .aiff will have a bitrate of 1.5Mbps, and if your using using a high max bitrate on your vision and you get a bitrate spike which Compressor is also known for then you could be blowing your bit budget (max of 9.8Mbps for vision and audio together), which could result in stuttered playback and freezes.
Next, are you burning out of DVDSP or are you using Toast. Some users report problems burning at higher than 2x speed (personally I burn at the limit of the media and haven't had a problem). As you can't control the burn speed out of DVDSP you might want to try just building in DVDSP and burning in toast at a low speed.
If you're burning from data on an external FW drive try moving it to the HD and try it again.
Try a few different brands of media. Keep it clean and out of the sun.
That's about all I can tell you at the moment - these are all the obvious things , maybe somone else can chime in with some more obscure causes.
Cheers
B

XDCAM export to disk

Hello,
I'm having a problem writing XDCAM clips back to a disk. We shot some car mount footage on another camera (GoPro)
• I compressed that footage to XDCAM 1080i60 35Mb/s
• Placed the compressed footage into a Final Cut timeline (XDCAM HD 1080i60 35Mb/s VBR).
• Set Audio output to four channels, 1 and 2 dual mono and 3 and 4 dual mono.
• Set our deck (Sony PDW-HD1500) to 59.94i/HD420-1080/HQ/4CH-16Bit
• File > Export > Sony XDCAM...
• Export to "Untitled" (the XDCAM disk that's in the deck.
• As format MXF (HDCAM, HD, HD422)
• Using settings XDCAM HD 1080i60 VBR
• REC INHIBIT off on the deck
It won't write that to the disk. I continue to get "Export Failed" windows telling me to check settings and make sure record inhibit is off.
Here's the problem: when I set the settings to XDCAM HD 1080i60 CBR (which is 25Mb/s) or XDCAM HD422 1080i60 CBR (which is 50Mb/s) the file writes properly EVEN THE DECK IS SET TO 420HQ.
Our show is shot at the 420HQ (35Mb/s) format and that is what we have to deliver to post.
The problem seems that CBR works just fine and VBR does not. Does the computer have a problem with a variable bitrate that it doesn't have with a constant bit rate?
The footage is not going to suffer at 25Mb/s, since it was shot on the little GoPro camera (it records to an mp4 file at a much lower compression). But we want to get the footage to post in the same format that they're getting everything else.
What can I do to fix this situation?
Thanks,
Stef

Hello Marcus,
You need to install the latest Sony FAM-driver on your Mac for writing your edit back to the disc. I guess that's all.
Importing goes now via the "Media Browser" as I understand it correct. I believe therefore XDCAM Transfer software isn't needed anymore, but I think it wouldn't hurt to have it installed too.
When your edited sequence is written back to the disc, you’re able to play it out on your PDW-700 via the SDI or HDSDI connection.
I still use FCP7 so how it all precisely goes in Premiere, I do not know for sure. I'm sorry for that! Production Premium CS5.5 is installed on my Mac, but haven't used Premiere Pro. Shortly I will be switching to CS6.
Here are some other movies for the PDW-700. In part 4 Andy explains how to write back to the 700 with FCP. I assume it's almost the same with Premiere.
http://resources.abelcine.com/2009/02/23/abel%e2%80%99s-sony-pdw-700-xdcam-camera-tour/
Another document from Adobe that can be useful. Using Adobe® Premiere Pro CS6 with file-based Sony XDCAM content.
http://www.adobe.com/content/dam/Adobe/en/products/premiere/cs6/pdfs/adobe-premiere-pro-cs 6-sony-xd-cam.pdf
Try it and let us know if it works.
Greetings,
Ivan
PS: what version of Premiere Pro are you using Marcus?

VBR or not?

Similar Messages

Maybe you are looking for