Welcome to our community

Be a part of something great, join today!

Register Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Quine & QuineCore @ around the globe

Christmass duties for a Jan 10th launch...

80549241_2783628648366528_4228222855680098304_o.jpg
 
hah.

Stuff happens when you release things.

We have been the workflow backbone for the Norwegian Broadcast Corp long-form things for a while, but now first Nordic Film and TV goes publicly out and tell about our plans:

https://www.facebook.com/shortcutnorge/

And Telia is starting to release our common press material:

https://bit.ly/363WtXi

Things are starting to happen now.

quinecore-laptop.jpg
 
Last edited:
This is more like a diary than anything else, but scaling brings new challenges...

The three previous years have first and almost been about "making things work", and then "packaging features into a robust product".

Jan 10th, we were out of beta. More or less exactly "on time" according to our own estimates.

And now we are scaling the product and usage.
Not super fast at this stage.
We try to onboard 2 productions a week right now, and hope to up that to 3-4/week from march.

Not at all enough to sustain things financuially in the long run, but definitely a way to try to keep all users happy.

So our product is a connection tool.
We make the file, information, communication and metadata flow between existing tools and users and uaergroups.

Half way joking I could say that we cover:

Silverstack
A dailies system
A review application
A logging system
Drop-box
Aspera
Slack
Direct editor integration
VFX exchange solutions (But we don't attempt replacing editor applications or say ShotGun, we just manage the exchange)
And a tool to distribute your finished production to the end-user platform (Broadcaster, cinematic distribution, playout systems and MAMs)

We also have a pricing model that encourages that "everyone in the production can have access". A production comes with 50 users "forever"
We don't charge wildly for storage.

We WANT people to upload editorials in good quality and all audio to cloud. Not 1,5 mBit h.264

We try to encourage exchange and simplicity.


Now that sounds all nice and dandy, but the downside is that we have a pretty vertical impact on the productions we are in.

And people (even though they sit and talk about: What if "this" or "that" was integrated, how much easier my life would be) still try to do everything like they used to.

So they try to treat the ingester as Silverstack, as that keeps the hours running, and the dailies tool like like any other dailies tool etc etc etc.

It's something comforting, too in calling IT and sit and wait, when you need to send something to post for a fix.

THAT, more than capacity, is why we roll out slowly.

To have the productions get the benefits of what we do, we need to show people hw to work ever so slightly differently along the way.

And that can at times be rattling a hornets nest.

The comforting thing with silo's (even though everyone hate them) is the LACK of interaction with the rest.


Then you can comfortably sit and swear why someone didn't share something on filemail or Aspera.

And that has a certain comfort to it.

We also rattle a bit of the cages with what we do.

Some are super happy for that.
Others, not so much.

It challenges domains.

But in all, if ever so slowly, we are fortunate to see that those using it, are embracing it and talking nicely about it.

So then the next challenge is user-control :)

Another reason we do this slowly, is to try to get exposure for one new problem at the time.

Despite three years of research and development and access to abundant datasets and productions on the way thanks to our partners, now we let it in the lose, and have to deal with that iPhone, GoPro, Olympus camera at wrong frame rates that keeps popping in.

We want to have a bit of control on that, adding automated recognition of devices as we go.

Maturing the base capabilities of our system.

And if we took in 10 productions/day at this stage, we wouldn't be able to keep track with the challenges.


The general thing of going from "making things work", to make people use, is super interesting.

We are super fortunate in some ways. Many houses have been waiting for us at least the last year, and it feels good to slowly let them in.

In that sense I think this period is a bit of a honeymoon.

We have more clients than we can manage.

We will definitely be exposed to a more cut-throat environment as we go.


But I have to say it is very rewarding after meeting with a major producer and hearing that their conclusion is that when they talk with their clients, they plan to say:

Either we use QuineCore, or we'll have to bill you 3X for data management.

Then at least we see that we're on to something.


Because we want this to get into volume and be 2nd nature tools for non-broadcast type productions everywhere.
 
Last edited:
Sad, but true - when you make a better mousetrap all the folks who have built skill sets with the old mousetraps push back.
That cultural resistance to change is powerful and it was certainly operative during the first few years of the RED Rebellion.
Looking forward to learning more about Quine, it just might be the droid I've been looking for the last 10 years...

Cheers - #19
 
I ws challenged to try to explain what we do and what we do different in a non-geeky and non-techy way.

This is what I came up with:

What we do.



QuineCore simplifies structured media-handling and sharing.

Quine takes the approach that tools that normally work in isolated silo’s but solves different aspects of the same problem: Exchange of files, metadata and communication - should work together as an orchestra and not as a bunch of individual soloists in different generes playing loudly at the same time.

Does that make sense?
 
It's been a while....

But that is mostly because it has been a bit.... Busy.


One of things I should brag about, is winning a 4 year tender for our national broadcaster for asset management for their series productions. In competition with Sony and some other big names.

But what I am equally proud of is that we by now serve a multitude of small productions where saving 2-3 positions and being able to work in a distributed manner and comply with Covid restrictions really matters to whether the productions are done ore not.

We have started to make a few usecase videos, and for now, I would like to start with this one.

https://www.youtube.com/watch?v=MI0bv4TT5II

These guys started off as soon as the Covid restrictions allowed in July to produce 8 episodes @ 40 minutes of "Nordic Noir" crime.

Principal started early July, the 8 episodes were delivered to distributer early October.

Editors and post was spread all over northern europe, and now we are starting another one.

Cheers
 
In a meeting today I was forced to make account, and the first year in product state where everything was sort of killed from march until august, we have been the backbone of 20 productions delivering 194 finished feature films or episodes of TV and a lot of them couldn't even have made it into startup without us.

That is a point of pride.

We have sort of made it our goal to serve the 99,9% productions that aren't James Bond or Avatar and where there isn't necessarily someone who natively speaks ACES. They shouldn't need to, as long as we do.
 
Busy times.

Supporting a lot oof productions is definitely something aside from wanting to support a lot of productions.

We really want to build QUineCore into an affordable product (not a service) that påroductions can take in as easily as starting up their editor.
We're getting there, but we still have tons of work to do.

I have been challenged to write a "timeline of Quine" in some context, and in doing that I came by the commercial we made in August 2018.

It's almost scary to see how far ahead of the curve we were already then, without taking Covid or other more recent events into account:

https://youtu.be/mjv00a8M0Do
 
You must log in or register to reply here.
Back
Top