NeowinCAST News Edition for October 31, 2007


Recommended Posts

You guys say yay, while the perfectionist in me spends time thinking about how I wish I could go back and rephrase a few things, shorten a few areas while embellishing on other points and so on lol. This is why I hated editing. I can't listen to the show if I wish to maintain my sanity. :p

Eurgh. I hate editing.

1hr45mins now, but we're getting there. 75% of the way probably.

Not to sound ignorant but what actually goes on for editing, I mean what do you edit? background noise? etc...

Not to sound ignorant but what actually goes on for editing, I mean what do you edit? background noise? etc...

We make full cuts and such. Someone stutters? (I do a lot) It gets removed. Screwed up word? Removed. The editing for the NeowinCAST is basically the same kind of editing that gets done to a TV show, minus the video. It's a lot of tedious work. Basically, you have to play it through and stop on every mistake, select the portion of the wave form, delete it, rewind a little, play through that part to make sure the edit is clean, and then continue the process until the end of the show.

It's any recording difficulties where we had to re-record a segment because something went wrong, or where we lost our train of thought and decided to just restart our commentary... any clicks of microphones, any background noise or additional 'umms' and 'errs' where it's overly distracting (though keeping the natural feel of the conversation - generally we leave them in but occasionally they'd be very noticeable).

Then editing in the intro music, the outtro music, the voicemails. Then sorting out volume levels, compressing the audio to MP3, adding ID3 tags and embedding a graphic in there for iTunes... updating the XML feed...

Special guests are something we'll consider down the road, though I'm not sure beating the life out of the Neowin beginning story would be the way to go.

Right now, our sole focus is a consistent release cycle. Being there's only two of us, scheduling is much easier and we don't have to deal with any of the issues we had before with people with poor connections, mics worse than the piece of garbage I have, and restrictive schedules. It's also difficult to find someone we both have a decent chemistry with. Thankfully, Rob and I bounce off each other pretty well and can pretty much free flow without having to worry about losing the other. That's not always the case with others.

I don't want it to seem like I'm blindly shooting down ideas, though. I just know that we need to keep this relatively simple if we wish to make it last. We've already had a number of suggestions that would have increased the workload considerably while adding little value and I know some are left with a bitter taste in their mouths when we pass on an idea. Please just understand that there are boundaries we wish to abide by, for now, for the sake of getting the show out weekly.

We actually have a pretty good email/PM from a listener who signed up, seemingly, just to contact us.

Heh, tis fine, ideas are ideas, if they are not followed, I'm not going to be hurt, maybe cry in bed at night, but otherwise fine. :p

Sounds like a lot of stuff to do for editing, thank heavens we have such dedicated team doing it. :rofl:

Eurgh. I hate editing.

1hr45mins now, but we're getting there. 75% of the way probably.

Sounds like its going to be one long show o.O....YEY! :D

Then editing in the intro music, the outtro music, the voicemails. Then sorting out volume levels, compressing the audio to MP3, adding ID3 tags and embedding a graphic in there for iTunes... updating the XML feed...

Yey album art stuffs! :cool:

Lol, we posted at the same time. To sum it up: Post production is A LOT of work. It's the reason why a lot of podcasts die off and the main reason ours has died off so many times before coming back.

But you have such a following now, you wouldn't want to let us down. :p

But you have such a following now, you wouldn't want to let us down. :p

I honestly have no idea how many listeners we have, but the thought of losing anyone we've managed to hook is what's gotten Rob and I through a show or two already, for sure. You can schedule the show, but you can't predict when you're going to have a bad day at work or something along those lines. Knowing people are waiting to listen to us talk is a bit weird, but also motivational.

I appreciate the work you put into these shows plus the stuff you chat and discuss is stuff I am really into so it is good.

That's the ultimate goal. Honestly, I'm a pretty poor public speaker and my attention span is way too short to do the show, but I just like the idea of being able to create a discussion. Getting users to contribute now with the voicemails and emails is an important aspect, to me. It means that, at least, one of the topics discussed will be something that someone wants to hear about.

Yea, updates are cool.

And we love to listen to your voices as well, so it's not just you. :p

And id also like to point out its always good to hear a Podcast traversing the Atlantic in that out of you two is from the UK. *waves his little flag* a bunch of Podcasts that I have listened to have people from one country.

Hi guys

Looking forward to the new one :)

Can I make a constructive criticism. The content is great, however when Rob speaks the volume for his parts is considerably louder than BanBangs'. I'm not sure if i'm the only one it bothers, but I listen to it in bed late at night then all of a sudden it'll go a lot louder, and annoy my flatmates, lol.

Keep up the great work :)

Si

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • finally [Taskbar] Taskbar customization just got easier. As we continue to make improvements to the Taskbar experience mentioned last month, we've introduced a dedicated Taskbar Size setting, making it simpler to find, understand, and personalize your ideal taskbar experience.
    • Let me get this straight... It was a web interface for Gmail, so if privacy at Google wasn't concerning enough you'd be going through two companies. And their big feature was the very thing that would make people consider dumping Gmail.
    • Microsoft's fast coding model MAI-Code-1-Flash comes to Copilot Business and Enterprise by Karthik Mudaliar Microsoft’s recently announced MAI-Code-1-Flash model is now generally available to GitHub Copilot Business and Copilot Enterprise customers. With this support, organizations can have more centralized policy controls and billing while finally being able to use Microsoft’s lightweight, first-party coding model. According to GitHub’s announcement, Business and Enterprise plan administrators must enable the MAI-Code-1-Flash policy in Copilot settings before developers can access the model. Microsoft says that MAI-Code-1-Flash is for fast, iterative coding work rather than the most demanding architectural or debugging tasks. GitHub’s official model comparison page says that the model is great for "general-purpose coding and writing," while it excels at fast, accurate code completions and explanations Microsoft introduced MAI-Code-1-Flash on June 2 as part of a broader collection of internally developed MAI models. GitHub subsequently expanded support to Copilot CLI, the Copilot cloud agent, GitHub.com chat, GitHub Mobile, Visual Studio, JetBrains IDEs, Eclipse, and Xcode, but said support for managed Business and Enterprise customers was still on the way. In Microsoft’s own benchmark testing, MAI-Code-1-Flash scored 51.2% on SWE-Bench Pro, compared with 35.2% for Anthropic’s Claude Haiku 4.5. Microsoft also claimed that the model used up to 60% fewer tokens on SWE-Bench Verified. Do note that these are vendor-run results rather than independent measurements. The model is billed at provider list pricing under GitHub’s usage-based system. GitHub currently lists MAI-Code-1-Flash at $0.75 per million input tokens, $0.075 per million cached input tokens, and $4.50 per million output tokens. For organizations, the main incentive to use MAI-Code-1-Flash is likely to be efficiency rather than maximum capability. A smaller model that responds quickly and limits unnecessary output is quite useful for repetitive agent tasks at scale, especially after GitHub Copilot’s move toward usage-based billing. The "Flash" model is recommended for fast work and not necessarily for huge repositories with loads of context. It's better if teams compare their output with other larger models, especially if they're working on security-sensitive changes and complex, multi-file work.
    • yes AND no the "original" or plain/normal Optiplex 7010 won't be getting any more new firmware updates BUT the Optiplex SFF/SFF Plus {small form factor}, Micro/Micro Plus & Tower/Tower Plus 7010 editions DO get new updates such as this new one   and here are similar guides from the Dell web site for Dell systems: https://www.dell.com/support/kbdoc/en-us/000390990/secure-boot-transition-faq https://www.dell.com/support/kbdoc/en-us/000347876/microsoft-2011-secure-boot-certificate-expiration
  • Recent Achievements

    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      462
    2. 2
      +Edouard
      213
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      72
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!