Zynewave's Forum Page
Forum Replies Created
-
July 30, 2009 at 11:03 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.July 30, 2009 at 10:55 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.July 30, 2009 at 10:50 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.July 30, 2009 at 10:34 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.July 30, 2009 at 10:00 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.July 30, 2009 at 09:43 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymaster@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.
July 30, 2009 at 02:34 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymaster@Zynewave wrote:
@thcilnnahoj wrote:
Here’s a new problem that at least wasn’t in beta 1:
When I load a WAV file into beta 3 (by drag and drop from browser or Windows), the event doesn’t display the waveform until the arrangement window is refreshed(?) by opening/closing the inspector/embedded editor/mixer/etc.. It works when I import a file that already has a .mini waveform.Confirmed. I need to spend a little more time with this. Maybe I’ll upload a beta5 later tonight.
Beta5 is up, with fixes for all reported bugs. Let me know if you encounter more problems.
ZynewaveKeymasterBeta4 is up. That should fix the crash bugs. It was a simple error in the new optimized UI code.
@thcilnnahoj wrote:
Here’s a new problem that at least wasn’t in beta 1:
When I load a WAV file into beta 3 (by drag and drop from browser or Windows), the event doesn’t display the waveform until the arrangement window is refreshed(?) by opening/closing the inspector/embedded editor/mixer/etc.. It works when I import a file that already has a .mini waveform.Confirmed. I need to spend a little more time with this. Maybe I’ll upload a beta5 later tonight.
ZynewaveKeymasterWell, it appears a beta4 will be needed 😉 Thanks for testing.
The crash doesn’t appear in my debug build, so I’ll need to spend some time on this. I hope to have a beta4 ready within hours.
ZynewaveKeymasterBeta3 is up. This is hopefully the last beta. I’ll release 2.19 tomorrow, unless you find problems with this beta.
The beta has more UI speed optimizations, and a change that may result in compatibility with wineasio.
ZynewaveKeymaster@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.
ZynewaveKeymaster@moikkelis wrote:
“Podium is now built using the latest Microsoft VS v9 C++ compiler. All previous Podium releases were built using the trusty but aging VS v6. The new build should result in overall speed improvements. “
After that my podium crash all the time. 2.17 is rock solid for me. Anyone else have this kinda behavior? 😕
I’m uploading a new 2.19 beta later today. I’d appreciate if you could try this and let me know if you still get crashes. If you do get a crash, it will be a big help for me if you can describe, or better yet create a video, of how you get the crash.
ZynewaveKeymaster@moikkelis wrote:
So, it’s a line indicating the end of the arrangement?
Well, my english sucks, so decide to make little video. (it hosted by my own website, 100% safe. It is direct link, no audio in videos)
Thanks for the videos. That’s a very efficient way of illustrating feature requests and bugs. I like the idea with the vertical guide lines when dragging events. I’ll keep that in mind for a future update.
What program are you using for the screen capture?