Linux...anybody using it?

[atraf11]

ya bitwig runs awesome on linux

[pc999]

Bug report for pydaw, latest version.

Code: Select all

pydaw.py crashed with Value Error in remove_note():list.remove(x):x not in list

That said the snap (inside the midi items) aren't working very well, I disabled it to make note less than 1/4, but after that I started to get very small ones I had to activate the snap again and disable to be useful.

That snap is a bit strange at times... but I cant really put the finger on it yet.

Hope it helps

UPDATE: Actually PyDaw still open and working


BTW other "bug" If I have a loop playing with a soled track it does what is suposed to do, but when I deactivate the solo it will still play solo, till I stop the audio and restart it.


And a FR : when someone edit multiple items it will soon not see the piano roll anymore, making very hard to know witch notes are entering in the piano roll.

But it is shaping nice, I will try t put the loop I am doing to discover PyDaw, later this night.





On a side, unrelated note, I tried to translate both hybrid drums and LMMS but their instructions to that give me errors, I tried to get help but so far I had little luck, if anyone have any idea...

[pc999]

ya bitwig runs awesome on linux

Any link or we should just envy you !

[jeffh]

Btw, does Ubuntu Vanilla come with some kind of USB creator as Mint does?

Yeah, you can find it in the startup menu under "Startup Disk Creator"(and that one is my recommendation), or they have full-on detailed instructions for all 37 different ways to do it here:

https://help.ubuntu.com/community/Insta ... omUSBStick

[jeffh]

Bug report for pydaw, latest version.

Code: Select all

pydaw.py crashed with Value Error in remove_note():list.remove(x):x not in list

Whenever you report a bug, could you please include the part that is either called "Stack Trace" or "Trace Back"? It makes it much easier to understand what went wrong...

That said the snap (inside the midi items) aren't working very well, I disabled it to make note less than 1/4, but after that I started to get very small ones I had to activate the snap again and disable to be useful.

That snap is a bit strange at times... but I cant really put the finger on it yet.

It was actually a fraction of a beat, so 1/4 = a 1/16 note, which I realized was a completely stupid way to do it a few minutes ago, so I made it proper 1/16 = a 1/16th note , and I added quantize settings for 1/64 and 1/32 notes...

...but... What kind of graphics do you have, and which driver are you running? Most of the bugs you've reported seem like some weird interaction between Qt and your graphics driver, because I've never been able to reproduce any of them on my systems.

UPDATE: Actually PyDaw still open and working

Yeah, it's virtually impossible to actually crash it and make the window go poof... But AppPort insists on showing that error window any time there's an unhandled exception, even though Python is smart enough not to crash because of it...

BTW other "bug" If I have a loop playing with a soled track but when I deactivate the solo it still play solo, till I stop the audio and restart it.

Yeah, that one has been a thorn in my side for a while, I'll try to fix it some time soon...

And a FR : when someone edit multiple items it will soon not see the piano roll anymore, making very hard to know witch notes are entering in the piano roll.

I'm not sure I understand, are you saying that the piano keys on the left are disappearing?

But it is shaping nice, I will try t put the loop I am doing to discover PyDaw, later this night.

Cool, I look forward to it.

[pc999]

Whenever you report a bug, could you please include the part that is either called "Stack Trace" or "Trace Back"? It makes it much easier to understand what went wrong...

Ok, I will see to it, actually it was been a little of lazyness once that we cant copy past it and that looked to be the relevant part. lol

It was actually a fraction of a beat, so 1/4 = a 1/16 note, which I realized was a completely stupid way to do it a few minutes ago, so I made it proper 1/16 = a 1/16th note , and I added quantize settings for 1/64 and 1/32 notes...

...but... What kind of graphics do you have, and which driver are you running? Most of the bugs you've reported seem like some weird interaction between Qt and your graphics driver, because I've never been able to reproduce any of them on my systems.

That makes more sense, I will see later.

I have a AMD 7770, with the proprietary drivers (9.something according to catalyst).

I'm not sure I understand, are you saying that the piano keys on the left are disappearing?

Yes.
When you scroll left they will go out of sight.

If you edit several (eg 4) midi items in group, like a single item of 4 measures (only way to do it if I am not mistaken) you need to scroll left to see the third and fourth item, at that time you cant see the piano roll anymore because it is at the beginning of the first item.

[StudioDave]

Hey Jeff,

I'm wrapping up the review, let me know if I need to update to the latest & greatest before final draft.

A quick report/question : As of 13.03-2 the File/New selection doesn't actually create a new file, it clears the track instruments but retains the existing regions and items. Kind of unexpected behavior, could you code it so that a default empty file comes up ?

Also, "PyDAW" or "PyDAW2" ?

Getting nicer all the time. I'm working on a demo (possibly) for the review, will link to it when complete.

dp

[jeffh]

I have a AMD 7770, with the proprietary drivers (9.something according to catalyst).

Ah... yeah... I have 2 AMD systems, but I always test them with the open driver, but one of them has the Catalyst driver on one partition, I'll start testing it with that too...

Yes.
When you scroll left they will go out of sight.

If you edit several (eg 4) midi items in group, like a single item of 4 measures (only way to do it if I am not mistaken) you need to scroll left to see the third and fourth item, at that time you cant see the piano roll anymore because it is at the beginning of the first item.

Ah... I got it now... I'm still trying to figure out how to do that in Qt, it seems tricky as hell... I think as a possible intermediate workaround, I'm just going to shade the black keys darker than the white keys on the grid, which should at least improve the situation somewhat until I can figure out how to make the keys stick to the left side of the screen...

[jeffh]

Hey Jeff,

I'm wrapping up the review, let me know if I need to update to the latest & greatest before final draft.

Ah... Thought you were already done with it... In that case, why not just go for the latest Git, I've fixed all of the issues you reported there (and even some issues you didn't report)... It once again looks quite different than a week or 2 ago, LOL...

EDIT: That latest Git will be released in the next couple of days, BTW...

A quick report/question : As of 13.03-2 the File/New selection doesn't actually create a new file, it clears the track instruments but retains the existing regions and items. Kind of unexpected behavior, could you code it so that a default empty file comes up ?

Hmmmm.... I'll investigate that, I can't remember the last time I used the "New" menu option, so I probably shouldn't be too surprised that it doesn't work anymore...

Also, "PyDAW" or "PyDAW2" ?

Really just PyDAW I guess, the PyDAWx-YY.MM-[release#-for-month] tracks the version by when it was released, but PyDAW1/2/3/4/5 really indicate when I've broken backwards compatibility for the sake of adding big new features... PyDAWv1 and PyDAWv2 can be installed in parallel on the same machine, but each has their own file format... PyDAWv3 will be the same way, new project format, but can be installed alongside PyDAWv2, and so on... As PyDAW matures, the number of backwards-incompatible releases will slow to a crawl...

Getting nicer all the time. I'm working on a demo (possibly) for the review, will link to it when complete.

dp

Cool, sounds good

[jeffh]

A quick report/question : As of 13.03-2 the File/New selection doesn't actually create a new file, it clears the track instruments but retains the existing regions and items. Kind of unexpected behavior, could you code it so that a default empty file comes up ?

I wasn't able to reproduce this behaviour... To make sure I'm understanding you correctly:

1. File->New (project)
2. Select a folder and give the project file a file name
3. Click "OK"

Expected: Region and Song editor get cleared
Actual: The existing regions/items are still there

I got the expected behaviour, ie: everything gets cleared, but let me know if I'm misunderstanding...

[jeffh]

Eh... Maybe I should create a separate PyDAW thread

In my latest Git, I've got the piano roll grid shaded (and looking pretty nice if I do say so myself), and I've fixed every other known bug except:

1. Dave's file->new bug... Still waiting on confirmation, or exact steps to reproduce
2. @PC999: I did find some weird issue with quantize being off sometimes when editing multi-items, I think it might be similar to the Dave's bug with the CC envelopes that I fixed earlier... I think that may be the weirdness you were referring to...

As soon as those 2 things are sorted out (and if I don't find anything else), then I'll do another release...

[StudioDave]

Hmmmm.... I'll investigate that, I can't remember the last time I used the "New" menu option, so I probably shouldn't be too surprised that it doesn't work anymore...

Btw, I just click File, then New, then I name the new file, click OK, and I still have the regions and items from the previously loaded song. I checked it before sending this message, the problem here is happening on 13.03-2, as mentioned.

Best,

dp

[jeffh]

Hmmmm.... I'll investigate that, I can't remember the last time I used the "New" menu option, so I probably shouldn't be too surprised that it doesn't work anymore...

Btw, I just click File, then New, then I name the new file, click OK, and I still have the regions and items from the previously loaded song. I checked it before sending this message, the problem here is happening on 13.03-2, as mentioned.

Best,

dp

Awwww... Crap... I think I just realized what's happening...

You're trying to save the file to the same directory, aren't you? That file you save to is actually just a placeholder, the folder itself(and it's numerous files and sub-folders) is the project... Any .pydaw2 file in that directory will point to the same project...

I'll add an error message if the user attempts to place the new file in the same directory...

Aside from that, I've really plowed through the bugs today, I think I have literally everything fixed, including some really nice fixes/enhancements to the piano roll...

[StudioDave]

Hey Jeff,

Thanks for the tip on File/New, that does remove all regions and items. However, I noted that MIDI data and control curves from the previous project were still present in their editors.

Some clarification re: the gain curve bug, the error occurs in multi-item edit mode. I select a plugin (Ray-V) and apply a control (Filter Cutoff). I add a breakpoint at 0 and one at the end of the display graph, then I add a breakpoint in the middle. If I move that breakpoint it snaps to the end, on top of the final breakpoint I already added. It keeps snapping to that position whenever I try to move it.

Btw. a Clear function would be helpful for the CC and pitchbend curves (though it is easy enough to delete them by block selection).

I recorded some MIDI input today, no problems with an Akai LP25. Not so lucky with audio recording, but it could be a configuration detail. Any tips for audio input ?

Best,

dp

[codec_spurt]

Btw, does Ubuntu Vanilla come with some kind of USB creator as Mint does?

Yeah, you can find it in the startup menu under "Startup Disk Creator"(and that one is my recommendation), or they have full-on detailed instructions for all 37 different ways to do it here:

https://help.ubuntu.com/community/Insta ... omUSBStick

Thanks. It's a great program, I nearly always have success with it when doing Minty flavours. I'm sure that will work perfectly.


cheers.