Forum Replies Created

Page 13 of 315
  • Herb Sevush

    March 27, 2019 at 12:42 pm in reply to: Keyframes in Submixes

    [matt chapman] ” Everything was mixed nicely in each sequence, but now that its all on one timeline, the mixes are off. “

    When you consolidated to a single timeline did you bring in the segments as a nest or separated into their individual tracks? To do what you want they should have been brought in as nests, then you can make the adjustments on the timeline like you want yet still have the ability to open the original segments to make changes.

    Herb Sevush
    Zebra Productions
    —————————
    nothin\’ attached to nothin\’
    \”Deciding the spine is the process of editing\” F. Bieberkopf

  • Herb Sevush

    March 22, 2019 at 12:31 pm in reply to: iMac bump

    A couple of factors are in play, says I.

    First, this is a minor upgrade. I will expect more interest when/if the next Mac Pro gets released.

    Next, I think the industry has matured to the extent that you can do what you want with whatever you have. All of the big time NLE’s are great, they can be used on anything from a laptop to a multi-screen workstation, utilizing either Mac or Windows. The differences are very nuanced, the NLE’s are customizable, the computer’s are available and cheap – there just isn’t that much to complain about. Not that that’s ever stopped us before.

    Finally, the thread about the renaming of this forum has sent some of our former contributors away. Debate leads to passion leads to volatility leads to bad behavior – and when that is not being tolerated, the ecosystem changes. Less passion, less interest.

    Herb Sevush
    Zebra Productions
    —————————
    nothin\’ attached to nothin\’
    \”Deciding the spine is the process of editing\” F. Bieberkopf

  • Herb Sevush

    February 14, 2019 at 7:04 pm in reply to: Premiere audio breaking MacBook Pro speakers

    [Tom Sefton] “Out of interest have you used a MacBook Pro with premiere pro recently?”

    Not recently, not ever. As I said in my first post, this doesn’t concern me personally because I never edit on laptops. I’m strictly a Mac Pro guy, with occasional cause to work with Imacs when out of house. The original post implied that this was a Ppro problem, I don’t see it that way.

    [Tom Sefton] “I don’t see the logic that it can be apples fault if no other software aside from adobe is causing this?”

    But can you see the logic if Premiere Pro works with every other computer Apple makes – since when do software makers have to customize not just for every OS but for every model of every type of computer within an OS?

    To put it another way – it’s both their faults: Ppro shouldn’t do this, MacBook Pro’s shouldn’t let it.

    A related question – is this the dark side of the fact that FCPX is customized for both the OS and the hardware Apple makes – does this mean that Apple is making it harder for others to play well with it? I don’t know, just asking.

    Herb Sevush
    Zebra Productions
    —————————
    nothin\’ attached to nothin\’
    \”Deciding the spine is the process of editing\” F. Bieberkopf

  • Herb Sevush

    February 14, 2019 at 12:34 pm in reply to: Premiere audio breaking MacBook Pro speakers

    [Brett Sherman] ” Are you suggesting that Apple should have code that analyzes the audio waveform that software is sending through the audio hardware and then stops it? That would be insane.”

    I don’t know what caused the speakers to blow, and I suspect neither do you, but the fact is that no other Apple computer has any reports of Premiere blowing their speakers – just the 15″ MBP. I don’t see how it’s possible that Ppro is sending out a different signal on Mac Pro’s then on MBP’s using the same OS. If Ppro software is creating full volume square waves then why haven’t the speakers blown on any of my Macs?

    And why exactly would it be insane to filter out audio signals that destroy speakers? Just curious.

    Herb Sevush
    Zebra Productions
    —————————
    nothin\’ attached to nothin\’
    \”Deciding the spine is the process of editing\” F. Bieberkopf

  • Herb Sevush

    February 11, 2019 at 12:42 pm in reply to: Fuller House Intro

    [Tiffany Jones] “Hi Does anyone know how I can make the intro to Fuller House? “

    This is like going to a doctor’s website and asking ” Hi Does anyone know how I can do an appendectomy, I want to do one as a project for my daughter?”

    Herb Sevush
    Zebra Productions
    —————————
    nothin\’ attached to nothin\’
    \”Deciding the spine is the process of editing\” F. Bieberkopf

  • Herb Sevush

    February 8, 2019 at 5:39 pm in reply to: Premiere audio breaking MacBook Pro speakers

    [Steve Connor] “Yep it’s all Apple’s fault, nothing to do with a bug in the software :)”

    It’s not all Apple’s fault, but a software bug should not allow a user to blow up his hardware. That’s why Apple fixed the issue with the nMP Gfx cards.

    I am not aware of any software that is blowing up any pc laptop, and that’s a much larger and varied source of software. Wonder why that is ?

    Dell’s new marketing slogan “well hell, at least our s**t doesn’t explode.”

    Herb Sevush
    Zebra Productions
    —————————
    nothin\’ attached to nothin\’
    \”Deciding the spine is the process of editing\” F. Bieberkopf

  • Herb Sevush

    February 8, 2019 at 5:26 pm in reply to: Premiere audio breaking MacBook Pro speakers

    [Steve Connor] “This doesn’t happen with anything else so it’s clearly a software issue.”

    Or – it doesn’t happen with any other hardware, so it’s clearly a hardware issue.

    In either case, just as the hardware should not allow software to send a signal that sets the GFX card on fire, it should not allow an audio signal to be sent that blows up the speakers. It’s a computer, not a dumb amplifier, and it should be able to control it’s environment.

    Herb Sevush
    Zebra Productions
    —————————
    nothin\’ attached to nothin\’
    \”Deciding the spine is the process of editing\” F. Bieberkopf

  • Herb Sevush

    February 8, 2019 at 4:33 pm in reply to: Premiere audio breaking MacBook Pro speakers

    [Tom Sefton] “is it an apple or an adobe fault? If it doesn’t do it with fcpx, logic or izotope is it a coding issue?”

    Since it only happens on MacBook Pro’s it’s similar to the situation a few years ago where nMPro’s were melting their GFX cards – hardware is not supposed to blow up no matter how bad the software.

    Herb Sevush
    Zebra Productions
    —————————
    nothin\’ attached to nothin\’
    \”Deciding the spine is the process of editing\” F. Bieberkopf

  • Herb Sevush

    February 8, 2019 at 12:45 pm in reply to: Premiere audio breaking MacBook Pro speakers

    Apparently 15″ Macbook Pro’s suck.

    In a Bill Davis influenced aside I can only note that since I never edit on a laptop this is a non-issue probably caused by holding the computer the wrong way and I hope Apple engineers don’t waste their precious time trying to fix it.

    Herb Sevush
    Zebra Productions
    —————————
    nothin\’ attached to nothin\’
    \”Deciding the spine is the process of editing\” F. Bieberkopf

  • Herb Sevush

    January 27, 2019 at 3:11 pm in reply to: Adjust levels to Loudness Radar

    You can select a group of audio clips and raise or lower the volume in increments of 1db by using the keyboard shortcuts / left bracket key decreases / right bracket key increases. If you hold the shift key down the increments will be 6db. If you need more granular control, nesting or creating a sub group in the track mixer will work fine.

    Herb Sevush
    Zebra Productions
    —————————
    nothin\’ attached to nothin\’
    \”Deciding the spine is the process of editing\” F. Bieberkopf

Page 13 of 315

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy