Propose your solution
Attachments
No attachments.
Duplicates
Comments
|
|
i had the same drama with my video camera via firewire
after some searching i found how to fix it and apparently its locked down to security reasons
but it should at least bring up some kind of warning box or the likes and ask you if you want to turn on fireware data capture
+1 from me
|
|
|
It would be really handy if Ubuntu could liaise with Dan Dennedy (who wrote Kino and dvgrab), to ensure that each new version of ubuntu works with these programs.
These are both used for firewire capture, and do it well (when working).
Ubuntu has changed the way it deals with firewire (programs and permissions, and groups) at some version upgrades. And it knocks the system out, till the user figures it was the upgrade they did between the last firewire capture and recent.
If we want a multimedia Ubuntu, then we need to make sure that we can load the media in the first place.
Firewire has a number of advantages over ordinary video capture;
- the sound is always in synch (or maintains the same offset)
- all capture devices are in synch
- data streams can go to hard drive with lower impact on CPU.
- more than one device can record or process the data being sent on any firewire channel.
- up to 63 channels.
It might be wise not to tell Ubuntu "how" to solve these problems,
as Dan is pretty good at getting them solved, and some of the multimedia team at Ubuntu could work with him to ensure that optimum solutions are obtained.
|
|
|
+1 a very good sugesstion.
Good Idea
|
|
|
|
i'm using Ubuntu on a MacBook since almost 2 years, and still without being able to use the iSight camera, which is a IEEE one, just like about this idea post.
|
|
Auzy
wrote on the 14 Sep 08 at 11:45
|
|
|
|
Nitrofurano, even in windows, the isights last I checked didn't work that great either.
|
|
|
In some versions of Ubuntu, Kino recommends enabling firewire access by using uDev.
Another way to do it is dv1394, which is not recommended.
But I have that method to work good enough for starters,
as i wasn't interested in controlling the camera from the pc - just capturing the video from what ever was plugged in.
|
|
Auzy
wrote on the 25 Sep 08 at 12:09
|
|
|
Its a lot more complicated then this though. For instance, in Nitrofurano's case, its hard to tell if its a driver issue or not. The old firewire isights were crap.
However, yeah, nobody should need to touch anything for firewire cameras which should work, to work. On OSX and windows nothing is needed.
|
|
|
With Hardy Heron, the issue is on permissions put on the /dev/raw1394 driver.
It is rw-rw---- (root,disk) .
It should either be rw-rw-rw , or atach to a group everybody can be easily belongs to without being a security hole.
And this should be DOCUMENTED.
|
|
|
Hi, we are in 2011 and i can't beleive this is not sorted yet.
Seriously ? Linux ubuntu 2.6.32-33 is not enough to do that ?
For a start why would you restrict camera usage to root only by default ?
Then, if you *really* want or need to do that, why is there no message/warning when the access is denied to give you a clue about what is going on (using Kdenlive here for instance).
Once again, a VERY little thing (meaning easy to detect/correct) that keeps Linux from being user friendly ...
(Best of all but not directly related to this, Kdenlive freezes the entire system when starting to record from my camera :-o Back to Windows just to get my miniDV tapes on disk).
|
Post your comment
|
