From: Arnold K. <ar...@ar...> - 2009-12-27 14:56:54
|
Hi, On Sunday 27 December 2009 01:10:11 siris phi wrote: > ieee1394.isomanager.isotask_activity_timeout_usecs, which online docs says > is int64. Im not on a 64 bit machine, If it is int64, it is int64. No matter what architecture you are on... And don't worry about the "portability", ffado is mainly developed on 32bit machines, so I seriously doubt that the code is not working and not even compiling. Just tell the compiler to use 64 bits for that int and it will do so. > and am somewhat confused because > isn't the config file in python syntax? How does ffado decide what type it > is? It is read from a text-file, right? If its integer, its integer. If 64bit are needed to store the value, it depends on the variable it is stored in whether the value gets truncated or not. In this case not because the variable is int64. And the configuration-file is read both by C++ libffado and by python ffado- mixer... > I've played with a handleful of values, but no luck, so I figured I'd > ask experts. Unless you have tried _really_ big values that are only in the range of 64bit integers and it seems like it truncated the value, your problem is not with the bit-depth of the variable. Probably your problem is more with the value itself. Unfortunately I can't help you there. Arnold |