Kostrowitzky.
koolkeysBy the way, I don’t mean to argue or labor the point. I just think that reality needs to be looked at.
I honestly don’t mean to be confrontational just for the sake of doing it. I do mean well!
Brent
adlaiusThis is a strange discussion that I don’t really understand. I like Podium a lot, but Ardour is a GPL’d, easy to use and high quality DAW (albeit only now coming around to MIDI support), Rosegarden and Hydrogen are available for sequencing/scoring/drum stuff, Renoise is there for the old-school crowd, and there’s an epic (EPIC) thread on the Reaper forums documenting Reaper-via-WINE in excruciating detail.
I’ve recorded a fair bit under Linux, and now happily use Podium under Windows. But forced to go back to Linux, I’d immediately go to Ardour. It’s already brilliant for audio, and once the MIDI implementation is finished, it’ll be pretty much unbeatable: fast/native to the OS, written by the guy who wrote JACK, free (beer/libre). Plus, watching Justin & co. try to get Reaper ported and debugged on OSX reminded me how porting apps is always slower, costlier, and more difficult than anyone expects.
Now, Podium on a dedicated hardware platform, on the other hand … 😉
druid@koolkeys wrote:
I think most threats can be avoided with smart browsing.
This is so very important I shouldn’t even need to quote it, but for some reason I do. There are still so many people who just aren’t smart when it comes to it; because the internet is a bonanza of multiple junkets and surely it’s all trustworthy! 🙂
Zynewave@kyran wrote:
It would be nice to claim Wine compatibility, but I do not have access to a Linux machine, so it’s going to take considerably more than half an hour.
The problem is connected with the wineasio driver, the source of which is available here. I think this looks very much like any other windows asio driver. I doubt much linux knowledge is required, but it is hard to debug ofcourse when you don’t have a machine present. If you have a spare machine try out a livedisk of ubuntu (in any of it’s variants) or do a wubi install: it installs ubuntu as an application in windows. No repartitioning needed, and you can just as easily remove it again later on. You can do a wubi install from the livedisc.
I’m willing to put in some effort here, so just let me know if you need something.
I had a quick look at the wineasio sourcecode. The problem may lie in what is returned by the ASIOGetSamplePosition() function. Can you please go to the Podium interfaces dialog report page and send/post the report for the wineasio driver?
kyranI’ve saved it as a txt file here:
http://files.getdropbox.com/u/464948/PodiumReport.txt
Let me know if you need something else.
thcilnnahoj@kyran wrote:
Maybe if Fritz could spare half an hour looking at this and then put a big “wine compatible” logo on his frontpage. I’ll happily make convenience scripts to install and configure linux boxes and update the wiki etc.
So, after it first f–ed me over royally during installation 🙄 I finally got my copy of Linux Mint working. If Frits can eventually make Podium run on Linux, I’d appreciate a little help in form of a “setting-up” tutorial.
Now I can at last take a peek at Ardour, Rosegarden, etc. later on… but don’t fret – Podium is where the heart is at. 😉
Zynewave@kyran wrote:
I’ve saved it as a txt file here:
http://files.getdropbox.com/u/464948/PodiumReport.txt
Let me know if you need something else.
Thanks. From the report:
ASIO driver status:
– ASIO sample position gaps: 6503 (-512)
That’s the problem. 6503 buffers * 512 sample buffer size / 44100 ~= 75 seconds of non movement, which is the exact duration of the interval measured in the report.
I checked the wineasio 0.7.4 sourcecode that you linked to, and it appears to set a valid sample position, provided that the jack_transport_query() function works as expected. I see that the sourcecode is a little experimental around this call. There is an outcommented “// if (ts == JackTransportRolling)” line, which could indicate that it is not working. The wineasio changelog also mentions a fix for the jack transport in the 0.7.3 wineasio release.
If you have other hosts that work with wineasio, then it must be because they ignore the sample offset provided by the ASIO driver. I’m checking the value in Podium, because some drivers may use this offset to indicate if buffer over/underruns have occurred. I’m not fond of compromising this security check because of faulty drivers, but I’ve added some code that ignores the sample offset if it is zero. Please try the 2.19 beta3 or the 2.19 final release and let me know if this fixes the wineasio issue.
kyranYour explanation made me think.
Jack has a transport control as well. If you set it to playback, the transport in podium starts functioning.
All the other apps I tried didn’t really need this. I don’t know why I didn’t try this before. I’m feeling kind of stupid here now. 😳
edit:
I tried beta 5 and it there is no change. Exactly the same behaviour as before, so you can put the check back in.
Hitting play in jack transport before you start working in podium fixes it though. I’ll put this in bold on my soon to be written FAQ 🙂
Zynewave@kyran wrote:
Your explanation made me think.
Jack has a transport control as well. If you set it to playback, the transport in podium starts functioning.
All the other apps I tried didn’t really need this. I don’t know why I didn’t try this before. I’m feeling kind of stupid here now. 😳
edit:
I tried beta 5 and it there is no change. Exactly the same behaviour as before, so you can put the check back in.Hitting play in jack transport before you start working in podium fixes it though. I’ll put this in bold on my soon to be written FAQ 🙂
Great. I am not familiar with Jack, so I didn’t know that transport functionality was something that should be configured. I’ll revert my ASIO code back to the way it was before.
KostrowitzkyYes, Linux!